Database Info

absurdly stupid move by me.3113wTWRPv2.6.3.0 only left

I was doing fine with my PAC-4.3.1. I backed everything up. Then I erased all ... yep... no OS. And trying to install something like the MicroDelta-P3110-4.2.2xxx... says its unable to open the zip file. So I probably messed up my root also.
I have very limited access to XP. I run Linux. Ubuntu, Debian ... but I can not find a working way to salvage my tab2.7 this way. odin for XP was how I got to 4.1.2.
I believe I need help in knowing what is the actual correct next step. I read the forum and have failed so far. So would someone be able to point me to the correct link knowing my situation?
I think I was on 4.2.2. Then PAC 4.3.1
I used to have Philz installed. Recently went to TWRP because I was getting very unreliable bootloops and switching helped in the short term...

try flashing PhilZ Touch using adb sideload, reboot into philz touch and try the rom again.... maybe flash the rom using sideload
---------- Post added at 11:27 PM ---------- Previous post was at 11:26 PM ----------
Read this: http://teamw.in/ADBSideload
---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------
You can also try flashing any other Rom using adb sideload

canezila said:
I was doing fine with my PAC-4.3.1. I backed everything up. Then I erased all ... yep... no OS. And trying to install something like the MicroDelta-P3110-4.2.2xxx... says its unable to open the zip file. So I probably messed up my root also.
I have very limited access to XP. I run Linux. Ubuntu, Debian ... but I can not find a working way to salvage my tab2.7 this way. odin for XP was how I got to 4.1.2.
I believe I need help in knowing what is the actual correct next step. I read the forum and have failed so far. So would someone be able to point me to the correct link knowing my situation?
I think I was on 4.2.2. Then PAC 4.3.1
I used to have Philz installed. Recently went to TWRP because I was getting very unreliable bootloops and switching helped in the short term...
Click to expand...
Click to collapse
Now what do you mean by you erased everything? Even wiping system, user data and both caches won't break root. Was there something else you wiped that you probably shouldn't have? What you could do is set up a virtual machine for XP, or even dual boot. It's a little time consuming, but in the end I do believe it would be worth it If you can't even flash a zip I don't really know what else you could do. Hopefully someone else will chime in with a less exhausting solution. But dual booting or using a virtual machine is certainly option. That way you can easily odin back to stock.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
Android-Andi said:
try flashing PhilZ Touch using adb sideload, reboot into philz touch and try the rom again.... maybe flash the rom using sideload
---------- Post added at 11:27 PM ---------- Previous post was at 11:26 PM ----------
Read this: http://teamw.in/ADBSideload
---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------
You can also try flashing any other Rom using adb sideload
Click to expand...
Click to collapse
I thought about that, but he said he broke root and can't flash a zip? Would sideloading work around that?

Sure Sideload should work, i think root is not broken (can access to storage be broken in recovery? i don´t think so ) - maybe bad download of the rom or he can only flash signed zip´s ? maybe he can try disable zip-verification (?)

Android-Andi said:
Sure Sideload should work, i think root is not broken (can access to storage be broken in recovery? i don´t think so ) - maybe bad download of the rom or he can only flash signed zip´s ? maybe he can try disable zip-verification (?)
Click to expand...
Click to collapse
I've never had to use side load lol... You know more than I on the issue

How to setup ADB on Ubuntu? ---> http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
or http://askubuntu.com/questions/318246/complete-installation-guide-for-android-sdk-on-ubuntu
---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------
@canezila can you please check in TWRP -> Settings -> "Zip file signarure verification?" Checked or unchecked? If it´s checked: uncheck it!

Recovery couldn't open the zip. A failed signature verification would return a "signature verification failed" error, no?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

i don´t know what he did (i don´t think he knows it too ) let´s wait for his feedback...
trying to flash a recovery or another rom using sideload might work...
or he can try another file (only flashing a recovery.zip) flashing from a microSD card?
could be a bad download of the file too...
i´m going to sleep now hope my tipps work for him - i am sure he´ll give any feedback
---------- Post added at 12:14 AM ---------- Previous post was at 12:08 AM ----------
"(...)I used to have Philz installed. Recently went to TWRP because I was getting very unreliable bootloops and switching helped in the short term..(...)"
a recovery wouldn´t make a rom bootlooping i think he forgot to wipe something.
i never had a bootloop or other strange problems on a working rom! NEVER!
What i am doing:
wipe cache partition
wipe dalvic cache
format /system
wipe data factory reset (on PhilZ Touch "Clean to install a new Rom")
flash rom
reboot
if it´s working i reboot into recovery again
flash gapps
flash NEXT Kernel
flash Proprietary files for NEXT Kernel
reboot again
(sometimes flashing NEXT Kernel + Proprietary files directly after the rom before 1st boot - only if i am on Dual-Boot)
---------- Post added at 12:18 AM ---------- Previous post was at 12:14 AM ----------
If you like MicroDelta 4.1.2
Download
MicroDelta-P3110-JB-4.1.2-P3110XXDME3-signed.zip and MicroDelta-P3113-JB-4.1.2-P3113XXDME3-signed.zip
Try this (yes do it again):
wipe cache partition
wipe dalvic cache
format /system
wipe data factory reset
First flash MicroDelta-P3110-JB-4.1.2-P3110XXDME3-signed.zip
directly after that flash MicroDelta-P3113-JB-4.1.2-P3113XXDME3-signed.zip

