Database Info

Solved-How To change My Sprint TP2 hardware keyboard to Spanish-Solved

Hi all.
I have a Sprint TP2. I want to change my hardware keyboard to spanish layout. I searched al the night and i cant found the way. so any body knows how to change my keyboard to spanish???
Thanks in advance.
SOLVED
After a long search I found the solution: YESSSSSSSSS
The keyboard mapping it's setting by the ".txt" file in the REG KEY:
"HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\Ime\Keyboar dLayouFiles\07FF:"Name of the file.txt")
The ".txt" specifies the hardware keyboard mapping. These file are located in the \windows\ directory in the TP2. We can edit the file as we want. I edited my file like this:
"
//
// N O T E: This file must be saved as Unicode
//
// This file contains the virtual keys mapping table for the
// Raphael device World-Wide English QWERTY layout.
// The mapping table is defined as follows
//
// VK_TPOUND = 0x78
// VK_TSTAR = 0x77
// VK_TAB = 0x09
//
// We do not support escape value yet. So the key/char values should be
// entered explicitly or by encoding start with 0x
//
// Format:
// {VK VK1 VK2 CH1 CH2}
// VK -> value from keyboard driver
// VK1 -> key mapped, interpret by IME
// VK2 -> key to interpret when for press and hold
// CH1 -> symbols produced by Fn + key
// CH2 -> symbols in 123 mode
// CH4 -> Key Index
// Row 1
{1 1 1 ! ! 0xff}
{2 2 2 @ @ 0xff}
{3 3 3 # # 0xff}
{4 4 4 $ $ 0xff}
{5 5 5 % % 0xff}
{6 6 6 ^ ^ 0xff}
{7 7 7 & & 0xff}
{8 8 8 * * 0xff}
{9 9 9 ( ( 0xff}
{0 0 0 ) ) 0xff}
// Row 2
{Q Q Q ¡ ¡ 0x00}
{W W W - - 0x01}
{E E E É É 0x02}
{R R R R R 0x03}
{T T T + + 0x04}
{Y Y Y = = 0x05}
{U U U Ú Ú 0x06}
{I I I Í Í 0x07}
{O O O Ó Ó 0x08}
{P P P _ _ 0x09}
// Row 3
{A A A Á Á 0x0a}
{S S S S S 0x0b}
{D D D : : 0x0c}
{F F F F F 0x0d}
{G G G G G 0x0e}
{H H H \ \ 0x0f}
{J J J / / 0x10}
{K K K ' ' 0x11}
{L L L " " 0x12}
{0x08 0x08 0x08 0xF02E 0xF02E 0xff} // BACKSPACE - 0x08 = VK_BACK, 0x2E = VK_DELETE
// Row 4
{0x10 0x10 0x10 0x14 0x00 0xff} // CAPS - 0x14 = VK_CAPITAL
{Z Z Z ¿ ¿ 0x13}
{X X X X X 0x14}
{C C C Ç Ç 0x15}
{V V V V V 0x16}
{B B B ; ; 0x17}
{N N N Ñ Ñ 0x18}
{M M M ? ? 0x19}
{0x26 0x26 0x26 0xF021 0xF021 0xff} // UP - 0x26 = VK_UP, 0x21 = VK_PRIOR (PAGE UP)
{0x0D 0x0D 0x0D 0x0D 0x0D 0xff} // ENTER - 0x0D = VK_RETURN
// Row 5
{0xEC 0xEC 0x00 0x00 0x00 0xff} // FN - 0xEC = FN
{0xF2 0xF2 0x00 0x00 0x00 0xff} // MSG - 0xF2 = MSG
{0xEB 0x93 0x00 0x00 0x00 0xff} // SMS - 0x93 = SMS
{0xBC , , 0xE9 0x00 0xff} // SYM - 0xE9
{0x20 0x20 0x20 0x12 0x20 0xff} // SPACE - 0x20 = VK_SPACE, 0x12 = XT9 Menu
{0xBE . . 0x00 0x00 0xff}
{0x25 0x25 0x25 0x92 0x00 0xff} // LEFT - 0x25 = VK_LEFT
{0x28 0x28 0x28 0xF022 0xF022 0xff} // DOWN - 0x28 = VK_DOWN, 0x22 = VK_NEXT (PAGE DOWN)
{0x27 0x27 0x27 0xF3 0x00 0xff} // RIGHT - 0x27 = VK_RIGHT
{0xE9 0xE9 0xE9 0x00 0x00 0xff} // SYM - 0xE9"
Like you can see, it's pretty easy. If i want a accent vocal I just press the FN key follow by the vocal key, and voila.
Cheers
Actualization:
After solved my issue, "Sonje" from the "HTC Manía" forum (http://www.htcmania.com/showthread.p...d=1#post678520) suggest me the next link.
http://www.htcmania.com/showthread.php?t=67632
In the link "Superjuani" suggest a program, but I didn't test it, buy I share the link if you want to try it
http://www.htcmania.com/showpost.php...2&postcount=10

Could You helpme???
Hi,
any body???

please, i need your help.
This don´t run over touch pro2, please other solution.
http://wiki.xda-developers.com/index.php?pagename=Raphael_Keyboard
THanks.

[Q] Device encryption not starting

Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
I/MountService( 872): encrypting storage...
I/power ( 872): *** release_dvfs_lock : lockType : 1
D/SSRMv2:CustomFrequencyManagerService( 872): releaseDVFSLockLocked : Getting Lock type frm List : DVFS_MIN_LIMIT frequency : 1188000 uid : 1000 pid : 872 tag : [email protected]
D/lights ( 872): button : 0 +
D/lights ( 872): button : 0 -
D/qdutils ( 321): getuiClearRegion:70 wormRect( l = 0 t = 0 r = 720 b = 50)
D/qdutils ( 321): getuiClearRegion:76 FinalwormRect( l = 0 t = 0 r = 720 b = 50)
E/SMD ( 346): DCD ON
I/SecureStorage(12345): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(12345): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Load image request failed ret = -1, errno = 14
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
E/SecureStorage(12345): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(12345): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(12345): [ERROR]:Error cannot connect to TA/driver!
Click to expand...
Click to collapse
Any ideas?

ccoager said:
Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
Any ideas?
Click to expand...
Click to collapse
My recommendation? DON'T DO ENCRYPTION!! you may get your phone in a lockmode and unable to recover data..

Is there anything else that could be causing this?
I have not chosen device encryption and I am also seeing these messages in logcat..
I/SecureStorage(15360): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(15360): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_stor.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
E/SecureStorage(15360): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(15360): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(15360): [ERROR]:Error cannot connect to TA/driver!
E/SMD ( 213): DCD ON

Same Problem
I am getting the same thing and when I rooted my SCH-r530u I disabled the Knox thing
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon is preparing to run
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon successfully binded a socket
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_stor.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_storage.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Loading app sec_stor and sec_storage failed
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Fail to open session with qualcomm
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Error cannot connect to TA/driver!
02-20 22:57:12.161: V/AlarmManager(411): waitForAlarm result :8
Click to expand...
Click to collapse
What does it mean? I keep getting it every few seconds while the screen is on
* I was going to edit out the sad faces but its too funny cause it fits the situation perfectly*

Wich Oreo Rom with Root and mirrorlink

Hi,
i have a peugeot 208 with mirrorlink and a galaxy S7
Mirrorlink works with stock oreo rom but stops working if i root the rom with SR5-SuperSU-v2.82-SR5-20171001224502.zip (the head unit says that auth certificate of the app is invalid)
Does anyone know a rooted rom compatible with mirrorlink ?
thanks

There aren't any at the moment with mirrorlink working, it's been discussed multiple times.

fresnillo said:
I want to say that this rom is excelent, but when I tried to go to my car and connect to mirrorlink the mobile shows that it needs to download a certification for mirrorlink, but never works.
In logcat I could see this error:
Code:
05-23 00:13:32.827 8000 18376 D TmsDapServer: getInstance enter
05-23 00:13:32.828 8000 18376 D TmsDapServer: getInstance exit
05-23 00:13:32.828 8000 18376 D TmsDapServer: getCACertificate for string enter
05-23 00:13:32.829 3727 17234 D MlDapService: getCACertificate enter
05-23 00:13:32.829 3727 17234 I MLDAP_JNI: GetCACertificate Entered
05-23 00:13:32.829 3727 17234 I MLDAP_NATIVE: Entered MLNGetCACertificate
05-23 00:13:32.829 3727 17234 I MLDAP : ...bMLDAP/TAStartupCodeMC.c: 119: sending command 0xc0, len: 164
05-23 00:13:32.836 3727 17234 E MLDAP : ...bMLDAP/TAStartupCodeMC.c: 155: Application TA reported error code: 0xfffffae2
05-23 00:13:32.836 3727 17234 I MLDAP_NATIVE: MLOtaGetDevicePK failed return value: -1310
05-23 00:13:32.836 3727 17234 I System.out: object is null
05-23 00:13:32.837 8000 18376 E TmsDapServer: FAILED to call service
05-23 00:13:32.838 8000 18376 W System.err: java.lang.NullPointerException: Attempt to get length of null array
05-23 00:13:32.840 8000 18376 W System.err: at java.lang.StringFactory.newStringFromBytes(StringFactory.java:65)
05-23 00:13:32.841 8000 18376 W System.err: at com.samsung.android.mirrorlink.appmanager.TmsDapServer.getCACertificate(Unknown Source:43)
05-23 00:13:32.841 8000 18376 W System.err: at com.samsung.android.mirrorlink.appmanager.GetAllCertThread.run(Unknown Source:479)
05-23 00:13:32.843 3727 17234 D ApplicationPolicy: isStatusBarNotificationAllowedAsUser: packageName = com.samsung.android.app.mirrorlink,userId = 0
05-23 00:13:32.844 3727 17234 D API test: getContainerInfo: value is
05-23 00:13:32.844 3727 17234 D ApplicationPolicy: isStatusBarNotificationAllowedAsUser: packageName = com.samsung.android.app.mirrorlink,userId = 0
05-23 00:13:32.844 3727 17234 D API test: getContainerInfo: value is
05-23 00:13:32.848 8000 18376 D TmsGetAllCertThread: 2nd thread for Dev cert run: POST
05-23 00:13:32.848 8000 18376 D TMProcessMonitor: Incrementing with pid : 8000 - Process monitor value: 2
05-23 00:13:32.850 8000 18376 I System.out: (HTTPLog)-Static: isSBSettingEnabled false
05-23 00:13:32.850 8000 18376 I System.out: (HTTPLog)-Static: isSBSettingEnabled false
Click to expand...
Click to collapse
I'm not 100% sure if this is really already about pure simple root/unlocking, or if you wouldn't need a custom kernel to break it.
But you can see the [Terminal mode server¿]Device attestation protocol Server calling the Mirror link Device attestation protocol service, then JNI is invoked, and whatever native_getCACertificate loads fails.
I guess like only disassembling that binary will tell it for sure, but my educate shot would be that we aren't passing the DAP (which I imagine was created exactly to prevent tampering)
If I check the firmware blobs, they are clearly Trusted Applications, and I wouldn't want to cry wolf, but knox itself could be involved judging by some names floating around the mirrorlink driver dependencies.
So, that's your reason.
The protocol is tentatively hackable then, maybe something like AAGateWay could be a nice workaround, perhaps you can fake to be a ML 1.0 server so you aren't forced to authenticate... But I'm afraid it's not a cakewalk.

Here too. Please, I have a Chevrolet with mylink and mirrorlink does not download the certificate. I installed the mirrorlink Samsung apk and the application stops.
I'm going crazy, there's no solution?
(I have a lightrom with android 9.0, but with any custom ROM that works, I'm satisfied)
Sorry muy bad English ?

rockchip 3229 android box.

i am using rockchip 3229 android box (version 5.0). box not booting and "rockchip" screen is displaying. please help.
tryed to short 7'and 8 pins but no use.
the follwing error is displaying.
21:55:25 261 <Layer 2-1-6> Test Device Start
21:55:25 261 Error:RKU_Write-->WriteFile failed,bRet=0,err=6,size=31,write=0
21:55:25 483 Error:RKU_ClearBuffer-->ReadFile failed,bRet=0,err=6,size=512,read=0
21:55:25 514 <LAYER 2-1-6> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_320B#6&8CA65F9&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
21:55:26 543 Error:RKU_Write-->WriteFile failed,bRet=0,err=6,size=31,write=0
21:55:26 777 Error:RKU_ClearBuffer-->ReadFile failed,bRet=0,err=6,size=512,read=0
21:55:26 793 <LAYER 2-1-6> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_320B#6&8CA65F9&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
21:55:27 813 Error:RKU_Write-->WriteFile failed,bRet=0,err=6,size=31,write=0
21:55:28 044 Error:RKU_ClearBuffer-->ReadFile failed,bRet=0,err=6,size=512,read=0
21:55:28 094 <LAYER 2-1-6> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_320B#6&8CA65F9&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
21:55:29 123 <Layer 2-1-6> Test Device Fail
21:55:29 123 **********Upgrade Done Success<0> Fail<1> Time<3891>ms**********

please help ☹️ my phone is bricked and i just can gp to edl mode

any soliotion to flash by edl mod whith qfile
i need firehose programmer for pcoco x2

same here, please let me know if you find solution please

[12:16:04 AM COM3]:MiFlash 2020.3.14.0
[12:16:04 AM COM3]:vboytest index:3
[12:16:04 AM COM3]:flash in thread name:COM3,id:27
[12:16:04 AM COM3]:sw in images
[12:16:04 AM COM3]:flash in thread name:COM3,id:27
[12:16:04 AM COM3]:vboytest do open :
[12:16:04 AM COM3]: serial port COM3 opend successfully
[12:16:04 AM COM3]:[COM3]:start flash.
[12:16:04 AM COM3]:received hello packet
[12:16:04 AM COM3]rogrammertype: 0
[12:16:04 AM COM3]:vboytest:C:\Users\Waqar\Desktop\phoenixin_in_global_images_V12.1.2.0.RGHINXM_20210115.0000.00_11.0_in\images
[12:16:04 AM COM3]:download programmer file: C:\Users\Waqar\Desktop\phoenixin_in_global_images_V12.1.2.0.RGHINXM_20210115.0000.00_11.0_in\images\prog_ufs_firehose_sdm855_ddr.elf
[12:16:04 AM COM3]:download programmer C:\Users\Waqar\Desktop\phoenixin_in_global_images_V12.1.2.0.RGHINXM_20210115.0000.00_11.0_in\images\prog_ufs_firehose_sdm855_ddr.elf
[12:16:14 AM COM3]:Send done packet
[12:16:14 AM COM3]:file C:\Users\Waqar\Desktop\phoenixin_in_global_images_V12.1.2.0.RGHINXM_20210115.0000.00_11.0_in\images\prog_ufs_firehose_sdm855_ddr.elf transferred successfully
[12:16:16 AM COM3]:send nop command
[12:16:16 AM COM3]:send command:<?xml version="1.0" ?><data><nop verbose="0" value="ping"/></data>
[12:16:18 AM COM3]:write time out try agian 1
[12:16:21 AM COM3]:write time out try agian 2
[12:16:23 AM COM3]:write time out try agian 3
[12:16:26 AM COM3]:write time out try agian 4
[12:16:28 AM COM3]:write time out try agian 5
[12:16:31 AM COM3]:write time out try agian 6
[12:16:33 AM COM3]:write time out try agian 7
[12:16:34 AM COM3]:error:The write timed out.
[12:16:34 AM COM3]:System.Exception: write time out,maybe device was disconnected.
at XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 201
at XiaoMiFlash.code.Utility.Comm.SendCommand(String command, Boolean checkAck) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 217
at XiaoMiFlash.code.bl.SerialPortDevice.ping() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 1873
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 251 at XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 201
at XiaoMiFlash.code.Utility.Comm.SendCommand(String command, Boolean checkAck) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 217
at XiaoMiFlash.code.bl.SerialPortDevice.ping() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 1873
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 251
[12:16:34 AM COM3]:no provision exit:COM3
[12:16:34 AM COM3]:flashSuccess False
[12:16:34 AM COM3]:isFactory False CheckCPUID False
[12:16:34 AM COM3]:before:flashSuccess is False set IsUpdate:True set IsDone True
[12:16:34 AM COM3]:after:flashSuccess is False set IsUpdate:false set IsDone true
POCO X2 FLASH LOG ANY HELP GUYS?