How to flash Android 11 Custom ROM coming from Android 9 - Xiaomi Mi A1 Questions & Answers

Hi, I'm on stock ROM Android 9 and want to update to Android 11 custom ROM. Is there any detailed guide on how to flash Android 11 AOSP based ROM from Stock Android 9?
I've tried flashing with TWRP and it's shown "unable to mount /vendor" and "unable to mount storage" warning. Proceed to flashed a ROM anyway and TWRP said "success" but when I tried to reboot system it says "no OS is installed are you sure you want to reboot?" or something like that lol. I rebooted and got bootloop, restored my stock ROM and here I am lol.
I clearly missed something during the flashing and hoping someone could tell me here. Any help will be much appreciated. Thanks in advance.

kusumalaga said:
Hi, I'm on stock ROM Android 9 and want to update to Android 11 custom ROM. Is there any detailed guide on how to flash Android 11 AOSP based ROM from Stock Android 9?
I've tried flashing with TWRP and it's shown "unable to mount /vendor" and "unable to mount storage" warning. Proceed to flashed a ROM anyway and TWRP said "success" but when I tried to reboot system it says "no OS is installed are you sure you want to reboot?" or something like that lol. I rebooted and got bootloop, restored my stock ROM and here I am lol.
I clearly missed something during the flashing and hoping someone could tell me here. Any help will be much appreciated. Thanks in advance.
Click to expand...
Click to collapse
1. Flash rom
2. Reboot to recovery
3. Flash gapps
4. Reboot

Related

[Q] D803 Help!

Hello XDA Developers,
I had a device that was rooted on stock rom and recovery. What happened was that an OTA was installed and it went to the "boot verify certification" screen. I had to install Ubuntu to get TWRP running again.
I'm able to boot into TWRP, and I tried installing different ROMs, using adb sideload, from Stock ROM, ParanoidAndroid, and Madri-ROM.
The first one was able to install, but when I reboot the phone, I get stuck on the LG logo. I wait for an hour and it still does not do anything.
So now I try the other two custom ROMs, and I get an error saying "E:Error executing updater binary in zip "... .zip".
Then it reads "Error flashing zip '... zip'.
My question is: What else can I do to get this phone working again? I would like stock ROM, and preferably stock recovery back (Recovery is secondary).
Thanks in advance,
DaAznMan
Note: When I use adb sideload, the .zip file that gets transferred becomes a file called 'sideload.zip'. Is that correct? If not, what do I need to do to fix it?

[GUIDE] How to get CM 14.1 working.