$ sudo apt-get install android-tools-adb
$ adb version
Android Debug Bridge version 1.0.31
$ adb sideload philz_touch_5.15.0-p3110-blackhawk.zip
$ adb sideload blackhawk-next-kernel-2.1.5-p31xx-miui.zip
**probably usless step but I wanted to see if it worked and it installed wo errors***
$ adb sideload miui_3.10.25_p3110_beta2.zip
$ adb sideload proprietary-vendor-samsung.zip
** yes, I have no idea what I am doing because this probably is part of another thread.... but it is ok**
But now that I can easily push ROMs over... I am going to go crazy installing a bunch of similar 4.3.1 roms.
THANKS FOR THE HELP!

I ended up on PAC MAN 4.3.1. at least for now

Droid MAXX unlocked BL Custom Recovery?

I am sure that people have ran into this question with the Chinese Man coming back and the consumer editions becoming unlocked (if you are lucky enough to be a 2014 model) My question is, i currently have an unlocked bootloader Consumer Edition Droid MAXX running 4.4 from verizon. i am looking for the correct version of TWRP or another custom recovery (not safestrap) for this phone. i apologize if somebody else has posted a thread about this, but from my quick skimming of thread titles this does not seem to be clearly addressed. Also any insight on ROMs, etc would be appreciated after the custom recovery question is addressed. Thanks guys.

C4Charizard said:
I am sure that people have ran into this question with the Chinese Man coming back and the consumer editions becoming unlocked (if you are lucky enough to be a 2014 model) My question is, i currently have an unlocked bootloader Consumer Edition Droid MAXX running 4.4 from verizon. i am looking for the correct version of TWRP or another custom recovery (not safestrap) for this phone. i apologize if somebody else has posted a thread about this, but from my quick skimming of thread titles this does not seem to be clearly addressed. Also any insight on ROMs, etc would be appreciated after the custom recovery question is addressed. Thanks guys.
Click to expand...
Click to collapse
Here is a better way to make a nandroid backup along with twrp links.
http://forum.xda-developers.com/moto-x/general/fyi-online-nandroid-backup-ready-t2762382
---------- Post added at 12:07 PM ---------- Previous post was at 11:55 AM ----------
Here is latest
http://forum.xda-developers.com/showpost.php?p=54953458&postcount=120

aviwdoowks said:
Here is a better way to make a nandroid backup along with twrp links.
http://forum.xda-developers.com/moto-x/general/fyi-online-nandroid-backup-ready-t2762382
---------- Post added at 12:07 PM ---------- Previous post was at 11:55 AM ----------
Here is latest
http://forum.xda-developers.com/showpost.php?p=54953458&postcount=120
Click to expand...
Click to collapse
None of these worked. i effectively have no recovery currently. it says invalid size or something and boots directly to bootlloader

C4Charizard said:
None of these worked. i effectively have no recovery currently. it says invalid size or something and boots directly to bootlloader
Click to expand...
Click to collapse
Tell us exactly what you did, please?

aviwdoowks said:
Tell us exactly what you did, please?
Click to expand...
Click to collapse
I specifically attempted TWRP and used flashify to flash recovery image for 2.7.whatever . is it relevant I am running KK 4.4? I then attempted philz and it worked. But I feel more comfortable with twrp as its all I have ever used.

Are you rooted? How so if you have no recovery?
If rooted you must flash the .img with Rashr recovery tools.
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
If Philz worked then redownload twrp.
Philz is great use my INI file to get started.

aviwdoowks said:
Are you rooted? How so if you have no recovery?
If rooted you must flash the .img with Rashr recovery tools.
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
If Philz worked then redownload twrp.
Philz is great use my INI file to get started.
Click to expand...
Click to collapse
yes i am rooted untethered with write protection off. and if i can use philz to root then i will just stick with it. no need to fix what isnt broken

