Verizon XT912 writing 'mbm' FAILED (remote: )

Verizon XT912 writing 'mbm' FAILED (remote: ) - Motorola Droid RAZR

Hello All.
Apologies if I am missing something obvious, but I am experiencing an issue with my US VZW XT912. Over a year ago, the phone bricked itself seemingly out of nowhere, only booting up into the "Encryption Failed" state. I went ahead and put it into AP fastboot and grabbed a copy of Matt's droid razr utility. I installed the motorola drivers and fired up the utility, then tried to flash the factory JB image to it WITH data wipe (option 1 on the utility). The process started, but right after "sending 'mbm' (512 KB)... OKAY [ 0.092s]" I got the message in the title of this post: "writing 'mbm'... FAILED (remote: )".
No matter how many different USB cables I tried, or how many different USB ports I used on several different computers and Operating Systems, I always got the same result; "writing 'mbm'... FAILED (remote: )".
I've gone as far as using ADB by hand and going through the flash instructions from an XML file step by step, but that fails in the same spot as well. RSDlite also failed.
My suspicions here are either A) The partition table is messed up somehow (which I unfortunately do not know how to fix) or B) The flash memory is actually just bad on the phone, which would obviously suck.
Now, most of my troubleshooting took place a year or so ago, so I've included a screenshot of Matt's utility that I just ran this morning. imgur<dot>com / QHsJbtO (sorry about the link; new user)
Any input is most appreciated.
Regards,
Steve P

physicsmaster131 said:
Hello All.
Apologies if I am missing something obvious, but I am experiencing an issue with my US VZW XT912. Over a year ago, the phone bricked itself seemingly out of nowhere, only booting up into the "Encryption Failed" state. I went ahead and put it into AP fastboot and grabbed a copy of Matt's droid razr utility. I installed the motorola drivers and fired up the utility, then tried to flash the factory JB image to it WITH data wipe (option 1 on the utility). The process started, but right after "sending 'mbm' (512 KB)... OKAY [ 0.092s]" I got the message in the title of this post: "writing 'mbm'... FAILED (remote: )".
No matter how many different USB cables I tried, or how many different USB ports I used on several different computers and Operating Systems, I always got the same result; "writing 'mbm'... FAILED (remote: )".
I've gone as far as using ADB by hand and going through the flash instructions from an XML file step by step, but that fails in the same spot as well. RSDlite also failed.
My suspicions here are either A) The partition table is messed up somehow (which I unfortunately do not know how to fix) or B) The flash memory is actually just bad on the phone, which would obviously suck.
Now, most of my troubleshooting took place a year or so ago, so I've included a screenshot of Matt's utility that I just ran this morning. imgur<dot>com / QHsJbtO (sorry about the link; new user)
Any input is most appreciated.
Regards,
Steve P
Click to expand...
Click to collapse
do you know which version the utility is?
what RSD Lite version?
Firmware version?
what is on AP Fastboot screen?
Sent from my XT1060 using XDA Labs

sd_shadow said:
do you know which version the utility is?
what RSD Lite version?
Firmware version?
what is on AP Fastboot screen?
Click to expand...
Click to collapse
Couldn't find a version number in the batch file of Matt's utility, but the created date on the file is August 26, 2014.
RSDLite 6.1.4
Was running stock JB when it bricked but I believe the phone shipped with ICS. I never loaded any custom ROMS, though.
"
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
"
Some (relatively poor) pictures of the AP screen: imgur<dot>com / a / mEFxz

sd_shadow said:
do you know which version the utility is?
what RSD Lite version?
Firmware version?
what is on AP Fastboot screen?
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
This is probably a dead thread, but I've been troubleshooting this issue on/off for over a year and still haven't managed to make any headway. Any other thoughts?

physicsmaster131 said:
This is probably a dead thread, but I've been troubleshooting this issue on/off for over a year and still haven't managed to make any headway. Any other thoughts?
Click to expand...
Click to collapse
What's the bootloader saying?
Sent from my sailfish using XDA Labs

sd_shadow said:
What's the bootloader saying?
Click to expand...
Click to collapse
Everything looks pretty normal on the bootloader. Trying to attach images but I keep getting an error so I'll type it out:
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: Size 16G
To Return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected

Some additional info:
When I try to boot normally I always get the "encryption failed" screen, and the reset button doesn't do anything.
When I try to boot into recovery, the android logo comes up, but I am never able to make it into the actual recovery menu.

Related

[GSM ONLY - TEST] EternityProject's Soft DEBRICK via FastBoot for Motorola RAZR XT910

Welcome to EternityProject Soft DeBrick for Motorola RAZR Thread!
What do we have today?
This is an image of the system partition of Motorola RAZR XT710 GSM EU. You should be able to use it for soft debricking your device in case of ****ups of the system partition.
Working on...
I don't know if this is working. I need someone with a bricked RAZR that can test it.
Why are you saying it is working?
From my past experiences on Motorola devices, I've learnt that a partition contains its signature, too. If you flash something via FastBoot, you'll flash it entirely, signatures included.
Other Infos:
System Version: 651.73.17.XT910.Retail.en.EU
Android Version: 2.3.5
Build Number: 6.5.1-73_SPU-9
Build Date: Sat Oct 29 15:40:46 CST 2011
APflex Version: GAS_EMEA_USASPDRRTGB_P034 GAS_EMEA_USASPDRRTGB_A010
Instructions:
1. Powerup your brain
2. Send your RAZR in FastBoot Mode
3. Decompress system.tar.bz2
4. fastboot flash system system.img
5. Be happy!
Downloads:
MegaUpload: Download
Let me know if someone of you has got a bricked RAZR and if this solution has been worked out for you. It'll be written on the first page of this thread and available for anyone wants to try a sure thing.
Remember that if you've got a bricked RAZR to return to Moto or to your provider, if you flash this you won't void your warranty more than you've already done, so, it's worth a try.
The EternityProject Developer,
--kholk

Thank you very much we have XT910, i cant test on it maybe get a bricking, if you have to XT910 plz .

link of megaupload is broken, send another link for download file pleaseeeee, my razr is in state of soft brick!

kholk send another link of download, your link is broken, i want download, thanks!

kholk please help Meteo on Italian forum we have only raimondo that help him. He bricked is phone when install a clock in notification bar. The software used overwrite with bad value framework and system. If possible explain to kholk the use of adb and where he can launch the command.

i tried to flash system image from fastboot , but don't flash, exit message signature verification failure, any solutions? please help me , my razr is bricked

Have you tried with moto fastboot?
Damn, it seems the image needs some work on it...!
Unfortunately I can't work on it until Monday, so, let's take some details on that, for example, on what device have you tried to flash it? EU? Retail? Branded? What was the previous original software version?
Sent from my XT910 using XDA App

my razr is retail version,and i bricked my phone when install a clock in notification bar, is in state of soft brick, i' don't have update software o firmware of my razr,i change only the recovery of phone (recovery bootstrap), help me please, when flash the system.img from fastboot exit message signature verification failure, another solution ?

Your phone can easily be fixed entering the official Moto Android Recovery and doing an hardreset. You don't need to flash a system image.

