Hard brick after LOS installation

[b.bew]

Hello everybody,

once again I'm in trouble.

With help of Marcowe I updated my phone with no OS to Oreo

https://forum.xda-developers.com/z2-force/help/z2-os-help-to-t3837577

I wanted to give it another try and here I my attempts to install LOS.

1. oem unlock
2. I booted into current twrp (fastboot boot twrp-3.2.3-2-nash.img
3. adb push of lineange onto internal sd card
4. In TWRP under advanced wipe I pressed format data (If I now think about it, in the progress windows there was some red text probably not a good sign)
5. I installed LOS with now error
6. There was an option to delete dalvik cache which I pressed
7 . System reboot
8. Black screen Device Manager shows me Qualcomm HS-USB QDLoader 9008 (COM6)

I tried a blankflash file from here

https://unbricks.com/unbrick-motorola-moto-z2-force-update-fix-issues/

but it shows me an error. Log file will be at end of post.

QFIL does not find a corresponding MBN nor an XML file in stock rom

https://forum.xda-developers.com/z2-force/development/factory-image-moto-z2-force-nash-retail-t3699306

If you have got any idea to get my phone back, I would be happy and would like to contribute.

Regards,
Bew

Log file:
[ 0.001] Opening device: \\.\COM6
[ 0.003] Detecting device
[ 34.009] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.009] Check qboot_log.txt for more details
[ 34.009] Total time: 34.011s
[ 34.009]
[ 34.009] qboot version 3.85
[ 34.009]
[ 34.009] DEVICE {
[ 34.009] name = "\\.\COM6",
[ 34.009] flags = "0x64",
[ 34.009] addr = "0x28FD74",
[ 34.009] api.bnr = "0x372FD8",
[ 34.009] }
[ 34.009]
[ 34.009]
[ 34.009] Backup & Restore {
[ 34.009] num_entries = 0,
[ 34.009] restoring = "false",
[ 34.009] backup_error = "not started",
[ 34.009] restore_error = "not started",
[ 34.009] }
[ 34.009]

 

[doubledragon5]

Try this, power the phone back on. If you get that screen again cover the power button (don't press yet) with one finger, then cover the volume down button (don't press yet) with another.. Then press the power button, until the screen goes blank, then right after it does, (while still holding down the power button) Press the volume down button, until it comes on again.. Hopefully it will give you the bootloader instead.. If it does, Then find a flashll file for your carrier.

 

[b.bew]

Try this, power the phone back on. If you get that screen again cover the power button (don't press yet) with one finger, then cover the volume down button (don't press yet) with another.. Then press the power button, until the screen goes blank, then right after it does, (while still holding down the power button) Press the volume down button, until it comes on again.. Hopefully it will give you the bootloader instead.. If it does, Then find a flashll file for your carrier.

Hello doubledragon5,

the screen is blank all the time. It stays black if I try to turn it on or off. The phone gives no sign if its on or off.

Regards,
Bew

 

[doubledragon5]

Hello doubledragon5,

the screen is blank all the time. It stays black if I try to turn it on or off. The phone gives no sign if its on or off.

Regards,
Bew

Sorry miss read your post.

 

[41rw4lk]

Unbrick yo Brick quick ish

Here are the signed diag drivers for win
Qualcomm Diag Drivers Signed

attached is the blankflash zip

Unplug your phone, install diag drivers, replug and wait for the everything to recognize and settle.
Unzip the blankflash to a folder and run the bat file, after it's done you should be back in bootloader where you can re-flash the latest firmware for your phone.
Use 2.0 usb ports from your motherboard, not a hub like the front of your pc; and use the oem cable.

If you have trouble getting this to work then unplug your phone from your pc, uninstall your moto drivers and the qualcomm drivers. Restart. Reininstall the drivers, reboot; then plug your phone and wait for the drivers to recognize, install, and settle. You may need to try to run the blankflash a couple of times to get it to take. You may need to try alternate usb ports, even 3.0+
This phone can be super picky about ports, cables, and even adb/fastboot versions. For most they won't have to worry about most of this, but for others this is the basic setup that works for the majority of users.

