PDA

View Full Version : Key Info on bricked Artemis/Orbit


softinker
26th July 2008, 12:43 PM
Got an XDA orbit two days back and it won't boot. Once when booted, it got stuck in the splash screen saying O2 and showed the protocols:



IPL:1.25.001
SPL:1.25.000
GSM:2.67.90
OS:1.25.00




It didn't go past this screen and a 4-sec press on power button switched it off. Any number of soft resets wouldn't solve the issue and there was this peculiar problem of the screen going dull and then fully dark, but u can see that the device is not off coz the screen is letting out a dull glow. Resetting switched off the phone.

Thinking it might be a battery issue, plugged in the USB power, but then there was no indication that it was charging. After sometime tried switching on and the unit was dead. Pulled out the battery and reinserted after
arnd 10 mins and did a hard reset. (Pulling battery out and reinserting was done so many times that I'd from now on refer to it as BOutReIn-10min;10min being the time it stayed out)Booted after the hard reset and it

started showing charge indication-orange, green n all.Then after setting the preferences, worked for abt 2 mins and the same problem of screen going dull and black gradually. Soft resets, hard resets, trying bootloader mode - nothing works. Just a brick with a nice thumbdial and trackball.DEAD.

Downloaded the Original O2 Uk ROM Image ARTEIMG.nbh (http://rs80l33.rapidshare.com/files/41574866/9300456/Arteimg.nbh)


BOutReIn-30min and tried flashing the ROM from PC.75% and the same
dimming of the screen, but in another pattern of going up from the bottom.

BOutReIn-5min and tried flashing from SD card (http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing).


After the "Reading from Sd card" message, while installing first OS, it showed same problem.
Finding that the timing of the problem is connected to the time the battery is out (or the time the unit is not being used), BOutReIn-6hrs and tried SD card flashing which went successful, but when the unit reset after the process, it got stuck in bootloader.Oh Oh! More problematic? Donno..Another reset, still BL.One more, still in BL, but the the screen went dull after 2-3 secs. It hasn't come out of the BL since then.


Possible reasons
1.Corrupt OS(most probable)
2.corrupt bootloader(less probable, but not impossible.the fact that it shows bootloader means it is intact,i think)
3.Mainboard problem(least probable, but seeing the way things go, i had started to suspect this, especially coz of the screen dimming)



Gotta be something inside which gets heated up or cuts out. So opened it up and cleaned the whole interior and this guide (http://wiki.xda-developers.com/index.php?pagename=Artemis_Disassemble), alongwith commonsense, came handy.


Then i found a small button cell soldered to the board. The presence of this really caught my attention coz i have had bad experiences with such things in older mobile phones and GPS units. My eTrex Vista went bad after some days of non-use and I found a leaking internal rechargeable cell just like this(3.3v), soldered to the board and it served the purpose of powering the memory where the system settings are saved. That GPS unit didn't come with a flash memory; tho Garmin learnt it fast and switched to Flashroms. Actually the only way of saving such things in GPS units is keeping operational batteries in the unit always and checking them frequently.

A quick check gave the cell voltage as 0.65v which is too low for such chemistry. Then connected the USB charger to the board and measured at the terminals and it was the same. it showed that it is not getting any
supply. Also, there was slight corrosion on the button cell body, which indicated that it might start leaking anytime, if not already. Cleaned up the body, brushed the whole area clean of any impurities and recharged it
using 2 duracells connected to the +/_ terminals and the voltage climbed to 1.7v. Kept it like that for sometime and checked the voltage once more, which showed 1.5v. This showed rapid voltage falling and that is not good news. The battery surely is on its last leg.

Not wanting to give up, and to test really whether the cell contributes to the system settings (otherwise, what is it there for?), connected everything rt back and did an SD card flashing which was successful and the unit booted after reset and started charging and everything was going smooth. Showed splash screen and when it was about to get into the customization phase, the screen began to dim...:(..

Sad, but I think that's at least some point to start. The board is having problems and that's why it doesn't charge the internal cell and the Artemis worked while the cell still had charge. When kept on working, the internal cell has discharged enough and more and that can be the beginning of so many problems which show up in bricked units (mostly Artemis).

No power
No charging
Stuck on bootloader
unit hanging when using


Now I don't think I can service the board successfully myself.Even professional servicing would be very costly. An alternative would be to replace the board.

Now i would like to know if such an internal rechargeable cell is there in other HTC devices. If so, then it is the culprit. If this is there in only Artemis-based PDAs having GPS, then it may or may not be the problem as it might be there just for the GPS, just like in older Garmins. Also, if that is the case, new GPS PDAs won't be having that cell too, after learning from such a mistake.

Let the discussion begin!!!

Hi-Res pics are here:
Internal Rechargeable cell (http://gpbipin.googlepages.com/internalcell.jpg)
Close-up of the cell (http://gpbipin.googlepages.com/internalcell_closeup.jpg)

softinker
26th July 2008, 01:08 PM
While researching on the problem and its possible solutions, I stumbled upon this information on a Trinity discussion board. This is very valuable information (read last resort) to those out there like me whose Orbits are not stable/dead. (No pun intended ;))Giving due credit to its author, fdp24, I am posting it here.

The actual thread is here (http://forum.xda-developers.com/showthread.php?t=287077&page=2).

rbmc is not in spl in Artemis device. On Trinity probably too.
These are some commands for Artemis:
Could be similarity for Trinity
CASE SENSITIVE!

Cmd>fm
Wrong parameters of FM Command!!
Usage:
fm [command] [frequency]
where:
if[command] = i Initialize FM.
if[command] = o Power on FM.
if[command] = f Power off FM.
if[command] = t Tune FM channel to [frequency].
if[command] = a FM auto seek test.
if[command] = m Mono(1) or Stereo(0).
if[command] = v Volume (0x00 - 0x0F).
if[command] = u Mute(0)
if[command] = g AGC(1)
if[command] = h Set seek threshold (0x00 - 0xFF).
if[command] = s Seek Up(1) or Down(0).
if[command] = r Get RSSI (0x00 - 0xFF).
if[command] = c Get current channel [frequency].
if[command] = d Get RDS data (1 - 10 groups of data).

************************************************** ************************************************** *
Cmd>cpldver
xsvfExecute - CpldType=1

SUCCESS - Completed XSVF execution.
CPLD Ver[0]=1
CPLD Ver[1]=FC
CPLD Ver[2]=26
CPLD Ver[3]=5

SetDsbDBGMSGT

Unknown yet.
************************************************** ************************************************** *
Cmd>ReadExtROM

Dump Ext ROM to MTTY terminal
************************************************** ************************************************** *

Cmd>WLANReset

Usage:
WLANReset 1(or0)
set SDIO: 0-WLAN ;1-SDMC.

Cmd>WLANReset 0
WLANReset(FALSE)

Cmd>WLANReset 1
WLANReset(TRUE)
************************************************** ************************************************** *

Cmd>SDSelect

Usage:
SDSelect 1(or0)
set SDIO: 0-WLAN ;1-SDMC.

Cmd>SDSelect 1
Select SD Card
************************************************** ************************************************** *
Cmd>emapiWlanMac
Notice: This MAC address takes effect only when your platform is EEPRON-less configuration. Please use (emapiTest) to verify it !
Copying GSM DATA image to SDRAM:00004000

Wlan data header ++++++++++++++++++++
Signature : 0xEE1250
UpdateStatus : 0x2
UpdateCount : 0xA
BodyLength : 0x1A1
BodyCRC : 0x4349311B
Wlan data header --------------------------
0x00000000
0x00000009
0x0000002D
0x000000D2
0x000000D5
0x000000FB
************************************************** ************************************************** *
Cmd>emapiTest
+emapiTest
1. Power on WLAN
2. Reset WLAN
3. Switch MUX to WLAN
4. Enable WLAN clock
5. Init WLAN SDIO interface
6. DeviceID Test
DeviceID = 4030xxx
EEPROMless configuration!
-emapiTest
************************************************** ************************************************** *
Cmd>emapiPwrDwn
************************************************** ************************************************** *
Cmd>emapiRead
Parameter Wrong!!
************************************************** ************************************************** *
Cmd>getdevinfo
Need password!
************************************************** ************************************************** *
Cmd>wdata
Usage:

wdata [StartAddr Len]



Write data to memory(if write to ROM, need erase first).

StartAddr : Start address of memory.

Len : How many bytes will be written.

Length must not more than 0x10000 bytes(buffer limitation).

Write to RAM: 4 bytes(CRC checksum limitation).

1 byte(in user mode).

Write to ROM: 4 bytes(CRC checksum limitation).

2(16-bit)/4(32-bit) bytes(in user mode).

Write to ROM(16-bit data bus): 32 bytes(writebuffer mode).

Write to ROM(32-bit data bus): 64 bytes(writebuffer mode).

Length must be 4 bytes boundary(CRC checksum) if not in user mode.



After command execute, then send out the data to terminal.

Data format: HTCS(4 bytes)+DATA+checksum(4 bytes, if not in user mode)+HTCE(4 bytes).
************************************************** ************************************************** *
Cmd>password
Usage:

password [String]
Enter the password string to enable wdata, erase and rbmc functions.
************************************************** ************************************************** *
Cmd>set
Usage:

set [Type Value]

Set control flags.

Type(hex) : Control function types.

Value(hex) : Setting values for types.

Type 1(Operation mode): 1(auto) and 0(user).

Type 2(Back color on/off): 1(on) and 0(off).

Type 4(Front color value): 16 bits data

Type 5(Background color value): 16 bits data

Type 6(Set color of screen): Fill color to whole screen one time.



Current flag settings:

Type 1(Operation mode flag): g_cOpModeFlag=(0x0).

Type 2(Back color flag): cBackColorShowFlag=(0x0).

Type 4(Front color): g_dwFColor24bit=(0x0).

Type 5(Background color): g_dwBColor24bit=(0xFFFFFF).

Type 6(Set color of screen): None.

Type 32: Unlock Flash Command

Set control flags.
************************************************** ************************************************** *

Cmd>SetDebugMethod
Copying GSM DATA image to SDRAM:00004000

Default DebugTransport Value =00000000
Current Usage:
0 No Debug
A UART MTTY Output Debug Message
B USB MTTY Output Debug Message
************************************************** ************************************************** *
Cmd>checksum
Usage:

checksum addr len

Return CRC checksum of memory.

In user mode: Show 4 bytes of CRC checksum value on display of terminal.

In auto mode: Send 4 bytes of CRC checksum value to terminal with data format.
************************************************** ************************************************** *
Cmd>ResetDevice
no comments
************************************************** ************************************************** *
**When CID is locked.
Cmd>ls
clean up the image temp buffer at 0x8C100000 Length 0x03A00000
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Clear image temp buffer done .
MTTYDownloadImage
Not allow operation!
Error : DownloadImage return error (code = 0xFFFFFFFF)
**When CID is locked.
************************************************** ************************************************** *
**When CID unlocked
Cmd>ls
clean up the image temp buffer at 0x8C100000 Length 0x03A00000
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Clear image temp buffer done .
MTTYDownloadImage
start download
==CreateFile err==
**When CID unlocked
************************************************** ************************************************** *
Cmd>GPSRouting

Dump code to mtty console.
************************************************** ************************************************** *
Cmd>BTRouting

Dump code to mtty console.
************************************************** ************************************************** *
Cmd>BTRouting
+GSM_Modem_Init : include DAGON
Copying GSM DATA image to SDRAM:00004000

GSM - dwSize = 3479D

GSM Page0

GSM - dwSize = 45457

GSM Page1

GSM - dwSize = 4B768

GSM Page2

GSM - dwSize = 4E0A9

GSM Page3

GSM - dwSize = 4B4C4

GSM Page4

GSM - dwSize = 4C71F

GSM Page5

GSM - dwSize = 2958E

GSM Page6

GSM - dwSize = E8D8

GSM Page7

Copying GSM CODE image to SDRAM:00000000

ARMBOOT = 1 --> boot from CS3
Reset ARM 7 -- ok


Please close MTTY USB connection and open BT Testing program...


************************************************** ************************************************** *

************************************************** ************************************************** *

************************************************** ************************************************** *

************************************************** ************************************************** *

************************************************** ************************************************** *

************************************************** ************************************************** *

password BsaD5SeoA - this is static password used during flashing device. (USB sniffer)
battery seems to be charging during bootloader.

If you stuck at bootloader during manipulations with commands, try this:
password BsaD5SeoA
ruurun 0

Alternatively, you can run rom flasher even on CID locked device. It will give you error message about Device ID or something, but your device will be back to normal and boot normally.

softinker
27th July 2008, 09:32 PM
The Orbit unit is up and running now....!!!!!WOOOOOOOOOOHOOOOOOOOOO!!!
I'll post what all i did to get it up.
now i really think the internal rechargeable cell is the culprit.
But for now, I'm one happy person, even if the Orbit in question is not mine.

GSM-working
GPS-working
Bluetooth-working
IR-working
USB charging
camera-working
sd card-working
fm radio-working
mouse ball and thumbwheel-working
Wifi-not turning on(need to investigate on this)

cafeazz
15th September 2008, 12:45 AM
no waaaaawwwwooooooooooooo iii
htc p3300 briked with error 300 help help:mad::mad

cafeazz
12th November 2008, 11:22 AM
newwws newwws
what happend this forum can be help us my artelis blocked error 300 in
all rom :mad::mad: