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
solved
TheFixItMan said:
This guide is for hard bricked Moto G5 Cedric
Hard bricked means a device which can not enter bootloader mode normally
This method has now been confirmed working
XT1672 32gb version (also works with XT1670 XT1671 and XT1676)
Download mmcblk0 image from here
Thanks to @jcbotelho for providing image
Requirements
Freshly formatted microSD card of at least 32gb
7zip
Linux mint live usb/dvd
USB card reader
Method
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-stick or pendrive that is at least 8gb
0) Put the Moto g5 on mains charge until you have finished flashing the sdcard so it's fully charged ready for the boot test!
1) Run linux, preferable cinnamon or mate versions of linux Mint
2) Insert the sdcard in pc or card reader and open "Disks" app
3) In "Disks" app select sdcard and you will see the sdcard partitions
4) Press "-" to delete the partition (delete all partitions if there is 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 the sdcard has (/dev/sd??) and then close the "Disks" app
7) Go to Desktop, open "Computer" and navigate to the location when the img file is extracted (mmcblk0.img)
8) Open the window where img file is with root (right click on window and select "open as root")
9) In root window open the Terminal (right click on window and select "open terminal")
no need to type "su" in terminal, it has root already (see notes if using Linux live usb/dvd)
10) Type in terminal the comand written below and dont forget to eliminate that "1" from the sdcard path,
that "1" can make the differnce betwen phone boot or not!!!!!
Things to note
Linux Live dvd doesn't have open as root so just open in terminal and add sudo to the start of the commands
I've included this in the commands below
If you get a status error just remove status=progress from the terminal command below
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal aply that comand:
sudo 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:
sudo dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
and the flashing process should start
when it finishes, test the sdcard in the phone and it should boot!
If you get a size error of the sdcard in terminal you have to change the sdcard and try again!
Thanks to vaserbanix for the guide
Re-flash Stock Firmware
Once the phone is in bootloader mode you can flash stock firmware via fastboot
Note that in order to flash gpt the firmware MUST be the same or newer than the version currently on your phone
Once you have firmware that is the same or newer than your current version you can remove the sd card and run these commands (assuming you have fastboot all setup on your pc)
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (ignore any error)
fastboot erase clogo (ignore any error)
fastboot oem fb_mode_clear
fastboot reboot
Imei fix
If your imei is 0 then follow instructions from here
You should be able to restore stock after & keep imei
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Something went wrong and now it does not start, only the led lights when it is connected to the pc. Only Qualcomm HS-USB QDLoader 9008 appears in the device manager.
I have tried several blankflash (1, 2, 3) but it does not work.
Also with Qfil and the same result.
Code:
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM3
OKAY [ 0.023s]
greeting device for command mode
ReadFile() failed, error=995
opening device: \\.\COM3
opening device: \\.\COM3
OKAY [ 0.008s]
greeting device for command mode
OKAY [ 0.010s]
identifying device
...serial = 0x1B9ACE0A
...chip-id = 0x4F
...chip-rev = 0x0
...sv-sbl = 0x1
OKAY [ 0.038s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.020s]
validating files
OKAY [ 0.002s]
switching to download mode
OKAY [ 0.004s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
:crying:
thanks in advance
Its call Hardbrick, dont have for now any flashbank for motog5
Seriously ? And do you know if there will be?
takoa said:
Seriously ? And do you know if there will be?
Click to expand...
Click to collapse
It will never be released officially - Motorola don't release these files - they are either leaked or someone modifies existing files
You can try
www.kriztekblog.com/2016/10/how-to-flash-qualcomm-mbn-firmware-qpst-tool.html/amp
The firehose file I'll put in the attachment below - Unzip it
Make sure you install everything & put all files in root of c: keep paths short with no spaces eg c:/flashtool
Iv no idea what else maybe required as I don't have this device anymore & even if I did I'd only test it if my device needed reimaging
Your only other option is a motherboard replacement or a repair shop with the equipment to reimage devices eg via a j-tag
more files are missing
TheFixItMan said:
It will never be released officially - Motorola don't release these files - they are either leaked or someone modifies existing files
You can try
www.kriztekblog.com/2016/10/how-to-flash-qualcomm-mbn-firmware-qpst-tool.html/amp
The firehose file I'll put in the attachment below - Unzip it
Make sure you install everything & put all files in root of c: keep paths short with no spaces eg c:/flashtool
Iv no idea what else maybe required as I don't have this device anymore & even if I did I'd only test it if my device needed reimaging
Your only other option is a motherboard replacement or a repair shop with the equipment to reimage devices eg via a j-tag
Click to expand...
Click to collapse
you will have the other path and xml files missing, Has someone already worked with you? tendras los demas archivos path y xml que falta, alguien ya le funciono con exito este metodo?
oxxo.andatti said:
you will have the other path and xml files missing, Has someone already worked with you? tendras los demas archivos path y xml que falta, alguien ya le funciono con exito este metodo?
Click to expand...
Click to collapse
You will either have to find one that works or develop your own if the ones that come with the program don't work
Like I said - I no longer have this phone & Iv tested nothing - I can provide ideas it's up to you to research alot of searching & come up with the solution
I have tried all the possible ways that I have found here and on the net ... and nothing. Still the same. Hopefully it will be soon the release of blankflash. I look forward to it. ?
work for me
takoa said:
I have tried all the possible ways that I have found here and on the net ... and nothing. Still the same. Hopefully it will be soon the release of blankflash. I look forward to it.
Click to expand...
Click to collapse
I found something that revive meu cedric that was only with LED blinking...
when conected to pc was found something like qualcomm 9008...
I'll get those files at my windows pc and can send to you
but is a kind of blankflash, write the bootloader and flash the room...
maybe i can get those files tomorow
carlapazin said:
I found something that revive meu cedric that was only with LED blinking...
when conected to pc was found something like qualcomm 9008...
I'll get those files at my windows pc and can send to you
but is a kind of blankflash, write the bootloader and flash the room...
maybe i can get those files tomorow
Click to expand...
Click to collapse
please, as soon as possible
thank you very much
:fingers-crossed::fingers-crossed::fingers-crossed:
files
takoa said:
please, as soon as possible
thank you very much
:fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
done!
just follow the sequence:
1 - blankflash
2 - bootloader gpt
then you can write de ROM with RSD or ADB
let me know if i could help you
drive.google.com/open?id=1pFMczSqIaw9qOPIuU2bywKEAgpeF41v_
carlapazin said:
done!
just follow the sequence:
1 - blankflash
2 - bootloader gpt
then you can write de ROM with RSD or ADB
let me know if i could help you
drive.google.com/open?id=1pFMczSqIaw9qOPIuU2bywKEAgpeF41v_
Click to expand...
Click to collapse
carla that so works in the Motorola cedric already proven it?
NABECKER16 said:
carla that so works in the Motorola cedric already proven it?
Click to expand...
Click to collapse
It works fo me!
carlapazin said:
It works fo me!
Click to expand...
Click to collapse
do you think it works on my moto g5 xt1672 from at & t mex
carlapazin said:
done!
just follow the sequence:
1 - blankflash
2 - bootloader gpt
then you can write de ROM with RSD or ADB
let me know if i could help you
drive.google.com/open?id=1pFMczSqIaw9qOPIuU2bywKEAgpeF41v_
Click to expand...
Click to collapse
it does not work
can you tell us what steps you have followed, the operating system you use, the driver used and so on?
not working in xt1672
takoa said:
it does not work
can you tell us what steps you have followed, the operating system you use, the driver used and so on?
Click to expand...
Click to collapse
I did with battery fully charged!
The bootloader of my XT1676 was locked
used the .bat file in:
1 - blankflash (the phone will restart on fastbot mode)
then the .bat file on 2 - bootloader gpt
again in fastboot mode, you can flash the early rom using ADB or RSD Lite.
my OS = Windows 7 (test mode active)
and the driver i've downloaded from anywere here at xda....
on windows the phone is show qualcomm 9008 (something like that)
oh yeah! uninstall all motorola drivers and just keep the qualcomm!!!
if u don't find those drivers, i can upload
---------- Post added 27th April 2018 at 12:04 AM ---------- Previous post was 26th April 2018 at 11:59 PM ----------
NABECKER16 said:
not working in xt1672
Click to expand...
Click to collapse
Sorry, bro...
Mine is XT1676... but I'm from Brazil... and the official model here is XT1672... I can look for something to ya
carlapazin said:
I did with battery fully charged!
The bootloader of my XT1676 was locked
used the .bat file in:
1 - blankflash (the phone will restart on fastbot mode)
then the .bat file on 2 - bootloader gpt
again in fastboot mode, you can flash the early rom using ADB or RSD Lite.
my OS = Windows 7 (test mode active)
and the driver i've downloaded from anywere here at xda....
on windows the phone is show qualcomm 9008 (something like that)
oh yeah! uninstall all motorola drivers and just keep the qualcomm!!!
if u don't find those drivers, i can upload
---------- Post added 27th April 2018 at 12:04 AM ---------- Previous post was 26th April 2018 at 11:59 PM ----------
Sorry, bro...
Mine is XT1676... but I'm from Brazil... and the official model here is XT1672... I can look for something to ya
Click to expand...
Click to collapse
takoa said:
[ 0.000] Opening device: \\.\COM5
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 79 (0x4f)
[ 0.000] ...cpu.sn = 463130122 (0x1b9ace0a)
[ 0.000] Opening singleimage
[ 0.000] ERROR: error opening singleimage
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.010s
[ 0.000]
[ 0.000] qboot version 3.40
[ 0.000]
[ 0.000] DEVICE {
[ 0.000] name = "\\.\COM5",
[ 0.000] flags = "0x64",
[ 0.000] addr = "0x28FE6C",
[ 0.000] sahara.current_mode = "3",
[ 0.000] api.buffer = "0x24F0020",
[ 0.000] cpu.serial = "463130122",
[ 0.000] cpu.id = "79",
[ 0.000] cpu.sv_sbl = "1",
[ 0.000] api.bnr = "0x652D78",
[ 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]
Click to expand...
Click to collapse
takoa said:
Click to expand...
Click to collapse
let's find another singleImage.... that's the only i've got
sorry, man
carlapazin said:
let's find another singleImage.... that's the only i've got
sorry, man
Click to expand...
Click to collapse
Maybe the image is corrupted when you uploaded it, since it cant be opened.
carlapazin said:
let's find another singleImage.... that's the only i've got
sorry, man
Click to expand...
Click to collapse
Hi. What I do not understand is because it does not work and it gives error being my terminal is the same model as yours, xt1676.
Use w7x64, unlocked bootloader, test mode, compilation 7601 and the correct qualcomm drivers.
Something I have or have overlooked.
Hi everybody.
As I know that it is possible that someone wants to know why I need a deep cable here is a super summary of my catastrophe:
I made a root in my Z2 Force with the bootloader unlocked (thanks to the number that Motorola gives to do that) and with the SU, after that I knew (not before, damn) that some applications don't work on root cell phones (****) among these my bank app, Netflix app, Fox app (**** **** ****), even using the Root Cloak app and others like that the result is that they don't work, so I needed to return to the unroot state, until there everything manageable, buuuuuuuuut, when I had to flash the stock ROM I downloaded the wrong version (fuuuuuuuck), the result was that the cell phone doesn't recognize the SIM cards, doesn't allow the use of WIFI, my IMEI was lost (wtf!) and when I try to flash again (in fastboot) with the correct ROM stock the bootloader doesn't leave me because it says "Flashing_locked", (what? but if I already unlocked it before !, well no, the ****ing cell phone doesn't recognize that, if I try to unblock it through the fastboot commands give as results that the process was satisfactory, but when restarting the bootloader it says NO, I'm still locked mother****er ! ...........
Well, that's why I need a deep cable, to flash with the (foolish) "Flasing_locked" status. So, the problem is basically that I found on the Internet those who do the deep cable with micro-usb, I haven't found how to do it with a usb-c cable. In the cases with micro-usb you only have to bridge the black and green wires and "ta dah" everything is done, in others I also see in micro-usb the pin 4 is jumpered with pin 1 in the micro-usb connector, but on the usb-c cable I have something like 20 pins and more than 4 cables, so I don't know how I can do the deep cable with a usb-c.
Please, I need help :crying:
I think there is another way to go about this than putting your devices into Qualcomm 9008. That is what you are wanting the EDL Deep Cable for, right? Instead of that, why not try this thread here, https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783, and see if Uzephi's method doesnt get you back to stock. If for some reason his flashall doesnt work, then I would suggest using a blankflash for your version of Android to wipe the slate clean and then use the return to stock method for your device.
fast69mopar said:
I think there is another way to go about this than putting your devices into Qualcomm 9008. That is what you are wanting the EDL Deep Cable for, right? Instead of that, why not try this thread here, https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783, and see if Uzephi's method doesnt get you back to stock. If for some reason his flashall doesnt work, then I would suggest using a blankflash for your version of Android to wipe the slate clean and then use the return to stock method for your device.
Click to expand...
Click to collapse
Okay ! I'm going to try those two options and I'll write you what happens.
Thanks !
Well, I'm here again.
I tried the two methods that you kindly indicated to me:
1. https://forum.xda-developers.com/z2-...print-t3694783 The Flashall.bat file really does not do anything different than being an automated flash of what you can usually do manually, I mean, it does the flash using the fastboot file by file, so because it's the same process (but automated) I got the same result, when the Flashall.bat file tries to send / flash the files the response status is Failed, because the flashing status in the bootloader is locked.
2. Blankflash metod. This method seems to work when the cell phone is bricked and does not enter the bootloader, and that is not my case because I can access the cell phone, for example if I connect the cell phone to the computer in:
a) the boot manager mode, the "Device Manager" recognizes it as "Android Device / Motorola ADB Interface"
b) started the ROM (and activated the "USB Debugging"), the "Device Manager" also recognizes it as "Android Device / Motorola ADB Interface"
c) QCOM mode (selected from the bootloader) the "Device Manager" recognizes it as "Qualcomm HS-USB Diagnostics 9092".
Anyway, if I run the blank-flash file in:
a) bootloader mode, the CMD shows "waiting device" and does nothing
b) started the ROM (and activated the "USB Debugging"), the CMD shows "waiting device" and does nothing
c) QCOM mode (selected from the bootloader), the CMD shows "waiting for the device" and does nothing (this same result with or without the activation of "USB Debugging")
So I'm still the same, I think my only option is Deep Cable, what do you think?
Loperaco said:
Well, I'm here again.
I tried the two methods that you kindly indicated to me:
1. https://forum.xda-developers.com/z2-...print-t3694783 The Flashall.bat file really does not do anything different than being an automated flash of what you can usually do manually, I mean, it does the flash using the fastboot file by file, so because it's the same process (but automated) I got the same result, when the Flashall.bat file tries to send / flash the files the response status is Failed, because the flashing status in the bootloader is locked.
2. Blankflash metod. This method seems to work when the cell phone is bricked and does not enter the bootloader, and that is not my case because I can access the cell phone, for example if I connect the cell phone to the computer in:
a) the boot manager mode, the "Device Manager" recognizes it as "Android Device / Motorola ADB Interface"
b) started the ROM (and activated the "USB Debugging"), the "Device Manager" also recognizes it as "Android Device / Motorola ADB Interface"
c) QCOM mode (selected from the bootloader) the "Device Manager" recognizes it as "Qualcomm HS-USB Diagnostics 9092".
Anyway, if I run the blank-flash file in:
a) bootloader mode, the CMD shows "waiting device" and does nothing
b) started the ROM (and activated the "USB Debugging"), the CMD shows "waiting device" and does nothing
c) QCOM mode (selected from the bootloader), the CMD shows "waiting for the device" and does nothing (this same result with or without the activation of "USB Debugging")
So I'm still the same, I think my only option is Deep Cable, what do you think?
Click to expand...
Click to collapse
To use blankflash you need to be in 9008 mode, since you have adb working try issuing the command 'adb reboot-edl' or 'adb reboot edl' can't recall at the moment. You'll know when you're in edl/9008 mode because the screen will be blank and the device will recognize as 9008. If you can't reboot to edl through adb, go to fastboot and try 'fastboot oem blankflash' again you'll know when you're ready for blankflash because the device will recognize as 9008. If the commands don't take, boot into QCOM mode and try 'fastboot oem blankflash'
*To unlock the bootloader you need to select oem unlock in settings. If it's greyed out you need to connect to internet and sign into google. Try bluetooth connection or a cable since wifi and mobile is borked at the moment.
41rw4lk said:
To use blankflash you need to be in 9008 mode, since you have adb working try issuing the command 'adb reboot-edl' or 'adb reboot edl' can't recall at the moment. You'll know when you're in edl/9008 mode because the screen will be blank and the device will recognize as 9008. If you can't reboot to edl through adb, go to fastboot and try 'fastboot oem blankflash' again you'll know when you're ready for blankflash because the device will recognize as 9008. If the commands don't take, boot into QCOM mode and try 'fastboot oem blankflash'
*To unlock the bootloader you need to select oem unlock in settings. If it's greyed out you need to connect to internet and sign into google. Try bluetooth connection or a cable since wifi and mobile is borked at the moment.
Click to expand...
Click to collapse
Hi.
I have fresh news.
The first thing I tried was to enable the option to unlock the OEM because that option was in gray, try to connect the internet via USB cable and no option worked, but when connecting by bluetooth (which is not easy either for those who don’t know how) I did it! and once connected, I enabled the option again, so I activated it to allow me to unlock the OEM, but when restarting the bootloader to verify it was still showing the status "Flashing_locked" (sad face).
Even knowing this, try the options in this order and with these results:
1. Try the command 'adb reboot-edl' or 'adb reboot edl'. The first command that the console recognized was 'adb reboot -edl' but once accepted by the CMD the cell phone was rebooted alone and went back to the ROM, that is, it was not blank.
2. Go to fastboot and try 'fastboot oem blankflash'. When doing this the result obtained in the CMD was “(bootloader) Command Restricted FAILED (remote failure) finished. total time: 0.006s”, probably due to the fact that the bootloader still indicates "Flashing_locked".
3. Boot into QCOM mode and try 'fastboot oem blankflash'. When I start the QCOM option from the bootloader the cell phone automatically loads the ROM, after this I activated the USB Debugging and ran the command in question but the result was "<waiting for any device>" and nothing happens. I tried the command again without activating the USB Debugging and nothing happened either. If I enter the command "fastboot devices" the command does not give any results, I give way to the next line as if nothing happened.
4. I was sad after all this so I decided to retry everything, starting with the command to put the phone in mode 9008, so, just out of curiosity I tried the second sentence you wrote, that is, 'adb reboot edl' (without the line in the middle before the word “edl”), this command also recognized it but this time if it went to blank (yeah !!!). So after accomplishing this I followed the instructions of https://forum.xda-developers.com/z2-force/help/hard-bricked-blankflash-z2-force-t3705789, but the result when executing the Blank-Flash file was:
[ 0.000] Opening device: \\.\COM11
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 94 (0x5e)
[ 0.005] ...cpu.sn = 3632543294 (0xd884363e)
[ 0.005] Opening singleimage
[ 0.005] Loading package
[ 0.009] ...filename = pkg.xml
[ 0.012] Loading programmer
[ 0.012] ...filename = programmer.elf
[ 0.013] Sending programmer
[ 0.091] ReadFile() failed, GetLastError()=0
[ 0.644] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.644] ERROR: sahara_download()->general error
[ 0.644] Check qboot_log.txt for more details
[ 0.645] Total time: 0.646s
[ 0.645]
[ 0.645] qboot version 3.85
[ 0.645]
[ 0.645] DEVICE {
[ 0.645] name = "\\.\COM11",
[ 0.645] flags = "0x64",
[ 0.645] addr = "0x28FD74",
[ 0.645] sahara.current_mode = "0",
[ 0.645] api.buffer = "0x2160020",
[ 0.645] cpu.serial = "3632543294",
[ 0.645] cpu.id = "94",
[ 0.645] cpu.sv_sbl = "0",
[ 0.645] cpu.name = "MSM8998",
[ 0.645] storage.type = "UFS",
[ 0.645] sahara.programmer = "programmer.elf",
[ 0.645] api.bnr = "0x20C7ED0",
[ 0.645] }
[ 0.645]
[ 0.645]
[ 0.645] Backup & Restore {
[ 0.645] num_entries = 0,
[ 0.645] restoring = "false",
[ 0.645] backup_error = "not started",
[ 0.645] restore_error = "not started",
[ 0.645] }
[ 0.645]When executing the "blank-flash" file again, the result obtained was:
[ 0.000] Opening device: \\.\COM11
[ 0.001] Detecting device
[ 34.005] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.005] Check qboot_log.txt for more details
[ 34.005] Total time: 34.006s
[ 34.005]
[ 34.005] qboot version 3.85
[ 34.005]
[ 34.005] DEVICE {
[ 34.005] name = "\\.\COM11",
[ 34.005] flags = "0x64",
[ 34.005] addr = "0x28FD74",
[ 34.005] api.bnr = "0x612CA8",
[ 34.005] }
[ 34.005]
[ 34.005]
[ 34.005] Backup & Restore {
[ 34.005] num_entries = 0,
[ 34.005] restoring = "false",
[ 34.005] backup_error = "not started",
[ 34.005] restore_error = "not started",
[ 34.005] }
[ 34.005]I thought I had made a worse mistake, but turning off the cell phone normally returned to enter the ROM without problem.
At this point I was left with no more ideas...
You need drivers so that your pc and the phone can communicate, here is a link and it also has a verified blankflash.zip that has worked many times for others in the past. The process is a bit hit and miss, meaning it can be finicky on some pcs. Make sure you use a usb 2.0 port off the mobo, and not a 3.0+ or a hub port, they're not all so universal and can cause problems, so stick to 2.0 mobo ports.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
41rw4lk said:
You need drivers so that your pc and the phone can communicate, here is a link and it also has a verified blankflash.zip that has worked many times for others in the past. The process is a bit hit and miss, meaning it can be finicky on some pcs. Make sure you use a usb 2.0 port off the mobo, and not a 3.0+ or a hub port, they're not all so universal and can cause problems, so stick to 2.0 mobo ports.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
Hiiiii.
Well, the file in the forum that you gave me works! I mean, it does something new, it generates a successful process and it was reinitiated to the bootloader, once there I noticed that there was a changed item "Software status: Official" (previously said modified), but the ítem of "Flashing_locked" is still the same ...
Anyway I tried to flash the stock ROM with that and I have the same result whenhen I get to the command "fastboot flash bootloader bootloader.img", here are the results:
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9884 KB) OKAY [ 0.266s]
Writing 'bootloader' (bootloader) Validating 'boot
loader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Another new thing found: in "bootloader logs" mode it says:
SSM: abl cvs roll back 0,1
Fastboot Reason: UTAG bootmode configured as fastboot
I feel that I am closer to each step, please continue to help me.
What firmware are you trying to flash? At this point it might be easier to use the lenovo moto smart assistant tool to do a rescue on your phone. Do a 'fastboot reboot bootloader' to get a fresh bootloader session, and run the lmsa tool and see it it will recover your phone. Either way, let me know what firmware you're trying to flash.
First of all, you need to make sure you are xt1789-? ? If x is 3, then he is the s version. You only need to install the rom of the corresponding carrier. I remember that the installation tool can choose whether to install the baseband and bp/bl lock (maybe)So your xt1789-? ? What is it?
Refer to the version number in the link image https://m.facebook.com/story.php?story_fbid=624595458056701&id=100015187571561
41rw4lk said:
What firmware are you trying to flash? At this point it might be easier to use the lenovo moto smart assistant tool to do a rescue on your phone. Do a 'fastboot reboot bootloader' to get a fresh bootloader session, and run the lmsa tool and see it it will recover your phone. Either way, let me know what firmware you're trying to flash.
Click to expand...
Click to collapse
Hi again !
I followed his advice to use the "lenovo moto smart assistant tool" but as a result I got that my device isn't supported by the software (see attached image).
On the other hand, regarding the firmware that I'm trying to recover, I don't know if I remembered that I told him to install a wrong ROM at the beginning of my problem, and I never backed up my original ROM, so I do not really have the least idea of what is my stock ROM (for Colombia - South America), if I search for firmware I find many categorized with letters at the beginning (AMXBR, AMXCO, AMXLA, AMXMX, ATT, ATTM, LRA, OPENMX, RETAIL, RETAPAC, RETBR, RETCN, RETEU, RETIN, RETLA, RETRU , SPRINT, TEFBR, TIMBR, TIMIT, TMO, USC, VFEU, VZW) ... investigate how I can know which was the original of my phone (after having made a mess) and can not find any reference in this regard.
I keep trying.
潇霄小云 said:
First of all, you need to make sure you are xt1789-? ? If x is 3, then he is the s version. You only need to install the rom of the corresponding carrier. I remember that the installation tool can choose whether to install the baseband and bp/bl lock (maybe)So your xt1789-? ? What is it?
Refer to the version number in the link image https://m.facebook.com/story.php?story_fbid=624595458056701&id=100015187571561
Click to expand...
Click to collapse
Hi 潇 霄 小云!
I am sure it is an XT1789-05 however I do not know which firmware corresponds to me (never look before deleting my stock ROM) and when looking for the firmware of my device there are many with many letters at the beginning (AMXBR, AMXCO, AMXLA, AMXMX, ATT, ATTM, LRA, OPENMX, RETAIL, RETAPAC, RETBR, RETCN, RETEU, RETIN, RETLA, RETRU , SPRINT, TEFBR, TIMBR, TIMIT, TMO, USC, VFEU, VZW), so I do not know which one corresponds to me for Colombia (South America).
You can not see my model in the image you send me ...
Thanks for the help, I'm still investigating!
Loperaco said:
Hi again !
I followed his advice to use the "lenovo moto smart assistant tool" but as a result I got that my device isn't supported by the software (see attached image).
On the other hand, regarding the firmware that I'm trying to recover, I don't know if I remembered that I told him to install a wrong ROM at the beginning of my problem, and I never backed up my original ROM, so I do not really have the least idea of what is my stock ROM (for Colombia - South America), if I search for firmware I find many categorized with letters at the beginning (AMXBR, AMXCO, AMXLA, AMXMX, ATT, ATTM, LRA, OPENMX, RETAIL, RETAPAC, RETBR, RETCN, RETEU, RETIN, RETLA, RETRU , SPRINT, TEFBR, TIMBR, TIMIT, TMO, USC, VFEU, VZW) ... investigate how I can know which was the original of my phone (after having made a mess) and can not find any reference in this regard.
I keep trying.
Click to expand...
Click to collapse
Well your device is showing -05, that's Mexico and South America I believe. There should be a model printed by the charge port on the phone. As for which firmware, look at your sim and see if you can get an idea from there, or if you can ask whomever you got your phone from. Do you remember what provider was listed under the software update channel originally? Your sim should be able to get you some info as to who the provider is even if it's just a subsidy of a major carrier.
Hi there !
Well today I have very good news!
At last I managed to reinstall everything. How it happened? So I went back to the steps in this way:
1. Having a wrong ROM version (it does not correspond to my stock) connect by bluethooth the cell phone to access the internet, so the cell phone recognized that the OEM had already been authorized and allowed me to access the option and change it (because before it was gray).
2. Go to the bootloader and find the indication "Flashing_locked", but as I knew I had already given the authorization from within the ROM I opened a console and wrote the command "fastboot oem unlock" AND RECOGNIZED IT!, Restart the bootloader and voila! the message already said "Flashing_unlocked"
3. After this it was a matter of trying (without lying) something like six firmware XT1789-05 version because I had no idea what mine was, it took me a long time because some left me without Wi-Fi again, but Finally, I managed to locate one that looked like the one I had (RETLA XT1789-05_NASH_RETLA_DS_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml), so I tried hard there, but still shows a warning that a version is installed of the different operating system, but it works for me and that's how it will stay for a couple of months.
4. Then I was able to install the TWRP and the Magisk without any problems.
5. Problems that I had: Warning of the bootloader without blocking, Notice of the different operating system, Application of finding my device does not work (it stays looking for the cell phone and never locates it).
Many thanks to 41rw4lk, without your help this would have been impossible.
I hope to share my experience with someone else who may have my problem or something like it!
Postscript: Finally, they never gave me instructions on how to make the Deep Cable when the cell phone is a USB-C type port (lol), so if the data appears I would still be interested only in general knowledge.
Hello.
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Note: Unlocked bootloader is not required to do any of the actions described in this guide.
Disclaimer: I'm in no way responsible for the actions you perform and whatever happens to your device due to these actions. Proceed at your own risk.
This guide is roughly based on the one @_Kuroi_ made. I have stripped out the OTA updating portion because at least currently I have the latest firmware for android 9 and 10. If you need instructions for applying an ota please read the original thread.
Prerequisites:
Service Firmware (Full QFIL) Only for WW SKU
If anyone would like to mirror these feel free to just send me a message and I'll add it to the OP.
WW-16.1220.1909.194 (Last Android 9/Pie Version)
Here
WW-17.1810.2009.176 (Latest at the time of posting Android 10/Q Version)
Here
Platform tools of Android SDK.
Latest package can be downloaded from: Windows | Linux. Somewhat optional but good to have.
Step 1 - Preparing the environment
Download and extract either the Android 9 or Android 10 Service firmware. Depending on what your phone was running before it was bricked.
Step 2 - Flashing service firmware
Connect your phone via USB
Enter fastboot mode
1.1 Turn off your device, then while holding down the volume up button press and hold the power button Release the power button when it powers up (keep holding the volume up button)
Open CMD (windows) | Terminal (unix)
CD into the folder with service firmware from item #2 from the step above.
Make sure your phone is detected by typing fastboot devices/FONT]
[*]Ensure battery is at least 20% charged. Aside from normal means, it's possible to check the battery charge via fastboot oem get-batcap.
Sample output: (bootloader) bat cap = 35, which means that the battery is 35% charged.
IMPORTANT NOTE BEFORE CONTINUING:
By default, flashing with one of the scripts wipes your userdata, in other words, it performs a factory reset.
[*]Run the script
1. 1. Windows: In the CMD you opened earlier, type flashall.cmd[/COLOR]
1. 2. Unix: In the Terminal you opened earlier, type ./flashall.sh
Note: An obvious note, do not disconnect your device from your PC while flashall script is running. Your device will reboot a few times during the execution.
[*]Once script outputs format logdump... and the phone reboots, service firmware will be flashed.
Your phone is now unbricked Congrats!
That's pretty much it. If you followed the steps above correctly, you should once again have a running phone.
If you have any questions, do not hesitate to ask.
Cheers.
Thanks for the files
I found some sites that might publish service fws
Spoiler: links
Rom stock / raw và bypass FRP cho Asus Zenfone 6 (ZS630KL) - vnROM
Rom stock / raw và bypass FRP cho Asus Zenfone 6 (ZS630KL) DOWNLOAD: WW_ZS630KL_17.1810.2011.183_M3.18.40.20_Phone-user.raw.zip / OneDrive / GDrive2 / GD3 WW_ZS630KL_17.1810.2010.179_M3.18.40.19_Phone-user.raw.zip / AFH / OneDrive / GDrive2...
vnrom.net
ZS630KL | Halab Tech Support
support.halabtech.com
{Mod edit: Links removed - Oswald Boelcke, Moderator}
Search for zs630kl | GSM HOSTING FILES
gsmhostingfiles.com
ZS630KL | Kurdish Firmware
kurdishfirmware.com
Search for zs630kl | VietNam GSM Services
vngsmservices.com
https://addrom.com/stock-raw-rom-and-bypass-frp-for-asus-zenfone-6-zs630kl/https://forum.gsmnigeria.com/threads/asus-zenfone-6-zs630kl-i01wd-firmware-complete-here.469https://firmwarex.net/asus-zenfone-6-i01wd-zs630kl-official-firmware/https://www.joelzr.com/2020/03/kumpulan-firmware-asus-raw-zip-dan-aft.htmlhttps://www.fullstockfirmwaredownload.com/asus/
FIRMWARE ASUS | Clan SOFT
www.clansoft.net
IMEI Source Forum
forum.imeisource.com
Mostrando resultados para 'zs630kl'. - Clan GSM
https://forum.imeisource.com/search/416782/?q=zs630kl&o=date
Asus Zenfone 6 ZS630KL/I01WD Firmware Here
Asus Zenfone 6 ZS630KL/I01WD Firmware Complete Here, All Link Google Drive Zenfone 6 ZS630KL/I01WD Download CSC_ZS630KL_16.0904.1810.58_M1.6.11.raw_Lock-132155848436752587 WW_ZS630KL_16.1210.1903.67_M2.6.17.12_Phone-user.raw-132010344012194561...
www.martview-forum.com
404 Error - Page Not Found! | Original Flash File Website GivemeRom
www.givemerom.com
https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=32713
ASUS Zenfone 6 I01WD (ZS630KL) Firmware | Qualcomm SDM855
Kali ini Firmware27 akan berbagi Firmware ASUS Zenfone 6 (2019) I01WD ZS630KL Qualcomm snapdragon 855, Firmware ini bisa digunakan untuk m...
www.firmware27.com
I was getting an error when I first tried executing flashall script
Code:
"flash boot boot.img BEGIN"
fastboot: error: boot partition is smaller than boot image
"flash failed and exit"
fastboot: error: boot partition is smaller than boot image
"FLASH FAIL"
fixed by running update_edl script
I also got an error saying 'QMSL_MSVC10R.dll' is missing. That's Microsoft Visual C++ 2010 Redistributable.
I also got another error when running flash all script
Code:
.\flashall.cmd
Spoiler
Code:
"=========================================== "
" format "
"=========================================== "
"enable flash and erase"
"format ADF..."
fastboot: error: Cannot generate image for ADF
"Format ADF fail and try again."
0
fastboot: error: Cannot generate image for ADF
"Format ADF fail and try again."
1
fastboot: error: Cannot generate image for ADF
"Format ADF fail and try again."
2
fastboot: error: Cannot generate image for ADF
"failed and exit"
"format asdf..."
fastboot: error: Cannot generate image for asdf
"Format asdf fail and try again."
0
fastboot: error: Cannot generate image for asdf
"Format asdf fail and try again."
1
fastboot: error: Cannot generate image for asdf
"Format asdf fail and try again."
2
fastboot: error: Cannot generate image for asdf
"failed and exit"
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.588s]
Finished. Total time: 0.607s
"wait for 30 seconds for bootloader to be ready..."
"reboot-bootloader..."
fastboot: error: Cannot generate image for ADF
fastboot: error: Cannot generate image for asdf
"failed and exit"
< waiting for any device >
Erasing 'userdata' OKAY [ 0.587s]
CreateProcess failed: %1 non è un'applicazione di Win32 valida. (193)
fastboot: error: Cannot generate image for userdata
"enable charging mode"
OKAY [ 0.002s]
Finished. Total time: 0.003s
"turn off uart"
OKAY [ 0.011s]
Finished. Total time: 0.011s
"turn off framdump mode"
(bootloader) *arg: n
(bootloader) GetForceRamdump(): false
OKAY [ 0.013s]
Finished. Total time: 0.013s
"disable flash and erase"
"Download_PASS"
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.006s
that's because I replaced fastboot of service fw with a newer fastboot exe
I upgraded to the latest android 11 version (UL-ASUS_I01WD-ASUS-18.0610.2101.132-1.1.1-user.zip) by placing the firmware file from asus download page to internal storage, rebooted, clicked on the notification saying an upgrade was available
changelog from asus website
I also found out from a thread in this section saying that you can use a script (vm03/payload_dumper: Android OTA payload dumper - GitHub) hosted on github to dump img files from the full ota that gets published from asus.
You only need termux app and then run
Code:
pkg install python
python -m pip install --upgrade pip
python -m pip install protobuf
python -m pip install bsdiff4
#gain access to storage where payload.bin is located
termux-setup-storage
python payload_dumper.py payload.bin
i got
Code:
Failed to load/authenticate boot image: Load Error
when rebooting the phone to twrp
Fixed by flashing boot and dtbo images to a/b slots
another problem was mtp not working when i pressed Format Data in twrp. Rebooting twrp again made mtp work again. adb sideload worked too
Guys, can you share the link for the latest raw firmware ?
latest raw firmware is available on halabtech and kurdish firmware, search with google
WW_ZS630KL_18.0610.2101.132_M3.23.44.19_Phone-user.raw.zip
sadly both sites let you download it only if you pay
raw firmware should only be available to repair centers so all the zips you find have been leaked
Hello I have a hardbrick that so far I cannot solve, because I want to close the bootloader, the fastboot rejects any command that I enter (including the "fastboot oem unlock") and when turning on motorola it generates the error 0xC2224571 "No valid operating system could be found. The device will not boot ". I thought about doing a "Blankflash", but I don't know what the Motorola "test point" is. Does anyone know how to do it and get to EDL mode?
seems a/b partition problem.
try fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
shadowchaos said:
seems a/b partition problem.
try fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
Click to expand...
Click to collapse
I already tried that of recovery_a and recovery_b, and nothing happens, that gives CMD:
1) fastboot flash recovery_a twrp-3.5.0-0-nairo.img
Sending 'recovery_a' (59392 KB) OKAY [ 1.827s]
Writing 'recovery_a' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
2) fastboot flash recovery_b twrp-3.5.0-0-nairo.img
Sending 'recovery_b' (59392 KB) OKAY [ 1.308s]
Writing 'recovery_b' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Also, everything I try to flash ends with this message "flash (bootloader) permission denied".
supermafari2.0 said:
I already tried that of recovery_a and recovery_b, and nothing happens, that gives CMD:
1) fastboot flash recovery_a twrp-3.5.0-0-nairo.img
Sending 'recovery_a' (59392 KB) OKAY [ 1.827s]
Writing 'recovery_a' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
2) fastboot flash recovery_b twrp-3.5.0-0-nairo.img
Sending 'recovery_b' (59392 KB) OKAY [ 1.308s]
Writing 'recovery_b' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Also, everything I try to flash ends with this message "flash (bootloader) permission denied".
Click to expand...
Click to collapse
Could you describe what moves at last time which causes this situation?
supermafari2.0 said:
I already tried that of recovery_a and recovery_b, and nothing happens, that gives CMD:
1) fastboot flash recovery_a twrp-3.5.0-0-nairo.img
Sending 'recovery_a' (59392 KB) OKAY [ 1.827s]
Writing 'recovery_a' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
2) fastboot flash recovery_b twrp-3.5.0-0-nairo.img
Sending 'recovery_b' (59392 KB) OKAY [ 1.308s]
Writing 'recovery_b' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Also, everything I try to flash ends with this message "flash (bootloader) permission denied".
Click to expand...
Click to collapse
Hey, can I ask you how did you manage to unbrick it? My phone doesn't get recognized via fastboot. It seems dead but when I connect it to the pc, it gets recognized as "Qualcomm HS-USB QDLoader 9008".
What can I do next?
Try a blank flash for your phone.
Hello,
I am in a similar situation and also interested in the test point for EDL mode, so rather than opening a new thread I figured I'd reply here.
As it stands, my phone has the /e/ project ROM and recovery flashed on it, the "Allow OEM unlock" option is disabled, and the bootloader is locked. Meaning, the OS doesn't get recognized and doesn't boot, flashing is disallowed across the board, fastboot oem unlock <UNLOCK_KEY> is rejected, and fastboot boot <any recovery stock or otherwise>.img fails.
fastboot oem blankflash returns "Command Restricted" and well, subsequently tells me it failed.
So my own ignorance left myself with a rather expensive paperweight and the last resort I believe is to flash a stock ROM in EDL mode. I have found a teardown video of the device and seen a few test points there (including 3 under the large heatsinking graphite film), and I'm ready to remove the back cover on mine. It seems that the EDL test point isn't documented... If need be, I could try to find the test points myself. I just need more info to not short and break anything.
Edit: so I've gone and done it. Stabbed all visible test points, one of them scores at 1.8v, one at 1.5v, the rest at 0v. [EDIT] Some actually show something below 0.5v.
The 1.8v test point is connected to a trace going to the connector's pin. Another pad goes just beside that pin. It is very enticing right now to try and bridge them, however I'm not confident those are the EDL test points and I may short something I don't want to. I'm gonna get resistors.
The missing connector tells me it's a connector that's important for Motorola, and clearly not for the end-user. This is a cost-saving measure, don't need to run extensive tests when the device is finalized, you only need the test points to... enable EDL? Ahah. The fact the connector pads are still there is because designing the rerouting to remove them also costs money.
The 1.5v test point is between the screen and bottom daughterboard flexible flat cables connectors. Without certainty, I believe it may be a voltage for one of those or both.
Attached is the photo of the test points around the missing connector, if that helps at all.
Edit2: I found this post about trying for test points. I'm lacking resistors right now to further test. https://forum.xda-developers.com/t/phone-doesnt-boot-even-in-edl-mode.4411915/#post-87260675
Edit3: welp, bridging the points linked to the missing connector pads did nothing. What I tried is keep the phone off, bridge the points, plug the USB, but it keeps sending me to "OS not found" error or fastboot, depending on if fb_mode_set or fb_mode_clear have been used.
Hey @Awilen please keep us posted. I too want to play with this phone, but am frustrated by lack of easy access to EDL mode (to unbrick). (I want to try to roll my own GSI/AOSP build + Moto proprietary drivers, which will likely not boot the first thirty or so times I try it.)
FWIW, I tried this method and a pre-bought cable that allegedly does the same thing- no dice either.
The fact that there ARE EDL IMAGES out there gives me hope.
This repository has some other tricks to try, if you are brave enough:
Use a edl cable (Short D+ with GND) and force reboot the phone (either vol up + power pressing for more than 20 seconds or disconnect battery), works with emmc + ufs flash (this will only work if XBL/SBL isn't broken)
If emmc flash is used, remove battery, short DAT0 with gnd, connect battery, then remove short.
If a ufs flash is used, things are very much more complicated. You will need to open the ufs die and short the clk line on boot, some boards have special test points for that.
Some devices have boot config resistors, if you find the right ones you may enforce booting to sdcard instead of flash.
(I've tried #1)
FWIW, I've never had any success with any "EDL cable" on any device, but that could be entirely due to timing/incompetence on my part.
A few devices I've been able to find EDL test points.
On some non-Qualcomm devices I have gotten to ROM bootloader by using a 100 ohm resistor (for safety, instead of a dead short) from some random test point near eMMC to ground.
Hey @Renate the cable works on my OnePlus (which, also, has a key sequence to do it, making the cable superfluous), so I know that isn't the issue here. I just don't want to unglue the phone and risk breaking something just to play. Once the battery becomes useless and that's inevitable, then I'll probably become a MB-shortin'-mo-fo.
SomeRandomGuy said:
This repository has some other tricks to try, if you are brave enough:
Use a edl cable (Short D+ with GND) and force reboot the phone (either vol up + power pressing for more than 20 seconds or disconnect battery), works with emmc + ufs flash (this will only work if XBL/SBL isn't broken)
If emmc flash is used, remove battery, short DAT0 with gnd, connect battery, then remove short.
If a ufs flash is used, things are very much more complicated. You will need to open the ufs die and short the clk line on boot, some boards have special test points for that.
Some devices have boot config resistors, if you find the right ones you may enforce booting to sdcard instead of flash.
(I've tried #1)
Click to expand...
Click to collapse
Hey! I was waiting on my EDL cable. I just tried it... no dice. No dice at all. I believe I've exhausted all non-intrusive tricks in the book, the next step is cleanly desoldering the EM shield over the processor and flash/RAM combo ICs.
Since the device is out of warranty anyway, I'll try for a repair shop to desolder it, as the only powerful-enough heat source I have is a large heat gun blowing 150°C, 450°C or 600°C air. Other than that I have a 60W soldering iron, I doubt that'll be enough.
The only problem with the desoldering is that the EM shield is part of the cooling solution for the processor/RAM/Flash ICs. It will need to be reapplied.
Edit: I made a thread on the e.foundation forums listing everything I tried: https://community.e.foundation/t/bo...and-wont-boot-am-i-out-of-luck/43362?u=awilen
Awilen said:
Edit: I made a thread on the e.foundation forums listing everything I tried: https://community.e.foundation/t/bo...and-wont-boot-am-i-out-of-luck/43362?u=awilen
Click to expand...
Click to collapse
TIL “fastboot oem qcom-on” and “fastboot oem qcom-off” are a thing.
For my part, to this day I cannot find a way to access this mode, I still have my theories, since on one page I found "official" diagrams of this motorola and the phrase "EDL" is indicated at various points, but I don't really know how to interpret them on the motherboard, I'll leave the link in case someone wants to review it, it's from a Brazilian page:
Motorola_Moto_G_5G XT2075 - LEMCELL.COM.BR.zip
drive.google.com
In that one there are several files, with more technical specifications, in case someone wants to review it and see what they find useful out there, to see if it is possible to reach EDL mode on this model.
The missing connector I shot in my photos is a JTAG connector. Make of that what you will.
I have desoldered the EMI shield above the SoC/eMCP area and there's no dice there either. The traces are hidden, the parts are BGAs, there's no "pin" to short there. The schematics may or may not have confirmed my suspicion the physical trace for the clock signal to the eMCP is unreachable, making reaching EDL mode through "PBL panic from not being able to access the flash" impossible.
The SMDs around the eMCP may or may not seem to all be related to power delivery smoothing, and shorting those is blue smoke waiting to happen. I'll resolder the shield later, I don't think there's any point in desoldering it in the future for the purpose of reaching EDL mode.
There are official blankflash utilities freely available. I have no doubt EDL mode is accessible. This connector must be just how.
BREAKTHROUGH TIME! I GOT INTO QCOM 9008 MODE!
In the attached photo are the EDL pads. Happy flashing!
Edit: now I'm getting some progress, but nothing is working. Here's the two logs I get, the first just after connecting, the second after having tried once already:
Code:
$ sudo ./qcom blank-flash
**** Log buffer [000001] 2022-12-02_19:02:50 ****
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 5.889] ERROR: sahara_greet_device()->change_mode()->do_hello()->Invalid command received in current state
[ 5.889] Check qboot_log.txt for more details
[ 5.889] Total time: 5.889s
[ 5.889]
[ 5.889] qboot version 3.86
[ 5.889]
[ 5.889] DEVICE {
[ 5.889] name = "/dev/ttyUSB0",
[ 5.889] flags = "0x60",
[ 5.889] addr = "0xFECAF690",
[ 5.889] serial_nix.device_pathname = "/sys/bus/usb/devices/1-3.2/1-3.2:1.0/ttyUSB0",
[ 5.889] api.bnr = "0x1FE4210",
[ 5.889] }
[ 5.889]
[ 5.889]
[ 5.889] Backup & Restore {
[ 5.889] num_entries = 0,
[ 5.889] restoring = "false",
[ 5.889] backup_error = "not started",
[ 5.889] restore_error = "not started",
[ 5.889] }
[ 5.889]
Code:
$ sudo ./qcom blank-flash
**** Log buffer [000001] 2022-12-02_19:03:50 ****
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.343] Detecting device
[ 34.920] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.920] Check qboot_log.txt for more details
[ 34.920] Total time: 34.920s
[ 34.920]
[ 34.920] qboot version 3.86
[ 34.920]
[ 34.920] DEVICE {
[ 34.920] name = "/dev/ttyUSB0",
[ 34.920] flags = "0x60",
[ 34.920] addr = "0xAEF35240",
[ 34.920] serial_nix.device_pathname = "/sys/bus/usb/devices/1-3.2/1-3.2:1.0/ttyUSB0",
[ 34.920] api.bnr = "0x21BC210",
[ 34.920] }
[ 34.920]
[ 34.920]
[ 34.920] Backup & Restore {
[ 34.920] num_entries = 0,
[ 34.920] restoring = "false",
[ 34.920] backup_error = "not started",
[ 34.920] restore_error = "not started",
[ 34.920] }
[ 34.920]
Edit 2: I got a blankflash to work! Now I don't know... This is what I got:
Code:
D:\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM3
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 286 (0x11e)
[ -0.000] ...cpu.sn = 3786473903 (0xe1b101af)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ -0.000] ...filename = pkg.xml
[ -0.000] Loading programmer
[ -0.000] ...filename = programmer.elf
[ -0.000] Sending programmer
[ 0.109] Handling things over to programmer
[ 0.109] Identifying CPU version
[ 0.109] Waiting for firehose to get ready
[ 3.220] ReadFile() failed, GetLastError()=0
[ 3.330] ...SM_SAIPAN 2.0
[ 3.330] Determining target secure state
[ 3.330] ...secure = yes
[ 3.377] Configuring device...
[ 3.377] Skipping UFS provsioning as target is secure
[ 3.377] Configuring device...
[ 3.470] Flashing GPT...
[ 3.470] Flashing partition with gpt.bin
[ 3.470] Initializing storage
[ 3.517] ...blksz = 4096
[ 3.580] ReadFile() failed, GetLastError()=0
[ 4.049] Re-initializing storage...
[ 4.049] Initializing storage
[ 4.361] Flashing bootloader...
[ 4.361] Wiping ddr
[ 4.392] Flashing abl_a with abl.elf
[ 4.439] Flashing aop_a with aop.mbn
[ 4.486] Flashing qupfw_a with qupfw.elf
[ 4.517] Flashing tz_a with tz.mbn
[ 4.783] Flashing hyp_a with hyp.mbn
[ 4.839] Flashing devcfg_a with devcfg.mbn
[ 4.854] Flashing keymaster_a with keymaster.mbn
[ 4.901] Flashing storsec_a with storsec.mbn
[ 4.933] Flashing uefisecapp_a with uefi_sec.mbn
[ 5.089] Flashing prov_a with prov64.mbn
[ 5.104] Flashing xbl_config_a with xbl_config.elf
[ 5.151] Flashing xbl_a with xbl.elf
[ 5.649] Rebooting to fastboot
[ 5.665] Total time: 5.665s
Somehow it worked, I got to flash another phone's blankflash (a "Racer" codenamed phone apparently) on it and the ABL (the thing that tells me it won't boot because it didn't find a valid system) changed visually. Now I'll try to unlock the bootloader, or flash a system on it.
Edit 3: Mmh. After clearing that EDL mode flashing worked, the system is still flashing-locked, secured, and fastboot oem unlock <unique_key> isn't working.
so you activated the qcom, but it is not responding to the blankflash? at least it's an advance, maybe it's a blankflash problem or do you think it's some kind of board protection?
Later I will try on my own on my board
Congrats on your quest. Were you literally shorting them, or did you use a resistor? You had to touch all three together?
I guess I still am confused how there is a blankflash out there for this phone, but no way to trigger EDL without a hardware kit. I just ran through all the key combinations (V+,V-, PWR) and USB in/out just to make sure I didn't miss something... no dice to EDL.
supermafari2.0 said:
so you activated the qcom, but it is not responding to the blankflash? at least it's an advance, maybe it's a blankflash problem or do you think it's some kind of board protection?
Later I will try on my own on my board
Click to expand...
Click to collapse
I am confident EDL mode flashing worked. I used a different phone's blankflash that had the same SoC and it worked, giving me a visually different "No OS found" error screen. I posted the log of the blanking process. The "Allow OEM Unlock" bit is still set to "disabled" after blanking, such that I still can't use "fastboot oem unlock" successfully.
There's this line that makes me think the system is still intact: "Skipping UFS provsioning as target is secure", meaning the UFS filesystem might have not been actually blanked. Since singleimage.bin is a signed binary, there's no way to force UFS provisioning or modify it in any other way. I think the only way in will be with a firehose and QFIL... Except I haven't found one for this SoC. The programmer.elf is the firehose, but again that needs to be signed to be useful after getting extracted.
SomeRandomGuy said:
Congrats on your quest. Were you literally shorting them, or did you use a resistor? You had to touch all three together?
I guess I still am confused how there is a blankflash out there for this phone, but no way to trigger EDL without a hardware kit. I just ran through all the key combinations (V+,V-, PWR) and USB in/out just to make sure I didn't miss something... no dice to EDL.
Click to expand...
Click to collapse
I marked two pads of the missing connector with a green rectangle (I reused the photo I posted earlier on which I had already marked the test points' voltages, disregard the test points). I shorted them with only one voltmeter probe.
The idea is that the EDL pads I marked in green are connected to a 1.8V supply and a pin on the SoC with "infinite resistance", so there's no need for an additional resistor. You are not at risk of shorting anything and cause a major disaster on pins on the row of the green rectangle. The connector is very small, so stab confidently in the middle of the row of pads!
The (V+, PWR) combination may be available in development units, and be disabled in production units at the hardware level (missing components).
(Keep in mind I'm talking in hypotheticals at times to keep up plausible deniability regarding the files posted earlier by supermafari2.0... Those are surely under copyright.)
Layers of security upon layers of security just to get a stock firmware on an empty filesystem on my own device... This is getting old...
Edit: I have, out of boredom, decomposed the singleimage.bin into its various files. Here is the file format:
Code:
* SINGLE_N_LONELY Header [256 bytes]
* FILE:
Header:
* file name: 248 bytes (name + "\0" padding)
* file size: 8 bytes, little-endian
Data:
* data: file size in bytes
* 0xA0 padding if (file size % 4096) != 0 : file size + 4096 - (file size % 4096) bytes
[* FILE...]
* LONELY_N_SINGLE Footer [256 bytes]
Do note the 4096 magic number is the flash sector size, thus is device-dependant. In singleimage.bin, there was gpt.bin which also follows the same format. Among the files is programmer.elf, a strong candidate to be a firehose, I'll try to use with QFIL tomorrow. I do take note of Motorola's attempt at psychological warfare.
So I tried the programmer I found in the singleimage.bin file, it's indeed capable of programming through QFIL! (Do note I needed to get QFIL through QPST to get it to work.) However now I'm faced with this as I'm trying to flash recovery.img to get to recovery and get recovery to reinstall a working system:
Code:
INFO: TARGET SAID: 'ERROR: range restricted: lun=5, start_sector=142688, num_sectors=25600'
I guess the programmer checks for the flash being in a locked state, so it's time to try to patch the programmer to force the flash, if at all possible...
Edit: guessed right. The programmer has a routine that does various checks. It isn't encrypted, but I found data that could indicate the file is signed. I didn't see either the PEEK or POKE strings in there, meaning these primitives weren't included in the programmer, so there's no way to manually poke any image by hand, or just enable that blasted "Allow OEM unlock" bit (the fact I don't know where it is not withstanding.)
I think that's the end of the line for my device. At this point the only way it will ever work again will be either getting a patched and signed firehose (unlikely), or getting Motorola to reflash a stock image internally (even more unlikely) or just changing the motherboard (which defeats the purpose of searching how to get the device back in working order after messing up!)