Database Develop

(SOLVED)Rom dump moto x4 xt-1900-1/6

Hi guys whats up? So anyone can make the dump ROM of Moto X4 (Android 8.0 or above) for me? My device was hard brick and i can save it, only with a DUMP ROM or a blank flash files that don't exist yet!! Thank You for attention...

LucasHanchop said:
Hi guys whats up? So anyone can make the dump ROM of Moto X4 (Android 8.0 or above) for me? My device was hard brick and i can save it, only with a DUMP ROM or a blank flash files that don't exist yet!! Thank You for attention...
Click to expand...
Click to collapse
The following apparently worked for someone:
https://forum.xda-developers.com/showpost.php?p=76918099&postcount=7

edufur said:
The following apparently worked for someone:
https://forum.xda-developers.com/showpost.php?p=76918099&postcount=7
Click to expand...
Click to collapse
I'll try bro! If works I will tell you soon! But if don't can you help me?

edufur said:
The following apparently worked for someone:
https://forum.xda-developers.com/showpost.php?p=76918099&postcount=7
Click to expand...
Click to collapse
[ -0.000] Opening device: \\.\COM4
[ 0.010] Detecting device
[ 34.031] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.031] Check qboot_log.txt for more details
[ 34.032] Total time: 34.032s
[ 34.032]
[ 34.032] qboot version 3.86
[ 34.032]
[ 34.032] DEVICE {
[ 34.032] name = "\\.\COM4",
[ 34.032] flags = "0x64",
[ 34.032] addr = "0x62FD64",
[ 34.032] api.bnr = "0xD82C88",
[ 34.032] }
[ 34.032]
[ 34.032]
[ 34.032] Backup & Restore {
[ 34.032] num_entries = 0,
[ 34.032] restoring = "false",
[ 34.032] backup_error = "not started",
[ 34.032] restore_error = "not started",
[ 34.032] }
[ 34.032]
Any Solution?

edufur said:
the following apparently worked for someone:
https://forum.xda-developers.com/showpost.php?p=76918099&postcount=7
Click to expand...
Click to collapse
man i did it thank you very muchhhh!!

edufur said:
The following apparently worked for someone:
https://forum.xda-developers.com/showpost.php?p=76918099&postcount=7
Click to expand...
Click to collapse
Mark this quote with solved! Please

LucasHanchop said:
[ -0.000] Opening device: \\.\COM4
[ 0.010] Detecting device
[ 34.031] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.031] Check qboot_log.txt for more details
[ 34.032] Total time: 34.032s
[ 34.032]
[ 34.032] qboot version 3.86
[ 34.032]
[ 34.032] DEVICE {
[ 34.032] name = "\\.\COM4",
[ 34.032] flags = "0x64",
[ 34.032] addr = "0x62FD64",
[ 34.032] api.bnr = "0xD82C88",
[ 34.032] }
[ 34.032]
[ 34.032]
[ 34.032] Backup & Restore {
[ 34.032] num_entries = 0,
[ 34.032] restoring = "false",
[ 34.032] backup_error = "not started",
[ 34.032] restore_error = "not started",
[ 34.032] }
[ 34.032]
Any Solution?
Click to expand...
Click to collapse
About this If dont work press the Power Button with the vol- Button and click in the blank-flash.bat on same time and wait the program recognize your board,storage,processor!

You can change the title and make it SOLVED I think!

abhi212b said:
You can change the title and make it SOLVED I think!
Click to expand...
Click to collapse
I've already did it! Thank you

Moto Z3 Play Hard Bricked

Tryng to root my device (XT1929-6), I bricked the phone. After installing the motorola device manager, i tried to blankflash the phone, but thats the log
Motorola qboot utility version 3.37
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 204 (0xcc)
[ 0.000] ...cpu.sn = 3748563624 (0xdf6e8aa8)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.016] Failed identify board. Wrong package?
[ 0.016] ERROR: error loading package
[ 0.016] Check qboot_log.txt for more details
[ 0.016] Total time: 0.031s
FAILED: qb_flash_singleimage()->error loading package
Please help! I am not 100% certain where this thread must to be, if I am wrong tell me.

And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..

