Related
There are unfortunately no ROMs specifically for this device yet, but has anyone tried to use a generic treble ROM on this device?
Thanks in advance
I have tried several treble ROMs, the majority don't even boot. Lineage os worked but was buggy. The more stable one was Havoc, if I remember correctly.
I was interested in the Q developer ROM but it didn't work. I'm back to the stock pie Rom, since there is no Netflix HD support on those treble roms.
gtaadicto92 said:
I have tried several treble ROMs, the majority don't even boot. Lineage os worked but was buggy. The more stable one was Havoc, if I remember correctly.
I was interested in the Q developer ROM but it didn't work. I'm back to the stock pie Rom, since there is no Netflix HD support on those treble roms.
Click to expand...
Click to collapse
Hi Mate, I've been trying to flash a working GSI rom but had no success so far(have an SM-T830). In the past have built ROMs for Tab A 10.1 and flashed them many times with TWRP and Odin so I just cannot understand am I retarded to not being able to flash a working one or what? Have managed to put TWRP 3.3.0.0 and TWRP 3.3.0.1 on the device. Have tried my own arm64_aonly image first. Then an original AOSP one, then a Lineage OS version, at the moment I am just downloading Havoc. The result (apart from the havoc) was always the same. The flashing went through successfully and when I rebooted into system the very fist image came up and boot looped from there. I am always able to go back to TWRP and try another image or through odin can restore the factory image but none of the GSI images seem to be working. So, here is my question. As you managed to get a Lineage and Havoc working, can you tell by looking at it what am I doing wrong please:
1.: OEM unlock
2.: TWRP install with odin
3.: Boot straight into TWRP to prevent being overwritten
4.: TWRP: format data
5.: Flash system image (arm64_aonly)
From here have tried so many things like,
- booting straight into system
- booting back to recovery
- flashing the force_decryptor or how the hell is that called
- formatted data again as the decryptor suggests
The result was always the same, boot looped from the very first image. It seems like that the image is not getting flashed and even if TWRP says was flashed right it is just not there. I'm literaly pulling my hair as it was so easy and straight forward with the Tab A 10.1, but with this ….. thanks for your answer in advance
anyone have any luck with treble GSIs? i can only get arrowos to boot and even then i cant install gapps.
droidbot1337 said:
anyone have any luck with treble GSIs? i can only get arrowos to boot and even then i cant install gapps.
Click to expand...
Click to collapse
I used AOSP 9.0 and LineageOS 16 with OpenGApps Pico and both work but are very buggy.
After hours of trying to figure this out myself i ended up finding two ROMs that work for me. I was running stock Android 9 with september's security updates when testing these out:
Roms that i tried, that did NOT work:
BlissOS
ArrowOS
Lineage16
The ROMs that DID work for me were:
phunsson's Treble Experimentations
microG ufOfficial
The only 2 bugs that i've seen so far have been a small graphical glitch of quickettings not staying within the bounds of the pulldown and MTP not working at all. These are both present in both ROMs (The microg ROM uses phhusson's rom as the base). Neither of these bother me all that and i'm very happy to be able to move to microg and not have all the google/samsung bloat hogging my tablet and constantly trying to ping their motherships.
Here's a great list of Generic System Image (GSI) ROMs that you can click scroll through and try downloading and flashing to your device to see if you have any luck.
My process of installing phunsson's GSI ROM:
Reboot to TWRP,
Do a factory reset (Wipe > "Swipe to Do Factory Reset")
Install Image
Reboot
Took about a minute and a half displaying the bootanimation before it got to the home screen for the first time. If it's loading for more than 5 minutes then that ROM definitely isn't going to work with your device.
Hope this helps someone out there trying to get away from their bloated Samsung One UI.
motomotomotoG said:
After hours of trying to figure this out myself i ended up finding two ROMs that work for me. I was running stock Android 9 with september's security updates when testing these out:
Roms that i tried, that did NOT work:
BlissOS
ArrowOS
Lineage16
The ROMs that DID work for me were:
phunsson's Treble Experimentations
microG ufOfficial
The only 2 bugs that i've seen so far have been a small graphical glitch of quickettings not staying within the bounds of the pulldown and MTP not working at all. These are both present in both ROMs (The microg ROM uses phhusson's rom as the base). Neither of these bother me all that and i'm very happy to be able to move to microg and not have all the google/samsung bloat hogging my tablet and constantly trying to ping their motherships.
Here's a great list of Generic System Image (GSI) ROMs that you can click scroll through and try downloading and flashing to your device to see if you have any luck.
My process of installing phunsson's GSI ROM:
Reboot to TWRP,
Do a factory reset (Wipe > "Swipe to Do Factory Reset")
Install Image
Reboot
Took about a minute and a half displaying the bootanimation before it got to the home screen for the first time. If it's loading for more than 5 minutes then that ROM definitely isn't going to work with your device.
Hope this helps someone out there trying to get away from their bloated Samsung One UI.
Click to expand...
Click to collapse
Did AOSP 10.0 work for you? I haven't been able to get it to boot. Strangely AOSP 9 and LOS 16 are the only ones I've had luck with.
@last1youlove whoa! You got LOS to work? What kind of magician are you? That one never booted for me. The only ROM I got working was ArrowOS and it has a few bugs. I really want to get HavocOS to work but it's a no-go!
droidbot1337 said:
@last1youlove whoa! You got LOS to work? What kind of magician are you? That one never booted for me. The only ROM I got working was ArrowOS and it has a few bugs. I really want to get HavocOS to work but it's a no-go!
Click to expand...
Click to collapse
Strange, How did you go about installing it?
last1youlove said:
Did AOSP 10.0 work for you? I haven't been able to get it to boot. Strangely AOSP 9 and LOS 16 are the only ones I've had luck with.
Click to expand...
Click to collapse
I have not. I just really wanted an AOSP based ROM and i had gotten to the point where i had reflashed the stock firmware 3 times through ODIN because I messed up 1 thing or another. So once i got a functional ROM that worked great I just decided to stick to it. Also I don't think Android 10 has Xposed support yet, and i need that in order to enable Signature Spoofing for MicroG's FakeStore.
Hi, I've tried to update my Global Redmi Note 5 Pro's firmware for a few days now to allow usage with the latest pie custom roms, but all the attempts to get my phone booting on the latest versions seem to have failed so far.
Everytime the phone either gets stuck on the boot logo or the loading screen (for more than an hour, so I assume it is bootlooping). I am not sure on what could be causing those issues, though they seem to have appened to a few other people on the miui forum. The phone does not get bricked by installing the latest firmware (fastboot and recovery still work), but it only appears to boot after reflashing oreo firmwares. Pie only seemed to work on custom roms relying on an oreo firmware.
Did those issue happen to anyone else, or has anyone found a solution?
So far what I've tried was:
- Installing the a pie firmware from twrp (from xiaomifirmwareupdater's github), installing a pie compatible twrp, formatting the data and cache partititon, then flashing a custom rom -> stuck on bootlogo
- Reformatting data, cache, vendor and system partitions to make sure they are not somehow damaged, then installing the latest firmware, twrp pie recovery, and a custom rom (retried with more than one custom roms) -> stuck on bootlogo
- Installing the latest stock miui pie fastboot firmware with flash_all.sh (should flash all device partitions) -> stuck on miui bootanimation for more than an hour
- Formatting Data/Factory reset -> still stuck on MIUI bootanimation
- Installing the latest stock MIUI Oreo fastboot firmware with flash_all.sh -> works flawlessy
- Installing any Oreo custom rom -> works flawlessy
So far I've not managed to take any logcat (adb does not detect any device, the issue probably happens before adbd starts running). I am not sure on what could cause those issues.
(I was wondering if it could be related to the latest kernel, though the fact that miui reaches the bootanimation means that it's at least somewhat working; another unlikely possibility might be an hardware issue, but then why'd it work on oreo?)
Thanks in advance for any help
With miui pie, older boot-loader wont work. Infact you would need pie recovery and pie rom to boot. You could try fastboot flashing oreo rom and older rom will work. try to flash arb v4 rom or device will get bricked.
Happend to me once.
What I have done:
Flash latest oreo (or pie for better sake) by miui flash. Remember to match your ARB value.
Go to pie via updater (if you don't care ARB thing. I don't know if fwless pie will work). Don't install recovery now. Let it boot first.
Load pie recovery via fastboot then flash recovery via recovery.
I have the same problems. Pie fw has not been use by dev. So please wait some future rom update
arunmohan16 said:
With miui pie, older boot-loader wont work. Infact you would need pie recovery and pie rom to boot. You could try fastboot flashing oreo rom and older rom will work. try to flash arb v4 rom or device will get bricked.
Click to expand...
Click to collapse
Thanks for the info; shouldn't the bootloader also get updated when fastboot flashing the latest pie firmware? (xbl.elf and abl.elf get flashed, bl looks like an abbreviation for bootloader)
kekesed97 said:
Happend to me once.
What I have done:
Flash latest oreo (or pie for better sake) by miui flash. Remember to match your ARB value.
Go to pie via updater (if you don't care ARB thing. I don't know if fwless pie will work). Don't install recovery now. Let it boot first.
Load pie recovery via fastboot then flash recovery via recovery.
Click to expand...
Click to collapse
Thanks, I just tried to update from an oreo miui firmware via ota as suggested. Unfortunately the result appears to be the same; the phone is stuck on the bootlogo forever and won't boot on a miui pie fw.
namhoang235 said:
I have the same problems. Pie fw has not been use by dev. So please wait some future rom update
Click to expand...
Click to collapse
You mean xiaomi/miui devs? But yeah, I guess waiting for some future update is the only thing I can do for now.
Is it your device is china variant or global variant ??
If your mobile is china variant follow below steps.
Flash China Oreo Fastboot rom using MiFlash Software and then flash China Pie fastboot ROM (Later you can flash global android pie fastboot rom but do not lock bootloader)
If your device global avriant, follow below steps
flash 10.3.1 Oreo fastboot ROM and then flash 10.3.1 android pie fastboot rom (or you can update to android pie using updater method)
this should resolve your issue. for more info visit en.miui.com/a-234.html
SunilSuni said:
Is it your device is china variant or global variant ??
If your mobile is china variant follow below steps.
Flash China Oreo Fastboot rom using MiFlash Software and then flash China Pie fastboot ROM (Later you can flash global android pie fastboot rom but do not lock bootloader)
If your device global avriant, follow below steps
flash 10.3.1 Oreo fastboot ROM and then flash 10.3.1 android pie fastboot rom (or you can update to android pie using updater method)
this should resolve your issue. for more info visit en.miui.com/a-234.html
Click to expand...
Click to collapse
It's a Global variant bought from an official Xiaomi Store in italy, it always worked with global roms.
Unfortunately I also already tried to flash an oreo fastboot (global) rom, then update to pie from there, but the result was the same, stuck on bootlogo.
---
About 10 minutes ago I got it to boot on Pie for about 2 seconds on the setup after another reflash, then it crashed and turned off (and bootlooped).
Idk, I'm starting to think that if it only happens to me it might be an hardware issue. Maybe some blocks of the eMMC are damaged, and the issue only happens in Pie due to the slightly larger firmware images flashed to the various partitions; by coincidence more important data might end up on corrupted blocks.
I'll have to verify by dumping the partitions some times and verifying the data/checking for coherency between the dumps
rw-r-r_0644 said:
It's a Global variant bought from an official Xiaomi Store in italy, it always worked with global roms.
Unfortunately I also already tried to flash an oreo fastboot (global) rom, then update to pie from there, but the result was the same, stuck on bootlogo.
---
About 10 minutes ago I got it to boot on Pie for about 2 seconds on the setup after another reflash, then it crashed and turned off (and bootlooped).
Idk, I'm starting to think that if it only happens to me it might be an hardware issue. Maybe some blocks of the eMMC are damaged, and the issue only happens in Pie due to the slightly larger firmware images flashed to the various partitions; by coincidence more important data might end up on corrupted blocks.
I'll have to verify by dumping the partitions some times and verifying the data/checking for coherency between the dumps
Click to expand...
Click to collapse
Hello! You're not the only one facing this.
I also have Redmi Note 5 global model, and I'm facing the very same problem. I've tried everything, just like you...
I don't see many people with this problem but I found other 3-4 with the same problem: on Mi Community forum and in some Facebook groups. No one is having success... No one is able to fix this!
I'm worried, because as we are not too much facing this problem, maybe Xiaomi is not knowing that this is happening.
Contact me if you want to know more, and maybe together we can make anything! Let's hope for the best!
floater3 said:
Hello! You're not the only one facing this.
I also have Redmi Note 5 global model, and I'm facing the very same problem. I've tried everything, just like you...
I don't see many people with this problem but I found other 3-4 with the same problem: on Mi Community forum and in some Facebook groups. No one is having success... No one is able to fix this!
I'm worried, because as we are not too much facing this problem, maybe Xiaomi is not knowing that this is happening.
Contact me if you want to know more, and maybe together we can make anything! Let's hope for the best!
Click to expand...
Click to collapse
same thing happening to me also tried everything
floater3 said:
Hello! You're not the only one facing this.
I also have Redmi Note 5 global model, and I'm facing the very same problem. I've tried everything, just like you...
I don't see many people with this problem but I found other 3-4 with the same problem: on Mi Community forum and in some Facebook groups. No one is having success... No one is able to fix this!
I'm worried, because as we are not too much facing this problem, maybe Xiaomi is not knowing that this is happening.
Contact me if you want to know more, and maybe together we can make anything! Let's hope for the best!
Click to expand...
Click to collapse
Ok...you all are not alone it seems.
Couple of months back I faced this issue but after struggling for a day I managed to boot into miui latest (global) after which I found my EFS+Modem partitions corrupted (ie. unknown baseband,no wifi or imei )...I guess data corruption is the cause.I went to the service center, they told me it was data corruption and the entire Motherboard had to be replaced...they quoted a price of ~Rs 8000 (Incl. GST ) for the repair...I am since then stuck without a phone
Edit: BTW...I bypassed the bootloop by flashing the latest global recovery rom through orange fox...(not recommended cause it might cause you to lose wifi and imei)..
The below is a guide to installing GSI images on the Mi 8 Pro. I specifically have experience with the PixelExperience 9.0 (Unofficial) but have had other GSI ROMs booting and working. I hope this is useful for some.
GSI (Generic System Image) ROMS can be flashed to any Project Treble enabled device. These devices have either an A/B partition layout (these allow for seamless updating as the system can boot from A or B partition) or just an A only partition layout. The Mi 8 Pro is an arm64 a only device and support project treble ROMs. You can choose from suitable ROMs listed here and here.
The instructions given below are for Android Pie (9.0). The same basic setup can be used for Android Oreo (8.0, 8.1) ROMs, but the Mi 8 Pro should be flashed with the appropriate Xiaomi base ROM first before flashing any 8 based GSI ROM
As the ROM development for the Mi 8 Pro is basically dead, I decided to buy a OnePlus 6T and sell my Mi 8 Pro. However, due to having my new OnePlus 6T stolen, and due to a lack of funds to buy a new device, I have revived my Mi 8 Pro to try to get something other than MIUI working on it. I now have The PixelExperience (Unofficial) GSI ROM running very smoothly on my Mi 8 Pro.
As the PixelExperience team has stated they will be delivering GSI images again, if there are enough of us asking, we could get better support for things like the fingerprint sensor, for a more complete experience.
Some of the below steps may be unnecessary, but are there for a complete beginner's guide to doing this and getting the right results.
Working:
WiFi
Bluetooth (with APTX)
NFC (Including Google Pay)
RIL
Mobile data (LTE / HSPDA / 3G / EDGE)
GPS
Camera (with camera built in to ROM, as well as some GCAM implementations)
Video Camera (not working on GCAM implementations tested so far - only working on Camer built in to ROM)
Flashlight
Sound / Vibrations
Face Unlock
Hotspot
Not Working:
VoLTE (I have had it working, but unable to end phone calls and problems receiving SMS messages, so reverted)
Fingerprint (There is some support. The fingerprint area of the screen lights up when trying to enrol a new fingerprint. The screen dims when a finger is placed on the sensor, and a green light us emitted from the sensor area, but it does not register the fingerprint and this is not currently working.)
Notification LED
You Tell Me
How to install
Flash the latest Fastboot Global Stable Android PIE (9.0) ROM for the Mi 8 Pro. (eg. equuleus_global_images_V10.3.4.0.PECMIXM_20190712.0000.00_9.0_global_9a181f79c1.tgz) using the Xiaomi Tool.
Update: Use the latest MIUI system. The contents of the vendor partition are important. The most compatible vendor partition as of 2019-08-19 is from equuleus_global_V10.3.5.0.PECMIXM. You can download and flash that vendor independantly, if you have already set up your GSI image.
Reboot and finish basic MIUI setup.
Reboot to recovery.
[*]Format data (Wipe - Advanced - format data - confirm by typing yes)
DO NOT FORMAT DATA. Just perform a factory reset. Formatting data can cause issues and prevent booting.
Wipe Cache - Dalvik Cache and System
Reboot recovery
Use adb to push PixelExperience GSI image (img file extracted from download) and latest version of Magisk to root of SDCard. (Empty due to formatting data).
("adb push c:\path\system.img /sdcard/" and then "adb push c:\path\Magiskv19.3.apk /sdcard/")
Flash the image to system partition by taping INSTALL and then on the "Install Image" button (to toggle between flashing zip and img files). Do not reboot yet.
Flash magisk zip in the normal way (hit the same button as in previous step to show zip files to flash. (This is necessary to avoid bootloops)
Reboot, and enjoy.
You can now set up your "PixelExperience" device with your apps and settings, including registering a face for face unlock.
To pass cts validation for the safetynet and to allow service such as Google Pay to work
In Magisk, under settings - Find “Magisk Hide” and toggle the switch on
Magisk restarts. Go to Magisk Hide from the Magisk menu and ensure that...
Google Pay
Google Play
Google Play Services
Google Service Framework
Any Banking Apps
...are checked so that they cannot see Magisk (canont see phone as rooted).
Now go to downloads and install the SafetyPatch v3 module (created by hackintosh5).
Reboot.
Open settings - go to apps and notifications - and find the above apps to clear all data.
Enjoy your rooted safetynet compliant, as close to stock as possible Xiaomi Mi 8 Pro.
nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!
axelgrox said:
nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!
Click to expand...
Click to collapse
Face unlock works fine. I have it paired with Pick to wake phone - so when I pick it up it wakes up to allow face unlock.
However, be prepared for some investment of time (not for face unlock).... I am a bit stuck now and cannot reproduce the above to get this working. Sometimes the results are different depending on base ROM etc.
Share how you get on and anything you may need to do to get this working.
Thanks
Nice work, i will try it .
The mi8 pro 's fingerprint is so bad which can be ignored, and the face unlock is the mostly used, hahahah
thank you very much for your work
Hi, I am waiting to unlock bootloader. Need 148hrs. Will install this. Thanks for sharing.
Quick update: There are some issues with GSI ROMs and the Mi 8 Pro. SOe of these relate to the SIMcard settings - and selection of preferred SIM for data, calls etc.
My experience shows that the vendor image from equuleus_global_V10.3.5.0.PECMIXM fixes many of these. The vendor image from the original MIUI ROM is used with the GSI system image to make the whole Project treble stuff work. I advise flashing this latest vendor image for maximum compatibility.
Do you know what issues remain after flashing the latest vendor image?
Does the face unlock on Pixel Experience work with IR camera or front cam?
I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!
eremeya said:
I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!
Click to expand...
Click to collapse
Have experienced this on occasion also.
What GSI image have you tried? after my multiple efforts, I would recommend... in this order: Omni. HavocOS, Descendant(no future updates), PIxelExperience. I am hopeful about the PixelExperience team who have made an announcement that as of August they will no longer produce CAF versions of PixelExperience, and that they will maintain regular GSI builds also. PE official GSI - I am full of hope.
Anyway, back on topic: Try this.
Follow the instructions - a few precisions:
Use XiaoMiFlash to flash the equuleus_global_images_V10.3.4.0 as a base. You can update the vendor partition once you have GSI up and running, but don't let the MIUI update to 10.3.5. Ensure you define a PIN to make sure that data partition is encrypted. (everyone should use encryption nowadays, and besides, I have had bad experiences whn using a xiaomi eu or mi-globe ROM (unencrypted) as the base
Reboot and finish basic MIUI setup. - What I mean here is to let the ROM boot, don't have to sign in to Google or Mi, but get to the home screen after the initial setup.
Then reboot fastboot and flash TWRP 3.3.0. Search for TWRP-3.3.0-0504-XIAOMI8UD-CN-wzsx150.zip.
Boot to TWRP. Make sure that you are able to decrypt the data partition with the PIN you set earlier. If TWRP does not ask you for the passcode / PIN - something is wrong. Try again. ONce all is OK in TWRP, perform factory reset. (DO NOT FORMAT DATA for the aforementioned encryption reason).
adb push the img file.
adb push the Magisk 19.3 zip.
Flash both in TWRP
Reboot TWRP
Reboot system. If it appears to hang, after 5 minutes you can force restart with the power button. I have had the ROM boot OK after second boot only?
Pretty sure that if you strictly follow the above you should get a working GSI image on Mi 8 Pro. Let me know...
It's a bit flaky to set up, but once set up, apart from fingerprint sensor not working, very stable and lovely to have the stock ish android system on a MIUI phone!
Be careful with preferred network type for mobile network as some selections have messed up incoming SMS messages for me... a dealbreaker.
What happens when you flash Magisk? What does TWRP say? Have you tried flashing Magisk, rebooting TWRP, and flahing Magisk again? It may be a TWRP version issue?
Thanks for your reply!
The version of twrp you mention is what I have used. I have not tried installing then rebooting to twrp so I try that.
When flashing magisk it usually flashes fine (I have had a couple times where it just throws an error) then when I reboot the phone will boot past the Mi logo the the Android boot logo then after 10-15 sec. it just reboots to twrp.
I was finally able to get the twrp to stick across boots by flashing twrp, signing boot image, removing twrp then reboot to Miui.
Do I need to adb push the GSI image or should it be fine to install from a USB drive?
The SMS issue isn't really a big deal for me as I use Google Fi routed through hangouts for one sim and a local sim where I'm living for mostly data and a few phone calls for the second one
Thanks so much for this post. I was completely oblivious to the fact that the Mi 8 Pro would actually be different to the Mi 8 when it comes to custom roms. When I decided on my next phone, I read the positive reviews and saw enough Mi 8 roms to be willing to make a switch to Xiaomi. Until I read your post I was close to despairing as I don't want a Xiaomi rom on my phone for various reasons (among them is the fact that I don't trust them and the way they have decided to collect user data).
I've tried to follow your guide in every step (I've also flashed the updated vendor.img), but unfortunately I have not been able to install the Pixel Experience rom on my device. I do see the boot animation but it never stops, I'm forever stuck with the Google-G and the progress bar below it. Has anyone else managed to install the Pixel Experience rom on the Mi 8 Pro? If yes, did you follow the guide here or did you do something else?
Also, in your initial post you write that we should wipe the system in TWRP but as far as I can tell GSI roms need you to wipe data, cache and dalvik cache but not the system partition (if you do it, you also don't get asked for your PIN code in TWRP any more, which - as you said - indicates that something went wrong).
Did you install a particular version of the Pixel Experience rom? Maybe that might be part of my issue?
I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.
tllim73 said:
I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.
Click to expand...
Click to collapse
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.
eremeya said:
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.
Click to expand...
Click to collapse
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.
tllim73 said:
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.
Click to expand...
Click to collapse
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?
eremeya said:
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?
Click to expand...
Click to collapse
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
I try rooting it with magisk but unable to boot up. That's why I turn to Miroom Rom. They have done something which can boot it up.
tllim73 said:
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
Click to expand...
Click to collapse
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
Might be the developer version is only for the Chinese Rom. Anyway I am happy now running with GSI Rom.
eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
What version of TWRP are you using?
Introduction
This is a LineageOS Recovery compiled from the source tree of LineageOS 17.1 for Redmi K30 5G. This is part of my ongoing work to port LineageOS 17.1 to this device. Work on the actual LineageOS 17.1 ROM is still under way (but it should be available very soon), while the recovery has been usable for quite some time now. Since it is not possible for TWRP to support any device launched with Android 10 for now, I figured that this might be useful even before I release the LineageOS custom ROM (e.g. people may want to flash Magisk on official ROMs).
I am aware that there is a TWRP port for this device, but since the source code is not accessible (as for as I can tell, maybe I just did not look hard enough for the source code), I can only advice against using it. The official TWRP open-sourced under GPLv3 does not even support devices launched with Android 10 yet, so there's clearly something going on here. I do not fix compatibility issues between my ROM and that TWRP port.
Instructions (Installing Recovery)
This recovery ONLY works on MIUI firmware version v11.0.11.0 (stable firmware before May 2020). Xiaomi hasn't released kernel source update for later firmware versions and you may experience blank screen and similar issues if you are on a newer firmware.
1. Download vbmeta.img, recovery-XXXX.zip (extract to get recovery.img)
2. Reboot to bootloader (`adb reboot bootloader`)
3. Run `fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img`
4. Run `fastboot flash recovery recovery.img`
5. Run `fastboot reboot recovery` to enter LineageOS Recovery
Instructions (Installing Magisk)
You have to use the official Magisk, version 20.4 or later. Installing an older Magisk will make the system unbootable.
1. Download Magisk >= 20.4, put onto computer
2. Reboot to LineageOS recovery, select `Mount /system` (you may see some errors, but they can be safely ignored)
3. Select `Apply update from ADB`
4. Run `adb sideload Magisk-xxx.zip`
5. You will see a signature verification error, select `Yes` to bypass the check
6. Reboot to system to enjoy your Magisk installation.
Caveats
1. Since it's not TWRP, you cannot decrypt your /data in recovery for now, which means no data backup or recovery, and you cannot install on-device flashable zips through this recovery.
2. Since it's not TWRP, it cannot prevent your OS from overwriting recovery automatically. If you use official ROM, you may need to manually re-flash the recovery every time. I'm not sure whether this can be bypassed with some Magisk module.
3. Don't expect to be able to flash anything into /system (e.g. OpenGAPPS) on stock ROMs; you might be able to do so once my LineageOS ROM is released
4. When trying to install OpenGAPPS on LineageOS 17.1 (not released yet as of 2020-03-06), it will get stuck at the end of the flashing process. This does not affect the functionality of the installed system and gapps, and a force-reboot into system will work just fine. Use my patched OpenGAPPS in the LineageOS thread.
5. You need to always click "Mount /system" before flashing any mods into the system (i.e. Magisk, OpenGapps, etc., ROMs themselves are not affected), otherwise they will fail to install. (Clicking the option does not actually mount /system; it just sets up necessary mappings from the super partition to each of the dynamic partitions so that the installation scripts will work)
Downloads
LineageOS Recovery (17.1, 2020-03-06): https://mega.nz/#!PZRCBaiA!L-c3Tn6E295xcAIZCSt9ribpGsutX3QJRt04uyQGg_k
Changelog: Improved compatibility with OpenGAPPS (won't work with MIUI; this change is solely for the soon-to-be-released LineageOS 17.1 port)
LineageOS Recovery (17.1, 2020-03-01): https://mega.nz/#!XI4BGDQS!CPH2kIUdqaTtU_Zdzx8bUiL7FcU-G51RwmdH0MGbSRk
vbmeta.img: https://mega.nz/#!vQohmJgJ!IWAjbxGIxxxQ4OScQH8YT8oKJMx8Q-2pV83zqxbItD4
Source Code
Device Tree (including LineageOS 17.1 port): https://github.com/PeterCxy/android_device_xiaomi_picasso
Kernel: https://github.com/PeterCxy/android_kernel_xiaomi_sm7250
Hello,
Thanks for the custom recovery and Magisk. Would that recovery work on K30 (not 5G) or Poco X2?
Good work and keep it up!
DyXen said:
Hello,
Thanks for the custom recovery and Magisk. Would that recovery work on K30 (not 5G) or Poco X2?
Good work and keep it up!
Click to expand...
Click to collapse
Probably won't. Those two phones are totally different from the 5G version, despite their similar name / non-SoC specs. They are closer to K20 than K30 5G.
What is the progress of this LineageOS?
How long can you experience it?
syutung said:
What is the progress of this LineageOS?
How long can you experience it?
Click to expand...
Click to collapse
I'm dogfooding right now. If I don't brick my phone by dogfooding my LOS port then it will be available for download in one or two days.
PeterCxy said:
I'm dogfooding right now. If I don't brick my phone by dogfooding my LOS port then it will be available for download in one or two days.
Click to expand...
Click to collapse
I got blanky blank screen on booting this recovery :/
It only shows the first two lines
Help
Hello!
I am trying to follow the instructions to install the Lineage Recovery on my K30 5G (Speed edition), which is also codenamed "picasso" and shares the same MIUI ROM with normal K30 5G.
No luck with a mostly blank screen after booting into recovery:
imgur.com/a/cmpDedZ (sorry for the bad quality because I shot it with a webcam). As in the picture, only one and a half lines of yellow text are visible near the top, which reads "Lineage Recovery" and "Redmi/picasso/picasso". The other part is just in grey without anything except a dotted vertical blue line (almostly invisible in the picture; not the thick white lines which is just reflection) in the middle of the screen. Besides, it seems to respond to the power/volume key.
I notice that you mentioned in the other thread that your ROM requires a specific MIUI firmware version. Then does the Recovery also require so? (I didn't have a chance to try that because my phone got fully bricked immediately after downgrading to V11.0.11.0 (now fixed).) Or do you kindly have any advice?
Thanks.
Pycoo said:
Hello!
I am trying to follow the instructions to install the Lineage Recovery on my K30 5G (Speed edition), which is also codenamed "picasso" and shares the same MIUI ROM with normal K30 5G.
No luck with a mostly blank screen after booting into recovery:
imgur.com/a/cmpDedZ (sorry for the bad quality because I shot it with a webcam). As in the picture, only one and a half lines of yellow text are visible near the top, which reads "Lineage Recovery" and "Redmi/picasso/picasso". The other part is just in grey without anything except a dotted vertical blue line (almostly invisible in the picture; not the thick white lines which is just reflection) in the middle of the screen. Besides, it seems to respond to the power/volume key.
I notice that you mentioned in the other thread that your ROM requires a specific MIUI firmware version. Then does the Recovery also require so? (I didn't have a chance to try that because my phone got fully bricked immediately after downgrading to V11.0.11.0 (now fixed).) Or do you kindly have any advice?
Thanks.
Click to expand...
Click to collapse
The recovery may not work on newer MIUI firmware versions because Xiaomi didn't release corresponding kernel source updates for those newer versions. This is unfortunate, but I can do nothing about it. Ask Xiaomi to release their source code.
Hi Peter,
Thanks very much for porting Lineage OS onto the Redmi K30 5G Pro. Mine arrived today, and I'm planning on installing your port ASAP.
However, I have run into a problem: The device shipped with MIUI version 11.0.12.0. Your post in the Lineage OS Recovery thread says that I can only install it on MIUI 11.0.11.0.
Do you know how I can downgrade my MIUI software so that I can install Lineage OS Recovery?
Thanks!
After doing this now I can't flash Twrp anymore (got bootloop). pls help
Anyone know the proper procedure to go back to Oxygen OS from LineageOS. I tried fastboot and I got errors after every command. flashing is not allowed for critical partitions, it's driving me mad.
Needs fastbootD:
[ROM][STOCK][FASTBOOT][OP7T] Stock Fastboot ROMs for OnePlus 7T
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are...
forum.xda-developers.com