I cant install any custom rom on my P2 - Lenovo P2 Questions & Answers

I cant install any custom rom on my P2 - Lenovo P2 Questions & Answers

I unlocked the boot loader & installed TWRP
I tried to install official Lienage 7.1.2 after flashing & wipe cache then restarting screen went black with long vibration & blue notification led
the other 8.1 roms the TWRP Stopes when flashing after saying flashing img
may anyone tell me the problem

Arafa1994 said:
I unlocked the boot loader & installed TWRP
I tried to install official Lienage 7.1.2 after flashing & wipe cache then restarting screen went black with long vibration & blue notification led
the other 8.1 roms the TWRP Stopes when flashing after saying flashing img
may anyone tell me the problem
Click to expand...
Click to collapse
Flash twrp via fastboot.
Boot to twrp via
Fastboot boot twrp.img
Replace "twrp" with the file name of your twrp.
Once twrp booted, go into reboot menu. And reboot to recovery again. That will make your phone boot again into twrp, but this time with more rights.
Go into wipe. Advanced wipe
Change data partition file system to ext4.
Reboot again into twrp via the reboot menu ,just like before.
Now go into wipe again, and format system,data,dalvik and cache.
Flash your rom.
Flash gapps (if not otherwise stated by ROM thread)
Flash Magisk (optional, if you want root)
Wipe dalvik and cache.
Reboot. And enjoy
Sent from my Lenovo P2a42 using XDA Labs

sm00th4f3 said:
Flash twrp via fastboot.
Boot to twrp via
Fastboot boot twrp.img
Replace "twrp" with the file name of your twrp.
Once twrp booted, go into reboot menu. And reboot to recovery again. That will make your phone boot again into twrp, but this time with more rights.
Go into wipe. Advanced wipe
Change data partition file system to ext4.
Reboot again into twrp via the reboot menu ,just like before.
Now go into wipe again, and format system,data,dalvik and cache.
Flash your rom.
Flash gapps (if not otherwise stated by ROM thread)
Flash Magisk (optional, if you want root)
Wipe dalvik and cache.
Reboot. And enjoy
Click to expand...
Click to collapse
Thx alot
But I have one more question
Should the bootloader to be marshmallow or nougat?

Arafa1994 said:
Thx alot
But I have one more question
Should the bootloader to be marshmallow or nougat?
Click to expand...
Click to collapse
What do you mean The bootloader is the bootloader.

Danoz88 said:
What do you mean The bootloader is the bootloader.
Click to expand...
Click to collapse
In my moto Z Play some roms needs Nougat bootloader like xperince

So Iam asking If some roms needs nougat bootloader in Lenovo P2

Arafa1994 said:
So Iam asking If some roms needs nougat bootloader in Lenovo P2
Click to expand...
Click to collapse
We only have one bootloader.
We have different firmwares though like nougat and marshmallow.
You will need Firmwares S244 for nougat ROMs.
That firmware must be flashed through ota. Stockrom-feature. Simply using twrp does not count as doing otas.
Basic starter things: Have Firmware S244 or S251 installed through stock ota feature.
Then use my earlier stated instructions.

Thx alot it worked & no problems

Related

Update from 3.2.7 to 4.1

Hey guys. I am still on marshmallow on my op3. I am rooted and have twrp recovery. My question is what firmware/modem do I need to flash before I update to latest Nougat update and if my steps below are correct.
I would prefer not to do a clean install.
My steps would be:
Download full rom
Flash any firmware if required - this is what I need to know
Flash Magisk as I need root
Profit?