*Note - To get into blankflash/edl mode manually...
from bootloader prompt 'fastboot oem blankflash' w/o quotes
via adb command 'adb reboot edl' w/o quotes

 

[b.bew]

Here are the signed diag drivers for win
Qualcomm Diag Drivers Signed

attached is the blankflash zip

Unplug your phone, install diag drivers, replug and wait for the everything to recognize and settle.
Unzip the blankflash to a folder and run the bat file, after it's done you should be back in bootloader where you can re-flash the latest firmware for your phone.

Thank you very much.
I was able to start in bootloader again. I was not able to flash the firmware via the procedure described by Marcowe (see link in first post, it mentioned that they are no sectors _a _b or something like that, I will recheck.). Still I was able too boot in Oreo.
I guess because its an A/B device? Does this mean that one is corrupted now?

Regards,
Bew

 

[41rw4lk]

Thank you very much.
I was able to start in bootloader again. I was not able to flash the firmware via the procedure described by Marcowe (see link in first post, it mentioned that they are no sectors _a _b or something like that, I will recheck.). Still I was able too boot in Oreo.
I guess because its an A/B device? Does this mean that one is corrupted now?

Regards,
Bew

So you're able to boot and use your phone, correct? If so, don't worry about the other slot, it'll get sorted when a new update comes out, or you flash a custom rom (if you choose to). If you followed Marcowe's flashing instructions from that other post you linked, then the same firmware is flashed on both slots. As for slot _a _b messages, could have been an out of date bootloader session depending on what you were doing and what, if anything, you flashed prior to trying to flash the firmware. A few different things could be going on there, so unless you can't boot I wouldn't trip on it at the moment.
Either way, if you can boot and use your phone I wouldn't worry about it, unless there is something specific you're trying to do. Alternatively, you can boot into bootloader mode and run the command 'fastboot getvar all' w/o quotes and get a little info about the state of your phone.

 

[b.bew]

So you're able to boot and use your phone, correct? If so, don't worry about the other slot, it'll get sorted when a new update comes out, or you flash a custom rom (if you choose to). If you followed Marcowe's flashing instructions from that other post you linked, then the same firmware is flashed on both slots. As for slot _a _b messages, could have been an out of date bootloader session depending on what you were doing and what, if anything, you flashed prior to trying to flash the firmware. A few different things could be going on there, so unless you can't boot I wouldn't trip on it at the moment.
Either way, if you can boot and use your phone I wouldn't worry about it, unless there is something specific you're trying to do. Alternatively, you can boot into bootloader mode and run the command 'fastboot getvar all' w/o quotes and get a little info about the state of your phone.

I'm able to boot and use my phone. I would like to use lineageos but my last two attempts where disasters.

I copied the last part of the info state which gives information about the slots since I'm not sure wat to delete besides of serial number.

