Related
So, long story short - I hard bricked my phone by trying to flash .bin files when they should have been .img files (rookie mistake). Anyways, once i flashed those the screen went black and the phone would not respond to anything. When i plugged the phone in it showed up as Qualcomm 9008 blah blah blah so i followed this method: http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853. I was able to flash some of my partitions but then suddenly the screen changed to this:
http://i.imgur.com/G0n16LP.jpg
I believe it was after flashing tz. Regardless, I could not flash any more partitions.
So i plugged in my battery and reconnected it to my computer and it shows up as this: http://i.imgur.com/zRKaNZC.jpg. For those who can't see it it shows up as LGE AndroidNet USB Serial Port. It also shows up as LGE AndroidNet USB Modem. Any idea on how to fix my phone from this? I've installed the Qualcomm Drivers as well as the ADB universal drivers and the LG Drivers for my phone. Using LG Mobile Support Tool the flashing goes until it says it can't connect to the phone. QPST can't see it, LG Flash Tool gives me "Model Information Check Fail" and any KDZ Flashing tool can not flash it.
I heard talk about shorting capacitors to put it into 9006 mode in order to see the partitions. Does anyone know which capacitors?
Any help would be great considering there is not a whole lot of (free) information out there on this.
Click to expand...
Click to collapse
So I fixed my phone. For everyone wondering how to do it follow this thread: http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091.
If you're stuck in the serial mode you have to short the pins on your emmc. Short then pins as described in the above thread and then plug your usb in. Then follow the steps in the thread and flash.
Man I'm in the same boat as you. I couldn't get the Qualcomm tool to work though.
Nothing seems to be working at the moment and neither flashtool or anything else seem to be finding my device.
I'd like to avoid sending it to LG if I can as I need this phone.
Have you had any luck at all?
Look's like your phone diag port. May need your msl/spc to get qualcomm tool to work.
fergie716 said:
How to Get your MSL/SPC
**NOTE** This will only work if your phone is able to turn on
Make sure you have the LG Drivers Installed on your computer (link is in 1st post for that)
Open up your dialer and enter ##DIAG#
Enable DIAG Mode
Connect your phone to your computer
On your phone change the USB Connection type to Charge Only (pull down your statusbar and click on USB Connected)
Download CdmaDevTerm on your computer(I prefer this version)
Extract the CdmaDevTermZip
Inside the extracted folder double click on the cdmaTerm file to start the application
On the right hand side of the CdmaDevTerm screen select "Scan ports"
Next select the LGE AndroidNet USB Serial Port from the drop down menu (mine was COM6) then click Connect
In the SPC/Lock Options change NV to LG from the drop down menu
Now click Read SPC
Success!
Click to expand...
Click to collapse
This looks like your phone is charging, that might mean your boot or aboot partitions are ok. Or maybe recovery, i'm not sure which one is used for phone off charging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jcfunk said:
Look's like your phone diag port. May need your msl/spc to get qualcomm tool to work.
This looks like your phone is charging, that might mean your boot or aboot partitions are ok. Or maybe recovery, i'm not sure which one is used for phone off charging.
Click to expand...
Click to collapse
I connected to it (I think) and got the spc number but it doesn't show up in the qualcomm tool/ i don't know what to do with the number haha.
jfedorchuk said:
I connected to it (I think) and got the spc number but it doesn't show up in the qualcomm tool/ i don't know what to do with the number haha.
Click to expand...
Click to collapse
Qualcomm tool, do you mean qpst?
if so you need to add port to server configuration tool. Or maybe try CDMAworkshop.
Have you tried volume + and USB insert?
maybe download or fastboot mode will start
jcfunk said:
Qualcomm tool, do you mean qpst?
if so you need to add port to server configuration tool. Or maybe try CDMAworkshop.
Have you tried volume + and USB insert?
maybe download or fastboot mode will start
Click to expand...
Click to collapse
Ya the qpst. I looked and the port doesn't show up as a phone. It just shows up as the serial port and won't allow me to connect. I'll look for the cdmaworkshop tool though. I'm probably going to just try to short the capactitors to get it into 9006 mode and reflash the partitions. Does anyone know where the specific capacitors are? There was a youtube video of it but the owner flipped out and made it private.... so much for advancing the community.
I tried the volume up and insert but nothing shows up. I'm curious if this were to go in for warranty if the company to fix it would be able to tell if its rooted or if they would be in the same position i am where nothing shows up.
Does it show comm7 , i know there is a box that is checked, in the add port screen, that keeps it from seeing the port. When i get home i'll take a screen shot
I too am having this exact issue.
I'm on the same boat. I don't even know how it happened since I wasn't even trying to flash a ROM. One person told me to look at tablets hard brick but I've had no luck yet. Phone was stuck in a recovery bootloop so I tried to wipe/restore backup which didn't work. Popped the battery, went to download mode, started flashing TOT, got an error (yes I had the right files), popped battery again hoping it was a bad connection but nope. I got it the other week :/ as a replacement because my G2 had hardware issues. There's gotta be a way somewhere. In the mean time, I had my gf call my service provider claiming she got a popup about an upgrade, clicked yes and came back to a black screen. They said to bring it in because it's within 14 days of the refurbished. I'm going to take it in but I'm hoping there's a way to get the phone to not load anything at all (led or the boot error during LG), or do sales reps not know enough and/or don't care enough?
I got it working!!! Somehow I got TWRP'd to boot then restored my backup of 4.4.2 stock. AT&T connecting/dropping and Baseband: "Unknown" before it randomly rebooted into download mode which I'm at now. I tried flashing TOT through COM41 but it wasn't successful. Not sure what to do now.
I had some paragraph typed and it must've not gone through. I got it back to the home screen and AT&T logo once "firmware upgrade" was an option again. I still don't know how I switched it from Qualcomm to LGE Mobile, maybe some files I deleted thinking an app backdoor'd it and injected files. After a fun and exciting 12+ hours straight with errors, bootloops, reading forums, videos, downloading/un-install. I managed a way that worked and booted back into a fresh device.
Flash Tools < BOARD_DL < Booted into Status 2
LG Suite < Restore < Fail
Flash Tools < UPGRADE_DL < Fail at 6%
Flash Tools < BOARD_DL < Fail at download mode
Device Manager < Show Hidden < Portable Devices < Un-install all MTP
Flash Tools < BOARD_DL < got to 8x% < Phone Reboot into AAT < Click < Power+Click on "Normal Boot"
LG Logo < AT&T Logo < Brand new G3
Click to expand...
Click to collapse
Hopefully this method will work for you, and who ever else has the same problem.
Here's part of the log. Not sure if hopeful or not.
[ 9:46:27] == PROPERTY INFO
[ 9:46:27] 1. download cable = USER
[ 9:46:27] 2. battery level = 77
[ 9:46:27] 3. download type =
[ 9:46:27] 4. download speed = 0
[ 9:46:27] 5. usb version = UHS
[ 9:46:27] 6. hardware revision = rev_10
[ 9:46:27] 7. download sw version =
[ 9:46:27] 8. device sw version = D85010d
[ 9:46:27] 9. secure device = S
[ 9:46:27] 10. laf sw version = 1.0
[ 9:46:27] 11. device factory version = LGD850AT-01-V10d-310-410-JUN-19-2014+0
[ 9:46:27] 12. device factory out version = LGD850AT-00-V10d-ATT-US-JUN-19-2014+0
[ 9:46:27] 13. pid = HD58S140925001695
[ 9:46:27] 14. imei = XXXXXXXXXXXXXXXXXXXX
[ 9:46:27] 15. model name = LG-D850
[ 9:46:27] 16. device build type = U
[ 9:46:27] 17. chipset platform = msm8974
[ 9:46:27] 18. target_operator = ATT
[ 9:46:27] 19. target_country = US
[ 9:46:27] 20. ap_factory_reset_status = 2
[ 9:46:27] 21. cp_factory_reset_status = 0
[ 9:46:27] 22. isDownloadNotFinish = 0
[ 9:46:27] 23. qem = 0
[ 9:46:27] 24. cupss swfv = FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-F
[ 9:46:27] 25. is one binary dual plan = 0
[ 9:46:27] 26. memroy size = 61071360
[ 9:46:27] 27. memory_id = 032GE4
[ 9:46:27] 28. bootloader_ver = MiniOS 3.0
[ 9:46:27] LAF : Bin_User_Mode
[ 9:46:27] isValidateSecureImage Device is a qfused.
[ 9:46:27] found sbl1 Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found aboot Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found rpm Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found tz Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] Secure Image Check Success
[ 9:46:27] * Set AP factory_reset= 0
[ 9:46:27] * Set qem_reset= 1
GrayNullFox said:
I'm on the same boat. I don't even know how it happened since I wasn't even trying to flash a ROM. One person told me to look at tablets hard brick but I've had no luck yet. Phone was stuck in a recovery bootloop so I tried to wipe/restore backup which didn't work. Popped the battery, went to download mode, started flashing TOT, got an error (yes I had the right files), popped battery again hoping it was a bad connection but nope. I got it the other week :/ as a replacement because my G2 had hardware issues. There's gotta be a way somewhere. In the mean time, I had my gf call my service provider claiming she got a popup about an upgrade, clicked yes and came back to a black screen. They said to bring it in because it's within 14 days of the refurbished. I'm going to take it in but I'm hoping there's a way to get the phone to not load anything at all (led or the boot error during LG), or do sales reps not know enough and/or don't care enough?
I got it working!!! Somehow I got TWRP'd to boot then restored my backup of 4.4.2 stock. AT&T connecting/dropping and Baseband: "Unknown" before it randomly rebooted into download mode which I'm at now. I tried flashing TOT through COM41 but it wasn't successful. Not sure what to do now.
I had some paragraph typed and it must've not gone through. I got it back to the home screen and AT&T logo once "firmware upgrade" was an option again. I still don't know how I switched it from Qualcomm to LGE Mobile, maybe some files I deleted thinking an app backdoor'd it and injected files. After a fun and exciting 12+ hours straight with errors, bootloops, reading forums, videos, downloading/un-install. I managed a way that worked and booted back into a fresh device.
Hopefully this method will work for you, and who ever else has the same problem.
Here's part of the log. Not sure if hopeful or not.
[ 9:46:27] == PROPERTY INFO
[ 9:46:27] 1. download cable = USER
[ 9:46:27] 2. battery level = 77
[ 9:46:27] 3. download type =
[ 9:46:27] 4. download speed = 0
[ 9:46:27] 5. usb version = UHS
[ 9:46:27] 6. hardware revision = rev_10
[ 9:46:27] 7. download sw version =
[ 9:46:27] 8. device sw version = D85010d
[ 9:46:27] 9. secure device = S
[ 9:46:27] 10. laf sw version = 1.0
[ 9:46:27] 11. device factory version = LGD850AT-01-V10d-310-410-JUN-19-2014+0
[ 9:46:27] 12. device factory out version = LGD850AT-00-V10d-ATT-US-JUN-19-2014+0
[ 9:46:27] 13. pid = HD58S140925001695
[ 9:46:27] 14. imei = XXXXXXXXXXXXXXXXXXXX
[ 9:46:27] 15. model name = LG-D850
[ 9:46:27] 16. device build type = U
[ 9:46:27] 17. chipset platform = msm8974
[ 9:46:27] 18. target_operator = ATT
[ 9:46:27] 19. target_country = US
[ 9:46:27] 20. ap_factory_reset_status = 2
[ 9:46:27] 21. cp_factory_reset_status = 0
[ 9:46:27] 22. isDownloadNotFinish = 0
[ 9:46:27] 23. qem = 0
[ 9:46:27] 24. cupss swfv = FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-FFFFFFFFFFF-F
[ 9:46:27] 25. is one binary dual plan = 0
[ 9:46:27] 26. memroy size = 61071360
[ 9:46:27] 27. memory_id = 032GE4
[ 9:46:27] 28. bootloader_ver = MiniOS 3.0
[ 9:46:27] LAF : Bin_User_Mode
[ 9:46:27] isValidateSecureImage Device is a qfused.
[ 9:46:27] found sbl1 Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found aboot Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found rpm Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] found tz Partition for secure image check
[ 9:46:27] Secure Image
[ 9:46:27] Secure Image Check Success
[ 9:46:27] * Set AP factory_reset= 0
[ 9:46:27] * Set qem_reset= 1
Click to expand...
Click to collapse
I appreciate you going through this, but I don't think that you were bricked to the point that we are.
-No Download Mode
-No Recovery
-Black Screen & nothing on it.
-When plugged in via USB it shows up on the pc as: LGE AndroidNet USB Serial Port
-LG Flash Tools will not work.
-When plugged in with no battery, the screen lights up with a symbol with a battery and an exclamation point.
ElectroSh0ck said:
I appreciate you going through this, but I don't think that you were bricked to the point that we are.
-No Download Mode
-No Recovery
-Black Screen & nothing on it.
-When plugged in via USB it shows up on the pc as: LGE AndroidNet USB Serial Port
-LG Flash Tools will not work.
-When plugged in with no battery, the screen lights up with a symbol with a battery and an exclamation point.
Click to expand...
Click to collapse
That's how I was. Secure info boot < red and blue led with black screen, no factory restore. I don't know how I got TWRP to boot. I started messing around with the device manager, deleting any files stored on the computer related to any LG device (AndroidNet, QualComm, MTP, etc) along with popping the battery in with the charge screen and reading a logs.
I hope you guys can get it fixed.
Not even getting a secure info boot here. Black screen no leds
Sent from my SM-N910V using XDA Free mobile app
Same here
After rooting it and installing TRWP, I was getting an Error when rebooting into recovery "Secure Boot error". I found a solution at this page: http://forum.xda-developers.com/lg-g3/help/help-secure-boot-error-trying-to-boot-t3054977 and I was trying to replicate. At the Terminal command step "su" worked, the second line didn't, the third line worked and the final one didn't. I know that the third line bricked my phone.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot (writes “zeroes” to the partition to “wipe” it out)
Since then the phone is almost dead. No way to wake it up, I've tried every combination of buttons and USB plugin. The only signs that is alive are that when I connect it without the battery to USB it shows the with the phone connected and the yellow triangle with a question mark and that is detected as LGE Androidnet USB and modem in the Device Manager. I tried the TOT method and the KDZ method, nothing worked. In Qpst it is detected as Phone in Download Mode and in QPST Configuration as Sahara Memory Dump (Connected Phone: Q/QCP-XXX).
LGNPST detects it as UNKNOWN, only Emergency active, and doesn't do anything when trying to upload the bin file, gives Error: Could not switch to download mode.
Getting crazy here.
What DLL did you use to get LGNPST to give you that error?
ElectroSh0ck said:
What DLL did you use to get LGNPST to give you that error?
Click to expand...
Click to collapse
The default one... LGNPST_LS970.dll It was the only one that it let me use.
alex_da_fixeru said:
The default one... LGNPST_LS970.dll It was the only one that it let me use.
Click to expand...
Click to collapse
Ah okay that makes sense. We will need a DLL specific to the model of G3 that we have. It is basically telling the program how to interact with the phone in emergency mode. I have tried the DLL's used to flash TOTs, but they will not register in Windows.
ElectroSh0ck said:
Ah okay that makes sense. We will need a DLL specific to the model of G3 that we have. It is basically telling the program how to interact with the phone in emergency mode. I have tried the DLL's used to flash TOTs, but they will not register in Windows.
Click to expand...
Click to collapse
I can't seem to find the correct .dll for LG G3. Anyone has it?
Wouldn't it be the one that came with your firmware file?
Sent from my Nexus 7 using XDA Free mobile app
danmak89 said:
Wouldn't it be the one that came with your firmware file?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I would think that was the case, but they will not show up in LGNPST. I can get the ones to work that others have provided specifically for LGNPST, but not the ones used to flash a TOT with LG Flash Tool.
ElectroSh0ck said:
I would think that was the case, but they will not show up in LGNPST. I can get the ones to work that others have provided specifically for LGNPST, but not the ones used to flash a TOT with LG Flash Tool.
Click to expand...
Click to collapse
Ah man. I managed to get my device recognised as LGE AndroidNet USB Serial Port but there's still another driver that won't install and I don't know which one it would need to be.
Device just won't boot in to any mode, no LEDs, nothing. Obvious tools don't work like flashtool, b2bsupport. I'm considering swapping out the main board as they don't seem too expensive but I'm trying to see if I can solve this first.
I refuse to accept that this is 100% bricked.
Sent from my Nexus 7 using XDA Free mobile app
hi pls share htc e9+ flashtools firmware
phone is soft breack
Operation : Check / Read Info [ v1.58 ]
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey
Wait for phone...
Phone found! [ 7 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6795
BB_CPU_NME : [MediaTek] Helio[X10]|MT6795_S00
BB_CPU_EXT : 0xCA00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
[DA_ERROR] : SECURITYBOOT_BOOT_NOT_ACCEPTED
Boot Error!
Operation Failed
Elapsed: 00:00:28
Reconnect Power/Cable!
Just got a XT1789-01 from a friend whos daughters phone just abruptly stopped working. No signs of life, except when plugged in to a computer I see the QLoader 9008 driver load. I tried some blank flash that says to bring the booloader back but it did nothing but say Generic Error. The tool does seem to detect the phone though.
Any ideas? The girl that uses this phone is like 10 so I know its not been tampered with software wise to cause this.
Motorola devices are not my cup of tea when it comes to flashing.
Thanks!
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
At the bottom of the post is a link for qualcomm diag drivers, signed for windows.
Attached is the unbrick.zip, use the drivers mentioned above though. Basically unplug your phone and install the drivers, reboot pc and plug in, wait for the drivers to recognize and settle, then blankflash. Afterwards you'll be in a clean bootloader. Flash the latest firmware for your variant. This thread has instructions and links for flashing firmwares, just make sure it's for your variant. You can also try using the lmsa tool mentioned in post #275 to flash the firmware needed.
41rw4lk said:
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
At the bottom of the post is a link for qualcomm diag drivers, signed for windows.
Attached is the unbrick.zip, use the drivers mentioned above though. Basically unplug your phone and install the drivers, reboot pc and plug in, wait for the drivers to recognize and settle, then blankflash. Afterwards you'll be in a clean bootloader. Flash the latest firmware for your variant. This thread has instructions and links for flashing firmwares, just make sure it's for your variant. You can also try using the lmsa tool mentioned in post #275 to flash the firmware needed.
Click to expand...
Click to collapse
Thanks. But I still get "FAILED General error" on the blank flash.
C:\1>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ -0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 94 (0x5e)
[ 0.004] ...cpu.sn = 3695693525 (0xdc47ced5)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.007] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.016] ReadFile() failed, GetLastError()=0
[ 0.342] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.344] ERROR: sahara_download()->general error
[ 0.344] Check qboot_log.txt for more details
[ 0.345] Total time: 0.346s
FAILED: qb_flash_singleimage()->sahara_download()->general error
C:\1>pause
Press any key to continue . . .
hyelton said:
Thanks. But I still get "FAILED General error" on the blank flash.
C:\1>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ -0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 94 (0x5e)
[ 0.004] ...cpu.sn = 3695693525 (0xdc47ced5)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.007] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.016] ReadFile() failed, GetLastError()=0
[ 0.342] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.344] ERROR: sahara_download()->general error
[ 0.344] Check qboot_log.txt for more details
[ 0.345] Total time: 0.346s
FAILED: qb_flash_singleimage()->sahara_download()->general error
C:\1>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Try holding pwr+vol down, then execute the bat file
Same exact error
hyelton said:
Same exact error
Click to expand...
Click to collapse
I've only had to use that once and I didn't run into problems. Double check that the right driver is installed in your device manager, make sure you're running admin prompt (best from the folder so the path is all set). Try executing the command then plug in your phone. Make sure you're using a 2.0 usb port off the mobo and not a hub or 3+ port. Outside of those suggestions I can't help, I don't know the error correlation. I know some had issues getting to to go, but ultimately it was "things just clicked and worked this time" scenario.
The post where you got the drivers has links to unbricking guides, check those if needed.
41rw4lk said:
I've only had to use that once and I didn't run into problems. Double check that the right driver is installed in your device manager, make sure you're running admin prompt (best from the folder so the path is all set). Try executing the command then plug in your phone. Make sure you're using a 2.0 usb port off the mobo and not a hub or 3+ port. Outside of those suggestions I can't help, I don't know the error correlation. I know some had issues getting to to go, but ultimately it was "things just clicked and worked this time" scenario.
The post where you got the drivers has links to unbricking guides, check those if needed.
Click to expand...
Click to collapse
Yeah drivers are correct, laptop and desktop both usb 2.0 and 3.0 has been tried. Different usb cables, I’m assuming something has went wrong with this phone. As it’s never been tampered with. So I’ll give it a few more goes before giving up on it.
Sent from my iPhone using Tapatalk
which blank flash did you try N or O?
Same here, I think we need an updated blankflash
**** Log buffer [000001] 2019-03-14_20:10:40 ****
[ 0.000] Opening device: \\.\COM3
[ 0.004] Detecting device
[ 0.008] ...cpu.id = 94 (0x5e)
[ 0.008] ...cpu.sn = 4062057235 (0xf21e1313)
[ 0.009] Opening singleimage
[ 0.015] Loading package
[ 0.027] ...filename = pkg.xml
[ 0.037] Loading programmer
[ 0.040] ...filename = programmer.elf
[ 0.040] Sending programmer
[ 0.100] ReadFile() failed, GetLastError()=0
[ 0.370] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.454] ERROR: sahara_download()->general error
[ 0.457] Check qboot_log.txt for more details
[ 0.475] Total time: 0.489s
[ 0.485]
[ 0.485] qboot version 3.85
[ 0.485]
[ 0.485] DEVICE {
[ 0.485] name = "\\.\COM3",
[ 0.485] flags = "0x64",
[ 0.485] addr = "0x28FD64",
[ 0.485] sahara.current_mode = "0",
[ 0.485] api.buffer = "0x2525020",
[ 0.485] cpu.serial = "4062057235",
[ 0.485] cpu.id = "94",
[ 0.485] cpu.sv_sbl = "15",
[ 0.485] cpu.name = "MSM8998",
[ 0.485] storage.type = "UFS",
[ 0.485] sahara.programmer = "programmer.elf",
[ 0.485] api.bnr = "0x475FF8",
[ 0.485] }
[ 0.485]
[ 0.485]
[ 0.485] Backup & Restore {
[ 0.485] num_entries = 0,
[ 0.485] restoring = "false",
[ 0.485] backup_error = "not started",
[ 0.485] restore_error = "not started",
[ 0.485] }
[ 0.485]
Same problem here!
I think that I need some updated blankflash files. I have tried to found in 4PDA, but the link was removed, the file name was "blankflash_SPRINT_8.0.0_OCXS27.109-48-6.zip" or " blankflash_VZW_8.0.0_ODXS27.109-34-12_12.zip". I have a xt1789-05, dual sim, but I think these files can save me! Anyone have these files? Thanks.
i have this error, can you help me?
[ 0.000] Opening device: \\.\COM5
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.001s
[ 0.001]
[ 0.001] qboot version 3.85
[ 0.001]
[ 0.001] DEVICE {
[ 0.001] name = "\\.\COM5",
[ 0.001] flags = "0x60",
[ 0.001] addr = "0x62FD54",
[ 0.001] api.bnr = "0x1D2D70",
[ 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]
XxeAgLeAnGeLxX said:
i have this error, can you help me?
[ 0.000] Opening device: \\.\COM5
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.001s
[ 0.001]
[ 0.001] qboot version 3.85
[ 0.001]
[ 0.001] DEVICE {
[ 0.001] name = "\\.\COM5",
[ 0.001] flags = "0x60",
[ 0.001] addr = "0x62FD54",
[ 0.001] api.bnr = "0x1D2D70",
[ 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]
Click to expand...
Click to collapse
I was experiencing this exact same issue when running the blankflash. I ran it several times only to receive the same error over and over.
Did you put your device into EDL Mode or did it happen after a bad flash?
Do you know if your bootloader is still intact? Do you know how to exit EDL Mode to get back to the bootloader?
Here is what you do...
Since you are in EDL Mode trying to run the blankflash, get everything set up like you are about to run the blankflash again. Connect your device and verify it is connected in the Device Manager. Press and Hold Volume Down + Power and double-click the file to run the blankflash. Continue holding the Volume Down + Power while attempting to run the blankflash and if your bootloader is still intact this will take you back into the bootloader. It may take a few attempts to get back. Just keep holding the Volume Down + Power and double clicking the blankflash file until it takes you back to the bootloader.
Now, this is assuming that your bootloader is still intact. If it is and you can get back to the bootloader then you can run a flash-all for your device that matches the software you were running and get your device back to an operational state. Good luck.
pekenolucas said:
I think that I need some updated blankflash files. I have tried to found in 4PDA, but the link was removed, the file name was "blankflash_SPRINT_8.0.0_OCXS27.109-48-6.zip" or " blankflash_VZW_8.0.0_ODXS27.109-34-12_12.zip". I have a xt1789-05, dual sim, but I think these files can save me! Anyone have these files? Thanks.
Click to expand...
Click to collapse
Follow this guide it has worked for many. Make sure you read it all first, and make sure your phone is in edl mode. Your phone will have a blank screen but you'll see HS-USB QLoader 9008 in your device manager when connected to your pc.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Blank flash after reomal of battery works
hyelton said:
Just got a XT1789-01 from a friend whos daughters phone just abruptly stopped working. No signs of life, except when plugged in to a computer I see the QLoader 9008 driver load. I tried some blank flash that says to bring the booloader back but it did nothing but say Generic Error. The tool does seem to detect the phone though.
Any ideas? The girl that uses this phone is like 10 so I know its not been tampered with software wise to cause this.
Motorola devices are not my cup of tea when it comes to flashing.
Thanks!
Click to expand...
Click to collapse
Dear remove battery and then blank flash it will work
Hi. Sorry my english)
I bought a phone on Ali. I tried to install LOS16, but after flashing the phone became a black screen and QUSB_BULK.
The phone was Android 8.0.0 retcn.
When I try to restore blankflash_oreo, I get the following errors:
Code:
**** Log buffer [000001] 2019-05-01_23:10:10 ****
[ 0.000] Opening device: \\.\COM7
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 94 (0x5e)
[ 0.005] ...cpu.sn = 2549234984 (0x97f23d28)
[ 0.005] Opening singleimage
[ 0.006] Loading package
[ 0.009] ...filename = pkg.xml
[ 0.011] Loading programmer
[ 0.012] ...filename = programmer.elf
[ 0.012] Sending programmer
[ 0.084] ReadFile() failed, GetLastError()=0
[ 0.390] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.390] ERROR: sahara_download()->general error
[ 0.391] Check qboot_log.txt for more details
[ 0.391] Total time: 0.391s
[ 0.391]
[ 0.391] qboot version 3.85
[ 0.391]
[ 0.391] DEVICE {
[ 0.391] name = "\\.\COM7",
[ 0.391] flags = "0x64",
[ 0.391] addr = "0x28FD64",
[ 0.391] sahara.current_mode = "0",
[ 0.391] api.buffer = "0x2145020",
[ 0.391] cpu.serial = "2549234984",
[ 0.391] cpu.id = "94",
[ 0.391] cpu.sv_sbl = "0",
[ 0.391] cpu.name = "MSM8998",
[ 0.391] storage.type = "UFS",
[ 0.391] sahara.programmer = "programmer.elf",
[ 0.391] api.bnr = "0x2085FF8",
[ 0.391] }
[ 0.391]
[ 0.391]
[ 0.391] Backup & Restore {
[ 0.391] num_entries = 0,
[ 0.391] restoring = "false",
[ 0.391] backup_error = "not started",
[ 0.391] restore_error = "not started",
[ 0.391] }
[ 0.391]
Please share blankflash on 1789-05 for 8.0.0
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Thanks, but not work
Code:
F:\1789-05\blankflash_from_NDX26.183-15_17>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ 0.000] Opening device: \\.\COM6
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 94 (0x5e)
[ 0.004] ...cpu.sn = 2549234984 (0x97f23d28)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.008] ...filename = pkg.xml
[ 0.010] Loading programmer
[ 0.011] ...filename = programmer.elf
[ 0.011] Sending programmer
[ 0.164] Handling things over to programmer
[ 0.164] Identifying CPU version
[ 0.166] Waiting for firehose to get ready
[ 29.142] ReadFile() failed, GetLastError()=0
[ 45.246] ReadFile() failed, GetLastError()=0
[141.851] ReadFile() failed, GetLastError()=0
[156.494] Waiting for firehose to get ready
[174.054] ReadFile() failed, GetLastError()=0
[190.155] ReadFile() failed, GetLastError()=0
[206.257] ReadFile() failed, GetLastError()=0
[217.966] ...MSM8998 unknown
[217.966] Determining target secure state
[217.968] Waiting for firehose to get ready
[222.356] ReadFile() failed, GetLastError()=0
Make sure you have the drivers installed, use a 2.0 usb port off the mobo. It can be finicky, so check your cable, check your drivers, use another port. It'll work. Some have had luck by unplugging the phone, starting the script, holding vol dwn, and replugging the phone. It can be finicky, just try it again.
I try more and more, but still not work.
I try: win vista x32, win 8.1 x64, win 10 x 64,
two cables, stock and other,
drivers qualcomm x32 and x64,
desktop and notebook, other port.
I try:
blankflash_from_NDX26.183-15_17
blankflash_oreo
blankflash_SPRINT_8.0.0_OCXS27.109-48-6
I don't know what to try yet.
MarkNsk87 said:
I try more and more, but still not work.
I try: win vista x32, win 8.1 x64, win 10 x 64,
two cables, stock and other,
drivers qualcomm x32 and x64,
desktop and notebook, other port.
I try:
blankflash_from_NDX26.183-15_17
blankflash_oreo
blankflash_SPRINT_8.0.0_OCXS27.109-48-6
I don't know what to try yet.
Click to expand...
Click to collapse
Idk if anyone has been successful using the oreo blankflash, the one I linked to has been used successfully many times, so use that one. Verify that the proper driver is assigned to the phone in your device manager, and make sure you're using an administrator cmd prompt. Might try uninstalling the drivers, reboot pc, reinstall drivers, reboot pc, plug in the phone and let everything recognize and settle, verify drivers in device manager, open admin prompt and go for it with the ndx (nougat) blankflash.
I reinstalled the driver, rebooted and tried to execute the command under the administrator, the log changed a little, but still unsuccessfully
Code:
**** Log buffer [000001] 2019-05-02_13:23:28 ****
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 12.844] ReadFile() failed, GetLastError()=0
[ 13.372] ...cpu.id = 94 (0x5e)
[ 13.372] ...cpu.sn = 2549234984 (0x97f23d28)
[ 13.372] Opening singleimage
[B][ 13.372] ERROR: error opening singleimage[/B]
[ 13.388] Check qboot_log.txt for more details
[ 13.388] Total time: 13.388s
[ 13.388]
[ 13.388] qboot version 3.85
[ 13.388]
[ 13.388] DEVICE {
[ 13.388] name = "\\.\COM3",
[ 13.388] flags = "0x64",
[ 13.388] addr = "0x28FD64",
[ 13.388] sahara.current_mode = "3",
[ 13.388] api.buffer = "0x25DB020",
[ 13.388] cpu.serial = "2549234984",
[ 13.388] cpu.id = "94",
[ 13.388] cpu.sv_sbl = "0",
[ 13.388] api.bnr = "0x5D2F78",
[ 13.388] }
[ 13.388]
[ 13.388]
[ 13.388] Backup & Restore {
[ 13.388] num_entries = 0,
[ 13.388] restoring = "false",
[ 13.388] backup_error = "not started",
[ 13.388] restore_error = "not started",
[ 13.388] }
[ 13.388]
Blankflash did not work because of the Motorola_Mobile_Drivers_v6.4.0 drivers, I don’t know how they interfere, but because of them there were errors reading the device and the blankflash did not work.
I worked on my body with blankflash_from_NDX26.183-15_17 - and this is a Verizon bout campaign, judging by the information in the bootloader.
Important all have brick: uninstall Motorola_Mobile_Drivers, before you start blankflash!
Don't wory Mark. I think I have the same gold retcn version of 1789-05. I tried flash some versions of LOS 15 and 16, always ends with Qualcomm mode. For me works blankflash from nougat, but only when battery is less than 10%. When my phone is fully charged, when I try blankflash the phone reconnect to pc. Take me a few evenings to figure it out. Works with Motorola drivers and Qualcomm certificate driver installed in the same time.
Now I have stock EU 8.0 and radio from retcn.
Works everything except Smart lock.
Good luck.
Wysłane z mojego Moto Z (2) przy użyciu Tapatalka
I get this error, can someone help me?
[ 0.000] Opening device: \\.\COM7
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 94 (0x5e)
[ 0.007] ...cpu.sn = 2357123697 (0x8c7eda71)
[ 0.007] Opening singleimage
[ 0.008] Loading package
[ 0.013] ...filename = pkg.xml
[ 0.015] Loading programmer
[ 0.017] ...filename = programmer.elf
[ 0.017] Sending programmer
[ 0.181] Handling things over to programmer
[ 0.182] Identifying CPU version
[ 0.185] Waiting for firehose to get ready
[ 3.642] ...MSM8998 2.1
[ 3.804] Determining target secure state
[ 3.987] ...secure = yes
[ 4.334] Configuring device...
[ 4.361] Skipping UFS provsioning as target is secure
[ 4.362] Configuring device...
[ 5.938] Target NAK!
[ 5.939] ...ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 1
[ 5.939] ...ERROR: Failed to open the device 3 slot 0 partition 1
[ 5.940] ...INFO: Device type 3, slot 0, partition 1, error 0
[ 5.940] ...WARN: Set bootable failed to open 3 slot 0, partition 1, error 0
[ 5.940] ERROR: do_package()->do_recipe()->NAK
[ 5.942] Check qboot_log.txt for more details
[ 5.943] Total time: 5.946s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->NAK
Thank you
41rw4lk said:
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
thanks this method heleped me
you need a blank flash updated for your bootloader, theres at least 5 updates on oreo (OTA UPDATES), then you will need the latest blankflash compatible, maybe the Oreo blank flash that you found here is older than your bricked bootloader. (Sorry for my bad english)
iurd2007 said:
you need a blank flash updated for your bootloader, theres at least 5 updates on oreo (OTA UPDATES), then you will need the latest blankflash compatible, maybe the Oreo blank flash that you found here is older than your bricked bootloader. (Sorry for my bad english)
Click to expand...
Click to collapse
This is a bit of an old post, and I assume those issues are resolved, not sure who you're addressing. As far as oreo blankflash, there is one but as far as I know no one has had success with it. The one that I post frequently uses nougat believe it or not, but it has worked many many times even on oreo and there is no reason to mess with what works. Especially when it comes to blankflashing, it's usually your last chance to resolve the problem.
41rw4lk said:
This is a bit of an old post, and I assume those issues are resolved, not sure who you're addressing. As far as oreo blankflash, there is one but as far as I know no one has had success with it. The one that I post frequently uses nougat believe it or not, but it has worked many many times even on oreo and there is no reason to mess with what works. Especially when it comes to blankflashing, it's usually your last chance to resolve the problem.
Click to expand...
Click to collapse
To blankflash Oreo , you need oreo blankflash, but the last version. There is a oreo (soak test) but not the official stock. But recently someone post the final blankflash for the latest OTA.
iurd2007 said:
To blankflash Oreo , you need oreo blankflash, but the last version. There is a oreo (soak test) but not the official stock. But recently someone post the final blankflash for the latest OTA.
Click to expand...
Click to collapse
You're mistaken. I won't argue the point, by all means do what you will.
41rw4lk said:
You're mistaken. I won't argue the point, by all means do what you will.
Click to expand...
Click to collapse
Ok...
Hi, looking for a kind soul who can provide me with some insight or direction.
My Phone:
Moto Z2 Force XT1789-04 AT&T
Carrier unlocked with unlock code from AT&T to use T-Mobile SIM
Updated to either Build number: OCXS27.109-47-20 or Build number: OCXS27.109-47-23 using LMSA (not OTA)
Official build, never tried to root it
My Circumstance:
I was using fingerprint unlock and my login attempts were failing.
In a brief moment of frustration, and stupidity, I repeatedly retried FP unlock (probably 10+ times)
Display went dim and phone became unresponsive, and ultimately turned into a brick with no way to power on; nothing displayed when plugged in to charge.
My Attempts to Fix:
After trying various button reset options with no success, I plugged my phone into my PC and saw QUSB_BULK
Further searching led me to https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5 (thanks 41rw4lk)
I installed the Qualcomm driver and got Qualcomm HS-USB QDLoader 9008 to show up in Device Manager.
I tried blank-flash.bat using blankflash_from_NDX26.183-15_17 (again, thanks, 41rw4lk)
Here is the output from the batch command:
Code:
c:\Downloads\MOTOZ2FORCE\blankflash_from_NDX26.183-15_17>blank-flash.bat
c:\Downloads\MOTOZ2FORCE\blankflash_from_NDX26.183-15_17>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ -0.000] Opening device: \\.\COM4
[ -0.000] Detecting device
[ 0.016] ...cpu.id = 94 (0x5e)
[ 0.016] ...cpu.sn = 1009594148 (0x3c2d2f24)
[ 0.016] Opening singleimage
[ 0.016] Loading package
[ 0.016] ...filename = pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.elf
[ 0.016] Sending programmer
[ 0.176] Handling things over to programmer
[ 0.176] Identifying CPU version
[ 0.176] Waiting for firehose to get ready
[ 3.200] ...MSM8998 2.1
[ 3.200] Determining target secure state
[ 3.200] ...secure = yes
[ 3.247] Configuring device...
[ 3.263] Skipping UFS provsioning as target is secure
[ 3.263] Configuring device...
[ 4.824] Target NAK!
[ 4.824] ...ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 1
[ 4.824] ...ERROR: Failed to open the device 3 slot 0 partition 1
[ 4.824] ...INFO: Device type 3, slot 0, partition 1, error 0
[ 4.824] ...WARN: Set bootable failed to open 3 slot 0, partition 1, error 0
[ 4.824] ERROR: do_package()->do_recipe()->NAK
[ 4.824] Check qboot_log.txt for more details
[ 4.824] Total time: 4.824s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->NAK
Here is the device info from the log:
Code:
[ 4.824] qboot version 3.85
[ 4.824]
[ 4.824] DEVICE {
[ 4.824] name = "\\.\COM4",
[ 4.824] flags = "0x144",
[ 4.824] addr = "0x62FD54",
[ 4.824] sahara.current_mode = "0",
[ 4.824] api.buffer = "0x29C4020",
[ 4.824] cpu.serial = "1009594148",
[ 4.824] cpu.id = "94",
[ 4.824] cpu.sv_sbl = "0",
[ 4.824] cpu.name = "MSM8998",
[ 4.824] storage.type = "UFS",
[ 4.824] sahara.programmer = "programmer.elf",
[ 4.824] module.firehose = "0x6D91C8",
[ 4.824] api.firehose = "0x721F50",
[ 4.824] cpu.ver = "513",
[ 4.824] cpu.vername = "2.1",
[ 4.824] fh.max_packet_sz = "1048576",
[ 4.824] fh.storage_inited = "1",
[ 4.824] }
So, best as I can decipher, the blank-flash is failing because it cannot create a filesystem on the internal memory.
I read something about A/B slots, but I'm starting to lose my way.
Am I done for?
Thanks for looking. Truly appreciate the folks in this community.
Wait! Am I using a Nougat blank-flash? Do I need an Oreo blank-flash? Is there one available for the XT1789-04?
lobbybee said:
Wait! Am I using a Nougat blank-flash? Do I need an Oreo blank-flash? Is there one available for the XT1789-04?
Click to expand...
Click to collapse
See if there is one on
https://mirrors.lolinet.com/firmware/moto
Sent from my Moto E (4) using Tapatalk
The Nougat blankflash is fine. The phone shipped with a Nougat pbl and the way I understand it is that can't be modified or upgraded, it can be reflashed with the same, but that's it. Don't quote me on that though. As for an Oreo blankflash, there is one, but I've never heard any success stories from it and Nougat has always done the trick.
I've seen that error before, it is speculated that maybe the storage is failing, but I don't know if anyone has ever been able to say 'yes, your storage is no good and that's why you get this error' etc. It maybe very well be the case and I'm not sure if those who have faced that error have been able to recover.
What version of windows are you running? Have you tried running as an admin, using different ports?
If you are on Win10 have you tried going old school and disabling integrity checks and turning test signing on? Win10 isn't very friendly when it comes to our phone, we recommend Win7 and command prompt, not powershell. So if you're using Win10 and haven't done the above, it's worth a shot.
41rw4lk said:
What version of windows are you running? Have you tried running as an admin, using different ports?
Click to expand...
Click to collapse
Previously on Win10 as Admin from CMD window.
Also just tried on Win7, per suggestion, with the same results.
I used 3 different USB2 ports on the PC, iterated through 3 different USB-C cables.
I found the --debug=2 flag for qboot.exe and started digging through the output. Now it's got me wondering:
1) Why is it specifying UFS instead of eMMC? Phonemore.com specs says it's UFS 2.1
2) It appears to be skipping storage initialization because "target is secure." Is blankflash failing b/c my bootloader was not unlocked before it bricked?
3) Should I look into using QFIL to manually configure the reinitialization of the file system, whether UFS or eMMC?
lobbybee said:
Previously on Win10 as Admin from CMD window.
Also just tried on Win7, per suggestion, with the same results.
I used 3 different USB2 ports on the PC, iterated through 3 different USB-C cables.
I found the --debug=2 flag for qboot.exe and started digging through the output. Now it's got me wondering:
1) Why is it specifying UFS instead of eMMC? Phonemore.com specs says it's UFS 2.1
2) It appears to be skipping storage initialization because "target is secure." Is blankflash failing b/c my bootloader was not unlocked before it bricked?
3) Should I look into using QFIL to manually configure the reinitialization of the file system, whether UFS or eMMC?
Click to expand...
Click to collapse
I believe the pbl is loaded before bootloader lock is detected, hence the reason it was able to exploit and unlock booloaders. Obviously we all can agree that something is failing when it comes to initializing the UFS storage it needs to write to. Whether it is corrupted, dead, or something else... I'm not knowledgeable enough to answer that. You might explore around with QFIL since it has an option in settings to select storage type, emmc or ufs. What you do from here on out is all you. I'd make sure you have your drivers installed and do only what is necessary to get back to a bootloader where you can flash a clean stock firmware. Keep us posted with your results and good luck.