Related
Just found out that I have a Mi Mix waiting for me when I get home. I've made a checklist of what I want to do to it to get it setup for my use. I wanted to know if anyone had anything to add or has done any of what I'm planning on.
Unlock Bootloader
This should be relatively simple. I already have my unlock permission and will be using the directions from here: http://en.miui.com/thread-202290-1-1.html
As far as I can tell by reading that thread, I do not need to install the developer ROM first. Is this correct?
I will also follow the top reply to this thread which mentions linking your device to your Mi account before unlocking to prevent errors: https://m.reddit.com/r/Xiaomi/comments/5co8t1/mi_unlock_approval/
Install TWRP
My plan is to follow these instructions: http://forum.xda-developers.com/mi-mix/development/recovery-official-twrp-xiaomi-mi-mix-t3498960
This is where I start having questions. I've been out of the rooting and ROMing game for a couple of years. Does anyone recommend rooting with anything other than SuperSU? I'm reading that it was bought by a Chinese company and shouldn't be trusted. I've also read that using Magisk you can have root that is easily turned off. I'll admit I'm pretty lost at the moment when it comes to what Magisk does and how to use it. But if it is the recommended way of doing things I will do the research to learn it.
Flash The EU ROM
I think my plan is to flash this EU ROM which debloats everything and seems to come with gapps and a lot of other nice optimizations: https://xiaomi.eu/community/threads/6-11-10.36056/
My first question is has anyone tried this?
My second question is will I need to reinstall TWRP and re-root? I think I will have to re-TWRP because on the TWRP page there is one version for stock and one for the EU version. I will be on stock first and I can't flash EU until after I flash TWRP. So I think the procedure will have to be:
Flash stock TWRP
Flash EU ROM
Flash EU TWRP
Re-Root?
Turn Off All Battery Optimizations
Don't have a guide for this yet but I'm guessing it's not hard to find. Feel free to reply with one if you have one.
Personalize
Launchers/Themes/Icon Packs/etc. Don't need suggestions here since I already know what I have in mind.
Anything else?
The only other thing I can think of that I might want to install is Xposed. I've never used it and don't know how to install it but I'll learn if I can be convinced that it's something I want.
What else am I missing?
I think right now the biggest thing I'm curious about is if anyone has used the EU ROM and what the procedure is if you use that ROM since there are 2 different versions of TWRP for the Mi Mix. But any other suggestions on what to do with the initial setup or how to make my experience better are welcome. I'd also love to hear about any "gotchas" that aren't mentioned in the guides from people who have actually done it.
Well I took the plunge without waiting for feedback and for anyone who is interested, I'll answer my own questions. Read the posts that I linked in the OP to understand what I'm doing below. I will not cover how to get unlock permission as this has been covered elsewhere.
Unlock Bootloader
As far as I can tell by reading that thread, I do not need to install the developer ROM first. Is this correct?
Click to expand...
Click to collapse
This is not correct. You must install the Dev ROM and connect to WiFi and follow the steps to enable Developer options and login to your Mi account in developer options.
Install TWRP
Before installing TWRP you must update back to the stable ROM. The non-EU version of TWRP will not work with the Dev ROM as of this posting. You can update to the stable ROM using the same steps as updating to the developer ROM. In the TWRP install guide I linked above, I stopped right after step 6 and continued below.
Flash the EU ROM
Instead of flashing SuperSU after installing TWRP, I copied over the EU ROM linked above and flashed that. Then I followed the instructions starting from step 3 of this post to flash SuperSU, Magisk, and suhide: https://www.reddit.com/r/pokemongod...k_v7_systemless_xposed_v866_released/d8d7ziw/
The only change I made is that in between steps 4 and 5, I flashed the EU version of TWRP before continuing because otherwise the touchscreen would not work in TWRP. I used the most recent versions for the SuperSU, Magisk, and suhide and I did not flash Xposed yet but I believe I can do that in the future if I want to.
That's where I'm at now. The rest of my checklist was mostly personal preference so I won't go into that. Hope this helps.
@chimera533
THX for taking the plunge & sharing your results with us.
I'm sure I'll be doing the same once mine arrives, hope you don't mind if I look this way if I have any questions regarding TWRP/Root/etc.....
Thank you for posting this, this is the exact list of what I will be doing when my Mi Mix comes in the mail (C'mon Ibuygou).
I couldn't seem to find a EU rom for Mi mix though it is listed in the thread as a supported drive. Will you please drop me the link to download? Thank you.
jim380 said:
I couldn't seem to find a EU rom for Mi mix though it is listed in the thread as a supported drive. Will you please drop me the link to download? Thank you.
Click to expand...
Click to collapse
I think I got mine from here: https://megadysk.pl/f/6.11.10
Just scroll down to the Mi Mix one.
There are 3 repositories to the 6.11.10 weekly ROMs at the top of the page here: https://xiaomi.eu/community/threads/6-11-10.36056/
As far as I know there are no stable EU builds for the Mi Mix probably because it's so new.
Also I believe the weekly updates show up here: https://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/
The Mi Mix was skipped for 6.11.17 as evidenced by the note at the top of the 6.11.17 thread.
That's about all I know. I highly recommend reading all or most of every link I posted here. I'll confess that if I had, I would've known things like having to flash back to stable before TWRP-ing as well as some other things.
It would be nice if you did an edit of your original post, rather than a 'by the way' post below it. It would be much easier to follow the instructions.
I've installed TWRP on multiple phones. The dm-verity stuff is new to me (A xiaomi/MIUI thing I guess),
so the sequence appears to be:
install Official MIUI China developer ROM
<unlock>
install Official stable rom
install Official (Non-EU) TWRP (requires stable)
copy/install EU ROM after step 6 (aka before exiting TWRP)
< Do you reboot now and go back into fastload now? or stay inside TWRP? >
Install EU TWRP
install supersu (again, before you exit TWRP?)
Install Magisk, suhide?
Apologies but I'm away from home at the moment. I'll update the OP with more detail when I have a bit more time. But I'll give you some quick answers below.
install Official MIUI China developer ROM
Remember to log in to your Mi account in the developer options
<unlock>
install Official stable rom
install Official (Non-EU) TWRP (requires stable)
copy/install EU ROM after step 6 (aka before exiting TWRP)
While still in TWRP, install SuperSU in systemless mode.
Boot to system once
Boot back to fastboot and install EU TWRP
Boot to TWRP and install Magisk, suhide
Boot to system and install magisk manager
Got the Mi Mix 128GB overpriced in Thailand, but without any waiting time.
Love your early thread, very helpful.
I also want to get twrp, suhide, magisk and xposed, but I like to stay on the Chinese Dev or official ROM, not xiaomi.eu, because I like the paid themes which are only available on official ROMs.
I've got a MIUI developer account for 4 years, so I can unlock the device directly, being on stable ROM.
Now the steps are a bit unclear for me. Do I understand them correctly?
1. Unlock bootloader
Download and install the developer rom: http://en.miui.com/download-317.html
Create/Login with your MI Account on the device.
Apply for unlocking the bootloader here: http://en.miui.com/unlock/
Install stable ROM if desired
2. Install official TWRP (NON-EU)
Boot into fastboot mode by turning off your device then pressing volume up and power button
Install Minimal ADB and Fastboot on your PC: http://forum.xda-developers.com/showthread.php?t=2317790
Download the correct TWRP image file: https://dl.twrp.me/lithium/twrp-3.0.2-0-lithium.img.html
Copy the twrp file to where minimal adb and fastboot has been installed and rename the twrp file to twrp.img
Open fastboot on your computer and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
3. Install SuperSU in systemless mode
Download newest SuperSU: https://play.google.com/store/apps/details?id=eu.chainfire.supersu / http://download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip
In ADB shell or TWRP shell, type
Code:
echo SYSTEMLESS=true > /data/.supersu
if you don't already have this file to configure SuperSU to install in systemless mode.
Flash SuperSU.
4. Boot to system
5. Boot into TWRP, install Magisk, suhide, Xposed
suhide: http://forum.xda-developers.com/apps/supersu/suhide-t3450396
systemless xposed 86.2: http://forum.xda-developers.com/attachment.php?attachmentid=3897543&d=1475913773
magisk: http://tiny.cc/latestmagisk
6. Boot to system and install Magistk Manager
magisk manager: http://tiny.cc/latestmanager
7. Install XPosed
chimera533 said:
I think I got mine from here: https://megadysk.pl/f/6.11.10
Just scroll down to the Mi Mix one.
There are 3 repositories to the 6.11.10 weekly ROMs at the top of the page here: https://xiaomi.eu/community/threads/6-11-10.36056/
As far as I know there are no stable EU builds for the Mi Mix probably because it's so new.
Also I believe the weekly updates show up here: https://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/
The Mi Mix was skipped for 6.11.17 as evidenced by the note at the top of the 6.11.17 thread.
That's about all I know. I highly recommend reading all or most of every link I posted here. I'll confess that if I had, I would've known things like having to flash back to stable before TWRP-ing as well as some other things.
Click to expand...
Click to collapse
Thank you so much for your help. I installed the ROM and have had it running for 2 days now. Coming from a HTC 10 (custom ROMed and everything), I;m really not digging MIUI on this phone. Lags so much it's literally driving me crazy. My 2 yrs old LG G2, which also has amazing screen-to-body ratio btw, runs circle around this phone. Really disappointed about this phone due to the software performance issues.
jim380 said:
Thank you so much for your help. I installed the ROM and have had it running for 2 days now. Coming from a HTC 10 (custom ROMed and everything), I;m really not digging MIUI on this phone. Lags so much it's literally driving me crazy. My 2 yrs old LG G2, which also has amazing screen-to-body ratio btw, runs circle around this phone. Really disappointed about this phone due to the software performance issues.
Click to expand...
Click to collapse
I don't experience any lags on the original ROM.
From my experience those micro-lags and performance issuese showed up on various devices in my Android past whenever something was wrong with the ROM. A clean flash mostly helped solve the problem.
I'm currently on the original Chinese stable with SuperSu and TWRP. It's blazing fast. What's the reason to flash the xiaomi.eu rom?
underlines said:
I don't experience any lags on the original ROM.
From my experience those micro-lags and performance issuese showed up on various devices in my Android past whenever something was wrong with the ROM. A clean flash mostly helped solve the problem.
I'm currently on the original Chinese stable with SuperSu and TWRP. It's blazing fast. What's the reason to flash the xiaomi.eu rom?
Click to expand...
Click to collapse
I had a nightmare trying to get to the EU Rom yesterday, I was mostly successful, however after a reboot i'd lose Touch in both TWRP and System. Thanks to this post from Chimera533 I was finally able to do it!
Anyway the main reason for the EU ROM is to get rid of all the Bloat and Chinese throughout the ROM that you cannot get rid of. It also has Google Services baked in properly so everything works correctly.
I also had a few other little niggles while on the Chinese ROM :-
Purchases from Google Play Movies wouldn't work
No Smart Lock while connected to Android Wear
No way to replace BAIDU and set Google as the search
So far i'm loving the EU Rom, i've not seen any lag at all while using it and pretty much everything seems to work exactly as it should - it has enhanced the MIX experience so much for me - love this thing!
Guys, how do I disable all battery saving optimizations / memory management optimzations? My background apps keep shutting automatically off after a while.
I'm on the default ROM without root (still waiting for developer approval)...
yakuzlin said:
Guys, how do I disable all battery saving optimizations / memory management optimzations? My background apps keep shutting automatically off after a while.
I'm on the default ROM without root (still waiting for developer approval)...
Click to expand...
Click to collapse
Go to the battery section & have a look around, you should find several settings for battery management.
You're gonna need root & an app such as Titanium Backup Pro, or, SD Maid Pro to disable a lot of the MIUI & Cheetah Mobile applications.
Fine tuning on a per app basis isn't enough (do not optimize battery savings for the apps you want to work properly, notifications, messaging, etc) .....
I highly recommend flashing the EU ROM, it seems to have better memory management than the Global ROM, but, you'll still need to disable a lot of the MIUI apps & all of the Cheetah Mobile s***ware to get memory management more to what you're used to experiencing.
One other item, go to Developer Options & disable MIUI Optimization, it should be the last item or close to it....
Hi all after trying hundreds of different roms on my old nexus. I think i have found the best way to boost the speed. I'm using xenonhd 5.1.1 with parrot mod and M-kernels. ??
Trying it out right now and it seems snappy. But I am using f2fs version of Xenonhd without the M kernel.
Give the xenonhd please...
Links please
GrandLuLu said:
Give the xenonhd please...
Click to expand...
Click to collapse
Sab3elbromba said:
Links please
Click to expand...
Click to collapse
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
"Lightning fast" and "Nexus 7 2012" are not normally used in the same sentence.
Maybe I'll have to give this a try. I've kept mine on stock KitKat, and it's dog slow.
Are you using SuperSU as recommended by ParrotMod, or does it work with Magisk? Thanks.
Edit: To answer my own question, it seems to work fine with Magisk.
so, you have to downgrade the bootloader to use this?
beside that, in the xenonhd thread someone said .. after u install some apps you'll get the same slow down like on every other rom
https://forum.xda-developers.com/showpost.php?p=69949425&postcount=1817
I just got myself a new Nexus 7 and all i've done is run the updates up to 5.1 as 5.1.1 fails to install.
It is pretty slow and crashes a lot, I don't remember it being this laggy and slow when I first got one in 2012. Is it just a function of the new OS's or the new apps? What is the best build to be in for speed? I don't mind losing some of the newer features of the OS. Would just prefer something I can use without being frustrated...
Thanks
Sorry to ask this, but can the nexus 7 2012 roms be used on a nexus 7 3g 2012? are they the same? I am new to this model, I am about to buy one (just as ereader), but would like to have the best rom on it.
jbaumert said:
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
Click to expand...
Click to collapse
The latest version update-XenonHD-09-13-15 is not available anymore. If anyone that has the files could share.
I was also pointed to try this rom: https://forum.xda-developers.com/nexus-7/development/rom-android-7-aosp-grouper-t3467514
And this one, but again no working links https://forum.xda-developers.com/showthread.php?t=2784244
I will buy today a Nexus 7 3G 2012 very cheap, so I will try some roms on it.
skinniezinho said:
Sorry to ask this, but can the nexus 7 2012 roms be used on a nexus 7 3g 2012? are they the same? I am new to this model, I am about to buy one (just as ereader), but would like to have the best rom on it.
Click to expand...
Click to collapse
To use a "Grouper" ROM on the "Tilapia / 3g" device, you just need to flash the Grouper ver of TWRP recovery. Granted, you will not have use of the 3g radio, but otherwise it will function normally.
jbaumert said:
To use a "Grouper" ROM on the "Tilapia / 3g" device, you just need to flash the Grouper ver of TWRP recovery. Granted, you will not have use of the 3g radio, but otherwise it will function normally.
Click to expand...
Click to collapse
Thanks. The device comes with 4.2.2 should I flash first 5.1.1 (in order to update radios and stuff) and then root=>recovery=>rom? Or should I just root it in 4.2.2?
If anyone have the older files that I pointed I would appreciate, I will test them and leave my feedback.
I would download the last "official" update from Google for your device (Tilapia I'm assuming), and manually flash the radio and bootloader with fastboot. (Granted, you could install the entire update, but why bother if you're going to put on a custom ROM anyways) Then, unlock the bootloader (if not already done) install TWRP recovery and flash away.
Anyone tested this ROM yet (with a bunch of apps installed to see if slows down or not) ?
jbaumert said:
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
Click to expand...
Click to collapse
The download links are dead. :crying:
Jaguar10301 said:
I just got myself a new Nexus 7 and all i've done is run the updates up to 5.1 as 5.1.1 fails to install.
It is pretty slow and crashes a lot, I don't remember it being this laggy and slow when I first got one in 2012. Is it just a function of the new OS's or the new apps? What is the best build to be in for speed? I don't mind losing some of the newer features of the OS. Would just prefer something I can use without being frustrated...
Thanks
Click to expand...
Click to collapse
Root it and load RootBooster and choose the last option..
andynroid said:
Root it and load RootBooster and choose the last option..
Click to expand...
Click to collapse
I have a 2012 Nexus 7 running Resurrection Remix M (Android 6.0.1), and I can say that RootBooster *does* help. My N7 was *very* laggy and slow to respond when tapping on anything. I chose "Basic Mode -- Speed", re-booted and it's a LOT faster now. Time will tell if it lasts.
I've had MultiROM and TWRP on this tablet for quite awhile, so I also have RR-N installed as a secondary ROM. I'm going to try RootBooster on that ROM also.
I have a Nexus 7 2012 wifi model and need it strictly for Chromecast audio to control Pandora and Spotify.
What's the best rom for that?
Don't care for anything else really...
I installed the setup mentioned by the OP on my Nexus 7 2012, and it is working well so far. Thank you OP.
Initially I tried to use the kernel that is included with the XenonHD ROM, but it seemed to have issues with lag, not waking from sleep, etc. Then I switched to M Kernel and it was much better, so switching the kernel is necessary in my opinion.
Links:
Main XenonHD thread:
https://forum.xda-developers.com/showthread.php?t=1826484
XenonHD download:
The main download link in post #2 of the above thread doesn't seem to contain the download anymore. But if you go to the "Older builds" link, you can find the 08-20-15 build there. Here is a direct link.
https://androidfilehost.com/?fid=24052804347797659
M kernel:
I used the latest a77 version available from the main M Kernel thread here:
https://forum.xda-developers.com/showthread.php?p=38551156
ParrotMod:
I used the universal version available from the main ParrotMod thread here.
https://forum.xda-developers.com/ne...arrotmod-speed-2012-nexus-7-emmc-fix-t3300416
GApps:
I used the "nano" version from Open GApps:
http://opengapps.org/
Magisk:
Main thread and downloads here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
My Procedure:
I was starting with stock rooted Android 4.4.4. I had previously used the WugFresh toolkit to root and install twrp. If you have something older or custom, you may need to flash a recent stock rom first to update your bootloader.
1) Update to current version of twrp. I used the twrp app from the play store.
2) Boot into twrp. Factory reset.
3) Boot into Android.
4) Download XenonHD, M Kernel, ParrotMod, and GApps files to PC, transfer to tablet via USB. (or download on tablet)
5) Boot into twrp. Wipe everything except internal storage.
6) Install XenonHD, M Kernel, ParrotMod, GApps
7) Boot into Android. Be patient, first boot takes a while
I also replaced SuperSU with Magisk, because I don't consider recent non-Chainfire versions of SuperSU to be trustworthy. To do this:
1) Download Magisk and Magisk Manager to PC, transfer to tablet via USB. (or download on tablet)
2) Open SuperSU settings, select option to uninstall and prepare for alternate su manager.
3) Reboot to TWRP. Flash Magisk. Wipe cache/davlik (not sure this is necessary). Reboot to Android. IMPORTANT: If twrp says device does not appear to be rooted and prompts you to install SuperSU, you must decline.
4) In Android, install Magisk manager.
Hope this helps someone else.
spocko said:
I installed the setup mentioned by the OP on my Nexus 7 2012, and it is working well so far. Thank you OP.
Initially I tried to use the kernel that is included with the XenonHD ROM, but it seemed to have issues with lag, not waking from sleep, etc. Then I switched to M Kernel and it was much better, so switching the kernel is necessary in my opinion.
Links:
Main XenonHD thread:
https://forum.xda-developers.com/showthread.php?t=1826484
XenonHD download:
The main download link in post #2 of the above thread doesn't seem to contain the download anymore. But if you go to the "Older builds" link, you can find the 08-20-15 build there. Here is a direct link.
https://androidfilehost.com/?fid=24052804347797659
M kernel:
I used the latest a77 version available from the main M Kernel thread here:
https://forum.xda-developers.com/showthread.php?p=38551156
ParrotMod:
I used the universal version available from the main ParrotMod thread here.
https://forum.xda-developers.com/ne...arrotmod-speed-2012-nexus-7-emmc-fix-t3300416
GApps:
I used the "nano" version from Open GApps:
http://opengapps.org/
Magisk:
Main thread and downloads here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
My Procedure:
I was starting with stock rooted Android 4.4.4. I had previously used the WugFresh toolkit to root and install twrp. If you have something older or custom, you may need to flash a recent stock rom first to update your bootloader.
1) Update to current version of twrp. I used the twrp app from the play store.
2) Boot into twrp. Factory reset.
3) Boot into Android.
4) Download XenonHD, M Kernel, ParrotMod, and GApps files to PC, transfer to tablet via USB. (or download on tablet)
5) Boot into twrp. Wipe everything except internal storage.
6) Install XenonHD, M Kernel, ParrotMod, GApps
7) Boot into Android. Be patient, first boot takes a while
I also replaced SuperSU with Magisk, because I don't consider recent non-Chainfire versions of SuperSU to be trustworthy. To do this:
1) Download Magisk and Magisk Manager to PC, transfer to tablet via USB. (or download on tablet)
2) Open SuperSU settings, select option to uninstall and prepare for alternate su manager.
3) Reboot to TWRP. Flash Magisk. Wipe cache/davlik (not sure this is necessary). Reboot to Android. IMPORTANT: If twrp says device does not appear to be rooted and prompts you to install SuperSU, you must decline.
4) In Android, install Magisk manager.
Hope this helps someone else.
Click to expand...
Click to collapse
The Gapps don't seem to fit on the standard storrage anymore. Did you enlarge the system storage?
Nevermind, found what I didn wrong. Thanks for your post where you gather all the info
Strormrage said:
The Gapps don't seem to fit on the standard storrage anymore. Did you enlarge the system storage?
Nevermind, found what I didn wrong. Thanks for your post where you gather all the info
Click to expand...
Click to collapse
What was it in your case?
Introduction
This is aimed to be a complete but simple guide for users which want to know what works in the Treble-World on the Mate 10 Pro and 'how to get there', based on other guides and my own findings
Disclaimer: I am not responsible for what you do with your device, you are free, probably old enough to know what you are doing and intelligent enough to read this through.
For the moment I will only speak about my own tests on a BLA L29 as I don't have the possibility to test everything.
Feel free to share your own discoveries via PM (just reuse the same formatting to make things easy)
Requirement
1. PC/Laptop running Windows 10 with adb and fastboot drivers installed
2. Original Huawei USB Type-C Cable
3. Being able to read and use search when a question arises
Summary
0. General Information
I. Unlock the Bootloader
II. Choose your ROM (a.k.a "What works on what")
III. Install your ROM
IV. Miscellaneous / Secondary stuff
V. Bonus : What to do if I am stuck / Bootlooping
0. General Information
To make things easier for everybody, here are some basic informations about your device and some common knowledge :
How do I get in Download / Bootloader / Fastboot Mode ?
Shut down your device, insert your USB cable. Keep the Volume DOWN button pressed and press the Power button, wait.
PRO TIPP : You may also get there from within android, first enable ADB debugging in developer options, then, on your PC open a command prompt and type "adb reboot-bootloader"
How do I get in Recovery Mode ?
While in Download / Bootloader / Fastboot Mode, take the USB cable out, keep the Volume UP button pressed and press the Power button until the phone reboots.
I. Unlock the Bootloader
We allready have a thread by @otonieru perfectly discussing this point, don't forget the Windows 10 fix :
https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535
II. Choose your ROM (a.k.a "What works on what")
This section isn't complete and should be detailed with time. None of these ROMs is specific for the Mate 10 Pro, but thanks to Treble, most images will work. Device-specific modifications are still needed in future, ask your local dev
1. Generic AOSP (Android 8.0 and 8.1) by Phhusson
Link : https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Description : Really basic ROM (basically pure AOSP) which serves as a basis for most of the other ROMs.
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk, Signal strength is reported incorrectly, error message at each start, Play Store tends to hang (solution : wipe the Play Store from recents or force close it)
Actual status : Barebones, can be customized in some ways with overlays.
2. LineageOS 15.1 (Android 8.1) by LuK1337
Link : https://forum.xda-developers.com/honor-view-10/development/rom-lineageos-15-1-t3753000
Description : If you don't know LineageOS, you should have heard about CyanogenMod (CM). This is a super clean, customizable version of Android, based on AOSP
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk (system crashes), Signal strength is reported incorrectly,
root works thanks to addon-su (see Miscellaneous)
Actual status : Working as a daily driver (at least in my case) if you can live with some very small drawbacks.
III. Install your ROM
Once you have unlocked your Bootloader and chosen the ROM your heart desires follow these steps :
1. BACK UP YOUR DATA ! -> You will certainly have to do a factory reset and backing up data should be something natural when flashing something on your phone, even before updates.
2. Download the ROM (latest is probably best, but it's best to read what is said in the respective threads before jumping in the hole.
3. Reboot to the Download / Bootloader / Fastboot Mode (see above)
4. Flash the ROM by opening a command prompt and typing :
Code:
fastboot flash system system.img
where "system.img" is the filename of the ROM you downloaded
5. Reboot the phone by typing :
Code:
fastboot reboot
6. The phone will probably get in a bootloop. Don't panic. This should be normal.
After 4-5 reboot the phone will go in Recovery mode. Make a Factory Reset
7. Reboot
8. Profit
IV. Miscellaneous / Device-Specific stuff
This is probably the more interesting part as it is quite hard to find the correct information for our device concerning these points.
Root
ROMs as Lineage don't come prerooted. To root your phone the only viable solution seems to be addon-su for the moment.
To install you will need to install TWRP (follow the instructions in this link by @Dees_Troy : https://forum.xda-developers.com/mate-10/development/recovery-twrp-3-2-1-0-touch-recovery-t3752399 ), boot to TWRP (same as booting to Recovery, as TWRP is the new Recovery). go to advanced -> adb sideload. Connect your phone to your PC and flash the file using
Code:
adb sideload addonsu-15.1-arm64.zip
finally reboot, go to 'developer options' and chose the desired option under 'root options'. Done.
Camera
When flashing a ROM it will probably come with the stock AOSP or Lineage camera which, just say it, sucks on our device form a quality point of view. Here are the answers found to this problem for the moment. Sadly, there isn't one solution which works for everything and everyone.
Google Camera - GCam
Photos work - Gallery works - Videos don't work
Right now his is probably the best compromise if you want something that works, easy to install, while not wanting every little gimmick (in that case you should probably stay on EMUI - The definition of gimmick). Simply install the apk.
Note : there are probably other versions of GCam that work or will work in future, feel free to inform me / us about better working versions.
Link : https://drive.google.com/file/d/1Rw2lXtSHvOUalpA8YKg_kW2Xj_Gu746M/view
More information / discussion :
https://forum.xda-developers.com/mate-10/help/gcam-mod-mate-10-t3729078
Camera Port from the Mate 9 - needs root
Photos work - Videos don't work - Gallery doesn't work - Most filters and gimmicks work
A bit more complicated to install. The easiest way found for now is to root first using addon-su and then copy the system folder inside this zip into the respective folders using a root enables explorer like solid explorer
Link : https://mega.nz/#!7hQDhQAK!p2s7jQp9-nhp2-O1U2s2GrBB9UVBhgKDtFfHTq_CHvI
More information / discussion : https://forum.xda-developers.com/pr...huawei-stock-camera-app-treble-roms-t3735169/
V. Bonus : What to do if I am stuck / Bootlooping
Remember when I said to back up ? Well I hope you did, because if you are really bootlooped and a reflash of the system image hasn't helped. you will have to reflash the whole device, which isn't quick.
Gladly @mankindtv has got you covered with his great guide : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I hope I could help a bit. Feel free to add your own findings, simply PM me.
Credits -
@otonieru for the great Bootloader unlocking thread
@phhusson for his many efforts to make Treble awesome
@LuK1337 for his many efforts to get things working on the Lineage side as well as for addon-su
@Dees_Troy for his awesome work on TWRP
@mankindtw for his great guide on recovering from the loops of boots
reserved
It's gonna be one of the most helpful threads for the novices.
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
If possible, please add how to go back to stock rom in simplified form.
mdjishadk said:
It's gonna be one of the most helpful threads for the novices.
Click to expand...
Click to collapse
I have lost three days to get out of bootloops and gather the info... I hope nobody else will have to live the same thing (and maybe this can become a dedicated thread to fix the last missing blocks to have a complete experience)
good job
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
good job on this one OP btw, video on mate 9 camera port is only broken on 8.1, on 8.0 all camera features work fine except opening of the picture from the camera app itself
Good job man!
Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It might be android 8.1. It worked fine for me when using 20180225 version, didn't test later ones.
What version are you on?
Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It crashed everything on my 8.1 build (and the developer himself recommended me addon-su) maybe a tad harder to use, but at least you learn something at the same time
You should add that the stereo speakers don't work.
Timate5 said:
You should add that the stereo speakers don't work.
Click to expand...
Click to collapse
"Stereo"... When coming from a Nexus 6P this Sally doesn't sound stereo at all... But you're right !
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
timo.helfer said:
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
Click to expand...
Click to collapse
That's too bad, android auto uses h264 streaming codec I think. I think this issue will have something to do with hardware acceleration. Have you tried messing around with the acceleration option found in the developer options to see if it might work?
Nice guide! Thank you @ChriKn!
Can you add to the "Generic AOSP (Android 8.0 and 8.1) by Phhusson"'s part that we need to use A-ONLY version of this rom?
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
ChriKn said:
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
Click to expand...
Click to collapse
Sure i can write some impressions. I just installed Carbon ROM.
I did flash but is not booting at all.
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
triconix555 said:
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
Click to expand...
Click to collapse
Let it Bootloop until it goes to erecovery and than factory reset it
Timate5 said:
Let it Bootloop until it goes to erecovery and than factory reset it
Click to expand...
Click to collapse
I did that but it is just boolooping again, I did all tge steos over and over and it just bootloops every tipe even after factory resete, it actualy asked le once to resete since then after a couole of reboots it goes straight to te erecovery, wherz it ask to login on a wifi to download latest bootloader and rom or reboot or shutdown device...
Note:- Credits To this guide goes to {Diablosss}
GUIDE FOR UNLOCKING BOOTLOADER OF MEIZU PRO 7
(Sorry for the inconvenience, but there are some issues in posting pictures. Therefore requesting you to please check the attached files for images)
This guide can also work with many other Meizu devices. Checked on 15, 16 all options (s, t, x) and on Pro7I post the archive and instructions in pictures.
Step 1: Download. Unpack. Run meizublunlocker.exe
meizublunlocker:-https://drive.google.com/open?id=1yEm_vZo4rsqEtii279AU6l1mBajiSPQ2
See Image 1 in Attachments.
Step 2:-We connect the phone to the computer in fastboot mode (hold down the Vol. Down and power buttons), click refresh. The program must identify the device.
See Image 2 in Attachments.
Step 3ress CheckBL to check bootloader status.
See Image 3 in Attachments.
Step 4:-Click the Create Request button. This will create a file with the end of req.dat in the folder with this program
We send it to the e-mail [email protected] and wait for the response file to unlock the bootloader.
(This takes usually 1 week to receive the unlocked file, but you can donate to get the file within 3 hours)
See Image 4 in Attachments.
Step 5:- After we received the unlock file with the end of res.dat, click UnlockBL and select the resulting file.
See Image 5 in Attachments.
If the file is correct then get this answer
See Image 6 in Attachments.
That's It. We successfully Unlocked the Bootloader.
Now the next thing is to install the TWRP in our Device. ( Further credits goes to{ sergpolov} )
Step 1: Download and install "adb_run"
adb run:-https://drive.google.com/open?id=1y4wdL53-P7mybKsj5XeimHRoMSpokMkQ
Step 2:- Download the required Files.
Stock Recovery Pro 7:-https://drive.google.com/open?id=1e2tRdqLi5jsT8J854RMcIA-jvZyR7xhT
Twrp Pro 7:-https://drive.google.com/open?id=1uYOT9HGractYuoJvRidgAgh8IBLhzFtu
Step 3:-We load the phone into fastboot mode, flash through the fastboot the recovery you need.
Launch the application shortcut
Step 4:-Click "3" - go to fastboot mode
See Image 7 in Attachments.
Step 5:-Click "3" - recovery
See Image 8 in Attachments.
Step 6:-Here we select the recovery file: - in the window that opens, we throw the file itself and close the window with the file and press any button.
See Image 9 in Attachments.
The process has begun.
See Image 10 in Attachments.
Step 7:- Choose "Y" and "Enter"
See Image 11 in Attachments.
The recovery firmware process is over!
Next Few Steps are Extremely Important , so follow with caution!Step 8:-Reboot into Recovery Mode(hold down "Power" and hold, as soon as the screen goes blank, hold down the second button "Volume +" - hold it until vibration and release "Power", and after it release the button "Volume +")
Step 9:-To disable encryption of the "Data" section (who installs TWRP), we immediately flash the zip archive - tool-root_unlock-Testing-Pro7.zip
(disables encryption of the "Data" section, disables Boot and Recovery checks, installs Magisk and disables system root) and reboot into the system.)
tool-root_unlock-Testing-Pro7.zip:-https://drive.google.com/open?id=1a3Gyyuoo2Jv3EN7EWPwj389tXorSwkxT
Attention ! When installing custom recovery (TWRP) on your device, for the full TWRP functionality, you should format the internal memory (Data section) of the device using TWRP itself, since the "Data" section on Meizu smartphones is encrypted, I highly recommend it before installing custom recovery , on creating backups using the internal Flyme firmware (after creating the backup, it is located in the "backup" folder of the internal drive), as well as copying all the necessary data from the phone’s internal memory to the computer!
NOTE:-No One shall be responsible to any damage ocurring to your device
Doubts and queries are welcomed .
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
XRed_CubeX said:
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
Click to expand...
Click to collapse
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
adityadhage said:
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
Click to expand...
Click to collapse
But then for other MTKs like M5C it will never work?
XRed_CubeX said:
But then for other MTKs like M5C it will never work?
Click to expand...
Click to collapse
i know you have already tried this method with your device and it didnt worked. I am not sure that m5c will get another method in future or not. Bcoz we also got lucky with pro 7 that it got successful by the help of guide ported from Meizu 16TH a Qualcomm device.
its now per donation only.
spiramedia said:
its now per donation only.
Click to expand...
Click to collapse
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
cris2d2 said:
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
Click to expand...
Click to collapse
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
adityadhage said:
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
Click to expand...
Click to collapse
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
cris2d2 said:
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
Click to expand...
Click to collapse
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
adityadhage said:
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
Click to expand...
Click to collapse
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
cris2d2 said:
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
Click to expand...
Click to collapse
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
adityadhage said:
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
Click to expand...
Click to collapse
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
cris2d2 said:
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
Click to expand...
Click to collapse
basically you are right
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
deathbreath2010 said:
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
Click to expand...
Click to collapse
this guide is now updated and guranteed to work with x30 also
follow this
https://www.youtube.com/watch?v=Rnuf-uNBnYA&t=319s
adityadhage said:
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
Click to expand...
Click to collapse
its not 5$ its now 15$ its too mutch
sajib_ngage said:
its not 5$ its now 15$ its too mutch
Click to expand...
Click to collapse
try asking them for lower price, they will help u i think. Tell them its for pro 7 bcoz pro 7 requires less work. try ur luck
This thread is how I have managed to upgrade a Samsung S5 with Android 6.01 to LineageOS 16 with a Mac laptop running Sierra, in an attempt to keep on using it with my car infortaintment system.
First of all it's important to leave very clear 2 things:
ALL THIS INSTRUCTIONS APPLY TO A SAMSUNG S5 SM-G900F kltexx device. I don't know how it will work in any other device . This is what has worked for me and I'm sharing this with you all just hoping that will be useful for someone else.
YOU ARE THE SOLE RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE.
So let's get started.
Prepare your system:
You must have the Samsung USB drivers installed (I used the latest ones from Samsung - https://developer.samsung.com/mobile/android-usb-driver.html).
You need to allow your device to debug it using the USB. Instructions here: https://androidcure.com/enable-usb-debugging-samsung-galaxy-s5/
You need to install adb in your computer. The easiest way to do it is this one: https://www.cyanogenmods.org/minimal-adb-and-fastboot-windows/ although another option would be to install Android SDK platform tools, but thats much heavier (https://developer.android.com/studio/releases/platform-tools). Usually the first option is enough.
You need to ensure that your Samsung will always trust your computer. So connect your Samsung with your computer and when it asks if your computer can be trusted, make sure that you click on the checkbox with the option "Always".
ODIN:
You need to install a Recovery System in your device and for that you will need ODIN which is a tool created by Samsung to flash files to Samsung devices. It has a version for Mac which has worked for me. Go to this site to learn how to use it and to download it: https://macmetric.com/odin-for-mac/ or you can right jump to this site (https://forum.xda-developers.com/devdb/project/dl/?id=20803) to just download the version that worked for me.
ROOT : (Optional)
By default your device has the bootloader unlocked. This was something that drove me crazy as I couldn't find anywhere to show me if it was. I ended up rooting my device to confirm that it was unlocked and also to confirm the real name of my device. So it's almost 100% certain that your Samsung S5 has the bootloader unlocked, but in case you want to confirm it, as I did, follow the instructions from this thread https://forum.xda-developers.com/showthread.php?t=2696537.
Basically, I ended up on this page, CF-Auto-Root homepage
http://autoroot.chainfire.eu/ downloading the file to root my device from there and flashing it with JOdin. Keep in mind that you might think that your device is version klte and there are at least 5 klte: kltedx, kltexx, kltezh, klteduosxx and kltejv. Mine ended up being kltexx
In my case I followed the process described in that thread and tried to root my device with the file for kltedx and it didn't wok out. Then I tried again with the file for kltexx and it worked. That's how I discovered that mine was kltexx.
TWRP :
You need to install a custom recovery system to your Samsung S5 device to be able to flash the LineageOS ROM. This site has the instructions that I followed to install it: https://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/
It is extremely important to highlight that the latest version of TWRP didn't work for me. I installed the latest one and everything seemed to be OK but it was not. I couldn't flash any ROM with it. I ended up discovering that for my case, the best option was to install an older version. To be more precise, version 3.0.2.2 (https://eu.dl.twrp.me/klte/twrp-3.0.2-2-klte.img.tar.html).
To make sure that you have been able to install TWRP do the following. There are 3 ways to boot your Samsung S5: Normal boot, Download mode (ODIN) and Recovery mode. We need to start up on recovery Mode and see a screen menu similar to the one we've seen in the previous thread (https://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/).
To do so, start the device on Recovery mode:
For the Normal mode you just click the Power Up key and wait. No magic here.
For the Download mode you have to switch off your device and then click at the same time the Power Up key, the Volumen Down key and Home key. It comes with the standard installation, so no magic here either.
Home Key
For the Recovery mode, you have to switch off your device and then click at the same time Power Up key, Volumen Up key and Home key. After a couple of seconds, the screen will say at the top "Recovery option..." and you should be able to see the touch screen menu of TWRP.
Flashing LineageOS 16 :
This is suppose to be an easy step but it ended up being very complicated because my device name was not properly being exposed by my device. So I ended up modifying the installation script to ensure it didn't matter.
So, you have to download not only the LineageOS version but also some other packages like Google apps, that are not installed and that you will need, and also the rooting package, which is always handy.
So the instructions and the links to download the packages are here. You might go there, read them and download all the packages: https://wiki.lineageos.org/devices/klte/install under the section Installing from Recovery....
Once you have all the packages ready to install, before you follow their instructions, you will have to do some hacking that you will find here explained here: http://www.lineageosdownloads.com/fix-error-7-lineage-os/ under section METHOD 1: UPDATER SCRIPT HACK TO FIX ERROR 7.
Basically, what I did was to edit the zip file using vim editor from the command line. You type "vim lineage-16.0-20200726-nightly-klte-signed.zip" (being lineage-16.0-20200726-nightly-klte-signed.zipand the name of the lineageOS image) and then go to "META-INF/com/google/android/updater-script" and then edit the file removing all the lines where it has any reference to the device name which are usually the first lines of the script containing the getprop(...) lines of code. To remove them, just click "dd" and they will be removed. Once they are removed, click on "Esc". Then type ":wq", it will go back to the previous screen, and then click ":q" and taht will be it, you have the package ready to be installed.
Now follow the instructions that you read previously and you should be able to have your Samsung S5 updated to LineageOS 16.
And now comes the part that I haven't resolved yet. How to install Mirrorlink in this device. So far I have managed to get several version of the Driverlink APK from Samsung but I'm not able to install them because when I try to do it using adb in root mode, I get the following message: "Package com.sec.android.automotive.drivelink has no signatures that match those in shared user android.uid.phone; ignoring!".
I know it has something to do with the signatures of LineageOS and that I need to sign the APK file with the LineageOS ROM signatures, but so far I haven't been able to find how to do it.
So I'll keep on trying and posting my discoveries here. Anyway, if anyone is willing to help me, it will be very welcome!!
I really hope that this helps others to take back from the closet their forgotten Samsung S5 and put it back to work.
I dont think it would help even if u did manage to install mirrorlink as samsung did drop support for mirrorlink.
Mirrorlink needs a new security certificate from samsung every month, and last certificate works until 2020-07-31
guroth said:
I dont think it would help even if u did manage to install mirrorlink as samsung did drop support for mirrorlink.
Mirrorlink needs a new security certificate from samsung every month, and last certificate works until 2020-07-31
Click to expand...
Click to collapse
I'm still working on it. Anyway, the certificate is not a problem. Once I have mirrorlink working, I will install some applications that will install the certificate (like RockScout - "https://play.google.com/store/apps/details?id=com.carconnectivity.mlmediaplayer&hl=en_US") or LG Mirrorlink. And with them I will use other apps to take control of the screen like for example Full Mirror for Mirrorlink - "https://play.google.com/store/apps/details?id=full.mirrorlink&hl=en_US"
The main challenge is to be able to create the connection between the cellphone and the car.
There is a button "Translation" in notification bar in LOS, that is a mirrorlink by itself if I do understand this correctly. But klte SM-G900F on LOS 17.1 and lentislte SM-G906S on LOS 16.0 doesn't discover a mirrorlink device that is working properly with Samsung A50 on stock ROM (Anydata device, Windows 10 PC). One day I have managed to establish a mirrorlink connection between A50 (it was a transmittor) and SM-G900F (receiver) via some (can't recall it's name) app. But still I haven't managed to use S5 as a transmittor for mirrorlink...