Can't Flash Any ROM with TWRP - Lenovo Zuk Z2 Pro Questions & Answers

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

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.

Not able to install any Android 9.0 based ROM's

I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Did you tried another recovery? Try Batik Recovery!
Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.
Amir_espie said:
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.
Click to expand...
Click to collapse
Sure,will give it a go
An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys
Solved Magisk Error!
I've been using Pixys OS on my Redmi 4A and it works fine smoothly. I recommended to clean wipe before installing. Android Pie us amazing and I've installed stable version. Do backup before clean wipe.
For Magisk I recommended this: https://freaksterism.blogspot.com/2018/10/solved-cannot-mount-vendor-magisk.html?m=1
It worked for me. Also go through this step before any custom ROM. Do let me know the status
Anirudh15 said:
An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys
Click to expand...
Click to collapse
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.
You have two problems.
Anirudh15 said:
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
You need to flash the twrp separated vendor version by my friend Offain https://androidfilehost.com/?fid=962187416754475993
The other problem with the decryption:
You must enter in the twrp press wipe and format data. Type yes and then reboot into twrp again. After that flash the rom and gapps and you will not have the decryption problem again
Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
I had the same problem. Its because your phone is encrypted. The only solution I found is to boot the device into fastboot and using command: [fastboot format userdata] on PC. This will wipe all data off your phone so do backup. It removes encryption and now you can install any custom rom.
Decrypt ur phone first then flash, use twrp vendor
athish said:
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.
Click to expand...
Click to collapse
Format Data was the only thing that worked for me. First backup everything on your mass storage.

Boot loop after trying to downgrade EU stable 11.0.2 to EU stable 10.13.17

TL;DR - Tried to downgrade Android 10 Xiaomi EU to Android 9 Xiaomi EU, tried wiping the device (besides storage). I can get into TWRP and Fastboot, just won't boot OS.
Detailed:
I was running the latest Android 10 Xiaomi EU Stable Rom MIUI 11 (11.0.2) and wanted to downgrade because I had a few issues.
I reinstalled the last stable Android 10 Xiaomi EU Stable Rom for MIUI 10 (10.3.17) and it ran fine. I then realized that I wanted to be back on Android 9....
I went and tried to install Android 9 Xiaomi EU Stable Rom for MIUI 10 (10.3.16) and then ran into boot looping.
So then I got into TWRP and erased all data and then tried to copy over the old update file and realized I can't copy over anything even with MTP Enabled.
All the folders in the sdcard are random letters and numbers..
So now I can't send any files over and im stuck wondering how to fix this problem and then go over to Pixel Experience.
Send help! Please!
You messed up with encryptions... Just flash Chinese fastboot rom before pixel experience... and, as always, don't forget: DO NOT lock your bootloader ..
thiagodark said:
You messed up with encryptions... Just flash Chinese fastboot rom before pixel experience... and, as always, don't forget: DO NOT lock your bootloader ..
Click to expand...
Click to collapse
And I would do that by downloading which version of fastboot? Any stable one that I want to run?
Also would it be through fastboot using Mi Flash Tool or something else?
Then the pixel experience would be installed just through TWRP?
Sorry, I just don't wanna mess up.
originalwill23 said:
And I would do that by downloading which version of fastboot? Any stable one that I want to run?
Also would it be through fastboot using Mi Flash Tool or something else?
Then the pixel experience would be installed just through TWRP?
Sorry, I just don't wanna mess up.
Click to expand...
Click to collapse
As you want to flash pixel experience, you need to flash chinese fastboot rom, because pixel experience is based on Chinese firmware. So, by flashing Chinese you will be half way. Pick last stable pie version.. I believe is 10.3.16, don't remember...
Yes. You should use miflash tool, just don't forget: you need to select "clean all" and not "clean all and lock".
Boot into miui system once.
After that just flash twrp through normal fastboot command, as you already did in the past. Then flash PE in twrp...
Remember to boot in twrp just after flash it, if you boot into device it will be replaced by stock one...
thiagodark said:
As you want to flash pixel experience, you need to flash chinese fastboot rom, because pixel experience is based on Chinese firmware. So, by flashing Chinese you will be half way. Pick last stable pie version.. I believe is 10.3.16, don't remember...
Yes. You should use miflash tool, just don't forget: you need to select "clean all" and not "clean all and lock".
Boot into miui system once.
After that just flash twrp through normal fastboot command, as you already did in the past. Then flash PE in twrp...
Remember to boot in twrp just after flash it, if you boot into device it will be replaced by stock one...
Click to expand...
Click to collapse
@originalwill23
After booting into TWRP and before flashing PE, wipe cache and dalvik, then format data. Either reboot into TWRP, or unmount and mount data, then carry on with the PE flashing.
Robbo.5000 said:
@originalwill23
After booting into TWRP and before flashing PE, wipe cache and dalvik, then format data. Either reboot into TWRP, or unmount and mount data, then carry on with the PE flashing.
Click to expand...
Click to collapse
@Robbo.5000
That sounds confusing..
So after flashing the chinese fastboot and starting the phone up once to confirm its working, i boot into twrp and wipe cache+dalvik, then format all data, then restart into twrp and flash pe?
Doing that is just making sure its a clean flash and not a dirty one?
originalwill23 said:
@Robbo.5000
That sounds confusing..
So after flashing the chinese fastboot and starting the phone up once to confirm its working, i boot into twrp and wipe cache+dalvik, then format all data, then restart into twrp and flash pe?
Click to expand...
Click to collapse
You boot into MIUI once to let it finalise the installation.
Then install TWRP and immediately boot into TWRP.
When changing ROMs you should clean flash, which normally means wiping cache, dalvik and data before installing the new ROM.
In this case it's best to format data instead, otherwise you may get problems with encryption, similar to what your seeing now.
After formatting data, TWRP sometimes has a problem seeing the data partition properly, to fix this you either reboot into TWRP or go to the mount menu and unmount data, then mount it again.
After this you copy the PE ROM onto the phone and flash it.
Robbo.5000 said:
You boot into MIUI once to let it finalise the installation.
Then install TWRP and immediately boot into TWRP.
When changing ROMs you should clean flash, which normally means wiping cache, dalvik and data before installing the new ROM.
In this case it's best to format data instead, otherwise you may get problems with encryption, similar to what your seeing now.
After formatting data, TWRP sometimes has a problem seeing the data partition properly, to fix this you either reboot into TWRP or go to the mount menu and unmount data, then mount it again.
After this you copy the PE ROM onto the phone and flash it.
Click to expand...
Click to collapse
I successfully got everything up and running in PE and im loving it. Thanks!!

