[ROM][Hybrid][8.24.12]Paranoid-Android v1.0 ~TeamNightmare~

[ROM][Hybrid][8.24.12]Paranoid-Android v1.0 ~TeamNightmare~ - HTC Amaze 4G

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an ongoing developer project to make way for a modification that will entirely transform your device, but retain the aesthetics and the experience of your phone. I know you've seen tablet mode roms before, they change two lines in your build.prop file which you could easily edit yourself in seconds and maybe throw a keyboard in there to make it work better. It's a start, but this ain't enough. This thing has potential, but it is wasted the moment you try to stuff a full blown tablet into your poor phone. Yet we all know our high res phones can very well handle more than silly 1-column layouts. So the magic must be in between somewhere, a place that Google must have overlooked and left blank. Yes, this rom strives to drop your device into tablet mode, but it won't stop there, it will reshape and redefine ICS to make it all a useful addition and not just a cute novelty. we're calling it: Hybrid Mode, best of both worlds.
Click to expand...
Click to collapse
-Download (in changelog)
- Wipe /system, /cache, and ,data
- Flash
- Reboot
- Enjoy! $$$
Click to expand...
Click to collapse
- Set the font size to 'Large'
- Go into the navigation bar settings, hold your phone in landscape, change the button quantity to 5, then back to 3. (Buttons shouldn't be crammed together anymore).
- Check "Auto Hide" in Settings, System, Statusbar, to finally get Fullscreen (or Hold power button, and press "Toggle StatusBar")
- Launcher Settings: margins: SMALL (If youre using Apex / Nova), show permanent searchbar: YES, Grid: 5x4, resize all widgets: YES, Wallpaper scrolling: OFF
Click to expand...
Click to collapse
- Same as cm9...
- "About Phone" force closes
Click to expand...
Click to collapse
Code:
v1.0- [URL="http://d-h.st/YsI"]Download[/URL]
[LIST]
[*]First Build!
[/LIST]
- CM9 Team, for their code.
- ParanoidAndroid team for the tweaks and Hybrid mode.
- The TeamNightmare team
- Anyone who I've missed, please pm me.
Click to expand...
Click to collapse

oh boy, another task set for me this weekend! thanks!

Screenshots plz!

S1D3winder016 said:
Screenshots plz!
Click to expand...
Click to collapse
getting there lol

ziggy46 said:
getting there lol
Click to expand...
Click to collapse
K thanks! Is this Sense, AOSP, etc.?
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
Wow, this looks like a tablet!

lol my friend just showed me this rom on his s3. decided to check our(amaze) dev section. boom here it is XD

S1D3winder016 said:
K thanks! Is this Sense, AOSP, etc.?
Click to expand...
Click to collapse
this is an aosp rom, but different. its similar to cm9 but with tablet mode and hybrid mode.

xilande said:
lol my friend just showed me this rom on his s3. decided to check our(amaze) dev section. boom here it is XD
Click to expand...
Click to collapse
how convenient lol

Check it out in a bit, gotta make a backup of my current ROM! I've notice there has been a lot of new stuff recently! I like it! Keep up the great work!

Link is up!

EDIT: nvm, i found my answer

theinitial21 said:
I'm assuming everything works such as, data and gps? because you dont have a known issue section.
Click to expand...
Click to collapse
data should work. (just like speedrom cm9)

Oh boy! The thought of not changing my build prop DPI has me drooling. I may give this a shot over the weekend, thanks!

Ziggy your AWESOME! I'm excited for this one!

ziggy46 said:
data should work. (just like speedrom cm9)
Click to expand...
Click to collapse
data is still broken, it comes off and on even if i conttect directly to my carriers proxy

crazysohc said:
data is still broken, it comes off and on even if i conttect directly to my carriers proxy
Click to expand...
Click to collapse
can you get me a logcat of the radio?
adb logcat -b radio > log.txt
or
adb logcat -b radio
also, this is a KANG from the sensation. therefore data may not work until someone here can build it from source. but we'll try to get it working.

ziggy46 said:
can you get me a logcat of the radio?
adb logcat -b radio > log.txt
or
adb logcat -b radio
also, this is a KANG from the sensation. therefore data may not work until someone here can build it from source. but we'll try to get it working.
Click to expand...
Click to collapse
yea bro just give me a few minutes as i just started restoring my backup, so ill flash it again and get you the log cat as soon as i can
---------- Post added at 05:46 PM ---------- Previous post was at 05:23 PM ----------
D/QC-QMI ( 166): 01 11 00 00 03 01 00 FC 00 20 00 05 00 10 02 00
D/QC-QMI ( 166): 3F 00
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 47 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [47]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
QMI_NAS_GET_SIGNAL_STRENGTH(0x20)]; MSG TX ID: [252]; CTL: [Response]
D/QC-QMI ( 166): 01 2E 00 80 03 01 02 FC 00 20 00 22 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00 01 02 00 9C 05 11 04 00 01 00 64 05
D/QC-QMI ( 166): 12 04 00 01 00 15 05 15 05 00 01 00 FF 00 05
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=81
D/QC-QMI ( 156): qmi_client 9c: Received 81 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 32
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_fetch_signal_strength_observati
ons: qcril_qmi_nas_request_signal_strength entered IF UTIL_RES = SUCCESS 127
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 47 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 47 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 13 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [13]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
<unknow NAS message id>(0x4f)]; MSG TX ID: [253]; CTL: [Request]
D/QC-QMI ( 166): 01 0C 00 00 03 01 00 FD 00 4F 00 00 00
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 26 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [26]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
<unknow NAS message id>(0x4f)]; MSG TX ID: [253]; CTL: [Response]
D/QC-QMI ( 166): 01 19 00 80 03 01 02 FD 00 4F 00 0D 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00 13 03 00 64 15 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=60
D/QC-QMI ( 156): qmi_client 9c: Received 60 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 79
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_fetch_signal_strength_observati
ons: qcril_qmi_nas_fetch_signal_strength_observations completed 0, 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_propagate_known_signal_strength
_ind: .. subfetch sig strength info 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: qcri
l_qmi_nas_dump_sign_strength_report entered
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: ..GW
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: .. s
ignalStrength 7, bitErrorRate 255
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: ..CD
MA
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: .. d
bm -1, ecio -1
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: ..EV
DO
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: .. d
bm -1, ecio -1, signalNoiseRatio -1
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: ..AT
T
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: .. d
bm 100, ecno 21
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: ..LT
E
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: .. s
ignalStrength 99, rsrp -1, rsrq -1, snr: -1
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: qcri
l_qmi_nas_dump_sign_strength_report completed
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_propagate_known_signal_strength
_ind: .. conf res 0
D/RILC ( 156): qmi_ril(0/156): qcril_send_unsol_response: UI <--- RIL_UNSOL_
SIGNAL_STRENGTH (1009) --- RIL [RID 0, Len 56, (null)]
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_propagate_known_signal_strength
_ind: qcril_qmi_nas_propagate_known_signal_strength_ind completed 0
I/RILC ( 156): qmi_ril(0/156): qcril_process_event: Exit qcril_process_event
() : <Unknown event> ?, err_no 0
D/RILC ( 156): qmi_ril(0/156): qcril_event_main: qcril_event_main(): Waiting
...
D/RILJ ( 775): [0245]> SCREEN_STATE: false
D/RILC ( 156): qmi_ril(0/156): onRequest: UI --- RIL_REQUEST_SCREEN_STATE (6
1) ---> RIL [RID 0, token id 245, data len 4]
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_request_screen_state: qcril_qmi
_nas_request_screen_state entered
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: q
cril_qmi_extend_print_power_statistics_9k entered
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 47 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 47 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 13 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [13]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x9)]; MSG TX ID: [55]; CTL: [Request]
D/QC-QMI ( 166): 01 0C 00 00 E4 01 00 37 00 09 00 00 00
D/GSM ( 775): [GsmDCT] onReceive: action=android.intent.action.SCREEN_OFF
D/GSM ( 775): [GsmDCT] stopNetStatPoll
D/GSM ( 775): [GsmDCT] overall state is CONNECTING
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 316 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [316]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x9)]; MSG TX ID: [55]; CTL: [Response]
D/QC-QMI ( 166): 01 3B 01 80 E4 01 02 37 00 09 00 2F 01 02 04 00
D/QC-QMI ( 166): 00 00 00 00 20 04 00 38 00 00 00 1F 04 00 C5 01
D/QC-QMI ( 166): 00 00 1E 04 00 62 04 00 00 1D 04 00 DC 82 0A 00
D/QC-QMI ( 166): 1C 04 00 56 02 00 00 1B 04 00 DB 22 00 00 1A 18
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 00 26 1A 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 19 70 00 1E 01 00 00
D/QC-QMI ( 166): 00 00 00 00 12 27 00 00 00 00 00 00 00 00 00 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 4E 44 01 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 03 23 00 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 5B 7A 01 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 F5 30 00 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 2E 09 00 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 18 08 00 6A
D/QC-QMI ( 166): 23 02 00 00 00 00 00 17 04 00 B7 41 00 00 16 04
D/QC-QMI ( 166): 00 20 00 00 00 15 04 00 62 0F 00 00 14 04 00 40
D/QC-QMI ( 166): 9A 0A 00 13 04 00 5F 02 00 00 12 04 00 8D 07 02
D/QC-QMI ( 166): 00 11 38 00 F3 00 00 00 91 05 00 00 00 00 00 00
D/QC-QMI ( 166): 00 00 00 00 A2 95 01 00 00 00 00 00 54 33 00 00
D/QC-QMI ( 166): 00 00 00 00 07 AF 01 00 00 00 00 00 71 2C 00 00
D/QC-QMI ( 166): 00 00 00 00 AC 08 00 00 00 00 00 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=350
D/QC-QMI ( 156): qmi_client 9c: Received 350 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 9
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]Q6_clients=243,1425,0,0,103842,0,13140,0,110343,0,11377,0,2220,0
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]Q6_try_PC=133005
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]Q6_PC_cnt=607,694848
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]ARM9_clients=0,0,0,6694,0,0
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]ARM9_try_XO=8923
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]ARM9_XO_cnt=598,688860
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: q
cril_qmi_extend_print_power_statistics_9k complete, result=0, error=0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_display_status:
qcril_qmi_ssdsrv_request_set_display_status entered
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 51 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 51 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 17 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [17]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x0)]; MSG TX ID: [56]; CTL: [Request]
D/QC-QMI ( 166): 01 10 00 00 E4 01 00 38 00 00 00 04 00 01 01 00
D/QC-QMI ( 166): 00
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 20 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [20]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x0)]; MSG TX ID: [56]; CTL: [Response]
D/QC-QMI ( 166): 01 13 00 80 E4 01 02 38 00 00 00 07 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=54
D/QC-QMI ( 156): qmi_client 9c: Received 54 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_display_status:
qcril_qmi_ssdsrv_request_set_display_status completed 0, 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_enable_networking_indications:
qcril_qmi_util_enable_networking_indications, param 0
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 91 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 91 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 57 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [57]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
QMI_NAS_SET_EVENT_REPORT(0x2)]; MSG TX ID: [254]; CTL: [Request]
D/QC-QMI ( 166): 01 38 00 00 03 01 00 FE 00 02 00 2C 00 10 04 00
D/QC-QMI ( 166): 00 02 FF 00 11 01 00 00 12 01 00 00 13 02 00 00
D/QC-QMI ( 166): 05 14 02 00 00 04 15 02 00 00 01 16 02 00 00 03
D/QC-QMI ( 166): 17 01 00 00 18 02 00 00 02
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 20 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [20]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
QMI_NAS_SET_EVENT_REPORT(0x2)]; MSG TX ID: [254]; CTL: [Response]
D/QC-QMI ( 166): 01 13 00 80 03 01 02 FE 00 02 00 07 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=54
D/QC-QMI ( 156): qmi_client 9c: Received 54 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 2
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_enable_networking_indications:
qcril_qmi_util_enable_networking_indications requested nas event report 0, 0
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 67 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 67 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 33 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [33]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
QMI_NAS_INDICATION_REGISTER(0x3)]; MSG TX ID: [255]; CTL: [Request]
D/QC-QMI ( 166): 01 20 00 00 03 01 00 FF 00 03 00 14 00 10 01 00
D/QC-QMI ( 166): 00 13 01 00 00 14 01 00 00 17 01 00 01 18 01 00
D/QC-QMI ( 166): 00
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 20 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [20]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
QMI_NAS_INDICATION_REGISTER(0x3)]; MSG TX ID: [255]; CTL: [Response]
D/QC-QMI ( 166): 01 13 00 80 03 01 02 FF 00 03 00 07 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=54
D/QC-QMI ( 156): qmi_client 9c: Received 54 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 3
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_enable_networking_indications:
qcril_qmi_util_enable_networking_indications requested nas indication reports 0
, 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_enable_networking_indications:
qcril_qmi_util_enable_networking_indications completed with 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_request_screen_state: Enable Ga
rbage Filter
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_gf_timer: qcril_
qmi_ssdsrv_request_set_gf_timer entered
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 51 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 51 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 17 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [17]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x5)]; MSG TX ID: [57]; CTL: [Request]
D/QC-QMI ( 166): 01 10 00 00 E4 01 00 39 00 05 00 04 00 01 01 00
D/QC-QMI ( 166): 02
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 20 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [20]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x5)]; MSG TX ID: [57]; CTL: [Response]
D/QC-QMI ( 166): 01 13 00 80 E4 01 02 39 00 05 00 07 00 02 04 00
D/QC-QMI ( 166): 01 00 1A 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=54
D/QC-QMI ( 156): qmi_client 9c: Received 54 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 5
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_gf_timer: qcril_
qmi_ssdsrv_request_set_gf_timer completed 0, 0
I/RILC ( 156): qmi_ril(0/156): fd_ballots: AP 0 votes to enable fast dormanc
y!
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_fast_dormancy_en
able: qcril_qmi_ssdsrv_request_set_fast_dormancy_enable entered
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 51 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 51 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 17 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [17]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x2)]; MSG TX ID: [58]; CTL: [Request]
D/QC-QMI ( 166): 01 10 00 00 E4 01 00 3A 00 02 00 04 00 01 01 00
D/QC-QMI ( 166): 01
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 20 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [20]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x2)]; MSG TX ID: [58]; CTL: [Response]
D/QC-QMI ( 166): 01 13 00 80 E4 01 02 3A 00 02 00 07 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=54
D/QC-QMI ( 156): qmi_client 9c: Received 54 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 2
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_fast_dormancy_en
able: qcril_qmi_ssdsrv_request_set_fast_dormancy_enable completed 0, 0
I/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: >>>>>
> LOCK QCRIL_DATA MUTEX 403308ac
I/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: LOCK
QCRIL_DATA MUTEX 403308ac result=0
D/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: Switc
h ON/OFF dormancy indications on all active interfaces
I/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: <<<<<
< UNLOCK QCRIL_DATA MUTEX 403308ac
I/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: UNLOC
K QCRIL_DATA MUTEX 403308ac result=0
I/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: qcril
_data_toggle_dormancy_indications: EXIT with SUCCESS
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_request_screen_state: .. data d
ormancy req 1, 0
I/RILC ( 156): qmi_ril(0/156): qcril_reqlist_find: [RID 0] Not found ReqList
entry : token id 245
D/RILC ( 156): qmi_ril(0/156): qcril_send_request_response: UI <--- RIL_REQU
EST_SCREEN_STATE (61) Complete --- RIL [RID 0, Token 245, Success, Len 0 ]
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_request_screen_state: qcril_qmi
_nas_request_screen_state complete with 0
D/RILJ ( 775): [0245]< SCREEN_STATE
sorry for it being so long
---------- Post added at 06:15 PM ---------- Previous post was at 05:46 PM ----------
ziggy46 said:
can you get me a logcat of the radio?
adb logcat -b radio > log.txt
or
adb logcat -b radio
also, this is a KANG from the sensation. therefore data may not work until someone here can build it from source. but we'll try to get it working.
Click to expand...
Click to collapse
let me know if you need another log

