Hi,
yesterday i went through the process of flashing custom rom and i just want to share my experience.
My daily driver was the latest MIUI7 because it was very stable and battery life was good (stock global stable, locked bootloader). But i decided to try custom rom mainly because i had strange performance issues every now and then.
1. Applied for official unlock - Unlock Page
2. I read many posts and i tought it might be best to upgrade to MIUI8 first. I updated with the official updater app.
3. Unlocking didnt work because you need a Developer Rom of MIUI installed to link the device to you Mi account and successfully unlock. I downloaded latest global dev rom and flashed with official updater app.
4. Unlocked successful with official Mi Unlock Tool.
5. Installing TWRP ZCX - worked and was easy
6. Backup System, Data, Firmware, Modem with TWRP (didnt need it so far)
7. Flash Nitrogen OS
8. Reboot to system - "to start android enter password" - surprised and shocked so i googled and found a hint to "format data" because storage might be encrypted.
9. In TWRP - Wipe i "formated data" so all files were deleted! be sure to backup everything!
10. Nitrogen OS booted (no need for Gapps - everything is built in)
11. Flash fingerprint fix - apparently i have the Goodix and need this fix for fingerprint to work
12. I was confused because there was no caller app (call worked but no UI) so i flashed new and again and tried Psy Firmware but i just had to set the caller app in settings.
13. All is working good so far :fingers-crossed:
Thanks for all the work done by this community. I greatly appreciate all the cool stuff! :highfive:
EDIT: I have FPC sensor not Goodix. The fix is for FPC! Thanks to @Denis:) for pointing that out.
You are wrong on some points ;p
Its so easy to flash roms on all snapdragon devices
Theres a need for gapps, it doesnt come preinstalled on roms, which is a good thing.
If you flashed fpc fix and it works now, it means you have FPC sensor, not goodix (which is good -like me), dev of NOS will make fpc default from now on.
For next time, you need to format data when you come from Miui MM, because it encrypts data by default.
Also I suggest formatting data,cache to F2FS, it actually makes it even faster a bit imo, but ita not a must.
Denis:) said:
For next time, you need to format data when you come from Miui MM, because it encrypts data by default.
Also I suggest formatting data,cache to F2FS, it actually makes it even faster a bit imo, but ita not a must.
Click to expand...
Click to collapse
I have installed LineageOS several times over MIUI but I didn't need to format data. Why does this happen in nitrogen os, any idea?
Denis:) said:
...
Click to expand...
Click to collapse
The level of difficulty may be different for different people
I flashed NitrogenOS and Gapps but then did a wipe and flashed only NiOS but in the end i had all the Google apps... Maybe this part didn't get wiped - Thanks for pointing that out.
Right, FPC sensor - my mistake
The encryption thing was confusing because there is not much info on that topic here - especially the guides. Thanks for confirming this is a thing.
This F2FS format thing is done in TWRP?
If you didnt wipe system aswell, gapps and ROM persisted.-dirty flash (update ROM)
If you want to update ROM + gapps, you must wipe System aswell with dalvik/art, cache
Then flash ROM+gapps , wipe cache and reboot
F2FS is done in twrp but you must have f2fs compatible twrp - I successfuly use rc1 latest by TheStrix, obviously if you choose to format data, cache you will lose data and you will have to clean flash ROM.
P.s By the way, when was your device made? Im just curious
funkymaster said:
The level of difficulty may be different for different people
I flashed NitrogenOS and Gapps but then did a wipe and flashed only NiOS but in the end i had all the Google apps... Maybe this part didn't get wiped - Thanks for pointing that out.
Right, FPC sensor - my mistake
The encryption thing was confusing because there is not much info on that topic here - especially the guides. Thanks for confirming this is a thing.
This F2FS format thing is done in TWRP?
Click to expand...
Click to collapse
If you want to experiment please try to format the partitions using f2fs and tell us your results.
I tried it but was unsuccessful since when I tried it there was no recovery that could support f2fs. Remember only dadii's TWRP works still I recommend you confirm it again.
Im using this one by thestrix and it works perfect;
https://www.androidfilehost.com/?fid=529152257862707658
currently i don't feel like tinkering with my phone any more. So i keep the F2FS in mind for some time in the future
Hm i don't know where to find the build date of my phone i bought it April 2016
Hi guys i tried using twrp 3.1.1.0 and it says password for unmount data. Also my phone in settings says encrypted.
I tried wiping data cahce, etc but that diidnt worked also using default_password but that diddnt worked as well
Model x820 stock ROM
Zlade112 said:
Hi guys i tried using twrp 3.1.1.0 and it says password for unmount data. Also my phone in settings says encrypted.
I tried wiping data cahce, etc but that diidnt worked also using default_password but that didnt worked as well
Model x820 stock ROM
Click to expand...
Click to collapse
Have you try reboot the phone into normal Android system? and later try reboot into TWRP, I read somewhere it might work.
Moon75 said:
Have you try reboot the phone into normal Android system? and later try reboot into TWRP, I read somewhere it might work.
Click to expand...
Click to collapse
Hi guys the solution for my me was doing an entire wipe of everything except recovery then flash rom, it seems that the stock rom of le max was causing that
What was your ROM in the beginning? Was it Indian ROM? Did it have the update manager? Which ROM did you flash after wiping everything except recovery?
I bought the phone from geekbuying with EUI version 5.8.019S (Stable), BUILD: FGXOSOP5801910121S release-keys. It looks like the latest vanilla Indian ROM, but it is most likely vendor-modified since the phone was received unsealed and there is no update manager. The main problem is the encryption - phone is encrypted right from the start without any password or PIN prompts. Factory reset allows to set up everything from the start, but the phone is still encrypted. TWRP asks for a decryption password. I have tried multiple vendor and default passwords with no luck. TWRP factory reset does not prevent the encryption.
This question keeps coming up in forums since people do not seem to search for similar questions. Well, I did. Therefore, I will try to assemble the list related to the encrypted ROM:
https://forum.xda-developers.com/le-max-2/help/eui-roms-support-device-encryption-t3516825
https://forum.xda-developers.com/le-max-2/help/wiping-to-install-rom-le-max2-suddenly-t3518405
https://forum.xda-developers.com/le-max-2/help/update-eui-t3480614
https://forum.xda-developers.com/le...dian-stock-19s-rom-chinese-bloatware-t3484388
https://forum.xda-developers.com/le-max-2/help/benefit-form-leaving-x829-to-indian-t3609698
Proposed solutions:
CASE 1: No Update manger + encrypted ROM
Since it is a vendor ROM, you can try flashing a clear stock ROM from recovery that can be downloaded from the official LeEco forum http://forum.le.com/in/eui_detail.html?euiid=206 . It might not directly resolve encryption, but will make the update manager appear, which can be used to upgrade to ROM w/o encryption. If you want to stick to the Indian ROMs, but want to remove encryption - see below
More reading here: https://forum.xda-developers.com/le-max-2/help/update-eui-t3480614
CASE 2: Encrypted ROM
You most likely have an Indian ROM. You can try reinstalling the ROM (TWRP) and immediately wiping the data partition from TWRP. Some users report success with this.
More reading here: https://forum.xda-developers.com/le...dian-stock-19s-rom-chinese-bloatware-t3484388
One user has found that upon multiple resets with TWRP the encryption seems to be ignored
More reading here: https://forum.xda-developers.com/le-max-2/help/benefit-form-leaving-x829-to-indian-t3609698
Another user suggests Chinese ROMs since they are likely not to encrypt the files. In other words, updating to a Chinese ROM might help.
More reading here: https://forum.xda-developers.com/le-max-2/help/plz-help-unskilled-x829-user-to-update-t3609639/page2
Have any of the proposed solutions worked for you?
Dear readers,
I flashed TWRP 3.3.1, booted into it, wiped data, did factory reset, and installed decrypt for latest pie.
i rebooted into twrp to verify the decryption and indeed I was not asked for a password.
Then I booted into Pie and went through the account setup and while I was doing that some updates got installed by android.
To my horor when I booted back into TWRP it again asked for password, meaning android pie somehow encrypts the data again.
(Second time I did this whole process again I installed magisk.zip, so at least I have root.)
My question is:
How can I stop Android from encrypting again during the account setup process?
Greetings,
Mike
This happens to me too, the only real workaround I've found so far is to flash your zips (ie. magisk) before booting the first time.
I did flash stock image, flash twrp, boot into twrp, format data, flash decrypt.zip, flash Magisk.zip, and reboot. First thing it does is encrypt it again.
Then I tried same process but with no-dm-verity-encrypt.zip or something like that, and it said success, but still Pie decrypts again.
Then I tried previous firmware, (. 48 instead of 51), but same result. It is driving me nuts.
And no help from here so far.
Maybe I should go back to oreo, that worked OK with decrypt.
Greetings
Same problem wait solutions.
Alas, still no fix for this major problem.
What is the point of creating TWRP and other custom recoveries for X01AD when they can not be used for making backups, due to decryption problem?
So please someone with the skills to create a force decryption that actually works, help us out.
Thanks in advance,
Mike
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
kishikaisei said:
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
Click to expand...
Click to collapse
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
mecoromeo said:
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
Click to expand...
Click to collapse
I tried that, now I am a step forward I think, I flashed the stock firmware I found, and installed the latest stock ROM, rebooted (doesn't say no os anymore), but the only thing I see is a DELETE ALL DATA button and at the bottom 'Encryption was interrupted and can't be completed. As a result, the data on your phone is no longer accessible.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.'
Darklouis said:
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
Click to expand...
Click to collapse
I have an issue with the MiFlash part, it seems that it doesn't work as I mentioned...
Aight all, formatting data partition to ext4 worked, now it is booting
kishikaisei said:
Aight all, formatting data partition to ext4 worked, now it is booting
Click to expand...
Click to collapse
Works now?
mecoromeo said:
Works now?
Click to expand...
Click to collapse
So I had an OS-less phone that don't get recognised in MiFlash, and I had orangeFox recovery.
The steps to fix were:
- Flash a full stock Firmware
- Flash the stock ROM
- Flash DFE
- Format data to ext4
- Reboot and it works
So thanks all for your help
Here's a quick guide to some of the basics.
Which recovery.
----------------------------
Use the latest from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
Do not use Orange Fox unless you intend to stick with stock MIUI. Orange Fox has extra features, which are almost all aimed at MIUI, but it often causes issues flashing custom ROMs, so it's a long way from the best option if you want to use custom ROMs. Orange Fox, along with other TWRP derivatives, allow complete access to virtually all of the phone, so it is very easy to accidentally hard brick the phone if you don't fully understand what your doing.
Ignore anyone who tells you to use Orange Fox when using custom ROMs.
Do I need to permanently disable encryption
-------------------------------------------------------------------------
No.
There is not a single reason to permanently remove encryption, other than personal preference.
It is recommended to have encryption removed when flashing, but this is easily done by temporarily removing lock screen security before flashing and adding it back after.
Ignore anyone who tells you that you need to flash a DFE (disable force encrypt) script.
Should I wipe all my partitions when flashing
------------------------------------------------------------------------------
No.
When clean flashing you only need to do a factory reset in TWRP.
There is absolutely no need to wipe system or vendor partitions. Ordinarily, when flashing, there is no need to go into the advanced wipe menu. I've had this phone 15 months and have never used the advanced wipe menu and have never had any issues.
When you flash a custom ROM, it will automatically wipe system first, so you don't need to do this yourself.
When you flash a vendor file, it will automatically wipe vendor first, so you don't need to do this yourself.
Even though almost all (it may actually be all) ROM flashing instruction tell you to wipe system, it is not needed.
Ignore anyone who tells you to wipe anything more than data, cache and dalvik.
Do I need to update my vendor and firmware when flashing a new ROM
-----------------------------------------------------------------------------------------------
Probably not.
If you currently have MIUI installed and it's up to date, then you will have the latest firmware and vendor and won't need to flash them.
If you're moving from one custom ROM to another, then it depends on how up to date your current ROM is. If the vendor and firmware requirements of the new ROM match the requirements of your current ROM, then will have the current vendor and firmware already installed and so do not need to flash them again.
Only when the new ROM needs a later version of vendor and firmware than you have currently installed will you need to flash them. This isn't such a common occurrence, so you'll not need to flash vendor and firmware often.
How to install a custom ROM over MIUI and remain encrypted
-------------------------------------------------------------------------------------------------
Assuming you have already unlocked the bootloader.
1 Boot into fastboot
2 Flash TWRP (fastboot flash recovery <path to TWRP file>
3 Immediately boot to TWRP (fastboot oem reboot-recovery)
4 Select Wipe Menu and Factory Reset
5 Return to Wipe Menu and Format Data
6 Return to Main Menu, then select Boot Menu
7 Select Boot to Recovery (this reboots TWRP to ensure the data partition is properly mounted after formatting)
8 Copy ROM and extras over to phone and flash them.
9 Reboot and enjoy.
Do not add any extra steps, do not miss any steps out
How to dirty flash a custom ROM update when encrypted
---------------------------------------------------------------------------------------------
1 Remove lockscreen security (this removes encryption)
2 Boot to TWRP
3 Flash the ROM update (plus vendor and firmware if the requirements for these have changed in the updated ROM)
4 Select to wipe cache and dalvik when the update finishes.
5 Reboot the ROM
6 Restore lockscreen security
How to clean flash a new custom ROM over another custom ROM
--------------------------------------------------------------------------------------------------------
1 Remove lockscreen security
2 Boot to TWRP
3 Select Wipe Menu and Factory Reset
4 Flash the ROM plus the extras you want (this includes new vendor and firmware if the requirements are different to your current ROM)
5 Reboot the ROM
6 Add lockscreen security
Thank you
Thank you very much for this. I just bought the device last week . Since i am upgrading from a lenovo vibe k5 plus (which also had a decent amountt of development support) i have a few questions. With the vibe k5 plus, installing a custom rom was very simple. flash cutsom recovery-factory reset (i used to wipe the internal storage too)-flash custom rom-flash magisk and you're done. My question(s) are 1) What is this "Force encryption" that we have to disable/keep enabled. 2) what are vendors and firmwares. I'm currently on MIUI10 (Got a Nov 2019 unit), it's pretty decent for now.
AkashNP said:
Thank you very much for this. I just bought the device last week . Since i am upgrading from a lenovo vibe k5 plus (which also had a decent amountt of development support) i have a few questions. With the vibe k5 plus, installing a custom rom was very simple. flash cutsom recovery-factory reset (i used to wipe the internal storage too)-flash custom rom-flash magisk and you're done. My question(s) are 1) What is this "Force encryption" that we have to disable/keep enabled. 2) what are vendors and firmwares. I'm currently on MIUI10 (Got a Nov 2019 unit), it's pretty decent for now.
Click to expand...
Click to collapse
Since, I think, Android Marshmallow, Google have added forced encryption. Before this you had the security menu option to encrypt your phone storage, which required a separate password to be entered on every reboot. Now encryption is done as standard and uses your lockscreen security PIN/password as the key.
Initially your phone will be unencrypted, but as soon as you first set-up lockscreen security the phone will be automatically encrypted.
Many people see this as a good thing. Should you lose the phone, you data is secure and cannot be accessed without the lockscreen PIN/password. Other people don't care about this and so prefer to disable encryption, as it makes life a little easier when flashing custom ROMs.
Some people, incorrectly, believe that disabling encryption is necessary when flashing custom ROMs, or that disabling encryption is the only solution to problems seen when flashing. This is not true and disabling encryption should only be about a users personal choice to be unencrypted.
Think of vendor and firmware as the equivalent to device drivers for PC components. They are a collection of compiled code files, provided by component manufacturers and the phone manufacturer, to allow Android to communicate with the hardware components in a standard way. Occasionally these files might get updated, as part of a MIUI update, to fix a bug or to add extra functionality. When these files are updated, custom ROM devs will include them so that they get the bug fixes or extra functionality. When this happens they will update the minimum vendor and firmware version requirements for their custom ROM - the version will be the actual MIUI version in which the vendor and firmware files were updated.
Thanks that was a really good explanation. I have one last question, so right now I'm on MIUI10 I've got the MIUI12 update notification but I want to try MIUI11 first. I've got the ROM file from the xiaomifirmwareupdater website, how do I flash it?
AkashNP said:
Thanks that was a really good explanation. I have one last question, so right now I'm on MIUI10 I've got the MIUI12 update notification but I want to try MIUI11 first. I've got the ROM file from the xiaomifirmwareupdater website, how do I flash it?
Click to expand...
Click to collapse
Follow this guide, assuming you've downloaded the recovery ROM.
https://c.mi.com/oc/miuidownload/detail?guide=1
If you view this on a mobile, it might be a blank page. In this case, you need to change the mobile browser to desktop mode when viewing this page.
The most simplest and right guide on the xda forum, well done! Thank You
Noob here
Are decrypted devices faster? Also please suggest stable roms. Also has anyone used 81hz extensively? Does it damage screen? Does it drain more battery?
jaydeep0712 said:
Are decrypted devices faster? Also please suggest stable roms. Also has anyone used 81hz extensively? Does it damage screen? Does it drain more battery?
Click to expand...
Click to collapse
As far as I'm aware, there shouldn't be any noticeable difference in speed. The whole data partition is encrypted as a block, so, in use, accessing files is done on an already unencrypted partition. The individual files are not encrypted/decrypted on demand on an individual basis.
All of the popular ROMs will be stable enough for daily use. Which one to go for depends on what you prefer - more AOSP, more Pixel Phone, more heavily customisable, etc., etc.
I've never gone for the screen refresh rate mods, so can't comment on them.
Thanks for replying.
Robbo.5000 said:
All of the popular ROMs will be stable enough for daily use. Which one to go for depends on what you prefer - more AOSP, more Pixel Phone, more heavily customisable, etc., etc.
Click to expand...
Click to collapse
Which custom rom do you use? Does it have any bugs (Like under screen fingerprint not working)?
jaydeep0712 said:
Which custom rom do you use? Does it have any bugs (Like under screen fingerprint not working)?
Click to expand...
Click to collapse
I'm currently using LOS. It's mostly bug free. There seems to be a current issue with wired headphones - on calls it is using the phone mic instead of the headphone mic. For my use, I don't see any other issues, but there could be other things around functionality I don't use.
Fingerprint recognition is about as good as it gets on custom ROMs. Not quite as good as MIUI, but good enough.
Thank you so much for busting so many myths, I was dying for someone to speak up but couldn't muster the courage myself. Hats off, and I support everything you said 100%.
Robbo.5000 said:
With the latest Flipkart sale, there have been a number of new owners asking a lot of old questions.
Here's a quick guide to some of the basics.
Which recovery.
----------------------------
Use the latest from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
Do not use Orange Fox unless you intend to stick with stock MIUI. Orange Fox has extra features, which are almost all aimed at MIUI, but it often causes issues flashing custom ROMs, so it's a long way from the best option if you want to use custom ROMs.
Ignore anyone who tells you to use Orange Fox when using custom ROMs.
Do I need to permanently disable encryption
-------------------------------------------------------------------------
No.
There is not a single reason to permanently remove encryption, other than personal preference.
Ignore anyone who tells you that you need to flash a DFE (disable force encrypt) script.
Should I wipe all my partitions when flashing
------------------------------------------------------------------------------
No.
When clean flashing you only need to do a factory reset in TWRP.
There is absolutely no need to wipe system or vendor partitions. Ordinarily, when flashing, there is no need to go into the advanced wipe menu. I've had this phone 15 months and have never used the advanced wipe menu and have never had any issues.
When you flash a custom ROM, it will automatically wipe system first, so you don't need to do this yourself.
When you flash a vendor file, it will automatically wipe vendor first, so you don't need to do this yourself.
Even though almost all (it may actually be all) ROM flashing instruction tell you to wipe system, it is not needed.
Ignore anyone who tells you to wipe anything more than data, cache and dalvik.
How to install a custom ROM over MIUI and remain encrypted
-------------------------------------------------------------------------------------------------
Assuming you have already unlocked the bootloader.
1 Boot into fastboot
2 Flash TWRP (fastboot flash recovery <path to TWRP file>
3 Immediately boot to TWRP (fastboot oem reboot-recovery)
4 Select Wipe Menu and Factory Reset
5 Return to Wipe Menu and Format Data
6 Return to Main Menu, then select Boot Menu
7 Select Boot to Recovery (this reboots TWRP to ensure the data partition is properly mounted after formatting)
8 Copy ROM and extras over to phone and flash them.
9 Reboot and enjoy.
Do not add any extra steps, do not miss any steps out
How to dirty flash a custom ROM update when encrypted
---------------------------------------------------------------------------------------------
1 Remove lockscreen security (this removes encryption)
2 Boot to TWRP
3 Flash the ROM update (plus vendor and firmware if the requirements for these have changed in the updated ROM)
4 Select to wipe cache and dalvik when the update finishes.
5 Reboot the ROM
6 Restore lockscreen security
How to clean flash a new custom ROM over another custom ROM
--------------------------------------------------------------------------------------------------------
1 Remove lockscreen security
2 Boot to TWRP
3 Select Wipe Menu and Factory Reset
4 Flash the ROM plus the extras you want (this includes new vendor and firmware if the requirements are different to your current ROM)
5 Reboot the ROM
6 Add lockscreen security
Click to expand...
Click to collapse
Good Day!
I installed Pixel Experience over MIUI and its stuck on Loading with Google Logo in it, it has been 30mins aprox after i first booted the device, any suggestion?
Or should i continue waiting?
Thanks in advance
XXXLR8 said:
Good Day!
I installed Pixel Experience over MIUI and its stuck on Loading with Google Logo in it, it has been 30mins aprox after i first booted the device, any suggestion?
Or should i continue waiting?
Thanks in advance
Click to expand...
Click to collapse
The first boot will take a bit longer, but only a minute or 2 at most. Something has gone wrong. Make sure you follow the guide exactly.
The most common issue is not formatting the data partition. This is not the same as wiping the partition. When formatting TWRP will ask you to type 'yes' to continue. When flashing over MIUI this is necessary to fully remove encryption before flashing.
Another common problem is wiping partitions unnecessarily. There is no need to wipe anything. Just do the factory reset, this wipes what's needed and nothing more, then format data.
Robbo.5000 said:
The first boot will take a bit longer, but only a minute or 2 at most. Something has gone wrong. Make sure you follow the guide exactly.
The most common issue is not formatting the data partition. This is not the same as wiping the partition. When formatting TWRP will ask you to type 'yes' to continue. When flashing over MIUI this is necessary to fully remove encryption before flashing.
Another common problem is wiping partitions unnecessarily. There is no need to wipe anything. Just do the factory reset, this wipes what's needed and nothing more, then format data.
Click to expand...
Click to collapse
I did the TWRP format (which prompted me to type yes to continue) and wipe data partition,but didnt wipe the partition itself, rebooted, installed pixel experience, and still same, i even got into a boot loop, which i got out to, by forcing my way out by fastboot, and reinstalled MIUI,
Im currently at MIUI, currently stable.
So Im going to try again some other time about this, when i have another available device to use while i reinstall pixel experience in Mi9T Pro
But, your guide is helpful, it failed on me probably because of a mistake I made.
Thanks anyways!
Best Regards.
hi,
in your guide, you do not have added a step for flashing the vendor.
is this intended ?
FuriousFrodo said:
hi,
in your guide, you do not have added a step for flashing the vendor.
is this intended ?
Click to expand...
Click to collapse
Flashing over MIUI, I've made the assumption that you'll be on the latest version of MIUI and the original region, which should therefore already have an appropriate vendor and firmware for the new ROM.
If you've not kept MIUI up to date or have flashed a different region of MIUI, then you may need to flash the correct vendor and firmware file(s)
Robbo.5000 said:
Flashing over MIUI, I've made the assumption that you'll be on the latest version of MIUI and the original region, which should therefore already have an appropriate vendor and firmware for the new ROM.
If you've not kept MIUI up to date or have flashed a different region of MIUI, then you may need to flash the correct vendor and firmware file(s)
Click to expand...
Click to collapse
thanks for that. i followed as you said and i was able to flash Evolution X
however, while flashing i got a warning in TWRP E:Unable to decrypt FBE device. The ROM booted fine but I think I have made a mistake. Additionally the folder I had created to transfer the ROM is gone after the phone booted.
What could be the issue ? and how to resolve this ?
FYI, I'm using Mauroonofrio's TWRP
FuriousFrodo said:
thanks for that. i followed as you said and i was able to flash Evolution X
however, while flashing i got a warning in TWRP E:Unable to decrypt FBE device. The ROM booted fine but I think I have made a mistake. Additionally the folder I had created to transfer the ROM is gone after the phone booted.
What could be the issue ? and how to resolve this ?
FYI, I'm using Mauroonofrio's TWRP
Click to expand...
Click to collapse
I've had that error a few times. It's normally from when your first boot into TWRP. All output from TWRP gets written to the same output screen, so when it is shown you are not seeing output from just the last command but for the whole session. If you had looked in more detail, you would have probably realised that the error was from before you started flashing.
With the ROM files going missing, that is a known problem. Actually anything copied before flashing gets lost. The first time it happened to me I had copied all my backed up data at the same time as the ROMs and it all got wiped. I can't remember exactly the details now, it's just something I've got used to. But if I remember correctly, the data disappears when you first boot into the new ROM. After it happened the first time, I checked in TWRP the next time, after flashing, but before booting the new ROM and the files were still there. It was only after booting to the ROM that they disappeared. (My memory is a bit vague now as it was over a year ago, but I think it might actually happen when you set up lockscreen security and the phone is encrypted in the new ROM for the first time). Maybe someone else can confirm or give the correct explanation.
Robbo.5000 said:
I've had that error a few times. It's normally from when your first boot into TWRP. All output from TWRP gets written to the same output screen, so when it is shown you are not seeing output from just the last command but for the whole session. If you had looked in more detail, you would have probably realised that the error was from before you started flashing.
With the ROM files going missing, that is a known problem. Actually anything copied before flashing gets lost. The first time it happened to me I had copied all my backed up data at the same time as the ROMs and it all got wiped. I can't remember exactly the details now, it's just something I've got used to. But if I remember correctly, the data disappears when you first boot into the new ROM. After it happened the first time, I checked in TWRP the next time, after flashing, but before booting the new ROM and the files were still there. It was only after booting to the ROM that they disappeared. (My memory is a bit vague now as it was over a year ago, but I think it might actually happen when you set up lockscreen security and the phone is encrypted in the new ROM for the first time). Maybe someone else can confirm or give the correct explanation.
Click to expand...
Click to collapse
So what you are saying is its quite normal, is it?
fearing I may have to do the whole process again, I haven't set anything up.[emoji3]
Sent from my [device_name] using XDA-Developers Legacy app
FuriousFrodo said:
So what you are saying is its quite normal, is it?
fearing I may have to do the whole process again, I haven't set anything up.[emoji3]
Click to expand...
Click to collapse
Yes, both things are normal. You should be good to go with your new ROM. No need to reinstall it.