Database Info

Android Nougat ROMs List for the BLU Life One X 2016

This is a list of Nougat ROMs for this device and it's clones.
The list will be in the following format:
ROM : Version : Device : Tested/Untested
LineageOS : 14.1 : MMXC5 / E481 : Untested
Resurrection Remix : 5.8.4 : MMXC5 / E481 : Tested
crDROID : v3.5 : MMXC5 / E481 : Tested
AOSGPX : 7.1.2 : MMXC5 / E481 : Untested
There are also ROMs for the Elephone P8000, however the first time I tried one I got into a bootloop. It could just have been that I didn't wipe my caches, or it could have been a fault in the ROM; nonetheless I haven't tried any others from that device.
I couldn't find any for other devices, let me know if you see others.
Here is the factory firmware, as according to this post (Direct Download).
Also, the stock recovery: Original Post | Direct Download.

Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.

elbastardo1 said:
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
Click to expand...
Click to collapse
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.

BereiBlue said:
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
Click to expand...
Click to collapse
Only bug so far is the kill app button not working (long press the back button) and sometimes after reboot sim cards not being detected. Usually it corrects itself after a few minutes. If not, I'll just re-flash the fix
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.

elbastardo1 said:
Only bug so far is the kill app button... and sometimes after reboot sim cards not being detected...
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
Click to expand...
Click to collapse
Happy to hear only minor bugs. I'm waiting on black Friday SD card to ship and then I'll be able to test too.
On lollipop all I needed to use was power nap to kill unwanted wake locks. I'll definitely try to get it to work because batter life is important to me. Only reason I'm upgrading is because of older exploits that stock didn't get updates for. Other than that stock with xposed is extremely stable for me.(30-60 days between reboots)
Do you know if crDroid is using stock lollipop kernel or is it a ported kernel? That would effect battery life greatly I suppose.

review of roms
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me a part of this rom was made by another group of people that were not given credit.. Default browser loads the homepage of the other group. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.

BereiBlue said:
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me this was made by some Russians. Default browser loads RU homepage. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
Click to expand...
Click to collapse
Just wondering with the ROM testing, did you disable the LiveDisplay nonsense? It drops my FPS to about 10, and is enabled by default.
Sorry, didn't read your whole post. I didn't find UI stuttering unless I enabled weird kernel stuff, or had L Speed installed.

Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?

tinpanalley said:
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
Click to expand...
Click to collapse
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.

elbastardo1 said:
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
Click to expand...
Click to collapse
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?

tinpanalley said:
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
Click to expand...
Click to collapse
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.

elbastardo1 said:
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
Click to expand...
Click to collapse
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?

tinpanalley said:
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
Click to expand...
Click to collapse
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.

elbastardo1 said:
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
Click to expand...
Click to collapse
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?

tinpanalley said:
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
Click to expand...
Click to collapse
You could flash a lollipop twrp backup, if anyone uploaded one or if you made one before. But if you don't have it, only way is by sp flash tool and original firmware (which is not a recovery flashable zip).

Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.

Teblakuda4o4 said:
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Click to expand...
Click to collapse
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.

tinpanalley said:
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
Click to expand...
Click to collapse
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.

Teblakuda4o4 said:
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Click to expand...
Click to collapse
I'd just not use the radio. [emoji4]

tinpanalley said:
I'd just not use the radio. [emoji4]
Click to expand...
Click to collapse
But the thing is you don't know what else has been tampered with.

Successfully able to boot Project Treble/AOSP rom