here is the rest i think

crazysohc said:
here is the rest i think
Click to expand...
Click to collapse
did you try going into the settings and manually selecting the apn like people had to do on speedrom? i honestly dont see anything wrong in that logcat

ziggy46 said:
did you try going into the settings and manually selecting the apn like people had to do on speedrom? i honestly dont see anything wrong in that logcat
Click to expand...
Click to collapse
yes i did all that i even added proxy port direct to t-mobile and still no data for me :/
---------- Post added at 07:23 PM ---------- Previous post was at 07:08 PM ----------
all i see in the log text is edge:2 css not supported
and with hsdpa

Related

Unable to activate wifi

Hi,
I seem to have lost the ability to activate wifi. Neither the "Comm Manager" nor the 'Wireless LAN" applications are able to turn wifi on. Also, the wifi details are not shown under the "Wireless" Today panel.
The device has been flashed quite a lot recently. I have tried reflashing the original phones roms, the v3 unlock radio rom, and the 2.05 & 2.11 HTC roms; none of these seem to have solved the problem.
Also, possibly the cause, I ran an 'erase 80000000 d80000' & 'erase 0x80100000 0x20000' (radio(?) & radio bootloader(?) from wiki.
Would reflashing the data that was deleted by the above two erases help? (in case a normal re-flash doesn't touch these areas).
I have searched through the forums and the wiki but I'm unable to find a similar problem, so if anyone has any ideas that would be appreciated.
thanks
rob-ix
WHOOPS just saw http://forum.xda-developers.com/showthread.php?t=295211 so this post my not have been required. But, I gotta read it first, so put this on hold for a few mins

Booting using Platform Builder gives the following possible answer for the problem:
20161 PID:239ceb52 TID:23862ede CertVerify: TIACXWLN.dll trust = 2
20179 PID:2375059e TID:23862ede no EEPROM no WLAN!!
I've tried, changing via HTweakC, to allow non-trusted apps to be used but this hasn't changed things.
If anyone can answer these questions or point me in the right direction to answer/fix them it would be appreciated:
1, Is the 'no EEPROM no WLAN' error being caused by 'trust = 2' on the above dll or is in fact caused by having no wlan EEPROM?
2, Is this EEPROM a real one or one simulated via the flash/NAND?
3, Can this data be re-written/flashed?
thanks
Rob-ix

rob-ix said:
1, Is the 'no EEPROM no WLAN' are being caused by 'trust = 2' on the above dll or is in fact caused by having no wlan eeprom?
Click to expand...
Click to collapse
By having EEPROM erased or corrupted.
2, Is this EEPROM a real one or one simulated via the flash/NAND?
Click to expand...
Click to collapse
I think it is inside the MSM6275 chip.
3, Can this data be re-written/flashed?
Click to expand...
Click to collapse
No that i know of.

pof said:
By having EEPROM erased or corrupted.
Click to expand...
Click to collapse
I ran these commands via the BL at one point to try to clear the radio, could these have been responsibile?
erase 80000000 d80000
erase 80100000 20000
thanks
rob-ix

not sure, let me check if i can get a dump of that...
did you actually use 'erase' from bootloader, or 'rerase' from radio bootloader?
where you successfully authenticated to the bootloader/radio bootloader when you did that?

Pof,
pof said:
not sure, let me check if i can get a dump of that...
Click to expand...
Click to collapse
Great. Then I should be able to compare the two dumps.
did you actually use 'erase' from bootloader, or 'rerase' from radio bootloader? where you successfully authenticated to the bootloader/radio bootloader when you did that?
Click to expand...
Click to collapse
I used 'erase' from the bootloader, and I believe I was authenticated at the time.
thanks
Rob

rob-ix said:
Then I should be able to compare the two dumps.
Click to expand...
Click to collapse
bootloader command 'rbmc' dumps nothing on that addreses

go into bootloader, type these commands:
Code:
task 32
task 37 ff
tell me the output of the second

task 37 ff - output
pof said:
go into bootloader, type these commands:
Code:
task 32
task 37 ff
tell me the output of the second
Click to expand...
Click to collapse
Please see attached.
thanks
Rob

Seems that you have erased the EEPROM:
Code:
03/24/2007 23:53:25 [K :: KERNEL] HTC Nand Read!
03/24/2007 23:53:25 [K :: KERNEL] Kernel: EEPROM signature=FF FF FF FF FF
03/24/2007 23:53:25 [K :: KERNEL] HTC Nand Read!
03/24/2007 23:53:25 [K :: KERNEL] Kernel: EEPROM signature Old=FF FF FF FF FF
[...]
CertVerify: TIACXWLN.dll trust = 2
no EEPROM no WLAN!!
On a normal hermes this looks like this:
Code:
05/01/2006 00:00:00 [K :: KERNEL] HTC Nand Read!
05/01/2006 00:00:00 [K :: KERNEL] Kernel: EEPROM signature=50 12 EE 0 2
05/01/2006 00:00:00 [K :: KERNEL] Kernel: EEPROM1 Checksum=0xbd4ccc54
05/01/2006 00:00:00 [K :: KERNEL] HTC Nand Read!
05/01/2006 00:00:00 [K :: KERNEL] Kernel: EEPROM signature Old=50 12 EE 0 2
05/01/2006 00:00:00 [K :: KERNEL] Kernel: EEPROM2 Checksum=0xbd4ccc54
If I find anything for you to try I'll let you know.

Pof,
pof said:
Seems that you have erased the EEPROM:
Click to expand...
Click to collapse
That makes sense. Do you know if it's a real EEPROM or just some flash pretending to be EEPROM? Would GNU Haret be able to dump/reload the information?
thanks
Rob

would HTC have to replace the entire mainboard for this to be fixed, or do they have a tool that could reflash the EEPROM with a new mac adress and such

In theory, should be possible to reflash via bootloader EMAPI commands, but we don't know how to use them, sure HTC knows... but in service centre they most probably will replace the mainboard for that.

pof said:
In theory, should be possible to reflash via bootloader EMAPI commands, but we don't know how to use them, sure HTC knows... but in service centre they most probably will replace the mainboard for that.
Click to expand...
Click to collapse
... thats not good, how much do you think that would cost? over $300?

is there anyway to emulate the EEPROM or put the MAC address in the registry?

task 37 ff output
Output of task 37 ff scrolls way too much overflowing the screen buffer. I don't see a log option in the mtty I downloaded from wiki pages. What's the method to capture large output like that?
TIA

@cjchriscj: no
@aarman: type "task 37 ff" and pull out the USB cable before the buffer grows too big.

Is it possible that people having this problem have flashed _too big_ a OS.nb file using MFG bootloader before having the problem?
I have the feeling that WLAN EEPROM is read from NAND flash, if we manage to find the right offset we can probably rbmc to read it and reflash it with lnb.

I have the same problem
05/23/2006 23:57:46 [K :: KERNEL] HTC Nand Read!
05/23/2006 23:57:46 [K :: KERNEL] Kernel: EEPROM signature=FF FF FF FF FF
05/23/2006 23:57:46 [K :: KERNEL] HTC Nand Read!
05/23/2006 23:57:46 [K :: KERNEL] Kernel: EEPROM signature Old=FF FF FF FF FF
05/23/2006 23:57:46 [K :: KERNEL]
If i understand that pof say for resolve my probleme i need the lnb wifi ?
The offset is not 0xb6d00000 0x20000000 ?

working on it
ok, good news for those who have ****ed up wlan EEPROM...
I was able to rbmc the right place where the WLAN eeprom is stored, as a proof of concept:
This is my MAC address: 00:09:2d:f1:f2:d3
This is the EEPROM signature reported by "task 32 ff": 50 12 EE 0 2
Code:
[B][COLOR="DarkGreen"]50 12 EE 00 02[/COLOR][/B] 00 00 00 06 00 00 00 A1 01 00 00 P.î.........¡...
43 50 AA 80 00 00 00 00 00 00 00 00 00 00 00 00 CPª?............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
02 11 56 05 1B 06 00 11 31 01 00 01 09 56 12 00 ..V.....1....V..
00 00 01 0D 56 71 00 00 00 02 6D 54 [B][COLOR="DarkRed"]D3 F2 F1 2D[/COLOR][/B] ....Vq..........
[B][COLOR="DarkRed"]09 00[/COLOR][/B] 00 00 01 05 5A 64 00 00 00 01 09 5A 00 00 ......Zd.....Z..
00 00 01 0D 5A 00 00 00 00 01 01 0C 03 00 00 00 ....Z...........
01 01 5A 00 00 00 00 01 55 09 01 00 00 00 01 E5 ..Z.....U......å
58 02 00 00 00 01 F1 58 08 00 00 00 01 D5 58 10 X.....ñX.....ÕX.
00 00 00 01 B1 58 04 00 00 00 00 00 00 00 00 00 ....±X..........
00 0C 00 8B 00 C6 00 D0 00 DC 00 EE 00 0C 01 15 ...?.Æ.Ð.Ü.î....
01 17 01 2D 01 67 01 77 01 7F 01 01 39 00 00 11 ...-.g.w...9...
00 04 01 01 01 00 05 01 06 00 02 01 02 01 02 1E ................
00 0A 00 02 05 02 04 11 22 44 03 06 41 20 30 31 ........"D..A 01
32 40 04 09 54 49 20 41 43 58 31 30 30 05 07 54 [email protected] ACX100..T
49 20 54 65 73 74 01 08 00 00 00 00 00 00 00 00 I Test..........
05 02 00 00 3B 00 81 00 C5 00 1F 01 04 04 44 10 ....;..Å.....D.
00 00 45 10 00 00 18 5A 40 00 14 5A 20 00 02 0E [email protected] ...
A0 01 F7 00 08 01 7E 02 78 00 B2 01 8A 09 80 00 .÷...~.x.².?.?.
F7 00 08 01 79 02 78 00 A4 01 8A 09 01 07 00 01 ÷...y.x.¤.?.....
40 00 00 00 01 00 00 05 04 00 01 01 00 00 00 00 @...............
FF FF FF FF FD FD FD FD FB FB FB FB FB 0E 04 09 ÿÿÿÿýýýýûûûûû...
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 ................
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 ................
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 ................
09 09 09 09 09 09 09 0E 01 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 03 02 D4 08 D4 08 07 00 01 .........Ô.Ô....
This is on NAND, around offset 0x500CD800 (after SPL and before MainSplash).
Probably this can be overwriten with 'lnb' command on MFG bootloader, i'm investigating this with Olipro right now.
If anyone wants to serve as a guinea pig, let us know

[Q] OTA update fails on stock firmware

I've been trying to figure out why my OTA update fails. I'm using stock 2.3.6 with kernel XWKK2 with XSA CSC.
The update fails when the counter reaches16% after the first reboot and then boots back into the old system with a message saying that it failed and no trace of the ~200mb download that it performed.
However, there is a file in /system/fota called "ssfback". It seems to contain the dates and times and some other info about the updates. Does anyone know what this file means?
Code:
$ hexdump -C ssfback
00000000 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000010 93 01 00 40 3e 01 00 80 44 41 54 41 05 00 00 00 |[email protected]>...DATA....|
00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000030 00 00 00 00 00 00 00 00 44 4f 4e 45 00 00 00 00 |........DONE....|
00000040 55 55 55 55 00 00 00 00 00 90 e5 05 00 30 8a 00 |UUUU.........0..|
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000060 31 32 2d 30 36 30 33 2d 30 38 32 36 35 36 00 00 |12-0603-082656..|
00000070 31 32 2d 30 36 30 33 2d 30 38 32 37 31 36 00 00 |12-0603-082716..|
00000080 93 01 00 40 3e 01 00 80 44 41 54 41 05 00 00 00 |[email protected]>...DATA....|
00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000a0 00 00 00 00 00 00 00 00 44 4f 4e 45 00 00 00 00 |........DONE....|
000000b0 55 55 55 55 00 00 00 00 00 80 e5 05 00 20 8a 00 |UUUU......... ..|
000000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000d0 31 32 2d 30 36 30 33 2d 30 38 34 37 32 36 00 00 |12-0603-084726..|
000000e0 31 32 2d 30 36 30 33 2d 30 38 34 37 34 36 00 00 |12-0603-084746..|
000000f0 93 01 00 40 3e 01 00 80 44 41 54 41 05 00 00 00 |[email protected]>...DATA....|
00000100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000110 00 00 00 00 00 00 00 00 44 4f 4e 45 00 00 00 00 |........DONE....|
00000120 55 55 55 55 00 00 00 00 00 80 e5 05 00 20 8a 00 |UUUU......... ..|
00000130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000140 31 32 2d 30 36 30 33 2d 32 32 33 34 32 39 00 00 |12-0603-223429..|
00000150 31 32 2d 30 36 30 33 2d 32 32 33 34 34 39 00 00 |12-0603-223449..|
00000160 93 01 00 40 3e 01 00 80 44 41 54 41 05 00 00 00 |[email protected]>...DATA....|
00000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000180 00 00 00 00 00 00 00 00 44 4f 4e 45 00 00 00 00 |........DONE....|
00000190 55 55 55 55 00 00 00 00 00 80 e5 05 00 20 8a 00 |UUUU......... ..|
000001a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001b0 31 32 2d 30 36 30 34 2d 32 32 34 34 32 33 00 00 |12-0604-224423..|
000001c0 31 32 2d 30 36 30 34 2d 32 32 34 34 34 32 00 00 |12-0604-224442..|
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000470

[Q] help~~ who know this ext4 format

the file head is :
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
00000000 3A FF 26 ED 01 00 00 00 20 00 10 00 00 10 00 00 :&?
00000010 00 00 03 00 BF 07 00 00 00 00 00 00 00 00 00 00 ?
00000020 C1 CA 00 00 00 00 00 00 01 00 00 00 10 10 00 00 潦
The right should be:
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
00000000 3A FF 26 ED 01 00 00 00 1C 00 0C 00 00 10 00 00 :&?
00000010 00 00 03 00 C0 07 00 00 00 00 00 00 C1 CA 00 00 ? 潦
00000020 01 00 00 00 0C 10 00 00 00 00 00 00 00 00 00 00
simg2img can't work;

showjechar said:
the file head is :
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
00000000 3A FF 26 ED 01 00 00 00 20 00 10 00 00 10 00 00 :&?
00000010 00 00 03 00 BF 07 00 00 00 00 00 00 00 00 00 00 ?
00000020 C1 CA 00 00 00 00 00 00 01 00 00 00 10 10 00 00 潦
The right should be:
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
00000000 3A FF 26 ED 01 00 00 00 1C 00 0C 00 00 10 00 00 :&?
00000010 00 00 03 00 C0 07 00 00 00 00 00 00 C1 CA 00 00 ? 潦
00000020 01 00 00 00 0C 10 00 00 00 00 00 00 00 00 00 00
simg2img can't work;
Click to expand...
Click to collapse
hello ~

showjechar said:
the file head is :
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
00000000 3A FF 26 ED 01 00 00 00 20 00 10 00 00 10 00 00 :&?
00000010 00 00 03 00 BF 07 00 00 00 00 00 00 00 00 00 00 ?
00000020 C1 CA 00 00 00 00 00 00 01 00 00 00 10 10 00 00 潦
The right should be:
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
00000000 3A FF 26 ED 01 00 00 00 1C 00 0C 00 00 10 00 00 :&?
00000010 00 00 03 00 C0 07 00 00 00 00 00 00 C1 CA 00 00 ? 潦
00000020 01 00 00 00 0C 10 00 00 00 00 00 00 00 00 00 00
simg2img can't work;
Click to expand...
Click to collapse
sudo java -jar ./sgs2toext4.jar system.img system_ext4.img

UNSOL_SIGNAL_STRENGTH final bytes meaning

Looking at logcat -b radio,
D/AT ( 227): +ECSQ: 4, 99, -417
D/AT ( 227): AT< +ECSQ: 4, 99, -417
D/AT ( 227): RIL_URC2_READER:+ECSQ: 4, 99, -417
D/AT ( 227): RIL_URC2_READER Enter processLine
D/RIL ( 227): Nw URC:+ECSQ: 4, 99, -417
I/RILC ( 227): RIL(2) UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:36
I/RILC ( 227): 01 00 00 00 F1 03 00 00 04 00 00 00 63 00 00 00
I/RILC ( 227): 5F FE FF FF 00 00 00 00 00 00 00 00 00 00 00 00
I/RILC ( 227): 00 00 00 00 35 57 08 40 C8 AE 4B 01 30 00 34 00
I figured out what most of UNSOL_SIGNAL_STRENGTH means,
I/RILC ( 227): RIL(2) UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:36
I/RILC ( 227): 01 00 00 00 F1 03 00 00 04 00 00 00 63 00 00 00
| 4| 99
I/RILC ( 227): 5F FE FF FF 00 00 00 00 00 00 00 00 00 00 00 00
-417|
I/RILC ( 227): 00 00 00 00 35 57 08 40 C8 AE 4B 01 30 00 34 00
| ?| ?| ?
except that last line. Chip is MTK6577.
I don't think it is Cdma, Evdo, Lte strength info, as this particular
hardware is GSM/2G.

OK I figured it out.
The bytes are always displayed in rows of 16.
So when it says "length:36" that means it will need at least three rows to display the bytes.
So the final (16×3)-36=12 bytes are irrelevant (assume garbage bytes) and can be ignored!

LG G5 Bootloop

Hello guys,
Since yesterday my g5 is blocked:
a message that the system was corompu appeared, so I wanted to put my re G5 zero except that it is not recognized by LGUP while he is detect by LG MOBILE SUPPORT TOOL and LG Bridge which does not start a recovery.
Do you have an idea ?
PS: I am french and translation through google sorry for spelling.

There's a reason of this bootlop and corrupted system?
Install the right driver for LGUP, it seems impossible that it's not recognized.

Erario said:
There's a reason of this bootlop and corrupted system?
Install the right driver for LGUP, it seems impossible that it's not recognized.
Click to expand...
Click to collapse
The reason comes from the fact bootloop of modifying the build.prop; I have yet resataure the file via a backup that I had done beforehand.
Since the message of corompu system over any access TWRP it was replaced by the original one.
Normally all the drivers are installed jai installed:
LGH850_DLL.msi
LGUP_Lab_Frame_Ver_1_11.msi
LGMobileDriver_WHQL_Ver_4.0.4.exe
LOG LG UP
[12:19:32] Start Find Available USB Port
[12:19:32] Find 0 Port de communication (COM1)
[12:19:32] Find 1 LGE AndroidNet USB Serial Port (COM41)
[12:19:32] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x2bc
[12:19:32] CPort:penPort() Success. Port number is 41
[12:19:32] [T000003] 41 54 0D AT.
[12:19:33] CBasicCom::SendRecvPacket, PACKET_ERROR code = 1460 Msg => [12:19:33] [T000005] EF 00 16 65 7E ...e.
[12:19:34] [R000007] EF 00 00 05 00 AD 7E .......
[12:19:34] ---------------------------------------------------------------------------------
[12:19:34] SubProcess Name : NoOperationCmd
[12:19:34] [T000004] 06 4E 95 7E .N..
[12:19:35] [R000004] 02 6A D3 7E .j..
[12:19:35] [T000005] EF 00 16 65 7E ...e.
[12:19:36] [R000007] EF 00 00 05 00 AD 7E .......
[12:19:36] [T000005] EF A0 1C C0 7E .....
[12:19:37] [R000150] EF A0 00 00 00 00 00 4C 47 2D 48 38 35 30 00 00 00 55 6E 6B 6E 6F 77 6E 00 00 00 00 00 00 00 00 .......LG-H850...Unknown........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 33 35 37 36 35 37 30 37 31 31 36 36 38 34 33 00 ................357657071166843.
00 00 00 00 64 1E 41 6E 64 72 6F 69 64 00 00 00 55 6E 6B 6E 6F 77 6E 00 00 00 00 00 00 00 00 00 ....d.Android...Unknown.........
00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 31 63 6F 6D 6D ...........................1comm
6F 6E 00 00 77 4F 50 45 30 00 00 00 00 00 00 00 00 00 00 0F 40 7E [email protected]
[12:19:37] CComPort::ClosePort, Closed Port Successfully for COM 41
[12:19:37] CBasicComControl::Close, the port(COM41) is closed successfully
[12:19:37] ==> COM41 is detected
[12:19:37] ModelListManager is initialized
[12:19:52] CBasicComControl::IsConnected, the port(COM41) connection is not detected
Click to expand...
Click to collapse

Better Mobile App

welcome