Database Users

Key Info on bricked Artemis/Orbit

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
Click to expand...
Click to collapse
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
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.
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)
Click to expand...
Click to collapse
Gotta be something inside which gets heated up or cuts out. So opened it up and cleaned the whole interior and this guide, 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
Close-up of the cell

Artemis Bootloader Commands
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.
fdp24 said:
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.
Click to expand...
Click to collapse

SOLVED!!!
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)

htc 3300 error 300
no waaaaawwwwooooooooooooo iii
htc p3300 briked with error 300 help help:mad

hellllllllllllllllllllllllllllllllllllps boys pof pof
newwws newwws
what happend this forum can be help us my artelis blocked error 300 in
all rom

[Q] Self-inflicted WiFi configuration trouble

SOLVED: I restored the "WiFi Access Points" backup from Titanium and I'm back online. Is there any way to get details on what files that entails?
Original query:
I'm trying to connect to a corporate IEEE8021x network, and I hand-edited my /data/misc/wifi/wpa_supplicant.conf to add my corporate network.
This didn't work, the WiFi wouldn't even enable; the top item in the Wi-Fi Settings screen Says "Error". I deleted the entry I added, but the results are the same. I then deleted everything except the first two lines
ctrl_interface=tiwlan0
update_config=1
and it appears to try harder to enable it, and it shows on for about 15 seconds, but no access points show up, the GUI asks if I want to forceclose Settings, and then it turns off.
wpa_supplicant.conf had those two lines in it, and the usual list of access points I've seen, nothing else.
Is there some other WiFi config file I need to clear out, or GUI access to this stuff? I just want to get open-access APs working again for now.
dmesg reports:
TIWLAN: driver init
TI WiLink 1271 SDIO: Driver loaded
evt_wifi_power: 0
evt_wifi_set_carddetect: 0
mmc2: card_present 0
kxtf9 1-000f: IRQ TAP2 [2]
kxtf9 1-000f: IRQ TAP2 [4]
wlanDrvIf_Stop
kxtf9 1-000f: IRQ TAP2 [1]
kxtf9 1-000f: IRQ TAP2 [8]
tiwlan: 20 sec os_SignalObjectWait timeout
evt_wifi_set_carddetect: 0
evt_wifi_reset: 1
evt_wifi_power: 0
and the driver unloads
Thanks!

[Q] touch screen not responding only when sd card is present

Hi all,
I have a problem with my defy, whitout fall or update the touch screen stop responding.
After some resets & sbf flashing I've noticed that the touch screen is ok only when there is no sdcard.
I've tried over sdcards with no more success.
The sdcard is readable, I can access with adb.
Clockworkmod access the sdcard too.
With sdcard dmesg :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_enq
touch_write: Error while trying to write 2 bytes
qtouch_set_addr: Can't send obp addr 0x 0
qtouch_process_info_block: Cannot read info object block
qtouch_ts_probe:Cannot read info block -121, checking for bootloader mode.
Without sdcard :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_en
qtouch_process_info_block: Build version is 0x10
qtouch_process_info_block: Object 5 @ 0x00f2 (9) insts 1 rep_ids 0
qtouch_process_info_block: Object 6 @ 0x00fb (6) insts 1 rep_ids 1
qtouch_process_info_block: Object 38 @ 0x0101 (8) insts 1 rep_ids 0
(...)
Can it be a HW problem ?
What do you think I can do ?

Questions go in the Q&A section

CharlyBrok said:
Hi all,
I have a problem with my defy, whitout fall or update the touch screen stop responding.
After some resets & sbf flashing I've noticed that the touch screen is ok only when there is no sdcard.
I've tried over sdcards with no more success.
The sdcard is readable, I can access with adb.
Clockworkmod access the sdcard too.
With sdcard dmesg :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_enq
touch_write: Error while trying to write 2 bytes
qtouch_set_addr: Can't send obp addr 0x 0
qtouch_process_info_block: Cannot read info object block
qtouch_ts_probe:Cannot read info block -121, checking for bootloader mode.
Without sdcard :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_en
qtouch_process_info_block: Build version is 0x10
qtouch_process_info_block: Object 5 @ 0x00f2 (9) insts 1 rep_ids 0
qtouch_process_info_block: Object 6 @ 0x00fb (6) insts 1 rep_ids 1
qtouch_process_info_block: Object 38 @ 0x0101 (8) insts 1 rep_ids 0
(...)
Can it be a HW problem ?
What do you think I can do ?
Click to expand...
Click to collapse
AFAIK, it is HW related..
Best choice, get it to the SC..

Maybe I'll try to change the digitizer (20€ on ebay).
Warranty period is finish.