C4Charizard said:
yes i am rooted untethered with write protection off. and if i can use philz to root then i will just stick with it. no need to fix what isnt broken
Click to expand...
Click to collapse
Flash from recovery
http://download.chainfire.eu/supersu

aviwdoowks said:
Here is a better way to make a nandroid backup along with twrp links.
http://forum.xda-developers.com/moto-x/general/fyi-online-nandroid-backup-ready-t2762382
---------- Post added at 12:07 PM ---------- Previous post was at 11:55 AM ----------
Here is latest
http://forum.xda-developers.com/showpost.php?p=54953458&postcount=120
Click to expand...
Click to collapse
Read notes here as to a condition where twrp may not stick, or rather the phone acts as though it is not there & gives the Bootloader instead.
http://forum.xda-developers.com/showpost.php?p=54631556&postcount=1342

Got philz to work, all good! Thanks guys

I also have a consumer addition that's unlocked and couldn't get twrp 2.7 to load. Same error message too. I ended up going with twrp 2.6.31 - ghost-4.4 and it works fine.

[ROM] SU4TL-44 100% Stock

SU4TL-44 Stock Image for XT1254: https://mega.nz/#!v4QWiITb!_0jWWzE4KWCEgT__C36rYe0vaTzGKcEFsZm0vvBtLBg
Flash with TWRP.
This package will flash every image in the SU4TL-44 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, revert to stock by following section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Thanks to @firstEncounter for letting me incorporate his flashable zip into this package.

Will have to download this later. Looked to go back to stock and wait for mm to come out.
Sent from my XT1254 using Tapatalk

Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?

schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
No it won't relock boot loader just installed it you will not be rooted and twrp will ask you if you want to root before reboot if you click no and want to at a later point just go back into boot loader by doing vol down power combo from power off and select open boot loader and when you click to reboot it will ask you again if you want to root then you can just slide to install

schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
Correct

Can I install viper and su along with this?

MazinDLX said:
Can I install viper and su along with this?
Click to expand...
Click to collapse
Sure. Just flash the rom first and the mods second.

TheSt33v said:
Sure. Just flash the rom first and the mods second.
Click to expand...
Click to collapse
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol

MazinDLX said:
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
Click to expand...
Click to collapse
I've never tried to install an image via ADB before. Did you mount the image elsewhere and extract the system folder, and then ADB-pushed that? If not, your bootloop is probably because there's just a big, unextracted system.img on your system partition, and not the actual files within it. Why not just flash it with TWRP? When I tested it, I flashed it via TWRP and it worked.
If you really don't want to flash it via TWRP for some reason, you can extract the system.img from the zip and flash it using fastboot (fastboot flash system system.img).
EDIT: Oh wait, I think I understand now. You just used ADB to put the zip on your phone, and then you installed it with TWRP. Got it. Well my next question is why use ADB at all? Why not just plug in your phone while it's booted into TWRP and use the native MTP to transfer files?

Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.

The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.

MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
This package only flashes /system. CM flashes its own boot.img, which is why this isn't working for you. I'll try to find some time tonight to add in the other images in the stock firmware to this package. Sorry about that.

firstEncounter said:
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
Click to expand...
Click to collapse
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?

TheSt33v said:
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
Click to expand...
Click to collapse
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.

MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.

firstEncounter said:
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
Click to expand...
Click to collapse
I'm not entirely sure how to write a script to flash those in TWRP. For boot and system, it's easy because the devices that they are flashed to match the names used by fastboot. Bootloader and radio seem to be a little different though. When I list the contents of /dev/block/bootdevice/by-name, there is no "motoboot" or "radio," which is what fastboot uses when you flash these. I do see "aboot" and "modem," and I'm pretty sure those are the targets I'm looking for, but I don't want to go flashing things unless I'm 100% sure. Since there's not a huge demand for figuring that out, and boot + system is all people will need in 99% of cases, I'll leave them out. Thanks though!

Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?

MazinDLX said:
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
Click to expand...
Click to collapse
No, but I appreciate the thought. Donate to this guy instead. He does way more than me and also needs it way more than me: http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945

TheSt33v said:
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
Click to expand...
Click to collapse
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.

bigv5150 said:
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
Click to expand...
Click to collapse
Awesome! That's why we do this

How many of you have rooted & had issues?

