Vista help!!! - Touch Pro2, Tilt 2 Windows Mobile General

I am running Vista 64x and when i try to get hardspl, I get the message hardspl has stopped working, windows can check online for errors. after this nothing happens. Help

HERE IS MY ERROR REPORT
Problem Event Name: APPCRASH
Application Name: rapitool.exe
Application Version: 1.0.8.0
Application Timestamp: 47186633
Fault Module Name: RAPI.dll
Fault Module Version: 6.0.6002.18005
Fault Module Timestamp: 49e03824
Exception Code: c0000135
Exception Offset: 0006f04e
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Information 1: 9d13
Additional Information 2: 1abee00edb3fc1158f9ad6f44f0f6be8
Additional Information 3: 9d13
Additional Information 4: 1abee00edb3fc1158f9ad6f44f0f6be8

Related

bad_pool_header crash with WM5 upgrade

I upgraded my XDA Exec with the new ROM 1.30.162 WWE and Activesync 4.1 but each time I sync, I get a "bad_pool_header" error on a blue background which crashes my machine.
I installed Activesync 4.1 on another laptop to check if this problem was due to drivers etc on my main laptop, and discovered that the device syncs with no problems. There is, therefore, a conflict between the new Activesync 4.1 or the new ROM, and something on my main laptop.
Has anyone come across this problem?
Thanks
The problem is definitely on your PC. Reinstall motherboard drivers, reflash bios, remove antivirus, reinstall windows, etc.
Thanks - pretty drastic...!
Is there a short cut? ie reinstalling drivers one by one? If so, which are likely to be the main culprits? Motherboard? Broadband modem? etc
The error code after reboot of the laptop is:
BC code 19 BCP1:00000020 BCP2: 89A76000 BCP3: 89A766C0 BCP4: 0AD8000
OS Ver 5_1_2600 SP: 2_0 Product 256_1
\WER22c7.dir00\Mini052506-06.dmp
\WER22c7.dir00\sysdata.xml
Does this reveal anything that could explain which driver?
Thanks
10860 said:
Does this reveal anything that could explain which driver?
Click to expand...
Click to collapse
no.
You should create a complete crash dump, and use microsoft debugging tools to find faulting driver. Or better reinstall windows.
I looked at the minidump file and used MS debugger, the readout is below. I am not sure if I did the debugging ok, or how to interpret it. Anything useful in the readout?
Thanks
Loading Dump File [C:\Mini052406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed May 24 20:25:34.038 2006 (GMT+1)
System Uptime: 0 days 0:52:32.633
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, 88187000, 881876c0, ad80000}
Probably caused by : Unknown_Image ( nt!KeBugCheck2+4d4 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 88187000, The pool entry we were looking for within the page.
Arg3: 881876c0, The next pool entry.
Arg4: 0ad80000, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: 88187000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 00000000 to 8053331e
STACK_TEXT:
f78cab74 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x4d4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeBugCheck2+4d4
8053331e ?? ???
FAULTING_SOURCE_CODE:
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KeBugCheck2+4d4
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: ZEROED_STACK
MODULE_NAME: Unknown_Module
Followup: MachineOwner
---------
Nothing useful, minidump does not have enough information
It is very difficult to debug pool corruptions.

Arte 110 Mda .simlock Plz Help

Wizard Service Tool v4.2.2
03/05/06 15:12:58
CPU Manuf. FAILED
IMEI: 355046015665718
=> Bootloaders:
IPL: 3.15.0001 (G4 device)
SPL: 3.15 (G3 device)
SPL date unknown
Registry AKU: .0.4.2
Radio values FAILED
=>Extended_ROM:
Version: Unknown
Name: Extended_ROM
Status: hidden
=> Drives and partitions:
|--Handle--|---Size---|
8e9e5e4a - 3.00M (0x2ff400)
eea932ca - 48.23M (0x303c000)
4eae72b6 - 52.82M (0x34d2000)
2eae7002 - 3.06M (0x310000)
afb24fa2 - 3.06M (0x30fc00)
=> DOC chip unique ID:
00000000e3270205060b04e80b0b0677
Key Index: 60
All Done.
PLEASE I NEED HELP TO UNLOCK MY ARTE 110 MDA .SIMLOCK
i have a unlock programm for u is very simple give your e-mail and a send it
Regards cash-net
thanks in advance dis is my email.address.
[email protected]
cash-net said:
i have a unlock programm for u is very simple give your e-mail and a send it
Regards cash-net
Click to expand...
Click to collapse
please send me sw for unlock thanks
[email protected]
i need to hard reset any one can help pls

So whats next??? Am I missing a step?

I'm kinda of a newbie to the whole flashing the HTC 8125...I've searched and searched and downloaded a couple of ROMS that I would find pretty cool on my phone but...whats next? I got a Cingular 8125 (G4)...I did the hardSPL..and heres what I got...
Wizard Service Tool v4.2.2
18/02/09 02:08:43
CPU: Texas Instruments - OMAP850
MODEL: Wizard
IMEI: ----------
=> Bootloaders:
IPL: 2.21.0001 (G4 device)
SPL: 2.21.Olip (G4 device w/ HardSPL)
Built on Aug 26 2007 at 19:41:34
Copyright (c) 2007 Olipro & HTC - Hard-SPL
=> Firmware:
OS: 5.1.xxx (Build 14928.2.2.0)
ROM: 2.25
Registry AKU: .2.2.0
Radio: 02.25.11
Protocol: 4.1.13.12
=>Extended_ROM:
Version: 2.25.11.102
Name: Extended_ROM
Status: hidden
=> Drives and partitions:
|--Handle--|---Size---|
ee9df2f2 - 5.00M (0x4fec00)
6ea9d13a - 48.23M (0x303c000)
0fb25f92 - 50.95M (0x32f4000)
0fb25f3e - 2.94M (0x2f0000)
2fb25fb6 - 3.06M (0x30fc00)
=> DOC chip unique ID:
00000000306901051024050918060635
Key Index: 84
All Done.
I still got WB5 on my phone..and I tried TNT.1933 touchflo..by hooking up my phone with a usb and activesync..but when I ran the RUU it said file error..do I have to upgrade to WB 6.1 first and if so...where do I get it (ive searched wiki and everything I could search here) or am I missing a step? Any help would be great, thanks!

Experts plz help me for Huawei E173u-2 USB modem.

Dear Sir Pls help me for my problem that i am facing.
I Accidently flashed "idea firmware" customized in my unlocked Stc Huawei E173u-2
Now my modem is locked and my device has changed to e1732. i have tried several firmware but its say modem inserted is not firmware .what is the solution pls help me.i am providing you detail of modem.
firmware info Before flashing firmware.
========================
Device
Device name: E173
Application port: COM14
Serial number: ADABYA9271403809
IMEI: 867749010913089
Hardware Version: CD1E153M
Firmware Version: 11.126.25.00.76
Software Version: 16.001.06.01.500 FaKiro
SIM/USIM
Own number(MSISDN): Unknown
Messages in SIM/USIM: 0 / 50
Contacts in SIM/USIM: 15 / 500
Message center number: +923189244444
PIN code status: Ready
Network status
Network name: Zong CMPak
RSSI: -73dBm
CS network registration: Registered
PS network registration: Registered
PS network attachment: Attached
Network settings
APN: zonginternet
Network selection mode: Automatic
:::::::
Firmware version after flashing
===========================
Device
Device name: E1732
Application port: COM19
Serial number: ADABYA9271403809
IMEI: 867749010913089
Hardware Version: CDXXXXX
Firmware Version: 11.126.16.01.356
Software Version: 23.009.17.00.035
SIM/USIM
IMSI number: 410060008853660
Own number(MSISDN): Unknown
Messages in SIM/USIM: Unknown
Contacts in SIM/USIM: Unknown
Message center number: Unknown
PIN code status: Ready
ICCID: 89410060900088536605
Network status
Network name: Unknown
Network type: No Service
Signal strength: 99, 99
RSSI: Unknown
RSQUAL(BER): 99
RSCP: -145
Ec/Io: -32
Cell ID: Unknown
LAC Code: Unknown
CS network registration: Not registered
PS network registration: Not registered
PS network attachment: Not attached
IPv4 address: Unknown
DNS server: Unknown
LTE band: Unknown
IPv6 address: Unknown
Network settings
APN: Unknown
Network selection mode: Automatic
Also when i flash with downgrader device name is changed to m6290 and then the system cant detect and NO application interface port is assigned to modem. Pls help me solve this problem.
Thanks in advance friend
Any one please help me ?

Fairphone 2, Lineageos 14.1, Error VPN connection since latest LineageOS-Version

Hello,
I'm using the Capsule app to establish a VPN connection into my employers's network, the authentication is done via certificates.
My environment:
Device: Fairphone 2
Recovery: TWRP
OS: LineageOS 14.1 (Android 7.1.2)
LineageOS-Version:
14.1-20180213-NIGHTLY-FP2 --> last version VPN connection works​14.1-20180220-NIGHTLY-FP2 --> first version VPN connection does not works anymore​
Since 14.1-20180220-NIGHTLY-FP2, the VPN client throws this error message:
'failed to retrieve certificate from device store'
below you can find more details copied out of the app's logfile.
The error is reproducable:
I always did TWRP backups before installing a newer lineage version. When restoring a version older than 20.02.2018, then VPN connection works. I can install update after update, till 14.1-20180220-NIGHTLY-FP2 all works fine.
Could someone give some advice how this can be solved?
Thanks in advance.
App's log file:
03-03 23:04:38.132 11264 259 E NEMO.In Service Main:
android.security.KeyChainException: java.security.UnrecoverableKeyException: Failed to obtain information about private key
at android.security.KeyChain.getPrivateKey(KeyChain.java:390)
at com.checkpoint.VPN.Service.b(SourceFile:1156)
at com.checkpoint.VPN.Service.b(SourceFile:67)
at com.checkpoint.VPN.Service$CCCDoer.handleMessage(SourceFile:706)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: java.security.UnrecoverableKeyException: Failed to obtain information about private key
at android.security.keystore.AndroidKeyStoreProvider.loadAndroidKeyStorePublicKeyFromKeystore(AndroidKeyStoreProvider.java:223)
at android.security.keystore.AndroidKeyStoreProvider.loadAndroidKeyStoreKeyPairFromKeystore(AndroidKeyStoreProvider.java:259)
at android.security.keystore.AndroidKeyStoreProvider.loadAndroidKeyStorePrivateKeyFromKeystore(AndroidKeyStoreProvider.java:269)
at android.security.KeyChain.getPrivateKey(KeyChain.java:382)
... 6 more
Caused by: android.security.KeyStoreException: Key not found
at android.security.KeyStore.getKeyStoreException(KeyStore.java:659)
at android.security.keystore.AndroidKeyStoreProvider.loadAndroidKeyStorePublicKeyFromKeystore(AndroidKeyStoreProvider.java:224)
... 9 more
03-03 23:04:38.137 11264 1 D NEMO.SyncController::handleMessage: got msg from service: type = CONNECT
03-03 23:04:38.138 11264 1 D NEMO.service says: CONNECT Failure: error_msg: 'failed to retrieve certificate from device store', error_code: '-1'
03-03 23:04:38.138 11264 1 D NEMO.In Connecting task activity:nCCCError(): failed to retrieve certificate from device store

Categories

Resources