Database Users

[Q] LS980 - Error: Device midel is diiferent.

Hello friends.
I'm russian. I try to write correct and clear.
I have a really hard problem with my LG LS980 - it is bricked.
I read many instructions and threads about restoring but nothing helped me.
When I flash my phone by Lg Flash Tool it stops with error: Device midel is different.
As you can see on the first attached picture the phone's model is the same as dll's model.
When I flashing it with another dll(LGUP_8974.dll) it writes CrossDL error(the second picture I attached).
Is there any possibility to ignore model verification in LG Flash Tool?
Now my LS980 has 3 modes: Stock Recovery, Download Mode, Black screen after LGs logo when booting.
In every mode there are the same devices and drivers(the same as on the Download mode) in device manager.
When flashing by KDZ for another model(D802) it get error on 49%.
I have Riff Box but there no possibility to ressurect at this moment it doesn't supports.
Help me please!

[Q] Security Error Code : 1003 (No download, No recovery, Bootloop)

Hello I got this device (MS345) last week and today I was going to unlock bootloader, everything was going ok, i put the MS34510f_00 kdz and it got me an error (couldn't connect to server i think it was) but when I tried to reboot the phone it just gave me this lines that says "Secure booting error! Error Code: 1003" I can't get my phone booted normally or going to download mode or try recovery, when i try to do a factory reset I select the yes option but then it gives me the same security error, what can I do? please help me

It happened to me the same thing I had to use the warranty I did not find any solution

trixi3 said:
Hello I got this device (MS345) last week and today I was going to unlock bootloader, everything was going ok, i put the MS34510f_00 kdz and it got me an error (couldn't connect to server i think it was) but when I tried to reboot the phone it just gave me this lines that says "Secure booting error! Error Code: 1003" I can't get my phone booted normally or going to download mode or try recovery, when i try to do a factory reset I select the yes option but then it gives me the same security error, what can I do? please help me
Click to expand...
Click to collapse
When this occured with me i just reinstalled de stock rom with lg flash tool and this put me automatically into download mode when i connected my phone in pc

[H918] Stuck in Serial USB Mode (Download Mode) Usual Fixes Not Working O.o

So I usually don't have to post for help as I've been doing this for a while and don't usually get this stuck.
Situation:
Rooted V20 H918 (T-Mo variant) with TWRP installed and working fine on v10d.
Phone got a little warm this afternoon so I rebooted figuring a process had run away or something (you know android).
Phone reboots and comes up to the Firmware Update screen. Mind you this isn't the same screen that folks often confuse as bootloader. There's no ADB/fastboot access only serial over USB.
Load up LGUP with Uppercut and grab the v10i KDZ. That runs flawlessly, finishes the upgrade and reboots.
This is where things go pants up.
When it reboots, I still get the triangle warning screen saying that the bootloader is unlocked and then it goes right back to the firmware update screen.
Things I've tried:
I've attempted to get into TWRP/recovery (Volume Down). I know I did the buttons right because it does that whole asking me if I'm sure I want to wipe my device, blah blah blah... but then after answer Yes twice... back to firmware update.
I've attempted to get into bootloader (Volume Up). Nothing... Right back to firmware update screen.
I've successfully flashed a 10i KDZ file using LGUP (In upgrade mode since refurb mode isn't supported by that kdz) both with Uppercut and extracting the LGUPc.dll file out of the KDZ archive. It successfully completes, reboots and goes right back to the Firmware Update screen. No errors, no changes, still no recovery, still no fastboot.
I've attempted flashing the full 6-point-something gig 10d TOT file in refurb mode and that dies out at about 11% with an invalid response error.
I've attempted flashing the boot partition only TOTs and in refurb mode that gets to 99% then dies with the invalid response error.
I've attempted flashing the recovery only 10d TOT in both refurb and upgrade mode and they both say "unable to determine OS version" and LGUP crashes out.
Things I haven't done:
I haven't been playing with ROMs or kernels.
I haven't been flashing random zips
I haven't been editing system files at all.
I haven't been washing, chewing, attempting to flush down the toilet or otherwise abusing my device.
Really I haven't been tinkering. I only wanted root for a couple of things (Ad Away primarily). So I'm certain I've done nothing negligent to cause this.
So I'm at a loss. LGUP completes successfully but doesn't fix anything. Halp?

UPDATE: LG Support Tool previously said it had the latest version of all software 10d, but now doesn't read the software version and lets me kick off the Upgrade Recovery Function. That appears to chooch fine but then tells me that it can't proceed because the battery is low. Checking the battery with a multi-meter shows it at 4.30v which is 100% according to spec.
So close... yet so far...
Thoughts?

Did you try that?
https://forum.xda-developers.com/v20/how-to/h918-dll-lgup-t3535988

netgar said:
Did you try that?
https://forum.xda-developers.com/v20/how-to/h918-dll-lgup-t3535988
Click to expand...
Click to collapse
Did you read my post? Did you see that I actually posted said DLL to that thread you linked me to?
Yes, I've tried it.

So after getting around the low battery warning crap, I finally got the LGMobile Support Tool to attempt to do something.
Basically I have to go to recovery update, punch in my IMEI and it chooches along. I then got it to download the latest update which looked to be the H91810i_00.kdz as I was snooping in it's hidden "phone" folder under ProgramData\LGMOBILEAX\
As soon as the download completes it deletes this folder and the downloaded kdz without ever talking to the phone (Phone's serial console output never updates). And then this screen with what looks like untranslated text (attached since I can't figure out how to properly embed an attached image.)

I see I'm going to have to start a bounty to get some help. ?

So check it out. I did learn something about the v20 which is how to get it into fastboot mode directly. Best way to do it is to turn off the device, then plug in a USB cable (connected to power or computer) and about 0.5 to 0.75 seconds later, just hit the volume down button. Boom, fastboot.
Unfortunately for my device, the only thing I'm able to do is lock or unlock the bootloader. Getvars spits this out:
Note that bootloader and baseband versions are blank.
I'm unable to erase or flash anything, I get (Remote: Unknown Command.)
So I relocked the bootloader and got a replacement from TMO. I honestly don't know if my rooting it would have caused such a catastrophic failure. But to be sure, since I need my v20 to be reliable. I think I'll refrain from tinkering until it becomes much more stable. Such as life on the bleeding unsupported edge.

XT1762 stuck at bootscreen, no options in recovery mode & baseband, sn, sku etc. lost

XT1762 stuck at bootscreen, no options in recovery mode & baseband, sn, sku etc. lost
Hello,
2 weeks ago many apps started to crash after I started the 9GAG app, and first the phone (Motorola moto e4 XT1762 [MEDIATEK]) ran very slowly, and then didn't respond. So I restarted it, but immediately after I entered my PIN all apps began to crash again. So I made a backup in phones recovery mode, then first wiped cache, which didn't help, and then made a factory reset, which didn't help either. So I decided to reflash the firmware with SP Flash Tool. From recovery mode I knew I needed version 7.1.1/NMA26.42-169/300, but first couldn't find it online. So I tried Motorola_Moto_E4_XT1762_MT6737M_WOODS_NMA26.42_75_04082017_7.0 first, but the problems remained. Then I found XT1762_WOODS_7.1.1_NMA26.42-169_subsidy-UNLOCKED_model-EMEADS_CFC_SVC and flashed it, which helped. Then I tried to restore the backup, but after that the phone got stuck on bootscreen. So I wiped and factory resetted again, which didn't help, so I flashed again. Unfortunately this time it didn't help, so my phone is always stuck at bootscreen. And in fastboot mode it now tells following:
Code:
AP Fastboot Flash Mode
Baseband: (not found)
Product/Version: null
SKU: null
Serial Number: null
IMEI: null
Console: null
BATTERY: OK
Engineering
Software status: official
Transfer Mode: Cable not Connected
Device Status: locked
And when I enter recovery mode no options are listed anymore. It's just a black screen with the text "Supported API: 3" in the bottom left corner.
So I installed "Rescue and Smart Assistant" and reinstalled android over it, but this didn't help.
Then I looked for another solution, and found this howto: https://forum.xda-developers.com/moto-e4-plus/how-to/fixed-moto-e4-plus-xt1771-unknown-t3831831
But at step 8 I don't get the error message, it's just stuck at bootscreen again, and also MAUI doesn't detect the phone like it should according to step 9 (the original link is offline, so the thread opener posted another one: https://forum.hovatek.com/thread-12328.html). I used the ROM XT1762_WOODS_7.1.1_NMA26.42-169_subsidy-UNLOCKED_model-EMEADS_CFC_SVC.xml.zip and programutags_XT1762_EMEA_Dual_SIM_V2.bat from here: https://mirrors.lolinet.com/firmware/moto/woods/official/RETEU/
I also tried it with flashing Motorola_Moto_E4_XT1762-DS_MT6737M_NMA26.42-11-3_3_7.1.1, and again stuck at bootscreen.
Now I don't know what to do else. So could please somebody help me?
Best regards

Has no one any idea?

@msfm44 Did you find any solution? My story is similar, I went a few steps further to brick it completely.
What I did I have installed Lineage 14 on it and it worked well, then I found a 16 version and wanted to install it. After that it would not boot into anything, was stuck in booting. Didn't help to reinstall 14 or wipe or anything. Then Then I downloaded the image you mentioned and flashed all the files preloader, boot, oem, system, etc. After that it would not do anything. Now if I plug it in the computer I only see the white LED on, and if I press long the power button then in "lsusb" it shows up for 2 seconds as MediaTek Inc. MT65xx Preloader.

Need help with a hard bricked Redmi Note 7.

Basically what the title says, Back in September 12, 2021, at 4 AM I had woken up out of nowhere and I thought I'd wanted to give that engineering firmware of my lavender a try, but then I did something bad, after digging in what the issue was and why my phone wasn't booting and was stuck in the splash screen (fastboot wasn't working either), I found out that there was a firmware OEM security certificate mismatch between the UEFI Bootloader (XBL.ELF) and the "Application Bootloader" which in android's case is "Kernel Flinger" (abl.elf), the mismatch between the certificates causes the phone to not load abl.elf and it ends up getting stuck at the splash screen and does nothing.
TL;DR my phone's hard bricked and won't boot up, fastboot won't work either.
I tried to unbrick it through the "Emergency Download Mode", also known as EDL Mode, but to no avail, I keep getting the exact same error I did before the battery this phone originally came from had died.
The error is "TARGET SAID: ERROR: Only nop and sig tag can be received before authentication."
I believe I'm getting stuck at xiaomi's authentication thing but I've tried everything, flashing stock ROM, flashing engineering ROM, trying the patched firehose that was available since a long time, trying the patched firehose that was in xiaomiengs, nothing.
Before the battery had died though, if I remember correctly, when I hadn't connected the battery to the phone and turned in on in a long time, after replugging everything and turning it on, the phone would power on it's battery LED and after getting it in EDL, instead of getting an EDL Authentication error, I was getting some weird write error and it would stop, after resetting the phone back, I'd get the same write error, I'm going to retest the thing where it'd get a write error and get past the EDL auth, but I'll have to wait.
I hope you all can give me some tips on how I can unbrick it and hopefully salvage this phone, then I can have it next to my Poco X3 NFC which I got 1 month ago and 23 days ago.

Oh and also if you were wondering why I was trying to flash the engineering firmware again through EDL even though it supposedly hard bricked my phone, that's not the case at all, what actually hard bricked it was that I had flashed MIUI 10's abl.elf (Application Bootloader/Kernel Flinger) and after rebooting, it didn't boot.
I'll admit that it was very dumb of me to flash just one firmware image out of all of them, but I should mention that I did it out of being afraid over the fact that flashing the engineering firmware might've caused my device to be stuck with it until I flashed the stock/production firmware through EDL Mode, now, I know I could've flashed it through fastboot but there was another problem with fastboot and it was that it would not flash anything due to a "image size mismatch error".
What were my findings after all? Well, Lavender (AKA Redmi Note 7) seems to have encryption stuff built right into it's bootloader which was what forced me to factory reset the device (Wipe out the data partition or "userdata"), I forgot to test whether disabling encryption wouldn't cause the entire encryption to not work (It does the same in stock/production firmware).
Another thing I also found out was that the UEFI Bootloader of the engineering firmware build is that it seemed to not have OEM certificates setup properly so it allowed the booting of MIUI 12.5's Kernel Flinger binary (abl.elf), one thing that confuses me is the fact that it wouldn't boot MIUI 10's Kernel Flinger binary (abl.elf).

Okay, update here, I've been messing around, getting help from some people in Telegram and I've managed to get past EDL Auth, unfortunately for me, it says "Failed to open the SDCC Device slot 0 partition" when attempting to flash.
I tried through Qualcomm's Product Configuration Assistant Tool and I got that error, I tried through QFIL, same error, I tried through Mi Flash and various different versions, still same error.
Does anyone have any idea what the error could mean? I hope it doesn't mean that my phone's eMMC isn't dead, because from what I remember it isn't.