So I was able to successfully root my AT&T HTC One X and decided I wanted to install the CM 10 ROM (1st ROM install). I did all the data backups with Titanium, downloaded the latest zip files from cyanogenMod (both the 12/13 and 12/14 nightly versions), transferred them to my phone, booted into recovery (TWRP), did a back-up, did a system wipe, flashed the ROM and then did a reboot. However, when it boots it gets stuck in the boot-up screen (bootloop) and doesn't do anything. I have read on this and it keeps saying to wipe system data again and flash the ROM again and it keeps doing this. I want to install this ROM, but I need some help. Any suggestions on what I did wrong?
Do I need to manually flash the boot.img file or should I only need to transfer the zip to my phone and install after wiping/doing a factory reset?
Well, that didn't work either as the zip file failed completely during install. So I downloaded the latest "stable" version just for giggles and wiped everything again and did an install. Just like before, the install was successful and on reboot it locks up on the boot screen. I am at a loss on what to do.
Hey buddy, i had cm10 running on my HOX, when i did it i had to flash the boot img through fastboot as well.
I found a tutorial on youtube by cursed forever helpful, sorry I'd post a link but my thread counts not high enough yet
Hi All,
Last week, I flashed my LG Nexus 4 (16GB) phone with stock Android 4.4 (Official Image), before that I was on CyanogenMod 10.1.3 Stable.
Now, for some reason I didn't like the stock 4.4 and tried to Flash back my CyanogenMod 10.1.3 from CWM "Install ZIP" but the problem I'm facing is that it CyanogenMod doesn't boot, hangs on "Spiral Splash Screen". Then I tried Flashing CM 10.0 stable, still loops into boot forever and at times boots (after 15-20 minutes of booting on spiral splash screen) and doesn't recognise SIM card, Camera, Storage, WIFI or anything.
Then after getting fed up with this I tried flashing MIUI V5. This also takes a 15-20 to boot and fails to recognise - SIM, WiFi, Camera etc.
So lastly like a loser I flashed back my Android 4.4 it works fine.
I've my boot-loader in unlocked state.
and Yes before flashing CM or MIUI, I did - wipe data/factory, wipe cache, wipe dalvik cache from CWM Recovery.
So I want to get back into CyanogenMod 10.1 stable. Help me out with this.
Restoring Nexus 4
prakharprasad said:
Hi All,
Last week, I flashed my LG Nexus 4 (16GB) phone with stock Android 4.4 (Official Image), before that I was on CyanogenMod 10.1.3 Stable.
Now, for some reason I didn't like the stock 4.4 and tried to Flash back my CyanogenMod 10.1.3 from CWM "Install ZIP" but the problem I'm facing is that it CyanogenMod doesn't boot, hangs on "Spiral Splash Screen". Then I tried Flashing CM 10.0 stable, still loops into boot forever and at times boots (after 15-20 minutes of booting on spiral splash screen) and doesn't recognise SIM card, Camera, Storage, WIFI or anything.
Then after getting fed up with this I tried flashing MIUI V5. This also takes a 15-20 to boot and fails to recognise - SIM, WiFi, Camera etc.
So lastly like a loser I flashed back my Android 4.4 it works fine.
I've my boot-loader in unlocked state.
and Yes before flashing CM or MIUI, I did - wipe data/factory, wipe cache, wipe dalvik cache from CWM Recovery.
So I want to get back into CyanogenMod 10.1 stable. Help me out with this.
Click to expand...
Click to collapse
Hello Prakhar,
I would suggest you to first download the official image of Nexus 4 for android 4.3 and flash it from https://developers.google.com/android/nexus/images and then you can try to flash CM 10.1.3 from the CWM Recover Console. Hope this helps!
I would also like to point you out to https://developers.google.com/android/nexus/drivers which contains drivers for your phone's camera, etc. you can download those binary and flash it one by one through your recovery console, which might fix your issues.
It worked !
Downgraded to stock 4.2.2 then Flashed CM 10.2 RC1 from CWM Recovery !
Thanks a lot U3ViaGFsbyA6UA==
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
So this is my first post, but whatever.
So it's safe to say I screwed up, I accidentally deleted my stock (rooted) Samsung OS. I somehow managed to download Paranoid Android 6.0.1 onto the Samsung Galaxy S3 GT-I9300 I received. I heavily dislike Paranoid Android, and I would like to give Cyanogen 14.1 a shot. The problem is since I wiped everything, every time I do a factory reset for my device, it goes into a bootloop, even if I flashed CM 14.1.
I have TWRP installed, if that helps, and all files (that I know of) are installed on my computer (Odin, CM14.1 ZIP, and Paranoid is backed up).
I'd like to thank everyone who even comes and reads this thread, and I'd be very grateful if I managed to get CM 14.1 on the Samsung Galaxy S3 GT-I9300.
Which version of TWRP is installed? If you have 2.87, try 3.02. Are you performing a full system and data wipe before installing cm14.1?
Hi bro
I am agree with the first reply to you.
All You need the official CM14.1 ROM
Download here https://download.cyanogenmod.org/?device=i9300
And then download Gapps for android 7.1 pico
Download here http://opengapps.org/
If yoy havn't twrp recovery ! Download it from here
https://dl.twrp.me/i9300/
The file end with (tar) it flashing with Odin.
And the file end with (img) it is update from other version to new with Flashify app (you can find the app in playstore free)
Now You have all requirements files
Let's flashing Your device:
Move the files to Ext.sdcard
Make sure you have 80% battery charge
Then reboot your device to (recovery mode)
Turn off your device and Push (Power+home+volume up) keys at the same time for 5 sec untill u see the recovery icon
Now go to wipe your phone choose advance wipe check the dalvilk + cache + system + data + inernal storage ,, done
Now go back and choose install
Search to your Ext.sdcard then choose the CM14.1 at the same time click on Add more zips
And choose Gapps 7.1 pico
Now swipe to flash
Wait to flash finish and then click on Reboot system
Done
Good luck
audit13 said:
Which version of TWRP is installed? If you have 2.87, try 3.02. Are you performing a full system and data wipe before installing cm14.1?
Click to expand...
Click to collapse
I'm using the latest TWRP, I made sure to install the latest one, and I'm performing a full data and system wipe before I install CM14.1. My question is does it HAVE to be on an external SD card, because I just port it over to a folder in my internal SD card.
It can be installed from the internal memory. Simplest way would be to boot into TWRP, mount storage, copy over CM and gapps, and flash.
Maybe try TWRP 2.87?
audit13 said:
It can be installed from the internal memory. Simplest way would be to boot into TWRP, mount storage, copy over CM and gapps, and flash.
Maybe try TWRP 2.87?
Click to expand...
Click to collapse
I've tried to do that multiple times, but everytime I try it, the S3 goes into a bootloop.
Due to the bootloop issue, I would flash a stock ROM with Odin, perform a factory wipe from stock recovery, and then see if the phone will boot properly.
Is the phone a gt-i9300 in download mode?
audit13 said:
Due to the bootloop issue, I would flash a stock ROM with Odin, perform a factory wipe from stock recovery, and then see if the phone will boot properly.
Is the phone a gt-i9300 in download mode?
Click to expand...
Click to collapse
Yeah, I managed to install the stock OS. I also tried to install CM14.1 again, following the instructions to the letter, but still no CM build. I have no idea what I'm doing wrong, since I've read multiple threads on XDA and the CM site.
Not exactly sure what you mean by in download mode, since I'm new to all this rooting business.
You need download mode to flash a stock ROM; otherwise, Odin can't install a stock ROM.
audit13 said:
You need download mode to flash a stock ROM; otherwise, Odin can't install a stock ROM.
Click to expand...
Click to collapse
Oh if that's the case, then yes. I put it in Odin mode to flash the stock ROM.
Okay, just to confirm but these are the major steps you took:
flashed the latest stock ROM to the phone;
flashed the latest tar version of TWRP using Odin;
booted into TWRP and copied CM14 to the internal memory or an SD card;
wipe data, system, and cache in TWRP;
flash CM14 in TWRP and rebooted.
Yup, those are the exact steps I took. I think I'm just going to tinker around with the Samsung a little longer, until I manage to brick it, or I'll just continue doing research. I'm already happy I managed to get out of a boot loop on my own, with and without OS.
Are you in Canada? Where did you get the i9300? The i747m is sold in Canada and the i747 is sold in the USA.
audit13 said:
Are you in Canada? Where did you get the i9300? The i747m is sold in Canada and the i747 is sold in the USA.
Click to expand...
Click to collapse
My dad got it for his work during his visit in Turkey, is that a factor during flashing of new OS's? What surprises me is that I could install Paranoid Android 6.0.1 onto it without an OS with little or no problem.
A pre-existing OS on the phone is not a requirement to flash a custom ROM.
As long as the ROM is for the i9300, you should be fine.
audit13 said:
A pre-existing OS on the phone is not a requirement to flash a custom ROM.
As long as the ROM is for the i9300, you should be fine.
Click to expand...
Click to collapse
I made sure it was for the i9300. I'm confused to where it doesn't work because I would see the CM battery charging logo, but when I wanted it to boot, it kept bootlooping for 10 minutes on end. The longest I've let it run was whilst I was sleeping, 8 hours, still nothing.
Maybe try a different version of CM14.1 or a different version of TWRP.
audit13 said:
Maybe try a different version of CM14.1 or a different version of TWRP.
Click to expand...
Click to collapse
I'll give those options a shot. I'll try out clockwork and see. I guess I'll keep going until I brick it. Thanks for aiding me, and enjoy having a happy new year.
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.