How to properly flash p8lite rom(Che2-TL00) - Honor 4x Questions & Answers

I need to flash RROS, but before that I need to flash p8lite rom first, I encountered an "unknow command" error during the flashing process, and after flashing rros, the data partition capacity was reduced by 700MB.:crying:

I use Google Translate to translate Chinese into English. I don't know if this is wrong.

Related

Cant return to MIUI from LineageOS

Wipe everything
Install global developer zip file
When reboot, twrp says no OS installed
Help pls
if the recovery method of flashing the full rom fails, then you have no other recourse except to flash via fastboot method.
take note of this "Please wipe all data in Recovery mode if you want to update to a discontinuous ROM version, or downgrade to an older ROM version using MIUI full ROM pack. If you upgrade from MIUI Stable ROM based on Android M to MIUI Developer ROM based on Android N, please flash it via Fastboot update. Recovery update might cause upgrade failure."
http://en.miui.com/a-232.html
http://en.miui.com/a-234.html
lucasho2312 said:
Wipe everything
Install global developer zip file
When reboot, twrp says no OS installed
Help pls
Click to expand...
Click to collapse
Did you just tried rebooting to system after flashing? I also got that error "no OS installed" in TWRP so many times, but rebooting to system with no problems at all.
nnth said:
Did you just tried rebooting to system after flashing? I also got that error "no OS installed" in TWRP so many times, but rebooting to system with no problems at all.
Click to expand...
Click to collapse
Unmounted system before flashing ROM .
in my opinion why just not use rom from xioami.eu because you have custom recovery .
p.chandra284 said:
Unmounted system before flashing ROM .
Click to expand...
Click to collapse
Dont unmount system flash zip and after flash use hardware buttons to reeboot
U need to format data before installing miui
lucasho2312 said:
Wipe everything
Install global developer zip file
When reboot, twrp says no OS installed
Help pls
Click to expand...
Click to collapse
The reason is, that you can't flash OFFICIAL Chinese (Developer/Stadle) Rom with cusom recovery (TWRP). But you can flash anything esle. Like Lineage OS. If you want to use MIUI Rom, you have to flast a Xiaomi.eu ( developer or stable) rom. NOT OFFICIIAL CHINESE !!! If you prefer Official Chinese Global rom, you must download a FASTBOOT rom (not recovery) , and flash it in fastboot mode, with MiFlash.
instead of beating around the bush, why not follow the official procedure of flashing an official miui rom
if you are coming from a custom rom, as specified herein?:
http://en.miui.com/a-234.html
When can we expect official RR for mi max 2?
It was already available for redmi note 4 which is having the same processor.
You have to wait for custom Rom until miui release the kernel source which is must have to develop a custom one. please be patience...
If you flash rom with out error, Even no os installed warning, you can boot into system without problem.

Can't Flash Any ROM with TWRP

Hi guys.
I had been on RR Oreo for quite a while and as I wasn't happy with battery endurance, I decided to go back to RR Nougat.
Initially, I just downloaded the zip and flashed it on the latest official TWRP 3.2.1.
The phone just bricked.
I then proceeded to flash Stock ZUI Nougat 3.1 with QFIL, flashed TWRP again and tried to flash RR Nougat. No way. Apparently /system was not properly mounting and I just got stuck on "flashing system" steps.
I tried to format data and system partitions, change them to ext2, ext3, f2fs and back on ext4, repaired the filesystem, wiped all /system, /data, /cache and /dalvik and nothing happened.
Actually, after rebooting to recovery, I noticed that I always got the "swipe for modifications menu" and /system could not be mounted. I could only apparently mount system after changing the partition type back and forth. However, it didn't seem to be really mounted in fact as everytime I tried to flash a ROM (being it RR, AEX or even custom-made stock ones), they got stuck and sometimes even bricked my phone again.
I also tried to flash Stock Marshmallow by QFIL to no avail...
This is a very strange issue...
After more than 10 years of flashing custom firmware, this absolutely never happened to me.
Can you be so kind and share some ideas on how to solve this?
Many thanks
Update: my phone is got now hard bricked while using stock marshmallow rom.
Please, can you still help me with the issue I shared above?
I will try to revive my device in the meanwhile.
Update 2: Phone is back on stock after I did a homemade deep flash cable and flashed stock nougat with qfil. Still looking for a way to flash custom roms
Patoilo said:
Update 2: Phone is back on stock after I did a homemade deep flash cable and flashed stock nougat with qfil. Still looking for a way to flash custom roms
Click to expand...
Click to collapse
Try with twrp 3.2.1-0 . Go to twrp /wipe /format dataand type "yes" . It will erase all your data and internal memory . If still get brick you should install zui 1.9.104 by qfil and start all from beginning .
mar.ur said:
Try with twrp 3.2.1-0 . Go to twrp /wipe /format dataand type "yes" . It will erase all your data and internal memory . If still get brick you should install zui 1.9.104 by qfil and start all from beginning .
Click to expand...
Click to collapse
Thanks a lot for the tip, my friend.
I did the formatting of data that you refer, no luck.
Anyway, I would like to try to flash zui 1.9 as I tried so far with 2.1, 2.3, 3.1 and 3.5.
However, all the links I found so far to download the 1.9 are down. Can you let me know where I can download 1.9?
Many thanks
Check here
https://zukfans.eu/community/forums/official-z2pro-zui-rom-releases.13/
Watch out -Zui 1.9.104 will relock bootloader . After that install Zui 3.1.194 bu qfil , then unlock bootloader , install twrp 3.1.1-0 and install non-treble custom rom ( RR 5.8.4 for example )
mar.ur said:
Check here
https://zukfans.eu/community/forums/official-z2pro-zui-rom-releases.13/
Watch out -Zui 1.9.104 will relock bootloader . After that install Zui 3.1.194 bu qfil , then unlock bootloader , install twrp 3.1.1-0 and install non-treble custom rom ( RR 5.8.4 for example )
Click to expand...
Click to collapse
Solved! Dziekuje