Hi,
So I have created this thread just because I can see many people creating new threads as after flashing CM 14.1, their phone doesn't boot up. So for all those who are going to flash CM 14.1 or have already flashed it and can't get it working, this thread is for you.
What you will need:
1. Rooted OnePlus X (Obviously)
2. Custom Recovery (TWRP recommended)
3. Latest CM 14.1 build
4. Arsenic Kernel or BlackReactor Kernel
So this is how you get CM 14.1 working on your OPX (make sure your battery is above 80% just to be sure that nothing will go wrong considering battery's point of view)
Make sure you have backed up everything before performing the following steps as the process will wipe your data completely. (I would recommend to take a Titanium backup of all user apps and then taking a nandroid backup of system and data)
1. Download the required files and place them in your SD Card or internal storage
2. Reboot your device into recovery
3. Go to wipe, and swipe to factory reset (Note! This will completely wipe all the data from your device including app data and SMS! This won't wipe the contacts but just to be safe, have a backup of all your contacts)
4. Go to Wipe again, and go to Advanced wipe, select the following partitions - System, Cache, Dalvik cache. Swipe to wipe (Note! Make sure you have a backup of the System as this will wipe the Operating System from your phone!) Although this step isn't necessary, I like to do it.
5. Go to install, and direct to the location where you have saved the CM 14.1 zip file and the kernel. Select the files, and swipe to flash.
6. If you want anything else in your system, direct to that location, select the zip file, and swipe to flash. (Note! You need not flash the SuperSU zip file as CM offers Root access in developer options)
7. Reboot your system and wait for it to boot.
Viola! Your device is now running official CM 14.1 nightly.
Hope this helps! ?
Downloads:
1. Latest CyanogenMod nightly - found here https://download.cyanogenmod.org/?device=onyx
You can have any version of the nightly as long as it is CM 14.1
2. Arsenic Kernel R32 (or R31) - http://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Open the above thread and follow the guide
OR
Black Reactor kernel v1.0 - http://forum.xda-developers.com/oneplus-x/development/kernel-blackreactor-kernel-oneplus-x-t3460989
-Reserved-
Good Evening, @aamodjoshi23 THX a Lot. You are my Hero. Finally it works.
greetings
If you're facing some Error 7 while trying to flash cm 14.1, you can try updating the bootloader following this
http://forum.xda-developers.com/showpost.php?p=69267239&postcount=2560
I used the Oxygen OS 3.13 full ROM as recommended, edited updater-script (following those instructions)
Immediately after flashing the OOS 3.13 rom, you don't have to reboot.
I immediately flashed twrp 3.0.3 original from https://dl.twrp.me/onyx/
I then rebooted into twrp 3.0.3 (using the reboot button in twrp, then bootloader)
Then I installed (in this order):
cm 14.1 (https://download.cyanogenmod.org/?device=onyx)
arsenic kernel (as recommended above)
opengapps
Not sure if this step is necessary, but I wanted to let twrp patch the rom to not overwrite twrp so I rebooted into twrp again (using reboot --> bootloader in twrp)
Then I used reboot --> system
First boot took a while, but now I have nougat!!
kenel zip every time
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
allons-y said:
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
Click to expand...
Click to collapse
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
aamodjoshi23 said:
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
Click to expand...
Click to collapse
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
shashanksachdeva said:
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
Click to expand...
Click to collapse
First of all we need more info about your current ROM recovery etc.
Fap4k said:
First of all we need more info about your current ROM recovery etc.
Click to expand...
Click to collapse
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
shashanksachdeva said:
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
Click to expand...
Click to collapse
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Fap4k said:
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
This is because you flashed wrong recovery twrp 3.0.3 is for new bootloader and you are on old bootloader..that's why it all happened..so you just need to flash old recovery..then follow given link to upgrade bootloader and recovery.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
I've got a good news and bad news for you.
The bad news is, no one has the older 2.8.x TWRP image files and there are no threads that have the download links for the older version of TWRP. So you're stuck and you have lost your recovery. You have lost everything... Having no recovery means you can't do a lot of things like factory reset, any wipe of a partition, you won't be able to update your system, you won't be able to flash zip files to enhance your experience and many more... I'm sorry my friend...
The good news is, I've got you covered. I had saved the older TWRP so that if anyone one day would need that recovery image, I would be able to help them.
Download the older TWRP from here : https://drive.google.com/file/d/0B2Ms-zaNd3SiTmpxX0UtYUV2R1k/view?usp=drivesdk
Flash it. You should get back your recovery.
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Fap4k said:
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Click to expand...
Click to collapse
using resurrection remix marshmallow 6.0...
Plush suthar said:
using resurrection remix marshmallow 6.0...
Click to expand...
Click to collapse
Did you ever updated bootloader?
If not than update your bootloader and install latest recovery!!
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
By stuck on boot, I didn't know you meant that it showed only the OnePlus logo and not even powered by Android.
In that case, follow this guide to update your bootloader :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917

Can't boot to recovery.

Phone is Lenovo A6000, not plus. I installed multiple TWRPs, 3.1.0 and 2.9 something.
I even installed CWM, still couldn't boot to the recovery.
Now, I know how to flash with fastboot, and I know how to boot. Booting doesn't work at all, it says "booting" and never finishes.
Flashing says "okay" and I reboot, do a reboot to recovery, and I get put into bootloader/fastboot.
Any help? I just bought the phone today, no one messed with it.
Edit: Nevermind. CWM installed. How do I install TWRP, so it works? Also, forgot to mention that the phone has the latest stock rom, 4.4.4.
Edit#2: While trying to install "TWRP-3.1.0-Lenovo-A6000.img",
I got an error.
"Can't open /tmp/update.zip (bad)"
"Installation aborted."
Edit#3: Same error with multiple TWRP images.
First of all the twrp 3.1.0 is meant for nougat roms. Since you are flashing that recovery on KitKat rom which it won't support. So first try updating phone to stock lollipop. Then flash twrp 2.8. then take a complete backup(most important) and save it on SD card. After that flash any rom you want. If you are flashing marshmallow or nougat rom then after flashing rom flash 3.1.0 twrp.
I have long ago (10 minutes after last edit) fixed the problem already by flashing stock firmware through some weird software, and then started updating to latest lollipop firmware, and then installed TWRP 3.1 and then installed RR android version 7.1.2. But, thank you for trying to help. I hereby ask a moderator to close the thread because the problem was resolved. Thank you.

Latest oreo roms and some problems...

When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:
Which recovery you using
poyraz4558 said:
When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:
Click to expand...
Click to collapse
Please provide specifics of ROM and TWRP Version. Did you load mods? Did you use custom kernel?
I installed this recovery for bootleggers 8.1 rom,
https://androidfilehost.com/?fid=673956719939820462 (twrp 3.2.1.0 It works well),
then I've installed Orangefox recovery for try and I used for long time without any problem,
later I flashed this recovery for Pixel Experience rom
https://androidfilehost.com/?fid=1322778262904027766 (twrp 3.2.3.0),
installed without a problem but a long time stuck in google logo, I rebooted three times a long press power button and the phone opened normally
No problem when using the phone but all times error on recovery.. such as 'vendor, invalid argument, mount error.
Always these errors during the rom installation and wiping..
Now is stock rom installed, I think there are some changes in the new rom because such problems did not happen before,
thank you for your answers and developers
poyraz4558 said:
I installed this recovery for bootleggers 8.1 rom,
https://androidfilehost.com/?fid=673956719939820462 (twrp 3.2.1.0 It works well),
then I've installed Orangefox recovery for try and I used for long time without any problem,
later I flashed this recovery for Pixel Experience rom
https://androidfilehost.com/?fid=1322778262904027766 (twrp 3.2.3.0),
installed without a problem but a long time stuck in google logo, I rebooted three times a long press power button and the phone opened normally
No problem when using the phone but all times error on recovery.. such as 'vendor, invalid argument, mount error.
Always these errors during the rom installation and wiping..
Now is stock rom installed, I think there are some changes in the new rom because such problems did not happen before,
thank you for your answers and developers
Click to expand...
Click to collapse
Okay... I'd recommend one thing.
Install the custom ROM. Then follow flashing procedure and do read the new FAQ posted by the devs. And after that... Try to reflash the recovery.img by pressing install image option. After this... If the problem persists, try to follow the procedure again and check if your recovery image isn't corrupt. Plus don't use the recovery from TWRP.ME
I have a recovery that can solve this problem but you can't restore ROMs you backed up
Phantom Slayer04 said:
Okay... I'd recommend one thing.
Install the custom ROM. Then follow flashing procedure and do read the new FAQ posted by the devs. And after that... Try to reflash the recovery.img by pressing install image option. After this... If the problem persists, try to follow the procedure again and check if your recovery image isn't corrupt. Plus don't use the recovery from TWRP.ME
Click to expand...
Click to collapse
thanks, I understand
I did actually try a second time, just flashed pixel experience rom and twrp 3.2.3.0 recovery on the stock rom - recovery.. same errors are happening and this problems improve only when I install stock rom with QPTS.. I will do clean installation in a short time again, just wonder why there is so much vendor error on recovery...
poyraz4558 said:
thanks, I understand
I did actually try a second time, just flashed pixel experience rom and twrp 3.2.3.0 recovery on the stock rom - recovery.. same errors are happening and this problems improve only when I install stock rom with QPTS.. I will do clean installation in a short time again, just wonder why there is so much vendor error on recovery...
Click to expand...
Click to collapse
Did you wipe the partitions? Did you format data partition?
Phantom Slayer04 said:
Did you wipe the partitions? Did you format data partition?
Click to expand...
Click to collapse
yes I did, including vendor..Today I searched the topics in the forum; return to old rom is not recommended after installing the new rom, I see similar troubles in rom forums..
poyraz4558 said:
yes I did, including vendor..Today I searched the topics in the forum; return to old rom is not recommended after installing the new rom, I see similar troubles in rom forums..
Click to expand...
Click to collapse
If you want to install latest update roms then read this FAQ:https://forum.xda-developers.com/showpost.php?p=77872447&postcount=2325:confused:
if you want to revert to old roms then you have to flash stock nougat rom using qfil and install twrp 3.2.1.0 and install old roms
don't do it wrongly otherwise you will get updater error 7 or can't mount vendor, etc,
Sudhar123 said:
If you want to install latest update roms then read this FAQ:https://forum.xda-developers.com/showpost.php?p=77872447&postcount=2325:confused:
if you want to revert to old roms then you have to flash stock nougat rom using qfil and install twrp 3.2.1.0 and install old roms
don't do it wrongly otherwise you will get updater error 7 or can't mount vendor, etc,
Click to expand...
Click to collapse
Thank you, I learned later that.. That's why i'm using an old rom because sometimes I can't any process on recovery, There are too many errors..
poyraz4558 said:
When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:
Click to expand...
Click to collapse
You should be on latest nougat that is with november security patch. All rom after 14/10/2018 should flash with latest twrp that is 3.2.3.0. all roms before that should be flashed with twrp 3.2.1.0.
sk.vyshak said:
You should be on latest nougat that is with november security patch. All rom after 14/10/2018 should flash with latest twrp that is 3.2.3.0. all roms before that should be flashed with twrp 3.2.1.0.
Click to expand...
Click to collapse
Ok..Which sections will be deleted on twrp 3.2.3.0 during wipe, is vendor partition included ?
poyraz4558 said:
Ok..Which sections will be deleted on twrp 3.2.0.3 during wipe, is vendor partition included ?
Click to expand...
Click to collapse
The thing is with new twrp there is decryption support which was lacked in old. Vendor partition is present in both i think. All the new roms are encrypted by default

Flashed TWRP and Lineage OS but getting error while booting

Hi All,
I was able to successfully install TWRP and get Lineage OS installed but when I am booting initially I get an error message, it waits 5 seconds and then boots into the O/S.
https://i.imgur.com/qTzytc5.jpg
Is this because it's a custom rom? If not can someone let me know what I did wrong? Also I noticed that the phone dialer isn't working and see others having a similar issue. Are there any custom roms where this is working? If not and I want to go back to the stock rom, can I just apply the update.zip via TWRP?
Thanks for the help,
Nick
npolite said:
Hi All,
I was able to successfully install TWRP and get Lineage OS installed but when I am booting initially I get an error message, it waits 5 seconds and then boots into the O/S.
https://i.imgur.com/qTzytc5.jpg
Is this because it's a custom rom? If not can someone let me know what I did wrong? Also I noticed that the phone dialer isn't working and see others having a similar issue. Are there any custom roms where this is working? If not and I want to go back to the stock rom, can I just apply the update.zip via TWRP?
Thanks for the help,
Nick
Click to expand...
Click to collapse
if you can apply update.zip from twrp and the phone dialing does not work "only in some mobile operators" and on that adventecia of the screen in image that you uploaded, that error is because you started twrp for the first time without flashing root and rom, why root and rom has integrated dm-verity disabled
dm-verity boot: is responsible for verifying the first boot system partitions, such as boot, data, system etc ...
there is a file with name no-verity-opt-encrypt-6.0.zip that serves to deactivate dm-verity boot, but the adventecia the only way to remove it is with stock rom, back flashing the stock rom.

Categories

Resources