So I tried to revive a water damaged galaxy s4 i9505 and everything seemed to be working. Always when booting finishes it hangs and hard reboots. TWRP and bootloader mode work just fine and I was able to backup the whole system with it.
It gets even more strange because LineageOS without gapps boots fine and works fine. When I flash the gapps it boots and get's stuck and hard reboots. Could a part of the RAM be damaged by the water, so it starts rebooting after it gets allocated?
I managed to grab a kmsg just before it rebooted and would be super excited if someone can find anything about why it's happening. It has been driving me mad as I don't know the cause. Everything is working on LineageOS even the wifi connects.
kmsg: http://pastebin.com/xx6NNNRr
another last_kmsg: http://pastebin.com/1sDAqK4B
I managed to trace it down. Seems like the L1 cache is somehow corrupted after the water damage.
Another log if someones interested:
Code:
[ 37.401977] L1 / TLB Error detected on CPU 2!
[ 37.402130] CESR = 0x00010002
[ 37.402374] CPU speed = 810000
[ 37.402526] MIDR = 0x511f06f0
[ 37.402679] D-cache data parity error
[ 37.402801] D-side CESYNR = 0x00002144
[ 37.402954] Kernel panic - not syncing: L1 nonrecoverable cache error detected
[ 37.403137] CPU0: stopping
[ 37.403289] [<c010b85c>] (unwind_backtrace+0x0/0xec) from [<c010abc8>] (handle_IPI+0x144/0x238)
[ 37.403381] [<c010abc8>] (handle_IPI+0x144/0x238) from [<c0100554>] (gic_handle_irq+0x138/0x164)
[ 37.403533] [<c0100554>] (gic_handle_irq+0x138/0x164) from [<c0105780>] (__irq_svc+0x40/0x74)
[ 37.403656] Exception stack(0xdeda5c20 to 0xdeda5c68)
[ 37.403747] 5c20: 00000001 ffffffff ffffffaa 00000001 c4998e40 c0f1a1c0 c0f1a1c8 00000003
[ 37.403869] 5c40: c0f17e40 00000000 00000001 03a81000 00000004 deda5c68 c017de58 c01d10f4
[ 37.404022] 5c60: 20000113 ffffffff
[ 37.404113] [<c0105780>] (__irq_svc+0x40/0x74) from [<c01d10f4>] (smp_call_function_many+0x26c/0x2a4)
[ 37.404266] [<c01d10f4>] (smp_call_function_many+0x26c/0x2a4) from [<c01d1174>] (smp_call_function+0x48/0x70)
[ 37.404388] [<c01d1174>] (smp_call_function+0x48/0x70) from [<c070d3b0>] (cpuidle_latency_notify+0x18/0x24)
[ 37.404541] [<c070d3b0>] (cpuidle_latency_notify+0x18/0x24) from [<c01a8bcc>] (notifier_call_chain+0x40/0x68)
[ 37.404693] [<c01a8bcc>] (notifier_call_chain+0x40/0x68) from [<c01a8e18>] (__blocking_notifier_call_chain+0x40/0x58)
[ 37.404846] [<c01a8e18>] (__blocking_notifier_call_chain+0x40/0x58) from [<c01a8e44>] (blocking_notifier_call_chain+0x14/0x1c)
[ 37.404998] [<c01a8e44>] (blocking_notifier_call_chain+0x14/0x1c) from [<c01bfdb8>] (pm_qos_update_target+0x118/0x130)
[ 37.405151] [<c01bfdb8>] (pm_qos_update_target+0x118/0x130) from [<c072c4b8>] (msmsdcc_enable+0x24/0x158)
[ 37.405242] [<c072c4b8>] (msmsdcc_enable+0x24/0x158) from [<c070fa9c>] (__mmc_claim_host+0x180/0x190)
[ 37.405395] [<c070fa9c>] (__mmc_claim_host+0x180/0x190) from [<c055a8c4>] (sdioh_buffer_tofrom_bus+0x50/0x118)
[ 37.405548] [<c055a8c4>] (sdioh_buffer_tofrom_bus+0x50/0x118) from [<c055ba14>] (sdioh_request_buffer+0x1e4/0x2ec)
[ 37.405700] [<c055ba14>] (sdioh_request_buffer+0x1e4/0x2ec) from [<c0559d58>] (bcmsdh_recv_buf+0xe4/0x110)
[ 37.405853] [<c0559d58>] (bcmsdh_recv_buf+0xe4/0x110) from [<c057e408>] (dhd_bcmsdh_recv_buf.constprop.8+0x68/0x84)
[ 37.406005] [<c057e408>] (dhd_bcmsdh_recv_buf.constprop.8+0x68/0x84) from [<c0581210>] (dhdsdio_readframes+0xbc8/0x183c)
[ 37.406158] [<c0581210>] (dhdsdio_readframes+0xbc8/0x183c) from [<c0585204>] (dhd_bus_dpc+0xa24/0x1230)
[ 37.406311] [<c0585204>] (dhd_bus_dpc+0xa24/0x1230) from [<c0576b60>] (dhd_dpc_thread+0x108/0x1a0)
[ 37.406402] [<c0576b60>] (dhd_dpc_thread+0x108/0x1a0) from [<c01a3040>] (kthread+0xb0/0xbc)
[ 37.406555] [<c01a3040>] (kthread+0xb0/0xbc) from [<c010673c>] (kernel_thread_exit+0x0/0x8)
[ 37.406677] CPU1: stopping
[ 37.406829] [<c010b85c>] (unwind_backtrace+0x0/0xec) from [<c010abc8>] (handle_IPI+0x144/0x238)
[ 37.406982] [<c010abc8>] (handle_IPI+0x144/0x238) from [<c0100554>] (gic_handle_irq+0x138/0x164)
[ 37.407135] [<c0100554>] (gic_handle_irq+0x138/0x164) from [<c010595c>] (__irq_usr+0x3c/0x60)
[ 37.407196] Exception stack(0xddfa5fb0 to 0xddfa5ff8)
[ 37.407348] 5fa0: 0000001b 12def1c0 00000002 12def000
[ 37.407501] 5fc0: b4284e00 b4283f00 00000014 133087b8 12c15b50 b4284e00 00008001 12e41f00
[ 37.407562] 5fe0: 71111850 acfcb010 b3ebc2d1 b41b125a 000d0030 ffffffff
[ 37.407714] CPU3: stopping
[ 37.407836] [<c010b85c>] (unwind_backtrace+0x0/0xec) from [<c010abc8>] (handle_IPI+0x144/0x238)
[ 37.407989] [<c010abc8>] (handle_IPI+0x144/0x238) from [<c0100554>] (gic_handle_irq+0x138/0x164)
[ 37.408142] [<c0100554>] (gic_handle_irq+0x138/0x164) from [<c010595c>] (__irq_usr+0x3c/0x60)
[ 37.408294] Exception stack(0xdcd71fb0 to 0xdcd71ff8)
[ 37.408386] 1fa0: 00000000 9c747600 00000034 00000034
[ 37.408538] 1fc0: a7b3bc80 a7b3bc80 b42d5140 00000034 9ec9b5b7 9c747600 a7b3bc98 97f33e30
[ 37.408599] 1fe0: 00001002 97f33d30 b409aafb b3ec69b0 200f0030 ffffffff
[ 37.810028] Rebooting in 5 seconds..
[ 42.825500] Going down for restart now
[ 42.825927] msm_restart : clear reset flag
I don't think there is hope for this board anymore :silly:
I got this little guy for cheap and swapped the motherboard into my functional screen, and guess what...everythings working
{
"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"
}
Related
Updated AICP today and I'm stuck at boot with the AICP logo... Here is what dmesg gives me:
Code:
[ 700.306266] voice_call_state_get: voice_call_state Off
[ 700.450763] msm_csid_init: CSID_VERSION = 0x30050000
[ 700.451654] msm_csid_irq CSID0_IRQ_STATUS_ADDR = 0x800
[ 700.460161] ====================== msm_sensor_power_up
[ 700.462547] MSM-CPP cpp_init_hardware:850 CPP HW Version: 0x60000000
[ 700.462564] MSM-CPP cpp_init_hardware:868 stream_cnt:0
[ 700.480582] msm_cci_init:1421: hw_version = 0x10040000
[ 700.480868] msm_get_otp_data: Enter
[ 700.480879] msm_get_otp_rear_camera_module_id: INFO: module_id is 0x9
[ 700.480884] msm_get_otp_rear_camera_module_id: sony_imx298 succeed
[ 700.480889] msm_sensor_match_id:imx298 OTP module id:0x9 expected module_id:0x9
[ 700.480892] msm_get_otp_data: Enter
[ 700.480896] msm_get_otp_rear_camera_vcm_id: INFO: vcm_id[0] is 0x09
[ 700.480900] msm_get_otp_rear_camera_vcm_id: INFO: vcm_id[1] is 0x05
[ 700.480903] msm_get_otp_rear_camera_vcm_id: INFO: vcm_id[2] is 0x1c
[ 700.480906] msm_get_otp_rear_camera_vcm_id: INFO: vcm_id[3] is 0x06
[ 700.480910] msm_sensor_match_id:eek:TP vcm id:0x6 expected vcm_id:0x6
[ 700.574085] msm_flash_subdev_do_ioctl:1427 Enter
[ 700.574158] msm_flash_subdev_ioctl:729 Enter
[ 700.574165] msm_flash_config:684 Enter msm_flash_config type 0
[ 700.574170] msm_flash_init:461 Enter
[ 700.574176] msm_flash_init:519 Exit<3>[ 700.574184] msm_flash_config:718 Exit msm_flash_config type 0
[ 700.574188] msm_flash_subdev_do_ioctl:1485 Exit
[ 700.590652] msm_qti_pp_get_rms_value_control, back not active to query rms be_idx:3
[ 700.592574] msm_voice_sound_focus_get: Error getting Sound Focus Params, err=-22
[ 700.592631] msm_voice_source_tracking_get: Error getting Source Tracking Params, err=-22
[ 700.592682] msm_audio_get_copp_idx_from_port_id: Invalid FE, exiting
[ 700.592687] msm_audio_sound_focus_get: Could not get copp idx for port_id=16385
[ 700.592733] msm_audio_get_copp_idx_from_port_id: Invalid FE, exiting
[ 700.592737] msm_audio_source_tracking_get: Could not get copp idx for port_id=16385
[ 700.592787] msm_voice_sound_focus_get: Error getting Sound Focus Params, err=-22
[ 700.592837] msm_voice_source_tracking_get: Error getting Source Tracking Params, err=-22
[ 700.592884] msm_audio_get_copp_idx_from_port_id: Invalid FE, exiting
[ 700.592888] msm_audio_sound_focus_get: Could not get copp idx for port_id=4101
[ 700.592935] msm_audio_get_copp_idx_from_port_id: Invalid FE, exiting
[ 700.592939] msm_audio_source_tracking_get: Could not get copp idx for port_id=4101
[ 700.594567] msm_flash_subdev_do_ioctl:1427 Enter
[ 700.594582] msm_flash_subdev_ioctl:729 Enter
[ 700.594589] msm_flash_config:684 Enter msm_flash_config type 1
[ 700.594596] msm_flash_off:401 Enter
[ 700.594616] msm_flash_off:413 Exit
[ 700.594621] msm_flash_config:718 Exit msm_flash_config type 1
[ 700.594626] msm_flash_subdev_do_ioctl:1485 Exit
[ 700.596206] msm_pcm_volume_ctl_get substream runtime not found
[ 700.596624] msm_pcm_volume_ctl_get substream runtime not found
[ 700.597381] msm_pcm_volume_ctl_get substream runtime not found
[ 700.597536] msm_compr_audio_effects_config_get: stream or effects inactive
[ 700.598061] msm_pcm_volume_ctl_get substream runtime not found
[ 700.598219] msm_compr_audio_effects_config_get: stream or effects inactive
[ 700.598672] msm_compr_audio_effects_config_get: stream or effects inactive
[ 700.599107] msm_compr_audio_effects_config_get: stream or effects inactive
[ 700.599551] msm_pcm_volume_ctl_get substream or runtime not found
[ 700.600098] msm_pcm_volume_ctl_get substream runtime not found
[ 700.600295] msm_compr_audio_effects_config_get: stream or effects inactive
[ 700.600815] msm_compr_audio_effects_config_get: stream or effects inactive
[ 700.601322] msm_compr_audio_effects_config_get: stream or effects inactive
[ 700.601717] msm_compr_audio_effects_config_get: stream or effects inactive
[ 700.602068] msm_compr_audio_effects_config_get: stream or effects inactive
[ 700.602422] msm_compr_audio_effects_config_get: stream or effects inactive
[ 700.607901] voice_call_state_get: voice_call_state Off
[ 700.609106] tasha_codec tasha_codec: tasha_mad_input_put: mic bias source not found for input = DMIC1
[ 700.624999] msm_csid_init: CSID_VERSION = 0x30050000
[ 700.625985] msm_csid_irq CSID2_IRQ_STATUS_ADDR = 0x800
[ 700.629203] MSM-CPP cpp_init_hardware:850 CPP HW Version: 0x60000000
[ 700.629213] MSM-CPP cpp_init_hardware:868 stream_cnt:0
[ 700.633399] ====================== msm_sensor_power_up
[ 700.647059] msm_cci_init:1421: hw_version = 0x10040000
[ 700.647330] msm_get_otp_data: Enter
[ 700.647337] msm_get_otp_front_camera_module_id: INFO: module_id is 0x2
[ 700.647341] msm_get_otp_front_camera_module_id: ov8865_plus succeed
[ 700.647345] msm_sensor_match_id:ov8865_sunny OTP module id:0x2 expected module_id:0x2
[ 703.392200] PWM device already freed
[ 703.392412] PWM device already freed
[ 703.392607] PWM device already freed
Any help would be great. I have tried re-flashing the update, as well as clearing cache, etc.
Ended up resetting the device. Please ignore
{
"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"
}
---Setup---
1) We are evaluating using Raspberry Pi Compute Module CM3.
2) USB-HUB and USB-UART are boarded on the IO board.
3) USB-HUB is working in Self-power mode.
4) VBUS-detect of USB-HUB uses the same 3.3V power supply as CM3.
5) Two LTE modules are connected to USB-HUB via USB-SERIAL and each LTE module takes 2A
---Protocol---
AT commands
---Problem----
The LTE modules which are connected to USB-HUB are disconnecting.This problem occurs only sometimes not always
Following are kernel Logs.
Kerenl log:
19:47:58 raspberrypi kernel: [ 9301.001438] usb usb1-port1: disabled by hub (EMI?), re-enabling...
19:47:58 raspberrypi kernel: [ 9301.001457] usb 1-1: USB disconnect, device number 11
19:47:58 raspberrypi kernel: [ 9301.001463] usb 1-1.1: USB disconnect, device number 12
19:47:58 raspberrypi kernel: [ 9301.001668] ftdi_sio ttyUSB2: error from flowcontrol urb
19:47:58 raspberrypi kernel: [ 9301.001872] ftdi_sio ttyUSB2: FTDI USB Serial Device converter now disconnected from ttyUSB2
19:47:58 raspberrypi kernel: [ 9301.001906] ftdi_sio 1-1.1:1.0: device disconnected
19:47:58 raspberrypi kernel: [ 9301.002107] ftdi_sio ttyUSB3: error from flowcontrol urb
19:47:58 raspberrypi kernel: [ 9301.003371] ftdi_sio ttyUSB3: FTDI USB Serial Device converter now disconnected from ttyUSB3
19:47:58 raspberrypi kernel: [ 9301.003429] ftdi_sio 1-1.1:1.1: device disconnected
19:47:58 raspberrypi kernel: [ 9301.010150] ftdi_sio ttyUSB4: FTDI USB Serial Device converter now disconnected from ttyUSB4
19:47:58 raspberrypi kernel: [ 9301.010212] ftdi_sio 1-1.1:1.2: device disconnected
19:47:58 raspberrypi kernel: [ 9301.010430] ftdi_sio ttyUSB5: error from flowcontrol urb
19:47:58 raspberrypi kernel: [ 9301.018012] ftdi_sio ttyUSB5: FTDI USB Serial Device converter now disconnected from ttyUSB5
---Question---
Any investigation method and solution?
Problem solved
I saw a threads from oneplus for unlock bootloader, I tried that and hope can use dual sim on my T-Mobile phone.
https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-%28t-mobile-version%29"]https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-%28t-mobile-version%29
I follow those steps unlocked bootloader but dual sim function is not available, so I found another threads shows dual sim is ready to use.
So I just follow his steps then ...... Phone always go recovery mode first, then reboot to initial welcome screen. It automatically turn off less than three sec.
I have no idea hoe fix that. If I just need official Rom in future, how can I fix that?
https://forums.oneplus.com/threads/no-longer-waiting-for-t-mobile-updates.942145/"]https://forums.oneplus.com/threads/no-longer-waiting-for-t-mobile-updates.942145/
{
"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 what shows on CMD
I also tried wipe data, format devise in recovery, it not works
C:\>cd fastboot
C:\FASTBOOT>flash-all.bat
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.293s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.044s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2860 MB) to disk... took 21.514s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
archive does not contain 'system_other.img'
extracting vbmeta.img (0 MB) to disk... took 0.002s
archive does not contain 'vbmeta.sig'
extracting vendor.img (1024 MB) to disk... took 9.014s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 28835840 4k blocks and 7223040 inodes
Filesystem UUID: 50d507d8-9c77-11e9-857c-a19626331dd2
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: f5f0ba62
--------------------------------------------
checking product...
OKAY [ 0.002s]
sending 'boot_a' (65536 KB)...
OKAY [ 1.886s]
writing 'boot_a'...
OKAY [ 0.287s]
sending 'dtbo' (8192 KB)...
OKAY [ 0.239s]
writing 'dtbo'...
OKAY [ 0.106s]
erasing 'system_a'...
OKAY [ 0.143s]
sending sparse 'system_a' 1/6 (524284 KB)...
OKAY [ 15.506s]
writing 'system_a' 1/6...
OKAY [ 0.003s]
sending sparse 'system_a' 2/6 (499286 KB)...
OKAY [ 17.704s]
writing 'system_a' 2/6...
OKAY [ 0.003s]
sending sparse 'system_a' 3/6 (519680 KB)...
OKAY [ 17.003s]
writing 'system_a' 3/6...
OKAY [ 0.004s]
sending sparse 'system_a' 4/6 (513053 KB)...
OKAY [ 17.302s]
writing 'system_a' 4/6...
OKAY [ 0.002s]
sending sparse 'system_a' 5/6 (522296 KB)...
OKAY [ 17.746s]
writing 'system_a' 5/6...
OKAY [ 0.004s]
sending sparse 'system_a' 6/6 (220472 KB)...
OKAY [ 8.681s]
writing 'system_a' 6/6...
OKAY [ 0.004s]
sending 'vbmeta' (4 KB)...
OKAY [ 6.543s]
writing 'vbmeta'...
OKAY [ 0.004s]
sending sparse 'vendor' 1/2 (523043 KB)...
OKAY [ 15.642s]
writing 'vendor' 1/2...
OKAY [ 0.004s]
sending sparse 'vendor' 2/2 (290984 KB)...
OKAY [ 11.753s]
writing 'vendor' 2/2...
OKAY [ 0.004s]
Setting current slot to 'a'...
OKAY [ 17.400s]
erasing 'userdata'...
OKAY [ 0.722s]
sending 'userdata' (5273 KB)...
OKAY [ 0.156s]
writing 'userdata'...
OKAY [ 0.004s]
rebooting...
finished. total time: 148.965s
Press any key to exit...
Don't use Fastboot, use Qualcomm Snapdragon processor tool instead.
Fastbooted image don't wipe the modem firmware properly, instead you have bricked the modem. I found out why - the exact same thing happened to me, shuts down immediately after it gets to the welcome screen so I reflashed the phone with Qualcomm Snapdragon processor tool (it's in a thread covering the conversion of T-Mobile phone to international - https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 ), with a modified flasher software (which bypasses the checks on the phone). On the Pixel Experience ROM before I nuked the SSD with the Qualcomm Snapdragon processor tool from OnePlus, I found out why when I was struggling to fix it; wiped IMEI ID so SIM wasn't detected at all (my own fault, I wiped the /system without realizing that it would brick the modem).
Sent from my ONEPLUS 6T using Tapatalk
Dr. Mario said:
Don't use Fastboot, use Qualcomm Snapdragon processor tool instead.
Fastbooted image don't wipe the modem firmware properly, instead you have bricked the modem. I found out why - the exact same thing happened to me, shuts down immediately after it gets to the welcome screen so I reflashed the phone with Qualcomm Snapdragon processor tool (it's in a thread covering the conversion of T-Mobile phone to international - https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 ), with a modified flasher software (which bypasses the checks on the phone). On the Pixel Experience ROM before I nuked the SSD with the Qualcomm Snapdragon processor tool from OnePlus, I found out why when I was struggling to fix it; wiped IMEI ID so SIM wasn't detected at all (my own fault, I wiped the /system without realizing that it would brick the modem).
Sent from my ONEPLUS 6T using Tapatalk
Click to expand...
Click to collapse
It's back to normal and able show dual sim now.
Thanks, I spent more than 12 hrs for that, finally its back and even better.
Good, I am glad you got it fixed.
Sent from my ONEPLUS 6T using Tapatalk
My Motorola MOTO G6 plus is dead
The model is the XT1926-3 and suddenly the screen "freezed" while I was using it. I restarted the phone by holding down the power button and from that moment it does not turn on anymore. Completely black screen. With the "power + volume -" keys I can't enter recovery.
So I tried to unbrick with the blankflash loading, but it always gives me this error:
[ 0.000] Opening device: \\.\COM4
[ 0.014] Detecting device
[ 0.016] ...cpu.id = 172 (0xac)
[ 0.016] ...cpu.sn = 2974230727 (0xb14728c7)
[ 0.016] Opening singleimage
[ 0.020] Loading package
[ 0.021] ...filename = pkg.xml
[ 0.022] Loading programmer
[ 0.022] ...filename = programmer.elf
[ 0.022] Sending programmer
[ 0.209] Handling things over to programmer
[ 0.209] Identifying CPU version
[ 0.209] Waiting for firehose to get ready
[ 3.221] ...SDM630 1.0
[ 3.221] Determining target secure state
[ 3.223] ...secure = yes
[ 3.238] Configuring device...
[ 3.242] Flashing GPT...
[ 3.242] Flashing partition with gpt.bin
[ 3.244] Initializing storage
[ 8.440] Target NAK!
[ 8.441] ...ERROR: Failed to open the SDCC Device slot 0 partition 0
[ 8.441] ...ERROR: Failed to open the device 1 slot 0 partition 0
[ 8.441] ...INFO: Device type 1, slot 0, partition 0, error 0
[ 8.441] ...WARN: Get Info failed to open 1 slot 0, partition 0, error 0
[ 8.441] ...ERROR: Failed to get device info slot:0artition:0
[ 8.441] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 8.441] ...ERROR 14: Line 1281: HANDLE_STORAGE_INFO_FAILURE
[ 8.442] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 8.442] Check qboot_log.txt for more details
[ 8.443] Total time: 8.444s
[ 8.443]
[ 8.443] qboot version 3.86
[ 8.443]
[ 8.443] DEVICE {
[ 8.443] name = "\\.\COM4",
[ 8.443] flags = "0x144",
[ 8.443] addr = "0x62FD54",
[ 8.443] sahara.current_mode = "0",
[ 8.443] api.buffer = "0xFB8020",
[ 8.443] cpu.serial = "2974230727",
[ 8.443] cpu.id = "172",
[ 8.443] cpu.sv_sbl = "1",
[ 8.443] cpu.name = "SDM630",
[ 8.443] storage.type = "eMMC",
[ 8.443] sahara.programmer = "programmer.elf",
[ 8.443] module.firehose = "0x7D1880",
[ 8.443] api.firehose = "0x7D1950",
[ 8.443] cpu.ver = "256",
[ 8.443] cpu.vername = "1.0",
[ 8.443] fh.max_packet_sz = "1048576",
[ 8.443] fh.storage_inited = "1",
[ 8.443] provisioning_may_hang = "true",
[ 8.444] }
[ 8.444]
Click to expand...
Click to collapse
I tried with 3 different blackflashes on 2 different PCs, also changing the USB port, but nothing: |
Do you have a working blankflash? Some advice?
Should I use it as a paperweight?
Try to hold the power button for 1-2 minutes.
ChIP_83 said:
My Motorola MOTO G6 plus is dead
The model is the XT1926-3 and suddenly the screen "freezed" while I was using it. I restarted the phone by holding down the power button and from that moment it does not turn on anymore. Completely black screen. With the "power + volume -" keys I can't enter recovery.
So I tried to unbrick with the blankflash loading, but it always gives me this error:
I tried with 3 different blackflashes on 2 different PCs, also changing the USB port, but nothing: |
Do you have a working blankflash? Some advice?
Should I use it as a paperweight?
Click to expand...
Click to collapse
What shows up in your device manager?
And send us the qboot_log.txt
Did you do any overclocking or modding in your phone before this happened?
ChIP_83 said:
My Motorola MOTO G6 plus is dead
The model is the XT1926-3 and suddenly the screen "freezed" while I was using it. I restarted the phone by holding down the power button and from that moment it does not turn on anymore. Completely black screen. With the "power + volume -" keys I can't enter recovery.
So I tried to unbrick with the blankflash loading, but it always gives me this error:
I tried with 3 different blackflashes on 2 different PCs, also changing the USB port, but nothing: |
Do you have a working blankflash? Some advice?
Should I use it as a paperweight?
Click to expand...
Click to collapse
Okay, what does the device manager show the device as, it could be bricked as qualcomm 9008,
The qboot log file could be nice as well,
After trying everything and failing, this file saved me.
C:\blankflash_river_QPU30.52-23>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ 0.003] Detecting device
[ 0.007] ...cpu.id = 186 (0xba)
[ 0.007] ...cpu.sn = 4075180311 (0xf2e65117)
[ 0.008] Opening singleimage
[ 0.117] Loading package
[ 0.123] ...filename = singleimage.pkg.xml
[ 0.126] Loading programmer
[ 0.127] ...filename = programmer.mbn
[ 0.127] Sending programmer
[ 0.413] Handling things over to programmer
[ 0.414] Identifying CPU version
[ 0.418] Waiting for firehose to get ready
[ 3.444] ...MSM8953 1.0
[ 3.444] Determining target secure state
[ 3.447] ...secure = yes
[ 3.502] Configuring device...
[ 3.512] Flashing GPT...
[ 3.513] Flashing partition with gpt.bin
[ 3.524] Initializing storage
[ 3.561] ...blksz = 512
[ 3.692] Re-initializing storage...
[ 3.693] Initializing storage
[ 3.811] Flashing bootloader...
[ 3.844] Flashing aboot_a with emmc_appsboot.mbn
[ 4.107] Flashing rpm_a with rpm.mbn
[ 4.190] Flashing tz_a with tz.mbn
[ 4.493] Flashing devcfg_a with devcfg.mbn
[ 4.544] Flashing cmnlib_a with cmnlib_30.mbn
[ 4.765] Flashing cmnlib64_a with cmnlib64_30.mbn
[ 4.998] Flashing keymaster_a with keymaster64.mbn
[ 5.213] Flashing prov_a with prov.mbn
[ 5.286] Flashing sbl1_a with sbl1.mbn
[ 5.420] Rebooting to fastboot
[ 5.423] Total time: 5.425s
guy thank you very much you're a god