cd69 said:
Hey guys. I am still on marshmallow on my op3. I am rooted and have twrp recovery. My question is what firmware/modem do I need to flash before I update to latest Nougat update and if my steps below are correct.
I would prefer not to do a clean install.
My steps would be:
Download full rom
Flash any firmware if required - this is what I need to know
Flash Magisk as I need root
Profit?
Click to expand...
Click to collapse
this is stock rom, you don't need to flash any firmware...
if you're coming from MM, i would recommend sideloading the rom, wipe everything, then go back to stock recovery then sideload then before 1st boot fastboot TWRP again, then reboot to TWRP and flash Magisk...Profit.
if you want to flash from TWRP without going through this (which i don't recommend), make sure in TWRP to format data as f2fs, wipe everything then flash the rom, and then form TWRP flash TWRP again, then reboot to recovery (not system), then flash Magisk.

theduke7 said:
this is stock rom, you don't need to flash any firmware...
if you're coming from MM, i would recommend sideloading the rom, wipe everything, then go back to stock recovery then sideload then before 1st boot fastboot TWRP again, then reboot to TWRP and flash Magisk...Profit.
if you want to flash from TWRP without going through this (which i don't recommend), make sure in TWRP to format data as f2fs, wipe everything then flash the rom, and then form TWRP flash TWRP again, then reboot to recovery (not system), then flash Magisk.
Click to expand...
Click to collapse
Thanks a ton for replying. Another question for you. I get the OTA notification. I could just let that run and flash twrp after the installation right.

cd69 said:
Thanks a ton for replying. Another question for you. I get the OTA notification. I could just let that run and flash twrp after the installation right.
Click to expand...
Click to collapse
if you're already rooted it wont install..and you can't flash the small ota file from TWRP, you have to flash the Full rom (1.4 GB)...
how you download is up to you, but why download from the update when there's many links available around !

Thanks for all the help. I flashed the new update successfully.

cd69 said:
Thanks for all the help. I flashed the new update successfully.
Click to expand...
Click to collapse
what steps did you follow ? did you have to wipe internal memory fully ?

netcitizen said:
what steps did you follow ? did you have to wipe internal memory fully ?
Click to expand...
Click to collapse
I just flashed the full Rom with Magisk. Wiped dalvick cache and nothing else. So far so goos.

cd69 said:
I just flashed the full Rom with Magisk. Wiped dalvick cache and nothing else. So far so goos.
Click to expand...
Click to collapse
Oh ok. I just flashed full rom via twrp after wiping cache and Dalvik cache.it updated fine. I wasn't sure of magisk.

The terrible fate of refurbished N5X

Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated ! ?

Atok_fr said:
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated !
Click to expand...
Click to collapse
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Thanks mate, it worked !

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.

negusp said:
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
Click to expand...
Click to collapse
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.

CazeW said:
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
Click to expand...
Click to collapse
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?

negusp said:
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
Click to expand...
Click to collapse
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.

CazeW said:
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
Click to expand...
Click to collapse
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.

negusp said:
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
Click to expand...
Click to collapse
I don't use Netflix so can't say if that works but Play Movies worked on Nougat.

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader

sigibian said:
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
Click to expand...
Click to collapse
I haven't tried this with a custom ROM but I would try it like this.
- Unlock bootloader from fastboot
- Flash TWRP from fastboot
- Select boot to recovery from the fastboot menu
- Do a factory reset
- Wipe system, cache, and dalvik cache
- Flash ROM, flash Gapps
- Flash Magisk
- Reboot

[SOLVED] HELP! i'm stuck in a boot loop! :(

my flashing history:
i was on audax (oos based nougat rom) with blu spark kernel before, then went to official ob1, then back to audax, then back to stock oos nougat and now i flashed audax and after clean flashing it, it just wont boot up.
when i try to boot up i see the 1+ logo but then it reboots to recovery. i also tried flashing stock nougat again and also flashed stock kernel manually but it also doesnt work.
i always do:
1. wipe system/dalvic/cache/data
2. install ROM
3. wipe dalvik/cache
4. flash magisk (also tried without flashing magisk)
5. reboot
i've been looking on the interwebs all day but nothing worked.. help pls :/
EDIT: problem was blu spark twrp. Maybe installing Oreo ****ed it up. I flashed codeworkx newest twrp universal build and now Im able to boot again!! Btw: I also found that magisk 15.0 prohibits a proper boot up and results in a boot loop. version 15.2, however, does the trick!

when it auto reboot to recovery, formate data

When s**t happens, it is wise to start everything from scratch:
-boot in fastboot mode and flash stock recovery with "fastboot flash recovery recovery.img" (rename recovery.img with your recovery filename), then reboot recovery and select english, advanced, adb sideload;
-flash stock OS with "adb sideload rom.zip" (rename rom.zip with your Oxygen OS filename).
Procedure will require some minute because of the large file size. Remember to save all your data on internal storage first!
I advice you to flash original recovery because often sideloading in TWRP leads to some error.
Your phone will boot again... after that you may reflash TWRP, Magisk etc

I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.

redatak said:
I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.
Click to expand...
Click to collapse
He says that it occurs even without Magisk... I had a similar trouble once, and the only way to solve it was the procedure I wrote above...

I dont know if you can boot it w/o root

redatak said:
I dont know if you can boot it w/o root
Click to expand...
Click to collapse
Why not? Stock OS is not rooted.

jonsat said:
Why not? Stock OS is not rooted.
Click to expand...
Click to collapse
He said audrax not stock oos

SOLVED! TWRP was the only variable left that I didn't think of. See initial post for solution. thx for help!

Oreo update for rooted OnePlus 5t

Pls help me updating my 5t to oreo.i am currently on version 4.7.6 with twrp recovery nd super su root.
After updating to Oreo I again want to root my phone
Pls share links to download compatibile ROM, recovery nd super su.zip

But you already have the OREO OOS ROM installed, why not use it? Flash the Oreo recovery from codeworkx through fastboot, make sure to follow the instructions so it sticks and then flash Magisk or any root solution of your choice. It's not hard if you do some searching.

Check in ROMs' threads and come back what your interested ROM is.

What I did was flash the ota to update me to Oreo. Then had to reflash Magisk and kernel.

jcroy2828 said:
What I did was flash the ota to update me to Oreo. Then had to reflash Magisk and kernel.
Click to expand...
Click to collapse
Kernel?

jcroy2828 said:
What I did was flash the ota to update me to Oreo. Then had to reflash Magisk and kernel.
Click to expand...
Click to collapse
Pls give me link to download magisk nd what does kernel mean?

mannulko said:
Kernel?
Click to expand...
Click to collapse
Il check when I get home. I just used Magisk 15.3 from the Magisk xda thread

jcroy2828 said:
Il check when I get home. I just used Magisk 15.3 from the Magisk xda thread
Click to expand...
Click to collapse
I mean pls tell me step by step what should I do.currently I am on 4.7.6 wth twrp recovery nd rooted.i want to update my phone to Oreo nd root again

mannulko said:
I mean pls tell me step by step what should I do.currently I am on 4.7.6 wth twrp recovery nd rooted.i want to update my phone to Oreo nd root again
Click to expand...
Click to collapse
If you have already installed a custom recovery and rooted your phone then you should be able to follow these instructions.
I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP or Codeworkx TWRP (I personally used Blu_Spark but both should work).
3. Download Magisk 15.3 (I havent used SuperSu in a while so I can't confirm how well it works on Oreo but in my opinion Magisk is a better root method and it works in this version of android).
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2, congrats, you're on the latest OxygenOS version for this phone).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
NOTE: Since this is a big version update from Nougat, it's always recommended to do a clean flash although not necessary in most cases unless there are issues like big battery drain or when apps or the OS are not working properly. Also, if you are coming from a custom ROM and not the official OxygenOS, then you should definitely do a clean installation (even if said custom ROM is based on OxygenOS).

HueleSnaiL said:
If you have already installed a custom recovery and rooted your phone then you should be able to follow these instructions.
I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP or Codeworkx TWRP (I personally used Blu_Spark but both should work).
3. Download Magisk 15.3 (I havent used SuperSu in a while so I can't confirm how well it works on Oreo but in my opinion Magisk is a better root method and it works in this version of android).
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2, congrats, you're on the latest OxygenOS version for this phone).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
NOTE: Since this is a big version update from Nougat, it's always recommended to do a clean flash although not necessary in most cases unless there are issues like big battery drain or when apps or the OS are not working properly. Also, if you are coming from a custom ROM and not the official OxygenOS, then you should definitely do a clean installation (even if said custom ROM is based on OxygenOS).
Click to expand...
Click to collapse
What is clean flash?

mannulko said:
What is clean flash?
Click to expand...
Click to collapse
Wiping data and system partition which means you're wiping the entire OS and installing the new version on a clean partition. Think of it as formatting a hard drive and installing an OS instead of just upgrading your existing OS.
You obviously lose all apps installed,and it would be like when you first turned on your phone, however as long as you don't wipe internal storage, all your photos,music,etc are not wiped so you can use apps like titanium backup to restore all apps and data .
This method is recommended when switching from different custom ROM's and when upgrading from major version updates, like for example, going to Android 8 from Andorid 7.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
rockuman_ex said:
Will the official TWRP work with no problem?
I'm already on 4.7.6, offical twrp-3.2.1-1-dumpling and magisk 15.3, and don't really want to flash another recovery.
Click to expand...
Click to collapse
I used that same version of TWRP back during the Oreo beta and it didn't work so I had to switch to blu_spark.

HueleSnaiL said:
Wiping data and system partition which means you're wiping the entire OS and installing the new version on a clean partition. Think of it as formatting a hard drive and installing an OS instead of just upgrading your existing OS.
You obviously lose all apps installed,and it would be like when you first turned on your phone, however as long as you don't wipe internal storage, all your photos,music,etc are not wiped so you can use apps like titanium backup to restore all apps and data .
This method is recommended when switching from different custom ROM's and when upgrading from major version updates, like for example, going to Android 8 from Andorid 7.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
I used that same version of TWRP back during the Oreo beta and it didn't work so I had to switch to blu_spark.
Click to expand...
Click to collapse
So i took the jump and flashed blu spark and the 5.0.3 full rom.
Yes i lost the recovery to stock, but that's ok. Just want to get OTA in the future and I don't need root at the moment.
So this is what i did (coming from 4.7.6, official twrp, magisk 15.3)
Make sure you have all the necessary files (eg. blu spark img file and the full ota file on your phone
boot the fastboot and "fastboot flash recovery twrp-3.2.1-x_blu_spark_v8.68-op5_op5t.img"
On the phone, choose and go to recovery
(now i'm on blu spark) Wipe Cache and Dalvik cache (i did this 2 times just to make sure)
Choose install and select the full ota rom file
Let it run and install the rom (took less than 5 mins)
Wipe Cache and Dalvik cache again (again, i wiped 2 times just to make sure)
Reboot
Make take a while (less than 10mins) for android to start and do the upgrade etc
Done
So far so good, i don't see any immediate problem. I will play a bit more and will post if I encounter any problem :good:

I have updated to 5.0.3 through system update app. where it downloaded full ota file and installed.Now I want to install twrp nd root my phone so pls confirm my steps
1 boot into fastboot mode and flash bluespark recovery
2 wipe delvik/cache from twrp recovery
3 flash magisk zip
4 again wipe delvik cache
5 reboot
are above steps correct?

Hello,
i have latest (8.69) twrp blue_spark and i try to flash latest oxygen os
1)Oreo 5.0.3: OnePlus5TOxygen_43_OTA_029_all_1802022353_460d.zip
2)magisk 15.3
3)wipe davlik/cache
reboot system and i get stucked at bootanimation of OxygenOS.
Any help guys please ?
Thanks!
Redownloaded Magisk 15.3 and ok

BrollyG4 said:
Hello,
i have latest (8.69) twrp blue_spark and i try to flash latest oxygen os
1)Oreo 5.0.3: OnePlus5TOxygen_43_OTA_029_all_1802022353_460d.zip
2)magisk 15.3
3)wipe davlik/cache
reboot system and i get stucked at bootanimation of OxygenOS.
Any help guys please ?
Thanks!
Redownloaded Magisk 15.3 and ok
Click to expand...
Click to collapse
I'm having the same problem, I think it's version (8.69) twrp blue_spark. I'll try with version 8.68

