Related
so i just doing a clean install of the beta 3 rom, i did follow the instruction that written in the thread but some how after installing the update when i'm about to reboot into system it keeps rebooting into the recovery. so i decided to clean wipe and re-flash the rom, and some how it says that there's no rom installed. i've tried to install other custom rom like, LOS 15 and Liquid Remix, but it's still the same, keep booting to recovery and showing that there's no rom installed. plz help...
Go to twrp > wipe > format data > yes
Then transfer oos OB 3 to your phone, use adb push command is better than copy paste(not sure why because sometimes i copy pasted into phone, sometime it bootloop or storage not recognised)
Flash it, then flash magisk 15.2. then reboot. It should work fine. Unless you use a not compatible twrp version.
thanks for ur solution before, but can u tell me the compatible twrp is, cuz i'm using the twrp 3.2.1 by blu spark and it keeps booting into recovery
You need to flash no verity zip. If you are decrypted.
"You need to flash no verity zip. If you are decrypted. "
Thanks god for this comment, use about 2 hours digging around forums and re-flashing, wiping, trying diffrent TWRPs, different roms. And when I found this comment I just isntalled the zip and it worked within 10 seconds.
I'm new to this device and already I'm extremely confused. I tried flashing TWRP the old school method and found out very fast that it was a no go. Upon reading around, I fount the following guide and booted TWRP:
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
The problem? I can install DotOS, but as soon as I try to flash the GAPPS, I get an error (it claims that I am on 7.1.2, but I'm using the latest DotOS version which is 8.1.0 based). Since from what I understand the recovery seems to be tied to the boot.img (like the Sony Ericsson Xperia Play), I believed simply rebooting into recovery would help. Unfortunately this boots into stock recovery for 8.0.0 (mind you I was on 8.1.0 stock). Upon reading around on how to install TWRP on the phone itself, I found this thread:
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
This is the bigger headache. After following the instructions which are clear as day, I encounter similar issues to half of the replies in that thread. Another issue is that there is no explanation on whether you should be on stock first or...? Secondly, nothing is said on which "slot" (a or b) to flash your desired rom. So my default slot was b, I switched to a to flash the TWRP installer and so on as per instructions. I then assume I am to switch back to slot b for my rom to be installed. The issue is that after trying to install the GAPPS, I am faced with the issue again of the 7.1.2 detected. The only way to get around this is to flash it in slot a, but then the device will never boot. I'm very confused?
Use this twrp. Then you flashed twrp, wipe, install ROM, reboot into recovery again and flash gapps.
Crossvxm said:
I'm new to this device and already I'm extremely confused. I tried flashing TWRP the old school method and found out very fast that it was a no go. Upon reading around, I fount the following guide and booted TWRP:
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
The problem? I can install DotOS, but as soon as I try to flash the GAPPS, I get an error (it claims that I am on 7.1.2, but I'm using the latest DotOS version which is 8.1.0 based). Since from what I understand the recovery seems to be tied to the boot.img (like the Sony Ericsson Xperia Play), I believed simply rebooting into recovery would help. Unfortunately this boots into stock recovery for 8.0.0 (mind you I was on 8.1.0 stock). Upon reading around on how to install TWRP on the phone itself, I found this thread:
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
This is the bigger headache. After following the instructions which are clear as day, I encounter similar issues to half of the replies in that thread. Another issue is that there is no explanation on whether you should be on stock first or...? Secondly, nothing is said on which "slot" (a or b) to flash your desired rom. So my default slot was b, I switched to a to flash the TWRP installer and so on as per instructions. I then assume I am to switch back to slot b for my rom to be installed. The issue is that after trying to install the GAPPS, I am faced with the issue again of the 7.1.2 detected. The only way to get around this is to flash it in slot a, but then the device will never boot. I'm very confused?
Click to expand...
Click to collapse
To install twrp, use twrp 3.2.3 from abishek (lineageOS) or from cosmicdan.
This phone have slot a/b. For installing twrp it doesn't matter from which slot you install as it will install in the boot partition, not in system.
First do facory reset, you don't have to be on stock.
For custom rom zip if you are in slot a it will be installed in the slot b. After installing rom install twrp again as it's deleted when you install new rom and change slot, reboot and install gapps according with the rom 8.1 or 9.0 and magisk, it installs on the same slot..
Cosmicdan twrp have an option to install rom zip on the same slot and have a survival option for twrp, so you don't have to install twrp when you install a rom or a new kernel.
ccalixtro said:
Use this twrp. Then you flashed twrp, wipe, install ROM, reboot into recovery again and flash gapps.
Click to expand...
Click to collapse
This is the link for twrp:
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
Reboot recovery after u flash rom, then flash gapps,magisk
Hi All, I have been reading various threads here and searching on Google for finding a method that truly works for successfully installing a custom ROM, getting TWRP installed and rooting with Magisk. So far, all I have found are numerous and usually contradictory methods and about 7 or 8 different versions of TWRP (so which one is completely stable and working properly?). I have tried several methods over the past two weeks and none of them are working completely.
Sometimes, I'll get a version of TWRP installed, but then trying to reboot to recovery results in a "system has been destroyed" image. Or I'll succeed in getting a custom ROM installed, but Gapps will fail with error 20 or error 70 or there's not enough space on the system partition (and I'm just trying to install the Pico version). Even I double check that the Gapps version matches the ROM version I've used, but still get an error 20 displayed.
From what I had read on numerous threads, it seemed like CosmicDans TWRP would be the one I should go with. I downloaded both of his files (the fastboot image and the zipped installer) and fastboot his "boot-recovery.img" that was specifically for fastboot only and from that recovery, I installed his "TWRP-Installer-3.2.1-with-Tissot-Manager-2.5.zip". Everything appeared as if successfully installed as per the logs, but immediately upon attempting to reboot to recovery, I get the "system has been destroyed" image.
What I want to do is:
Get a working custom ROM (preferably Pie) installed
Install Gapps
Install a working TWRP (that will not display "system has been destroyed" whenever trying to boot to recovery)
Finally, install Magisk and root my phone
Can anyone suggest a site or link or a post somewhere that would explain everything correctly and is actually working? This has been a very frustrating experience. I'm almost sorry that I even bought the Mi A1. Never had any problems installing custom ROMs or rooting the OnePlus devices. All I'm left with currently is an expensive paperweight.
Thanks so much!
Cheers
From your description, I'm certain that you do this on a Pie stock rom right? the installer never work on Pie stock and will cause system destroy. Just hotboot TWRP. And for the Gapps, I think it's due to the time you install it. From my experience, install Gapps after rom and before Magisk usually work. Install after magisk or custom kernel will somehow cause the same issue that you described.
Oh, in case you want to install LineageOS, you have to come to the LOS16 thread and download the TWRP from there, it's the only TWRP that can install LOS16.
Never_Sm1le said:
From your description, I'm certain that you do this on a Pie stock rom right? the installer never work on Pie stock and will cause system destroy. Just hotboot TWRP. And for the Gapps, I think it's due to the time you install it. From my experience, install Gapps after rom and before Magisk usually work. Install after magisk or custom kernel will somehow cause the same issue that you described.
Oh, in case you want to install LineageOS, you have to come to the LOS16 thread and download the TWRP from there, it's the only TWRP that can install LOS16.
Click to expand...
Click to collapse
Thank you for your reply. When I first started the process to change to a custom ROM, I was on stock Pie. But one of the times I was wiping the device after one more problem, I accidentally also wiped Internal Storage as well. I didn't have much there since I had already backed some things up in advance. Now it's virtually empty. The steps I take are:
1. Hotboot TWRP
2. Install Custom ROM
3. Hotboot TWRP again
4. Install Gapps
This is where I usually have some problem. It's the process of installing Gapps that creates some error.
I also did attempt to install LineageOS 16 using the TWRP recovery that was linked in the post. Follow the instructions precisely I believe and now when it's time to install Gapps, I get error 64. I can't understand why. I am attempting to install "open_gapps-arm64-9.0-nano". This should be compatible with the Mi A1 with LineageOS 16 from what I am able to tell.
No matter what TWRP version I use, no matter what custom ROM I try, no matter what steps I take, there is always some issue that prevents me from completing any installation. But the abundance of so many conflicting posts don't help either. One post will state to use a specific TWRP and certain steps; another post will suggest completely different steps using another TWRP; and yet another post will provide different steps still. In some instances, there will be steps listed in the script on the phone regarding the next steps after the ROM installation that are completely different then the steps provided in the post for that ROM in the forum.
It would just be tremendously helpful to get some instructions that actually do work. As of now, I'm about ready to dump this phone in the trash bin. It's horrible. I can't even tell if it might be decent eventually since I never can get anything installed.
Thanks again for your reply Never_Sm1le.
Cheers.
There is no permanent TWRP install for android 9 on MiA1 as far as i know.
Hotboot works just perfect.
Brianne8 said:
Thank you for your reply. When I first started the process to change to a custom ROM, I was on stock Pie. But one of the times I was wiping the device after one more problem, I accidentally also wiped Internal Storage as well. I didn't have much there since I had already backed some things up in advance. Now it's virtually empty. The steps I take are:
1. Hotboot TWRP
2. Install Custom ROM
3. Hotboot TWRP again
4. Install Gapps
This is where I usually have some problem. It's the process of installing Gapps that creates some error.
I also did attempt to install LineageOS 16 using the TWRP recovery that was linked in the post. Follow the instructions precisely I believe and now when it's time to install Gapps, I get error 64. I can't understand why. I am attempting to install "open_gapps-arm64-9.0-nano". This should be compatible with the Mi A1 with LineageOS 16 from what I am able to tell.
No matter what TWRP version I use, no matter what custom ROM I try, no matter what steps I take, there is always some issue that prevents me from completing any installation. But the abundance of so many conflicting posts don't help either. One post will state to use a specific TWRP and certain steps; another post will suggest completely different steps using another TWRP; and yet another post will provide different steps still. In some instances, there will be steps listed in the script on the phone regarding the next steps after the ROM installation that are completely different then the steps provided in the post for that ROM in the forum.
It would just be tremendously helpful to get some instructions that actually do work. As of now, I'm about ready to dump this phone in the trash bin. It's horrible. I can't even tell if it might be decent eventually since I never can get anything installed.
Thanks again for your reply Never_Sm1le.
Cheers.
Click to expand...
Click to collapse
Your reply makes me want to stay on LOS 15.1 even more. So many weird problems happen in LOS 16
I followed all the instructions of Resurrection Remix and TWRP is installed and magisk works perfect.
Hello friend, I am currently on Lineage OS 16.0 with Magisk, Opengapps and TWRP installed. I can boot to recovery with no problems at all; in fact, I used the flashed TWRP to install Magisk.
Here are the steps I took:
Download the TWRP boot img and TWRP installer by CosmicDan (Link below)
Copy the custom rom ZIP, TWRP installer, Magisk installer and Gapps into your SD card
Reboot your device to bootloader
Boot into TWRP using
Code:
fastboot boot boot-recovery.img
do NOT flash via fastboot
Go to Wipe>Advanced Wipe and wipe System, Dalvik, Data, Internal Storage
Press the home button and proceed to flashing the custom rom ZIP
After flashing, reboot to BOOTLOADER then do step 4 again
Flash Gapps, TWRP Installer, then Magisk Installer. You should flash TWRP first before Magisk
Reboot to system and you're good to go
Note that if you are installing Lineage OS and wish to receive nightly OTA updates, having an installed TWRP as your recovery might result in a bootloop after updating. Also, if you want to manually flash the nightly update, you need to boot to the TWRP variant of @flex1911 as flashing lineage using other TWRP will result in an error. I suggest not installing TWRP when using Lineage OS.
(Source: [ROM][OFFICIAL] LineageOS 16.0 for Xiaomi Mi A1)
Regarding your problem with flashing, try to check which slot you are currently in by going to TWRP>Reboot. Keep in mind that when you install a rom, it will always be installed to the inactive slot. For example if you are in slot A, your rom will be installed in slot B. After rebooting, your current active slot will be where the rom is installed. When installing Gapps or any addons, check the slot first. However, when flashing TWRP installer, it will patch both boot_a and boot_b and this is the reason why you need to install twrp first before magisk as TWRP also modifies the boot image.
Download:
Bootable TWRP
TWRP Installer
(Both files by @CosmicDan)
Cheers mate!
rexendz said:
Here are the steps I took:
Download the TWRP boot img and TWRP installer by CosmicDan (Link below)
Copy the custom rom ZIP, TWRP installer, Magisk installer and Gapps into your SD card
Reboot your device to bootloader
Boot into TWRP using
Code:
fastboot boot boot-recovery.img
do NOT flash via fastboot
Go to Wipe>Advanced Wipe and wipe System, Dalvik, Data, Internal Storage
Press the home button and proceed to flashing the custom rom ZIP
After flashing, reboot to BOOTLOADER then do step 4 again
Flash Gapps, TWRP Installer, then Magisk Installer. You should flash TWRP first before Magisk
Reboot to system and you're good to go
Click to expand...
Click to collapse
Thanks for the lengthy reply. However, those steps do not work as you have described. Since, if I wipe Internal Storage (as per your step 5), I just deleted all the files I copied previously in Step 2. What I did, was wipe everything, *then* copied all the files and tried to install. As soon as it try to install Gapps, I get Error 64 again. I am absolutely using "open_gapps-arm64-9.0-nano" and it always fails. I have attempted 11 or 12 times already, using different slots, using different dates of "open_gapps-arm64-9.0-nano" and ALWAYS Error 64. I don't know any other version of Gapps I should be trying. The arm64 versions never will work for me.
I give up. I'll just have to stick with stock ROM. No custom ROMs will work for me no matter which one I use or which version of TWRP I use. I already wasted too much of my life with this garbage phone.
ccalixtro said:
I followed all the instructions of Resurrection Remix and TWRP is installed and magisk works perfect.
Click to expand...
Click to collapse
Hi,
Which version of TWRP did you use? There's too many. I don't know which one is considered to be the right one.
Brianne8 said:
Thanks for the lengthy reply. However, those steps do not work as you have described. Since, if I wipe Internal Storage (as per your step 5), I just deleted all the files I copied previously in Step 2. What I did, was wipe everything, *then* copied all the files and tried to install. As soon as it try to install Gapps, I get Error 64 again. I am absolutely using "open_gapps-arm64-9.0-nano" and it always fails. I have attempted 11 or 12 times already, using different slots, using different dates of "open_gapps-arm64-9.0-nano" and ALWAYS Error 64. I don't know any other version of Gapps I should be trying. The arm64 versions never will work for me.
I give up. I'll just have to stick with stock ROM. No custom ROMs will work for me no matter which one I use or which version of TWRP I use. I already wasted too much of my life with this garbage phone.
Click to expand...
Click to collapse
Copy the files to your external SD card not internal storage. But if you don't have an ext SD card, don't wipe internal storage.
Also try to check if system is properly mounted when installing gapps.
May I ask what custom rom you are trying to install?
I suggest you try Pixel Experience as it already has a builtin Gapps so you dont have to flash opengapps.
I'm no stranger to rooting and ROM'ing I've been doing it for years now. However I've never had an a/b device and it's confusing me I have a T-Mobile variant switched to international the bootloader is unlocked I'm rooted with magisk 18.1, and TWRP 3.3.0-2 and I have OOS 9.0.12 installed. I don't understand having OOS as a base ROM for other custom ROMs, some people say to flash OOS twice because apparently it goes into both slot a and b but then twrp encrypts data forcing you to msmtool. I know to take any password and finger print off the phone before switching ROMs and to change the lock screen to none.
My understanding of the steps to follow are
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good
If that's correct please let me know and I appreciate the help
Joe199799 said:
I'm no stranger to rooting and ROM'ing I've been doing it for years now. However I've never had an a/b device and it's confusing me I have a T-Mobile variant switched to international the bootloader is unlocked I'm rooted with magisk 18.1, and TWRP 3.3.0-2 and I have OOS 9.0.12 installed. I don't understand having OOS as a base ROM for other custom ROMs, some people say to flash OOS twice because apparently it goes into both slot a and b but then twrp encrypts data forcing you to msmtool. I know to take any password and finger print off the phone before switching ROMs and to change the lock screen to none.
My understanding of the steps to follow are
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good
If that's correct please let me know and I appreciate the help
Click to expand...
Click to collapse
First you need to flash OOS stable because of vendor and second to avoid the bugs. If you flash open beta u will face alot of face issues that why stable is always recommend to flash before flashing ROM and it's also must to flash before flashing ROM again same thing to avoid bugs but it's personal choice if u flash Rom and face any Issue flash OOS stable and then flash Rom. If u don't flash OOS and u didn't face any Issue you are fine that's my experience so far if I flash issue I repeat but stable first then custom and 99% bugs fixed that I "Only" face ..
And method yes that is correct for flashing ROM at least for me I followed always and nothing happens!
farhan20 said:
First you need to flash OOS stable because of vendor and second to avoid the bugs. If you flash open beta u will face alot of face issues that why stable is always recommend to flash before flashing ROM and it's also must to flash before flashing ROM again same thing to avoid bugs but it's personal choice if u flash Rom and face any Issue flash OOS stable and then flash Rom. If u don't flash OOS and u didn't face any Issue you are fine that's my experience so far if I flash issue I repeat but stable first then custom and 99% bugs fixed that I "Only" face ..
And method yes that is correct for flashing ROM at least for me I followed always and nothing happens!
Click to expand...
Click to collapse
I flashed OOS 9.0.12 yesterday because I switched ROMS with 9.0.11 and it resulted in a msm flash, turns out switching roms from 9.0.11 is a bad idea. But after updating I flashed havoc OS and everything is all good. We appreciate the answer I understand it a little better now
A/B slotting implies having a pair of partitions for most partition types (eg., Boot, System, etc...). This does not include the Data partition, however. The purpose was never to allow the coexistence of multiple ROMs but to install an OTA stock update into the unused slot while you're already using the ROM. That way if there's an error during the update process, the OS can choose not to switch over to the updated partition on reboot and continue using the current one. This redundancy is why they were able and willing to scrap the Recovery partition, too.
When flashing a ROM for an A/B device, it actually flashes to the slot you are currently not using. Then upon reboot, it switches to that slot. This is why to maintain TWRP, you need to run TWRP installer after flashing the ROM but before the reboot. Otherwise, restarting into recovery would restart into the ROMs recovery or stock recovery. The TWRP installer unconditionally patches tho Boot partition of both slots. Note that other installers like Magisk and GApps do not. If you were to install Magisk before rebooting, it would install to the currently active slot, not the one the ROM was installed to.
After flashing the ROM and TWRP and rebooting into recovery, the slot would then be set to the newly installed ROM's slot and you can finish installing Magisk and/or GApps. You would wipe data unless you're dirty flashing an updated ROM. If you've removed security password/pin/pattern before flashing it's safe to flash before rebooting in recovery. In situations where I still had such security on, I had to wipe data after rebooting into recovery to maintain working decryption. Taking off the password/pin/pattern before flashing effectively disables the encryption of files on the data partition making it easier to transition to another ROM without any decryption problems.
Whether you need to flash OOS before flashing a ROM, I presume, would depend on whether the ROM, itself, is OOS based. It's not necessary for a non-OOS ROMs. There is a nasty problem that creeps up with OOS based ROMs in which it might boot-loop into recovery. I assume the double flashing might prevent that, though my experience with that problem is after a TWRP restore of OOS stock. You could use msmtool in such a situation as stated, but I always get rid of it by flashing stock Boot partition in fastboot, booting into stock recovery, and factory reset + erase sdcard.
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good.
Click to expand...
Click to collapse
Don't reboot into ROM before reboot into recovery and make sure to take off Pin/Password/Pattern/Fingerprints before booting into TWRP. Otherwise, this should be fine. For the wipe stage, you don't even need to wipe System or Boot (never Boot), in my experience. Just Data and Dalvik, if not dirty flashing the same ROM type.
Nsane457 said:
A/B slotting implies having a pair of partitions for most partition types (eg., Boot, System, etc...). This does not include the Data partition, however. The purpose was never to allow the coexistence of multiple ROMs but to install an OTA stock update into the unused slot while you're already using the ROM. That way if there's an error during the update process, the OS can choose not to switch over to the updated partition on reboot and continue using the current one. This redundancy is why they were able and willing to scrap the Recovery partition, too.
When flashing a ROM for an A/B device, it actually flashes to the slot you are currently not using. Then upon reboot, it switches to that slot. This is why to maintain TWRP, you need to run TWRP installer after flashing the ROM but before the reboot. Otherwise, restarting into recovery would restart into the ROMs recovery or stock recovery. The TWRP installer unconditionally patches tho Boot partition of both slots. Note that other installers like Magisk and GApps do not. If you were to install Magisk before rebooting, it would install to the currently active slot, not the one the ROM was installed to.
After flashing the ROM and TWRP and rebooting into recovery, the slot would then be set to the newly installed ROM's slot and you can finish installing Magisk and/or GApps. You would wipe data unless you're dirty flashing an updated ROM. If you've removed security password/pin/pattern before flashing it's safe to flash before rebooting in recovery. In situations where I still had such security on, I had to wipe data after rebooting into recovery to maintain working decryption. Taking off the password/pin/pattern before flashing effectively disables the encryption of files on the data partition making it easier to transition to another ROM without any decryption problems.
Whether you need to flash OOS before flashing a ROM, I presume, would depend on whether the ROM, itself, is OOS based. It's not necessary for a non-OOS ROMs. There is a nasty problem that creeps up with OOS based ROMs in which it might boot-loop into recovery. I assume the double flashing might prevent that, though my experience with that problem is after a TWRP restore of OOS stock. You could use msmtool in such a situation as stated, but I always get rid of it by flashing stock Boot partition in fastboot, booting into stock recovery, and factory reset + erase sdcard.
Don't reboot into ROM before reboot into recovery and make sure to take off Pin/Password/Pattern/Fingerprints before booting into TWRP. Otherwise, this should be fine. For the wipe stage, you don't even need to wipe System or Boot (never Boot), in my experience. Just Data and Dalvik, if not dirty flashing the same ROM type.
Click to expand...
Click to collapse
That was a very well written and insightful answer thank you. The way you wrote makes everything much easier to understand
I think with the new TWRP recovery flashing is about to be less of a d**k. TWRP 3.3.0-0
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
CptUnicorns said:
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
Click to expand...
Click to collapse
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Striatum_bdr said:
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Click to expand...
Click to collapse
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
CptUnicorns said:
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
Click to expand...
Click to collapse
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Striatum_bdr said:
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Click to expand...
Click to collapse
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
CptUnicorns said:
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
Click to expand...
Click to collapse
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
OhioYJ said:
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
Click to expand...
Click to collapse
That does clear up things for me, I've either mis-read or not read that when on slot A you are actually flashing slot B and Visa versa.
I'll be flashing both my slots to 10.3.1 just so they're fully updated. ( A is my main)
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
CptUnicorns said:
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
Click to expand...
Click to collapse
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Great stuff. Thought I understood from how you explained it. I'll check that guide as well and have it to hand just incase.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Something didnt want to play when I was flashing... Got to flashing gapps and magisk, gapps flash gave me a error 64 and i got magisk installed, booted, now I've got no twrp and when I use fastboot it just softbricks then restarts after about 5 minutes, I'm gonna try booting from 3.2.3-2 as that was fine and hope I can boot into recovery and just go lineage I think for something new
EDIT
So I used fastboot --set-active=a, managed to get back to twrp so now its flashed on both again. In the process of flashing lineage now, hopefully this wont chuck another error at me for gapps