Bring light into the darkness of encryption

Hi togehter,
I had some problems with flashing new custom roms and ended up in a bootloop with not being able to boot to recovery. This could be solved by flashing the stock image with the xiaomi flash tool.
Before I will fu up again I would like to bring some light into the darkness.
When coming from Stock Rom:
1. Unlock Bootloader -> done successfully
2. Flashed TWRP Recovery -> done successfully but storage (data) was encrypted
3. Flashed Magisk via Recovery -> done successfully (storage still encrypted)
from here I was happy using the Stock Rom with Root.
Now I started messing things up:
Because there are a few things that bother me about the stock rom i wanted to use lineageOS/Pixel Experience. So I proceeded as following:
1. Backup my data (still have to enter key when starting twrp to decrypt the storage) -> done successfully
2. Flash LineageOS -> resulted in bootloop to TWRP
When entering twrp there was no query about the key and data where encrypted. Also the Backup was not accessible .
3. I used all in one tool to erase storage and decrypt data. -> successfully... Now i was able to place data on the internal storage again and start flashing a rom
4. Flashing LineageOS -> done successfully and able to boot into rom
Back to TWRP data was encrypted and I had to enter key.
5. Flashing remove force encryption script via twrp. -> done but now i was facing boot to black screen. TWRP was not working anymore.
Only way to get it work again, was flashing stock image.
Why is the data system always encrypted. This is rly annoying and backups don't work, because i can not encrypt them. Also, I can not put any files on the memory because it is encrypted.
I would rly like to try a custom rom, but I would also like to be able to go back to a backup. What have i done wrong?
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
SeppGoPro said:
Hi togehter,
.... What have i done wrong?
Click to expand...
Click to collapse
You need to format data (not just wipe data) in TWRP. Some people suggest before flashing a ROM and some say after, but I don't think it makes a great deal of difference either way.
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Then in TWRP wipe cache and dalvik, then format data.
Reboot into TWRP, or unmount and mount the data partition in TWRP so it correctly reads the data partition.
Copy across the ROM (and GApps if needed)
Them flash.
Boot into the ROM and you should be good.
After initial setup, if you want root, boot into TWRP and flash Magisk.
From here, if you've set a pin on the ROM, you'll be encrypted, but everything should still work normally. You should be able to access everything normally in TWRP and also perform backups. You should be able to got data across from/to a PC normally.
Turbine1991 said:
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
Click to expand...
Click to collapse
Not true in many ways.
There is need to flash no dm verity. It's one way of solving the issue, but it's not the only way. You should only do this if you know what it's for and if you know you want this.
AOSP ROMs are not unstable. I've been using them on mine for over 4 months. None are perfect and they have a few minor issues/bugs, but they are far from being considered unstable. I've never had shutdowns, reboots or FC'S.
Thanks for the replies.
Robbo.5000 said:
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Click to expand...
Click to collapse
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
SeppGoPro said:
Thanks for the replies.
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
Click to expand...
Click to collapse
Fastboot ROMs are official ROMs that are flashed through the Mi Flash Tool
, with the phone booted into fastboot mode and connected to the PC. They contains almost all partitions, including vendor and all firmware. They will be a .tgz file. They are mainly used as an almost failsafe way to recover the phone, should you mess things up. Flashing them will restore the phone to factory, so will lose TWRP, but you're guaranteed a clean starting point.
If, for example, you want to install Havoc 3, it is recommended to flash it on top of either China or India 10.4 vendor and firmware. So if you're phone is currently on global firmware, you would then need to flash, say, Chinese firmware and vendor flies, before flashing Havoc.
If you have been previously flashing other mods, such as 75Hz, screen refresh rate, for example, then you might choose to flash the official Chinese fastboot ROM, instead of just the firmware and vendor, to ensure that you've cleaned the phone of any mods, etc. In most cases you will be fine flashing firmware and vendor, though.
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Robbo.5000 said:
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Click to expand...
Click to collapse
So in this case, i can just flash this rom and there is no need of flashing a diffrent vendor or firmware.
So final question: I'm happy with the stock rom plus root. I would like to try a custom rom but I'm not willing to go through the whole installtion procedure again. Is there a way of making a backup and keeping it?
When I backup the stock rom right now, the backup will ne encrypted again...When I formate the data, all my data will be gone again ?