HELP! Phone only boots into recovery after fresh install

I have now tried to install the latest RR and Omnirom builds and the problem remains the same.
I've been very particular about wiping data before the installs.
Here is what I have done,
Performed data wipe by typing "yes" when requested. Used advance wipe to wipe everything.
Installed Rom, Stock Gapps and Magisk zip files.
Wiped Cache.
Reboot
The phone will not boot and only returns to recovery.
Can anyone help?

Here is my TWRP log if this helps - https://pastebin.com/ghpXkt3t

Not sure if this is relevant, but every time I try to flash a ROM it always fails on the first attempts and needs a second try to succeed.

TylerDurdenK said:
I have now tried to install the latest RR and Omnirom builds and the problem remains the same.
I've been very particular about wiping data before the installs.
Here is what I have done,
Performed data wipe by typing "yes" when requested. Used advance wipe to wipe everything.
Installed Rom, Stock Gapps and Magisk zip files.
Wiped Cache.
Reboot
The phone will not boot and only returns to recovery.
Can anyone help?
Click to expand...
Click to collapse
If you only get to the mi logo and not the ROM boot screen then format data "yes 3-4 times in a row.
If that doesn't work then wipe the system and data and retry

I was only getting the Mi logo, so I did the format data 4 times in a row and rebooted.
I then saw the Omnirom logo for the first time!
unfortunately 2 seconds later I'm back in TWRP.

