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 There,
I've the Problem that I havent't TWRP-Recovery and SuperSu after Updating to OOS 4.1.1 and Android 7.1.1.
Do someone know if i had to flash TWRP with qiping all Data? Or is there a Way to Flash TWRP and SuperSu without wiping? =(
Sorry I'm new to Android and started with the oneplus 3t. So i didn't know that i hadn't to update the Phone.
Or is the best opinion for me to choose a custom rom? But there are so much, i don't know what to choose.
Thanks for help! =)
Neither TWRP nor SuperSU will wipe anything.
It's totally up to you whether you need a custom ROM or not. If you want features like switching tracks just with your volume keys, you'll totally need a custom ROM since stock ones don't provide this feature. But this is just one example of many.
Regards.
Sent from my OnePlus 3T using Tapatalk
Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
I'll try my best today evening, hopefully nothing will go wrong :-O
What do I need to center the clock?
I'll flash trwp and supersu and anything to center the clock today evening.
Don't know if I need a custom rom, are there reason for a custom rom?
Thank you so much!
m4l4g4 said:
Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
I'll try my best today evening, hopefully nothing will go wrong :-O
What do I need to center the clock?
I'll flash trwp and supersu and anything to center the clock today evening.
Don't know if I need a custom rom, are there reason for a custom rom?
Thank you so much!
Click to expand...
Click to collapse
If you need help with anything, just ask.
I never had to wipe anything. I just wipe the phone when I want to remove the encryption.
EDIT: regular security patches is one big reason for me to install a custom ROM.
Thanks, I'll ask my questions
But why did the update delete trwp and supersu?
I was happy with OOS but missed the future of centering the clock.
May I ask which custom rom you use?
Updates remove SuperSU because they essentially flash over all non-user partitions (everything except /data, where your files, settings and user apps are stored). To root the OS, SuperSU installs its files in the /boot partition, which gets overwritten during ROM flashes. Root gets deleted any time you flash any mod (including most custom ROMs, since they also replace /boot). The only exception to this is if you flash a custom ROM that comes pre-rooted.
TWRP does not get deleted immediately during flashing, but rather when you first boot up afterwards. OOS will attempt to replace any custom recovery with the stock recovery when it first boots up after updating. You can get around this by either flashing TWRP again, or rooting immediately after flashing a ROM update, before you reboot (flash ROM, wipe cache/delvik, flash root, reboot). Most custom ROMs will not replace your custom recovery.
There's a few threads containing OPSystemUI.apk mods in the Themes, Apps and Mod section, though most of them also contain a bunch of other graphical modifications. If you only want to center your clock and nothing else, it can be achieved by modding OPSystemUI.apk yourself, though there is a bit of a learning curve to it.
m4l4g4 said:
Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
Click to expand...
Click to collapse
You are mixing things up a bit but don't worry, I'll explain.
You need to unlock the bootloader first, and that always wipes your data for security reasons. So if your phone is stolen, the thief won't be able to access your data by installing TWRP or a custom rom. After unlocking you install TWRP (custom recovery), and use it to flash stuff. (roms, mods, etc)
After that you only lose data if you (or a rom) mess things up, and your data becomes unaccessible, or you relock your bootloader for whatever reason. That's why you should always backup to a computer before doing major flashing/upgrades, etc.
If you upgrade the rom you'll lose root and/or TWRP, but you can flash it again as explained by others.
Hi there,
so I've flashed TWRP and SuperSu again. You are all right, i haven't to wipe anything. I really mixed up things. But now everything is working for me.
Okay, i have to learn how to get my OPSystemUI.apk modify it and flash it back?
I will seach the threads and learn.
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Glendog1 said:
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Click to expand...
Click to collapse
Clean Flash:
1) Latest Official TWRP (Can be done from within old TWRP)
2) Reboot Recovery to new TWRP
3) Wipe
4) Latest Firmware (OB29)
5) ROM
6) OpenGapps Arm64 8.1 Nano or Pico
7) Root Optional
Don't forget to Nandroid first, and it might be a good idea to remove any security measures on your current setup too. (Fingerprint/Pin/Pattern)
Queue up the zips for Firmware/ROM/Gapps and flash in that order together.
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Glendog1 said:
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Click to expand...
Click to collapse
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
DirkGently said:
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
Click to expand...
Click to collapse
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Glendog1 said:
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Click to expand...
Click to collapse
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
DirkGently said:
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
Click to expand...
Click to collapse
Pin/password and fingerprints are two different things. Fingerprints are just a convenient method of authenticating. Removing them does nothing for the actual security with is pin/password.
The reason for removing the lock screen password before taking a backup is that if you install a new ROM and set a password and then restore your older backup, you can't get past the lock screen password. So, remove the password before taking the backup and then you can restore it later and set a new password.
I find the better option is to not remove the password and then, if you need to restore the backup after having changed passwords, you can delete the passwords of the restored backup in TWRP from Advanced>Terminal with these commands:
Code:
cd /data/system
rm -f gatekeeper.* locksettings.*
Changing the pin/password to none doesn't wipe out the on-boot password. However, when setting up a new password and selecting to not set an on-boot password will remove the current on-boot password for some users, but not for others (it doesn't for me).
Sent from my OnePlus 3T using XDA Labs
Thanks guys.
I followed your instructions @DirkGently and it worked a charm.
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Thanks,
Glendog1 said:
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Click to expand...
Click to collapse
Magisk
Glendog1 said:
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Click to expand...
Click to collapse
Yes and yes, but firmware may be tricky and messing up too much may render phone unusable. Messing with ROMs is fine though.
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Glendog1 said:
I have already installed a custom rom, will this be an issue?
Click to expand...
Click to collapse
That's ok of you asking questions, that's what this forum is about.
You should have got no problems if you're running a kernel shipped with custom ROM. Custom kernel is like EX, Mady's Xtended, Franco and so on.
Glendog1 said:
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Click to expand...
Click to collapse
You don't need to worry about Kernel stuff. RR already includes Caesium Kernel. You chose a good ROM by the way!
Here's a little information about Firmware. The OP3 and OP3T have unified builds. This means that in some cases the same Custom ROM can be used on both. There is some device specific software though so this has to be separated out and treated as independent from the ROM. This is what we refer to as Firmware. When Oneplus release new builds they include the updated Firmware in their Official ROM. If you look at the Firmware thread i linked you to, you'll see that kamilmirza takes the Firmware from the Official OOS builds and makes them available as flashable .zip files that we can use on Custom ROMs. Bookmark his Thread for future use.
There is no need to stress about always being on the latest Firmware for your Custom ROM, just ensure it is the Firmware intended for your device. The version you flashed earlier will probably do you for a while. At the same time, if you do always want to be on the latest, there's no reason not to. There's little to be gained by it though. If you're following the RR thread you'll probably see people mention it when the ROM requires a new Firmware. Again, don't stress about it.
As far as flashing Firmware, you can do it any time. You can do it before flashing an updated build of your ROM, or on it's own in a separate visit to Recovery. It's not particular either way. I would stick with the Open Beta Firmware, which people usually abbreviate to OBXX, i.e OB29. Just remember what you flashed so that you know which version you are using.
Now that you're rocking your Custom ROM you're next questions will be about updating it. This can be done easily and safely by Dirty Flashing. I've done dozens of updated builds since my last clean flash and everything has gone perfectly every single time.
Dirty Flash:
1) Download new ROM build (and Firmware if applicable) to Internal Storage.
2) Boot into Recovery
3) Nandroid Backup
4) From Install Menu, flash Firmware (if applicable), and ROM.
5) Wipe Dalvik & Cache when prompted. (BillGoss will tell you it's not necessary. It doesn't hurt either way, so up to you!)
6) Reboot phone.
For a Dirty Flash, you do not need to use the 'Wipe' Menu at all.
I always take a new Nandroid before flashing an updated build. I will have had a whole week on the previous build so i know i'm not backing up a bug and the backup will be as recent as possible if a problem occurs. Once i boot back into the phone i delete the old Backup. The new one is there if i need it. Always have that one recent Backup, just in case. As i've said, RR is great and i'm yet to run into a problem with it. From now on you can Dirty Flash the updated weekly builds with little to worry about and with a Backup to fall back to if anything goes wrong.
I don't mention Magisk because i don't use it, and i don't advise others use it. Unless you need Root access for something specific, don't bother. Half the threads on XDA are about problems with Magisk. Avoid the added complication if you can. Now this statement will trigger the Magisk fans, but nobody has ever had a bug or failure with something that they did not flash in the first place. Keep it as simple as possible.
Hi everyone! I'm very much a newbie when it comes to custom ROM's, so apologies if this is a a dumb question...
I just managed to install the latest Pixel Experience ROM on my K20 Pro, from the stock Chinese ROM. Before installing it, I had to flash DFE. So, from my understanding, it is now blocking me from re-enabling encryption. I need to have encryption enabled for work email access, so is it possible to enable it somehow? I'm not worried about losing any data on the phone, but I would certainly prefer to use Pixel Experience than to go back to MIUI.
Per another forum thread I found, one member suggested to "reflash your vendor/firmware." Is that accurate? If so, how do I do that, and what would be the result?
shleepy said:
Hi everyone! I'm very much a newbie when it comes to custom ROM's, so apologies if this is a a dumb question...
I just managed to install the latest Pixel Experience ROM on my K20 Pro, from the stock Chinese ROM. Before installing it, I had to flash DFE. So, from my understanding, it is now blocking me from re-enabling encryption. I need to have encryption enabled for work email access, so is it possible to enable it somehow? I'm not worried about losing any data on the phone, but I would certainly prefer to use Pixel Experience than to go back to MIUI.
Per another forum thread I found, one member suggested to "reflash your vendor/firmware." Is that accurate? If so, how do I do that, and what would be the result?
Click to expand...
Click to collapse
Why did you have to flash DFE? It's only used if you change roms frequently to avoid encryption.
I initially had trouble successfully installing the ROM. So, I started from scratch and followed some thorough instructions I found online, which included the DFE step. (I noticed that TWRP was previously showing an encryption error at the start of ROM installation; but I guess it could just be a "warning" more than an error. I suspect my problem before was probably more related to not having the latest MIUI update installed, or something like that.)
I don't plan on frequently swapping ROM's.
shleepy said:
I initially had trouble successfully installing the ROM. So, I started from scratch and followed some thorough instructions I found online, which included the DFE step. (I noticed that TWRP was previously showing an encryption error at the start of ROM installation; but I guess it could just be a "warning" more than an error. I suspect my problem before was probably more related to not having the latest MIUI update installed, or something like that.)
I don't plan on frequently swapping ROM's.
Click to expand...
Click to collapse
Your best bet is to go back to stock and start again. I believe installing an official fastboot ROM will restore encryption. Your previous issues were probably caused by not formatting data when flashing PE.
There is no requirement to disable encryption on this phone, ignore any guide that adds that as a step. You should only disable encryption if it's your personal preference to disable it.
Follow this guide.
Flash the latest Chinese 11.0.5 fastboot ROM. Make sure you don't lock the bootloader if using the Mi Flash Tool.
Boot into MIUI once to allow it to finalise the install, you don't need to do the initial phone setup once it boots into MIUI.
Boot into fastboot and install TWRP. I recommend the latest from mauronofrio which should be 3.1.1-32
Boot immediately into TWRP. I use the volume up button while powering up the phone.
Perform a factory reset in TWRP (using the swipe button), then format data (need to type 'yes' to confirm).
Reboot into TWRP using the TWRP boot menu, this ensures the newly formatted data partition is correctly mounted.
Copy over the PE ROM, then flash.
Boot into your new ROM, everything should be OK. Then boot back into TWRP to install Magisk if you want root.
shleepy said:
I initially had trouble successfully installing the ROM. So, I started from scratch and followed some thorough instructions I found online, which included the DFE step. (I noticed that TWRP was previously showing an encryption error at the start of ROM installation; but I guess it could just be a "warning" more than an error. I suspect my problem before was probably more related to not having the latest MIUI update installed, or something like that.)
I don't plan on frequently swapping ROM's.
Click to expand...
Click to collapse
Do yourself a favour and follow the instructions in the description of the rom, not some instructions you found online telling you to do some unnecessary stuff. Going to and from miui, format data, everything else just wipe cache, system and data to avoid issues, even then you can get away with dirty flashing aosp based roms 99% of the time imo.
As for the miui update, I have no idea how you came to that conclusion but just no, that's not how it works at all. Vendor firmware and the rom is all you need for pixel experience at the bare minimum.
You can try flashing the rom again, but don't flash the DFE.
Hello everyone, try to install several custom roms, there is no tutorial that explains how the rom and twrp are installed. There are many tutorials and they all contradict, some say do this, others say do the other, but all fail.
Twrp boot, flash rom, install custom rom on SLOT A, install TWRP on slot B.
PROVEN ROMS:
PixelExperience:
Very low call volume, impossible to fix.
LineageOS:
Does not start play store, does not allow login to accounts, does not allow to install gapps.
- CURRENT ROM--
Evolution X:
Does not start play store, does not allow login to accounts.
I have been installing customs roms for years and this device is costing me my life. HELP
The most users get in trouble with A/B devices because they don't know exactly the differences between A-only and A/B partitions.
You don't know how to install TWRP? Why? On twrp.me you can find a detailed instruction for every single model.
A custom ROM is always a .zip file and you can flash a .zip file via TWRP. If you flash a ROM while slot _a is set as active you will install the ROM on slot _b. That's all. That is the meaning of semless updates.
Every new ROM must contain a own boot.img. A new boot.img will delete TWRP and Magisk. TWRP is a recovery and A/B devices don't have own partition for recovery. The recovery is merged in the boot partition.
Also Magisk uses the boot.img to patch the ramdisk. Flashing a new boot.img means you override the patched ramdisk with a new own. As a result you need a new Magisk installation.
my recommendation is starting from scratch with a clean stock 10 install then trying again...
lineage wiki probably has the best install instructions https://wiki.lineageos.org/devices/lake/install but also check its forum thread https://forum.xda-developers.com/g7-plus/development/rom-lineageos-17-1-t4076569 for other recommendations . if you want evolution X read the instructions in its thread https://forum.xda-developers.com/g7-plus/development/rom-evolution-x-4-1-69-moto-g7-plus-t4081731 as well but there pretty much the same.... you've probably went threw those threads already based upon you saying you have tried 3 diff roms already, but try again from a clean install of stock 10 (IF you want to run a 10 rom). i know it's not really a "clean/easy/simple" solution/tutorial, but with this device there is some trial and error for getting a half assed working install. however MAKE SURE you are on a stock 10 rom when installing a 10 rom, pixel experience is a 9 rom and that could be part of your problem. moving from android 10 stock, to a 9 rom, then back to a 10 rom will lead to issues. or a 9 rom, to a 10 rom, without moving to stock 10 in between will lead to problems.
as this isnt nearly a widely adopted device, custom rom development and support isnt even close to other devices, so expect bugs. i've always ran cfw's on all my devices ever since the htc g1/dream days, this is my first device i've stuck with stock due to the lack of rom development, lack of widespread use and people actually wanting to use cfw and users to bug report, and stock being more stable... but your mileage may vary. also no disrespect meant towards the hard working dev's who do work on this device, keep it up.
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
prodigy90 said:
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
Click to expand...
Click to collapse
yeah it seems to be pretty finicky getting a good install and gapps seem to have issues. reading all the posts in the lineage17 thread just make me cringe. as much as i'd love to use lineage as my daily driver (or evo X) my days of willing to put up with a buggy rom and daily dirty flashing have come and gone. this was my first, and will be my last, moto device for the the simple fact it just doesnt have the user base and its development is stunted, compared to more widely used devices.
i hope you get something working, the lineage17 thread definetly has some good advice on what people have done to get a working install, should be able to apply flash order etc to a evoX install (minus having to install gapps for evoX)
solved
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
prodigy90 said:
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
Click to expand...
Click to collapse
yup, the LMSA is a great tool for sure. glad you got back to a clean stock install.