is it possible to triple boot/duel boot - Galaxy S III Q&A, Help & Troubleshooting

is it possible to triple boot/duel boot - Galaxy S III Q&A, Help & Troubleshooting

hi i was wondering if i can triple boot my s3 with CM13 Nightly, AMCHA ROM, and 4.3 Stock Jellybean or 4.4 Kitkat (Back_to_n00t)
or duel booting CM13 and Amcha Rom
P.S i know it kinda sounds weird

I'm currently running a dual boot method. Kk 4.4.4 back to noot ROM and temesak cm12.1 lollipop 5.1.1. Using the arter97 kernel. I also wanted to run a cm13 based ROM but this kernel stops support at lollipop 5.1. But I'm really pleased with this set up. If you need help let me no.
---------- Post added at 02:18 PM ---------- Previous post was at 02:04 PM ----------
spyroz540 said:
hi i was wondering if i can triple boot my s3 with CM13 Nightly, AMCHA ROM, and 4.3 Stock Jellybean or 4.4 Kitkat (Back_to_n00t)
or duel booting CM13 and Amcha Rom
P.S i know it kinda sounds weird
Click to expand...
Click to collapse
I did this so i could still use the mhl support on touchwz and use a custom lollipop daily driver. Good setup with good kernel tweaks
kush2.0 said:
I'm currently running a dual boot method. Kk 4.4.4 back to noot ROM and temesak cm12.1 lollipop 5.1.1. Using the arter97 kernel. I also wanted to run a cm13 based ROM but this kernel stops support at lollipop 5.1. But I'm really pleased with this set up. If you need help let me no.
Click to expand...
Click to collapse

kush2.0 said:
I'm currently running a dual boot method. Kk 4.4.4 back to noot ROM and temesak cm12.1 lollipop 5.1.1. Using the arter97 kernel. I also wanted to run a cm13 based ROM but this kernel stops support at lollipop 5.1. But I'm really pleased with this set up. If you need help let me no.
Click to expand...
Click to collapse
ok thanks how can i do this? can i use boeffla kernal?

spyroz540 said:
ok thanks how can i do this? can i use boeffla kernal?
Click to expand...
Click to collapse
Boeffla does not support duel boot and never will. The Arter97 kernel you need is this http://www.arter97.com/s3_kernel.htm v4.1 and final v5 both support cm12.1 lollipop 5.1.1 I used the v4.1 because there is loads more customizations compared to v5. I think arter97 just removed the most liable instabilities so he could move on to newer devices hence why it ends with lollipop 5.1.1 support. Anyway not a big step to marshmallow anyways. Read threw the change log and overview etc.
Right first thing I did was all downloads to ext SD card inc.
1. KK 4.4.4 back to noot ROM,
2. Arter97 v4.1 kernel,
3. Dual boot 2.2.zip
4. SuperSU 2.4.6.zip (very important)
5. 5.1.1 Gapps.zip
And 6. Your 5.1.1 lollipop ROM.
Note that first time I did this setup I used Ressurection remix v5.5.9 lollipop 5.1.1 cm12.1 ROM as my 1st ROM and KK 4.4.4 back to noot ROM as the 2nd ROM but unless I crancked my CPU up to 1800mhz on a performance governor my sgs3 would crash and reboot when I inserted the mhl-hdmi lead so I swapped the ROMs around and found that the 2nd ROM (lollipop) wouldn't install. Not sure why!!
That is the reason I flashed temesak cm12.1 v18.0 5.1.1 lollipop (by arter97) as the 2nd ROM and this was successful and in truth I'm happier with this setup. And now I don't have the mhl issue of crashing even when my CPU is settled at just 200mhz!!!
I use twrp 2.8.7.0 for this process.
Assuming you have backed up everything boot into twrp 2.8.7.X and go to wipe - format SD card. This will warn you it will wipe all data/media from partition type "yes" hit "go". Now for good measure hit home then wipe again - advanced wipe and check first 3 boxes data/factory reset, cache and dalvic cache. Now install / flash 4.4.4 back to noot ROM wipe cache/dalvic and reboot recovery. Next install / flash arter97 v4.1 or v5 kernel and finally flash superSU 2.4.6.zip and then advanced wipe and just wipe the dalvic cache only (1st check box). Reboot system and setup your first 4.4.4 KK back to noot ROM and make sure its stable and running fine.
Now reboot into recovery and go to install and flash arter97 dual boot 2.2.zip ( now anything flashed as during this visit to recovery will flash onto you 2nd ROM partition until you leave recovery. So every new visit to recovery will require you to flash dual boot 2.2.zip to install anything onto 2nd ROM ) it will say this in twrp install script. Next flash cm12.1 temesak 5.1.1 lollipop v18.0 ROM. Don't wipe anything now as it will probable wipe the 1st ROM. Next flash Gapps and finally flash superSU 2.4.6.zip ignoring all warnings that " unable to mount pre-load " as this ROM is not using pre-load. You do not need to flash arter97 kernel. Next reboot recovery. And advanced wipe dalvic cache only (1st ROM) next reboot system.
You will now boot into 1st ROM ( back to noot 4.4.4 ) so use newly installed aswitch app to boot into 2nd ROM and visa versa. If you chose the temesak v18.0 lollipop 5.1.1 ROM be patient on first boot as it really does take some time to first boot.
Also if you find that aswitch and atweaks apps are not installed in 2nd ROM check kernel version. If its not arter97 v4.1 or v5 kernel then reboot recovery and flash the kernel also (flashing dual boot 2.2.zip first) but I didn't need to.
Also if twrp at any time offers to root device then don't use that method. The superSU 2.4.6.zip is the best way to obtain root access which you must have to be able to use the aswitch and atweaks.
Hope this is helpfull

