Related
< waiting for device >
opening device: \\.\COM5
OKAY [ 0.004s]
greeting device for command mode
OKAY [ 0.003s]
identifying device
...serial = 0x42BC4F8
...chip-id = 0x811
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.007s]
validating files
OKAY [ 0.001s]
switching to download mode
OKAY [ 0.001s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
there were something wrong in programmer.mbn file
is any one knows what programmer.mbn file contain .
i thought it contain qualcomm msm programmer code and some sdi.img file content.
before adding sdi file it cant start download but after adding some sdi content then phone goes to downloading image but has some packet problem .please help
Mine tooo.......
hiten7236 said:
< waiting for device >
opening device: \\.\COM5
OKAY [ 0.004s]
greeting device for command mode
OKAY [ 0.003s]
identifying device
...serial = 0x42BC4F8
...chip-id = 0x811
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.007s]
validating files
OKAY [ 0.001s]
switching to download mode
OKAY [ 0.001s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
there were something wrong in programmer.mbn file
is any one knows what programmer.mbn file contain .
i thought it contain qualcomm msm programmer code and some sdi.img file content.
before adding sdi file it cant start download but after adding some sdi content then phone goes to downloading image but has some packet problem .please help
Click to expand...
Click to collapse
Can u just upload the file in a zip which ur using...ill check that i may help u....
I have the same problem, I was constantly changing roms and never had this problem at most had a bootloop, but that was all. :crying:
I tried with Miflash, blankflash does not work, the only options that remain are to develop the missing files and / or find out who gave him solution for hardbrick moto X and moto G and ask him where he got those files or how made the files?
So, can you tell me... We need to find any solution, the problem is old, I realized when I read the forums and others.
My English is horrible, in fact I do not speak English, I speak Spanish, but I do understand some English
I'm new here
Harsh_1998 said:
Can u just upload the file in a zip which ur using...ill check that i may help u....
Click to expand...
Click to collapse
@Harsh_1998 I have a blankflash zip file but its a older version and I need a newer but Motorola isn't releasing blankflash zip file for Moto X Play and I found it myself and now my device got hard bricked can you see to it I need a blankflash for unbricking my device. Please help!!!!
Hi, after the official OTA upgrade of my Nexus 9 the MAC address of WiFi is 02:00:00:00:00 and the WiFi is not working anymore.
The same problem for the Bluetooth.
I try to reinstall everything many times, different ROM's too, but I cannot solve It.
I search everywhere on internet bit I cannot find any useful information.
Can anyone help me please?
mirkorazietti said:
Hi, after the official OTA upgrade of my Nexus 9 the MAC address of WiFi is 02:00:00:00:00 and the WiFi is not working anymore.
The same problem for the Bluetooth.
I try to reinstall everything many times, different ROM's too, but I cannot solve It.
I search everywhere on internet bit I cannot find any useful information.
Can anyone help me please?
Click to expand...
Click to collapse
Can you give me the kernel log after full boot
just do
su
dmesg > /sdcard/log.log
Then just give me /sdcard/log.log
I probably won't be able to fix it but I want to know what's happening
USBhost said:
Can you give me the kernel log after full boot
just do
su
dmesg > /sdcard/log.log
Then just give me /sdcard/log.log
I probably won't be able to fix it but I want to know what's happening
Click to expand...
Click to collapse
Hi, that's the log file
Thank in advance for your time
mirkorazietti said:
Hi, that's the log file
Thank in advance for your time
Click to expand...
Click to collapse
Wow that's something you don't see everyday....
Code:
[ 31.074029] found wifi platform device bcm4329_wlan
[ 31.074046] unregister wifi platform drivers
[ 31.074094] dhd_module_init: Failed to load the driver, try cnt 1
[ 31.074207] found wifi platform device bcm4329_wlan
[ 31.074434] Power-up adapter 'DHD generic adapter'
[ 31.074476] wifi_platform_set_power = 1
[ 31.074492] flounder_wifi_power: 1
[ 31.380496] wifi_platform_bus_enumerate device present 1
[ 33.380485] failed to power up DHD generic adapter, 3 retry left
[ 33.396608] wifi_platform_set_power = 0
[ 33.396628] flounder_wifi_power: 0
[ 33.497077] wifi_platform_bus_enumerate device present 0
[ 33.497137] wifi_platform_set_power = 1
[ 33.497153] flounder_wifi_power: 1
[ 33.803833] wifi_platform_bus_enumerate device present 1
[ 35.803940] failed to power up DHD generic adapter, 2 retry left
[ 35.820048] wifi_platform_set_power = 0
[ 35.820067] flounder_wifi_power: 0
[ 35.920592] wifi_platform_bus_enumerate device present 0
[ 35.920648] wifi_platform_set_power = 1
[ 35.920666] flounder_wifi_power: 1
[ 36.227139] wifi_platform_bus_enumerate device present 1
[ 38.227168] failed to power up DHD generic adapter, 1 retry left
[ 38.243300] wifi_platform_set_power = 0
[ 38.243320] flounder_wifi_power: 0
[ 38.343735] wifi_platform_bus_enumerate device present 0
[ 38.343797] wifi_platform_set_power = 1
[ 38.343814] flounder_wifi_power: 1
[ 38.650518] wifi_platform_bus_enumerate device present 1
[ 40.650406] failed to power up DHD generic adapter, 0 retry left
[ 40.666528] wifi_platform_set_power = 0
[ 40.666547] flounder_wifi_power: 0
[ 40.677534] INFO: task kworker/0:1:18 blocked for more than 10 seconds.
[ 40.677561] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.677589] kworker/0:1 D ffffffc000086904 0 18 2 0x00000000
[ 40.677663] Workqueue: events request_firmware_work_func
[ 40.677691] Call trace:
[ 40.677726] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.677758] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.677779] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.677799] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.677820] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.677843] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.677864] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.677885] [<ffffffc00047cc50>] request_firmware_work_func+0x28/0x54
[ 40.677911] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.677932] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.677956] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.677998] INFO: task kworker/0:2:85 blocked for more than 10 seconds.
[ 40.678014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.678030] kworker/0:2 D ffffffc000086904 0 85 2 0x00000000
[ 40.678076] Workqueue: events request_firmware_work_func
[ 40.678099] Call trace:
[ 40.678120] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.678140] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.678174] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.678193] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.678258] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.678279] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.678299] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.678319] [<ffffffc00047cc50>] request_firmware_work_func+0x28/0x54
[ 40.678340] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.678362] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.678382] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.678402] INFO: task kworker/u4:1:87 blocked for more than 10 seconds.
[ 40.678417] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.678434] kworker/u4:1 D ffffffc000086904 0 87 2 0x00000000
[ 40.678486] Workqueue: fwu_workqueue fwu_startup_fw_update_work
[ 40.678509] Call trace:
[ 40.678530] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.678550] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.678570] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.678590] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.678611] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.678631] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.678651] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.678672] [<ffffffc00047cc20>] request_firmware+0x14/0x1c
[ 40.678693] [<ffffffc000635454>] synaptics_fw_updater+0x3e0/0x8b0
[ 40.678713] [<ffffffc000636100>] fwu_startup_fw_update_work+0x24/0x50
[ 40.678734] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.678754] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.678774] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.767142] wifi_platform_bus_enumerate device present 0
[ 40.767181] failed to power up DHD generic adapter, max retry reached**
It looks like something happened to your wifi card that it can't poweron.
There's really nothing you can do in the software side of things sorry.
You can try replacing the motherboard but that's like 1/3 the cost of the tablet.....
Or send it in to repair, do you still have warranty? I know you rooted your device but who knows right :laugh:
Sorry for the bad news...
If none of those are options you can always just use ethernet.
USBhost said:
Wow that's something you don't see everyday....
Code:
[ 31.074029] found wifi platform device bcm4329_wlan
[ 31.074046] unregister wifi platform drivers
[ 31.074094] dhd_module_init: Failed to load the driver, try cnt 1
[ 31.074207] found wifi platform device bcm4329_wlan
[ 31.074434] Power-up adapter 'DHD generic adapter'
[ 31.074476] wifi_platform_set_power = 1
[ 31.074492] flounder_wifi_power: 1
[ 31.380496] wifi_platform_bus_enumerate device present 1
[ 33.380485] failed to power up DHD generic adapter, 3 retry left
[ 33.396608] wifi_platform_set_power = 0
[ 33.396628] flounder_wifi_power: 0
[ 33.497077] wifi_platform_bus_enumerate device present 0
[ 33.497137] wifi_platform_set_power = 1
[ 33.497153] flounder_wifi_power: 1
[ 33.803833] wifi_platform_bus_enumerate device present 1
[ 35.803940] failed to power up DHD generic adapter, 2 retry left
[ 35.820048] wifi_platform_set_power = 0
[ 35.820067] flounder_wifi_power: 0
[ 35.920592] wifi_platform_bus_enumerate device present 0
[ 35.920648] wifi_platform_set_power = 1
[ 35.920666] flounder_wifi_power: 1
[ 36.227139] wifi_platform_bus_enumerate device present 1
[ 38.227168] failed to power up DHD generic adapter, 1 retry left
[ 38.243300] wifi_platform_set_power = 0
[ 38.243320] flounder_wifi_power: 0
[ 38.343735] wifi_platform_bus_enumerate device present 0
[ 38.343797] wifi_platform_set_power = 1
[ 38.343814] flounder_wifi_power: 1
[ 38.650518] wifi_platform_bus_enumerate device present 1
[ 40.650406] failed to power up DHD generic adapter, 0 retry left
[ 40.666528] wifi_platform_set_power = 0
[ 40.666547] flounder_wifi_power: 0
[ 40.677534] INFO: task kworker/0:1:18 blocked for more than 10 seconds.
[ 40.677561] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.677589] kworker/0:1 D ffffffc000086904 0 18 2 0x00000000
[ 40.677663] Workqueue: events request_firmware_work_func
[ 40.677691] Call trace:
[ 40.677726] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.677758] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.677779] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.677799] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.677820] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.677843] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.677864] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.677885] [<ffffffc00047cc50>] request_firmware_work_func+0x28/0x54
[ 40.677911] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.677932] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.677956] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.677998] INFO: task kworker/0:2:85 blocked for more than 10 seconds.
[ 40.678014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.678030] kworker/0:2 D ffffffc000086904 0 85 2 0x00000000
[ 40.678076] Workqueue: events request_firmware_work_func
[ 40.678099] Call trace:
[ 40.678120] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.678140] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.678174] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.678193] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.678258] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.678279] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.678299] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.678319] [<ffffffc00047cc50>] request_firmware_work_func+0x28/0x54
[ 40.678340] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.678362] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.678382] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.678402] INFO: task kworker/u4:1:87 blocked for more than 10 seconds.
[ 40.678417] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 40.678434] kworker/u4:1 D ffffffc000086904 0 87 2 0x00000000
[ 40.678486] Workqueue: fwu_workqueue fwu_startup_fw_update_work
[ 40.678509] Call trace:
[ 40.678530] [<ffffffc000086904>] __switch_to+0x74/0x8c
[ 40.678550] [<ffffffc0009eb8a8>] __schedule+0x2e8/0x854
[ 40.678570] [<ffffffc0009ebe3c>] schedule+0x28/0x68
[ 40.678590] [<ffffffc0009e9f68>] schedule_timeout+0x1d4/0x284
[ 40.678611] [<ffffffc0009ec598>] wait_for_common+0xb8/0x15c
[ 40.678631] [<ffffffc0009ec650>] wait_for_completion+0x14/0x1c
[ 40.678651] [<ffffffc00047c97c>] _request_firmware+0xa60/0xcf0
[ 40.678672] [<ffffffc00047cc20>] request_firmware+0x14/0x1c
[ 40.678693] [<ffffffc000635454>] synaptics_fw_updater+0x3e0/0x8b0
[ 40.678713] [<ffffffc000636100>] fwu_startup_fw_update_work+0x24/0x50
[ 40.678734] [<ffffffc0000cf580>] process_one_work+0x13c/0x474
[ 40.678754] [<ffffffc0000cf9f4>] worker_thread+0x13c/0x3c0
[ 40.678774] [<ffffffc0000d70ac>] kthread+0xcc/0xd4
[ 40.767142] wifi_platform_bus_enumerate device present 0
[ 40.767181] failed to power up DHD generic adapter, max retry reached**
It looks like something happened to your wifi card that it can't poweron.
There's really nothing you can do in the software side of things sorry.
You can try replacing the motherboard but that's like 1/3 the cost of the tablet.....
Or send it in to repair, do you still have warranty? I know you rooted your device but who knows right :laugh:
Sorry for the bad news...
If none of those are options you can always just use ethernet.
Click to expand...
Click to collapse
Ok, I know where's the problem. now. Thanks a lot for your help
The tablet should be under warranty, I bought It in Amazon in 01/2015
What can You suggest me about the sw? If I format all again, remove the root and lock the system, could I have some problems with the warranty?
Couold It be possible that the wifi board is the only hw broken? or You are sure about the mother board
mirkorazietti said:
Ok, I know where's the problem. now. Thanks a lot for your help
The tablet should be under warranty, I bought It in Amazon in 01/2015
What can You suggest me about the sw? If I format all again, remove the root and lock the system, could I have some problems with the warranty?
Couold It be possible that the wifi board is the only hw broken? or You are sure about the mother board
Click to expand...
Click to collapse
The thing is that the wifi chip is in the main board so you would have to replace the whole thing.
https://www.ifixit.com/Teardown/Nexus+9+Teardown/31425
Step 11 shows the wifi chip
About getting it ready for warranty... I never had to deal with doing that so my knowledge set on that is low.
Relocking the bootloader is vary risky... Also I think it would show that it was locked by showing a padlock on the boot screen.
I would recommend asking a separate question about what are the steps into sending it to warranty when the bootloader is unlocked.
Are you sure your in warranty? Is warranty 2 years? Because from 2015-01-01 to 2016-10-27 is 1 year and 9 months
If all else fails and you still have warranty you can kill the bootloader and then send it in to warranty.
And say that my wifi stopped working then I rebooted it, it would not turn on again.
But that's last last case scenario... when all hope is lost! When you have nothing to lose...
mirkorazietti said:
Ok, I know where's the problem. now. Thanks a lot for your help
The tablet should be under warranty, I bought It in Amazon in 01/2015
What can You suggest me about the sw? If I format all again, remove the root and lock the system, could I have some problems with the warranty?
Couold It be possible that the wifi board is the only hw broken? or You are sure about the mother board
Click to expand...
Click to collapse
Just flash complete stock with fastboot and relock the bootloader. Theoretically it should be back to stock. They will take it if you relock the bootloader on stock.
My Moto Z XT1650 has been dead for months, last time my pc detected it, i tried running the blankflash file and it gave me the following error, i believe the emmc is currupt. Can anyone help me recover it? i've heard there are ways to boot it from the sd card.
Motorola qboot utility version 3.37
[ 0.000] Opening device: \\.\COM6
[ 0.003] Detecting device
[ 0.007] ...cpu.id = 2375 (0x947)
[ 0.007] ...cpu.sn = 1125564604 (0x4316c0bc)
[ 0.007] Opening singleimage
[ 0.035] Loading package
[ 0.037] ...filename = singleimage.pkg.xml
[ 0.039] Loading programmer
[ 0.041] ...filename = programmer.elf
[ 0.041] Sending programmer
[ 0.117] Handling things over to programmer
[ 0.118] Identifying storage type
[ 0.119] Waiting for firehose to get ready
[ 60.122] Could not determine storage type. Assuming eMMC...
[ 60.122] Identifying CPU version
[ 60.122] Waiting for firehose to get ready
[ 63.136] WriteFile() failed, GetLastError()=0
[120.126] Waiting for firehose to get ready
[123.141] WriteFile() failed, GetLastError()=0
Click to expand...
Click to collapse
I got in same issue
.
.how to unbrick a bricked moto g6 plusThanks to @vache we can now flash a blankflash file to unbrick our devices.
Things you'll need:
Drivers
The blankflash zip
Stock ROM or a custom ROM
How to unbrick:
step 1: extract the blankflash.zip
step 2: run the blank-flash.bat file (or blank-flash.sh if you use Linux). Your phone should boot into fastboot now.
step 3: now you can flash your stock ROM (or TWRP and then a custom ROM).
ahmed.al said:
.
.how to unbrick a bricked moto g6 plusThanks to @vache we can now flash a blankflash file to unbrick our devices.
Things you'll need:
Drivers
The blankflash zip
Stock ROM or a custom ROM
How to unbrick:
step 1: extract the blankflash.zip
step 2: run the blank-flash.bat file (or blank-flash.sh if you use Linux). Your phone should boot into fastboot now.
step 3: now you can flash your stock ROM (or TWRP and then a custom ROM).
Click to expand...
Click to collapse
Dude, but my device does not even enter in Fastboot mode, because I switched the Slots from A to B, does it even work? I'll take the test soon and report here the results. Many thanks to you and everyone who helped to make this Thread
luiz_neto said:
Dude, but my device does not even enter in Fastboot mode, because I switched the Slots from A to B, does it even work? I'll take the test soon and report here the results. Many thanks to you and everyone who helped to make this Thread
Click to expand...
Click to collapse
Well, did it work for you?
ahmed.al said:
Well, did it work for you?
Click to expand...
Click to collapse
I haven't tested it, I'll test it tomorrow and leave the feedback here.
ahmed.al said:
.
.how to unbrick a bricked moto g6 plusThanks to @vache we can now flash a blankflash file to unbrick our devices.
Things you'll need:
Drivers
The blankflash zip
Stock ROM or a custom ROM
How to unbrick:
step 1: extract the blankflash.zip
step 2: run the blank-flash.bat file (or blank-flash.sh if you use Linux). Your phone should boot into fastboot now.
step 3: now you can flash your stock ROM (or TWRP and then a custom ROM).
Click to expand...
Click to collapse
Man, unfortunately it didn't work out. Shows this in CMD:
C:\Users\Neto\Desktop\[GUIA] Como fazer o Unbrick do Moto G6 Plus>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM6
[ 0.000] Detecting device
[ 34.380] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.380] Check qboot_log.txt for more details
[ 34.380] Total time: 34.380s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
C:\Users\Neto\Desktop\[GUIA] Como fazer o Unbrick do Moto G6 Plus>pause
Log File details:
**** Log buffer [000001] 2018-05-14_10:59:17 ****
[ 0.000] Opening device: \\.\COM6
[ 0.000] Detecting device
[ 34.380] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.380] Check qboot_log.txt for more details
[ 34.380] Total time: 34.380s
[ 34.380]
[ 34.380] qboot version 3.86
[ 34.380]
[ 34.380] DEVICE {
[ 34.380] name = "\\.\COM6",
[ 34.380] flags = "0x64",
[ 34.380] addr = "0x62FD64",
[ 34.380] api.bnr = "0xEE2CB0",
[ 34.380] }
[ 34.380]
[ 34.380]
[ 34.380] Backup & Restore {
[ 34.380] num_entries = 0,
[ 34.380] restoring = "false",
[ 34.380] backup_error = "not started",
[ 34.380] restore_error = "not started",
[ 34.380] }
[ 34.380]
luiz_neto said:
Man, unfortunately it didn't work out. Shows this in CMD:
C:\Users\Neto\Desktop\[GUIA] Como fazer o Unbrick do Moto G6 Plus>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM6
[ 0.000] Detecting device
[ 34.380] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.380] Check qboot_log.txt for more details
[ 34.380] Total time: 34.380s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.380] }
[ 34.380]
Click to expand...
Click to collapse
Hmm, try the blankflash a few times - sometimes the blankflashes take several attempts to open a stable sahara connection to your device. Looking at the hex code of the included singleimage.bin, this blankflash is for SDM630 Motorola devices, though I don't know how new or old it is with regards to your bootloader .
Just asking, are you able to power off your device and try booting to the bootloader with the power/volume keys held down? I'm just curious as to how your device won't boot into the bootloader.
@luiz_neto try:
holding the power and volume down button for 2 minutes
an USB with more power
try it again and again and again (it doesn't usually work right away)
ahmed.al said:
@luiz_neto try:
holding the power and volume down button for 2 minutes
an USB with more power
try it again and again and again (it doesn't usually work right away)
Click to expand...
Click to collapse
I do not understand, hold the power button + volume down for 2 minutes and then run the blank-Flash or execute the blank-flash first to do the process? And what do you mean "an USB with more power"? I'm using the device's own USB cable.
---------- Post added at 03:46 PM ---------- Previous post was at 03:36 PM ----------
ahmed.al said:
@luiz_neto try:
holding the power and volume down button for 2 minutes
an USB with more power
try it again and again and again (it doesn't usually work right away)
Click to expand...
Click to collapse
Now i have in cmd:
C:\Users\Hermerson\Desktop\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM3
[ 0.016] Detecting device
[ 0.031] ...cpu.id = 172 (0xac)
[ 0.031] ...cpu.sn = 2641944531 (0x9d78dfd3)
[ 0.031] Opening singleimage
[ 0.172] Loading package
[ 0.203] ...filename = pkg.xml
[ 0.218] Loading programmer
[ 0.246] ...filename = programmer.elf
[ 0.246] Sending programmer
[ 0.324] ReadFile() failed, GetLastError()=0
[ 0.434] ReadFile() failed, GetLastError()=0
[ 0.965] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.965] ERROR: sahara_download()->general error
[ 0.965] Check qboot_log.txt for more details
[ 0.965] Total time: 0.965s
FAILED: qb_flash_singleimage()->sahara_download()->general error
C:\Users\Hermerson\Desktop\blankflash>pause
And in Log file:
**** Log buffer [000001] 2018-05-14_12:43:55 ****
[ 0.000] Opening device: \\.\COM3
[ 0.016] Detecting device
[ 0.016] ...cpu.id = 172 (0xac)
[ 0.016] ...cpu.sn = 2641944531 (0x9d78dfd3)
[ 0.016] Opening singleimage
[ 0.016] Loading package
[ 0.031] ...filename = pkg.xml
[ 0.031] Loading programmer
[ 0.031] ...filename = programmer.elf
[ 0.031] Sending programmer
[ 0.109] ReadFile() failed, GetLastError()=0
[ 0.218] ReadFile() failed, GetLastError()=0
[ 0.782] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.782] ERROR: sahara_download()->general error
[ 0.782] Check qboot_log.txt for more details
[ 0.798] Total time: 0.798s
[ 0.798]
[ 0.798] qboot version 3.86
[ 0.798]
[ 0.798] DEVICE {
[ 0.798] name = "\\.\COM3",
[ 0.798] flags = "0x64",
[ 0.798] addr = "0x22FD74",
[ 0.798] sahara.current_mode = "0",
[ 0.798] api.buffer = "0x16D0020",
[ 0.798] cpu.serial = "2641944531",
[ 0.798] cpu.id = "172",
[ 0.798] cpu.sv_sbl = "1",
[ 0.798] cpu.name = "SDM630",
[ 0.798] storage.type = "eMMC",
[ 0.798] sahara.programmer = "programmer.elf",
[ 0.798] api.bnr = "0x1629140",
[ 0.798] }
[ 0.798]
[ 0.798]
[ 0.798] Backup & Restore {
[ 0.798] num_entries = 0,
[ 0.798] restoring = "false",
[ 0.798] backup_error = "not started",
[ 0.798] restore_error = "not started",
[ 0.798] }
[ 0.798]
Try it again and again with a different pc or usb cable. It took Erfan 20 tries with 4 different PC’s.
Verzonden vanaf mijn iPhone met Tapatalk
luiz_neto said:
<snip>
Now i have in cmd:
C:\Users\Hermerson\Desktop\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM3
[ 0.016] Detecting device
[ 0.031] ...cpu.id = 172 (0xac)
[ 0.031] ...cpu.sn = 2641944531 (0x9d78dfd3)
[ 0.031] Opening singleimage
[ 0.172] Loading package
[ 0.203] ...filename = pkg.xml
[ 0.218] Loading programmer
[ 0.246] ...filename = programmer.elf
[ 0.246] Sending programmer
[ 0.324] ReadFile() failed, GetLastError()=0
[ 0.434] ReadFile() failed, GetLastError()=0
[ 0.965] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.965] ERROR: sahara_download()->general error
[ 0.965] Check qboot_log.txt for more details
[ 0.965] Total time: 0.965s
FAILED: <snip>
[ 0.798]
Click to expand...
Click to collapse
Hmm, so the blankflash does make contact with your device, establishes a connection and sends over the programmer to verify your device, but the programmer reports an incorrect response...
What happens if you try the blankflash again, do you get a different response? Seems you're getting closer. The power and volume key trick has been suggested: (credit to https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 )
Or any other error, then its little tricky to solve this.
Follow the below steps.
1. Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.
4. keep trying step 3 unless you dont see below logs.
Click to expand...
Click to collapse
Having a look in the Pixel forums (also with a A/B partition system), users that have experienced similar issues a couple of years ago had to have their device replaced. I'm hoping we can get your device working without having to pay for a repair... https://forum.xda-developers.com/pixel-xl/help/pixelxl-bricked-t3517310
echo92 said:
Hmm, so the blankflash does make contact with your device, establishes a connection and sends over the programmer to verify your device, but the programmer reports an incorrect response...
What happens if you try the blankflash again, do you get a different response? Seems you're getting closer. The power and volume key trick has been suggested: (credit to https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 )
Having a look in the Pixel forums (also with a A/B partition system), users that have experienced similar issues a couple of years ago had to have their device replaced. I'm hoping we can get your device working without having to pay for a repair... https://forum.xda-developers.com/pixel-xl/help/pixelxl-bricked-t3517310
Click to expand...
Click to collapse
Doesn't work, i'll wait a update of blank-flash file.
luiz_neto said:
Doesn't work, i'll wait a update of blank-flash file.
Click to expand...
Click to collapse
You might be waiting a long time - those blankflashes are usually a leak from Motorola internal development. As such, we don't have access to new files and we're very lucky to get the ones we have. As far as I understand, we can't make them ourselves, as the blankflashes are signed by Motorola, and attempts to change the blankflash may break the signature (though this is old, I would not be surprised if the same still holds: https://forum.xda-developers.com/showpost.php?p=62191317&postcount=2112 )
Unless there's an updated SDM630 blankflash for the G6 Plus (or the X4?), you may have to consider a replacement or service repair.
ahmed.al said:
Try it again and again with a different pc or usb cable. It took Erfan 20 tries with 4 different PC’s.
Verzonden vanaf mijn iPhone met Tapatalk
Click to expand...
Click to collapse
Did you have the same problem as me? Had your moto G6 bricked too?
---------- Post added at 02:46 PM ---------- Previous post was at 02:36 PM ----------
echo92 said:
You might be waiting a long time - those blankflashes are usually a leak from Motorola internal development. As such, we don't have access to new files and we're very lucky to get the ones we have. As far as I understand, we can't make them ourselves, as the blankflashes are signed by Motorola, and attempts to change the blankflash may break the signature (though this is old, I would not be surprised if the same still holds: https://forum.xda-developers.com/showpost.php?p=62191317&postcount=2112 )
Unless there's an updated SDM630 blankflash for the G6 Plus (or the X4?), you may have to consider a replacement or service repair.
Click to expand...
Click to collapse
Since the Moto X4 has the same Chipset as Moto G6, can I use the same Blanck flash of the X4 on the G6? Since the Chipset of the two is the SDM630.
@luiz_neto there's nothing wrong with the blankflash. As mentioned earlier you need to try it a ****load of times (this is common). Using the moto X4's blankflash will change nothing.
luiz_neto said:
Did you have the same problem as me? Had your moto G6 bricked too?
---------- Post added at 02:46 PM ---------- Previous post was at 02:36 PM ----------
Since the Moto X4 has the same Chipset as Moto G6, can I use the same Blanck flash of the X4 on the G6? Since the Chipset of the two is the SDM630.
Click to expand...
Click to collapse
In theory, you could use the X4 blankflash - but the bootloaders would ideally have to be the same/similar to reduce the chance of any issues later on. That is if there even is an X4 blankflash...
If ahmed.al's and my suggestions to try the blankflash a few more times doesn't work, then it looks like you may have to talk to Motorola/your retailer and see if they'd be willing to repair/replace it. However, with an unlocked bootloader, I'm not sure if they will charge you. I don't know of a way to change back to the previous bootloader slot without fastboot.
luiz_neto said:
Did you have the same problem as me? Had your moto G6 bricked too?
---------- Post added at 02:46 PM ---------- Previous post was at 02:36 PM ----------
Since the Moto X4 has the same Chipset as Moto G6, can I use the same Blanck flash of the X4 on the G6? Since the Chipset of the two is the SDM630.
Click to expand...
Click to collapse
have you tried with linux? maybe you can get a more stable usb connection
jekyll86 said:
have you tried with linux? maybe you can get a more stable usb connection
Click to expand...
Click to collapse
Not yet, just run the blank-flash.sh file on Linux???
luiz_neto said:
Not yet, just run the blank-flash.sh file on Linux???
Click to expand...
Click to collapse
yes, give it a try
jekyll86 said:
yes, give it a try
Click to expand...
Click to collapse
nothing happens dude. :crying:
luiz_neto said:
nothing happens dude. :crying:
Click to expand...
Click to collapse
What error do you see?
Hey all. Ran into a bit of an issue. My Motorola Edge Plus (XT2061-3) is stuck in EDL mode. I have managed to locate the blankflash file for this device. When trying to flash it, this is the errors I get. (Got this blankflash of Lolinet under Burton > Blankflash)
"Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM3
[ 0.008] Detecting device
[ 0.010] ...cpu.id = 195 (0xc3)
[ 0.010] ...cpu.sn = 621922316 (0x2511c80c)
[ 0.010] Opening singleimage
[ 0.020] Loading package
[ 0.022] ...filename = pkg.xml
[ 0.024] Loading programmer
[ 0.024] ...filename = programmer.elf
[ 0.024] Sending programmer
[ 0.089] ReadFile() failed, GetLastError()=0
[ 0.454] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.455] ERROR: sahara_download()->general error
[ 0.455] Check qboot_log.txt for more details
[ 0.455] Total time: 0.456s
FAILED: qb_flash_singleimage()->sahara_download()->general error
blankflash_from_QPBS30.188-48-3 (1)>pause
Press any key to continue . . ."
From the log file:
"
[ 0.000] Opening device: \\.\COM6
[ 0.001] Detecting device
[ 0.003] ...cpu.id = 195 (0xc3)
[ 0.003] ...cpu.sn = 621922316 (0x2511c80c)
[ 0.003] Opening singleimage
[ 0.013] Loading package
[ 0.016] ...filename = pkg.xml
[ 0.017] Loading programmer
[ 0.018] ...filename = programmer.elf
[ 0.018] Sending programmer
[ 0.088] ReadFile() failed, GetLastError()=0
[ 0.335] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.336] ERROR: sahara_download()->general error
[ 0.336] Check qboot_log.txt for more details
[ 0.336] Total time: 0.338s
[ 0.336]
[ 0.336] qboot version 3.86
[ 0.336]
[ 0.336] DEVICE {
[ 0.336] name = "\\.\COM6",
[ 0.336] flags = "0x64",
[ 0.336] addr = "0x62FD54",
[ 0.336] sahara.current_mode = "0",
[ 0.336] api.buffer = "0x2A5A020",
[ 0.336] cpu.serial = "621922316",
[ 0.336] cpu.id = "195",
[ 0.336] cpu.sv_sbl = "1",
[ 0.336] cpu.name = "SM8250",
[ 0.336] storage.type = "UFS",
[ 0.336] sahara.programmer = "programmer.elf",
[ 0.336] api.bnr = "0x2993FE0",
[ 0.336] }
[ 0.336]
[ 0.336]
[ 0.336] Backup & Restore {
[ 0.336] num_entries = 0,
[ 0.336] restoring = "false",
[ 0.336] backup_error = "not started",
[ 0.336] restore_error = "not started",
[ 0.336] }
[ 0.336]
"
It tries to send "programmer.elf" and "pkg.xml". The blankflash package does not contain those files. I have all the correct drivers. The phone shows up as "Qualcomm HS-USB QDLoader 9008" in Device Manager.
Any help is greatly appreciated. I've been stuck on this for quite a while.
latest blank flash for android 11
download here
I just brought my edge back to life. hope it helps. remember to update gpt.bin of ur own version
jackeylei said:
latest blank flash for android 11
download here
I just brought my edge back to life. hope it helps. remember to update gpt.bin of ur own version
Click to expand...
Click to collapse
It worked! Thank you so much for providing this.
I have the same problem on moto edge 20 pro any suggestions thank you very much
I have the same problem on moto edge foto here https://ibb.co/7Vz3vBg help me plss
jackeylei said:
último flash en blanco para android 11
descarga aquí
Acabo de traer mi borde de vuelta a la vida. Espero eso ayude. recuerda actualizar gpt.bin de tu propia versión
Click to expand...
Click to collapse
¿Puede indicar los pasos para actualizar gpt.bin?
marcoryu said:
¿Puede indicar los pasos para actualizar
Click to expand...
Click to collapse
There are some tutorial posts in this forum, just search for posts related to blank flash and understand how to use.
My general suggestion is to "extract some files from the firmware and put them into the singleimage file in the blank flash folder".
jackeylei said:
There are some tutorial posts in this forum, just search for posts related to blank flash and understand how to use.
My general suggestion is to "extract some files from the firmware and put them into the singleimage file in the blank flash folder".
Click to expand...
Click to collapse
exactly which firmware files should i move to the blankflash folder
AREALE said:
I have the same problem on moto edge foto here https://ibb.co/7Vz3vBg help me plss
Click to expand...
Click to collapse
Just keep trying
marcoryu said:
exactly which firmware files should i move to the blankflash folder
Click to expand...
Click to collapse
1. You have to determine which firmware ur phone is on when bricked then download the firmware from here and the right blankflash file here
2. Get gpt.bin from the firmware, and put it into singleimage file.
3. Flash
Refer to this post:
[BLANKFLASH] Moto G7 XT1962-5 RIVER RETEU 9.0 PPO29.80-66
I have built a blankflash that revived my XT1962-5, which had firmware PPO29.80-66 before hardbricking it. Maybe it is useful to others: https://www27.zippyshare.com/v/lL4eo830/file.html The blankflash is based on this firmware...
forum.xda-developers.com
good morning friend, could you help me create the blank flash to be able to recover my device, thank you very much for answering and for your help
jackeylei said:
1. You have to determine which firmware ur phone is on when bricked then download the firmware from here and the right blankflash file here
2. Get gpt.bin from the firmware, and put it into singleimage file.
3. Flash
Refer to this post:
[BLANKFLASH] Moto G7 XT1962-5 RIVER RETEU 9.0 PPO29.80-66
I have built a blankflash that revived my XT1962-5, which had firmware PPO29.80-66 before hardbricking it. Maybe it is useful to others: https://www27.zippyshare.com/v/lL4eo830/file.html The blankflash is based on this firmware...
forum.xda-developers.com
Click to expand...
Click to collapse
good morning friend, could you help me create the blank flash to be able to recover my device, thank you very much for answering and for your help
marcoryu said:
good morning friend, could you help me create the blank flash to be able to recover my device, thank you very much for answering and for your it
Click to expand...
Click to collapse
When the phone bricked, is it on Android 11 or 10? When it happened?
jackeylei said:
When the phone bricked, is it on Android 11 or 10? When it happened?
Click to expand...
Click to collapse
Android 11 https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in this version it was when it was blocked
marcoryu said:
Android 11 https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in this version it was when it was blocke
Click to expand...
Click to collapse
windows recognizes it as Qulcomm hs-usb Dloader 9008
Have u tried this blankflash? if yes, what's the error msg?
I assume that you already know how to use blankflash. otherwise, it is difficult for me to explain.
jackeylei said:
Have u tried this blankflash? if yes, what's the error msg?
I assume that you already know how to use blankflash. otherwise, it is difficult for me to explain.
Click to expand...
Click to collapse
Here I attach the blankflash file which I update the gpt.bin provided in your firmware. Try the original blankflash first, if failed, try this one.
jackeylei said:
Here I attach the blankflash file which I update the gpt.bin provided in your firmware. Try the original blankflash first, if failed, try this one.
Click to expand...
Click to collapse
hello mate and tried the blank flash file of version 19.50 and the one you sent me and both give me this error
marcoryu said:
hello mate and tried the blank flash file of version 19.50 and the one you sent me and both give me this error
Click to expand...
Click to collapse
Try , keep trying.
Based on my personal understanding, u have only one chance to blank flash ur phone during the connection with pc.
Therefore after u plug in the USB, u should keep running blank-flash command until the real results display.
Try.
Check others posts about blank flash.