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)
Related
Now with LineageOS 14.1 Nougat
builds
sources (github) PATCHES STRONGLY ENCOURAGED
local_manifests for building
current branch is cm-14.1 (LineageOS 14.1 with Linux 3.10.x)
Instructions:
Unlock bootloader
Flash TWRP from kugo/twrp/recovery.img or from https://forum.xda-developers.com/x-compact/development/recovery-twrp-t3522249
Do not use AndroPlus's, it does not handle /system writing very well (in my experience)
Do not use my recovery build for stock, it does not handle /data encryption
Flash zip in recovery
SELinux: Permissive (I haven't updated the sepolicy in a while, enforcing makes the camera panic which causes bootloop. I may fix this later.)
Lineage 14.1
WORKING:
WiFi
Data/Cellular (you may want to jot down APN settings from stock before flashing)
Fingerprint reader (a bit unreliable, will fail sometimes)
FMRadio
Camera
NOT WORKING:
AudioFX (the built in equalizer thing; just disable it from the apps menu)
SELinux (sepolicy needs update)
Bluetooth (system seems to crash when turning it off)
Whatever isn't working in AOSP/Omnirom (e.g. in-call volume control)
UNTESTED:
NFC (it turns on, but I have no NFC devices)
Keep in mind that I am not really a developer but will do what I can to help with issues
Special thanks to the Sony-Kitakami team for serving as a base to port changes from suzuran/kitakami to kugo/loire
Additional thanks to humberos for porting omnirom to kugo and serving as a base to port to kugo
...and thanks to Sony for allowing us to unlock our bootloaders and for porting AOSP to their phones (unlike some other manufacturers)
Recent Changes:
Rebased device trees off of omnirom trees, updated everything
I'll go first and say thank you for developing for this device.
Hope that this encourages other devs to build their ROMs too.
Great job! :good:
Nice
as soon as audio playback is fixed i will flash and try to post logcats !
A little love for the XC
Keep up with the good work! Now that TA backup is also possible, it's just a matter of fixes until this is good to go!
ardylemon said:
Keep up with the good work! Now that TA backup is also possible, it's just a matter of fixes until this is good to go!
Click to expand...
Click to collapse
Not to mention greater adoption of ROM flashing now that we have a way to get back to stock.
thanks for the update!
Looking forward to testing cm14.1. Has anyone already flashed it and can give some feedback and impressions?
Micka84 said:
Looking forward to testing cm14.1. Has anyone already flashed it and can give some feedback and impressions?
Click to expand...
Click to collapse
I would go with cm-13.0 honestly unless bluetooth is that important (which is next on the to-do list for cm-13).
CM-14.1 is pretty incomplete upstream, so it's missing some features (like theming).
It's also still running the marshmallow kernel, so things like vulkan probably won't work either, and
I don't plan on releasing a build with the nougat kernel until we at least get prebuilts for it.
howdid said:
as soon as audio playback is fixed i will flash and try to post logcats !
Click to expand...
Click to collapse
Audio playback should be "fixed" now, for both 13 and 14.1
How is camera quality and battery life?
Looking for a little bit of clarification. After unlocking the bootloader, what is the process for installing TWRP? Does it require a modified boot.img to boot recovery as outlined in AndroPlus's thread? Thanks.
ammarr said:
Looking for a little bit of clarification. After unlocking the bootloader, what is the process for installing TWRP? Does it require a modified boot.img to boot recovery as outlined in AndroPlus's thread? Thanks.
Click to expand...
Click to collapse
I don't think I ever needed to flash a modified boot.img, so just flash recovery in fastboot, power off the phone, and then boot into it with volup+power
If for some reason that doesn't work, you can flash AndroPlus's boot.img and try again
tlxxxsracer said:
How is camera quality and battery life?
Click to expand...
Click to collapse
I can't really comment on the camera (it seems fine to me, but that isn't my area of expertise), but the battery is admittedly not where I want it to be after disabling audio offloading and rolling back the kernel for bluetooth.
Kind of waiting for CM-14.1 to be more ready to fix both of those
EliWallace said:
I don't think I ever needed to flash a modified boot.img, so just flash recovery in fastboot, power off the phone, and then boot into it with volup+power
If for some reason that doesn't work, you can flash AndroPlus's boot.img and try again
I can't really comment on the camera (it seems fine to me, but that isn't my area of expertise), but the battery is admittedly not where I want it to be after disabling audio offloading and rolling back the kernel for bluetooth.
Kind of waiting for CM-14.1 to be more ready to fix both of those
Click to expand...
Click to collapse
Thanks for the reply and for bringing CM to the XC.
Comparatively how much worse is the battery life compared to stock? Obviously depends on usage but are you still able to make it through the day?
ammarr said:
Thanks for the reply and for bringing CM to the XC.
Comparatively how much worse is the battery life compared to stock? Obviously depends on usage but are you still able to make it through the day?
Click to expand...
Click to collapse
It was enough to get through a day, but I would end up with 30-50% instead of 60-75% (I have mail checking constantly, so that was a big drain)
Thats in comparison to a CM build with a newer kernel and audio offloading not disabled,
I haven't used stock at all so I don't know how the battery life is on it
Why not use an existing msm8956 tree for kenzo and hydrogen and make Sony additions to a car kernel source and boot cm. It will bring much lesser issues.
Rom looks good!
But I only have 2 problems:
1) I have a changing mac adress. Every time I reboot my device, I get another mac adress. It always starts with 00:90:4c but the remaining part changes.
I found some solutions on google, but nevertheless they didn't work... Maybe because the solution is not for X compact or CM 13/14.1....
2) The phone doesn't charge when I connect it to the wall socket. Just for half a second the led turned yellow, but after that it stops charging. The cable and battery are fine (I went to stock and it charges immediately).
Hopefully does anybody have a solution or idea how I could fix these problems!
NL_henk said:
Rom looks good!
But I only have 2 problems:
1) I have a changing mac adress. Every time I reboot my device, I get another mac adress. It always starts with 00:90:4c but the remaining part changes.
I found some solutions on google, but nevertheless they didn't work... Maybe because the solution is not for X compact or CM 13/14.1....
2) The phone doesn't charge when I connect it to the wall socket. Just for half a second the led turned yellow, but after that it stops charging. The cable and battery are fine (I went to stock and it charges immediately).
Hopefully does anybody have a solution or idea how I could fix these problems!
Click to expand...
Click to collapse
I think it has something to do with the kernel. Could someone let me know which kernel-version is used?
NL_henk said:
I think it has something to do with the kernel. Could someone let me know which kernel-version is used?
Click to expand...
Click to collapse
I also noticed that the mobile does not charge however at the laptop over USB load it
Ps. i use not Costum Kernel
Present you with a 7.1 .1 Nougat AOSP!
Tested on E6853, released a build for Dual E6883 "NOT TESTED" try at your own risk
Install trough ADB as usual by flashing boot.img system img and userdata.img
(detailed how to in post no.2)
Note:
If you are updating from previous release, flash only system.img if you wanna keep your userdata (you will only loose gapps)
This is pure AOSP.
have tried most of it and everything has been working fine.
Improvments from 7.0:
Camera is working (Not inverted anymore)
Fingerprint is working
Auto brightness works as intended
Known bugs:
AC 5GHz wifi might not work for all.
Fingerprint might bug out for some people.
Download Here
GApps
(Use arm64 7.1)
Updated 2017-04-14
AOSP 7.1.1 rev 38
Cheers
XDA:DevDB Information
AOSP 7.1.*, ROM for the Sony Xperia Z5 Premium
Contributors
Elfmirth
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: _r7
Stable Release Date: 2016-12-18
Created 2016-12-14
Last Updated 2017-04-17
Reserved
How to:
In the ADB folder press shift key and right klick with your mouse, choose "Open Command prompt here"
Power off your phone, once it's off, press and hold volume key up, and plugg it in to your PC, now the indicator on the phone sould turn blue, that shows that the phone is in Fastboot mode.
(Check in your device manager that the sony fastboot drivers are installed)
when all that is done, in the command promt type:
Code:
fastboot flash boot "drag and drop the boot.img file"
when that is done type:
Code:
fastboot flash system "drag and drop the system.img file"
after that:
Code:
fastboot flash recovery "drag and drop the recovery.img file"
when all is done type:
Code:
fastboot reboot
and your phone will reboot, it might take longer than usual.
If you wanna install gapps and root READ!! and follow this to boot up TWRP.
When phone is booted up, turn it off again enter fastboot mode then:
1.
Code:
fastboot [U]boot[/U] TWRP.img
2. On your phone press volume up until you see that you're booting in to TWRP
Thanks a lot! I've been meaning to try building this myself. Thanks for giving me hope again for the Z5P!
e6833
thank you.
is it working for z5p Dual?
faraheed said:
thank you.
is it working for z5p Dual?
Click to expand...
Click to collapse
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend ?
e6833
Elfmirth said:
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend
Click to expand...
Click to collapse
thank you my friend, can i try it on my e6833?
faraheed said:
thank you my friend, can i try it on my e6833?
Click to expand...
Click to collapse
Ofc you can try, but to be safe wait until I have made a proper build for it ?
e6683能用吗，或者说e6653
I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.
Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!
WannaB101 said:
Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!
Click to expand...
Click to collapse
The speed will improve over time, the first 2-3 hours and 2-3 reboots mine was a bit laggy to, but after installing pixel launcher and playing around for a few hours there is no lag at all and it's just as fast as my HTC 10 (if not faster)
FC on SU I havent had, but then again only used it for 3-4 apps but worked fine with those.
The asop.zip was a typo on my end, have removed it now (was a little to tired)
exvargos said:
I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.
Click to expand...
Click to collapse
"Edit" I tried a couple of times now and the only issue I had was cus of bad reception. But then again I dont have AC router only N 5GHz
WannaB101 said:
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
Click to expand...
Click to collapse
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.
It's a lot better than the current 6.0.1 ROM I was previously using. RAM usage was cut down by half, battery life is pretty phenomenal and everything is butter smooth. I had some camera issues in the past where the z5p could never focus on anything.
All fixed with AOSP 7.1, making it my daily driver
Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?
KbaB.BroS said:
Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?
Click to expand...
Click to collapse
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
exvargos said:
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.
Click to expand...
Click to collapse
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)
Elfmirth said:
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)
Click to expand...
Click to collapse
Battery life is much better than Sony stock ROM and everything based on it, easily lasts me one day which is what I need. Light usage keeps the phone alive for more than two days.
@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.
KbaB.BroS said:
@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.
Click to expand...
Click to collapse
The first FW I started out flashing from was 32.1.A.1.163. Then I flashed AOSP 7.0 and after that AOSP 7.1
OP Updated with rev7 for both e6853 & e6883
enjoy
Hi Elfmirth,
Thanks for your work.
Hope you keep support for the dual sim devices too. Thanks
Best Regards,
Ashray
Elfmirth said:
OP Updated with rev7 for both e6853 & e6883
enjoy
Click to expand...
Click to collapse
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.
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.
I've tested 3 GSI images with my phone last weekend, here are the results:
--------------------------------------------------------------------------------------------------------------------------------------------------------------
1. PixelExperience: https://forum.xda-developers.com/poco-f1/how-to/treble-pixel-experience-9-0-t3839681
or here: https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
- Everything work well
- Feel faster than stock, no mi nonsense
- Wifi and data work fine
- Sound: OK
- Camera: work
- Bug: NO DARK MODE, it went black, and never come back.
- Ugly: the notification bar is not so compatible with curve screen, the clock and battery percentage almost got cut-off
- I might do something wrong, but my bank app said the phone is rooted. So, I have to flash stock back.
2. LineageOS: https://forum.xda-developers.com/pr...vice-development/9-0-lineage-os-16-0-t3840801
- There is this "privacy protection" error pop-up all the time
- Booted, run smooth
- Wifi and data work fine
- Sound and camera work.
- LineageOS handles the top and bottom curve better than PixelExp, the notification bar look better
- Some setting features were not working and follow with error, but the phone still work normally after error message
- I really hope the Lineage team get it work really soon. :good:
3. HavocOS: https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
- Bootloop...end
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Step
1. Unlock bootloader
2. Flash TWRP
3. With adb tool, flash system image (I've tried to flash PixelExp system image with TWRP, and got to bootloop, so I've changed to flash with adb command)
4. With TWRP flash decrypt
5. With TWRP wipe cache/dalvick
5. With TWRP format data
6. With TWRP flash decrypt again
Is there any way to flash PixelExperience without root?
PS. When I wrote that the camera work: I mean it works you can take a picture with both front and back cameras, but I didn't compare the picture quality at all.
Just tested Aosp Extended and I'll take the template you posted in the OP so it's easier for you.
AEX post: https://forum.xda-developers.com/pr...device-development/rom-aosp-extended-t3821934
- Rebooted itself a few times during the first boot.
- Felt sluggish during the first minutes, but then everything went smooth as butter.
- Wifi and data work fine
- Sound: OK
- Camera: work, but worse quality than stock
- Bug: NO DARK MODE, it went black, and never come back. In order to fix this you need to reflash the image
- Ugly: the notification bar is not so compatible with curve screen, the clock and battery percentage almost got cut-off. However you can almost fix it changing the display size, not a perfect fix but better than stock.
I'll be going to MIUI stock again, even though I hate it
Thanks for your feedback, you will save us a lot of time!
So, so far, you haven't found any GSI that handle completely properly the notch and curves of our screen?
I dont have any cut off on pixel experience after couple of reboots
Tomatot- said:
Thanks for your feedback, you will save us a lot of time!
So, so far, you haven't found any GSI that handle completely properly the notch and curves of our screen?
Click to expand...
Click to collapse
LineageOS handle the notch almost perfect, however, with other bug.
tomhtg90 said:
I dont have any cut off on pixel experience after couple of reboots
Click to expand...
Click to collapse
It looks nice indeed! Thanks, I'll give it a try.
tomhtg90 said:
I dont have any cut off on pixel experience after couple of reboots
Click to expand...
Click to collapse
For me, the time and battery percentage are closer to the edge than yours.
Also, is it root? Can we flash without root?
Thanks.
kikoarl said:
Just tested Aosp Extended and I'll take the template you posted in the OP so it's easier for you.
AEX post: https://forum.xda-developers.com/pr...device-development/rom-aosp-extended-t3821934
- Rebooted itself a few times during the first boot.
- Felt sluggish during the first minutes, but then everything went smooth as butter.
- Wifi and data work fine
- Sound: OK
- Camera: work, but worse quality than stock
- Bug: NO DARK MODE, it went black, and never come back. In order to fix this you need to reflash the image
- Ugly: the notification bar is not so compatible with curve screen, the clock and battery percentage almost got cut-off. However you can almost fix it changing the display size, not a perfect fix but better than stock.
I'll be going to MIUI stock again, even though I hate it
Click to expand...
Click to collapse
I, personally don't have any preferred template.
It seems as if the AEX is more or less on par with the PixelEx.
Can you manage to flash it without root?
I can live with a bit ugly notification and some minor bug, but I need to use the bank app. So I want to flash it without root.
I tested RR v6.1 GSI and it works with 2 intolerable bugs.
1, 3.5mm headphone not works. Speaker still works when haedphone plug in.
2, since the notch removed by command 'wm size 1080x2074' (result:here), screenshots will add black frame on the top and bottom, and the original contents(1080x2274) are zipped into 1080x1902, so it looks a liitle strange
RR GSI post: gsi-resurrection-remix-o-6-1-0-t3811299
Flashed arm64 a only 0818 version.
- root(magisk 17.1) and xposed v90 beta3 work.
- Wifi and data(CMCC) work
- Sound: both speakers work
- Camera: work
- Bug: headphone not work , screenshot problem
although i hate MIUI , i have to return to it . i need 3.5mm. looking foward to lineage 15.1 or aosp, etc.
I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.
Daruwalla said:
I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.
Click to expand...
Click to collapse
I could answer that...easily...maybe
I hate MIUI.
I hate ads full rom.
I have high hope for the project treble, it's a good starting point for generic device rom.
I don't know about your development of the lineageos, this is the first post I saw this information.
Also, it's fun to try something, even not perfect, it's still fun to mess around.
Daruwalla said:
I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.
Click to expand...
Click to collapse
Thanks for the great news. And do you mind telling that you ve been watching the development where exactly?
Thanks once again.
Tried 9.0 roms
1 Treblized os: very smooth and stable VOLTE problem.
2 Pixel experience: Smooth but thermal throttling is broken hearts up quite bit.
3 lineage os: doens't look as good as PE and yeah no VOLTE is any GSI 9 or 8.1
4 Arrow os: The best of all. Fast snappy.
5 Havoc os: Bootloop tried everything.
Tried 8.1 roms:
1 Arrow os: The best I must say. PUBG experience is great the touch is really snappy and accurate for some reason.
2 RR official: Has some weird issue maybe sound don't remember.
3RR unofficial: there were 2 unofficial builds one booted fine and the other got Bootloop. Sound was good in unofficial and boot animation is better.
4 Aquarius os: Simple and good.
5 Dot os: well I've tried this GSI on my OP5T it was amazing but in Poco it doesn't feel as stable as others.
After trying all these GSI roms the best stable snappy and thermal friendly ROM was 8.1 and 9 Arrow os.
Like if I helped you.
$hivaM Manav said:
Tried 9.0 roms
1 Treblized os: very smooth and stable VOLTE problem.
2 Pixel experience: Smooth but thermal throttling is broken hearts up quite bit.
3 lineage os: doens't look as good as PE and yeah no VOLTE is any GSI 9 or 8.1
4 Arrow os: The best of all. Fast snappy.
5 Havoc os: Bootloop tried everything.
Tried 8.1 roms:
1 Arrow os: The best I must say. PUBG experience is great the touch is really snappy and accurate for some reason.
2 RR official: Has some weird issue maybe sound don't remember.
3RR unofficial: there were 2 unofficial builds one booted fine and the other got Bootloop. Sound was good in unofficial and boot animation is better.
4 Aquarius os: Simple and good.
5 Dot os: well I've tried this GSI on my OP5T it was amazing but in Poco it doesn't feel as stable as others.
After trying all these GSI roms the best stable snappy and thermal friendly ROM was 8.1 and 9 Arrow os.
Like if I helped you.
Click to expand...
Click to collapse
Wow, arrow os was not on my tested list. :good:
Need to try it asap.
Just question: can I flash it without root status?
Adios2nd said:
Wow, arrow os was not on my tested list. :good:
Need to try it asap.
Just question: can I flash it without root status?
Click to expand...
Click to collapse
Well I'm not sure because I flashed root on every GSI because my device feels uncomplete without it but I'm sure you won't have any problem with no root and yeah in some GSI roms we have option to download with gapps/su/ or vanilla
Edit:
I needed root access because I used this universal notch fix
Go to terminal give root access and type
"wm overscan 0,90,0,0" this completely pushes the notification panel below the notch and fits perfectly!
$hivaM Manav said:
Well I'm not sure because I flashed root on every GSI because my device feels uncomplete without it but I'm sure you won't have any problem with no root and yeah in some GSI roms we have option to download with gapps/su/ or vanilla
Edit:
I needed root access because I used this universal notch fix
Go to terminal give root access and type
"wm overscan 0,90,0,0" this completely pushes the notification panel below the notch and fits perfectly!
Click to expand...
Click to collapse
2 Questions
1. I didn't intend to flash root, but when I flashed the "Encryption disabler" (that every guides suggest to flash, see attached), it became root itself. Can I not flash it?
2. Do I need to fix the notch in ArrowOS, is it not detect and adjust by itself?
Adios2nd said:
2 Questions
1. I didn't intend to flash root, but when I flashed the "Encryption disabler" (that every guides suggest to flash, see attached), it became root itself. Can I not flash it?
2. Do I need to fix the notch in ArrowOS, is it not detect and adjust by itself?
Click to expand...
Click to collapse
1. The encryption disabler is only for MIUI roms because it encrypts your data on first boot but GSI roms don't encrypt your data so you can skip flashing that after flashing GSI
2. Only Pie roms have the ability to adjust to notch currently this feature is not available in 8.1 roms so it'll look weird.
The notch situation is a bit better in Lineage 9.0.
In every ROM, ir unlock doesn't work (as expected), and volte doesn't work (expected?!).
All cameras work well.
---------- Post added at 05:14 PM ---------- Previous post was at 05:14 PM ----------
Daruwalla said:
I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.
Click to expand...
Click to collapse
mind posting the link?
$hivaM Manav said:
1. The encryption disabler is only for MIUI roms because it encrypts your data on first boot but GSI roms don't encrypt your data so you can skip flashing that after flashing GSI
2. Only Pie roms have the ability to adjust to notch currently this feature is not available in 8.1 roms so it'll look weird.
Click to expand...
Click to collapse
I'm a very beginner so to flash without root:
0. Unlock bootloader
1. Flash recovery TWRP
2. In TWRP flash encryption disabler
3. Wipe (normal wipe?)
4. Reboot to recovery (Do I need this step?)
5. Flash GSI
6. Then reboot to system
Am I right?
Thanks for your answer.
PS.
If I flash the GSI with adb fastboot, do I need to flash the encryption disabler?
(In fastboot, I do the "fastboot flash system GSI.img")
Adios2nd said:
I'm a very beginner so to flash without root:
0. Unlock bootloader
1. Flash recovery TWRP
2. In TWRP flash encryption disabler
3. Wipe (normal wipe?)
4. Reboot to recovery (Do I need this step?)
5. Flash GSI
6. Then reboot to system
Am I right?
Thanks for your answer.
Click to expand...
Click to collapse
One-time process:
1. UL bootloader.
2. Flash twrp.
3. Format user data for twrp dycript then reboot to recovery again without booting to os.
4. Flash encryption disabler boot once to os.
After this process you don't have to flash the encryption file again and again because it modifies your vendor partition for treble enable. You'll have to flash this file again after flashing any MIUI rom. If you need root in GSI you can flash this file or you can skip.