Database Develop

HELP!"data crashes.contact service center"

hallo.
got a spv m3000 with the following problems:
1. the camera doesn`t work.. it`s shows some sort of green and black horizontal stripes [with a sim in it or not]
2. it works ok without a sim as a pda, but when i put a sim in it.. it shows "data crashes.contact service center"
using the Wizard service tool 4.2.1 i checked and it was cid locked, besides the cid was key 88 and DOC chip unique ID was 66
i followed http://forum.xda-developers.com/showthread.php?t=285435 and installed button`s rom and changed the cid key into 66 using WST and the keys provided ..
AND IT STILL DOESN`T WORK [i did everything fine, a couple of times]
i`m now currently here:
Wizard Service Tool v4.2.1
31/03/08 22:16:27
CPU Manuf. FAILED
MODEL: Wizard
IMEI: 356381000075907
=> Bootloaders:
IPL: 1.01 (G3 device)
Built on Sep 19 2005 at 18:00:32
Copyright (c) 2003 High Tech Computer Corporation
Getting more info...
=> Firmware:
OS: 5.1.xxx (Build 14406.1.1.1)
ROM: 5.1
Registry AKU: .1.1.1
Radio values FAILED
=>Extended_ROM:
Version: Unknown
Name: Extended_ROM
Status: visible
Getting drives,disks and partitions info...
=> Drives and partitions:
|--Handle--|---Size---|
8fb7d622 - 1.87G (0x778e0400)
0fb891ee - 10.00M (0xa00000)
aea14ec6 - 10.00M (0xa00000)
ceae9ece - 48.23M (0x303c000)
cfb2bf36 - 51.06M (0x3310000)
afb2bd76 - 2.88M (0x2e0000)
0fb2bd52 - 3.06M (0x30fc00)
=> DOC chip unique ID:
00000000a93802021223005c0a0905b8
Key Index: 66
All Done.
CID INFO:
Reading CID block...
Calculating CID block sum...
CID checksum: 2BB2824F
Decrypted stored sum: 626DAEC493E695B6
Decrypted calcd sum: 626DAEC493E695B6
Key index : 88 - Block index: 139
CIDkey: MODULESN
CID IMEI: 356382000275596
CID: 11111111 (SuperCID)
Phone is already CID unlocked!
any ideas?
thanks
tintome

not it works..
yey..10x..

tintome said:
not it works..
yey..10x..
Click to expand...
Click to collapse
hmmm, what happened? Did you fix it or not?
Did the Data Crashes Project worked for you? If so leave feedback in its thread. tx

[Solved] Any luck with WPA Enterprise using CM 3.9.3 and up?

Since Cyanogen ported over the WPA Enterprise support from the donut branch, I have been eagerly wanting to get onto my corporate network.
With 3.9.5 running on my phone now, I can see the SSID of my network
show up in the list of available APs. It is listed as secured with WPA-EAP.
When I click the AP, I can set the EAP method (PEAP), the Phase 2 authentication (MSCHAP2),etc...
When I try to connect, it fails and gives a Disconnected status. When I
enter the following in Terminal:
Code:
su
cat /data/misc/wifi/wpa_supplicant.conf
I can scroll to the bottom and see the following:
network={
ssid="____"
key_mgmt=WPA-EAP
group=CCMP TKIP
priority=23
}
It does not appear to keep the settings for PEAP or MSCHAP2...
I manually edit the entry to the following:
network={
ssid="___"
key_mgmt=WPA-EAP
group=CCMP TKIP
eap=PEAP
identity="xxxxx"
password="xxxxx"
phase2="AUTH=MSCHAPV2"
priority=19
}
When I push the changes back into the /data/misc/wifi directory and restart,
it now tries to obtain an address... unsuccessfully... lol...
Here is the output from wpa_cli:
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>Trying to associate with 00:13:60:d4:e5:70 (SSID='___' freq=2462 MHz)
<2>CTRL-EVENT-STATE-CHANGE id=4 state=3
<2>CTRL-EVENT-STATE-CHANGE id=4 state=4
<2>Associated with 00:13:60:d4:e5:70
<2>CTRL-EVENT-EAP-STARTED EAP authentication started
<2>CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
<2>CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
<2>CTRL-EVENT-STATE-CHANGE id=4 state=5
<2>CTRL-EVENT-STATE-CHANGE id=4 state=5
<2>CTRL-EVENT-STATE-CHANGE id=4 state=6
<2>CTRL-EVENT-STATE-CHANGE id=4 state=6
<2>WPA: Key negotiation completed with 00:13:60:d4:e5:70 [PTK=TKIP GTK=TKIP]
<2>CTRL-EVENT-STATE-CHANGE id=4 state=7
<2>CTRL-EVENT-CONNECTED - Connection to 00:13:60:d4:e5:70 completed (auth) [id=4
id_str=]
<2>CTRL-EVENT-STATE-CHANGE id=4 state=8
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=8
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=2
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
.
.
.
I am still reading up on all of this and will post anything I find, but I wanted to throw it out there for others too...
Any help would be greatly appreciated...
L8r,
Vermithrax