Willy33 said:
And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..
Click to expand...
Click to collapse
I tried to use SuperSU zip file to root. I wasn't able to install TWRP, for installing supersu I used "fastboot boot TWRP.img" beacause the phone doesn't have a recovery partition. When i tried to install supersu, it returned "Unable to mount /vendor (busy)" (not full message beacause i don't have acces to the logs), then y tried to fix "vendor using the repair tool of twrp, and after the restart it was full bricked. Actually windows sometimes detects the device if you press power button and vol down, but it can't recognise the type of device.

Teto Balsámico said:
I tried to use SuperSU zip file to root. I wasn't able to install TWRP, for installing supersu I used "fastboot boot TWRP.img" beacause the phone doesn't have a recovery partition. When i tried to install supersu, it returned "Unable to mount /vendor (busy)" (not full message beacause i don't have acces to the logs), then y tried to fix "vendor using the repair tool of twrp, and after the restart it was full bricked. Actually windows sometimes detects the device if you press power button and vol down, but it can't recognise the type of device.
Click to expand...
Click to collapse
I don’t understand why it was to invent with su when a working method for getting root rights using magisk and even without twrp was already described here, but this is not the point ... you need to install the necessary drivers for blankflash and the phone is defined as Qualcomm 9008 , and after that start blankflash. But as I said earlier, there is no blankflash file yet, just for our phone.

Willy33 said:
And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..
Click to expand...
Click to collapse
Willy33 said:
I don’t understand why it was to invent with su when a working method for getting root rights using magisk and even without twrp was already described here, but this is not the point ... you need to install the necessary drivers for blankflash and the phone is defined as Qualcomm 9008 , and after that start blankflash. But as I said earlier, there is no blankflash file yet, just for our phone.
Click to expand...
Click to collapse
And how do i get those drivers? And where i can see how the computer recognises the mobile as Qualcomm 9008? just for the time being.

Internet spaces help very well))) it is enough to drive in Qualcomm 9008 and that's it. And to look naturally in the windows device manager.
and on YouTube you can even find instructions on how to properly install these drivers.

Willy33 said:
Internet spaces help very well))) it is enough to drive in Qualcomm 9008 and that's it. And to look naturally in the windows device manager.
and on YouTube you can even find instructions on how to properly install these drivers.
Click to expand...
Click to collapse
Thanks for your help!

I have the same problem. Could you fix the error?

Do I have to do something else for linux to detect my moto z3? Windows detects it without problem, but it always shows an error when reading the storage

Help..
E:\Descargas\qualkom dri>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.002] Opening device: \\.\COM4
[ 0.238] Detecting device
[ 0.248] ...cpu.id = 204 (0xcc)
[ 0.248] ...cpu.sn = 2761611797 (0xa49ada15)
[ 0.249] Opening singleimage
[ 0.594] Loading package
[ 0.603] ...filename = pkg.xml
[ 0.606] Loading programmer
[ 0.637] ...filename = programmer.elf
[ 0.638] Sending programmer
[ 0.832] Handling things over to programmer
[ 0.833] Identifying CPU version
[ 0.833] Waiting for firehose to get ready
[ 4.132] ...SDM636 1.0
[ 4.134] Determining target secure state
[ 4.137] ...secure = yes
[ 4.200] Configuring device...
[ 4.211] Flashing GPT...
[ 4.212] Flashing partition with gpt.bin
[ 4.221] Initializing storage
[ 4.300] ...blksz = 512
[ 4.521] Target NAK!
[ 4.521] ...ERROR: SDCC Error 29 (3)
[ 4.521] ...ERROR: Write Failed sector 0, size 48
[ 4.522] ...ERROR: Failed to write 1 slot 0, partition 0, start_sector 48 num_sectors 0, error 3
[ 4.522] ...Finished programming start_sector 48 and TotalSectorsToProgram 48
[ 4.522] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->lun_write()->storage_write()->firehose_do_fmt()->do_recipe()->NAK
[ 4.523] Check qboot_log.txt for more details
[ 4.524] Total time: 4.538s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->lun_write()->storage_write()->firehose_do_fmt()->do_recipe()->NAK

Moto X4 XT1900-2 Hard Bricked Error

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

Moto G6 XT1925-6 "bricked" from normal use--blankflash not working

