Guys, my motorola z play was updating and unfortunately was not loading and died kk
When I connect it on the charger, it keeps the LED next to the front camera flashing and only, also when I connect it on the pc it appears `QUSB_BULK`
The few information I've known in a group that can be a hard brick
Can someone help me and tell me where to start?
Thank you all
bruno-prata13 said:
Guys, my motorola z play was updating and unfortunately was not loading and died kk
When I connect it on the charger, it keeps the LED next to the front camera flashing and only, also when I connect it on the pc it appears `QUSB_BULK`
The few information I've known in a group that can be a hard brick
Can someone help me and tell me where to start?
Thank you all
Click to expand...
Click to collapse
What is your software channel ?
jatinkhatri said:
What is your software channel ?
Click to expand...
Click to collapse
I do not remember
I install upgrading it from marshmallow to nougat, it was bought in brazil
bruno-prata13 said:
I do not remember
I install upgrading it from marshmallow to nougat, it was bought in brazil
Click to expand...
Click to collapse
I think you have to install stock room from following link ( it's not flashable zip , you have to flash it through adb )
https://mirrors.lolinet.com/firmware/moto/addison/official/RETBR/
Mobile is not found by cmd
I did a moto x and g procedure so I need a file called `BlankFlash` from the moto z play.
I already researched and nothing until now ....
Look at this thread
https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
And download the nougat firmware, that one includes blankflash files.
Just double tap de blankflash.bat file in blankflash folder, if match with your last versión of the bootloader, it will boot to fastboot. Then flash the firmware with the flashall.bat file in root folder.
GuzXT said:
Look at this thread
https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
And download the nougat firmware, that one includes blankflash files.
Just double tap de blankflash.bat file in blankflash folder, if match with your last versión of the bootloader, it will boot to fastboot. Then flash the firmware with the flashall.bat file in root folder.
Click to expand...
Click to collapse
This error appears in the log
**** Log buffer [000001] 2017-05-19_17: 49: 32 ****
[0.000] Opening device: \\. \ COM3
[0.002] Detecting device
[4.013] ERROR: sahara_greet_device () -> change_mode () -> do_hello () -> IO error
[4.019] Check qboot_log.txt for more details
[4.023] Total time: 4.025s
[4.025]
[4.025] qboot version 3.40
[4.025]
[4.025] DEVICE {
[4.025] name = "\\. \ COM3",
[4.025] flags = "0x64",
[4.025] addr = "0x61FE5C",
[4.025] api.bnr = "0x832930",
[4.025]}
[4.025]
[4.025]
[4.025] Backup & Restore {
[4.025] num_entries = 0,
[4.025] restoring = "false",
[4.025] backup_error = "not started",
[4.025] restore_error = "not started",
[4.025]}
[4.025]
**** Log buffer [000001] 2017-05-19_17: 54: 12 ****
[0.000] Opening device: \\. \ COM5
[0.002] Detecting device
[4.012] ERROR: sahara_greet_device () -> change_mode () -> do_hello () -> IO error
[4.015] Check qboot_log.txt for more details
[4.016] Total time: 4.017s
[4.018]
[4.018] qboot version 3.40
[4.018]
[4.018] DEVICE {
[4.018] name = "\\. \ COM5",
[4.018] flags = "0x64",
[4.018] addr = "0x61FE5C",
[4.018] api.bnr = "0xB12930",
[4.018]}
[4.018]
[4.018]
[4.018] Backup & Restore {
[4.018] num_entries = 0,
[4.018] restoring = "false",
[4.018] backup_error = "not started",
[4.018] restore_error = "not started",
[4.018]}
[4.018]
bruno-prata13 said:
This error appears in the log
**** Log buffer [000001] 2017-05-19_17: 49: 32 ****
[0.000] Opening device: \. \ COM3
[0.002] Detecting device
[4.013] ERROR: sahara_greet_device () -> change_mode () -> do_hello () -> IO error
[4.019] Check qboot_log.txt for more details
[4.023] Total time: 4.025s
[4.025]
[4.025] qboot version 3.40
[4.025]
[4.025] DEVICE {
[4.025] name = "\. \ COM3",
[4.025] flags = "0x64",
[4.025] addr = "0x61FE5C",
[4.025] api.bnr = "0x832930",
[4.025]}
[4.025]
[4.025]
[4.025] Backup & Restore {
[4.025] num_entries = 0,
[4.025] restoring = "false",
[4.025] backup_error = "not started",
[4.025] restore_error = "not started",
[4.025]}
[4.025]
**** Log buffer [000001] 2017-05-19_17: 54: 12 ****
[0.000] Opening device: \. \ COM5
[0.002] Detecting device
[4.012] ERROR: sahara_greet_device () -> change_mode () -> do_hello () -> IO error
[4.015] Check qboot_log.txt for more details
[4.016] Total time: 4.017s
[4.018]
[4.018] qboot version 3.40
[4.018]
[4.018] DEVICE {
[4.018] name = "\. \ COM5",
[4.018] flags = "0x64",
[4.018] addr = "0x61FE5C",
[4.018] api.bnr = "0xB12930",
[4.018]}
[4.018]
[4.018]
[4.018] Backup & Restore {
[4.018] num_entries = 0,
[4.018] restoring = "false",
[4.018] backup_error = "not started",
[4.018] restore_error = "not started",
[4.018]}
[4.018]
Click to expand...
Click to collapse
If the last OTA was april security, then you need to wait for most recent firmware. The april patch upgrade bootloader, so, you need blankflash of April firmware or later.
If the OTA wasn't the april patch, Try again, sometimes it's hard to detect the device.
GuzXT said:
If the last OTA was april security, then you need to wait for most recent firmware. The april patch upgrade bootloader, so, you need blankflash of April firmware or later.
If the OTA wasn't the april patch, Try again, sometimes it's hard to detect the device.
Click to expand...
Click to collapse
I need the blank flash of april firmware or later, would not you have it available?
bruno-prata13 said:
I need the blank flash of april firmware or later, would not you have it available?
Click to expand...
Click to collapse
My z play is now bricked and I'm also looking for the blankfile...
Sorry that page is for moto z NOT moto z play
https://forum.xda-developers.com/mo...-to-unbrick-moto-z-hardbricked-t3590133/page2
GuzXT said:
If the last OTA was april security, then you need to wait for most recent firmware. The april patch upgrade bootloader, so, you need blankflash of April firmware or later.
If the OTA wasn't the april patch, Try again, sometimes it's hard to detect the device.
Click to expand...
Click to collapse
I left it in full brick, I was tunneling MM and Nougat down with the script Downgrade and coming up with adb sideload and it happened when installing Nougat again.
It should be mentioned that it was with the April patch, the downgrade of a patch MM, restart and install the apps as always and personalize, then added in December, reboot and reinstall No but end instead of restart, I chose to start The bootloadder and alli brickeo.
Everything only with the charger open, no root or any modification, now no garment or anything and if I connect it to the charger of the PC only the charge led flashes, when I connect it the PC recognizes me as ¨Qualcomm hs-usb qdloader 9008 COM5¨ has used and Blankflash for the bike does not finish the process and the 1,2 and 3 dce XDA and neither.
If someone can pass me the Blankflash will thank you, please.
I arrived here:
Blur_Version.25.211.10.addison.retail.es.ES - Security April 2017
NPN 25.137-24-1-9
Download here:
Blur_Version.24.221.12.addison.retail.es.ES - Security November 2016
MPNS24.104-44-10
Install this:
Blur_Version.24.231.19.addison.retail.es.ES - Security December 2016
MPNS24.104-44-16
Then bricke it at the end of the process:
Blur_Version.25.21.2.addison.retail.en.US - Android 7.0 Nougat January 2017
NPN25.137-15.2
By the way a colleague Ali Guzman of the group facebook my pass this compilation NPN25.137-24-1 with the included blankflash but in the middle of the process notifies me of package error.
lenovo-forum.ru page
PLEASE ALL GO TO THIS LINK
Http://lenovo-forums.ru/topic/20594-...comment-550611
WHILE MORE OF US SEE AND LEN LIKE THE COMMENT OF
* VVizard @
SAGE
THEY COULD HELP US CHECK IT
[GUIDE] Unbrick MOTO Z Play.... work in progress! (not working yet)
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Related
**** Log buffer [000001] 2018-05-27_19:15:58 ****
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.002] ...cpu.id = 79 (0x4f)
[ 0.002] ...cpu.sn = 3414389940 (0xcb8374b4)
[ 0.002] Opening singleimage
[ 0.339] Loading package
[ 0.343] ...filename = singleimage.pkg.xml
[ 0.345] Loading programmer
[ 0.347] ...filename = programmer.mbn
[ 0.347] Sending programmer
[ 1.378] ERROR: sahara_download()->IO error
[ 1.378] Check qboot_log.txt for more details
[ 1.378] Total time: 1.378s
[ 1.378]
[ 1.378] qboot version 3.40
[ 1.378]
[ 1.378] DEVICE {
[ 1.378] name = "/dev/ttyUSB0",
[ 1.378] flags = "0x60",
[ 1.378] addr = "0x41C63D78",
[ 1.378] serial_nix.device_pathname = "/sys/bus/usb/devices/2-1.3/2-1.3:1.0/ttyUSB0",
[ 1.378] sahara.current_mode = "0",
[ 1.378] api.buffer = "0x7FE2D204C010",
[ 1.378] cpu.serial = "3414389940",
[ 1.378] cpu.id = "79",
[ 1.378] cpu.sv_sbl = "1",
[ 1.378] cpu.name = "MSM8937",
[ 1.378] storage.type = "eMMC",
[ 1.378] sahara.programmer = "programmer.mbn",
[ 1.378] api.bnr = "0xC5B7F0",
[ 1.378] }
[ 1.378]
[ 1.378]
[ 1.378] Backup & Restore {
[ 1.378] num_entries = 0,
[ 1.378] restoring = "false",
[ 1.378] backup_error = "not started",
[ 1.378] restore_error = "not started",
[ 1.378] }
[ 1.378]
HI! I flashed the wrong firmware in my Moto G5 Cedric, using the Fastboot, and now my phone is hard-bricked. (sorry for my bad english). I tryed some methods... This is the blank-flash log:
Code:
[ 0.000] Opening device: \\.\COM4
[180.350] Detecting device
[218.959] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[218.959] Check qboot_log.txt for more details
[218.959] Total time: 218.979s
[218.980]
[218.980] qboot version 3.40
[218.980]
[218.980] DEVICE {
[218.980] name = "\\.\COM4",
[218.980] flags = "0x64",
[218.980] addr = "0x61FE5C",
[218.980] api.bnr = "0x762E30",
[218.980] }
[218.980]
[218.980]
[218.980] Backup & Restore {
[218.980] num_entries = 0,
[218.980] restoring = "false",
[218.980] backup_error = "not started",
[218.980] restore_error = "not started",
[218.980] }
[218.980]
And i saw a method with something called QFIL (best pro name i ever seen xD) and yeah.. fail. Here is the log:
Code:
Process Index:0
Programmer Path:C:\Users\OurNation\Desktop\8675_W00\prog_emmc_firehose_8936.mbn
Image Search Path:C:\Users\OurNation\Desktop\8675_W00
Please select the XML file
Start Download
Program Path:C:\Users\OurNation\Desktop\8675_W00\prog_emmc_firehose_8936.mbn
COM Port number:4
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
I can't do anything to revive this phone...........
Help me pls........
I heard about a MicroSD method, but i can't see Qualcomm MMC Storage USB Device on the Device manager so i can't flash the mmcblk0p.img.
There is no blank flash for this device
Follow the guide - without a JTAG its the only known way to unbrick this device
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
TheFixItMan said:
There is no blank flash for this device
Follow the guide - without a JTAG its the only known way to unbrick this device
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Click to expand...
Click to collapse
it works xD i have a 32gb sdhc and in linux Mint shows as ,,32.3" after format, and with 'sudo fdisk -l' it's 30.3, that is smaller then 31.3 but works.
Hmmm...Does the device boot from the sd? Is this why it must be formatted?
Hi,
Sorry to trouble....
I have so far been able to get qboot communicating with the QDloader,
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 79 (0x4f)
[ -0.000] ...cpu.sn = 3471194414 (0xcee6392e)
[ 0.008] Opening singleimage
[ 0.054] Loading package
[ 0.054] Failed identify board. Wrong package?
[ 0.062] ERROR: error loading package
[ 0.062] Check qboot_log.txt for more details
[ 0.062] Total time: 0.070s
FAILED: qb_flash_singleimage()->error loading package
-----
[ 0.062] DEVICE {
[ 0.062] name = "\\.\COM3",
[ 0.062] flags = "0x64",
[ 0.062] addr = "0x61FE4C",
[ 0.062] sahara.current_mode = "3",
[ 0.062] api.buffer = "0xF01020",
[ 0.062] cpu.serial = "3471194414",
[ 0.062] cpu.id = "79",
[ 0.062] cpu.sv_sbl = "1",
[ 0.062] api.bnr = "0x6E1D70",
[ 0.062] }
-----
But i dont seem to have a singleimage.bin to match ?
i have tried the 64 page XT179x thread, but cant seem to find the working singleimage.bin file to try with qboot ?
https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150/page1
Also my version of qboot is 3.4 and 3.8 is being discussed
Any ideas ? it seems i need:
- a 'blank-flash' for my xt1794 / G5S, arounf : 5MB in size
- a newer version of qboot
I have tried the installation onto an SD-card, but zero joy on that approach at the moment
HELP
ZT
Hi!hello, did you find the file?
Hello, after almost having a heart attack with my Razer 2 showing the qusb_bulk message, I decided to fix my moto z2 with the same message. Did what almost all good threads say but while running the blankfast (blankflash_from_NDX26.183-15_17) it keeps showing the same error, I made sure I don't have moto drivers installed, and uninstalled the qualcomm drivers once. And it keeps showing.
If anyone had the same error, and can help, I'll be pretty grateful.
**** Log buffer [000001] 2022-12-21_16:42:26 ****
[ 0.000] Opening device: \\.\COM6
[ 0.000] ERROR: device_open()->error opening device
[ 0.001] Check qboot_log.txt for more details
[ 0.001] Total time: 0.002s
[ 0.001]
[ 0.001] qboot version 3.85
[ 0.001]
[ 0.001] DEVICE {
[ 0.001] name = "\\.\COM6",
[ 0.001] flags = "0x60",
[ 0.001] addr = "0x62FD54",
[ 0.001] api.bnr = "0xE22FE8",
[ 0.001] }
[ 0.001]
[ 0.001]
[ 0.001] Backup & Restore {
[ 0.001] num_entries = 0,
[ 0.001] restoring = "false",
[ 0.001] backup_error = "not started",
[ 0.001] restore_error = "not started",
[ 0.001] }
[ 0.001]
Did anyone manage to generate a SingleImage htc file for flashing via blankflash program (for motorola )? To my strangeness, I downloaded the BlankFlash program for Motorola with the same processor as the HTC M9 model, installed the drivers (Qalcomm Emergency 9008 Download Model for qhusb_bulk Device) and communicates with the computer . Any idea how to fix the bootlader for this model?
**** Log buffer [000001] 2023-02-06_15:00:07 ****
[ -0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 2368 (0x940)
[ 0.005] ...cpu.sn = 17772425 (0x10f2f89)
[ 0.005] Opening singleimage
[ 0.006] ERROR: error opening singleimage
[ 0.006] Check qboot_log.txt for more details
[ 0.007] Total time: 0.008s
[ 0.008]
[ 0.008] qboot version 3.86
[ 0.008]
[ 0.008] DEVICE {
[ 0.008] name = "\\.\COM3",
[ 0.008] flags = "0x64",
[ 0.008] addr = "0x62FD54",
[ 0.008] sahara.current_mode = "3",
[ 0.008] api.buffer = "0x2AF0020",
[ 0.008] cpu.serial = "17772425",
[ 0.008] cpu.id = "2368",
[ 0.008] cpu.sv_sbl = "0",
[ 0.008] api.bnr = "0x1092D88",
[ 0.008] }
[ 0.008]
[ 0.008]
[ 0.008] Backup & Restore {
[ 0.008] num_entries = 0,
[ 0.008] restoring = "false",
[ 0.008] backup_error = "not started",
[ 0.008] restore_error = "not started",
[ 0.008] }
[ 0.008]
blankflash.zip | by erfanoabdi for Moto G6 Plus
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
please delete singleimage,img before run
Or anyone have mmcblk0.img file from htc m9 ?
Maybe this : https://www.hovatek.com/forum/thread-19721.html