kush2.0 said:
Boeffla does not support duel boot and never will. The Arter97 kernel you need is this http://www.arter97.com/s3_kernel.htm v4.1 and final v5 both support cm12.1 lollipop 5.1.1 I used the v4.1 because there is loads more customizations compared to v5. I think arter97 just removed the most liable instabilities so he could move on to newer devices hence why it ends with lollipop 5.1.1 support. Anyway not a big step to marshmallow anyways. Read threw the change log and overview etc.
Right first thing I did was all downloads to ext SD card inc.
1. KK 4.4.4 back to noot ROM,
2. Arter97 v4.1 kernel,
3. Dual boot 2.2.zip
4. SuperSU 2.4.6.zip (very important)
5. 5.1.1 Gapps.zip
And 6. Your 5.1.1 lollipop ROM.
Note that first time I did this setup I used Ressurection remix v5.5.9 lollipop 5.1.1 cm12.1 ROM as my 1st ROM and KK 4.4.4 back to noot ROM as the 2nd ROM but unless I crancked my CPU up to 1800mhz on a performance governor my sgs3 would crash and reboot when I inserted the mhl-hdmi lead so I swapped the ROMs around and found that the 2nd ROM (lollipop) wouldn't install. Not sure why!!
That is the reason I flashed temesak cm12.1 v18.0 5.1.1 lollipop (by arter97) as the 2nd ROM and this was successful and in truth I'm happier with this setup. And now I don't have the mhl issue of crashing even when my CPU is settled at just 200mhz!!!
I use twrp 2.8.7.0 for this process.
Assuming you have backed up everything boot into twrp 2.8.7.X and go to wipe - format SD card. This will warn you it will wipe all data/media from partition type "yes" hit "go". Now for good measure hit home then wipe again - advanced wipe and check first 3 boxes data/factory reset, cache and dalvic cache. Now install / flash 4.4.4 back to noot ROM wipe cache/dalvic and reboot recovery. Next install / flash arter97 v4.1 or v5 kernel and finally flash superSU 2.4.6.zip and then advanced wipe and just wipe the dalvic cache only (1st check box). Reboot system and setup your first 4.4.4 KK back to noot ROM and make sure its stable and running fine.
Now reboot into recovery and go to install and flash arter97 dual boot 2.2.zip ( now anything flashed as during this visit to recovery will flash onto you 2nd ROM partition until you leave recovery. So every new visit to recovery will require you to flash dual boot 2.2.zip to install anything onto 2nd ROM ) it will say this in twrp install script. Next flash cm12.1 temesak 5.1.1 lollipop v18.0 ROM. Don't wipe anything now as it will probable wipe the 1st ROM. Next flash Gapps and finally flash superSU 2.4.6.zip ignoring all warnings that " unable to mount pre-load " as this ROM is not using pre-load. You do not need to flash arter97 kernel. Next reboot recovery. And advanced wipe dalvic cache only (1st ROM) next reboot system.
You will now boot into 1st ROM ( back to noot 4.4.4 ) so use newly installed aswitch app to boot into 2nd ROM and visa versa. If you chose the temesak v18.0 lollipop 5.1.1 ROM be patient on first boot as it really does take some time to first boot.
Also if you find that aswitch and atweaks apps are not installed in 2nd ROM check kernel version. If its not arter97 v4.1 or v5 kernel then reboot recovery and flash the kernel also (flashing dual boot 2.2.zip first) but I didn't need to.
Also if twrp at any time offers to root device then don't use that method. The superSU 2.4.6.zip is the best way to obtain root access which you must have to be able to use the aswitch and atweaks.
Hope this is helpfull
Click to expand...
Click to collapse
spyroz540 said:
Thank you so much! here are my questions
can i change the first rom (back to n00t)?
if you tried AMCHA ROM can i have your opinion whats better back to n00t or AMCHA ROM? (if you havent tried it then you can skip this question)
does Offline Charging work?
Click to expand...
Click to collapse
I tried it with Mr modys M.D.4 galaxy S6 port v1.0 which is a 4.4.4 kitkat ROM first but it didn't support the arter97 kernel.
Not tried amcha ROM. No!!
Offline charging works fine on both ROMs at my current setup however when I had the resurrection remix ROM (1st) and back to noot ROM (2nd) setup offline charging would only work if I powered off from resurrection remix ROM an not the back to noot (2nd) which became a problem as if for example my battery died whilst hml mirroring a movie or something I was unable to get power into my battery completely because of this bug.
But as it stands right now its all good.

