Database Develop

Trinity bootloader

i'm using the hermes/artemis reference to see what works and not
first: almost every other commands give the "Command Error"
the wdata exists and gives: Command is Locked!
The first thing will be to get into the radio bootloader - seems that the password is fixed. As far as the bootloader I hope that it can be downgraded.
---
info 2:
HTCSHTC__102Ã;¿HTCE
info 3:
HTCST
info 4:
IsAllBytesTheSame-: dwLength=8, bResult=0
HTCSHTC__102Ã;¿HTCE
info 6:
HTCST ÚÈÒHTCE
info 7:
HTC Integrated Re-Flash Utility, Common Base Version : 1.51b
Device Name: TRIN100, Bootloader Version : 1.06.0000
Built at: Oct 19 2006 20:31:29
Copyright (c) 1998-2006 High Tech Computer Corporation
CPU ID=0x41129200
Main CPLD version=0xA
Main Board version=0x5
info 8:
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x18700
Partition[3], type=0x4, start=0x1B700, total=0x1F100
CE Total Length(with sector info) = 0x37BB800
CE CheckSum Length(without sector info) = 0x36E0000
-----
task 32 : Level FF
-----
checkimage
IPL CRC checksum = 0x96BE3C47
SPL CRC checksum = 0xBA45D40C
CE CRC checksum = 0xE86D6EC6
ExtROM CRC checksum = 0x3FBE8D13
Radio Image CRC checksum = 0xAB599ED8
-----
progress - shows bar

SD Upgrade
I tried the SD upgrade method.
I placed an nbh file on it called TRINIMG.nbh but after cheking gaves me "NOT ALLOW" 00028002
Any ideea ?

As your seclevel is FF, the CID on the NBH should be the same on your device. info 2 shows your CID = HTC__102 (HTC Germany), so you need to put an HTC german rom in the TRINIMG.nbh file or CID unlock your device.
Nice work on the bootloader

I've just decoded Trinity radio, it is very very similar to Hermes radio (Same Qualcomm JNAND Identification block), so radio bootloader commands should be the same in Trinity as on Hermes (and radio patch for SIM/CID unlock too!).
Normal bootloader commands should be quite similar too, but not necessarily the same, this is what I found on Trinity's SPL:
getdevinfo
ResetDevice
progress
ruustart
rbmc
password
info
task
emapi
btrouter
wdata
lnbs
erase
checkimage
checksum
wdata
wdatah
Click to expand...
Click to collapse
There's also the static password: BsaD5SeoA
Can you add all this info to the wiki?

pof said:
I've just decoded Trinity radio, it is very very similar to Hermes radio (Same Qualcomm JNAND Identification block), so radio bootloader commands should be the same in Trinity as on Hermes (and radio patch for SIM/CID unlock too!).
Normal bootloader commands should be quite similar too, but not necessarily the same, this is what I found on Trinity's SPL:
There's also the static password: BsaD5SeoA
Can you add all this info to the wiki?
Click to expand...
Click to collapse
excellent. i'm in office only with my trusted Universal (i'll fill up all the info tonight).

from artemis Wiki:
Artemis Bootloader Password
Seems that artemis bootloader password is static: BsaD5SeoA
If you enter this password in mtty terminal, you may not be able to boot device into Windows, only in bootloader. Be carefull.
It's meaning that Artemis has the same bootloader (or similar) with trinity.
The question: why it cannot get out from the bootloader ??

decebal said:
It's meaning that Artemis has the same bootloader (or similar) with trinity.
Click to expand...
Click to collapse
No, if you compare SPL they are very different one from the other.
Trinity's SPL is more similar to Hermes SPL, but Artemis SPL is different.
decebal said:
The question: why it cannot get out from the bootloader ??
Click to expand...
Click to collapse
probably you just need to 'set 14 0' or hard reset to go back to OS, I don't know... the wiki edit was done by fdp24, he can probably explain

pof said:
I've just decoded Trinity radio, it is very very similar to Hermes radio (Same Qualcomm JNAND Identification block), so radio bootloader commands should be the same in Trinity as on Hermes (and radio patch for SIM/CID unlock too!).
Normal bootloader commands should be quite similar too, but not necessarily the same, this is what I found on Trinity's SPL:
There's also the static password: BsaD5SeoA
Can you add all this info to the wiki?
Click to expand...
Click to collapse
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSTRIN100HTCE
--
Reset Device - works
--
Progress - works
--
ruustart - blocked - hard reset needed
--
rbmc - not working
--
password works with the password BsaD5SeoA
--
info - works as in wiki
--
task - works as in wiki
--
emapi and btrouter - blocks the device
--
wdata - works with the password provided
--
lnbs - not working
--
erase - working
HTCST ÚÈÒHTCE
--
checkimage - working as in wiki
--
checksum - seems working
--
wdatah - not working

