Stuck at EMUI - Huawei P20 Lite Questions & Answers

I tried to flash stock rom by flashing Img files one by one I flashed :
Kernel
System
RAMDISK
recovery_ramdisk
All these worked fine but when I flashed Vendor.img it says
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460706 KB)...
OKAY [ 18.084s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
Then I rebooted my phone it asked for factory reset I click that and it booted again and now it's stuck on EMUI screen nothing is happening I press hold power button it boot again to EMUI screen my phone is still ON I can't power off of enter bootloader. My phone is unlocked I don't know what to do

Related

TWRP flashing trouble

Also it will not show up in the LG up app this is what I get when I try to flash an recovery "target reported. Max download size of 536870912 bytes
Sending 'recovery' (31748kb)...
Okay [0.710s]
Writing 'recovery'...
FAILED (remote: unknown command)
finished. Total time .728s"
I have to be in ptp mode just to get adb to recognize my phone any suggestion. My boot loader is unlocked, and I cannot use hard keys to boot into recovery or download mode.

Oneplus x not booting into recovery - soft bricked(no os); please help!!

OnePlus X (Onyx) - Soft bricked
Boots into Fastboot mode, gets detected by PC.
No OS, No Recovery.
Problem: Recovery gets flashed successfully using adb and fastboot. But when trying to boot into recovery using commands, it says FAILED (remote:dtb not found); and when trying to boot into recovery using physical buttons, then it just stays on the OnePlus boot logo till eternity.
I tried using a flash tool as well(got from XDA), but the result is same.
Here is a look from cmd:
C:\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\platform-tools>fastboot flash recovery twrp-3.0.2-0-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 0.260s]
finished. total time: 0.728s
C:\platform-tools>fastboot boot twrp-3.0.2-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.465s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.505s
I tried flashing twrp 2.8.7.0(onyx) but still I got the same error. (remote:dtb not found). No matter what, but it just won't boot into recovery.
How it happened:
Long back, I unlocked my bootloader, installed twrp recovery and also achieved root access. Then I flashed CM13. It was working quite fine. But then OOS 3(Official) came out for OnePlus X, so I decided to download it and flash it too. It was working all fine. But then I realised that I lost my root access and my recovery was changed back to stock OnePlus recovery. After that I tried for 2 days to flash twrp back, but I continued to get that (remote:dtb not found) error. It was quite desperate; then I thought to lock the bootloader back and unlocking it back again. But the moment I used the command "fastboot oem unlock", my phone didn't ask me for a yes or no, so I tried restarting it. But it was too late, my phone got soft-bricked till then. I am trying to fix this since days, PLEASE SOMEONE HELP!!
Try to create a Thread in the One Plus X Section .

Oneplus x soft bricked; won't boot into recovery (no os) please help!

OnePlus X (Onyx) - Soft bricked
Boots into Fastboot mode, gets detected by PC.
No OS, No Recovery.
Problem: Recovery gets flashed successfully using adb and fastboot. But when trying to boot into recovery using commands, it says FAILED (remote:dtb not found); and when trying to boot into recovery using physical buttons, then it just stays on the OnePlus boot logo till eternity.
I tried using a flash tool as well(got from XDA), but the result is same.
Here is a look from cmd:
C:\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\platform-tools>fastboot flash recovery twrp-3.0.2-0-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 0.260s]
finished. total time: 0.728s
C:\platform-tools>fastboot boot twrp-3.0.2-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.465s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.505s
I tried flashing twrp 2.8.7.0(onyx) but still I got the same error. (remote:dtb not found). No matter what, but it just won't boot into recovery.
How it happened:
Long back, I unlocked my bootloader, installed twrp recovery and also achieved root access. Then I flashed CM13. It was working quite fine. But then OOS 3(Official) came out for OnePlus X, so I decided to download it and flash it too. It was working all fine. But then I realised that I lost my root access and my recovery was changed back to stock OnePlus recovery. After that I tried for 2 days to flash twrp back, but I continued to get that (remote:dtb not found) error. It was quite desperate; then I thought to lock the bootloader back and unlocking it back again. But the moment I used the command "fastboot oem unlock", my phone didn't ask me for a yes or no, so I tried restarting it. But it was too late, my phone got soft-bricked till then. I am trying to fix this since days, PLEASE SOMEONE HELP!!

How to put the recovery on my redmi note 4?

Sure its maybe asked before but followed all the treads but can't come any further.
I did all what was written but it does not work.
In CMD message cannot load twrp_mido.img all is on place on my PC (Windows 10) and the files in my phone.
tried again and again, my phone is not locked and in developer USB debug is also checked.
Superuser is installed
Even tried with flashify and starting it tells You don't have ROOT/Superuser access on your device, which is strange as i have a Root unlocked.
So maybe someone has any idea what to do next?
target reported max download size of 536870912 bytes
sending 'recovery' (29604 KB)...
OKAY [ 0.667s]
writing 'recovery'...
OKAY [ 0.168s]
finished. total time: 0.842s
ok well finally I got a ok with fastboot flash recovery twrp_mido.img but rebooting will not start the TWRP recovery but the Redmi recovery.
so whats next?
fastboot boot twrp_mido.img
Sent from my Redmi Note 4 using Tapatalk
Unetwork said:
target reported max download size of 536870912 bytes
sending 'recovery' (29604 KB)...
OKAY [ 0.667s]
writing 'recovery'...
OKAY [ 0.168s]
finished. total time: 0.842s
ok well finally I got a ok with fastboot flash recovery twrp_mido.img but rebooting will not start the TWRP recovery but the Redmi recovery.
so whats next?
Click to expand...
Click to collapse
after flashing twrp recovery.(on fastboot screen) press volume up+power butten until restart and shows mi logo.when mi logo appears release power button only(hold volume+ button) you will be able to boot twrp recovery
1, flash twrp.img with your PC.
2, DON'T reboot now. Because MIUI will recover it's original recovery.img when reboot. After flashing twrp.img, try this command in cmd:
fastboot boot yourTwrpImgName
e.g. fastboot boot twrp_mido.img
or, press power key and volume up for a long time until it shows Mi logo. And then release volume up only.
3, wait a moment.
4, reboot by twrp. It will ask you if want to prevent recovering stock recovery image. Slide this block.
5, enjoy it.
Sorry for my bad English.

can't boot into recovery

I want to install lineageOS on my Xperia Z5C (I followed these instructions: https://wiki.lineageos.org/devices/suzuran/instal) . The problem is that my phone won't boot into recovery (bootloader is unlocked), after I flashed the recovery onto the phone (I downloaded the suggested recovery file from this page https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050) .
Flashing the recovery file on the phone seems successful to me, because in the Terminal this is displayed:
sh recovery recovery_v3.2.3_22.08.2018.img
target didn't report max-download-size
sending 'recovery' (17352 KB)...
OKAY [ 0.821s]
writing 'recovery'...
OKAY [ 0.180s]
finished. total time: 1.001s
I tried to boot into recovery with all 3 methods known to me: with key combination power on + volume down; via adb with adb reboot recovery and with the quick reboot app. Every time the phone is just booting into android again.
I tried to find people reporting the same problem but I was not really successful.

Categories

Resources