Hi all,
My girlfriend's Moto G6 XT1925-6 (purchased via Best Buy, never rooted/modded) got slow one day, I recommended rebooting and then it never came back. The only signs of life are that when plugged into a computer or charger. the white light blinks every second or so, and the phone shows up as the following USB device (port):
Qualcomm HS-USB QDLoader 9008 (COM4)
I have tried 3-4 different blankflash files numerous times (including the two from https://mirrors.lolinet.com/firmware/moto/ali/blankflash/) and always get an IO error. The phone would have been fully updated as of 11/1, it was being used on Cricket Wireless if that matters. Lenovo Moto Smart Assistant was no help unfortunately since the phone cannot boot into fastboot.
I tried again today since one 'fix' seemed to be to let the battery discharge. It was unplugged for ~5 days and no change.
Any other tips/tricks or am I SOL? She was somewhat due for an upgrade anyways, but thought I'd try one last time to look for other solutions.
Thanks!

timing is absolutely critical in EDL mode - i.e., you don't have long to start the flashing once you plug the USB cable in. sounds like you have the correct drivers, given that the phone shows up properly in device manager. try the following in quick succession:
0. plug the USB cable into the computer (not the phone, yet)
1. start the blankflash script from lolinet
2. depress and hold the power and volume_down buttons
3. connect the USB cable
4. script will do its magic (release the buttons) and reboot the phone to the bootloader
hope this helps!

armrbackthrsday said:
timing is absolutely critical in EDL mode - i.e., you don't have long to start the flashing once you plug the USB cable in. sounds like you have the correct drivers, given that the phone shows up properly in device manager. try the following in quick succession:
0. plug the USB cable into the computer (not the phone, yet)
1. start the blankflash script from lolinet
2. depress and hold the power and volume_down buttons
3. connect the USB cable
4. script will do its magic (release the buttons) and reboot the phone to the bootloader
hope this helps!
Click to expand...
Click to collapse
Exactly when are you supposed to release the buttons? No matter when I do, I get:
ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error

Heat84 said:
Exactly when are you supposed to release the buttons? No matter when I do, I get:
ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
Click to expand...
Click to collapse
hmm, sounds like the blankflash script is not recognizing the correct COM port. does the device show up as "Qualcomm HS-USB QDLoader 9008" in device manager?

armrbackthrsday said:
hmm, sounds like the blankflash script is not recognizing the correct COM port. does the device show up as "Qualcomm HS-USB QDLoader 9008" in device manager?
Click to expand...
Click to collapse

I fixed that problem by rebooting the phone while qflash was running. Now I have a different error that you see below at 3. 485.
Code:
[ -0.000] Opening device: \\.\COM11
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 286 (0x11e)
[ 0.002] ...cpu.sn = 1010000641 (0x3c336301)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.009] ...filename = programmer.elf
[ 0.009] Sending programmer
[ 0.131] Handling things over to programmer
[ 0.131] Identifying CPU version
[ 0.131] Waiting for firehose to get ready
[ 3.213] ...SM_SAIPAN 2.0
[ 3.214] Determining target secure state
[ 3.219] ...secure = yes
[ 3.307] Configuring device...
[ 3.317] Skipping UFS provsioning as target is secure
[ 3.317] Configuring device...
[ 3.483] Flashing GPT...
[ 3.483] Flashing partition with gpt.bin
[ 3.485] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->find_first_package()->not found
[ 3.486] Check qboot_log.txt for more details
[ 3.486] Total time: 3.487s
[ 3.487]
[ 3.487] qboot version 3.86
[ 3.487]
[ 3.487] DEVICE {
[ 3.487] name = "\\.\COM11",
[ 3.487] flags = "0x144",
[ 3.487] addr = "0x28FD74",
[ 3.487] sahara.current_mode = "0",
[ 3.487] api.buffer = "0x2570020",
[ 3.487] cpu.serial = "1010000641",
[ 3.487] cpu.id = "286",
[ 3.487] cpu.sv_sbl = "0",
[ 3.487] cpu.name = "SM_SAIPAN",
[ 3.487] storage.type = "UFS",
[ 3.487] sahara.programmer = "programmer.elf",
[ 3.487] module.firehose = "0x24D1248",
[ 3.487] api.firehose = "0x67D948",
[ 3.487] cpu.ver = "512",
[ 3.487] cpu.vername = "2.0",
[ 3.487] fh.max_packet_sz = "1048576",
[ 3.487] fh.storage_inited = "1",
[ 3.487] }
[ 3.487]
I don't actually have to worry about this any more because I was tired of playing around and took the phone(a Motorola Edge plain 2020) back to Best Buy where I got it, and they couldn't fix it, but they did offer to exchange it for a new one. I chose an "open box" one that probably was returned the day after it was bought by the first owner for some stupid reason. I also got a $74 refund to even the exchange(I would've had to wait a week for a new one or choose a different make and/or model phone available in store otherwise). But don't let that stop you from offering a translation to this error message if you have one. I'm curious and you may help someone else.
Why would the developer of Qboot not have any documentation of what the error messages mean? What's the point of writing error messages if you don't tell anybody what they mean? Was that done out of arrogance or stupidity? Also, when it says to check qboot log for details, that BS. Everything you see during the flash attempt on screen is all you see in the log. Nothing more.
By the way if you're interested, I started a thread about my problem before I found this one: https://forum.xda-developers.com/t/...hard-hard-bricked-edge.4341829/#post-85717539
By the way 2: It seems to be a weird coincidence that you resurrected this thread almost a year after the last (and only) post at the SAME TIME I was having the same issue they were. Even though you didn't help me and I don't need the help anymore, you gotta admit that that's a little creepy. lol

Struggling to recover Moto G6

I had my moto G6 in storage as I had upgraded and no longer needed it till today. I pulled it out and noticed it wouldn't turn on. I figured it was dead and plugged it in when I was promptly greeted with a fastboot menu and logs complaining the hab image couldn't be verified. Tried rebooting a couple times hoping for a fluke and alas, my luck is not good.
So I followed the recommendation on the screen and got the lovely Lenovo Rescue and Smart Assistant to reprogram my phone. It tried the first time and my phone ended up with a black screen and white LED blinking at 1Hz. After a time the Lenovo tool gave up and errored out. I held the power button for a minute and I was able to get back to the fastboot screen and figured I would just try again.
I tried a second time and it progressed further into the process before it did the same thing again. I am now with a phone that does little more than blink the white LED. But I do see that the CPU is in a EDL mode and enumerates as a COM port. I found this thread for the G6 Plus and was able to get some luck but the blankflash errored out (not surprised as it was for the plus and not the 'regular' G6).
[ULTIMATE GUIDE] How To Unbrick your Moto G6 Plus
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY AND IT'S NOT 100% GUARANTEED TO WORK. WORKED ON MY G6 PLUS (XT1926-7) AND SOME OTHER USERS ON WINDOWS. THINGS YOU WILL NEED: Motorola and Qualcomm Drivers; BlankFlash file; Stock ROM; STEPS: PART...
forum.xda-developers.com
I spent some time online and found this link:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
I downloaded the PDS29.118-15-11-14 and gave that a try. I produced some results but ultimately ended in an error.
[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 154 (0x9a)
[ 0.004] ...cpu.sn = 1862624572 (0x6f05653c)
[ 0.004] Opening singleimage
[ 0.012] Loading package
[ 0.015] ...filename = singleimage.pkg.xml
[ 0.017] Loading programmer
[ 0.018] ...filename = programmer.mbn
[ 0.018] Sending programmer
[ 0.265] Handling things over to programmer
[ 0.266] Identifying CPU version
[ 0.268] Waiting for firehose to get ready
[ 60.504] Waiting for firehose to get ready
[121.584] ...MSM8953 unknown
[121.584] Determining target secure state
[121.586] Waiting for firehose to get ready
[184.162] ...secure = no
[184.177] Waiting for firehose to get ready
[244.227] Configuring device...
[244.229] Waiting for firehose to get ready
[306.781] Waiting for firehose to get ready
[370.379] Waiting for firehose to get ready
[431.463] Waiting for firehose to get ready
[494.029] ERROR: do_package()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[494.029] Check qboot_log.txt for more details
[494.029] Total time: 494.032s
[494.029]
[494.029] qboot version 3.40
[494.029]
[494.029] DEVICE {
[494.029] name = "\\.\COM3",
[494.029] flags = "0x64",
[494.029] addr = "0x61FE4C",
[494.029] sahara.current_mode = "0",
[494.029] api.buffer = "0x802020",
[494.029] cpu.serial = "1862624572",
[494.029] cpu.id = "154",
[494.029] cpu.sv_sbl = "0",
[494.029] cpu.name = "MSM8953",
[494.029] storage.type = "eMMC",
[494.029] sahara.programmer = "programmer.mbn",
[494.029] module.firehose = "0x6A1D30",
[494.029] cpu.ver = "0",
[494.029] cpu.vername = "unknown",
[494.029] api.bnr = "0x6AAAA8",
[494.029] }
[494.029]
[494.030]
[494.030] Backup & Restore {
[494.030] num_entries = 0,
[494.030] restoring = "false",
[494.030] backup_error = "not started",
[494.030] restore_error = "not started",
[494.030] }
[494.030]
I think the exact blankflash I am looking for might be called: PPS29.118_15_11_16_cid18
The reason I suspect this is because the image that the Lenovo tool was trying to download and install to the phone has a full name of:
ALI_AMZ_PPS29.118_15_11_16_cid18_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
Does anyone happen to have any suggestions? Would be cool to get this phone back from the dead, no matter what ROM ends up on it.
Thanks in advance