Related

S4 Dev Edition issues

Does anyone else with a Verizon S4 Dev Edition have problem with no audio when installing AOSP based ROMs?
TW based ROMs seems to work fine but when I install *any* AOSP based roms it there is no sound from first boot.
Every Install follows the same procedure:
Clean to Install a New ROM
Wipe Dalvik
Install Zip (ROM)
Wipe Cache (if it says to in ROM Install Instructions)
Wipe Dalvik (if it says to in ROM Install Instructions)
Reboot For First Run (if it says to in ROM Install Instructions)
OR
Install GaApps (if needed)
Wipe Cache (if it says to in ROM Install Instructions)
Wipe Dalvik (if it says to in ROM Install Instructions)
Reboot For First Run (if it says to in ROM Install Instructions)
I'm not sure if I'm missing something. The Google Edition 4.4.4 works perfectly with no audio issues. On the other hand the fun stuff like:
SOKP
CarbonROM
Dirty Unicorns
Just has no audio from calls to Bluetooth Music.
Any Ideas?
Device:
Verizon S4 Developer Edition
Baseband: I545OYUEMJ7
Philz Touch Recovery 6.50.6

Just got a Developer Edition yesterday and have exactly this problem. Version here was I545OYUFNC5. Also using philz recovery, I was wondering if that might have something to do with it, though I was unable to get TWRP to open recovery once installed, so I'm not really sure where to go from here.

[Q] Sacs Rom 4.4 with beast kernel freezing after install

So I have been rooting and customizing phones for a while now, but this one has me totally stumped.
Running A Sprint Note 3, I used auto root to root the phone. Using CWM recovery and both install fine.
These are the steps I took:
wipe data/factory reset
wipe cache partition
wipe dalvik cache
format system
format data
format cache
reboot back into recovery and then install Sacs Rom from zip
It installs fine when it reboots it hangs on the Samsung splash screen
I have let it sit for hours and it does not move.
Any help and advice would be great.

First, we need to know which sacs rom 4.4 you are referring to there is more than one. Next we need to know what version of KitKat you are running. The first thing I would do is get fresh download of the sacs rom. To eliminate the possibility of a bad download the first time. Next pick another rom try and flash that one. Eliminate the possibility of a bad recovery install.
I run stock, rooted, KK 4.4.2 NC5 with Philz custom recovery, version 6.12.9
If you want a stock copy of NC5 here is the link http://forum.xda-developers.com/showthread.php?t=2712205 if you need a copy of the recovery here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltespr/ to root I used SuperSu v 2.02 is the latest version here is the link http://forum.xda-developers.com/showthread.php?t=1538053 and from your post you already have Odin but I use version 1.85 here is the link http://www.downloadodin.info/download-odin-1-85
Remember, once you are at KK 4.4.2 NC5 the custom rom that you are going to install has to have a kernel that is compatible with NC5 and it's bootloader.

