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!)
Related
Hello XDA,
Long time reader, first time really really needing some expert help.
The GF phone was stuck in a bootloop after she installed an OTA - Motorola would not help, other than re flashing whole device, and she would lose all data. No backup, yes yes i know.
Real men do not make backups, they just cry when stuff like this happens..
So I tried in fastboot to flash recovery to get mobile into recovery so i could get data from adb or recovery. This made it worse...
Now i con only get access the mobile with QFIL or the MOTO "qboot" tool. I have however not found a "singleimage.bin" it will flash yet.
Seen that the "bootloder.bin" in many Moto G5 files is equal to the "singleimange.bin" file.
Any inputs? Or is it dead jim?
Post I have been looking into:
https://forum.xda-developers.com/g5/help/moto-g5-cedric-xt1676-led-lights-help-t3773984
https://forum.xda-developers.com/g5/help/to-recover-hard-brick-bootloader-t3778119
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
https://forum.xda-developers.com/g5/help/how-to-develop-blank-flash-t3791525
https://forum.xda-developers.com/g5/help/xt1676-stuck-unlocked-bootloader-wipe-t3766827
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
https://forum.xda-developers.com/g5/how-to/fix-phone-reboots-recovery-mode-started-t3705325
Closest i got to success with qboot is:
**** Log buffer [000001] 2018-09-25_02:15:32 ****
[ -0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.003] ...cpu.id = 79 (0x4f)
[ 0.004] ...cpu.sn = 51414XXXX (0x1ea5XXXX)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.007] No suitable package found for MSM8937
[ 0.007] ERROR: error loading package
[ 0.007] Check qboot_log.txt for more details
[ 0.007] Total time: 0.012s
[ 0.008]
[ 0.008] qboot version 3.40
[ 0.008]
[ 0.008] DEVICE {
[ 0.008] name = "\\.\COM4",
[ 0.008] flags = "0x64",
[ 0.008] addr = "0x28FE5C",
[ 0.008] sahara.current_mode = "3",
[ 0.008] api.buffer = "0x2116020",
[ 0.008] cpu.serial = "51414XXXX",
[ 0.008] cpu.id = "79",
[ 0.008] cpu.sv_sbl = "1",
[ 0.008] cpu.name = "MSM8937",
[ 0.008] storage.type = "eMMC",
[ 0.008] api.bnr = "0x205XXXX",
[ 0.008] }
[ 0.008]
[ 0.008]
[ 0.008] Backup & Restore {
[ 0.008] num_entries = 0,
[ 0.008] restoring = "false",
[ 0.008] backup_error = "not started",
[ 0.008] restore_error = "not started",
[ 0.008] }
[ 0.008]
This is the last proof of life while still having access to fastboot (output from terminal while flashing different stuff):
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
Sending 'modem' (65228 KB) OKAY [ 2.263s]
Writing 'modem' OKAY [ 2.656s]
Finished. Total time: 5.124s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
Sending 'partition' (45 KB) OKAY [ 0.019s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
Finished. Total time: 0.323s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash bootloader bootloader.img
(bootloader) has-slot:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.192s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 1.751s]
Finished. Total time: 2.145s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
Sending 'modem' (65228 KB) OKAY [ 2.095s]
Writing 'modem' OKAY [ 2.713s]
Finished. Total time: 5.006s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash fsg fsg.mbn
(bootloader) has-slot:fsg: not found
Sending 'fsg' (2592 KB) OKAY [ 0.106s]
Writing 'fsg' OKAY [ 0.205s]
Finished. Total time: 0.511s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash dsp adspso.bin
(bootloader) has-slot:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.586s]
Writing 'dsp' OKAY [ 0.852s]
Finished. Total time: 1.642s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
Sending 'logo' (2242 KB) OKAY [ 0.084s]
Writing 'logo' OKAY [ 0.350s]
Finished. Total time: 0.635s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.531s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 0.924s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.543s]
Writing 'recovery' (bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 0.970s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
Sending 'system' (524052 KB) OKAY [ 19.276s]
Writing 'system' (bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 19.602s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot oem getvar max-sparce-size
(bootloader) 'getvar' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote: '')
Finished. Total time: 0.036s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot oem max-sparce-size
(bootloader) 'max-sparce-size' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote: '')
Finished. Total time: 0.045s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot getvar max-sparce-size
(bootloader) max-sparce-size: not found
getvar:max-sparce-size FAILED (remote: '')
Finished. Total time: 0.029s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash system system.img_sparsechunk.1
(bootloader) has-slot:system: not found
Sending 'system' (520883 KB) OKAY [ 19.927s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 20.186s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash system system.img_sparsechunk.2
(bootloader) has-slot:system: not found
Sending 'system' (520702 KB) OKAY [ 19.170s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 19.427s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash system system.img_sparsechunk.3
(bootloader) has-slot:system: not found
Sending 'system' (521654 KB) OKAY [ 19.606s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 19.869s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
Sending 'system' (422743 KB) OKAY [ 16.362s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 16.622s
C:\_temp\android\Moto_G5_1st_November_2017_update>fastboot flash oem oem.img
(bootloader) has-slotem: not found
Sending 'oem' (188514 KB) OKAY [ 6.881s]
Writing 'oem' (bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 7.176s
Update 1
Hi,
Just remembered - I got access to an identical mobile that has not run the OTA update yet. Maybe I can download the OTA files on it, at from that get a single image bin i can flash?
StuartStardust said:
Hi,
Just remembered - I got access to an identical mobile that has not run the OTA update yet. Maybe I can download the OTA files on it, at from that get a single image bin i can flash?
Click to expand...
Click to collapse
None of that will work but there is a solution if you can spend time reading my thread - everything is provided for you but please read it fully
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Also you will need newer firmware as you are tried to flash old firmware hence the security downgrade errors & the reason you hard bricked in the first place
Here's a perfect step-by-step tutorial for unbricking hard bricked Moto G5: https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012. You need 32GB SD card (64GB is recommended) and a basic knowledge of Linux OS.
Just one question: why did you flash all the partitions instead of recovery only? The reason why have you hardbricked the phone is simple - you have most probably flashed firmware with older build number than it was already installed - according to log, you have also tried to flash gpt and bootloader partitions but as they can't be downgraded, it resulted in hardbrick.
Hi guys,
Wow, fast response!
Yes, I know I f***ed up by trying to flash the old files and hard bricked it, but realized that too late... But to be fair the OTA started it... :crying:
Sorry, I forgot to include this in the list, yes,:
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Have tried that also, with 3 different SD cards, using Win32DiskImager, Rufus and DD in Linux (using a rpi).
There are no qboot option or QFIL option? It seems that interface is still alive, just missing the "right" file to pass to it. Would Motorola not have it?
Also, while the fastboot was still alive, I tried the fastboot command for booting recovery directly from img file, but that was also blocked/not allowed.
Why are the brands making it hard for us to fix stuff like this? I myself have a Moto G6, and love it, but now I do not think I would buy a new Moto to the GF..
Kind regards and thanks for all the help and info
StuartStardust said:
Hi guys,
Wow, fast response!
Yes, I know I f***ed up by trying to flash the old files and hard bricked it, but realized that too late... But to be fair the OTA started it... :crying:
Sorry, I forgot to include this in the list, yes,:
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Have tried that also, with 3 different SD cards, using Win32DiskImager, Rufus and DD in Linux (using a rpi).
There are no qboot option or QFIL option? It seems that interface is still alive, just missing the "right" file to pass to it. Would Motorola not have it?
Also, while the fastboot was still alive, I tried the fastboot command for booting recovery directly from img file, but that was also blocked/not allowed.
Why are the brands making it hard for us to fix stuff like this? I myself have a Moto G6, and love it, but now I do not think I would buy a new Moto to the GF..
Kind regards and thanks for all the help and info
Click to expand...
Click to collapse
is very strange, should it work, your 32 gb memory, correctly completed the writing? must be installed directly from the PC, not through any equipment, (using an adapter my memory was receiving data at 890 kbps for 8 hours, but it worked, my team was able to resuscitate)
Andrej_SK said:
Just one question: why did you flash all the partitions instead of recovery only? The reason why have you hardbricked the phone is simple - you have most probably flashed firmware with older build number than it was already installed - according to log, you have also tried to flash gpt and bootloader partitions but as they can't be downgraded, it resulted in hardbrick.
Click to expand...
Click to collapse
I think i tried the recovery first, twrp (failed, no root) then stock, without any success, but my memory has failed me before... ...but when it first failed booting after the OTA, both the "os" and the recovery was dead, only fastboot was alive, which i think is wierd..
StuartStardust said:
Hi guys,
Wow, fast response!
Yes, I know I f***ed up by trying to flash the old files and hard bricked it, but realized that too late... But to be fair the OTA started it... :crying:
Sorry, I forgot to include this in the list, yes,:
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Have tried that also, with 3 different SD cards, using Win32DiskImager, Rufus and DD in Linux (using a rpi).
There are no qboot option or QFIL option? It seems that interface is still alive, just missing the "right" file to pass to it. Would Motorola not have it?
Also, while the fastboot was still alive, I tried the fastboot command for booting recovery directly from img file, but that was also blocked/not allowed.
Why are the brands making it hard for us to fix stuff like this? I myself have a Moto G6, and love it, but now I do not think I would buy a new Moto to the GF..
Kind regards and thanks for all the help and info
Click to expand...
Click to collapse
It will work if done correctly - you MUST use the method provided - do not use windows win32diskmanager Rufus etc - I repeat you MUST use Linux & the method provided
StuartStardust said:
Hi guys,
Wow, fast response!
Yes, I know I f***ed up by trying to flash the old files and hard bricked it, but realized that too late... But to be fair the OTA started it... :crying:
Sorry, I forgot to include this in the list, yes,:
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Have tried that also, with 3 different SD cards, using Win32DiskImager, Rufus and DD in Linux (using a rpi).
There are no qboot option or QFIL option? It seems that interface is still alive, just missing the "right" file to pass to it. Would Motorola not have it?
Also, while the fastboot was still alive, I tried the fastboot command for booting recovery directly from img file, but that was also blocked/not allowed.
Why are the brands making it hard for us to fix stuff like this? I myself have a Moto G6, and love it, but now I do not think I would buy a new Moto to the GF..
Kind regards and thanks for all the help and info
Click to expand...
Click to collapse
Download Linux Mint e use on Live USB, any distro on RPI or Windows virtual machine running Linux not work correctly.
Your SD as really original ? Many fake SD not work
how revive moto g5
you can download two file annd fast boot the file at last reply on thread without use sd card
https://forum.xda-developers.com/g5/help/want-stock-rom-moto-g5-xt1676-to-t3837814
waleedzzz said:
you can download two file annd fast boot the file at last reply on thread without use sd card
https://forum.xda-developers.com/g5/help/want-stock-rom-moto-g5-xt1676-to-t3837814
Click to expand...
Click to collapse
You do realise you need to be able to access the bootloader mode to be able to to flash them via fastboot
The op can't - the sd card method is the only known working method to access the bootloader & reflash the firmware (which includes gpt & bootloader)
Ok that s right but when you finished the commands for rom to the mobile not open again the two file you should fast boot by fastboot app you should insert sd card and bootloader again by sd then remove the flash gpt and bootloader
qboot-ing the waleedzzz option
waleedzzz said:
you can download two file annd fast boot the file at last reply on thread without use sd card
https://forum.xda-developers.com/g5/help/want-stock-rom-moto-g5-xt1676-to-t3837814
Click to expand...
Click to collapse
Yes, tried getting this file, rename to singleimage.bin and qboot it, but no success - did not expect it to work either, but could not hurt to give it a try.
Output below:
**** Log buffer [000001] 2018-10-06_18:03:25 ****
[ -0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 0.004] ...cpu.id = 79 (0x4f)
[ 0.005] ...cpu.sn = 51414XXXX (0x1ea5XXXX)
[ 0.009] Opening singleimage
[ 0.029] Loading package
[ 0.031] Failed identify board. Wrong package?
[ 0.032] ERROR: error loading package
[ 0.034] Check qboot_log.txt for more details
[ 0.038] Total time: 0.041s
[ 0.043]
[ 0.043] qboot version 3.40
[ 0.043]
[ 0.043] DEVICE {
[ 0.043] name = "\\.\COM3",
[ 0.043] flags = "0x64",
[ 0.043] addr = "0x28FEXX",
[ 0.043] sahara.current_mode = "3",
[ 0.043] api.buffer = "0x21C4020",
[ 0.043] cpu.serial = "51414XXXX",
[ 0.043] cpu.id = "79",
[ 0.043] cpu.sv_sbl = "1",
[ 0.043] api.bnr = "0x21014F8",
[ 0.043] }
[ 0.043]
[ 0.043]
[ 0.043] Backup & Restore {
[ 0.043] num_entries = 0,
[ 0.043] restoring = "false",
[ 0.043] backup_error = "not started",
[ 0.043] restore_error = "not started",
[ 0.043] }
[ 0.043]
Dont rename use command as you see
Using: https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
I now tried the boot from SD after making the SD card in linux on a PC with SD card reader - no error in the copy to SD card.
How should I boot the phone? How do i make it boot from the SD card? Power on? Vol down + power on?
Right now i just got a white blinking led when it is in its original charger, else noting.
Any suggestions?
waleedzzz said:
Dont rename use command as you see
Click to expand...
Click to collapse
Sorry, i do not understand? Is you method not using fastboot? I have no fastboot access, only qboot is alive on the mobile. Think it is called hardbrick, but not sure..
Ran the MAF.exe directly also, but no success:
C:\_temp\android\Gpt.bin___Bootloader_Moto_G5\Gpt.bin & Bootloader Moto G5\Fastboot>MAF32.exe
'Bootloader' is not recognized as an internal or external command,
operable program or batch file.
DEBUG Window You May Close This
StuartStardust said:
Using: https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
I now tried the boot from SD after making the SD card in linux on a PC with SD card reader - no error in the copy to SD card.
How should I boot the phone? How do i make it boot from the SD card? Power on? Vol down + power on?
Right now i just got a white blinking led when it is in its original charger, else noting.
Any suggestions?
Click to expand...
Click to collapse
Just turn phone with sdcard in & it will display bootloader screen
If it doesn't you either haven't created the sd card correctly or your sdcard is too small (formatted size)
TheFixItMan said:
If it doesn't you either haven't created the sd card correctly or your sdcard is too small (formatted size)
Click to expand...
Click to collapse
This was output from writing SD, including SHA of imagefile:
[email protected]:/media/user/Android/MotoG5# sudo dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
31264342016 bytes (31 GB, 29 GiB) copied, 3407.34 s, 9.2 MB/s
7455+0 records in
7455+0 records out
31268536320 bytes (31 GB, 29 GiB) copied, 3407.82 s, 9.2 MB/s
[email protected]:/media/user/Android/MotoG5# sha
sha1sum sha224sum sha256sum sha384sum sha512sum shadowconfig shasum
[email protected]:/media/user/Android/MotoG5# shasum mmcblk0.img
da39a3ee5e6b4b0d3255bfef95601890afd80709 mmcblk0.img
shasum of mmcblk0.img = da39a3ee5e6b4b0d3255bfef95601890afd80709
Can anyone check? :fingers-crossed:
Another thing, this phone model is following:
board: cedric
sku: XT1676
hwrev: P5
emmc: 16GB SAMSUNG RE1BMB
ram: 3GB SAMSUNG LP3
cpu: MSM8937
Can this method be used on this 16 GB version of the MOTO G5?
PS. Now doing it again on a bigger SD card, got a 128 GB, the one I already tried was a SanDisk Ultra 32 GB.
StuartStardust said:
This was output from writing SD, including SHA of imagefile:
[email protected]:/media/user/Android/MotoG5# sudo dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
31264342016 bytes (31 GB, 29 GiB) copied, 3407.34 s, 9.2 MB/s
7455+0 records in
7455+0 records out
31268536320 bytes (31 GB, 29 GiB) copied, 3407.82 s, 9.2 MB/s
[email protected]:/media/user/Android/MotoG5# sha
sha1sum sha224sum sha256sum sha384sum sha512sum shadowconfig shasum
[email protected]:/media/user/Android/MotoG5# shasum mmcblk0.img
da39a3ee5e6b4b0d3255bfef95601890afd80709 mmcblk0.img
shasum of mmcblk0.img = da39a3ee5e6b4b0d3255bfef95601890afd80709
Can anyone check? :fingers-crossed:
Another thing, this phone model is following:
board: cedric
sku: XT1676
hwrev: P5
emmc: 16GB SAMSUNG RE1BMB
ram: 3GB SAMSUNG LP3
cpu: MSM8937
Can this method be used on this 16 GB version of the MOTO G5?
PS. Now doing it again on a bigger SD card, got a 128 GB, the one I already tried was a SanDisk Ultra 32 GB.
Click to expand...
Click to collapse
I would say your sd card was too small by something silly like 100mb- people have more success with 64gb plus cards
It will work on any variant
TheFixItMan said:
I would say your sd card was too small by something silly like 100mb- people have more success with 64gb plus cards
It will work on any variant
Click to expand...
Click to collapse
Just tried with the 128GB card, same number of bytes written, but faster as card is bigger :good:... However...
Redownloaded the zip file and unpacked on the linux system - now the sha of the img file changed, not good - output below:
[email protected]:/media/user/Android/MotoG5# sudo dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
31251759104 bytes (31 GB, 29 GiB) copied, 949.115 s, 32.9 MB/s
7455+0 records in
7455+0 records out
31268536320 bytes (31 GB, 29 GiB) copied, 949.64 s, 32.9 MB/s
[email protected]:/media/user/Android/MotoG5# shasum mmcblk0.img
2855681a27ceb9f7fff3a44ee58c3a0c8768a21b mmcblk0.img
[email protected]:/media/user/Android/MotoG5# shasum mmcblk0
mmcblk0 (1).zip mmcblk0.img mmcblk0_old.img.bak
[email protected]:/media/user/Android/MotoG5# shasum "mmcblk0 (1).zip"
bb986826091c68dbed30e6e29367b991bc8d96b4 mmcblk0 (1).zip
It will not boot on the 128GB either..
FYI: Both the 32 GB and 128 GB card have partitions from p1 up to p54, after the dd command, and the 32 GB have a bit more than 600 MB free after last patition (the 128 GB around 97 GB free), so i guess that is not the problem. The 32GB has enough space i t looks like.
Thanks for all the help so far :highfive:
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.
My phone wich i never unlocked nor tried flashing with custom roms before started losing functionalities like part of the settings menu, for example the sim cards menu, not loading up or apps not loading/crashing and massive battery use, which i then solved by flashing a raw original rom file using fastboot from a nice guy on youtube with my exact model. youtube.com/watch?v=pOShAjiDeo0 , his 3 gig raw file and flashall.bat did everything with just one bat executable for me after extracting his package
This worked flawlessly to revive the phone five times to its out of the box original state, in the last 6-8 months after each time the phone started having these weird glitches as if it forgot parts of its systemfiles im assuming . (and the phones built in recovery factory reset thing didnt do anything to fix the phone)
Yesterday while in the mids of using the phone on the loo surfing the web all apps i was using started crashing instantly after opening them so i was like, ok lets flash again for the sixt time like we have done before, only this time, it gave me FAILED error at the partitioning stage. Im suspecting my partition is corrupted this time , as even the recovery mode of the phone does not load , it just keeps rebooting when i press the volume down button while powering on the phone. Fastboot still works when holding the volume up button and is the only thing working at this time
flashall.bat (@ECHO OFF FOR /F "delims=" %%i IN ('dir "%~dp0" /B ^| findstr /I "raw"') DO ( SET RAW=%%i )
fastboot flash all -f "%RAW%"
fastboot oem adb_enable
fastboot continue )
/////////////////////////////////////////////////
// WIPE-DISABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS Fastboot Tool (Android L)
// Version V4.0 (2015/06/16)
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE500KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 705
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 268435456 bytes
sending 'partition' CRC (0x446454cf)...
OKAY [ 0.005s]
writing 'CRC'...
OKAY [ 0.001s]
sending 'partition' (33 KB)...
OKAY [ 0.004s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.029s
...
OKAY [ 0.001s]
finished. total time: 0.002s
resuming boot...
FAILED (command write failed (No such file or directory))
finished. total time: 0.003s
Thanks for reading, my first time dabling in all this stuff as id hate to see a perfectly good screen and ram and device going to waste because of a corrupted storage system, partition issue. How to i go about recreating the partition in such a case ? all i have to work with is fastboot, i never got this adb stuff to list the device)
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.
Hi, i buy used Lenovo P2 for 10 dollars in very good visual shape, wchich not boot up, only red diode blinking, im trying blankflash but i have some error and can't find any answer for this on xda or in google, most people have IO error or something else, can anybody help and say what is wrong with this?
Opening device: \\.\COM3
OKAY [ -0.000s]
Detecting device
...cpu.id = 70 (0x46)
...cpu.sn = 3079725329 (0xb790e111)
OKAY [ 0.010s]
Opening singleimage
OKAY [ 0.000s]
Loading package
...filename = bootloader.qboot.xml
OKAY [ 0.010s]
Loading programmer
...filename = programmer.mbn
OKAY [ -0.000s]
Sending programmer
OKAY [ 0.239s]
Handling things over to programmer
Waiting for firehose to get ready ......
Identifying CPU
...MSM8953 1.1
Storage Information
...physical partition number: 0
...num_partition_sectors=61071360
...SECTOR_SIZE_IN_BYTES=512
...num_physical_partitions=3
...MFR_ID=21
...OEM_ID=0
...Product name=RX14MB
...{"storage_info": {"total_blocks":61071360, "block_size":512, "page_size":512, "num_physical":3, "mfr_id":21, "serial_num":3702248578, "fw_version":"7","mem_type":"eMMC", "prod_name":"RX14MB"}}
Flashing partition sbl1 with sbl1.mbn (373KB)
..FAILED: handle_command()->handle_program()->send_raw()->"NAK"