Hard brick after LOS installation

[Sackgi]

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.

Just because it is no longer officially signed, doesn't mean that people that ended up with a paper holder wouldn't mind trying this. I know this is an old phone and such, but it is just a shame to see how disposable technology becomes in just a couple of years.

 

[41rw4lk]

Well to be fair, most of it was just people flashing the wrong firmware, they dug their own graves. Plus there are always risks when you start modding your phone, you have to ne prepared to assume those or move on. Hardware wise it is still a half solid phone no doubt, but Moto dropped the ball on support. That's why I didn't get another Moto phone, I voted with my wallet. That's a shame too because I like Moto, but the way they pulled they rug on android 9 after promising it, then saying it was too complex to implement was a deal breaker.
As for those with paper weights or bricked basebands all I can say is get experimental. You've got nothing to lose. I don't have my phone anymore, Moto's experimental shatterproof screen lifted on me and it wasn't something I wanted to invest in anymore. I couldn't try anything to help if I wanted to.

 

[Sackgi]

Well to be fair, most of it was just people flashing the wrong firmware, they dug their own graves. Plus there are always risks when you start modding your phone, you have to ne prepared to assume those or move on. Hardware wise it is still a half solid phone no doubt, but Moto dropped the ball on support. That's why I didn't get another Moto phone, I voted with my wallet. That's a shame too because I like Moto, but the way they pulled they rug on android 9 after promising it, then saying it was too complex to implement was a deal breaker.
As for those with paper weights or bricked basebands all I can say is get experimental. You've got nothing to lose. I don't have my phone anymore, Moto's experimental shatterproof screen lifted on me and it wasn't something I wanted to invest in anymore. I couldn't try anything to help if I wanted to.

You mentioned there were other posts where people were trying to revert old modems into updated revision phones. Do you recall which post was that? I'm curious to know if someone might have more info on how I could give this a try.

 

[hasanabasi0231]

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]

.....

 

[hasanabasi0231]

Hi my friends, I solved this problem. To solve this problem, you have to open the phone and disconnect the battery socket, connect the USB and do the burning.

1 Download the drive.
2. Download the Qualcomm 9008K drive in the second post
3. Open the phone
4. Disconnect the battery socket
5. Connect the USB to the phone and start flashing.


Thanks to my dear friend Mohammad K for solving this problem.





Long live Iran