[Q] Can't update current rom OR install new rom! help

hey guys
i was on Temasek CM11 v142 + PA pico-gapps-20140916a + Boeffla kernel omnirom NG beta6a
now i wanna update to latest build, i mean v151
but when i follow these steps [the method that i always use]:
- wipping cache and dalvic cach
- formatting /system /cache /preload
- installing rom + gapps + kernel
after reboot, it will stay on Samsung logo for a long time and then it will reboot to the recovery menu by itself
i tried full wipe, fresh install of the latest Temasek CM11 v151 + gapps + kernel , again, same problem
even i tried without gapps or kernel, only rom, and no success
i tried fresh install of the latest Slimrom 8.6.1 with latest Slim gapps, same problem also latest L-Droid 4.0.0, no success
tried latest Philz and TWRP recovery, same problem
extra info: but when i try installing Temasek CM11 v142 [for testing] there's no problem
i think it's about something new in new builds of the roms...
can anyone help plz?

SignalX said:
hey guys
i was on Temasek CM11 v142 + PA pico-gapps-20140916a + Boeffla kernel omnirom NG beta6a
now i wanna update to latest build, i mean v151
but when i follow these steps [the method that i always use]:
- wipping cache and dalvic cach
- formatting /system /cache /preload
- installing rom + gapps + kernel
after reboot, it will stay on Samsung logo for a long time and then it will reboot to the recovery menu by itself
i tried full wipe, fresh install of the latest Temasek CM11 v151 + gapps + kernel , again, same problem
even i tried without gapps or kernel, only rom, and no success
i tried fresh install of the latest Slimrom 8.6.1 with latest Slim gapps, same problem also latest L-Droid 4.0.0, no success
tried latest Philz and TWRP recovery, same problem
extra info: but when i try installing Temasek CM11 v142 [for testing] there's no problem
i think it's about something new in new builds of the roms...
can anyone help plz?
Click to expand...
Click to collapse
First of all,for Temasek you should use Cm kernel,not Omni kernel(Boeffla recommends). Second,if you use Philz let recovery do the wipe by choose instal new rom option afte you select factory reset option.
Flash rom then gapps then boot and after first boot ,change the kernel.
Sent from my GT-I9300 using XDA Free mobile app

andjeomilosrdja said:
First of all,for Temasek you should use Cm kernel,not Omni kernel(Boeffla recommends). Second,if you use Philz let recovery do the wipe by choose instal new rom option afte you select factory reset option.
Flash rom then gapps then boot and after first boot ,change the kernel.
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
thanks for answer
i tried all of these different methods, but same problem again
i tried:
-full wipe ( "Clean to install new rom" in recovery menu) and installing Rom + gapps + kernel doesn't works, still bootloop
also i tried:
-full wipe ( "Clean to install new rom" in recovery menu) and installing Rom (only rom, without gapps or kernel) and again bootloop
tried two above methods with these roms: latest Temasek CM11 rom - latest L-Droid v4.0.0 - latest Slimrom 8.6.1 with Philz recovery and TWRP recovery
extra info: this Bootloop that i said, i mean after installing rom and rebooting system from recovery, phone will stay in "Samsung" logo for about 10 seconds and it will reboot to recovery menu automatically
another suggestion plz...

SignalX said:
thanks for answer
i tried all of these different methods, but same problem again
i tried:
-full wipe ( "Clean to install new rom" in recovery menu) and installing Rom + gapps + kernel doesn't works, still bootloop
also i tried:
-full wipe ( "Clean to install new rom" in recovery menu) and installing Rom (only rom, without gapps or kernel) and again bootloop
tried two above methods with these roms: latest Temasek CM11 rom - latest L-Droid v4.0.0 - latest Slimrom 8.6.1 with Philz recovery and TWRP recovery
extra info: this Bootloop that i said, i mean after installing rom and rebooting system from recovery, phone will stay in "Samsung" logo for about 10 seconds and it will reboot to recovery menu automatically
another suggestion plz...
Click to expand...
Click to collapse
Try reflash Philz recovery ,something is wrong with recovery. Maybe it's outdated. Flash 6.48.4 is the latest one.
Sent from my GT-I9300 using XDA Free mobile app