(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0

 

[npjohnson]

I'm able to boot and use my phone. I would like to use lineageos but my last two attempts where disasters.

I copied the last part of the info state which gives information about the slots since I'm not sure wat to delete besides of serial number.

(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0

You weren't on the correct build when you flashed Lineage OS. It explicitly says which one to be on in the OP.

http://download.invisiblek.org/nash/unbrick.zip -- this has instructions in it. We've done it hundreds of time, and I know it works.

Best of luck.

 

[riskyfuture]

fastboot oem fb_mode_set
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash oem_a oem.img
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_b adspso.bin
fastboot flash logo_b logo.bin
fastboot flash boot_b boot.img
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash system_b system.img_sparsechunk.3
fastboot flash system_b system.img_sparsechunk.4
fastboot flash system_b system.img_sparsechunk.5
fastboot flash oem_b oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear

Put this as your flashall.bat with your correct firmware

 

[XxeAgLeAnGeLxX]

hello i have the same problem all time, first install qualcom drivers, then i uninstall motorola drivers and reboot, is very difficult to detect my phone in my pc, dont know why, but when detects it says unknown device, then i manually update the driver to Qualcomm HS-USB QDLoader 9008 (COM6), and its ok, run bat file blankflash, but it says waiting for device all time i did on my windows 7 pc and my windows 1 pc is the same, can anyone help me?

 

[41rw4lk]

hello i have the same problem all time, first install qualcom drivers, then i uninstall motorola drivers and reboot, is very difficult to detect my phone in my pc, dont know why, but when detects it says unknown device, then i manually update the driver to Qualcomm HS-USB QDLoader 9008 (COM6), and its ok, run bat file blankflash, but it says waiting for device all time i did on my windows 7 pc and my windows 1 pc is the same, can anyone help me?

You have to stop thread jumping and posting bits and pieces of your problem here and there, it makes it difficult to help you and it clutters the thread making it hard to reference for other users. Are we to back track through 3-4 different threads to see what the original problem is and what you've tried? Plus this thread is almost a year old and I'm sure isn't relevant to what your problem is.

 

[XxeAgLeAnGeLxX]

You have to stop thread jumping and posting bits and pieces of your problem here and there, it makes it difficult to help you and it clutters the thread making it hard to reference for other users. Are we to back track through 3-4 different threads to see what the original problem is and what you've tried? Plus this thread is almost a year old and I'm sure isn't relevant to what your problem is.

sorry

 

[latadswapnil]

Here are the signed diag drivers for win
Qualcomm Diag Drivers Signed

attached is the blankflash zip

Unplug your phone, install diag drivers, replug and wait for the everything to recognize and settle.
Unzip the blankflash to a folder and run the bat file, after it's done you should be back in bootloader where you can re-flash the latest firmware for your phone.
Use 2.0 usb ports from your motherboard, not a hub like the front of your pc; and use the oem cable.

If you have trouble getting this to work then unplug your phone from your pc, uninstall your moto drivers and the qualcomm drivers. Restart. Reininstall the drivers, reboot; then plug your phone and wait for the drivers to recognize, install, and settle. You may need to try to run the blankflash a couple of times to get it to take. You may need to try alternate usb ports, even 3.0+
This phone can be super picky about ports, cables, and even adb/fastboot versions. For most they won't have to worry about most of this, but for others this is the basic setup that works for the majority of users.

*Note - To get into blankflash/edl mode manually...
from bootloader prompt 'fastboot oem blankflash' w/o quotes
via adb command 'adb reboot edl' w/o quotes

I tried multiple methods to get into edl mode to do a blankflash , but I am not succesful. I tried the manual commands you mentioned but "fastboot oem blankflash" throws an error "command restricted".
adb reboot edl simply reboots multiple times and then boots normally to os, doesn't get detected as Qualcomm 9092 device.
I tried qcom method from bootloader which just normally boots the device to android but my laptop does detect it as qualcomm 9092 device. but then your blank-flash file doesn't work on it and stays on "waiting for device" .

Reason I want to blankflash is I accidentally flashed stock pie retail rom on my TMO 1789-04 device and now I dont have network/no sim error. Although baseband and imei are visible I dont have network or shows no sim error. I did manage to install TMO stock oreo but still no luck. As a last try I want to do blankflash and see if it helps.

can you please help me to get into edl mode or help blankflash my moto XT 1789-04?

 

[41rw4lk]

I tried multiple methods to get into edl mode to do a blankflash , but I am not succesful. I tried the manual commands you mentioned but "fastboot oem blankflash" throws an error "command restricted".
adb reboot edl simply reboots multiple times and then boots normally to os, doesn't get detected as Qualcomm 9092 device.
I tried qcom method from bootloader which just normally boots the device to android but my laptop does detect it as qualcomm 9092 device. but then your blank-flash file doesn't work on it and stays on "waiting for device" .

Reason I want to blankflash is I accidentally flashed stock pie retail rom on my TMO 1789-04 device and now I dont have network/no sim error. Although baseband and imei are visible I dont have network or shows no sim error. I did manage to install TMO stock oreo but still no luck. As a last try I want to do blankflash and see if it helps.

can you please help me to get into edl mode or help blankflash my moto XT 1789-04?

Blankflash won't solve that problem. Once you flash a pie modem you're stuck with it. The only solution is a pie modem which doesn't exist for TMO. No one has found a work around for this and with this phone being as old as it is now, it's unlikely that anything useful will be provided. Sorry. If you look around the forum you see dozens of warnings and examples of flashing the wrong firmware to your phone, most notably pie firmware. I think the only solution would be a pie modem that works for TMO too or a way to overwrite the modem nv value, both are pretty far out there.

 

[latadswapnil]

Blankflash won't solve that problem. Once you flash a pie modem you're stuck with it. The only solution is a pie modem which doesn't exist for TMO. No one has found a work around for this and with this phone being as old as it is now, it's unlikely that anything useful will be provided. Sorry. If you look around the forum you see dozens of warnings and examples of flashing the wrong firmware to your phone, most notably pie firmware. I think the only solution would be a pie modem that works for TMO too or a way to overwrite the modem nv value, both are pretty far out there.

is there a way we can erase flash memory and reinstall bootloader and everything from scratch?
Also, can you please help blankflashing the phone? any steps that I can take to be in edl mode?

 

[Sackgi]

Blankflash won't solve that problem. Once you flash a pie modem you're stuck with it. The only solution is a pie modem which doesn't exist for TMO. No one has found a work around for this and with this phone being as old as it is now, it's unlikely that anything useful will be provided. Sorry. If you look around the forum you see dozens of warnings and examples of flashing the wrong firmware to your phone, most notably pie firmware. I think the only solution would be a pie modem that works for TMO too or a way to overwrite the modem nv value, both are pretty far out there.

So it seems that the problem is flashing a newer modem that is not compatible with Tmobile. Can you expand on where the info is written and why it cannot be reverted?

 

[41rw4lk]

So it seems that the problem is flashing a newer modem that is not compatible with Tmobile. Can you expand on where the info is written and why it cannot be reverted?

The problem is TMO stopped with oreo, never made pie. So if you flashed a pie modem on TMO you're out of luck. When you flash a new modem most times it bumps your revision number up, so you can't roll back. You can typically only flash within the same revision or higher. Meaning you can't rollback to a lower revision modem.That info and warnings are all over this forum, and a lot of it is just anti-rollback.

Even on oreo whenever someone would flash the wrong oreo firmware, if it had a higher revision than what the proper firmware had, they would have to wait for an update that had an equal or higher revision modem to recover. Since TMO never and won't ever make pie firmware, going back is just not possible.

 

[Sackgi]

The problem is TMO stopped with oreo, never made pie. So if you flashed a pie modem on TMO you're out of luck. When you flash a new modem most times it bumps your revision number up, so you can't roll back. You can typically only flash within the same revision or higher. Meaning you can't rollback to a lower revision modem.That info and warnings are all over this forum, and a lot of it is just anti-rollback.

Even on oreo whenever someone would flash the wrong oreo firmware, if it had a higher revision than what the proper firmware had, they would have to wait for an update that had an equal or higher revision modem to recover. Since TMO never and won't ever make pie firmware, going back is just not possible.

So what you are telling me is that there is no way to rollback once the revision number is higher. I question how is that no one has figured it out how to overcome this. Is it not possible to write a script to trick the system to install the old modem using the new modem file? In other words, if what needs to be verified is that the revision number matches, would it be possible to modify the new modem file with the old modem one?

 

[41rw4lk]

Nothing is ever impossible, this site is a testament to that. Those revision numbers are most likely stored as nv values. How easy it is to edit those, idk. Can it be done without bricking your phone, idk. I do know that plenty of members have thrown everything they can think of at this problem to no avail, several of them just completely bricking their phone entirely.
What you're saying makes sense on paper, but you're talking about hijacking the boot process and injecting data long before android even enters the picture. That's qualcomm stuff, like blankflashing.
The reality is, it's an android 9 problem on a phone that's stuck on 8 while the rest have moved on to 10 and 11. Not a big market of players to delve into this problem, sorry. As for just editing a modem, not so easy. I've seen others trying in other forums. Not to mention what gets flagged and tripped trying to flash something like that. Once you edit an officially signed package, it's no longer officially signed. Sorry to be the bad news bear.