I have now tried for the 5th time to perform a fresh install.
Formatting data multiple times, wiping system and data multiple times.
The result is the same.
I see a flicker of the Omnirom logo and I get booted back into recovery.

TylerDurdenK said:
I see a flicker of the Omnirom logo and I get booted back into recovery.
Click to expand...
Click to collapse
Please try this:
1. Wipe: Dalvik / Art Cache; System; Data; Cache;
2. Go back to main TWRP screen and install the rom, install Google Apps, install "addonsu-15.1-arm64-signed.zip" (in case of Lineage) or the latest Magisk (in case of other rom)
3. Wipe Cache
4. Reboot
If this doesn't work and the device restarts in twrp, then pls download the twrp flashable Xiaomi rom from here: http://en.miui.com/download-334.html
1. Wipe: Dalvik / Art Cache; System; Data; Cache
2. Go back to main twrp screen and install the Xiaomi rom. Do not reboot.
3. Go back to main twrp screen and Wipe: Dalvik / Art Cache; System; Data; Cache
4. Go back to main twrp screen and install the rom (Lineage or OMNI or RR), install Google Apps, install "addonsu-15.1-arm64-signed.zip" (in case of Lineage) or the latest Magisk (in case of other rom)
5. Wipe Cache
6. Reboot
I had the same problem and this method worked for me, maybe it will work for you too. :fingers-crossed:
If it doesn't then maybe you have to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (bootloader might relock), flash twrp and then flash new custom rom.