andjeomilosrdja said:
Try reflash Philz recovery ,something is wrong with recovery. Maybe it's outdated. Flash 6.48.4 is the latest one.
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
i'm using latest version of Philz recovery, also tried latest TWRP recovery
reflashing recovery doesn't fix this problem
current rom that i'm using is Temasek CM11 v142, when i full wipe my phone and flash this 142 again, there's no problem and phone will boot

SignalX said:
i'm using latest version of Philz recovery, also tried latest TWRP recovery
reflashing recovery doesn't fix this problem
current rom that i'm using is Temasek CM11 v142, when i full wipe my phone and flash this 142 again, there's no problem and phone will boot
Click to expand...
Click to collapse
In that case it's something beyond my knowledge. I can only reccomend the hard way and that is flashing stock rom and then all over again,rooting ,flashing recovery etc. Wait,maybe someone can help you and save you the trouble or do it as i said if it's not to much hassle for you.
Sent from my GT-I9300 using XDA Free mobile app

[Complete Guide] Flash AOSP ROM over Stock/Cloudy ROM for LG G2 D802/D802T

Alright, plenty of you folks might already be enjoying Cloudy/Stock ROM but there are guys out there, like me, who would sacrifice a very few LG core apps for the outstanding AOSP ROM i.e Resurrection Remix.
So here in this guide I'll show you all the steps that i followed to Flash Resurrection Remix over CloudyG2 3.3 (Obviously this guide will work for Stock Rooted ROM too with TWRP ofcourse!)
Have a look at the Pros and Cons BEFORE proceeding with the procedure!
Pros:
1. It's AOSP ROM dude!
2.Excellent Battery timing.
3.Super Smooth with ZERO LAG!
4.You get continuous updates.
5.Tremendous customization's via RR Rom.
Cons:
1. Camera not as cool as Stock.
2. NO fully supported Quick-Remote
3. No Quick Note or any other Stock app you liked.
Should I proceed or Stick with Cloudy/Stock?
Well, to be honest, its worth the hassle. The only thing i really miss was the Stock G3 camera that came with CoudyG2 but i guess CameraNext ain't so bad too. Moreover u get a hell lot of improvements with UI and other AOSP gimmicks.
NOTE:
I TAKE NO CREDIT IN THE DEVELOPING OF ANY APP/ROM SHARED!
Please Follow each step carefully, I'm not responsible if you mess up your device, no one is forcing you to do so, proceed at your own risk[ Nah, don't worry, i tried all this personally and nothing went wrong. Just be careful though!]
*****************************************Instructions************************************************
I'm assuming you already have a Rooted device with Custom Recovery installed.
What you need! [Links at the END]
1. RR Roms
2. KK Baseband
2. Gapps Package (for 5.1)
3. LP Bootstack
4. Quick-Remote
5. Partition Back&Resore
6. Donation to all the Devs who made this possible [If you can afford one ]
BACKUP:
Its always good to create a Backup of a very few System partitions and if something goes wrong, you'll thank me later for this!
1.Install Partition Backup&Restore
2.Backup The following Partitions [Your own Bootstack].
aboot, boot, dbi, laf, rpm, tz, sbl1, persist
3.Backup Modem.
Modem, Modemst1, Modemst2.
4.You can backup your apps too via Titanium Backup.
5.Copy All your Saved Partitions to your PC.
Getting Ready:
1.Copy ROM, KK baseband, LP Bootstack, Quickremote and Gapps Package to your phone.
2.Boot into Recovery.
3.Backup System, EFS and boot.
4.Wipe cache, dalvik cache, data and System.
Now, follow these steps in the following order.
1.Flash LP Bootstack.
2.Flash KK Baseband.
3.Flash ROM.
4.Flash Gapps.
Now, clear dalvik cache and cache .
Reboot your device.
Finally, if all went fine you'll be seeing RR booting.
Setting up Quick-Remote:
1. Goto Setting -> Configurations -> Miscellaneous -> Set SeLinux to Permissive (Make sure you give root permission to Setting via SuperSU).
2. Download Int.D Enabler via Playstore and Enable Int.D via this app.
3. Download BusyBox and install it. (Do not forget to install Busybox files within the app).
4. Reboot to Recovery and Flash Quickremote.zip.
5. Clear Cache and dalvik cache.
6. Reboot
Other [Must] addons:
Beside the awesomeness already provided by RR, let's crank it up a little bit
Boost Sound(Yup, you gotta do it!):
1. Download mixerpath.zip and extract it.
2. Goto System -> etc -> rename mixerpath.xml to mixerpath.bak (creating a backup just in case).
3. Now copy the extracted mixerpath.xml to System -> etc.
4. Download Viper4Android.
5. Install apk and run it (choose the "ViPER4Android_FX_A4.x.apk" file).
6. It'll ask for which driver to install, Choose High Quality.
7. Reboot.
Improve Camera:
1. Download CameraNext.
2. Reboot to recovery and flash it.
3. Wipe cache and dalvik cache.
Other thoughts:
LTE should be working as it's available in the Setting.
Goto Setting and apply the PitchBlack theme (if you like).
There you go, now i guess you won't regret your decision of choosing AOSP ROM for your G2.
Hit Thanks as i won't ask you for a drink or hoe
LINKS:
ROM+Gapps
KK Baseband
LP BootStack (Click on 'View Full file' to Download)
Viper4Android