OTA update problems

So 7-8 weeks ago i played around a little with my mi a2 trying to flash some roms. I was completely new Xiaomi's slot a/b system. I oem unlocked. I accidentally wrote over twrp on both slots and had some problem. I downloaded some image files (i think boot and system) for the V9.6.15.0.ODIMIFE and flashed them. Now run my mi a2 on that version. *Fastforward to now* Now the problem is that I can't install the OTA updates (google drive images). Is it possible to getting the OTA updates again and how would I do that if it works?
Screenshots of error messages
https://drive.google.com/drive/folders/1ITVTRPX2g3iiIqoC9VOsXoNPAG-fMfkZ?usp=sharing
Let me know if you need more information to identify the problem
Help would be appreciated
EDIT: Currently i have twrp/rom on slots a/b
What you need to do is download a dump and flash all original files back to your phone, including boot_a, boot_b, system_a, system_b, and so forth.
You don't need to relock the bootloader.
Tipically the dumps have a "flash all except user data" script that does it for you.
This will remove Magisk/TWRP/whatever you've installed

Please i need fix this

After unlocking the bootloader, I installed AEX 9, then I decided to flash the stock rom 8.1 and it worked ... But there is a problem, I have the bootloader unlocked and I receive OTA updates ... but now I want to install TWRP and it doesn't work, it says "recovery.img is not signed", I tried to flash another stock of rom and the same problem, I can't ... it says "boot.img is not signed"
How I fix this? I just want flash TWRP for Magisk... any solution?
PD: My English is not good for all... sorry
Use the correct version of twrp and disregard image not signed message

(flashing / booting) Problems with all roms

Hi,
since many days I have a new Mi8.
The device is a chineese model, and because it was delivered with unlocked bootloader and a shop ROM, i want to use the latest Xiaomi.eu stable rom.
After flashing the TWRP, i cleared all (System, Data, Cache, internal storage) and installes the latest xiaomi.eu ROM.
Unfortunately the ROM was notstartet. Later i readed, that the xiaomi.eu ROM needs the system partition, so i tried to install some different ROMs.
All tested roms failed to install (device missmatch), so i tried to use different recoveries and at least i updated the vendor Image to MI8Global_V10.3.5.0.PEAMIXM.
After this, some Roms are able to install, mut the ROMs wont boot.
After a clean install of the xiomi global fastboot image, the phone is running, but i still have problems to install custom ROMs or the stable Xiaomi.eu ROM.
The fastboot ROM installation with mi flash tools ends with an error (Not catch checkpoint (\fastboot -s .*lock) Flash is not done (I choosed the option clean all, not the lock function)
cDroid Rom is working, but with this ROM i cant use google pay.
cDroid with update to xiaomi.eu weekly is also working, but also without google pay.
Xiaomi.eu stable - bootloops
Do you have any ideas why i cant use all ROMs?
Should i choose a chineesevendor image or something else?
I also heared, that it could be, that the device bricks, when i try to re-lock the bootloader, is this an option?
Which ROM should work fith functional google pay ?
Thanks in advance
The problem seems to be solved,
i have to flash "Disable_Dm-Verity_ForceEncrypt" after the flashing of every ROM, then I have no bootloops / boot Problems.
Now i only have the problem with google pay...
I couldn't also get Miui Eu bootable on my mi8 last time. I didn't realize what you had mentioned Disable_Dm-Verity_ForceEncrypt. But I could manage to get MiRoom Miui workable and it seems ok for now.
stevedat said:
I couldn't also get Miui Eu bootable on my mi8 last time. I didn't realize what you had mentioned Disable_Dm-Verity_ForceEncrypt. But I could manage to get MiRoom Miui workable and it seems ok for now.
Click to expand...
Click to collapse
DM verity zip removes the 'DM Verity' check that looks for modifications to the boot partitions (D-device M-mapper). You cannot boot with modifications (like root) without disabling the verity check. Also, if you are on a stock ROM, your custom recovery image file will be overwritten with stock upon reboot if you don't disable DM Verity. Hope this helps you understand more.
Found it on this topic.
I´m still looking for a ROM with google pay support, but iu think with unlocked bootloader and without root therre is no chance...

Categories

Resources