No idea what happened but I have the same issue atm.
I was running a recent Omnirom for a few weeks. System got unstable, so decided to flash the newest version. Got me stuck in a bootloop. I tried everything, short of relocking and unlocking the bootloader.
- Full wipe, including storage
- Reflash Global Dev through TWRP.
- Flash stock Global Dev over flashboot
- Flash Omni, wipe, flash omni again.
All the same. Global Dev runs, all AOSP roms just go into bootloop. No idea what went wrong, I've flashed tens of custom roms over the past months without issues.

Firipu said:
No idea what happened but I have the same issue
All the same. Global Dev runs, all AOSP roms just go into bootloop. No idea what went wrong, I've flashed tens of custom roms over the past months without issues.
Click to expand...
Click to collapse
Then maybe the right solution to get out of bootloops would be to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (as bootloader will relock), flash twrp, do a full wipe and then flash new custom rom.

senerex said:
Then maybe the right solution to get out of bootloops would be to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (as bootloader will relock), flash twrp, do a full wipe and then flash new custom rom.
Click to expand...
Click to collapse
I have reflashed the original Xiaomi ROM (running it atm ) using the official Xiaomi Flash Tool.
I just did not relock my bootloader doing that (there's an option to leave it unlocked). Will relocking and then unlocking the bootloader really make a difference?

Firipu said:
I have reflashed the original Xiaomi ROM (running it atm ) using the official Xiaomi Flash Tool.
I just did not relock my bootloader doing that (there's an option to leave it unlocked). Will relocking and then unlocking the bootloader really make a difference?
Click to expand...
Click to collapse
Not really. You ev. save yourself a waiting time of 72h....

Not sure what happened. I set up MIUI completely. Then, getting frustrated after using it for 10 minutes, decided to try one more time. Same thing.
1) Fastboot flash TWRP.
2) Wipe
3) Flash Rom
4) Flash GAPPS
Worked this time. No idea what went wrong the first 4 times. Only difference is that I went through the trouble to set up the entire phone this last time before trying again.
Anyhoo, so if anyone has the same issue. Set up phone in MIUI, only then wipe/flash