awesome guides, works great.

I really want to update to update to marshmallow but have no idea which bootstack to use. I've never needed to change bootstack when updating other phones.

Update TWRP before installing ROM
Thanks for the guide. I had an issue after installing this ROM on D802T, whereby I could not longer boot into TWRP recovery and received a "secure boot error" followed by a blank screen. Before installing RR, I had to update TWRP to blastagator's TWRP w/ Thermal Control & F2FS (twrp-3.0.2-1-d802-bump-blastagator-signed.zip).

MonsieurLorax said:
Thanks for the guide. I had an issue after installing this ROM on D802T, whereby I could not longer boot into TWRP recovery and received a "secure boot error" followed by a blank screen. Before installing RR, I had to update TWRP to blastagator's TWRP w/ Thermal Control & F2FS (twrp-3.0.2-1-d802-bump-blastagator-signed.zip).
Click to expand...
Click to collapse
You actually messed up the recovery partition. You had to flash the D802T recovery NOT D802. If your phone is booting then do so else restore to Stock and reproduce the steps. Good luck!
Sent from my LG-D855 using XDA-Developers mobile app

Kind attention!!
Currently I am on cloudy g2 3.3 and i have a full backup of cm13 rom,which I was using earlier.My question is, can i simly restore that backup through twrp or not?

akki809 said:
Kind attention!!
Currently I am on cloudy g2 3.3 and i have a full backup of cm13 rom,which I was using earlier.My question is, can i simly restore that backup through twrp or not?
Click to expand...
Click to collapse
Cm13 uses LP bootstack so i think there won't be any issue but I'm not sure about the modem though, do backup everything before you proceed.
Sent from my LG-D855 using XDA-Developers mobile app

stock 4.1.2 to CM13 way

Hi all!
I'm a new user of i9100
I already rooted my phone and got cwm 3.75 (with touch)
now I want to install CM13
I ready losts of post about upgrade and I generate few steps for this
1. backup
2. install recovery for kk
3. install kernel for kk
4. re-partition
5. flash CM13
6. flash gapps v.6
7. flash TWRP for CM13
is this way correct?
ps. my english isn't good, sorry

Hi
Best way is to stick to the thread by @gsstudios : " (Guide) ( Noobfriendly) Want to update to Cm 13? Read this first!
Many new users made 2 mistakes you should avoid:
1) they did not increase the System space to at least 1GB System and 4 GB Date - so they could not install any Gapps
2) they did not install the isorec-Revovery TWRP by @arnab - so they had no useful Revovery (but only the useless CM - recovery)
Which worked for me on 3 Devices:
1) Backup
2) flash pitfile 1GB System 4 GB data and the gustavo kernel (which includes CWM Recovery)
3) Do not forget to format in CWM recovery
4) Then make a clean flash and install CM 13 and the Gapps (open gapps pico) AND the isorec-recovery TWRP [email protected] ALL IN ONE GO - TO NOT REBOOT IN BETWEEN-
5) Reboot system and enjoy

Better Mobile App

welcome