I want more log,
The goal is to enable logging debug in qtouch_obp_ts
I put in /system/etc/init.d/77debug
Echo 0xFF > /sys/module/qtouch_obp_ts/parameters/tsdebug
But no change at all...
What I am doing wrong ?
Envoyé depuis mon A500 avec Tapatalk

Eris msm_pm_wait_state reboot syndrome?

Hi folks,
Long time since I popped in here.
I'm wondering if you've seen behavior similar to this before:
Spontaneous reboots during suspend/resumes (that is, an app running but the screen is off) which *sometimes* result in output like this at the tail end of /proc/last_kmsg
Code:
[ 2331.773132] msm_pm_wait_state(80, 0, 0, 0) failed 10d29
[ 2331.773132] msm_sleep(): msm_pm_wait_state failed, 10d29
[ 2331.929382] msm_pm_wait_state(80, 0, 0, 0) failed 10d29
[ 2331.929382] msm_sleep(): msm_pm_wait_state failed, 10d29
No errors detected
I can manage to run logcat as a background process (the syndrome seems to involve the kernel PM (Power Management) suspend/resume function, as it refuses to occur when plugged in to USB); sometimes I also see
Code:
09-01 21:07:58.371 273 416 E RPC : error writing RPC packet: 22 (Invalid argument)
as the last line in the logcat. I don't know what is lost in the logcat output after that due to buffering, but the "No errors detected" in /proc/last_kmsg seems to point away from a kernel panic. And yet the phone reboots in a decidedly ungraceful fashion... if all filesystems were flushed I would expect to see something in the logcat about a reboot.
Test conditions:
Kernel: 2.6.29-DecaFuctCFS-dirty-9ff84b92 ([email protected]) (gcc version 4.4.0 (GCC) ) #5 PREEMPT Thu Jan 27 22:14:44 EST 2011
ROM: Condemned Soul's CCM7-V21 Vanilla
CM CPU min/max: 245/729 (* I don't think this matters)
Governor: ondemand
Other: Screen must be off and phone disconnected from external (USB) power for this reboot to occur; my test condition also includes the phone in Airplane mode. (I do not know if the latter is necessary for bug expression).
I can add more detail, but I didn't want my post to get too long. I can cause this to happen deterministically (a delay of one to several minutes before the phone reboots). The app involved uses the GPS hardware...
Anyhow... does this syndrome sound familiar at all?
bftb0
PS Yes this is a real-world scenario - I want to do GPS track recording in areas without cell/wifi service, so... running without USB power and no radios (for battery conservation) is a priority.

[HELP] Z00TD/ZE551KL stuck in EDL mode, unsure what to do.

I have a Zenfone 2 Laser (ZE551KL) and it's currently stuck in EDL mode. The bootloader was locked when this happened, and the phone was running stock Android M rom. I'm not sure what happened, but I can guarantee it is not a hardware failure.
When I first plugged the phone in and ran EDL, the partition table (edl printgpt) was empty. After I went, grabbed the firmware and the GPT file (I tried gpt_main, gpt_backup, and gpt_both, same end result) and flashed it, I get the following:
Code:
$ edl printgpt
Parsing Lun 0:
GPT Table:
-------------
sbl1: Offset 0x0000000000004400, Length 0x0000000000140000, Flags 0x0000000000000000, UUID b6e183fd-7e32-6aab-45a0-95aa05d488ff, Type 0xdea0ba2c, Active False
DDR: Offset 0x0000000000144400, Length 0x0000000000008000, Flags 0x1000000000000000, UUID 12145d01-36e4-dabb-43ee-d41814020b99, Type 0x20a0c19c, Active False
rpm: Offset 0x000000000014c400, Length 0x0000000000080000, Flags 0x0000000000000000, UUID a6cde2ba-f246-d267-4e32-27a784384929, Type 0x98df793, Active False
tz: Offset 0x00000000001cc400, Length 0x0000000000080000, Flags 0x0000000000000000, UUID 65484ccf-89c1-6697-724e-ca807a503232, Type 0xa053aa7f, Active False
aboot: Offset 0x000000000024c400, Length 0x0000000000500000, Flags 0x1000000000000000, UUID d85a0017-ca5e-5ae5-7501-e91c6e879873, Type 0x400ffdcd, Active False
hyp: Offset 0x000000000074c400, Length 0x0000000000080000, Flags 0x0000000000000000, UUID e8e93198-beea-0f83-ba35-62b457a963c2, Type 0xe1a6a689, Active False
Total disk size:0x0000000000004400, sectors:0x0000000000000022
I made sure to flash all the partitions using the appropriate files from the latest firmware from ASUS's website. (sbl1 = sbl1.mbn, etc.)
Unfortunately, the phone simply didn't boot. I tried a final "hail mary" of sorts, and I ran the command "edl setbootablestoragedrive 0". The command returned success, but unfortunately, nothing changed.
Any help is appreciated, thanks in advance.