I got mine working by not installing Magisk. I just flashed Omnirom and GApps and it worked.
After setting up my phone I have since rebooted into recovery and installed Magisk and it works.

Can't system boot after install TWRP, Lazy Magisk on MIX M2S
Hello,
I have this problem, the phone does not boot after TWRP, Lazyflasher and Magisk being installed all fine.
I have re-installed the official ROM on my Xiaomi MI MIX 2S, then TWRP is fine too, then Lazy and Magisk fine.
When I reboot, it is stocked on MI logo whatever I do.
I have tried most of the advise posted but still stocked.
I restarted from scratch, installing again the official ROM, then fastboot flash recovery twrp, then lazy and Magisk, but still stocked on MI.
Thanks a lot in advance

Did you wipe system by any chance.. If you did you need to flash miui again with fastboot.. Or boot into fastboot and type this command 'fastboot format userdata' and press enter. You are facing this issue because of encryption

goxthak0 said:
Did you wipe system by any chance.. If you did you need to flash miui again with fastboot.. Or boot into fastboot and type this command 'fastboot format userdata' and press enter. You are facing this issue because of encryption
Click to expand...
Click to collapse
Gratitude for your reply. What do you mean by "wipe system". I installed the rom and then TWRP etc...
I flashed the ROM again and went into bootloader
I typed "fastboot format userdata" and the system replied:
"/usr/local/bin/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Can you advise.
Thanks a LOT

Did you use the correct rom ? Mi mix 2 or mi mix 2s?

fotocreaman said:
Did you use the correct rom ? Mi mix 2 or mi mix 2s?
Click to expand...
Click to collapse
I used MI MIX 2D:
As in en.miui web site
https://en.miui.com/download-343.html
Author: MIUI Official TeamVersion: V10.0.9.0.PDGMIFH (MIUI10) Size: 1.7G
My mobile is:
MI MIX 2S, Android 9PKQ1
MIUI Global 10.0
Thanks a lot for your advise as always stock, despite different attempts

Did you try to flash using mi tools?

fotocreaman said:
Did you try to flash using mi tools?
Click to expand...
Click to collapse
NO, I followed the usual process with ADB tools.
However, I have no boot "stuck at MI logo (bootloop)" problem when I flash the ROM.
It happens only when use TWRP and flash Magisk and Lazy.
Then, when I restart it got stuck at MI Logo.
Do you suggest I try to flash with MI logo (I don't have a PC though).
If so, should I just flash the ROM and then, what about TWRP, should I use MI flash or ADB?
I just want to make sure that the problem is with the ROM instal?
Thanks a LOT

Develop Bugs

welcome