Solved
K.. Apparently all I needed to do was reboot after I made the changes above... Came into work this morning and I can now connect to my company network...
Go figure...
L8r,
Vermithrax

[Q] Hardware Watchdog Crash

I have a Sony Xperia TX. It randomly crashes and it reads - Phone crashed please wait for the crash reports to be saved.
it also say Hardware Watchdog crash stored on internel sdcard.
I am posting my crash reports from the CrashDump folder.
rdlog_init() created temp log file: /hhVMYg
[E] Could not open VT /dev/tty0: "No such file or directory"
Framebuffer initialized: 720x1280, 16bpp, 1.8MB
Setting backlight [/sys/class/leds/lcd-backlight_1/brightness] intensity to 255 (masked to 255)
Setting backlight [/sys/class/leds/lcd-backlight_2/brightness] intensity to 255 (masked to 255)
[E] Failed to open /sys/class/timed_output/vibrator/enable: No such file or directory
RamdumpV3 app. Version: 1.0.A.0.57
Loading configuration from conf.xml
adding 1 mount point(s)
Mount of /dev/block/by-name/SDCard on /YMogkv with file system ext4 returned: SUCCESS
DUMP /YMogkv /dev/block/by-name/SDCard 179:15 ext4 READY
Cleaning up permission problems for CrashDump
Unable to open RTC device
No rtc time
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000 directory
[W] Failed to create /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000, retrying... No such device
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0 directory
ramdump log created at "/YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdump.log"
Updating /YMogkv/CrashDump/crashinfo
opened memory device node /dev/mem (3) in O_RDWR | O_SYNC mode
Verify config
Reading cmdline file /proc/cmdline:
* Found: startup=6a58c
* Found: warmboot=6a594
* Found: androidboot.serialno= CB5A1JYRHT
RestartReason=0xabadbabe, restartReasonType=1
No buildinfo found, fallback to crash-notes.
Storing kernel log to: /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdump_system.log
Searching linux area 12 (0x80200000, 0x8d00000) for magic 0xCAFEBABE.
[W] Default build id checksum! Early kernel crash?
Found build info in crash notes: 7.0.A.3.193\hayabusa\userdebug
Found crash notes for crashing CPU! Crashing process:
[W] Skipping ram console search, crash type is 1
RESTART_REASON: 0xABADBABE (Hardware watchdog)
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdumpinfo
HWWD but can't read /proc/rdtags/addr_scm_regsave from rdtags: errno=2 <No such file or directory>
HWWD using hardcoded physical addr 0x2a03f658
CPU registers dump addr (phy) 0x00000000={0xea000006, 0xea000060, 0xea000063, ...}
HWWD found but no TZBSP_DUMP_CTX_MAGIC (found 0xea000006 expected 0x44434151)
RDTAG_DIR not set for this platform! Skipping rdtags dump!
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/productinfo
Creating dump file: /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/tlcore
Platform: blue
Dump areas:
( 0) address=0x0006206c size=0x00000004 flags=0x00006000 name: WDT Reset... success!
( 1) address=0x09000000 size=0x00008000 flags=0x0000a000 name: MDSP Ram A... success!
( 2) address=0x09200000 size=0x00008000 flags=0x0000c000 name: MDSP Ram B... success!
( 3) address=0x09400000 size=0x0000f800 flags=0x0000e000 name: MDSP Ram C... success!
( 4) address=0x12000000 size=0x0002c000 flags=0x00010008 name: SPS RAM... success!
( 5) address=0x12040000 size=0x00004000 flags=0x00012000 name: SPS Buff RAM... success!
( 6) address=0x12800000 size=0x00008000 flags=0x00014000 name: SPS Pipe Mem... success!
( 7) address=0x28400000 size=0x00020000 flags=0x00016008 name: Lpass Memory... success!
( 8) address=0x2a000000 size=0x00010000 flags=0x00018008 name: System IMEM-A... success!
( 9) address=0x2a03f000 size=0x00001000 flags=0x0001c000 name: System IMEM-C... success!
(10) address=0x38000000 size=0x04000000 flags=0x00020008 name: SMI CS0... success!
(11) address=0x80000000 size=0x00200000 flags=0x00080088 name: EBI1_CH0_CS0(SMEM)... success!
(12) address=0x80200000 size=0x08d00000 flags=0x00080028 name: EBI1_CH0_CS0(LINUX)... success!
(13) address=0x88f00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(APPSBL)... success!
(14) address=0x89000000 size=0x04400000 flags=0x00080018 name: EBI1_CH0_CS0(Modem Q6 SW)... success!
(15) address=0x8d400000 size=0x00600000 flags=0x00080018 name: EBI1_CH0_CS0(Modem Q6 FW)... success!
(16) address=0x8da00000 size=0x01800000 flags=0x00080008 name: EBI1_CH0_CS0(LP_Audio_SS)... success!
(17) address=0x8f200000 size=0x00500000 flags=0x00080008 name: EBI1_CH0_CS0(WConnect_SS)... success!
(18) address=0x8f700000 size=0x00080000 flags=0x00080008 name: EBI1_CH0_CS0(TZ Image)... success!
(19) address=0x8f780000 size=0x00080000 flags=0x00080008 name: EBI1_CH0_CS0(Reserved)... success!
(20) address=0x8f800000 size=0x00300000 flags=0x00080008 name: EBI1_CH0_CS0(FS Cache)... success!
(21) address=0x8fb00000 size=0x00300000 flags=0x00080008 name: EBI1_CH0_CS0(RAM EFS)... success!
(22) address=0x8fe00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(SPS Image)... success!
(23) address=0x8ff00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(SBL3)... success!
(24) address=0x90000000 size=0x10000000 flags=0x00080028 name: EBI1_CH1_CS0(LINUX)... success!
(25) address=0xa0000000 size=0x10000000 flags=0x00100028 name: EBI1_CH0_CS1(LINUX)... success!
(26) address=0xb0000000 size=0x10000000 flags=0x00100028 name: EBI1_CH1_CS1(LINUX)... success!
(27) path=/dev/msm_etb_boot flags=0x00024008 name: ETB... Read from /dev/msm_etb_boot: 16384, written to dump: 1530
success!
(28) cmdlineParam=semcandroidboot.rpmcoderamcopy, address=0x00020000 size=0x00000000 flags=0x00002008 name: RPM Code RAM... Found cmdline specified dump area (semcandroidboot.rpmcoderamcopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmcoderamcopy=
cmdLine area [email protected],0x20000
addr = 0x88f00000 size = 147456 orgAddr = 0x20000
success!
(29) cmdlineParam=semcandroidboot.rpmregistercopy, address=0x0002e000 size=0x00000000 flags=0x00004000 name: RPM Registers... Found cmdline specified dump area (semcandroidboot.rpmregistercopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmregistercopy=
cmdLine area [email protected],0x2E000
addr = 0x88f24000 size = 104 orgAddr = 0x2e000
success!
(30) cmdlineParam=semcandroidboot.rpmmsgramcopy, address=0x00108000 size=0x00000000 flags=0x00008000 name: RPM Msg RAM... Found cmdline specified dump area (semcandroidboot.rpmmsgramcopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmmsgramcopy=
cmdLine area [email protected],0x108000
addr = 0x88f24100 size = 24575 orgAddr = 0x108000
success!
Updating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdumpinfo
Ramdump finished in 154s
Ramdump done! type: 1, name: , result: RAMDUMP_RESULT_OK (00)
SD card free space: 8495 MB
Closing graphics and flushing log files
Setting backlight [/sys/class/leds/lcd-backlight_1/brightness] intensity to 0 (masked to 0)
Setting backlight [/sys/class/leds/lcd-backlight_2/brightness] intensity to 0 (masked to 0)
[E] Could not open VT /dev/tty0: "No such file or directory"
Can anyone help me fix this problem?

Go on ,please try to help us help you.
Rooted?
Bootloader unlocked? If so which kernel?
Stock ROM? If so which FW?
Custom ROM? If so which ROM and version.
What did you do to the phone prior to this happening?

gregbradley said:
Go on ,please try to help us help you.
Rooted?
Bootloader unlocked? If so which kernel?
Stock ROM? If so which FW?
Custom ROM? If so which ROM and version.
What did you do to the phone prior to this happening?
Click to expand...
Click to collapse
Not rooted
Bootlocker is not unlocked
The phone is out of the box and i did not change any ROM settings or Rooted it. Nothing has been changed.
I was surfing my gallery when this first happened.
after that it was like 2 to 3 times a day

my wifi disconnect and reconnect itself ?

this is the log :
false
E/ConnectivityService( 1488): not failing over to mobile type 0 because Mobile Data Disabled
D/ConnectivityService( 1488): Dropping ConnectivityChange for WIFI: DISCONNECTED/SCANNING
help plz

Did you root your phone, flash ROM/kernel or change any system settings before this happened?
Sent from my CM7 GT-S5570I

[Q] net.dnsX not set on mobile data connection

Hi there,
I'm using the following rom: [ROM[DEV]]AOSP GingerBread 2.3.7 [COOPER][V3][02-08-13]
Despite being a fast and stable rom, it suffers a bug on mobile data connection, whereas wifi works fine. I'm currently trying to fix that bug. I would have posted that bug report/analysis in the corresponding rom's thread, but I'm not allowed to due to the 10-posts-limit in the developmental sections.
The following sections show how the dns properties differ when using wifi or mobile data:
If you think "tl;dr", scroll down for my questions
Connected to wifi:
Code:
# getprop | grep dns
[net.change]: [net.dnschange]
[net.dns1]: [192.168.1.25]
[net.dns2]: []
[net.dnschange]: [5]
[net.pdp0.dns1]: []
[net.pdp0.dns2]: []
[dhcp.wlan0.dns1]: [192.168.1.25]
[dhcp.wlan0.dns2]: []
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
As you can see:
wlan0 got its nameserver via dhcp
pdp0 (mobile data) has no nameserver set (because it's disconnected)
net1.dns got its value fr om dhcp.wlan0.dns1
-> internet access (name resolution) works
Now with wifi disconnected and mobile data connected:
Code:
# getprop | grep dns
[net.change]: [net.dnschange]
[net.dns1]: []
[net.dns2]: []
[net.dnschange]: [7]
[net.pdp0.dns1]: [139.7.30.126]
[net.pdp0.dns2]: [139.7.30.125]
[dhcp.wlan0.dns1]: []
[dhcp.wlan0.dns2]: []
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
wlan0 has no nameserver set (OK)
pdp0 (mobile data) has the right nameserver (Vodafone DE)
net1.dns has NOT copied its value from net.pdp0.dns1
-> internet access (name resolution) does NOT work
XDA member mahithm supplied a fix for that problem: http://forum.xda-developers.com/showpost.php?p=48640501&postcount=133
He simply put a script to /system/etc/init.d/555dns that does the following:
Code:
#!/system/bin/sh
#Written By mahithm
setprop net.dns1 8.8.8.8
setprop net.dns2 8.8.4.4
initscripts are run once at boot, so this makes mobile data work as long as you were not connected to a wifi since the last boot. Connecting to wifi sets the dns server of the wifi and overwrites net.dns1. Disconnecting clears net.dns1, thus not allowing name resolution as without mahithm's fix.
I tried to modify /system/etc/dhcpcd/dhcpcd-hooks/20-dns.conf like this:
Code:
unset_dns_props()
{
for i in 1 2 3 4; do
setprop dhcp.${interface}.dns${i} ""
done
setprop net.dns1 8.8.8.8
setprop net.dns2 8.8.4.4
setprop net.dns3 $(getprop net.pdp0.dns1)
setprop net.dns4 $(getprop net.pdp0.dns2)
}
unset_dns_props() is calles when wifi is disconnected and dhcpcd (which is not needed for mobile data) quits. My modification should set the google dns to net.dns1/2 and try to extract the mobile data dns (if already set, only for testing purposes) to net.dns3/4. However, none of that works - it seems as if net.dnsX gets overwritten by another process after dhcpcd exits.
So now my questions are:
What service/program sets net.dnsX? Perhaps ConnectivityManager? How can I manipulate that behaviour?
May it be possible that what-service-soever tries to copy a wrong dns setting, e.g. from net.ppp0.dns1 which does not exists and thus is empty? Where are the communication interfaces set (build.prop etc.)?
Does dhcpcd (which calls the hook-script) not have permission to change net.dnsX but dhcp.*.dnsX?
Is there a possibility to create a hook that always gets called when net.dnsX changes?
Any other idea to fix it? How do other roms do this?

Hey man,
Thanks for bringing this bug to my notice. I don't have a wifi, so i couldn't test this out. I read that entries in default.prop, present in the root directory, is permanent. So try adding the following in default.prop
net.dns1 8.8.8.8
net.dns2 8.8.4.4
Before adding this, take a backup and then add the following to test it out. Do post your result.