seems that the 1.06 is somehow limited as bootloader. how can we get the 1.04 or other upgrade solution ??
thanks

Nice work on the wiki decebal
Answers to your comments:
rbmc and lnbs - probably only work on SuperCID devices.
emapi and btrouter - I think it switches to wlan or bluetooth and disables USB connection.
wdata and wdatah - In hermes wdatah is for flash NBH and wdata for flash NBF in preproduction devices. Have you captured a full ROM upgrade using USB monitor?? which one it uses the RUU? Probably it has a dynamic password which enables wdatah for NBH files. Does 'info 3' works as in Hermes (you need to watch usb monitor output, can't see in mtty generally).
decebal said:
seems that the 1.06 is somehow limited as bootloader. how can we get the 1.04 or other upgrade solution ??
Click to expand...
Click to collapse
Generally by flashing a ROM matching your CID with bootloader 1.04.

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.

help me rsd lite error msg

help me error message rsd lite flashing error
iam used Droid a855 and bootloader 2c7c FRG32D
Code:
08:13:04, March 09, 2011
Line: 527
ERROR: AP Die ID: 1a90011715680304000000002400
08:13:04, March 09, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
08:13:04, March 09, 2011
Line: 541
ERROR: AP Public ID: ffffffffffffffffffffffffffffffffffffffff
08:13:04, March 09, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
08:20:33, March 09, 2011
Line: 962
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x152000 Command: ADDR
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp
Device ID: 0
08:20:33, March 09, 2011
Line: 1190
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
08:20:33, March 09, 2011
Line: 597
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x152000 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
and now restart the phone normal but cannot flashing the prl

I am Having Same issue. Phone Keeps failing. tried on Multiple computers and multiple os's (Windows 7 32/64, ubuntu) nothing seems to work. Only thing I have done to phone is Adeo (REDUX) and Superuser.
Now I want to go to 1.5.7 and I can not. I am attempting to flash back to vanilla 1.2.6 and am getting this error. ANY help with this would be greatly appreciated!
Been at this for a week now
BTW, Mine in an Atrix (AT&T) but same issue

[Q] Lost IMEI after upgrade

Hi all!
I were in the process to upgrade to 10b on my phone, but during the upgrade the phone stopped responding on upgrading S/W. Please wait. And after some time on that screen, I removed the battery and cable, and tried the different solutions provided by the LG B2C Support Tool.
After that I tried to flash the phone with smartflash and the latest software. And that worked perfectly, but now the phone has no IMEI. Have tried to install the backup I had via CWM but still no IMEI.
I was looking forward to use the 2x this easter, but if noone has a good solution in getting the IMEI back, the phone needs to go on a easter holiday to the service centre.

You did the same thing with me. When using smartflash, DO NOT check option "Erase CAL data" but I did. My SU660 now has serial number = 0000000. P990 will lost IMEI.
Sent from my LG-SU660 using XDA Premium App

I had the same problem, you need to flash the baseband firmware as it is gone.
I think that it was during updating the baseband as part of the V10b mine stopped flashing.
Look here: http://forum.xda-developers.com/showthread.php?t=1008070
It worked with mine o2x.

I managed to solve the situation.
I applied the 10b firmware using nvflash. And then flashed the 10a fw with smartflash, checked that the IMEI were back in business. And then did a new update using smartflash to 10b and now everything is back as normal

restore IMEI (From Modaco)
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset

Hi mohicanrat,
I tried to set 'Port Setting' -> 'CP USB', but in the device manager (i'm using win7), this device then shows up as 'Other Devices' -> 'Unknown device'.
What should I do now? Where can I get the device driver for this?

hello,
please where i go to "Start hyperterminal, in COM settings"

HyperTerminal was binned after Windows XP, if you have Vista onwards you'll need to download an equivalent.

mohicanrat said:
1. Connect phone by usb
2. Enter 1809#*990# in dialer
3. Select port settings -> select cp usb
4. Start hyperterminal, in com settings select same port like in devide manager -> lge mobile usb serial port, 115200
5. Type at if response is not ok, change port number
6. Type at%imei, it should display your current imei
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... Is your orginal imei number
8. Reset
Click to expand...
Click to collapse
thank you very much. I did as you said and finally got my imei back
thank you a million.

mohicanrat said:
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset
Click to expand...
Click to collapse
It gives error on running at%imei, might it be because phone driver not installed on windows?
at%imei
ERROR
I instaled driver from LG site LGUnitedMobileDriver_S498MA22_WHQL_ML_Ver_2.2.exe
when i type ATI4 for instance it shows same info as from log.
Here's log from modem i removed my IMEI though.
PHP:
11-26-2011 01:29:11.420 - File: C:\Windows\system32\tapisrv.dll, Version 6.1.7600
11-26-2011 01:29:11.420 - File: C:\Windows\system32\unimdm.tsp, Version 6.1.7600
11-26-2011 01:29:11.421 - File: C:\Windows\system32\unimdmat.dll, Version 6.1.7600
11-26-2011 01:29:11.421 - File: C:\Windows\system32\uniplat.dll, Version 6.1.7600
11-26-2011 01:29:11.430 - File: C:\Windows\system32\drivers\modem.sys, Version 6.1.7600
11-26-2011 01:29:11.430 - File: C:\Windows\system32\modemui.dll, Version 6.1.7600
11-26-2011 01:29:11.438 - File: C:\Windows\system32\mdminst.dll, Version 6.1.7600
11-26-2011 01:29:11.439 - Modem type: LGE Mobile USB Modem
11-26-2011 01:29:11.439 - Modem inf path: oem29.inf
11-26-2011 01:29:11.439 - Modem inf section: LGSI.Install
11-26-2011 01:29:11.439 - Matching hardware ID: usb\vid_1004&pid_6000_modeminterface
11-26-2011 01:29:11.470 - 460800,8,N,1, ctsfl=0, rtsctl=1
11-26-2011 01:29:11.488 - Initializing modem.
11-26-2011 01:29:11.488 - CD is high while initializing modem.
11-26-2011 01:29:11.498 - Send: AT<cr>
11-26-2011 01:29:11.504 - Recv: <cr><lf>OK<cr><lf>
11-26-2011 01:29:11.504 - Interpreted response: OK
11-26-2011 01:29:11.514 - Send: ATE0V1&D2&C1S0=0<cr>
11-26-2011 01:29:11.526 - Recv: <cr><lf>ERROR<cr><lf>
11-26-2011 01:29:11.526 - Interpreted response: Error
11-26-2011 01:29:11.527 - Session Statistics:
11-26-2011 01:29:11.527 - Reads : 15 bytes
11-26-2011 01:29:11.527 - Writes: 20 bytes
ATQ0V1E0 - OK
AT+GMM - 0
AT+FCLASS=? - +FCLASS: (0-1)
AT#CLS=? - COMMAND NOT SUPPORTED
AT+GCI? - COMMAND NOT SUPPORTED
AT+GCI=? - COMMAND NOT SUPPORTED
ATI1 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI2 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI3 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI4 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI5 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI6 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI7 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES

help!!
i can connect but cant type anything in the terminal.. can anyone help .. i ve never done this before.. using win7 x64

Same Problem here....
I've the same problem
IMEI is gone
Baseband is "Unknown"
Battery shows 999%
And like the poster above me, I cant type anything in the Hyperterminal
PLS, who got his IMEI (and with this his loved Optimus) back, help us!!
Thx in advance,
sleep

mohicanrat said:
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset
Click to expand...
Click to collapse
Today i was flashing LG Optimus Black P970 with SmartFlash and accidentaly i checked "Erase entire CP". In a result my IMEI has changed...
With this tutorial I managed to recover my IMEI successfully!
It took me 2 minutes and worked at first time.

i'm trying this method but not working
when type At...i get ok
but when i type imei i get error

What error? Paste screenshot or log.
What firmware version do you have in your LG?
You must type exactly this: at%imei - (% symbol is very important) it will display your current IMEI, then
at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x (, (comma) is very important too)

Hi,
I had one time that when i change ril. After backup my old ril all work fine.

I tried this method but i get "IMPL ERROR".
Stock ROM V10c
Tried to downgrade baseband from
1035.21_20110405
to
1035.21_20110315
but still same error...
Any idea?
Can you please tell me exact software version on what this method worked?

any solution for su660 i have the same problem

I expect the same thing would work.

mohicanrat said:
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset
Click to expand...
Click to collapse
Anyone know how to perform this with an Optimus L3 device? Apparently i can't have acces to "Port Settings"

[Q] HD7 Tethering "Error 692"

I'm beside myself trying to get my HD7 to tether.
First, I've read every post remotely related to this topic on this forum and others. Thanks to all the people in this community who have shared information on how to crack these phones, provide ROMs, troubleshooting and expertise.
I would have never gotten this far without all of your help.
I hope someone can solve this issue, because it sounds like many others have, or will have the dreaded "Error 692" problem when attempting to tether.
Some background: I'm attempting to tether a Windows 7 32-bit laptop to a T-Mobile HD7 in the US. In order to jailbreak the phone, I got an sim unlock code, then I installed one of the 7004 build ROMs from the HD7 developer's forum on this board, then unlocked with Chevron. I'm still under OS7004, with a boot loader version of 1.54.2250 and firmware 2250.09.15402.531.
I then followed the following procedure, posted on this forum and others:
//
1. Download XAP file
2. Download HTC Sync for Android from HTC for USB Modem driver
3. Deploy XAP file to your phone
4. Turn of your Data conection in your phone.
5. Run DFRouter and click on “HTC Modem”
6. Open your device manager, it will show 2 unknown device, choise device have ID is : USBVID_0BB4&PID_0EFF&REV_0000&MI_01, update your driver with HtcUsbMdm and you got HTC USB Modem.
7. Make a dial up call from your computer and set it work like other WP7 tethering from samsung or LG.
8. Click “Zune Mode” to come back with Zune Sync.
For dial up make a call *99# with mi_01 id modem. Mi_00 is diag port, maybe have some qualcomm unlock here. Don’t forget add +CGDCONT=1,”IP”,”your apn” in your advance property of modem.
//
The only variation is that I could not, no matter how hard I tried, manually install or change the two HTC modem drivers. Despite downloading them from several sources, and even trying both 32bit and 64bit drivers, I could not get windows to accept them. Even if I "uninstalled and deleted the drivers" then attempted to reinstalled the drivers for the two "Unknown Devices" I could not. Windows would not recognize the HTC drivers as being appropriate for the device. The only way I could get the HTC modem to install was using the HTC Sync software that automatically installs those drivers. By doing so, it seemed that in the Device Manager the HTC mode is installed... but there is only one device listed, the "HTC USB Modem."
In troubleshooting this, here are the things I have tried:
- Restarting the phone and machine numerous times.
- Performing all functions with anti-virus and firewall disabled.
- Yes, I have made sure the WiFi and data connection are off before connecting the USB and attempting dial up.
- I have tried the trick of selecting "USB" Sync then "HTC Modem" right before attempting dial up.
- I have tried every T-Mobile APN known to man in the initialization string.
- I have turned off "IPV6" and compression on modem settings.
- I have tried all COM ports 1-8.
- I have entered in the same APNs that are in the modem init string to the HD7's settings under cellular > Network Selection.
There are probably other things I have tried as well... if it was listed in any post on this board, I've probably tried it.
When I attempt to query the HTC Modem, the response I get is always something to the effect of "can't detect modem... make sure it is turned on." Here is a cut and paste of the log... which is always the same no matter what I seem to try.
05-14-2011 08:35:33.152 - File: C:\Windows\system32\tapisrv.dll, Version 6.1.7600
05-14-2011 08:35:33.153 - File: C:\Windows\system32\unimdm.tsp, Version 6.1.7600
05-14-2011 08:35:33.154 - File: C:\Windows\system32\unimdmat.dll, Version 6.1.7600
05-14-2011 08:35:33.154 - File: C:\Windows\system32\uniplat.dll, Version 6.1.7600
05-14-2011 08:35:33.156 - File: C:\Windows\system32\drivers\modem.sys, Version 6.1.7600
05-14-2011 08:35:33.156 - File: C:\Windows\system32\modemui.dll, Version 6.1.7600
05-14-2011 08:35:33.157 - File: C:\Windows\system32\mdminst.dll, Version 6.1.7600
05-14-2011 08:35:33.157 - Modem type: HTC USB Modem
05-14-2011 08:35:33.158 - Modem inf path: oem19.inf
05-14-2011 08:35:33.158 - Modem inf section: Modem0
05-14-2011 08:35:33.159 - Matching hardware ID: usb\vid_0bb4&pid_0eff
05-14-2011 08:35:33.163 - Opening Modem
05-14-2011 08:35:33.163 - 115200,8,N,1, ctsfl=0, rtsctl=1
05-14-2011 08:35:33.168 - Initializing modem.
05-14-2011 08:35:33.173 - DSR is low while initializing the modem. Verify modem is turned on.
05-14-2011 08:35:33.173 - CTS is low while initializing modem.
05-14-2011 08:35:33.185 - Send: AT<cr>
05-14-2011 08:35:35.185 - Timed out waiting for response from modem
05-14-2011 08:35:35.185 - The modem failed to respond to the initialization command, Retrying one more time
05-14-2011 08:35:35.185 - 115200,8,N,1, ctsfl=0, rtsctl=1
05-14-2011 08:35:35.186 - DSR is low while initializing the modem. Verify modem is turned on.
05-14-2011 08:35:35.186 - CTS is low while initializing modem.
05-14-2011 08:35:35.197 - Send: AT<cr>
05-14-2011 08:35:37.197 - Timed out waiting for response from modem
05-14-2011 08:35:37.197 - The modem failed to respond to the initialization command, Retrying one more time
05-14-2011 08:35:37.199 - 115200,8,N,1, ctsfl=0, rtsctl=1
05-14-2011 08:35:37.201 - DSR is low while initializing the modem. Verify modem is turned on.
05-14-2011 08:35:37.202 - CTS is low while initializing modem.
05-14-2011 08:35:37.212 - Send: AT<cr>
05-14-2011 08:35:39.217 - Timed out waiting for response from modem
05-14-2011 08:35:39.220 - Session Statistics:
05-14-2011 08:35:39.220 - Reads : 0 bytes
05-14-2011 08:35:39.220 - Writes: 9 bytes
I'm sure I must be missing something simple or stupid. I sounds like windows doesn't have the drivers it needs or can't connect to the device.
Any help would be hugely appreciated... I desperately need to get this working so that I can have mobile internet access for my work.
Thanks!

Okay what worked for me was, +CGDCONT=1,”IP”,”your apn” had weird quotation marks, try re-typing the whole lines. If you have the same problem I did you'll notice the quotation marks you type are different than the quotation marks in the box, i.e. " and ”. See how the second is sorta angled?

juanfpina said:
Okay what worked for me was, +CGDCONT=1,”IP”,”your apn” had weird quotation marks, try re-typing the whole lines. If you have the same problem I did you'll notice the quotation marks you type are different than the quotation marks in the box, i.e. " and ”. See how the second is sorta angled?
Click to expand...
Click to collapse
Had same issue and re-typed quote. works a dream. thanks.

[Q] Flash Tool + Linux Mint Help

Hey All,
So today I've tried rooting the .253 by downgrading my firmware back to .434 but for some reason it just doesn't work I've inserted the log from the terminal and the log from Flash Tool (Latest Release), I'm running Linux Mint 14 xfce (Running Flash Tool as root of course) I took a risk by unplugging the device after 25 minutes and luckily it still works no brick so I'm happy but I'm a little stuck on how to actually get it to work because I had the same problem with it not downgrading on windows which I was stuck on because thats how I flashed the .253 firmware :S
Terminal Log
Code:
JAVA_HOME not set. Using default value : ./x10flasher_lib/linjre32
Error parsing gtk-icon-sizes string: ''
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (read) : No device
flashsystem.X10FlashException: S1 Header checksum Error
at flashsystem.S1Packet.<init>(S1Packet.java:55)
at flashsystem.io.USBFlashLinux.linuxReadS1Reply(USBFlashLinux.java:53)
at flashsystem.io.USBFlash.readS1Reply(USBFlash.java:50)
at flashsystem.io.USBFlash.writeS1(USBFlash.java:33)
at flashsystem.Command.writeCommand(Command.java:123)
at flashsystem.Command.send(Command.java:140)
at flashsystem.X10flash.uploadImage(X10flash.java:215)
at flashsystem.X10flash.sendLoader(X10flash.java:272)
at flashsystem.X10flash.flashDevice(X10flash.java:355)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
flashsystem.X10FlashException: Cannot read from device
at flashsystem.Command.writeCommand(Command.java:129)
at flashsystem.Command.send(Command.java:140)
at flashsystem.X10flash.uploadImage(X10flash.java:215)
at flashsystem.X10flash.sendLoader(X10flash.java:272)
at flashsystem.X10flash.flashDevice(X10flash.java:355)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
flashsystem.X10FlashException: Cannot read from device
at flashsystem.X10flash.uploadImage(X10flash.java:222)
at flashsystem.X10flash.sendLoader(X10flash.java:272)
at flashsystem.X10flash.flashDevice(X10flash.java:355)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (read) : No device
flashsystem.X10FlashException: S1 Header checksum Error
at flashsystem.S1Packet.<init>(S1Packet.java:55)
at flashsystem.io.USBFlashLinux.linuxReadS1Reply(USBFlashLinux.java:53)
at flashsystem.io.USBFlash.readS1Reply(USBFlash.java:50)
at flashsystem.io.USBFlash.writeS1(USBFlash.java:33)
at flashsystem.Command.writeCommand(Command.java:123)
at flashsystem.Command.send(Command.java:140)
at flashsystem.X10flash.endSession(X10flash.java:398)
at flashsystem.X10flash.closeDevice(X10flash.java:408)
at flashsystem.X10flash.flashDevice(X10flash.java:373)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
release_interface : No device
release_interface : No device
Flash Tool Log
Code:
23/054/2013 08:54:04 - INFO - <- This level is successfully initialized
23/054/2013 08:54:04 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 22:29:21
23/054/2013 08:54:04 - INFO - You can drag and drop ftf files here to start flashing them
23/054/2013 08:54:08 - INFO - Device disconnected
23/054/2013 08:54:13 - INFO - List of connected devices (Device Id) :
23/054/2013 08:54:13 - INFO - List of ADB devices :
23/054/2013 08:54:13 - INFO - - none
23/054/2013 08:54:13 - INFO - List of fastboot devices :
23/054/2013 08:54:13 - INFO - - none
23/003/2013 09:03:28 - INFO - Flash canceled
23/004/2013 09:04:00 - INFO - Selected Xperia Z_10.1.A.1.434_Generic_WORLD.ftf
23/004/2013 09:04:00 - INFO - Preparing files for flashing
23/005/2013 09:05:32 - INFO - Please connect your device into flashmode.
23/005/2013 09:05:42 - INFO - Device connected in flash mode
23/005/2013 09:05:42 - INFO - Opening device for R/W
23/005/2013 09:05:42 - INFO - Device ready for R/W.
23/005/2013 09:05:42 - INFO - Reading device information
23/005/2013 09:05:43 - INFO - Phone ready for flashmode operations.
23/005/2013 09:05:43 - INFO - Current device : C6603 - CB5A1PQBU0 - 1270-4986_R7A - 1269-5309_10.1.1.A.1.253 - GLOBAL-LTE_10.1.1.A.1.253
23/005/2013 09:05:43 - INFO - Start Flashing
23/005/2013 09:05:43 - INFO - Processing loader
23/005/2013 09:05:43 - INFO - Checking header
23/005/2013 09:05:43 - INFO - Flashing data
23/023/2013 09:23:51 - INFO - Ending flash session <--- This is were I disconnected the device after 25 mins of waiting
23/023/2013 09:23:51 - ERROR - Cannot read from device
23/023/2013 09:23:51 - ERROR - Error flashing. Aborted
23/023/2013 09:23:52 - INFO - Device disconnected
23/025/2013 09:25:24 - INFO - Selected Xperia Z_10.1.A.1.434_Generic_WORLD.ftf
23/025/2013 09:25:24 - INFO - Preparing files for flashing
23/026/2013 09:26:48 - INFO - Please connect your device into flashmode.
23/027/2013 09:27:32 - INFO - Device connected in flash mode <--- This is me trying it again ...
23/027/2013 09:27:33 - INFO - Opening device for R/W
23/027/2013 09:27:33 - INFO - Device ready for R/W.http://forum.xda-developers.com/showthread.php?p=41741577#
23/027/2013 09:27:33 - INFO - Reading device information
23/027/2013 09:27:33 - INFO - Phone ready for flashmode operations.
23/027/2013 09:27:33 - INFO - Current device : C6603 - CB5A1PQBU0 - 1270-4986_R7A - 1269-5309_10.1.1.A.1.253 - GLOBAL-LTE_10.1.1.A.1.253
23/027/2013 09:27:33 - INFO - Start Flashing
23/027/2013 09:27:33 - INFO - Processing loader
23/027/2013 09:27:33 - INFO - Checking header
23/027/2013 09:27:33 - INFO - Flashing data <--- And this is me just giving up ... (got to get to work so :()