Good night ... I have a Moto g2 lte xt1078. it does not start, no fastboot, no booting... they tried to install lolipop and did root procedure. already tried several tutorials, as the blankflash, but without results. I removed the battery several times; Full battery; when connected to PC without battery the LED flashes once; all drivers installed. current driver Qualcomm HS-USB QDloader 9008. The result of the blankflash this in content below.
help please.
sorry bad english.
C:\Users\Claus\Desktop\blankflash_lollipop>.\qboot.exe blank-flash
opening device: \\.\COM9
OKAY [ 0.002s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x7B72F04
...chip-id = 0x805 (MSM8926)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer_8926.mbn
...singleimage = singleimage_8926.bin
OKAY [ 0.005s]
validating files
OKAY [ 0.001s]
switching to download mode
OKAY [ 0.002s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
OKAY [ 0.012s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
C:\Users\Claus\Desktop\blankflash_lollipop>pause
Pressione qualquer tecla para continuar. . .
tested: MBM-CI 4.3; 4.4.2; 4.4.4; 5.0.
It's the same error:
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
motherboard is dead.
Moto G 2014 xt1068/xt1069/xt1078
Is there any tool that can get the Moto G 2014 xt1068 / xt1069
/ Xt1078 hardblick in the development? if not I humbly ask that the group managed to get the g1 moto hardblick can also take other cell line motorola umm thanks to @ilikered for its beautiful job with the bike g1 parabens it stays that way and that can help us not only to me but to several people who are in the same situation , thanks
Method tested and used with succes by @kalyansundhar on xt1795
Thanks for his detailed tutorial for unbrick the phones!
https://forum.xda-developers.com/showpost.php?p=76747247&postcount=258
Also please read the post's after that before posting your question
can be already answered to it
Tutorial for using Windows 7(language Brasilian & English, Thanks to @caikehenrique)
becouse flashing process can be done on Windows too
Thanks to @Thi_os
i made a video presentation to help the users wich dont
know how to do it
video for users with windows OS
video for extracting the.tar.gz archive in windows
sorry for my english
Oreo 8.1 mmcblk0.img thanks to @meltbanana
Nougat 7.1 mmncblk0.img xt1794(102-49-8) with md5-code by @hanshu43
Nougat 7.1 mmncblk0.img xt1795 with md5-code and tool to verify it
Thanks to @echo92 for providing md5-code of a working file
Tips & tricks!
The BEST method to flash the sdcard with mmcbk0.img file is to use LINUX!
Windows user have no need to install Linux in pc, you can run Linux from a bootable usb-stik or pendrive by 8Gb at least
0)put the moto g5s in wall charger till finish flashing sdcard to be charged on boot test!
1) run linux, preferable cinnamon or mate versions of linux Mint or Ubuntu(for ubuntu dont use LTS version)
2)insert the sdcard in pc or card reader and opend "Disks" apk
3)in "Disks"apk select sdcard and you will see the sdcard partitions
4) press "-" to delete the partition(delete al partitions if are more than one)
5)press "+" to create a new one and name it mmcblk0, set FAT(FAT32) file format and press "CREATE"
6)press "Play"button to mount the sdcard, look to see what path sdcard have(/dev/sd??) the and close the "Disks"apk
7)go to Desktop, opend "Computer" and navigate to the location when the img file is extracted(mmcblk0.img)
8)opend the window where img file is with root(right click on window and select "opend as root")
9)in root window opend the Terminal(right click on window and select "opend terminal")
no need to type "su" in terminal, it have already root
10)type in terminal the comand writed below and dont forget to eliminate that "1" from the sdcard path,
that "1"can make the differnce betwen phone boot or not!!!!!
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal aply that comand:
dd bs=4M if=mmcblk0.img of=/dev/sdb status=progress oflag=sync
-if your sdcard is seen like " /dev/mmcblk0p1"
in terminal aply that comand:
dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
and flashing process should start
when it finish, test the sdcard in phone and it should boot!
IF you get an size error of the sdcard in terminal you have to change the sdcard and try again!
This is the last edit of sdcard flashing tutorial, i cant make better than that!!
Thankyou!
thanks bro! i have my device hard bricked,but device manager detects it as "quectel QDLoader 9008" but not Qulacomm dloader husb 9008 now what to do ?
pardhav said:
thanks bro! i have my device hard bricked,but device manager detects it as "quectel QDLoader 9008" but not Qulacomm dloader husb 9008 now what to do ?
Click to expand...
Click to collapse
i resume you flashed a wrong image files.
did you try to use blankflash with montana image files?
:/
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
Marceloaps said:
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
Click to expand...
Click to collapse
Thankyou very much for your report!
can you provide the qboot_log.txt saved to chech it?
also can you try the singleimage.bin atached?
rename it from singleimage.bin.txt to singleimage.bin(delete .txt from name)
Thankyou!
here
**** Log buffer [000001] 2018-03-19_14:40:38 ****
[ -0.000] Opening device: \\.\COM3
[ -0.000] Detecting device
[ 4.032] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.032] Check qboot_log.txt for more details
[ 4.032] Total time: 4.032s
[ 4.032]
[ 4.032] qboot version 3.40
[ 4.032]
[ 4.032] DEVICE {
[ 4.032] name = "\\.\COM3",
[ 4.032] flags = "0x64",
[ 4.032] addr = "0x22FE6C",
[ 4.032] api.bnr = "0x3A2FE8",
[ 4.032] }
[ 4.032]
[ 4.032]
[ 4.032] Backup & Restore {
[ 4.032] num_entries = 0,
[ 4.032] restoring = "false",
[ 4.032] backup_error = "not started",
[ 4.032] restore_error = "not started",
[ 4.032] }
[ 4.032]
**** Log buffer [000001] 2018-03-19_14:41:06 ****
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.049] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.049] Check qboot_log.txt for more details
[ 4.049] Total time: 4.049s
[ 4.049]
[ 4.049] qboot version 3.40
[ 4.049]
[ 4.049] DEVICE {
[ 4.049] name = "\\.\COM3",
[ 4.049] flags = "0x64",
[ 4.049] addr = "0x22FE6C",
[ 4.049] api.bnr = "0x372FE8",
[ 4.049] }
[ 4.049]
[ 4.049]
[ 4.049] Backup & Restore {
[ 4.049] num_entries = 0,
[ 4.049] restoring = "false",
[ 4.049] backup_error = "not started",
[ 4.049] restore_error = "not started",
[ 4.049] }
[ 4.049]
**** Log buffer [000001] 2018-03-19_14:51:30 ****
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.047] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.047] Check qboot_log.txt for more details
[ 4.047] Total time: 4.047s
[ 4.047]
[ 4.047] qboot version 3.40
[ 4.047]
[ 4.047] DEVICE {
[ 4.047] name = "\\.\COM3",
[ 4.047] flags = "0x64",
[ 4.047] addr = "0x22FE6C",
[ 4.047] api.bnr = "0x7D2FE8",
[ 4.047] }
[ 4.047]
[ 4.047]
[ 4.047] Backup & Restore {
[ 4.047] num_entries = 0,
[ 4.047] restoring = "false",
[ 4.047] backup_error = "not started",
[ 4.047] restore_error = "not started",
[ 4.047] }
[ 4.047]
**** Log buffer [000001] 2018-03-19_15:11:44 ****
[ -0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.007] Total time: 4.008s
[ 4.051]
[ 4.051] qboot version 3.40
[ 4.051]
[ 4.051] DEVICE {
[ 4.051] name = "\\.\COM3",
[ 4.051] flags = "0x64",
[ 4.051] addr = "0x22FE6C",
[ 4.051] api.bnr = "0x582FE8",
[ 4.051] }
[ 4.051]
[ 4.051]
[ 4.051] Backup & Restore {
[ 4.051] num_entries = 0,
[ 4.051] restoring = "false",
[ 4.051] backup_error = "not started",
[ 4.051] restore_error = "not started",
[ 4.051] }
[ 4.051]
Marceloaps said:
**** Log buffer [000001] 2018-03-19_14:40:38 ****
[ 4.051] }
[ 4.051]
Click to expand...
Click to collapse
Thankyou, is not very clear!
did you test the singleimage.bin posted above?
help me
Unable to download file
call me on facebook and pass qboot.log
https://www.facebook.com/
---------- Post added at 08:06 PM ---------- Previous post was at 08:04 PM ----------
help me :/ :crying:
sorry for all!
the file dont work
i will keep looking for a working file
Thankyou!
also thanks to @Marceloaps for patience to test and test and test.......
Pls help me ;(
Can u upload new singleimage.bin to any filehost? or help me differently please.
**** Log buffer [000001] 2018-03-19_22:15:26 ****
[ -0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.053] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.053] Check qboot_log.txt for more details
[ 4.053] Total time: 4.055s
[ 4.053]
[ 4.053] qboot version 3.40
[ 4.053]
[ 4.053] DEVICE {
[ 4.053] name = "\\.\COM10",
[ 4.053] flags = "0x64",
[ 4.053] addr = "0x61FE5C",
[ 4.053] api.bnr = "0x2F92E28",
[ 4.053] }
[ 4.053]
[ 4.053]
[ 4.053] Backup & Restore {
[ 4.053] num_entries = 0,
[ 4.053] restoring = "false",
[ 4.053] backup_error = "not started",
[ 4.053] restore_error = "not started",
[ 4.053] }
[ 4.053]
**** Log buffer [000001] 2018-03-19_22:28:48 ****
[ 0.000] Opening device: \\.\COM10
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 79 (0x4f)
[ 0.016] ...cpu.sn = 868549579 (0x33c503cb)
[ 0.016] Opening singleimage
[ 0.187] ERROR: error opening singleimage
[ 0.187] Check qboot_log.txt for more details
[ 0.187] Total time: 0.266s
[ 0.187]
[ 0.187] qboot version 3.40
[ 0.187]
[ 0.187] DEVICE {
[ 0.187] name = "\\.\COM10",
[ 0.187] flags = "0x64",
[ 0.187] addr = "0x61FE5C",
[ 0.187] sahara.current_mode = "3",
[ 0.187] api.buffer = "0x3245020",
[ 0.187] cpu.serial = "868549579",
[ 0.187] cpu.id = "79",
[ 0.187] cpu.sv_sbl = "1",
[ 0.187] api.bnr = "0x2EF2FE8",
[ 0.187] }
[ 0.187]
[ 0.187]
[ 0.187] Backup & Restore {
[ 0.187] num_entries = 0,
[ 0.187] restoring = "false",
[ 0.187] backup_error = "not started",
[ 0.187] restore_error = "not started",
[ 0.187] }
[ 0.187]
**** Log buffer [000001] 2018-03-19_22:29:02 ****
[ 0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.047] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.047] Check qboot_log.txt for more details
[ 4.047] Total time: 4.049s
[ 4.047]
[ 4.047] qboot version 3.40
[ 4.047]
[ 4.047] DEVICE {
[ 4.047] name = "\\.\COM10",
[ 4.047] flags = "0x64",
[ 4.047] addr = "0x61FE5C",
[ 4.047] api.bnr = "0x2F02EE0",
[ 4.047] }
[ 4.047]
[ 4.047]
[ 4.047] Backup & Restore {
[ 4.047] num_entries = 0,
[ 4.047] restoring = "false",
[ 4.047] backup_error = "not started",
[ 4.047] restore_error = "not started",
[ 4.047] }
[ 4.047]
I'm counting on you.
It was nothing, so we improved more and we moved slowly, I need to be here.
anyone, has a OTAupdate saved?
to share it here please!
Thankyou!
vaserbanix said:
After many searching's, i think i managed to create a singleimage.bin for montana
it is made on xt1793 modell and it (maybe) can work on all montana version's
i cant test it! sorry, my phone is not bricked and hope to do not brick it in near future
so the singleimage.bin file is not tested
you will do test on your own risk
please think twice or more many times before act
Download the "Blankflash" zip, (link removed)
extract it in your pc(Windows or Linux)
in Windows opend the blankflash folder and do double-click on blank-flash.bat
a cmd window will opend and it will wait for your device to be conected
connect the phone and the process should start
in Linux opend the blankflash folder, opend terminal and tipe:./blank-flash.sh and hit enter
after you will see "<waiting for device>" line, connetct the phone and the process should start
hope singleimage.bin to be good for all versions of montana and to work helping you to restore the phone
What is a Forum without users?
Thankyou!
in case of ERRors please post along your coment a screenshot with cmd or terminal
or copy-paste all lines from it here
Thankyou again!
Click to expand...
Click to collapse
Where is the files why linked removed haven't tried yet. Is there any other file.
ASHDCBZ said:
Where is the files why linked removed haven't tried yet. Is there any other file.
Click to expand...
Click to collapse
i removed the link becouse the file is corupted or not valid, blankflash cant open it!
i have to get other method to get singleimage.bin for montana
Thankyou!
Sent from my Moto G5s using Tapatalk
vaserbanix said:
i removed the link becouse the file is corupted or not valid, blankflash cant open it!
i have to get other method to get singleimage.bin for montana
Thankyou!
Sent from my Moto G5s using Tapatalk
Click to expand...
Click to collapse
ok thank you for trying pls. find any other way as service center not helping and not doing anything about it.
ASHDCBZ said:
ok thank you for trying pls. find any other way as service center not helping and not doing anything about it.
Click to expand...
Click to collapse
I'm working on that.
Thankyou!
Sent from my Moto G5s using Tapatalk
Good work and thanks. My device I left for maintenance in a specialized store. Unfortunately they called me saying it could not be fixed. So as soon as I search I will participate in the forum and help develop it to help others. Leave your work as soon as I will part of it.
hey... plz help me i m alo facing this problem my device moto g5s got hard brickes
xdanielmonster said:
Can u upload new singleimage.bin to any filehost? or help me differently please.
**** Log buffer [000001] 2018-03-19_22:15:26 ****
[ -0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.053] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.053] Check qboot_log.txt for more details
[ 4.053] Total time: 4.055s
[ 4.053]
[ 4.053] qboot version 3.40
[ 4.053]
[ 4.053] DEVICE {
[ 4.053] name = "\\.\COM10",
[ 4.053] flags = "0x64",
[ 4.053] addr = "0x61FE5C",
[ 4.053] api.bnr = "0x2F92E28",
[ 4.053] }
[ 4.053]
[ 4.053]
[ 4.053] Backup & Restore {
[ 4.053] num_entries = 0,
[ 4.053] restoring = "false",
[ 4.053] backup_error = "not started",
[ 4.053] restore_error = "not started",
[ 4.053] }
[ 4.053]
**** Log buffer [000001] 2018-03-19_22:28:48 ****
[ 0.000] Opening device: \\.\COM10
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 79 (0x4f)
[ 0.016] ...cpu.sn = 868549579 (0x33c503cb)
[ 0.016] Opening singleimage
[ 0.187] ERROR: error opening singleimage
[ 0.187] Check qboot_log.txt for more details
[ 0.187] Total time: 0.266s
[ 0.187]
[ 0.187] qboot version 3.40
[ 0.187]
[ 0.187] DEVICE {
[ 0.187] name = "\\.\COM10",
[ 0.187] flags = "0x64",
[ 0.187] addr = "0x61FE5C",
[ 0.187] sahara.current_mode = "3",
[ 0.187] api.buffer = "0x3245020",
[ 0.187] cpu.serial = "868549579",
[ 0.187] cpu.id = "79",
[ 0.187] cpu.sv_sbl = "1",
[ 0.187] api.bnr = "0x2EF2FE8",
[ 0.187] }
[ 0.187]
[ 0.187]
[ 0.187] Backup & Restore {
[ 0.187] num_entries = 0,
[ 0.187] restoring = "false",
[ 0.187] backup_error = "not started",
[ 0.187] restore_error = "not started",
[ 0.187] }
[ 0.187]
**** Log buffer [000001] 2018-03-19_22:29:02 ****
[ 0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.047] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.047] Check qboot_log.txt for more details
[ 4.047] Total time: 4.049s
[ 4.047]
[ 4.047] qboot version 3.40
[ 4.047]
[ 4.047] DEVICE {
[ 4.047] name = "\\.\COM10",
[ 4.047] flags = "0x64",
[ 4.047] addr = "0x61FE5C",
[ 4.047] api.bnr = "0x2F02EE0",
[ 4.047] }
[ 4.047]
[ 4.047]
[ 4.047] Backup & Restore {
[ 4.047] num_entries = 0,
[ 4.047] restoring = "false",
[ 4.047] backup_error = "not started",
[ 4.047] restore_error = "not started",
[ 4.047] }
[ 4.047]
I'm counting on you.
Click to expand...
Click to collapse
plz reply me please its too urgent I lost my device I mean device hard bricked I need a working blank flash file for my montana sory for my bad English but I m very worried about my device plz someone help me anyway.....plz reply me on [email protected] its been too long there is no solution I found on internet ....plz help mee guys to get my device backon track...its hard bricked and only a notification light is blinking ...I can nor go to fastboot mode as well.....plz help and rplyyy..than you
For few days i have to fix some my heathy problems, my possibilities right now are limited(i have only the phone with me).
When I'll go back home, I'll continue to try to get a working singleimage.bin for unbrick the phones(or others method if exist)
Sorry and thanks for understanding!
Also please dont add other post's under this for now so everyboby can see it!
Thankyou again!
XT1792
> Unlocked bootloader + twrp + root
> accidentally removed stock rom by twrp
> installing new stock rom by adb fastboot
> BRICKED
> only selfie flash light blinkin when I put on charger or USB
> I installed qualcom drivers and worked, tried others blankflash
but I'm stucked and can't revive G5S by those blankflash
> Please, help me
Two days ago I purchased a new Moto X4 XT1900-1 and eagerly installed lineage-16.0-20190311-nightly-payton-signed.zip, only to brick my phone. It no longer turns on, but it does appear in syslog:
Code:
Mar 14 07:59:59 mint kernel: [ 2846.234567] usb 3-3: new high-speed USB device number 11 using xhci_hcd
Mar 14 07:59:59 mint kernel: [ 2846.389413] usb 3-3: New USB device found, idVendor=05c6, idProduct=9008
Mar 14 07:59:59 mint kernel: [ 2846.389415] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 14 07:59:59 mint kernel: [ 2846.389416] usb 3-3: Product: QUSB__BULK
Mar 14 07:59:59 mint kernel: [ 2846.389417] usb 3-3: Manufacturer: Qualcomm CDMA Technologies MSM
Mar 14 07:59:59 mint kernel: [ 2846.390291] qcserial 3-3:1.0: Qualcomm USB modem converter detected
Mar 14 07:59:59 mint kernel: [ 2846.390354] usb 3-3: Qualcomm USB modem converter now attached to ttyUSB0
Mar 14 07:59:59 mint mtp-probe: checking bus 3, device 11: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3"
Mar 14 07:59:59 mint mtp-probe: bus: 3, device: 11 was not an MTP device
Mar 14 07:59:59 mint upowerd[1768]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0
Mar 14 07:59:59 mint upowerd[1768]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-3
I found this thread: reddit.com/r/LineageOS/comments/b06uoi/moto_x4_payton_bricked_after_update_to_110319, where @erfanoabdi indicated it was a known issue and recoverable.
I downloaded the blankflash from drive.google.com/file/d/1XWPW7qEYhWqi6lL-1308GgmFht98BiV5/view and followed the steps as described at reddit.com/r/LineageOS/comments/b06uoi/moto_x4_payton_bricked_after_update_to_110319/eicp5sy/
The output of blank-flash.sh is
Code:
[email protected]:~/Downloads/blankflash$ ./blank-flash.sh
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.000s
FAILED: qb_flash_singleimage()->device_open()->error opening device
The output of qboot_log.txt is
Code:
[email protected]:~/Downloads/blankflash$ cat qboot_log.txt
**** Log buffer [000001] 2019-03-14_08:18:31 ****
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.000s
[ 0.000]
[ 0.000] qboot version 3.86
[ 0.000]
[ 0.000] DEVICE {
[ 0.000] name = "/dev/ttyUSB0",
[ 0.000] flags = "0x60",
[ 0.000] addr = "0xA3CCC830",
[ 0.000] serial_nix.device_pathname = "/sys/bus/usb/devices/3-3/3-3:1.0/ttyUSB0",
[ 0.000] api.bnr = "0x1B535F0",
[ 0.000] }
[ 0.000]
[ 0.000]
[ 0.000] Backup & Restore {
[ 0.000] num_entries = 0,
[ 0.000] restoring = "false",
[ 0.000] backup_error = "not started",
[ 0.000] restore_error = "not started",
[ 0.000] }
[ 0.000]
I have tried running blank-flash.sh while holding down the Power Button + Vol Down Button, but the results are always the same.
HALP PLZ!!!!
dougfir said:
Two days ago I purchased a new Moto X4 XT1900-1 and eagerly installed lineage-16.0-20190311-nightly-payton-signed.zip, only to brick my phone. It no longer turns on, but it does appear in syslog:
I found this thread: reddit.com/r/LineageOS/comments/b06uoi/moto_x4_payton_bricked_after_update_to_110319, where @erfanoabdi indicated it was a known issue and recoverable.
I downloaded the blankflash from drive.google.com/file/d/1XWPW7qEYhWqi6lL-1308GgmFht98BiV5/view and followed the steps as described at reddit.com/r/LineageOS/comments/b06uoi/moto_x4_payton_bricked_after_update_to_110319/eicp5sy/
The output of blank-flash.sh is
The output of qboot_log.txt is
I have tried running blank-flash.sh while holding down the Power Button + Vol Down Button, but the results are always the same.
HALP PLZ!!!!
Click to expand...
Click to collapse
Run it as root.
The power vol down combo is more an art than science.
serial_write Error Help
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB1
[ 0.000] Detecting device
[ 21.382] ...cpu.id = 172 (0xac)
[ 21.382] ...cpu.sn = 4247084357 (0xfd255d45)
[ 21.382] Opening singleimage
[ 21.382] Loading package
[ 21.384] ...filename = pkg.xml
[ 21.385] Loading programmer
[ 21.385] ...filename = programmer.elf
[ 21.385] Sending programmer
[ 21.570] Handling things over to programmer
[ 21.570] Identifying CPU version
[ 21.570] Waiting for firehose to get ready
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error
Are you running as root?
ttyUSB Permissions Linux
gee one said:
Are you running as root?
Click to expand...
Click to collapse
Yes as root. Solved as an issue between the device showing up on /dev/ttyUSB0 initially on Linux. I set permissions correctly there, but it reconnects with VolDown+Power on /dev/ttyUSB1 which had limited permissions. While udev rules could solve it, I was lucky to catch the device correctly in time to manually change the permissions and have blankflash progress all the way through. [Upon further thought root should have solved this, so it is likely just an issue with how devices/permissions are set up on my system].
mistryous said:
Yes as root. Solved as an issue between the device showing up on /dev/ttyUSB0 initially on Linux. I set permissions correctly there, but it reconnects with VolDown+Power on /dev/ttyUSB1 which had limited permissions. While udev rules could solve it, I was lucky to catch the device correctly in time to manually change the permissions and have blankflash progress all the way through. [Upon further thought root should have solved this, so it is likely just an issue with how devices/permissions are set up on my system].
Click to expand...
Click to collapse
doing it as root but getting
Code:
serial_write(), line 280: Input/output error
please help!!!!
Hello Everyone. Please help me un bricking moto X4.
1) First, I'm new to this field.
2) My Moto X4 is totally dead and no sign of life. No fastboot, no recovery and none of the key works.
One thing I want to say that my device is totally intact. I have never try to root or unlock this. The device is in stock condition with the last latest update. Day before I was just using its hotspot to access internet on my PC. I don't know when it get switched off. And till then no sign of life on my moto x4. Can't even see whether it is charging or not? I tried to flash firmware but stuck with errors. I have read blankflash can be helpful but didn't find a blankflash for moto X4 XT1900-2. I also tried a blankflash file but stuck at a problem with error.
**** Log buffer [000001] 2020-09-30_13:20:41 ****
[ 0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 34.445] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.445] Check qboot_log.txt for more details
[ 34.445] Total time: 34.446s
[ 34.445]
[ 34.445] qboot version 3.86
[ 34.445]
[ 34.445] DEVICE {
[ 34.445] name = "\\.\COM3",
[ 34.445] flags = "0x64",
[ 34.445] addr = "0x62FD54",
[ 34.445] api.bnr = "0x1102BE0",
[ 34.445] }
[ 34.445]
[ 34.445]
[ 34.445] Backup & Restore {
[ 34.445] num_entries = 0,
[ 34.445] restoring = "false",
[ 34.445] backup_error = "not started",
[ 34.445] restore_error = "not started",
[ 34.445] }
Please anyone can provide me blankflash file for Motorola X4 XT1900-2. And suggest any other solution so that I can reboot my device, unbrick, . I'm on Android 9 with last latest update. please help me.
siddh315 said:
Hello Everyone. Please help me un bricking moto X4.
1) First, I'm new to this field.
2) My Moto X4 is totally dead and no sign of life. No fastboot, no recovery and none of the key works.
One thing I want to say that my device is totally intact. I have never try to root or unlock this. The device is in stock condition with the last latest update. Day before I was just using its hotspot to access internet on my PC. I don't know when it get switched off. And till then no sign of life on my moto x4. Can't even see whether it is charging or not? I tried to flash firmware but stuck with errors. I have read blankflash can be helpful but didn't find a blankflash for moto X4 XT1900-2. I also tried a blankflash file but stuck at a problem with error.
**** Log buffer [000001] 2020-09-30_13:20:41 ****
[ 0.000] Opening device: \.\COM3
[ 0.002] Detecting device
[ 34.445] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.445] Check qboot_log.txt for more details
[ 34.445] Total time: 34.446s
[ 34.445]
[ 34.445] qboot version 3.86
[ 34.445]
[ 34.445] DEVICE {
[ 34.445] name = "\.\COM3",
[ 34.445] flags = "0x64",
[ 34.445] addr = "0x62FD54",
[ 34.445] api.bnr = "0x1102BE0",
[ 34.445] }
[ 34.445]
[ 34.445]
[ 34.445] Backup & Restore {
[ 34.445] num_entries = 0,
[ 34.445] restoring = "false",
[ 34.445] backup_error = "not started",
[ 34.445] restore_error = "not started",
[ 34.445] }
Please anyone can provide me blankflash file for Motorola X4 XT1900-2. And suggest any other solution so that I can reboot my device, unbrick, . I'm on Android 9 with last latest update. please help me.
Click to expand...
Click to collapse
Window 10?
Sent from my ocean using XDA Labs
sd_shadow said:
Window 10?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Yeah, WIndows 10, 64 bit with 20H1 update.
siddh315 said:
Yeah, WIndows 10, 64 bit with 20H1 update.
Click to expand...
Click to collapse
It shows in Device Manager as ?
Qualcomm HS-USB QDLoader 9008 or
Qualcomm QHSUSB_Bulk
sd_shadow said:
It shows in Device Manager as ?
Qualcomm HS-USB QDLoader 9008 or
Qualcomm QHSUSB_Bulk
Click to expand...
Click to collapse
it is Qualcomm HS-USB QDLoader 9008
Anyone who have qcn file for Moto x4