My RAZR xt910 is stuck on a black screen
AP Fastboot Flash Mode (S) (Flash Failure)
Device Status Code is LOCKED (0)
while the prompt windows
(bootloader) preflash validation failure
FAILED (remote
and hence the device does not restart again and remains on that screen
help me what should I do?
mine is a no brand bought on EU eXpansys

you can still flash from there...
desmonexus said:
My RAZR xt910 is stuck on a black screen
AP Fastboot Flash Mode (S) (Flash Failure)
Device Status Code is LOCKED (0)
while the prompt windows
(bootloader) preflash validation failure
FAILED (remote
and hence the device does not restart again and remains on that screen
help me what should I do?
mine is a no brand bought on EU eXpansys
Click to expand...
Click to collapse

pOOBAH1973 said:
you can still flash from there...
Click to expand...
Click to collapse
in what sense? I'm sorry but I did not understand what you mean

If you fail the flash or your device stays on flash failure, try to send "fastboot continue".
It may boot.

kholk said:
If you fail the flash or your device stays on flash failure, try to send "fastboot continue".
It may boot.
Click to expand...
Click to collapse
resume booting FAILED <remote unsupported command>

kholk said:
If you fail the flash or your device stays on flash failure, try to send "fastboot continue".
It may boot.
Click to expand...
Click to collapse
I did wipe the recovery stocks, but on reboot I get the screen Fastboot flash failure
select recovery - Tool the device reboots normally and it works but once cycled reappears Fastboot flash failure
I tried with fastboot fastboot continuous but FAILED to resume booting <remote unsupported command>
Help me

Try fastboot erase kpanic

@acer73
Oh, so..what I said you in PM did work?
So erase kpanic worked, huh?
That sounds good!

acer73 said:
Try fastboot erase kpanic
Click to expand...
Click to collapse
I try Fastboot erase kpanic
C:\Users\android-sdk\tools>fastboot erase kpanic
erasing 'kpanic'...
(bootloader) Command restricted
FAILED (remote: )
finished. total time: 0.010s
and now?

Umh. It seems they've disabled erase kpanic, too.
Mmh, we'll find something else.

kholk said:
Umh. It seems they've disabled erase kpanic, too.
Mmh, we'll find something else.
Click to expand...
Click to collapse
you have some ideas on how to solve my problem?
Tomorrow I have to return to eXpansys for replacement because my pre-series model is a bug and is subject to system
you say I do it under warranty?
thanks

FIX Stuck in FASTBOOT (Battery is dying)

If you are reading this and were having the same situation then time is very important here. First off if you are stuck looping into fastboot and cannot get it to do anything else quickly go throw your Razr onto a wall charger (This will not charge up your phone but it will stave off its death) Reboot until fastboot says battery OK.
Okay relax we have a little bit of time now.
I AM IN NO WAY SHAPE OR FORM RESPONSIBLE IF YOU BRICK YOUR DEVICE
Go download (adb /fastboot files) http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
And Download (Droid Razr Utility) http://www.filefactory.com/file/7ki1gjhtk1jj/n/DroidRAZRUtility1_51_ICS_COMPATIBLE_zip
I DID NOT MAKE EITHER OF THESE TOOLS BUT COMBINED THEY SAVED ME
1: Extract the adb / fastboot files to your desktop
2: Copy the SYSTEM.IMG out of the Razr utility into the folder with your adb / fastboot stuff
3: Hold shift and right click inside the folder with all your adb / fastboot files and select open command prompt here
4: Unplug your Razr and plug your Razr into your computer DO NOT REBOOT IT (Make sure it still says battery OK)
5: Type in the command (Do not type in the brackets) [fastboot flash system system.img]
6: WAIT its going to take a little over a minute to send the file and a little over a minute to write the file
7: Once the system file has been sent over reboot
8: You should see the Droid Razr boot image just give it time to start up
9: CHARGE YOUR PHONE
10: Go back and run Droid Utility and press 1 on its options to properly reimage the device.
I hope this was helpful I havent seen any guides like this before. I was almost to the point of caving in and tearing the Razr open but I really didn't feel comfortable doing that. I was looking everywhere for a guide to trick fastboot or get the Razr to charge in fastboot (No luck) I was in that scary place were I thought I had bricked my first phone ever but I was able to recover from it. If you still have life in your phone this should work. The reason the Droid Razr utility does not work is it reboots the phone and then knows the battery is dying. This guide tricks fastboot into thinking the battery is okay. Once fastboot is tricked you should be able to flash by pushing it yourself.
If your phone dies while doing this you are probably hard bricked now.
-Xaikar

Xaikar, I am in the exact same boat you were, stuck in bootloop after a botched flashing, slow leak of life for 2 days now, had to travel 2 hours to get high speed so i can dl these damn files, I live in boondocks for the moment where service and internet is piss poor. Anyways tried your method with a system.img from the later version of Matt's DroidRAZRUtility1.6_final (shouldn't matter changelog didn't mention anything about changing the file); and it had a INFOPreflash validation failure FAILED <remote: >. So I am running out of ideas & time man, tried everything else. probably have to find a different system.img, which version was your phone, or how would I go about making my own system.img from the fastboot files for my signed GSM-LATAM system?

Try getting a GSM version of a system.img, I was able to do the utility one because I am cdma. Also try flashing the recovery. fastboot flash recovery recovery.img that might help get back a working recovery so you can get some kind of image on there to charge the Razr back up.

HELP!!
Idk if im just THAT computer dumb but i finally downloaded the files after roughly 4 hours and i dont see a "SYSTEM.IMG" file within it. You are literally my only hope cause i've looked everywhere for a solution and this is the only one close to what i need!!!

Did you extract the utility into its own folder? Inside of that folder there should be a System file somewhere you might not see system.img unless you have extensions turned on. You should still see a SYSTEM file name it should be rather large in size. Let me know if that works.

how will I know when the system file will be done sending in order to reboot? it just keeps saying sending system?

Should take a few minutes 5 at the most. It should say something like writing system complete. Let me know if you need more help.

apixelheDrew said:
Xaikar, I am in the exact same boat you were, stuck in bootloop after a botched flashing, slow leak of life for 2 days now, had to travel 2 hours to get high speed so i can dl these damn files, I live in boondocks for the moment where service and internet is piss poor. Anyways tried your method with a system.img from the later version of Matt's DroidRAZRUtility1.6_final (shouldn't matter changelog didn't mention anything about changing the file); and it had a INFOPreflash validation failure FAILED <remote: >. So I am running out of ideas & time man, tried everything else. probably have to find a different system.img, which version was your phone, or how would I go about making my own system.img from the fastboot files for my signed GSM-LATAM system?
Click to expand...
Click to collapse
I ran into a problem using the util today but you can simply unzip another rom and replace the files in the " files " folder to the new rom and then run it again. It will install it via fastboot just like the rom that came with it.

I got the same flash failed message.. have you found any to fix it?? I tried flashing the recovery and I got the same message for that too

Can you be more elaborate on the error mesaage
Sent from my Galaxy Nexus using xda app-developers app

INFOPreflash validation failure
FAILED <remote:
This is what I get when I try to flash the system.img

Is it a GSM or CMDA Razr?

I have a CDMA Razr

uuh... all I get is a <waiting for device> message. I can't get the phone to respond. It's stuck on the red droid-eye boot screen. I'm CDMA, btw
I have the system.img file in the same folder as all your other files, and followed the directions exactly. Help?

Florestan2 said:
uuh... all I get is a <waiting for device> message. I can't get the phone to respond. It's stuck on the red droid-eye boot screen. I'm CDMA, btw
I have the system.img file in the same folder as all your other files, and followed the directions exactly. Help?
Click to expand...
Click to collapse
You need to install the MOTOROLA Drivers that why it says you are waiting for device. I need to edit the guide to include that sorry I would do it now but I am crazy tired.

Xaikar said:
You need to install the MOTOROLA Drivers that why it says you are waiting for device. I need to edit the guide to include that sorry I would do it now but I am crazy tired.
Click to expand...
Click to collapse
They are installed.... I've checked 3 times...

When you are in the command prompt. Try typing
fastboot devices
Did it show any devices?
Also try loading your task manager and killing any ADB.exe running so it can reboot those utilities.

Xaikar said:
When you are in the command prompt. Try typing
fastboot devices
Did it show any devices?
Also try loading your task manager and killing any ADB.exe running so it can reboot those utilities.
Click to expand...
Click to collapse
It returns:
014e64e40101100D fastboot
Yup - killed all instances of ADB* in task manager, too.

Great so it sees the device thats great news. What do it say about the battery does it say its low or battery OK?

Xaikar said:
Great so it sees the device thats great news. What do it say about the battery does it say its low or battery OK?
Click to expand...
Click to collapse
It says:
Device is locked. Status Code: 0
Battery OK
OK to program
Transfer Mode:
USB Cable

unbricking RAZR XT910

Okay, so after nearly a whole day of not getting any work done trying to revive my effed-up RAZR, reading through the forums and beyond, I think it's just time to buckle down and ask for some help.
So I'm trying to revert to stock ICS on my RAZR after going through a bunch of custom ROMs. Downloaded a bunch of Fastboot files and tried both the Eternity Project batch file and flashing through RSD Lite (I'm on 6.14), and no go. Results are as follows:
1. Eternity Project flashes successfully(?) albeit with several error prompts, specifically:
a. writing 'boot'... INFOPreflash validation failure
b. writing 'cdrom'... INFOPreflash validation failure
c. writing 'recovery'... INFOPreflash validation failure
d. writing 'devtree'... INFOPreflash validation failure
End result for this is that it boots into the green Android with its chest open and a red exclamation mark and then into the Motorola Dual Core logo for a couple of seconds then goes to a blank screen. From there, it's unresponsive, but no "Failure" prompts reflected on AB Fastboot Flash Mode.
2. RSD Lite fails much earlier on. It stops at flashing cdt.bin, phone returns FAILED and then stops. Afterwards, phone only boots into Fastboot mode and shoes a "Flash Failure" prmopt next to AB Fastboot Flash Mode. I read that cdt.bin is usually linked to flashing a wrong region image onto my phone. Thing is, this phone was given to me by my aunt, and she only gave me the phone itself. No box, no nothing, and she doesn't remember where she bought it from, as it in turn was given to her by a former boyfriend who she no longer has contact with. Do I have any alternatives aside from downloading every single file on the SBF repository and trying them all one-by-one?
Any help?
Other info is that I used to be on stock Motorola ICS on System_1 partition with AOKP Unofficial Jelly Bean on System_2 partition. Bootloader is 0A.6C, RAZR XT910 GSM.

Failed to boot 4 Starting Fastboot protocol support

So last night my phone decided to bring up a screen
"Failed to boot 4
Starting Fastboot protocol support"
I have searched and searched and searched and have found no one with this same issue...I can not get into RSD mode at all, ONLY Fastboot mode and when I try to flash or erase recovery i get
"erasing 'recovery' ... Failed (remote: (00180001))"
"sending 'recovery' (4786 KB) ... OKAY [ 0.437s]
writing 'recovery' ... FAILED (remote: (00180002))"
I've tried just about everything but am no where near an expert so please any help would be greatly appreciated as this is my only phone and I don't have money for another one any time soon...Thanks in advance

tony442 said:
So last night my phone decided to bring up a screen
"Failed to boot 4
Starting Fastboot protocol support"
I have searched and searched and searched and have found no one with this same issue...I can not get into RSD mode at all, ONLY Fastboot mode and when I try to flash or erase recovery i get
"erasing 'recovery' ... Failed (remote: (00180001))"
"sending 'recovery' (4786 KB) ... OKAY [ 0.437s]
writing 'recovery' ... FAILED (remote: (00180002))"
I've tried just about everything but am no where near an expert so please any help would be greatly appreciated as this is my only phone and I don't have money for another one any time soon...Thanks in advance
Click to expand...
Click to collapse
I would try to go flash the stock rom via RSDLite to make sure you are in a good state. Download the stock rom and try that first.

I think you can flash a system.img in fastboot
Sent from my MB855 using xda app-developers app

I cannot get the phone into RSD mode at all. The phone does not respond to volume up or volume down during power up...just gives me the Motorola Dual Core screen and then the failure I stated above....
Can anyone direct me in the direction of a system.img for the photon that could get me up and running and possibly a little bit of guidance in the process?
Thanks again for looking into this post as this has always been my favorite phone and I would love to get this back if I could.

UPDATE
So far I have tried to flash a boot.img to the Photon but I do not believe this is working properly as I still am not able to get anything other than the Failed to boot 4 message.

Has anyone ever booted into RSD from fastboot? i've looked into the command line help but it tells me nothing about RSD mode ...has anyone gathered a system.img from anywhere for the Photon? Any help at all would be greatly appreciated with a donation...please......

Friend
If this happened during normal functioning (not during flashing) there is a chance of hardware failure
Sent from my Motorola Electrify using Tapatalk 2

pradeeppk said:
Friend
If this happened during normal functioning (not during flashing) there is a chance of hardware failure
Sent from my Motorola Electrify using Tapatalk 2
Click to expand...
Click to collapse
That's what I have come to conclude but didn't know if anyone could help with fastboot mode just to rule any software failure issues. Thanks
Sent from my ADR6300 using xda premium

"Your device is corrupt. It cannot be trusted and will not boot."

Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
for g5 the command are these:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
Click to expand...
Click to collapse
I tried those, and that's how I got here.

Try reflashing twrp.img in fast boot (see Autoprime's AIO post for instructions) then try booting into twrp - then at least you can wipe and flash a new stock/custom rom!
Best of luck!

megatron_lives said:
Try reflashing twrp.img in fast boot (see Autoprime's AIO post for instructions) then try booting into twrp - then at least you can wipe and flash a new stock/custom rom!
Best of luck!
Click to expand...
Click to collapse
Thanks for the reply!
Reflashing TWRP doesn't work as the device is somehow locked again:
Code:
fastboot flash recovery twrp-3.1.1-0-h850.img
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.471s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.490s
Unlocking fails as mentioned in my fist post.

did you try flashing stock kdz file with lgup? if it boots you can later try unlocking.

ozkaya said:
did you try flashing stock kdz file with lgup? if it boots you can later try unlocking.
Click to expand...
Click to collapse
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.

gqo said:
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.
Click to expand...
Click to collapse
good point. how about if you try fastboot flash recovery twrp.img or if it fails flash stockrecovery.img?
---------- Post added at 06:11 PM ---------- Previous post was at 06:08 PM ----------
gqo said:
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.
Click to expand...
Click to collapse
if flashing recoveries fail, try fastboot flash bootloader stockbootloader.img (you can find these images from stock zip format in the forum)

Thanks everyone for the help! Just to be thorough, I tried entering download mode for what felt like the 42nd time, and whaddaya know, it worked! So I'm currently in the process of returning to the point I was on before I tried that ill-fated update of LineageOS. Thanks again everyone!

gqo said:
Thanks everyone for the help! Just to be thorough, I tried entering download mode for what felt like the 42nd time, and whaddaya know, it worked! So I'm currently in the process of returning to the point I was on before I tried that ill-fated update of LineageOS. Thanks again everyone!
Click to expand...
Click to collapse
what exactly have you done? i have the same problem

trinity_user said:
what exactly have you done? i have the same problem
Click to expand...
Click to collapse
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!

gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
did u lost ur imei?

Zer0_rulz said:
did u lost ur imei?
Click to expand...
Click to collapse
Not sure what you mean. If you're wondering whether I lost that piece of information: no, it's printed on a sticker on the back of my phone. In general there's usually a sticker with your phone's IMEI somewhere on the packaging or, like in my case, on the device itself.

gqo said:
Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
I tried those, and that's how I got here.
Click to expand...
Click to collapse
Wow... It's uncanny how close this is to the my own situation, except that in my case it's a G6 (US997).
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
Again I did the same, bar the tea, but unfortunately my tale does not end quite so happily... Not yet at least. I can "upgrade" with literally no problems using LGUP and one of the few G6 KDZs available, but when it's time reboot my phone always boots into the fastboot for bootloader unlock mode. I can use fastboot commands but my bootloader relocked at some point and I'm still not able to unlock it again. No matter what I do my phone always boots to fastboot... Except when I do the recovery key combination and press "Yes" twice, in this case there's a brief "erasing" animation and then I'm back to fastboot.
I realize I'm using a different device, but would anyone happen to have any thoughts on this? This is my first time using a non-Nexus LG and I must admit I'm struggling a bit to get out of this mess. The recovery and fastboot modes also look quite bare to me, but I might just be using the wrong.
Cheers!

You are a life saver
Thank you for detailed tutorial.
My H850, which I managed to almost dead brick, like yours (of course from the same source - reddit ) after few minutes with uppercut + lgup ressurected with all the files and apps inside
So, after that I'm running through factory reset now and trying to unlock once again.
Thank you

Have the same problem but......
gqo said:
Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
I tried those, and that's how I got here.
Click to expand...
Click to collapse
i have the same problem but i can still use the phone, how can i delete this error?
the boot loader it s not working.......PLEASE HEEEELP

Use uppercut

Hello. I have the same problem. I was on LOS 15.1, then i deviced to go back on stock. I relocked the bootloader and i have this messege. When i go to download mode, lgup recognize the phone, but after 10 seconds the phone reboot and go to that screen again. Any suggestions?

volen said:
You are a life saver
Thank you for detailed tutorial.
My H850, which I managed to almost dead brick, like yours (of course from the same source - reddit ) after few minutes with uppercut + lgup ressurected with all the files and apps inside
So, after that I'm running through factory reset now and trying to unlock once again.
Thank you
Click to expand...
Click to collapse
I've got this problem also, thanks to those lines put into 'terminal'.
I can get into download mode easily, however by the time I then open Uppercut and try doing anything the phone reboots itself back into the 'corrupt' screen and keeps looping on that.

mgolder said:
I've got this problem also, thanks to those lines put into 'terminal'.
I can get into download mode easily, however by the time I then open Uppercut and try doing anything the phone reboots itself back into the 'corrupt' screen and keeps looping on that.
Click to expand...
Click to collapse
Maybe unlock.bin is corrupted, try ask LG to resend the file.

Better Mobile App

welcome