I keep bricking my 9t pro, what's wrong ?

Hello,
I am trying to install lineage OS on my 9t pro, but it fails every time.
I managed to unrbick my phone thanks to miflash, but now i'm totally stuck
So, i'm on miui Global 11 QFKEUXM, and i can install twrp-3.3.1-22-raphael-mauronofrio.
Then, if I try to flash a rom with it (i also tried RevengeOS), i'm going to be stuck in a bootloop, until it goes to twrp again.
When it appens, i can't access files from my computer anymore, all folders seems to have random names like "uzehfj405Cuh5635azP5IUHDPuZ".
So i have to use miflash to go back to miui. I don't know what's wrong i've spent hours trying, can someone help me ?
Thanks and have a nice day
EDIT :
Indeed i didn't format data in TWRP. I tried to, and i'm still in that boot loop unfortunatly.
But this time, file system seems to be ok because i can access internal storage from my computer
EDIT2 :
I think the problem come from GAPPS. If i format then flash lineage without GAPPS, I can boot it
But if then i try to flash them, it won't boot anymore.
I am using the "nano" package here https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Is this incorrect ?
hi,
have already format data in TWRP?
BuckyBucks said:
Hello,
I am trying to install lineage OS on my 9t pro, but it fails every time.
I managed to unrbick my phone thanks to miflash, but now i'm totally stuck
So, i'm on miui Global 11 QFKEUXM, and i can install twrp-3.3.1-22-raphael-mauronofrio.
Then, if I try to flash a rom with it (i also tried RevengeOS), i'm going to be stuck in a bootloop, until it goes to twrp again.
When it appens, i can't access files from my computer anymore, all folders seems to have random names like "uzehfj405Cuh5635azP5IUHDPuZ".
So i have to use miflash to go back to miui. I don't know what's wrong i've spent hours trying, can someone help me ?
Thanks and have a nice day
Click to expand...
Click to collapse
See bro When we buy the android the the storage is
Encrypted , when you unlock the bootloader and install TWRP it doesn't decrypt the internal storage that's why only the stick rom i.e. Miui can access the storage , here is what you need to do ..
Install TWRP then go to wipe then click on format data and type yes this will decrypt the internal storage and so that any custom rom you install can access the data ..
Make sure that you format data then reboot trwp and then connect the phone to of transfer the files and install the rom and gappa it will boot just fine
Although for some reason when i install the LOS my storage gets decrypt again I say you try the EvoX rom which doesn't require gappa just flash the rom and the firmware
Also there is some force decrypt zip file that lets you decrypt the internal storage because sometime install the firmware may encrypt your storage again so flash that DFE file you will find that in telegram grp ..
Basically you can't boot into rom and see files on computer cause your storage is encrypted and only Miui can decrypt it unless decrypted ...
Hope it help
Every time when you want to flash aosp or other custom rom you need to format data ( wiping isnt enough because of encryption) when coming from stock miui or miui eu rom.
Best way is to read instruction of rom you want to install.
My steps are when coming from stock miui:
Install twrp
Boot to twrp
Format data with yes
Reboot to twrp
Copy rom you want to install to internal storage, usually you need also rom+vendor file of latest stable miui.
Flash vendor+rom of stable miui
Wipe dalvick+ cache
Flash custom rom (los, evolutionx...)
Wipe dalvick+ cache
Flash gapps if needed
Wipe dalvick + cache
Reboot to system, set your system to your liking
Then reboot to twrp to flash magisk ( if you like to be rooted, otherwise continue to use rom as is)
Best is to read install instructions of rom you want to install
ranjan_shivam said:
See bro When we buy the android the the storage is
Encrypted , when you unlock the bootloader and install TWRP it doesn't decrypt the internal storage that's why only the stick rom i.e. Miui can access the storage , here is what you need to do ..
Install TWRP then go to wipe then click on format data and type yes this will decrypt the internal storage and so that any custom rom you install can access the data ..
Make sure that you format data then reboot trwp and then connect the phone to of transfer the files and install the rom and gappa it will boot just fine
Although for some reason when i install the LOS my storage gets decrypt again I say you try the EvoX rom which doesn't require gappa just flash the rom and the firmware
Also there is some force decrypt zip file that lets you decrypt the internal storage because sometime install the firmware may encrypt your storage again so flash that DFE file you will find that in telegram grp ..
Basically you can't boot into rom and see files on computer cause your storage is encrypted and only Miui can decrypt it unless decrypted ...
Hope it help
Click to expand...
Click to collapse
Hello, thanks for taking the time to help me. I tried again formating the data, it seems a bit better (i can acces file system from my computer), but i'm still in that boot loop :/
BuckyBucks said:
Hello, thanks for taking the time to help me. I tried again formating the data, it seems a bit better (i can acces file system from my computer), but i'm still in that boot loop :/
Click to expand...
Click to collapse
Maybe it's the vendor. What device do you have (china, global, etc.)?
ef1x said:
Every time when you want to flash aosp or other custom rom you need to format data ( wiping isnt enough because of encryption) when coming from stock miui or miui eu rom.
Best way is to read instruction of rom you want to install.
My steps are when coming from stock miui:
Install twrp
Boot to twrp
Format data with yes
Reboot to twrp
Copy rom you want to install to internal storage, usually you need also rom+vendor file of latest stable miui.
Flash vendor+rom of stable miui
Wipe dalvick+ cache
Flash custom rom (los, evolutionx...)
Wipe dalvick+ cache
Flash gapps if needed
Wipe dalvick + cache
Reboot to system, set your system to your liking
Then reboot to twrp to flash magisk ( if you like to be rooted, otherwise continue to use rom as is)
Best is to read install instructions of rom you want to install
Click to expand...
Click to collapse
djoni wallauer said:
hi,
have already format data in TWRP?
Click to expand...
Click to collapse
Thanks to both of you for helping me. As i sayed, I tried to to so and now i can see the filesystem from my computer, but i'm still stuck in the bootloop
Isley_ said:
Maybe it's the vendor. What device do you have (china, global, etc.)?
Click to expand...
Click to collapse
I think it's a global one, but now i have doubts... Is there a way to be sure ?
In the MIUI i managed to flash with miflash, it's sayed MIUI GLOBAL
vladsendrix said:
if it s a mi9t pro its probbably the global version, to make sure try downloading the firmware and vendor from here https://downloads.akhilnarang.me/MIUI/raphael/ . try downloading the global and indian version and try both since you dont know whihch model you have. also dont forget to format before trying anything. hope i helped
Click to expand...
Click to collapse
I'm a bit affraid to flash indian version, it's says to not cross flash ^^
I’d flash MIUI.eu before lineage, let it boot and then do the whole process to install lineage. Yo don’t have nothing to lose.
vladsendrix said:
well i d rrecommen you put your device in fastboot, go to aXiaomiADBFastbootTools and it ll show you your model number or use TOOLSALLINONE. Search ythese on xda and youll find the links and that will definetly show you your model number
Click to expand...
Click to collapse
What fastboot commands should I use to get the model number ? I tried fastboot oem get-psid but it didnt work
When I boot MIUI, in the settings its "MIUI GLOBAL QFKEUXM". So it's correct isn't it ?
vladsendrix said:
well i d rrecommen you put your device in fastboot, go to aXiaomiADBFastbootTools and it ll show you your model number or use TOOLSALLINONE. Search ythese on xda and youll find the links and that will definetly show you your model number
Click to expand...
Click to collapse
I think the problem come from GAPPS. If i format then flash lineage without GAPPS, I can boot it
But if then i try to flash them, it won't boot anymore.
I am using the "nano" package here https://sourceforge.net/projects/ope...beta/20191114/
Is this incorrect ?

Categories

Resources