Related
So I was rooted and had TWRP, I installed the OTA via the OnePlus Updater. Then I proceeded to flash TWRP in fastboot again, flashed twrp installer afterwards and finally flashed magisk 19.3. Then I rebooted into system, but whenever I 'm at the pin field the device shuts down and reboots to TWRP.
I uninstalled magisk via the zip file and succesfully rebooted into my system. Why is this happening and how can I get back Magisk?
Maybe you have some Magisk module causing this. There is an option to disable Magisk modules through command line.
memocatcher said:
So I was rooted and had TWRP, I installed the OTA via the OnePlus Updater. Then I proceeded to flash TWRP in fastboot again, flashed twrp installer afterwards and finally flashed magisk 19.3. Then I rebooted into system, but whenever I 'm at the pin field the device shuts down and reboots to TWRP.
I uninstalled magisk via the zip file and succesfully rebooted into my system. Why is this happening and how can I get back Magisk?
Click to expand...
Click to collapse
If you used magisk uninstaller and the reboots are gone then just flash magisk again. Also it's best to use 19.4 magisk
Like the title says, I can´t boot to recovery (Oneplus one). If I try to boot to recovery, I´m ending in the Qualcomm CrashDump Mode.
I have a Oneplus 7 Pro with Stable 10.0 BA FW.
Rooted with Magisk (Patched Boot.img) Is this causing the problem?
After pressing Vol+ and powerbutton, the devices boots normally.
Thanks in advance.
RealDanyo said:
Like the title says, I can´t boot to recovery (Oneplus one). If I try to boot to recovery, I´m ending in the Qualcomm CrashDump Mode.
I have a Oneplus 7 Pro with Stable 10.0 BA FW.
Rooted with Magisk (Patched Boot.img) Is this causing the problem?
After pressing Vol+ and powerbutton, the devices boot normally.
Thanks in advance.
Click to expand...
Click to collapse
I had the same issue this morning when trying to update to 10.0.1. Just boot to bootloader and boot twrp then install 10.
I think is the magisk update (magisk 20.0) that causes this, because it's happening to me in the beta 3 and before I updated magisk it was working fine with the beta 2
ItsTecnoDavid said:
I think is the magisk update (magisk 20.0) that causes this, because it's happening to me in the beta 3 and before I updated magisk it was working fine with the beta 2
Click to expand...
Click to collapse
I have no issues with magisk or twrp.
It might be the way you are installing ota or rom.
Might be model specific not sure as I don't know what model you are on. Mine is GM1915.
I'm talking about the official recovery
GM21AA, exactly the same situation (from 10 stable to 10.0.1 and magisk from 19.4 beta to 20) and the stock recovery bump into Qualcomm Crashdump problem here, system bootup normal as well as bootloader.
Troubleshooting:
1. Local update twice, install magisk at inactive slot OTA before reboot, for Android 10's A/B partitions machinasm , try let magisk patch both boot.img. Same...
2. Local update and reboot, lost root but stock recovery work, Fastboot boot twrp.img (latest, not flash, cause I don't need the permanent twrp)->twrp install magisk, reboot system, then, again, same problem.
Todo:
Magisk manager or twrp uninstall magisk, but if it's fail maybe ended up to bootloop, scary.
May try to install back old 19.4 magisk.zip via twrp, it's working in 10.0.0
Anyone with the same problem have any idea?
Thats the exact same error I ran into.
But as mentioned earlier, I never had TWRP on my OP7P. I flashed the patched boot.img via adb and I´m still on 10.0 BA Firmware.
I thought TWRP dosn´t work on Android Q (I´m coming from an Pixel3 and there it won´t work) So maybe I will give TWRP a try tomorrow. Are there different versions or is the official one the best?
RealDanyo said:
Thats the exact same error I ran into.
But as mentioned erlier, I never had TWRP on my OP7P. I flashed the patched boot.img via adb and I´m still on 10.0 BA Firmware.
I thought TWRP dosn´t work on Android Q (I´m coming from an Pixel3 and there it won´t work) So maybe I will give TWRP a try tomorrow. Are there different versions or is the official one the best?
Click to expand...
Click to collapse
The recovery here is the one to use.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Be sure to read through
So thanks erveryone who helped.
I now have TWRP running as recovery. So there is no need for official recovery. (and no Qualcomm CrashDump Mode)
Had this happen to me earlier this week. Just ended up using the MSM tool and restoring shipping firmware. You can look for the unbricking thread here for more info on that.
Yea, this just happened to me. Updated Magisk, Updated to 10.0.1 from 10.0. Booted fine.
Re-installed a few magisk modules (didn't just re check the modules, but reinstalled each)
Now OS won't boot, and recovery goes to Crash Dump. Would be ok if OS wouldn't bootloop and I could get to OS.
Oh, and my ADB now is an unauthorized device while its in bootloop mode
EDIT:
phew. Tried to hold volume up+dn rather than up or dn, got into bootloader. Able to fastboot boot TWRP and then delete problematic RIRU magisk modules. All is well in the world now...
I don't get it why it have to be so hard.
I'm constantly soft bricking/ bootlooping this phone when trying to do simple things such flashing magisk and twrp. I remember it being so much easier with my Poco F1, never got close to bricking it.
Now every little mistake ends with a bricked phone and 5 hours on the internet trying to understand why
WillyRy said:
Yea, this just happened to me. Updated Magisk, Updated to 10.0.1 from 10.0. Booted fine.
Re-installed a few magisk modules (didn't just re check the modules, but reinstalled each)
Now OS won't boot, and recovery goes to Crash Dump. Would be ok if OS wouldn't bootloop and I could get to OS.
Oh, and my ADB now is an unauthorized device while its in bootloop mode
EDIT:
phew. Tried to hold volume up+dn rather than up or dn, got into bootloader. Able to fastboot boot TWRP and then delete problematic RIRU magisk modules. All is well in the world now...
Click to expand...
Click to collapse
Same issue here and no TWRP installed.
I did ADB REBOOT FASTBOOT and was able to install the twrp image by FASTBOOT BOOT twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
Going to try and remove Magisk and see if I can salvage my data and then re-install Magisk afterwards.
Ok...got back into the system by flashing the Magisk Uninstaller in TWRP that is here: https://magiskroot.net/md/Magisk_Manager_for_Recovery_Mode_(mm)-2019.4.4.zip
Went to advanced in TWRP, then to terminal, then typed mm.
Typed in C for Core only to load into system without Magisk. Deleted my Magisk modules that may have interfered with it (I had an older version of No Limit that I should have updated prior. After removing and rebooting back into system, all is fine now.
JLine05 said:
Same issue here and no TWRP installed.
I did ADB REBOOT FASTBOOT and was able to install the twrp image by FASTBOOT BOOT twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
Going to try and remove Magisk and see if I can salvage my data and then re-install Magisk afterwards.
Ok...got back into the system by flashing the Magisk Uninstaller in TWRP that is here: https://magiskroot.net/md/Magisk_Manager_for_Recovery_Mode_(mm)-2019.4.4.zip
Went to advanced in TWRP, then to terminal, then typed mm.
Typed in C for Core only to load into system without Magisk. Deleted my Magisk modules that may have interfered with it (I had an older version of No Limit that I should have updated prior. After removing and rebooting back into system, all is fine now.
Click to expand...
Click to collapse
Yea man, things are hinkey this update.
My big problem was i had twrp but it got wiped i guess (could no longer access) and couldn't access adb nor fastboot. But finally got into bootloader (cmd fastboot) so was able to fix.
Easier solution than installing Magisk uninstaller (presuming one has twrp installed, which would be the case if able to flash Magisk uninstaller) is go to TWRP>advanced>file manager and navigate data/adb/modules and delete from there
DO you guys know if there is an updated magisk being developed or what is the way to fix it? Uninstall magisk via TWRP (since I can temporarily install and get into TWRP using the all in one tool by the TWRP developer). Then install TWRP and then Install Magisk ?
I have same problem
How to fix it and bring back stock recovery?
wawanRedblack said:
I have same problem
How to fix it and bring back stock recovery?
Click to expand...
Click to collapse
Can you boot OS?
Can you get to bootloader?
WillyRy said:
Can you boot OS?
Can you get to bootloader?
Click to expand...
Click to collapse
Yes i can boot os and bootloader is ok
Ive tried uninstalling magisk using the un-installer and no go. Ive tried booting into twrp then flashing the twrp zip then rebooting into recovery and it goes to the stock recovery. How do i get back TWRP?? Im on Pie and was using twrp .65
NVM: I had to re-flash 9.5.11 then twrp then reboot then magisk 19.4
I am in your same situation oneplus7.
Currently I was with twrp 3.3.1.1 but there is no way to catch any recovery. By flashing the image either version 1/65/70 (more current) by fastboot it enters correctly img you access twrp to later flash the zip But it never gets installed.
I tried to uninstall using img twrp Magisk zip uninstaller and install the 19.3 / 20v uninstall it completely and flash back to zip twrp but I am in a dead end.
Right now I am with Magisk v20 root edxposed and everything goes phenomenally as a result that I am going to "peel" without having twrp for my backups or anything.
Anyone have any idea how to install twrp again?
boot into twrp.img then flash the last rom you were using, then flash twrp.zip, reboot into recovery and install magisk 19.4. After reboot you will have to enable all your rooted apps again and install your magisk modules again.
Hello, So i tried to install GPS joystick privacy mode app as a system app first thru titanium backup then ..., i rebooted and now im on boot loop, what do i do?
Any help is appreciated, Thanks
{Mod edited}
Hold Power + vol up + vol down for several seconds should put you in bootloader. Or alteranately, Power+vol down for several seconds should send you to TWRP if you have it installed. From there, I'm thinking you may need to flash the stock ROM again, since you were messing with the system partition, and the phone is not booting now. Either flash stock ROM in TWRP, or use the fastboot stock ROM.
I didn't have twrp installed and i still dont, i patched the boot image with magisk and all i have is root cause i cant seem to keep TWRP installed after 9.5.3, im currently on 10.3.0
cmurder61 said:
I didn't have twrp installed and i still dont, i patched the boot image with magisk and all i have is root cause i cant seem to keep TWRP installed after 9.5.3, im currently on 10.3.0
Click to expand...
Click to collapse
You should be able to fastboot flash stock boot.img from the fastboot ROMs to get the phone running again: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
This will unroot the phone. But you should be able to easily root again by the method you did originally.
What is the problem you are having with installing TWRP? You haven't specifically described how you tried to install. I've had no issues using the TWRP installer zip, after multiple updates.
You need to re flash stock so, boot lastest twrp (fastboot boot twrp.img) and flash lastest stock rom.
And if you need an app as system use magisk module App Systemizer (you also need busybox module and Termux app from playstore) this is the only way (that I known) to convert user apps to system
Sent from my OnePlus7Pro using XDA Labs
redpoint73 said:
You should be able to fastboot flash stock boot.img from the fastboot ROMs to get the phone running again: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
This will unroot the phone. But you should be able to easily root again by the method you did originally.
What is the problem you are having with installing TWRP? You haven't specifically described how you tried to install. I've had no issues using the TWRP installer zip, after multiple updates.
Click to expand...
Click to collapse
Ive tried that it only boots to recivery, i restarted my phone completely with msm its wokring fine now but even after i root on 10.3.0 i still cant get twrp
when i try to install "fastboot flash twrp" it goes thru but it always boot loops to fastboot but when i flash the stock boot image it goes to normal and i can boot into the phone again
RokCruz said:
You need to re flash stock so, boot lastest twrp (fastboot boot twrp.img) and flash lastest stock rom.
And if you need an app as system use magisk module App Systemizer (you also need busybox module and Termux app from playstore) this is the only way (that I known) to convert user apps to system
Sent from my OnePlus7Pro using XDA Labs
Click to expand...
Click to collapse
tried that first part too, cant get into twrp and that makes sense now, i installed busy box but never opened the app to install to system/xbin
here's how ive done my part so far.. ever since i bricked my device last feb 24 , rendering it totally unresponsive.. that not even vol up & power button dont work
1. had to use msm tool just to boot my device. successfully boot my device to 9.5.3
2. device seemed to have a locked bootloader again so i un.lock it again. downloaded a patched 9.5.3 boot.img and flashed it via fastboot
3. successful root confirmed..
4. downloaded twrp 3.3.1-75 unofficial installer.. about 17.5mb. flashed it thru magisk as a module.. then install magisk ( as recommended) then reboot.
5. after a reboot.. and setting it up to my liking,, i reboot to twrp to flash the latest 10.3.1 stable rom..
6. flash twrp installer again.
7. hit reboot then choose Recovery . phone reboot to recovery again
8. flash magisk.zip which i downloaded earlier. then reboot.
done
updated to 10.3.1 with magisk & twrp intact..
btw.. i really dont know how to force my phone to reboot to twrp via PC ADB fastboot command.. easiest way for me to install TWRP is by flashing the TWRP INSTALLER as magisk module
cmurder61 said:
tried that first part too, cant get into twrp and that makes sense now, i installed busy box but never opened the app to install to system/xbin
Click to expand...
Click to collapse
Use busybox magisk module, don't install busybox apps!
Sent from my OnePlus7Pro using XDA Labs
cmurder61 said:
when i try to install "fastboot flash twrp" it goes thru but it always boot loops to fastboot but when i flash the stock boot image it goes to normal and i can boot into the phone again
Click to expand...
Click to collapse
That is because that is NOT the correct way to install TWRP img. You need to fastboot boot TWRP, then once in TWRP flash the TWRP installer zip, as I already mentioned.
This is described in the TWRP dev's thread (and you will see no mention of fastboot flash TWRP).
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Also make sure you use a current version of TWRP (latest is unofficial -76) which you can get from the above link.
redpoint73 said:
That is because that is NOT the correct way to install TWRP img. You need to fastboot boot TWRP, then once in TWRP flash the TWRP installer zip, as I already mentioned.
This is described in the TWRP dev's thread (and you will see no mention of fastboot flash TWRP).
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Also make sure you use a current version of TWRP (latest is unofficial -76) which you can get from the above link.
Click to expand...
Click to collapse
ive tried that still didn't work but illl try again i guess
santiagoruel13 said:
here's how ive done my part so far.. ever since i bricked my device last feb 24 , rendering it totally unresponsive.. that not even vol up & power button dont work
1. had to use msm tool just to boot my device. successfully boot my device to 9.5.3
2. device seemed to have a locked bootloader again so i un.lock it again. downloaded a patched 9.5.3 boot.img and flashed it via fastboot
3. successful root confirmed..
4. downloaded twrp 3.3.1-75 unofficial installer.. about 17.5mb. flashed it thru magisk as a module.. then install magisk ( as recommended) then reboot.
5. after a reboot.. and setting it up to my liking,, i reboot to twrp to flash the latest 10.3.1 stable rom..
6. flash twrp installer again.
7. hit reboot then choose Recovery . phone reboot to recovery again
8. flash magisk.zip which i downloaded earlier. then reboot.
done
updated to 10.3.1 with magisk & twrp intact..
btw.. i really dont know how to force my phone to reboot to twrp via PC ADB fastboot command.. easiest way for me to install TWRP is by flashing the TWRP INSTALLER as magisk module
Click to expand...
Click to collapse
See the way u did it is diff, i did not root first before installing twrp or install twrp as a magisk mod, what is the mod for magisk? where do i get it
cmurder61 said:
See the way u did it is diff, i did not root first before installing twrp or install twrp as a magisk mod, what is the mod for magisk? where do i get it
Click to expand...
Click to collapse
i just simplified it as magisk mod.. but in TWRP THREAD,, its named by maoronofrio as TWRP UNIFIED UNOFFICIAL INSTALLER
and it can only be installed by installing it as magisk module
here's the link
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
May be the first thing I'd think of trying it to disable any/all Magisk module installed.
Then, with the full OTA ROM stored in the main storage directory of your device... Basically a dirty Flash using the same OOS version you are using now and that should save the wipe/reset...
OTA Flash that and do not reboot and in Magisk manager check to see if manager is able to install Magisk as in install after OTA (?). That should work and then reboot device then verify. Don't forget to re-enable and Magisk modules...
Hope that can and will point you into the right direction.
I've not bothered with TWRP since I installed it then the next OTA went back to stock recovery. So, might be worth skipping TWRP for root as is not required so far as I can tell ... But I also have a Windows computer set up to flash via adb command alternatively.
Edit:. Think I forgot to say that the OTA update changed my TWRP back to stock recovery... But that's easy enough it change if desired
wugga3 said:
May be the first thing I'd think of trying it to disable any/all Magisk module installed.
Then, with the full OTA ROM stored in the main storage directory of your device... Basically a dirty Flash using the same OOS version you are using now and that should save the wipe/reset...
OTA Flash that and do not reboot and in Magisk manager check to see if manager is able to install Magisk as in install after OTA (?). That should work and then reboot device then verify. Don't forget to re-enable and Magisk modules...
Hope that can and will point you into the right direction.
I've not bothered with TWRP since I installed it then the next OTA went back to stock recovery. So, might be worth skipping TWRP for root as is not required so far as I can tell ... But I also have a Windows computer set up to flash via adb command alternatively.
Edit:. Think I forgot to say that the OTA update changed my TWRP back to stock recovery... But that's easy enough it change if desired
Click to expand...
Click to collapse
Hello, thanks for the reply, I wanna get a few things straight before doing anything that have the potential to brick my phone.
1. My phone rn isn't rooted, so I cant uninstall or disable Magisk modules, I CAN root my device but it is very unstable and im not sure doing it is a good idea, maybe there's another way to disable them?
2. What do you mean by dirty flash? Using the device update section and selecting the official OOS version I downloaded from OnePlus.com?
1) may be forget about root for now as that's probably not the priority at this time. Getting a stable operating system is the priority. And skip TWRP (don't see the point of if being needed at this step either).
2) my best guess is that I've used oxygen updater from the play store to download the full update (not incremental update) that exactly matches the one you have installed now - or search here and find the match to download or used the OnePlus cite to get the file. Then once that is downloaded to your device - go to settings/system/system updates/local update and install and reboot. That's the dirty Flash as in don't wipe/reset your device either before/after the installation. I'm hoping that this method will clean up both the recovery and boot images to stock and hopefully restore stability to your device without the wipe/reset.
Hope that helps and restore the device stability without TWRP nor root.
Hi wugga3, thanks again for your time, unfortunately a stable device is not my problem, I have managed to make a stable boot image by downloading the OOS version from the Oneplus website and flashing the boot image after attempting to root my device unsuccessfully.
My problem right now is that my device isn't rooted and I can't manage to root it using the methods I mentioned above, I currently have an unrooted stable OOS version 11.0.6.1.GM21AA.
NitayMa'ah said:
Hi wugga3, thanks again for your time, unfortunately a stable device is not my problem, I have managed to make a stable boot image by downloading the OOS version from the Oneplus website and flashing the boot image after attempting to root my device unsuccessfully.
My problem right now is that my device isn't rooted and I can't manage to root it using the methods I mentioned above, I currently have an unrooted stable OOS version 11.0.6.1.GM21AA.
Click to expand...
Click to collapse
How about installing just the magisk APK then taking the exctracted boot.img patching it in magisk APK, then disabling all security , take the patched boot.img and flash it in fast boot ( fastboot flash boot boot.img) reboot to system .
hammered58 said:
How about installing just the magisk APK then taking the exctracted boot.img patching it in magisk APK, then disabling all security , take the patched boot.img and flash it in fast boot ( fastboot flash boot boot.img) reboot to system .
Click to expand...
Click to collapse
Ill try it now thank you
NitayMa'ah said:
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
Click to expand...
Click to collapse
Here's a image file you can flash in fastboot. It's
NitayMa'ah said:
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
Click to expand...
Click to collapse
Here's an Orangefox prerooted OxygenOS 11 boot.img that works on 11 and 12. Just boot to fastboot, connect to a PC open a command prompt in the same directory and type..
fastboot flash boot boot-v9-root24.img...
Also it's easier to just flash both slots by this commands..
Fastboot flash boot_a boot-v9-root24.img and then fastboot flash boot_b boot-v9-root24.img...
I dual boot with this version of twrp and here's a solid boot img. You can flash it also in recovery or with "partition manager off play store. Check it out.
Fixed!
Thanks so much for the suggestions, which I might didn't fully consider in a rush...
The solution was to root my phone, reboot it all shaky and try to disable all Magisk modules (took me 2 tries because of the crashes and stuff), then flash again the original boot image, rebooting, creating a rooted boot.img using Magisk and flashing it.
Littlemether said:
Here's a image file you can flash in fastboot. It's
Here's an Orangefox prerooted OxygenOS 11 boot.img that works on 11 and 12. Just boot to fastboot, connect to a PC open a command prompt in the same directory and type..
fastboot flash boot boot-v9-root24.img...
Also it's easier to just flash both slots by this commands..
Fastboot flash boot_a boot-v9-root24.img and then fastboot flash boot_b boot-v9-root24.img...
I dual boot with this version of twrp and here's a solid boot img. You can flash it also in recovery or with "partition manager off play store. Check it out.
Click to expand...
Click to collapse
First of all thanks for the help but I ended up fixing it in another way.
Second of all, not really related but do you know if I can use this recovery on OP7Pro A12 custom Rom? (and flash it)