This is not a guide as such but more of direction to other peoples hard work and effort. I am not a developer, just an experimenter!
Main Credits - @MishaalRahman and @phhusson.
For me one of the main selling points of the Mediapad M5 was being Project Treble enabled. Being a big Nexus/Pixel fan I am not particularly fond of EMUI.
So after reading this detailed and clear guide by Mishaal Rahman http://www.xda-developers.com/flash-generic-system-image-project-treble-device/, I was able to successfully install an AOSP Generic System Image by phhusion http://forum.xda-developers.com/project-treble/trebleenabled-device-development/experimental-phh-treble-t3709659
My device - CMR-W09 (10.8" non pro wifi).
I flashed v17 with Gapps and SU and apart from an Android System error upon boot it seems to work ok. I have not had much time to play with it but so far Wifi, Bluetooth, sound, camera, fingerprint sensor, MTP and SD card appear to be working. I had issues with google play not downloading apps but worked after clearing data/cache on google play and google play services. Also have issues with superuser force closing.
For the nervous and unsure, you can easily return to stock Huawei firmware by flashing your devices stock system.img in fastboot.
Obviously bootloader needs to be unlocked see guide - https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275 by @Apo11on. You can use Apo11on's root guide to download your firmware to get your stock system.img.
OEM needs to be disabled in developer options.
It is best to factory reset via recovery mode and then boot straight into bootloader to keep FRP unlocked.
Do this at your own risk but please read all the available information and guides on XDA.
pphusion has made other Project Treble roms but I have yet to try them. Hopefully it would be nice if someone could fully develop Lineage for this device.

which rom did you use ? the A/B one or A only ?

It's an A-only device.
I tried AOSP with GAPPS and SU but SuperSU shows the su binary as being occupied through several reboots. Getting the Lineage GSI now and will root with magisk.
Edit:
Blah... Lineage is not an option until we have twrp :/ (at least for me) No way to install GAPPS.
Edit:
SU works with phh's super user available from the play store.

Yes i have the AOSP one now on my AL-09 and it works fine till now. Bugs : home Button not working but fingerprint works, supersu with the phhs one works. Bluetooth sometimes gives an error message. Battery drain is a little bit high. I installed the Huawei camera apk from treble forum and This works also good.
Another Bug is Apps sometimes force closing but Not often.
How is Lineage performing?

A little bit off topic, but how did you unlock the bootloader on the Wifi only version since the website for the code is offline for a few weeks now?
Thanks in advance.
Fantastic to see that Treble works.

On my AL09(ASOP with gapps and su) bluetooth never connects to any of my devices and fc on pairing.
Lineage was a non-starter, since I was unable to get gapps running. I was also getting a vendor mismatch toast. I'm back on the stock .125(C00), no working tether is infinitely more useable than no BT.
It was nice to be able to flash something that didn't brick it and was partially useable.

fargonaz said:
On my AL09(ASOP with gapps and su) bluetooth never connects to any of my devices and fc on pairing.
Lineage was a non-starter, since I was unable to get gapps running. I was also getting a vendor mismatch toast. I'm back on the stock .125(C00), no working tether is infinitely more useable than no BT.
It was nice to be able to flash something that didn't brick it and was partially useable.
Click to expand...
Click to collapse
I understand, Do you think it gets more stable for our device in the future?

florian-m19 said:
I understand, Do you think it gets more stable for our device in the future?
Click to expand...
Click to collapse
I think so, if you look at the github comments there is a huawei phone having the same problem, so as long as a phone is having problems it should get fixed

We would like some screenshots to see if this is real @AndDiSa @rcstar6696 @phhusson @MishaalRahman

Just installed it, attached a few screenshots. Haven't tested it a lot, but it boots.

Wie are Not joking, its real ??

Delete, double post

I will be getting my Mediapad M5 8.4 tomorrow and will be flashing the AOSP treble build straight away. Just a heads up a updated build has just been posted with some Huawei related fixes.

i flash it now, and give feedback tomorrow

I flashed the new one with gapps and su, and for the sht-l09 there is no working bluetooth, so that's as far as I go. It will be nice when the BT is fixed for this device.

Works good with dirty flash, Home Button is working now and also Automatic Brightness, but battery draining is really high and it gets hot.

florian-m19 said:
Works good with dirty flash, Home Button is working now and also Automatic Brightness, but battery draining is really high and it gets hot.
Click to expand...
Click to collapse
Have you tried changing the cpu governor? Is it set to something like interactive? I got my Mediapad today but I am waiting for the bootloader unlock code from Huawei.

darren1 said:
Have you tried changing the cpu governor? Is it set to something like interactive? I got my Mediapad today but I am waiting for the bootloader unlock code from Huawei.
Click to expand...
Click to collapse
yes it is on interactive, should i change this ?

florian-m19 said:
yes it is on interactive, should i change this ?
Click to expand...
Click to collapse
Might be worth experimenting with. Try conservative or ondemand if they are available. You can always change back if it doesn't make any difference.

darren1 said:
Might be worth experimenting with. Try conservative or ondemand if they are available. You can always change back if it doesn't make any difference.
Click to expand...
Click to collapse
okay i change it in helix engine to ondemand and the suspend engine is now on powersafe.

[ROM] [Experimental] [LineageOS 15.1] [8.1] [Build 2018-07-05] [Oppo R7f]

First off, huge thanks to all the LineageOS developers. Specially MikeNG for his continuous work on OPPO devices.
Lineage 15.1 is finally here!
Device(s) Supported:
R7f *ONLY*
Don't flash this rom to any other R7 variant
What's working:
* Boot (Much better than not booting obviously)
* RIL (Calls,Text,Data)
* WiFi
* Bluetooth
* Camera
* Audio
* Sensors
* Flashlight
* Notification LED
What's not working:
* Double tap screen to lock/unlock. Unlock not working
From Stock (ColorOS) Installation:
*Charge battery near full, DISCONNECT usb cable
Having the USB cable connected in this process causes hard to get out of bootloop after installation
1. Boot phone in fastboot mode: Press and hold both Power + Volume Up buttons.
2. Unlock boot loader with command: fastboot oem unlock
3. Flash recovery with command: fastboot flash recovery name.recovery.img
4. Reboot phone into recovery mode using command "fastboot reboot-bootloader" and press and hold Volume Down button.
5. Full wipe of device. Place ROM and Gapps on external SDcard or use ADB to transfer them to the (now wiped) internal Data partition.
6. Install ROM and GApps.
7. Reboot phone and wait (first boot will take quite a bit of time)
* If you don't have any previous experience with rooting, custom roms & recoveries. Please follow the more 'newbie' friendly in-depth tutorials
XDA forums has plenty of well done easy to follow tutorials!
From Lineage 14.1 :
*Charge battery near full, DISCONNECT USB cable before reboot into recovery
Having the USB cable connected in this process causes a hard to get out of bootloop after installation
*Make sure you have the latest TWRP recovery installed before continuing
1. Wipe device, perform a clean install
Downloads :
[ROM] Unofficial R7f LineageOS 15.1
Archive must be unpacked! Contains flash-able zip & md5 checksum
[Gapps -> ARM -> 8.1]
*Don't select the Aroma variant. TWRP doesn't like it
[TWRP Recovery for R7f] (twrp-3.2.2-0)
NOTES:
*This is bat country! You are on your own when something goes bad, I can't help you in case of bricked device
*Precaution: Charge battery atleast 80%
*Advisable: Make Nandroid backup before flashing
*Precaution: Due to a weird device specific bug
Don't (re)boot into Recovery nor flash the R7 with the USB cable still attached. Could result in a bootloop which is rather hard to get out off
Bootloop trick: When finally powered off, leave the device off for at least a hour Take a walk or something!
No idea why but this seems to do the trick, after a prolonged period of being turned off, it boots normally into LineageOS
And will continue to reboot just fine! Maybe disconnect usb cable before rebooting out of precausion tho

Great work once again!
I assume this will be without the "project tremble" hardware separation layer introduced in Android Oreo, no?
With the differences in Android versions compared to stock, I do start to wonder, what are the drawbacks with this ROM? I mean in terms of performance, size, etc. Do you know of any?

Forage81 said:
Great work once again!
I assume this will be without the "project tremble" hardware separation layer introduced in Android Oreo, no?
With the differences in Android versions compared to stock, I do start to wonder, what are the drawbacks with this ROM? I mean in terms of performance, size, etc. Do you know of any?
Click to expand...
Click to collapse
Thank you!
Concerning Tremble, can't have 8.1 without but seems to be using legacy & updated vendor blobs.
Not sure what you mean with "stock" Stock AOSP 8.1 builds or the stock ColorOS?
Compared to stock ColorOS 4.4. too many differences to name. Compared to AOSP, I'd suggest reading into LineageOS features
Drawbacks to using this rom I can't think of one. Till now everything seems to be working just fine
Performance seems to be great, Battery life seems better than LineageOS 14.1 and concerning size it's smaller than stock ColorOS

I believe tremble is mandatory for new phones and optional for existing that update to 8.1.
You would have known you are using Tremble if you are the one who created the port for this phone.
I don't believe you can just use existing blobs for a change like that and it would require help from Oppo, who had never offered even the slightest for our phone.
I meant Lineage OS 15.1 compared to stock Oppo/ColorOS. I know the differences OS/functionality wise. With such a big jump I would have expected at least performance issues since non of the blobs have been touched anymore. Decreased compatibility seems likely to me in such a case.
Good to hear you do not experience this.
I am hesitant to take the risk using this ROM though. For the same reasons mentioned above.
Have you been using the phone in real life without (too many) glitches for a bit by now?

I really hope
I already test this rom.
It's really good.
I found the bug
1. Charging slow. Take 1 hour 45 mnite to full
2. Double tap to wake not work
I'm back to your previous rom 14.1
In Los 14.1 your build. Fast charging like vooc dan double tap to wake work.
Can u fix it?
Thanks somuch for great work.

Ravhinzy said:
I already test this rom.
It's really good.
I found the bug
1. Charging slow. Take 1 hour 45 mnite to full
2. Double tap to wake not work
I'm back to your previous rom 14.1
In Los 14.1 your build. Fast charging like vooc dan double tap to wake work.
Can u fix it?
Thanks somuch for great work.
Click to expand...
Click to collapse
Both work fine in this 15.1 build
VOOC charging, and double tap @ statusbar/lockscreen
Must be something on your end. did you perform a clean install?
Wipe system,data,cache dalvik etc
But out of precaution I'll test it further in the coming days. More charging and more tapping on my screen

Forage81 said:
I believe tremble is mandatory for new phones and optional for existing that update to 8.1.
You would have known you are using Tremble if you are the one who created the port for this phone.
I don't believe you can just use existing blobs for a change like that and it would require help from Oppo, who had never offered even the slightest for our phone.
I meant Lineage OS 15.1 compared to stock Oppo/ColorOS. I know the differences OS/functionality wise. With such a big jump I would have expected at least performance issues since non of the blobs have been touched anymore. Decreased compatibility seems likely to me in such a case.
Good to hear you do not experience this.
I am hesitant to take the risk using this ROM though. For the same reasons mentioned above.
Have you been using the phone in real life without (too many) glitches for a bit by now?
Click to expand...
Click to collapse
Concerning your last question
Haven't turned my phone off since 7-5 while running this 15.1 build
Works great so far. Haven't found issues/glitches as of yet. No weird things happening with my daily usage thus far

-Oops things went a bit wrong-

JJRT said:
Both work fine in this 15.1 build
VOOC charging, and double tap @ statusbar/lockscreen
Must be something on your end. did you perform a clean install?
Wipe system,data,cache dalvik etc
But out of precaution I'll test it further in the coming days. More charging and more tapping on my screen
Click to expand...
Click to collapse
Thanks for ur answers.
Oh. I will try it again. I always clean install like u said.
Double tap to sleep work fine in status bar or home botton. But to wake, all screen i taping, the phone not wake. Any ideas the problem?
I back to Los 14.1. all fine.
I really like u work on los 15.1. i want to use it

Ravhinzy said:
Thanks for ur answers.
Oh. I will try it again. I always clean install like u said.
Double tap to sleep work fine in status bar or home botton. But to wake, all screen i taping, the phone not wake. Any ideas the problem?
I back to Los 14.1. all fine.
I really like u work on los 15.1. i want to use it
Click to expand...
Click to collapse
Ah indeed, the waking up using double tab isn't working atm.
I will look into that. The 15.1 build is perfectly usable otherwise.
But yeah you can roll back to 14.1 in the meantime if you really need the double tap option

JJRT said:
Ah indeed, the waking up using double tab isn't working atm.
I will look into that. The 15.1 build is perfectly usable otherwise.
But yeah you can roll back to 14.1 in the meantime if you really need the double tap option
Click to expand...
Click to collapse
Yes. I wait until the problem fix. And plis check charging time

Ravhinzy said:
Yes. I wait until the problem fix. And plis check charging time
Click to expand...
Click to collapse
The charging time should not be impacted in any way as it is hardware based. Unless a ROM or app is using extreme resources while charging, draining the battery at the same time you are charging it, charging times should be the same in both 14.1 and 15.1.
Please double check if it has really changed.

Forage81 said:
The charging time should not be impacted in any way as it is hardware based. Unless a ROM or app is using extreme resources while charging, draining the battery at the same time you are charging it, charging times should be the same in both 14.1 and 15.1.
Please double check if it has really changed.
Click to expand...
Click to collapse
Ok, thank you. I have returned to los 14.1. how to fix or replace double tap to wake to work? I want to try again. I will check it again

Wow amazing work!
I have checked that charging times are the same as los 14.1 as opposed to claims by Ravhinzy.
However, the issue of double tap to unlock is also present for all other screen off gestures (drawing O, M, V etc. when screen is off). Other than that, the roms seems stable enough. (so are u planning to make r7f rom official on lineage os?)
In any case, keep up the good work and thanks for sharing this rom!

ph03nae said:
Wow amazing work!
I have checked that charging times are the same as los 14.1 as opposed to claims by Ravhinzy.
However, the issue of double tap to unlock is also present for all other screen off gestures (drawing O, M, V etc. when screen is off). Other than that, the roms seems stable enough. (so are u planning to make r7f rom official on lineage os?)
In any case, keep up the good work and thanks for sharing this rom!
Click to expand...
Click to collapse
do you know how to fix dt2w?
eg with flash module or update.zip to fix it.
I've been looking for ways on google how to fix it still has not worked.
I really hope to get this cusrom. fell in love when first tried it.

ph03nae said:
Wow amazing work!
I have checked that charging times are the same as los 14.1 as opposed to claims by Ravhinzy.
However, the issue of double tap to unlock is also present for all other screen off gestures (drawing O, M, V etc. when screen is off). Other than that, the roms seems stable enough. (so are u planning to make r7f rom official on lineage os?)
In any case, keep up the good work and thanks for sharing this rom!
Click to expand...
Click to collapse
Thank you
Yeah I can't replicate the charging issue as well. I have 2 R7f's laying around.
VOOC is working fine on both of them with my 15.1 build. Drained them both multiple times and recharged.
Still haven't figured out what the deal is with tap 2 wake.
The r7f will never get official lineageOS builds sadly because of the weird USB-attached on (re)boot bootloop bug

The link for the OS takes me to something called mega.nz but nothing loads, then it times out.

MrFlibble23123 said:
The link for the OS takes me to something called mega.nz but nothing loads, then it times out.
Click to expand...
Click to collapse
This rom is not for the r7plusf.

kishd said:
This rom is not for the r7plusf.
Click to expand...
Click to collapse
Good job I couldnt download it then, I'd have been scratching my head. The official Lineage page has a 15.1 nightly build but I can't get WiFi working on the device using it so have gone with 14.1

Ravhinzy said:
do you know how to fix dt2w?
eg with flash module or update.zip to fix it.
I've been looking for ways on google how to fix it still has not worked.
I really hope to get this cusrom. fell in love when first tried it.
Click to expand...
Click to collapse
New release, tape 2 wake should be functioning correctly now (I have tested it)

[Guide][9.0 pie GSI] Install any android Pie gsi in Rosy

Easy to flash
*All required file below*
Steps to flash GSI:-
1.Flash treble recovery.
2.Wipe data,dalvik,system,vendor.
3.Download and flash latest LOS15.1 by murlidharan.
4.Download any "ARM64 Aonly" gsi file and flash it as system image.
5.Download and flash OpenGapps 9.0.
6.Reboot,and enjoy!!
ALL PIE GSI's HAVE SAME BUGS AS OREO
All required file
~Treble Recovery:- https://forum.xda-developers.com/redmi-5/development/official-batik-recovery-t3838833
~Link to download LOS 15.1:- https://forum.xda-developers.com/redmi-5/development/rom-lineage-os-15-1r46-xiaomi-redmi-5-t3849181
~All available PIE GSI:- https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
~Gapps 9.0:- https://opengapps.org
For updates join our telegram group:- @redmi5official

Does the camera and fingerprint work?

Which GSI image have you tried? There are only two which are A only.
Tried the Treble-ized 0s.
VolTE does not work.

N1ghtr08d said:
Does the camera and fingerprint work?
Click to expand...
Click to collapse
Camera working, FP for goodix not working.

finalmoksha said:
Which GSI image have you tried? There are only two which are A only.
Tried the Treble-ized 0s.
VolTE does not work.
Click to expand...
Click to collapse
A only available for all GSI's, I tried all gsi available and works smooth, I'm not using volte.

Anybody got a fix for the camera? I flashed the pixelized treble o image and everything seems to be working really well except I've no camera. It just keeps crashing

N1ghtr08d said:
Anybody got a fix for the camera? I flashed the pixelized treble o image and everything seems to be working really well except I've no camera. It just keeps crashing
Click to expand...
Click to collapse
Can you try another rom? If you can, do so and report back to see if camera is fixed. I tried Pixel Experience and camera works. I have tried some roms and so far no problems, but have not yet tried the one you have and I'm far from where my Rosy is.

drnoellyg said:
Can you try another rom? If you can, do so and report back to see if camera is fixed. I tried Pixel Experience and camera works. I have tried some roms and so far no problems, but have not yet tried the one you have and I'm far from where my Rosy is.
Click to expand...
Click to collapse
I installed open camera and it works just fine, however I just now realized that there's more than 2 A-only images. I was misreading the page and didn't notice that they all say (except for the 2 I noticed) A A/B so they all have an A-only image. I just downloaded the benzo ROM sand in flushing it now so I'll report back with results.

N1ghtr08d said:
I installed open camera and it works just fine, however I just now realized that there's more than 2 A-only images. I was misreading the page and didn't notice that they all say (except for the 2 I noticed) A A/B so they all have an A-only image. I just downloaded the benzo ROM sand in flushing it now so I'll report back with results.
Click to expand...
Click to collapse
Yeah I also thought at first there were only 2 available because it said A only. Which one are you trying next?

I tried Benzo and it wouldn't work properly out of the box because it has gapps pre installed and my device is not registered with Google for whatever the hell they want now with custom ROMs and gapps.
After that debacle I flashed Havoc OS and it's fantastic. Rock solid stable, fast, no graphic glitches like on the pixelized ROM, and the fingerprint is lightning fast and the camera works perfectly.

N1ghtr08d said:
I tried Benzo and it wouldn't work properly out of the box because it has gapps pre installed and my device is not registered with Google for whatever the hell they want now with custom ROMs and gapps.
After that debacle I flashed Havoc OS and it's fantastic. Rock solid stable, fast, no graphic glitches like on the pixelized ROM, and the fingerprint is lightning fast and the camera works perfectly.
Click to expand...
Click to collapse
Benzo didn't work? That one worked wonders for me. Pixel Experience also worked great for me. I'm glad you have now reached a ROM you like. Congratulations. Are you thinking of switching soon?

drnoellyg said:
Benzo didn't work? That one worked wonders for me. Pixel Experience also worked great for me. I'm glad you have now reached a ROM you like. Congratulations. Are you thinking of switching soon?
Click to expand...
Click to collapse
Actually you might be able to help me. I've tried to install Benzo, Arrow OS, and the pixel experience and they all start going crazy about the device but being registered with the Google framework id and I can't fix the issue. I've gone to the Google page to authorize the phone and I got my framework id and entered it but the phone never became authorized and therefore the roms were all useless to me.
Can you tell me what I'm doing wrong or how to correct this problem so I can try those roms?

N1ghtr08d said:
Actually you might be able to help me. I've tried to install Benzo, Arrow OS, and the pixel experience and they all start going crazy about the device but being registered with the Google framework id and I can't fix the issue. I've gone to the Google page to authorize the phone and I got my framework id and entered it but the phone never became authorized and therefore the roms were all useless to me.
Can you tell me what I'm doing wrong or how to correct this problem so I can try those roms?
Click to expand...
Click to collapse
You did as much as I did. I also went into the googlel page with my id and that fixed it. Are you on telegram? Join the official redmi5 group and ask there.

How did you get your id?

N1ghtr08d said:
How did you get your id?
Click to expand...
Click to collapse
I followed this guide:
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
Is this the problem you're having?

Thanks, I forgot to report back. That worked for me but the problem I have is that there's a big with Bluetooth audio in that I can hear music no problem but I can't get any phonecall audio through Bluetooth and this problem is apparent across any pie ROMs so I had to go back to 8.1

Moved from stable miui to android pie and its a great exp thanks to the good people hard work
But i dont know why the colors on the aosp rom in so washed compared to the stock rom
If there is something i can do to get the normal colors back plz tell me
---------- Post added at 02:21 AM ---------- Previous post was at 02:13 AM ----------
There is also two bugs i hope u can help me with them
1- a red colored border shows then disappear
2-settings force close when i try to enter the battery section

For the first bug you can check under developer options if strict mode is enabled. If it is, disable it and see if it fixes it.

can someone help me plz??
I tried havoc gsi in this process
also tried two different gsi's..
after flashing system.img when I boot
it boots to bootloader and not in system.
I can't figure out the problem

Working GSI ROMs on Mi Note 10 Lite / toco

As the title says, here's a list of some GSI's i have tested so far... but first for some story.
Bought the phone in summer, it's quite nice but has its own issues like no kernel source BUT since we can unlock the device and actually play around, oh boy it has been fun.
On the course of few hours and many downloads later I have a small list of GSI's that worked!
Every GSI I have mentioned REQUIRE device specific patch(es)!!!
For that you have to root.
----------------------WORKING GSI's-------------------------
BlissROM - It boots and functions quite fast
Cons: no included Gapps
Flashing any system editing patch results in "Phone is booting" homescreen.
https://sourceforge.net/projects/treblerom/files/BLESS/2020.09.21/
3.5 jack, VoLTE, Bluetooth, ComboFix patches are required, flash with Magisk manager
DO NOT USE FixLagSmooth
HavocOS 3.7 and 3.6 - Work and can be daily driven
3.6 requires FixLagSmooth patch
MUST root and apply all linked patches (don't use FixLagSmooth on 3.7, you can but no need)
https://forum.xda-developers.com/mi...rom-how-to-install-android-10-gsi-mi-t4126223
AOSP Android 10 based - Also does work and requires patching
https://forum.xda-developers.com/mi...rom-how-to-install-android-10-gsi-mi-t4126223
HydrogenOS Android 10 - Works
Has few bugs
No Google services
https://mirrors.lolinet.com/firmware/gsi/HydrogenOS/
----------------------COMMUNITY REPORTED GSI's-------------------------
Android 11 GSI - Reported to be functional by HumptyPotato47, thanks mate!
No Gapps as of now NikGapps exist for Android 11, search XDA for it!
Requires more testing...
https://github.com/phhusson/treble_experimentations/releases/tag/v300.f
----------------------MAYBE WORKING GSI's-------------------------
OxygenOS 10 GSI - Seems to work.. sorta
First boot after exiting fastboot causes the phone to reboot
Second boot will loop
https://mirrors.lolinet.com/firmware/gsi/OxygenOS/
----------------------NON FUNCTIONAL GSI's-------------------------
You tell me
...I did find a very nice list of GSI ROMs to try out more, here's the link:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
----------------------FLASHING GSI-------------------------
If you test one then don't hesitate with replying which one, about the experience, bugs and how you installed it.
My method of installing was this:
1. Make sure to have the new adb commandline that supports fastbootd mode
2. Drop the GSI .img file in /adb directory for ease
3. Make sure you're running MIUI with unlocked bootloader and USB debugging enabled
3.5 MAKE SURE you get a GSI ROM with Gapps as existing TWRP isn't fully functional
4. GSI you should have must be AB partition!!!​
Once all set then follow the next commands
>adb reboot bootloader
>fastboot -w
>fastboot reboot fastboot
>fastboot erase system
>fastboot flash system "GSI-ROM-name-without-quotes".img
>fastboot reboot bootloader
>fastboot reboot​
----------------------SETTING UP GSI-------------------------
Once all that is complete it should boot, if not then that specific GSI does not work.
Also a thing worth mentioning! Whenever I boot this phone to fastbootd Windows keeps forgetting what driver it was which requires
few extra clicks in device manager to set it up for fastbootd use. Including an image with simple to follow instructions if you have the same issue.
>fastboot boot twrp.img
Once in TWRP you should be able to access internal storage with your computer, drag Magisk.zip over and flash. Don't forget to wipe cache!
If it boots normally then root was successful, now apply the linked patch and reboot once again. Since we are playing with GSI:
Head to Settings
Find Phh Treble Settings
Misc features
Check Disable audio effect. -- DISABLE IT AFTER PATCHING!!!​
IMPORTANT!!! I only tested Havoc and Bliss for a long period, IF one of my mentioned GSI's or others require more patches then I have linked headphone jack and Bluetooth audio patches too.
Combo fix should do the trick thought so your mileage may vary.
----------------------HELP US-------------------------
IF you find more working GSI's then tell us and I will make sure to add them to the main post so it won't get clogged under other comments!

Update on 05.10.2020 GMT+3
Bliss ROM GSI
As only a day or two have passed I already encountered few issues.
> You cannot remove screenshot sounds, even when fully muted
> Data drain is something interesting I've noticed, consumption compared to MIUI is higher.
> When using the gesture navigation it is a bit buggy when using quick side swipe for multitasking.
Positive notes!
> It is stupid fast
> Battery life is good
> GCam is amazing
> 99% of the customization options work perfectly
> Fast charging modes and such work perfectly
Neutral stuff...
> No FOD, thanks for closed source
> whenever you take a picture or a screenshot and have Blutetooth audio connected, it pauses and plays out loud via speaker. No music leaks out

this phone is born dead, no developer cares about it.

alsartawi said:
this phone is born dead, no developer cares about it.
Click to expand...
Click to collapse
Sad truth but won't stop others from working on it. Eventually we might get a kernel source

Kevin Soosaar said:
Sad truth but won't stop others from working on it. Eventually we might get a kernel source
Click to expand...
Click to collapse
i would pay to see a stable custom rom for this phone, i really loved it.

alsartawi said:
i would pay to see a stable custom rom for this phone, I really loved it.
Click to expand...
Click to collapse
Havoc OS and Bliss ROM are both quite stable, albeit with Bliss you don't get Gapps which is a huge bummer to most users.
Personally I just installed MicroG services and use Aurora store with anonymous "account".
When I tried to flash Gapps with TWRP I ended up soft bricking ROM so it was required to restore stock and try again. Of course there's no need if you can still use fastbootd.

Kevin Soosaar said:
Havoc OS and Bliss ROM are both quite stable, albeit with Bliss you don't get Gapps which is a huge bummer to most users.
Personally I just installed MicroG services and use Aurora store with anonymous "account".
When I tried to flash Gapps with TWRP I ended up soft bricking ROM so it was required to restore stock and try again. Of course there's no need if you can still use fastbootd.
Click to expand...
Click to collapse
does FOD works on Havoc OS?
edit: sorry i just read that it's not working.

alsartawi said:
does FOD works on Havoc OS?
Click to expand...
Click to collapse
FOD is not working as the driver sources are not public, reverse engineering is not possible too afaik. Everything else works.

Should i send this phone back to Amazon?
Seriously, last night i bought it, thinking about to install some custom rom, but if there are no developers caring of it, i might returb the phone to the seller...

IMO MIUI EU is better then GSI roms. Everything works. Got rid of most chinese crap. You can use Magisk.
Have nice features (MIUI in general). The only thing i dont like -mine turns on WIFI byitself dotn know how it happens... but it happens when i sleep. china collecting logs?
https://www.scmp.com/abacus/tech/ar...earch-and-browsing-data-china-researcher-says

afigienas said:
IMO MIUI EU is better then GSI roms. Everything works. Got rid of most chinese crap. You can use Magisk.
Have nice features (MIUI in general). The only thing i dont like -mine turns on WIFI byitself dotn know how it happens... but it happens when i sleep. china collecting logs?
https://www.scmp.com/abacus/tech/ar...earch-and-browsing-data-china-researcher-says
Click to expand...
Click to collapse
Literally the main reason I made this post is to help others who are interested to use GSI ROM's on their devices. I do agree that MIUI has some decent features and I did use Xiaomu.eu before but it was so buggy. In the end I love customizing the device however I like it so MIUI is just not for me. Either way I might try to negotiate with Amazon to get a refund as touch and Bluetooth problems still persist. Fun fact, on Bliss the edge detection is pretty good and not as aggressive or straight out bad.

Simon_19 said:
Seriously, last night i bought it, thinking about to install some custom rom, but if there are no developers caring of it, i might returb the phone to the seller...
Click to expand...
Click to collapse
Actually there are plenty of people ready to build ROMs for Toco (Mi Note 10 Lite) and Tucana (Mi Note 10) but there just isn't any kernel source available. Making things worse is the cancelled release of Toco in India and we know that they are one of the biggest Android ROM builders next to Russians. No one there is gonna import a device like this because better phones for money exist. If you don't like it then yeah I recommend returning otherwise give GSI a try for now and see what happens.
You won't lose warranty as there is no E-fuse like on Samsung phones so locking bootloader and flashing back to stock is enough.

Is anyone try oos gsi ?

HumptyPotato47 said:
Android 11 GSI of phh is working fine. It is very smooth. But i switched back to miui because i can't find any android 11 gapps.
Click to expand...
Click to collapse
can you give the link of the rom?

HumptyPotato47 said:
Android 11 GSI of phh is working fine. It is very smooth. But i switched back to miui because i can't find any android 11 gapps.
Click to expand...
Click to collapse
Hi, there are gapps for Android 11, look for NikGapps here in XDA

Kevin Soosaar said:
Actually there are plenty of people ready to build ROMs for Toco (Mi Note 10 Lite) and Tucana (Mi Note 10) but there just isn't any kernel source available. Making things worse is the cancelled release of Toco in India and we know that they are one of the biggest Android ROM builders next to Russians. No one there is gonna import a device like this because better phones for money exist. If you don't like it then yeah I recommend returning otherwise give GSI a try for now and see what happens.
You won't lose warranty as there is no E-fuse like on Samsung phones so locking bootloader and flashing back to stock is enough.
Click to expand...
Click to collapse
who said its cancelled?

Dr. DoubtReaper said:
who said its cancelled?
Click to expand...
Click to collapse
The mentioned Mi Note 10 Lite for India was supposed to be called Mi 10i or something like that. It quickly disappeared and is not happening.
Of course I might be wrong by this date but looking for now there is no 10i, only speculation videos and threads.
Mi Note 10 Lite for India would've been code named "tocoin", same hardware and everything else so just a rebadge in old Xiaomi fashion... :laugh:

anyone tried new version of blissROM? feedback?

GaryFisher88 said:
anyone tried new version of blissROM? feedback?
Click to expand...
Click to collapse
Not sure if the one I linked is up do date, give it a try yourself as my device went in for warranty repairs.

Hello, I am currently using Xiaomi.eu based on MIUI 12 and I would like to know how to flash HAVOC OS GSI. Should I flash back to Global Rom then flash the GSI as indicated? Answer is greatly appreciated.