Related
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about 14GB from flashing ROMS and such.Everything seems to have gone smoothly however when I try the oem unlock command I am told that the device is already unlocked.I proceeded to root and then I tried to flash TWRP but I get permission denied.
Also,my Play Store just crashed when I try and type in an app to search for.
The question is-how do I know which factory image is right for my device?
There are a number of 5.1.1 images,I selected the one marked for all carriers except T-Mobile.Could I have selected the wrong image to be causing some of these problems?
Or should I just go ahead and jump up to 6.0.1-there is only 1 image for that release.
I would't think the image mattered that much but something is wrong here.
I got the phone last week from the Amazon sale and I activated it no problem on Verizon and flashed several ROMS no issue.
Advice is much appreciated.
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
dahawthorne said:
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
Click to expand...
Click to collapse
Thanks for the detailed response. I was running 5.1 initially because that is what the phone booted with and I like full-featured ROMS like BlissPop. I guess I'll give 6.0.1 a whirl.It just seemed like it was too new to be rock solid. I had as many features on my old S3 running 4.4.2 as I have seen since then if not more actually. I am curious about Google Now On Tap however.
Hopefully this gets me fixed up.Cheers.
chiadrum said:
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about .......
Click to expand...
Click to collapse
It is possible that the issue is caused because you downgraded the bootloader by flashing 5.1.1.
Flash the complete latest stock 6.0.1 images.
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig. I am guessing that is normal?
The 5.1.1 started working fine after an update all but I still couldn't install TWRP fyi.
Let's see how Marshmallow tastes!
The "does not contain boot.sig and recovery.sig" is standard. I have no idea why it continues to appear version after version, but it has no effect on the installation.
chiadrum said:
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig.
Click to expand...
Click to collapse
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
NLBeev said:
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
Click to expand...
Click to collapse
Thanks guys.
chiadrum said:
Thanks guys.
Click to expand...
Click to collapse
Ok more strangeness.pPhone is working fine,no issues.However I am unable to unlock bootloader using the fastboot OEM unlock command.
The message is "Not supported command in current status".
Yes,OEM unlock is allowed in Dev Options.I tried turning that off in case the indicator was faulty and then I couldn't even attempt to unlock,immediate failure.
Tried this several times after reboots as well.
Build MMB29K.
Any ideas?
Would it be too simple an answer to say that it's because the phone is already unlocked? You couldn't install a new ROM with a locked bootloader.
I myself have been a bit surprised by the peremptory & derogatory comments of some of the very senior members in these forums when people ask what seem to be questions with obvious answers, and I'm beginning to see their point...
Still, I also recognise that an "easy" question is one that you know the answer to, and I don't want to put people off asking questions. Being knocked back myself several times hasn't stopped me asking.
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
chiadrum said:
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
Click to expand...
Click to collapse
Confirmed I am an idiot.Device is unlocked already. Wasn't expecting that.The people way smarter than me who prepared that image took care of it for me.
Not an idiot at all. Like I said, an easy question is one that you know the answer to. Experience counts...
It's not the image that is unlocked - it's the device. Once unlocked, you have to specifically lock it again, but it's neither simple nor a good idea. An unlocked device gives you a far better chance to recover from errors.
AS OF RIGHT NOW THIS IS ONLY FOR T-MOBILE AND NOW SPRINT!
This is a stock rom for the retail brazil MotoZ(2) force ported over to our phone.
This is stock with only encryption and dm verity removed for support with twrp. (No more boot image including.)
Flashing instructions.
NOTE: CLEAN FLASH! This is a rom from another phone. I cant help you if you write me and say system fc's or any other fc's and you didnt clean flash.
1. Download rom and place it on sd card or internal.
2. Download oem.img and flash it (fastboot flash oem oem.img)
3. Reboot to recovery
2. Wipe system data cache.
3 Flash rom.
4. Reflash whatever root you had. (Magisk)
5. Profit.
As far as I know this does have all the latest fixings (KRACK,Bluebourne, ECT)
Includes VOLTE
Includes WIFI Calling
Usually all roms are pretty stable. IF there is any bugs post below and ill get to working on it.
Sprint install guide
Guide for Sprint users:
Go into Bootloader
Flash This oem.img (courtesy @joemossjr) "fastboot flash oem oem.img
Go into recovery
wipe system and data.
Flash rom
Tested this on my Sprint phone and everything works just fine and with Pantheon, you will pass Safetynet if you flash the image in bootloader.
note: for Sprint users, we NEED to flash the oem.img to not have dialer issues, so I will stress, flash that oem image and if you don't want the bloat, you can delete everything but oem.prop from /oem folder through root or recovery's file manager after you mount OEM.
FLASH ALL
Flash all has been made this includes T-Mobiles Modem with stock everything else. you wont be able to take otas on it due to modified Modem. But updates for thes roms come a lot faster then ours so when one comes out ill update it. Please flash the latest twrp. This is going to encrypt you so your gonna have to format data in twrp and flash this Unencrypt Zip
This will format data. Treat it as a flash all to get back to stock also if you dont want tmobile bloat. This rom in it self with twrp will pass safetynet without magisk as long as you dont modify oem partition. Other then that happy flashing. Download for flash all is below
Downloads: November
oem.img
November Flash all
CREDITS
Motorola Firmware Team
@SuperR. for providing a bad ass platform for Rom making.
@Uzephi for testing the Sprint side of things lol
First! ?
Pantheon works on this rom.
Edit: kernel upstream has KRACK and blueborne fixes in it ?
Edit: tried same install instructions. Works for Sprint phones and activates them
Edit 3: well had to do some dialer stuff, but everything else worked. Will give guide in the morning to get the rom 100%
Sprint install guide
Guide for Sprint users:
Go into Bootloader
Flash This oem.img (courtesy @joemossjr) "fastboot flash oem oem.img
Go into recovery
mount oem. (you can delete everything using file manager in /oem besides oem.prop)
wipe system and data.
Flash rom
Tested this on my Sprint phone and everything works just fine and with Pantheon, you will pass Safetynet if you flash the image in bootloader.
Edit: for Sprint users, we NEED to flash the oem.img to not have dialer issues, so I will stress, flash that oem image and if you don't want the bloat, you can delete everything but oem.prop from /oem folder through root or recovery's file manager after you mount OEM.
Edit 2: Wifi Calling will not work, that file is in sprint's OEM partition and it FC's when adding it or using sprint's oem.img, so if you want this rom, I advise WiFi calling will not work until further notice.
updated thread
ADDED Stock oem image
ADDED Sprint support per @Uzephi
joemossjr said:
updated thread
ADDED Stock oem image
ADDED Sprint support per @Uzephi
Click to expand...
Click to collapse
WiFi calling currently doesn't work for Sprint. Technical details: Sprint uses a different WiFi calling setup where a special Google dialer is in /oem to work. If you use this dialer or the included wifi dialer.jar file, it will just continuously FC and you can't do anything. To get Sprint models working we have to use the stock dialer which doesn't work with Sprint's WiFi calling. We will put a poll up to see interest in WiFi calling since this will take a bit of hackery to get working. I want to gauge interest before I take on this task.
My new T mobile Moto Z2 Force still has stock August image on it. I am waiting for my screen protector and case to arrive before I transfer my account to this phone. I am also waiting to unlock the bootloader and root the device. Now, should I flash your new Nov image since I want KRACK and blueborne fixes OR should I first flash the August image first, then upgrade to Nov image.
kendallgreen said:
My new T mobile Moto Z2 Force still has stock August image on it. I am waiting for my screen protector and case to arrive before I transfer my account to this phone. I am also waiting to unlock the bootloader and root the device. Now, should I flash your new Nov image since I want KRACK and blueborne fixes OR should I first flash the August image first, then upgrade to Nov image.
Click to expand...
Click to collapse
Either or honestly lol you can go to August for the updated firmware
So going from a brand new device on NCX26.7, how do we go about getting our phones ready to flash this? Unlock bootloader, root, then flash this and reroot? Then follow the instructions for TWRP in your other post?
swidger said:
So going from a brand new device on NCX26.7, how do we go about getting our phones ready to flash this? Unlock bootloader, root, then flash this and reroot? Then follow the instructions for TWRP in your other post?
Click to expand...
Click to collapse
Unlock bootloader, install TWRP, follow instructions in OP.
Moto Z2 Force Edition - T-Mobile
Unlocked Bootloader
TWRP 3.2.0-0
I keep trying to flash this ROM, and have succeed in the flashing process. However, whenever I boot up, I get "TMOConfig has stopped" and then I can close it. I notice, that cellular data is not active. I continue through setup as normal until the Moto Permissions screen. When I try to go through this screen, whether I accept or decline, "com.motorola.tmo.setupext has stopped" comes up. The only option is to open app again and it takes me to the prior screen for Google setup and gets stuck in this loop until I restart the phone.
I've followed the instructions exactly MULTIPLE times just to verify I got it right. I'm clean flashing as well, so no it's not cuz of that. I've even redownload the files three times just to ensure it wasn't the result of possible file issues. Anyone else having this issue? I'd greatly appreciate a second pair of eyes on this!
champ784 said:
Moto Z2 Force Edition - T-Mobile
Unlocked Bootloader
TWRP 3.2.0-0
I keep trying to flash this ROM, and have succeed in the flashing process. However, whenever I boot up, I get "TMOConfig has stopped" and then I can close it. I notice, that cellular data is not active. I continue through setup as normal until the Moto Permissions screen. When I try to go through this screen, whether I accept or decline, "com.motorola.tmo.setupext has stopped" comes up. The only option is to open app again and it takes me to the prior screen for Google setup and gets stuck in this loop until I restart the phone.
I've followed the instructions exactly MULTIPLE times just to verify I got it right. I'm clean flashing as well, so no it's not cuz of that. I've even redownload the files three times just to ensure it wasn't the result of possible file issues. Anyone else having this issue? I'd greatly appreciate a second pair of eyes on this!
Click to expand...
Click to collapse
you still have OEM stuff - you need to wipe oem partition and then flash.
byt3b0mb said:
you still have OEM stuff - you need to wipe oem partition and then flash.
Click to expand...
Click to collapse
Does formatting help wipe that? I've done wipes and formatting just to be safe
Gotta flash the oem.img then reflash
joemossjr said:
Gotta flash the oem.img then reflash
Click to expand...
Click to collapse
Just tried redoing everything again. I get cellular now, and it boots. But now the phone will randomly freeze after a few minutes and restart
Sorry for being such a noob... This is my first dual partition device I've worked with... I've gotten spoiled with OnePlus and Nexus devices lol
champ784 said:
Just tried redoing everything again. I get cellular now, and it boots. But now the phone will randomly freeze after a few minutes and restart
Sorry for being such a noob... This is my first dual partition device I've worked with... I've gotten spoiled with OnePlus and Nexus devices lol
Click to expand...
Click to collapse
Sorry I meant which slot/ota are you on
joemossjr said:
Sorry I meant which slot/ota are you on
Click to expand...
Click to collapse
To check this, go to TWRP and in the reboot menu it will tell you which slot you're on like the below screenshot of me on slot B
For sprint users, there is a poll to end on dec 8th asking if WiFi calling is a must for your rom. please answer it. I have tried a few methods but all fail. any further would require editing the framework.jar file in oem and some trickery that needs some serious coding done to work correctly. So I will take on the task if enough vote for it. (I do this in my free time for free and if not enough interest is given, I'd rather not waste the time as another update might break it, and it also takes me away from my EAS project which has a lot of interest.)
joemossjr said:
Sorry I meant which slot/ota are you on
Click to expand...
Click to collapse
Mine shows Slot A. Am I correct in assuming that should be Slot B?
champ784 said:
Mine shows Slot A. Am I correct in assuming that should be Slot B?
Click to expand...
Click to collapse
Slot A has less bugs than Slot B. I would stay slot A if you can. I would suggest wiping oem in TWRP, mount oem, wipe oem, then reboot to bootloader and flash the oem img in OP.
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.
The question probably sounds stupid but after almost a year of just forgetting about using root or unlocking bootlader i forgot many things.
I remember i used to have a mi 9 with encryption on and everytime i open twrp you will need to decrypt the data.
Now with the MI 9T Pro i had to format data in order to boot into Evolution X ROM that of course left me with a decrypted phone and i dont really like it in case my phone gets stole or something.
Do you guys know if i can use the option inside teh ROM to encrypt and what else i wuld need to do?
Thanks in advance to whoever takes the time to respond
PriPhaze said:
The question probably sounds stupid but after almost a year of just forgetting about using root or unlocking bootlader i forgot many things.
I remember i used to have a mi 9 with encryption on and everytime i open twrp you will need to decrypt the data.
Now with the MI 9T Pro i had to format data in order to boot into Evolution X ROM that of course left me with a decrypted phone and i dont really like it in case my phone gets stole or something.
Do you guys know if i can use the option inside teh ROM to encrypt and what else i wuld need to do?
Thanks in advance to whoever takes the time to respond
Click to expand...
Click to collapse
If all you did was format data, then encryption is still enabled. As soon as you setup lock-screen security, i.e. PIN, password, pattern, etc., for the first time your phone will automatically be encrypted.
Robbo.5000 said:
If all you did was format data, then encryption is still enabled. As soon as you setup lock-screen security, i.e. PIN, password, pattern, etc., for the first time your phone will automatically be encrypted.
Click to expand...
Click to collapse
No I couldn't boot until I flashed the DM verity.
So the encryption is now gone, but do you know if I can encrypt and then flash DM verity again with the force encryption on?.
PriPhaze said:
No I couldn't boot until I flashed the DM verity.
So the encryption is now gone, but do you know if I can encrypt and then glad DM verity again with the force encryption on?.
Click to expand...
Click to collapse
Ordinarily you shouldn't need to flash dm-verity. And as far as I'm aware, there is still no need to.
Normally it's just a case of formatting data to temporarily remove encryption, if flashing over MIUI.
As to your specific question, I couldn't say, as I've never needed to flash a dm-verity, disable force encrypt, or vbmeta file/script.
Personally, I would flash the latest fastboot MIUI ROM for the phone, then reinstall EvoX.
Before installing the ROM, in TWRP do the factory reset and then format data (There is no need to wipe anything else). Then reboot into TWRP to ensure the newly formatted data partition is properly mounted and flash as normal.
This has worked for me every time.
Yeah, some roms aren't booting without dfe.
to remove decrypt you can just wipe vendor and flash it again. you'll get encrypted. (however, some users confirm it puts them back into recovery, and they needed to reflash vendor+dfe for them.) Currently investigating if this is a RIN or RCN problem or for every device.
alternatively. If you are scared about having your device stolen. May I suggest you stay decrypted. Use ofox. and under ofox settings add a recovery password?
In the event you get stolen, they won't be able to access your recovery.
also, I'm looking for someone to test if wiping the data partition and not flashing dfe (after a rom has booted for the first time) and rebooting causes encyrption. (as you desired.) If you're willing to test. Try the above 3 methods?
Sandeeep Kiran said:
Yeah, some roms aren't booting without dfe.
to remove decrypt you can just wipe vendor and flash it again. you'll get encrypted. (however, some users confirm it puts them back into recovery, and they needed to reflash vendor+dfe for them.) Currently investigating if this is a RIN or RCN problem or for every device.
alternatively. If you are scared about having your device stolen. May I suggest you stay decrypted. Use ofox. and under ofox settings add a recovery password?
In the event you get stolen, they won't be able to access your recovery.
also, I'm looking for someone to test if wiping the data partition and not flashing dfe (after a rom has booted for the first time) and rebooting causes encyrption. (as you desired.) If you're willing to test. Try the above 3 methods?
Click to expand...
Click to collapse
BS. There is zero 'need' to flash dfe scripts. People are not formatting data when they need to, then when they cannot boot into a newly flashed ROM, they search and find solutions telling them to format data and flash dfe scripts. The thing is, people do not realise that it is the formatting data that fixes the problem, and they believe it is the dfe patch that is the fix. In all these cases formatting data alone would have been enough to fix the problem.
Also Orange Fox is only preferential if you stay with MIUI, as it's extra features are all about working with MIUI. If you are going with an AOSP ROM, stick with mauronofrio's latest TWRP, it is by far the best recovery for this phone.
As far as your 'test' is concerned, twice I have had bootloops after flashing a ROM, that have been fixed by formatting data alone.
The first time was when I first flashed an AOSP based ROM over MIUI before knowing that formatting data was required in this scenario. The second time was flashing AOSiP over LOS, when I still thought that going from one AOSP ROM to another never needed to format data when flashing.
Robbo.5000 said:
BS. There is zero 'need' to flash dfe scripts. People are not formatting data when they need to, then when they cannot boot into a newly flashed ROM, they search and find solutions telling them to format data and flash dfe scripts. The thing is, people do not realise that it is the formatting data that fixes the problem, and they believe it is the dfe patch that is the fix. In all these cases formatting data alone would have been enough to fix the problem.
Also Orange Fox is only preferential if you stay with MIUI, as it's extra features are all about working with MIUI. If you are going with an AOSP ROM, stick with mauronofrio's latest TWRP, it is by far the best recovery for this phone.
As far as your 'test' is concerned, twice I have had bootloops after flashing a ROM, that have been fixed by formatting data alone.
The first time was when I first flashed an AOSP based ROM over MIUI before knowing that formatting data was required in this scenario. The second time was flashing AOSiP over LOS, when I still thought that going from one AOSP ROM to another never needed to format data when flashing.
Click to expand...
Click to collapse
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Sandeeep Kiran said:
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Click to expand...
Click to collapse
Numerous cases? Who's we? What roms on what devices need dfe then? Only seen 2 roms ask for dfe, everything else it's as easy as 'going to and from miui, format data and reboot recovery' works every single time.
Sandeeep Kiran said:
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Click to expand...
Click to collapse
Try this next time you see somebody saying they have tried may things and always get bootloops when trying to flash an AOSP ROM and you want to advise them to flash dfe.
Instead tell them to flash the latest MIUI fastboot ROM for their device, then install TWRP, in TWRP do a factory reset followed by format data, then reboot into TWRP and flash the ROM.
I bet they will come back and tell you it worked.
Again there should be zero need to flash dfe scripts.
If there are any AOSP ROMs out there that genuinely won't boot without flashing dfe (and here I'm talking about all users of such ROM), then the dev had done something stupid and everyone should seriously avoid the ROM.
At least half of the 50+ ROMs are no longer actively maintained.
The vast majority of Orange Fox extra features are specific to MIUI and so are redundant for AOSP ROMs. Mauronifrio's latest TWRP is the most stable for this phone, so if you're going with AOSP ROMs then the extra stability makes most sense.
I've been aware that mauronifrio does not own this phone ever since his initial build. I was also aware back then that he is also an official TWRP maintainer for other devices and so would mostly likely become the maintainer of the official version for this phone, which has now happened. If you go to the official TWRP site and download for this phone, it is by mauronifrio. You can also download the official version from the OP of his TWRP thread.
I would suggest that in most cases, people getting error 7 issues are not on the latest mauronofrio TWRP build.
Are you aware that all these different recoveries are just TWRP with a fancy dress. This is the great thing about TWRP. It was designed to be extensible, to allow others to build on it, in terms of functionality and design. So really there is only TWRP, just many different flavours.