Bootloader Flashing_locked, unable flash any img files. Please help - Moto G5 Plus Questions & Answers

my Bootloader is showing Flashing_locked, unable flash any img files. Please help, i'm even unable to open recovery, it is giving Invalid boot image header, failed to load kernel.

Related

error flashing Zip files

I flashed a few bootloader animations and later it stopped working. Whenever I try to flash them through flashify, it shows this error:
In case the image doesn't show, I uploaded it to imgur.
http://imgur.com/KRrnSjE
Have you tried flashing them directly in TWRP manually?

lenovo k4 note error in boot.img

hey
i tried unlocking the bootloader using recovery unlocking methods and through sp flash tool, rooting the android version 5.1 thorugh kingroot, then after installing the twrp.img it reboots and throw up an error showing as invalid .img file and install a lenovo.img itself and further it keeps restarting i tried the same with many twrp(recovery.img) files available in many links found in youtube and also in few threads of xda, but nothing working rather than landing up in the same boot error.
pl somebody help me out in the link with working custom boot loader .img and also with steps rather than facing the landing up in the same error.
Same problm
I will try to install recovery with flashify and my devices can't turn on
It will shows invalid boot.img
Help me.....
Sorry for my bad English

Corrupted partitions?

Hello, I was trying to downgrade from N to MM and somehow i lost my system and data partition. I have the custom revolution recovery and i cant mount data or system on the mount menu, also when i try to flash any package it gives me the error "cant mout /datad/system oartition". I also tried to extract system from a original firmware and tried to flash it with fastboot, but it gives me the error "FAILED (remote: sparse flash write failure)". Is there a way to get back my partitions and reflash MM on here, or have i just won a new (very slim) paperweight? Any help would be much appreciated sice im kinda dependent on this phone.
For some reason system is able to mount now... but still nothing in the data partition , it show 0B
i have the same issue
Have you tried to flash oeminfo?

[SOLVED] [Loop] Your device is corrupt it cannot be trusted and will not boot

Hello,
I have an issue with my brand new G6.
It is in a loop "Your device is corrupt it cannot be trusted and will not boot" , no more recovery available.
What i did:
I unlocked the bootloader and flashed Magisk via TWRP the device displayed that the partition was corrupt and need to be erased.
After that the device was in a loop to twrp, whatever the wipe or ... no system boot.
I read that i had to format the data partition so i adapted a what i found here to my available partitions
https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the device is now in a constant loop.
Does someone can help me please ?
is there any way to recover it ? download mode ? how ?
Update : I succeed to boot into download mode but LGUP gives me an error while trying to flash
error 0x2000 ... ... cefs::initialize()
docizoc said:
Hello,
I have an issue with my brand new G6.
It is in a loop "Your device is corrupt it cannot be trusted and will not boot" , no more recovery available.
What i did:
I unlocked the bootloader and flashed Magisk via TWRP the device displayed that the partition was corrupt and need to be erased.
After that the device was in a loop to twrp, whatever the wipe or ... no system boot.
I read that i had to format the data partition so i adapted a what i found here to my available partitions
https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the device is now in a constant loop.
Does someone can help me please ?
is there any way to recover it ? download mode ? how ?
Update : I succeed to boot into download mode but LGUP gives me an error while trying to flash
error 0x2000 ... ... cefs::initialize()
Click to expand...
Click to collapse
Can you boot to TWRP?
Did you make a backup and have access to it? Especially the EFS partition? If you do, restore the EFS partition.
If you can boot to TWRP, try the following:
- wipe everything (the option where you have to type 'yes').
- download lineageOS and flash it. If this is working fine, install whatever ROM you want to install.
no access to twrp anymore , no backup , only access to download mode now
is there a way to flash back twrp or stock recovery from download mode ? boot into fastboot ?
(i know... i have no excuses , but made that so many times without issues ...)
thank you in advance
Maybe you should go in download mode and flash stock Rom with LGUP.
LGUP gives me an error while trying to flash the rom error 0x2000 ... ... cefs::initialize()
Can you flash twrp through lgup or fastboot?
For those that could be in the same situation i finally succeed to flash with LGUP last version but without the 8894DLL
the error was probably coming from the dll.
Cheers and thanks all for the answers
docizoc said:
LGUP gives me an error while trying to flash the rom error 0x2000 ... ... cefs::initialize()
Click to expand...
Click to collapse
It's probably a problem with the DLL, try to extract it from the kdz and input it in Lgup folder (I don't remember where and I'm not home, check the main thread for that) and after that retry flashing
EDIT : well you were faster than my phone glad it worked for you.

PSA: How to recover from soft brick after installing twerp over lineage OS

Hello every one. Total noob here. But this is to answer a question I had earlier but found no help with at least upon a basic google search. Earlier I bricked my Tab S6 Lite while trying to install TWRP to replace the current recovery. Hind sight being 20/20 I know now that TWRP is no long active and that is was simply a bad idea. I ended up stuck in odin boot loop with the error message of..
Odin Mode (DT Load Fail)
[DTH] dt table header check Fail: <unknown error>
Load_kernal: Could not do normal boot. (DT LOAD FAILURE)
vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA : No sign info
This put me in a bad spot as ADB, and Fastboot were no longer an option and I could not pull a viable pit from Tab using Heimdall, and Odin will not allow you to flash the recovery that can be found in Lineage downloads page as they are img files.
The solution I found was to use a program to change the recovery.img file found in the Nightly lineage zip folder into to a tar file using the program. And then flash that tar file using odin. This brought me back to standard liniage with no data loss.
Disclaimer: The file attached is not my own, download and use at your own risk.
I do not recommend you mess with software if you're not ready to brick and fix your own device.
Thanks

Categories

Resources