Just interested to know many of you have rooted & had any issues. Twice I've been rooted myself & had to use msm recovery program to get me up & running again!
First time it worked well for a few weeks but then I had a charging issue that eventually got me stuck in fastboot. Second time the phone simply gave up after using titanium to remove bloatware
I love my OP7P but never had issues like this on any Samsung device. TWRP backups cause major issues as well!

Had no issues with Root like those. I'm not using TWRP.

No issues with my phone i'm rooted since 1st day and i use twrp

c3drik 67 said:
No issues with my phone i'm rooted since 1st day and i use twrp
Click to expand...
Click to collapse
Whatever you do don't attempt a recovery backup, it won't work

Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
mike710_0 said:
Whatever you do don't attempt a recovery backup, it won't work
Click to expand...
Click to collapse
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322

No issues, rooted, love it.

vtec303 said:
Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
No I haven't but I'll certain give it a try. Usually when I backup I select everything

Zero issues
Root w/ Magisk 19.3
TWRP unofficial installed
Handful of Magisk Mods
Renovate ROM
Kirisakura custom kernel

vtec303 said:
Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
Same. You hit the nail on the head.....backup and restores fine.... But you have to follow these rules....running twrp, magisk, bunch of modules..... everything is kosher

Make sure you're only using stable magisk
The others cause charge issues

vtec303 said:
Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
You sir are an absolute legend! Just done this & it worked great.
Thanks very much ??

mike710_0 said:
You sir are an absolute legend! Just done this & it worked great.
Thanks very much ?
Click to expand...
Click to collapse
No problem, you are welcome. Enjoy ?

Help Needed Please

Hi everyone, my dad has been using the oneplus one since it came out. he has been mentioning lately the phone is really slow, so i decided to try and root the phone and get a newer OS for him in hope it runs more smooth.
here where the trouble began, so i had to root the phone in order to get a new OS, so i got as far as installing supersu, which came up with a binary error so i went back out to TWRP and flashed a newer version, when i rebooted phone when in to a loop at the cyonegenmod, it just wont load. so i rebooted back in to TWRP and thats when i went stupid and deleted everything ( with out making a backup ).
So I am now stuck with no OS installed, with out an OS i have been able to adb push files to the internal storage for the roms i have down loaded, i try using sideload to install the roms i have downloaded, which has always failed, with the sideload error executing updater zip / xxxxx/ xxxx/ etc.
questions i have
-the error is due to the wrong ROM i have sideloaded? ( what is the stock version? some say 4.4.2 kitkat? some say cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot )
-if i am using adb sideload, which file should i be using? cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot or cm-13.1.2-ZNH2KAS3P0-bacon-signed ?
- to my understanding ( whihc isnt much ) i just need to find the right stock ROM zip file and sideload it in and it should run again right?
or am i totally wrong and the phone is pretty much dead?
any help would be great
Thanks in advance

I'm replying since no one is. I'm not sure about the error but did you factory reset prior to flashing?
You can restore stock rom using the method in this thread https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541.
Other than sideloading, you can use an OTG adapter + thumbdrive. Even in recovery, OTG storage is still detected.
Hopefully you are able to solve your issue.
---------- Post added 10-08-2020 at 12:07 AM ---------- Previous post was 09-08-2020 at 11:59 PM ----------
Also, supersu/superuser is outdated. Magisk is the current way to root now.

risay07 said:
I'm replying since no one is. I'm not sure about the error but did you factory reset prior to flashing?
You can restore stock rom using the method in this thread https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541.
Other than sideloading, you can use an OTG adapter + thumbdrive. Even in recovery, OTG storage is still detected.
Hopefully you are able to solve your issue.
---------- Post added 10-08-2020 at 12:07 AM ---------- Previous post was 09-08-2020 at 11:59 PM ----------
Also, supersu/superuser is outdated. Magisk is the current way to root now.
Click to expand...
Click to collapse
Thanks for your reply
yeah i did do a factory reset, i then wiped everything including the system
so i am now stuck with NO OS i believe, i did read that post you linked, but i cant access fastboot mode
all i can access is TWRP, so i can push files in the storage, but when ever i sideload or install the Stock roms and reboot the phone nothing is happening just stuck at the one plus logo
any suggestions from this point??
Thanks in advance

Did you try to boot to fastboot by plugging the usb cable while volume up button is pressed? What android version are you on before you wiped? And what is your current TWRP version.
---------- Post added at 03:16 AM ---------- Previous post was at 02:51 AM ----------
IMO, since fastboot and adb sideload not working for you, try going the thumbdrive+OTG cable method. Download any Pie or Q rom and open gapps pico and copy them to the thumbdrive. Connect the thumbdrive to your phone using the OTG cable and flashed it in TWRP.