How can solve blackscreen at moment installing twrp ? - Xiaomi Mi A1 Questions & Answers

I tried to install several versions of twrp by fastboot and I ever get same error, someone can help me ?

Too laconic description. Write according to what instructions (link) you are doing the flashing.

Related

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

[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.

Possibly Dead Device? [P8/P9 Lite (2017)][PRA-LX1]

Urgent help needed as I'm leaving the country at the end of the week o any help is appreciated!
Just successfully rooted my device:
Black, Unlocked, PRA-LX1, UK, Dual SIM
After doing so successfully, I attempted to flash LineageOS from the following link:
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-lineageos-15-1-hi6250-devices-t3811583
Although when I completed Step 6 on the Installation guide and rebooted the phone, I started seeing the message:
------------------
ERROR MODE
Attention!
Please update system again
(Green Android picture)
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
------------------
Despite this, I didn't receive a box with my phone due to being second hand, and I didn't see the model number on the receipt as it was from a reselling store. I didn't remember to note down the specific model number
It'd be extremely helpful if someone could possibly help just from the device description above as I'm not sure if it's safe for me to just attempt to flash every stock rom for every other LX1 device out there.
---------------------------------------------------------------
Update:
To restore this, I connected via fastboot with a working USB & flashed an original stock recovery in the video found here
(Just in case their download link ever goes down, I have uploaded the same copy to my MEGA, found here)
The recovery installed fine when using the command
fastboot flash recovery oeminfo.img
Click to expand...
Click to collapse
Whenever trying to flash any other recovery such as twrp before this fastboot stuck on a loading icon.
The stock recovery seems to be downloading the original firmware, too.
PRA-LX1C432B202 is presumably the model.
Both the bootloader and FRA were unlocked when everything else was inaccessible.
Looks like the custom ROM's recovery that you've flashed is not compatible with PRA-LX1. Try to flash stock recovery. If not working, then flash stock firmware.
Thanks @Botar230!
I didn't see your comment until just now after deciding to edit this post since I've gotten a step closer to restoring my device.
Your solution was the method I used although I didn't know my phone model, so I found a random solution which just worked for my device, and the eRecovery seems to be downloading the stock firmware anyways. Thanks again
Before flashing this lineage os you should update to EMUI8 to get treble support, i suppose you was running EMUI5, hence the error mode.

I have bricked asus ZenFone max pro m1. Please help me unbrick it!!!

While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Can’t post it in the developer forum for this device as I don’t meet the requirements for posting it
i.am.the.best said:
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Click to expand...
Click to collapse
1. 1st try to flash fastboot rom,
after install fastboot rom if the phone stuck on asus logo or any other error then
2.Try to install Qfll file (select ww_no_fsg.xml file) after successful installation , boot your phone.
3. again connect your phone fastboot mode and flash fastboot rom
If every installation is successfully done then i am sure that your phone is boot properly in stock rom with lock bootloader.
because I faced same issue,
remember 1st try to install stock fastboot rom and then try to flash Qfil files
Wish you good luck :good:
Try flashing fw063 before flashing your custom rom.(that fixed for me)
if it didn't work try this (rooted):-
https://forum.xda-developers.com/showthread.php?t=2522762
Thanks bro. I have successfully unbricked my mobile

A20e (SM-A202F) stuck in download mode - error validating footer

Hello, i hope someone can help me. My goal was to install lineageos on the A20e. So i unlocked the bootloader succesfully. Then i wanted to install TWRP. I used heimdall for flashing (with: heimdall flash --recovery twrp.img). The process ended without any errors. But since this point the phone stuck in download mode. When i restart the phone (volume down + power) the phone runs rapidly into the download mode. On the top left corner it show an error message (look at the screenshots). I tryed to flash twrp again for two or three times and one times the orange recovery - the results are the same.
I can still reach the phone via heimdall or odin. i have downloades the latest stock rom. So i hope to unbrick the phone - but until now i have no idea how to do. Please tell me, if you know some hints. You can also post if you think its hopeless and there ist no way to unbrick the phone.
Update: I have flashed the stock rom via odin succesfully. now it starts normaly. Do i want to do a next try ;-) ...
Thread can be closed...
Thank U
Jan
Flash a blank vbmeta after flashing recovery.img, Using Heimdall

Categories

Resources