Hello Friends,
I have tried to root my OPO running on cos 13 through TWRP. Unfortunately the rooting failed and the phone failed to start, It hangs in "cyanogen mod ready " boot animation screen. some how I have managed to flash the phone to stock OS and again updated it to COS 13.
Now I would like to root the phone , Please someone provide me the right SUPERSU link !
so that I can use it through TWRP.
P.S: The bootloader is already Unlocked.
Thanks in advance :good:
I'm dealing with the same problem, and I've had to flash the system partition back to 5.1.1 and then upgrade to 6.0.1 3 times. Each time I try installing different versions of SuperSU It hangs. Apparently you aren't supposed to install it, and enable root from the developer options, but I don't have any such option.
srink.007 said:
Hello Friends,
I have tried to root my OPO running on cos 13 through TWRP. Unfortunately the rooting failed and the phone failed to start, It hangs in "cyanogen mod ready " boot animation screen. some how I have managed to flash the phone to stock OS and again updated it to COS 13.
Now I would like to root the phone , Please someone provide me the right SUPERSU link !
so that I can use it through TWRP.
P.S: The bootloader is already Unlocked.
Thanks in advance :good:
Click to expand...
Click to collapse
squigley said:
I'm dealing with the same problem, and I've had to flash the system partition back to 5.1.1 and then upgrade to 6.0.1 3 times. Each time I try installing different versions of SuperSU It hangs. Apparently you aren't supposed to install it, and enable root from the developer options, but I don't have any such option.
Click to expand...
Click to collapse
You need to flash the beta sytemless SU, downloads are at the bottom of this post. Latest is BETA-SuperSU-v2.67-20160121175247.zip - http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Ok, so I found a Beta version of SuperSU 2.7.1, and it seems to have worked. It was a different install process, saying it detected a "systemless root" or something, and it needed to patch the boot image. After that I appear to have root access again..
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Edit: Whoops, guess I should have refreshed the page before posting.. What you said is correct Ken.
Thank you
kenboyles72 said:
You need to flash the beta sytemless SU, downloads are at the bottom of this post. Latest is BETA-SuperSU-v2.67-20160121175247.zip - http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
thanks a lot
DONE
http://imgur.com/hh3qkdxGuys Finally I have done it. Yes the phone is rooted now
1. Flash Stock COS 12
2.Update Stock COS 13 using stock recovery
3. Installed SUPERSU (chainfire) from Play Store
3. Install TWRP
4. Create NANDROID BACKUP (optional , I have created since I doubted the rooting process on cos 13)
5. Installed Latest STABLE SUPERSU ( V 2.65 as of now) {my last attempt with beta 2.71 failed }
6. Done
http://imgur.com/hh3qkdx
TWRP 3.0.2-0
SuperSu Pro 2.78
Android 6.0 Marshmallow build MPH24.49-18
I have systemless rooted my phone as per the instructions at http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
although, it didn't work without some tweaking... Unfortunately I don't remember what steps I took to get it working.
I am not sure of the process form here. Now that I have root, am I supposed to flash boot_orig.img permanently or just when I want to update?
I have tried:
fastboot flash boot boot_orig.img
but I loose wifi and can't download.
I have tried letting the OTA fail with the boot.img flashed, then reflashed with boot_orig.img and tried to install the update zip file via TWRP, but that fails.
I made a TWRP backup before I started rooting and for every major step after that, so I can start fresh if need be.
[EDIT]
I noticed on this thread, http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 , the following comment:
You must absolutely re-flash your stock /system partition, or the separate root instances will interfere with each other. The installer for this experiment will not clean up old root files.
- Flash stock /system (and /vendor and /oem, if present)
- Flash the attached boot image
- Flash the attached SuperSU ZIP in TWRP
Click to expand...
Click to collapse
Could this be the problem? If so, How do I "flash stock /system (and /vendor and /oem, if present)"?
Any help appreciated...
Greetings from the AT&T S5 Forum!
We've recently discovered the usability of engineering firmwares in our journey to get root, as outlined here: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
Now, I'm here to try to bring this same method to you guys! With the help of @jrkruse, here are the root instructions:
How it works:
These engineering firmwares are usually based on KitKat, and have their SELinux set to PERMISSIVE. This not only leaves the firmware very vulnerable to towelroot, but it also keeps SELinux from raining on our parade.
Thanks again to @jrkruse for the updated root instructions, and @mohammad.afaneh for the Safestrap!
Revised October 6, 2018.
Directions:
Before you get going, use this APK to check your eMMC chip's CID:
eMMC_CID_Checker_.apk[/SIZE][/B][/CENTER]
Your CID Number will be the first two numbers in the eMMC Box under "CID"
If the first two digits are "15," your bootloader is unlockable and you can install TWRP/AOSP ROMs.
If the first two digits are "11," your bootloader is not unlockable, but you can use rooted Lollipop ROMs that are based on TouchWiz (with the help of SafeStrap). You can also use non-rooted Marshmallow ROMs (based on TouchWiz) and flash mods with SafeStrap.
BACK UP YOUR STUFF NOW, YOUR STORAGE WILL BE WIPED!
If your eMMC CID starts with "15," start here:
1. Download and unzip this file: EMMC_15_Root_Bootloader_Unlock S5_QB2_PB1.zip
2. Reboot the phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the "COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5" firmware in the AP Slot
4. Flash and let the phone process the file. It will reboot twice and you should be dropped into Android within a minute and a half.
5. Copy the following files to your phone:
"RootS5" Folder and "EMMC_15_SafeStrap_QA1_6_0_1_MM_Bootloader_Unlock_AIO.zip",
and EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery choose install and select EMMC_15_SafeStrap_QB2_6_0_1_MM_Bootloader_Unlock_AIO.zip
13. Install the zip. The phone will power off. Reboot the phone to TWRP Recovery with Pwr+VolUp+Home
14. You will now have an Unlocked Bootloader and TWRP recovery Installed. Now whoose Wipe > Advanced Wipe. Select Dalvik Cache; Data; System; Cache, and swipe the swipe to wipe bar. When done, click the back button, click Install, and choose:
EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
You're done! You will have stock rooted Marshmallow QB2 Build installed with an unlocked bootloader and custom recovery.
If your eMMC CID starts with "11," start here:
1. Download and unzip this file: EMMC_11_ Root S5_QB2_PB1.zip
2. Reboot Phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot.
4. Flash and let the phone reboot. It will reboot to recovery and finish install then it will reboot and take about 20 seconds to boot.
5. Copy the following to the phone:
Root S5 Folder, EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip, and the TouchWiz ROM you want to install.
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery, choose what firmware you want to be on:
Lollipop 5.0 Firmware=EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip
Marsmhallow 6.0 Firmware=EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip
13. Install the firmware zip, and then flash a TouchWiz Lollipop ROM. (Here is the latest stock rooted Lollipop Rom: VZW_BPB1_ODEX_DEODEX_V9.zip). You may want to download a copy of the latest SuperSu zip, and flash if installing a Lollipop ROM that is not rooted. Remember that you cannot root Marshmallow ROMs, so do not try and flash the SuperSu zip on a Marshmallow Rom (you will softbrick if you do).
14. After you install any Lollipop ROM, you may need to reinstall SafeStrap Recovery. Most of the time you don't have to and SafeStrap can be reached by flashing the KitKat Kernel in Download Mode with ODIN. But, in some cases, when flashing a ROM that flashes a system.img instead of a system folder, you may lose SafeStrap during install. This will be the case if you install the above ROM. You can reinstall it after the ROM is booted up. A Safestrap-G900V-4.04_LL_MM.apk is included that will flash a version of SafeStrap that will allow you to reboot to SafeStrap Recovery without flashing a KitKat kernel in Odin. Install BusyBox again from the BusyBox App in the RootS5 Folder. Install Safestrap-G900V-4.04_LL_MM.apk and make sure to grant SuperSU access. It may take a few seconds to prompt. If SafeStrap is not installed, click "Install Recovery". If Safestrap is still installed click on "Uninstall Recovery", close the app, and reopen it. It should say recovery is not installed. Now click on "Install Recovery". If this doesn't work, reboot the phone and try again. Once installed, you can just click reboot to SafeStrap from the SafeStrap app and you will reboot straight to SafeStrap. Remember to flash the appropriate Kernel when leaving SafeStrap!
Download and place these on your device:
LL_KERNEL_SS-FF_Flashable.zip, and
MM_KERNEL_SS-FF_Flashable.zip
If something goes wrong you can usually get back to SafeStrap by simply rebooting the phone to Download Mode and flashing NI2_stock_kernel.tar.md5. When the phone reboots, watch for the SafeStrap splash screen and enter SafeStrap.
WARNING: Do NOT change ANY boot options in SafeStrap. ROM slots cannot be used, so you must flash to the Stock ROM slot EVERY TIME OR YOU WILL SOFTBRICK. Some functions don't work in SafeStrap, like choosing an image file to flash directly. All image files must be flashed via zip file.
For CID11 users that have followed the above instructions and want to use Marshmallow:
QA1_MM_Firmware_With_QA1_Bootloader_CAUTION.zip=Marshmallow Firmware (use if flashing a MM TW ROM other than the one posted below). Just remember there is no root for Marshmallow ROMs, but having SafeStrap installed gives you the ability to do things like flash debloat Scripts, Mods, etc and the ability to go back to a rooted Lollipop ROM without going through the root process all over again. Simply flash the Lollipop ROM and EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip.
Here is a special ROM that includes SafeStrap, so you can flash a Marshmallow ROM and still be able to use SafeStrap to flash things. You will not have root but you can still access SafeStrap. VZW_QB2_STOCK_SAFESTRAP_ONLY_V1.zip More Instructions about this can be found HERE
When using a MM ROM, it is necessary to flash the KitKat Kernel with Odin to enter SafeStrap. When leaving SafeStrap, make sure to flash MM_KERNEL_SS-FF_Flashable.zip which is necessary to leave SafeStrap (This zip will be placed on storage automatically with the above ROM and you also download it in instructions above.) Just navigate to the .MM_KERNEL_SS-FF folder located on both Internal and External storage.
i'll odin my spare s5 to stock later if i get the chance and let you know if this works on my g900v.
The methods in post 1 are seriously outdated the easiest method to obtain unlocks or update or downgrade unlocked bootloaders can be found below they were updated December of 2021
EMMC 15 Unlocking Bootloader
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
EMMC 15 Updating Unlocked Bootloaders Or Downgrading
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
For Rooting EMMC 11 Phones
2021_VZW_Locked_Bootloader_EMMC_11_Rooted/NonRooted_Roms_With_Safestrap_MM_LL_KK
This Process Will Install On The EMMC_11 Locked Bootloader Verizon S5 Marshmallow QL1 Stock Rom NonRooted With Safestrap. Lollipop PB1 Stock Rom Rooted With Safestrap. KK Rom Rooted With Safestrap What This Does This gives you the ability to...
forum.xda-developers.com
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
its uploading sorry it failed at 99 percent
jrkruse said:
its uploading sorry it failed at 99 percent
Click to expand...
Click to collapse
Thank you! very much appreciated
jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
Its uploaded
jrkruse said:
Its uploaded
Click to expand...
Click to collapse
Downloading as we speak. I will let you know how everything goes!
tested on one of the spares I had kicking around
does what it says on the tin
!kickass
The apps are kind of hard to see in the App Drawer I installed View attachment Apex_Lancher.apk and it gets rid of that Info screen covering the Apps
The OP has been updated to reflect @jrkruse 's new instructions
AptLogic said:
The OP has been updated to reflect @jrkruse 's new instructions
Click to expand...
Click to collapse
I just cleaned them up a little I'll Pm you the changes
---------- Post added at 08:22 PM ---------- Previous post was at 07:32 PM ----------
jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.
jrkruse said:
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.
Click to expand...
Click to collapse
Which, I should add, has about a 1 in 10,000,000 chance of occurring.
I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used: (one linked in original thread)
http://org.downloadcenter.samsung.c...NG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe
guitar1238751 said:
I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used:
Click to expand...
Click to collapse
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.
AptLogic said:
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.
Click to expand...
Click to collapse
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.
guitar1238751 said:
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.
Click to expand...
Click to collapse
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.
AptLogic said:
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.
Click to expand...
Click to collapse
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks
guitar1238751 said:
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks
Click to expand...
Click to collapse
Happy to help
["QUOTE=AptLogic;71212479]Happy to help [/QUOTE]
Hi, I have a problem where I can not do root in my mi-4c after this miui 8.2 update came out, there was a day when my cell phone updated and restored everything, I flash everything in TWRP, I executed the script To disable DM verification and when I gave flash in supersu it gave infinite loop, does anyone know how to solve this? Is it necessary to downgrade to re-rotate the device again? Can someone tell me what the source of the problem is? If it is the new binary su or if the script does not work anymore?
Must flash the newest version of SuperSU
http://download.chainfire.eu/supersu-beta
isaque-v-soares said:
Hi, I have a problem where I can not do root in my mi-4c after this miui 8.2 update came out, there was a day when my cell phone updated and restored everything, I flash everything in TWRP, I executed the script To disable DM verification and when I gave flash in supersu it gave infinite loop, does anyone know how to solve this? Is it necessary to downgrade to re-rotate the device again? Can someone tell me what the source of the problem is? If it is the new binary su or if the script does not work anymore?
Click to expand...
Click to collapse
Had this problem too.
In version 8.2.x.x the system partition has no free space to accommodate supersu although twrp doesn't complain when installing supersu- this corrupts the system partition.
You should reflash the system partition and start over.
Before installing supersu you should delete some useless system apps like AnaliticsCore, BaiduLocation (or smth), SystemAdSolution using twrp's file manager to make some space on the system partition.
If you are not comfortable with that you should try Magisk.
thanks bro i try
Can you tell me what this AnaliticsCore app is for? It n exists only in the miui already used other devices like moto G2 and moto maxx and I already saw this app there
Hello XDA !
This is my first post..sorry for my bad english.
I bought a S7 (SM-G930F) Android 8.0 and i rooted it then i noticed that was just systemless root.. and it's totally useless for me because i want to uninstall system apps and change build.prop..
so I flashed the stock rom and reflashed TWRP, then I executed a command to force SuperSU to install in system
(echo SYSTEMLESS=false>>/data/.SuperSU)
and I installed SuperSU.zip..but it stucks on bootloop.. I tried many different SuperSU.zip versions even a modified version for system mode root, but nothing works..
by the way I installed no-verity-opt-encrypt-6.1.zip before installing SuperSU.zip !
ysnelazzab said:
Hello XDA !
This is my first post..sorry for my bad english.
I bought a S7 (SM-G930F) Android 8.0 and i rooted it then i noticed that was just systemless root.. and it's totally useless for me because i want to uninstall system apps and change build.prop..
so I flashed the stock rom and reflashed TWRP, then I executed a command to force SuperSU to install in system
(echo SYSTEMLESS=false>>/data/.SuperSU)
and I installed SuperSU.zip..but it stucks on bootloop.. I tried many different SuperSU.zip versions even a modified version for system mode root, but nothing works..
by the way I installed no-verity-opt-encrypt-6.1.zip before installing SuperSU.zip !
Click to expand...
Click to collapse
i havent rooted an S7 in a while, but dont you just flash twrp in Odin with the reboot box unchecked and once the flash completes, reboot into twrp which will present you a slider that says something along the lines of "slide to allower SU access" or something like that. Once youve done that, then you flash magisk in TWRP, boot, install busybox, and you should then be asked if you want to grant SU access to busybox, if it does that, youre all set
youdoofus said:
i havent rooted an S7 in a while, but dont you just flash twrp in Odin with the reboot box unchecked and once the flash completes, reboot into twrp which will present you a slider that says something along the lines of "slide to allower SU access" or something like that. Once youve done that, then you flash magisk in TWRP, boot, install busybox, and you should then be asked if you want to grant SU access to busybox, if it does that, youre all set
Click to expand...
Click to collapse
Thank you so much for your response !
I did everything in the correct way, i flashed twrp with reboot option disabled.. and i formated data then reboot to recovery and I installed no verity and after that i installed SuperSU and it's done successfully but it ended up with a bootloop..
also I tried to install a system mode supersu.zip and it freezes TWRP and stuck on "installing"
I think literally I can't do the system root.. so i did systemless root.
ysnelazzab said:
Thank you so much for your response !
I did everything in the correct way, i flashed twrp with reboot option disabled.. and i formated data then reboot to recovery and I installed no verity and after that i installed SuperSU and it's done successfully but it ended up with a bootloop..
also I tried to install a system mode supersu.zip and it freezes TWRP and stuck on "installing"
I think literally I can't do the system root.. so i did systemless root.
Click to expand...
Click to collapse
the F models should allow for system root, not sure tho as i didnt spend much time with my S7 and S7 Edge. Still have em tho. If i remember, i could dink with them tonight
youdoofus said:
the F models should allow for system root, not sure tho as i didnt spend much time with my S7 and S7 Edge. Still have em tho. If i remember, i could dink with them tonight
Click to expand...
Click to collapse
mine is G930F oreo 8.0 i tried everything to do system root but failed.. one thing I didn't do is a custom rom. i prefer a rooted stock rom.
ysnelazzab said:
mine is G930F oreo 8.0 i tried everything to do system root but failed.. one thing I didn't do is a custom rom. i prefer a rooted stock rom.
Click to expand...
Click to collapse
well, you cant do a custom ROM without a custom recovery. bootloader is unlocked i assume
youdoofus said:
well, you cant do a custom ROM without a custom recovery. bootloader is unlocked i assume
Click to expand...
Click to collapse
as I said i have TWRP which is a custom recovery. and i don't want custom ROM i just want my stock ROM system rooted not systemless.
ysnelazzab said:
as I said i have TWRP which is a custom recovery. and i don't want custom ROM i just want my stock ROM system rooted not systemless.
Click to expand...
Click to collapse
im well aware that TWRP is a custom recovery, i remember when it first launched and people were converting from CWM to TWRP. Anyways, if youve successfully installed twrp, try factory resetting the device and then booting. You should only need to flash magisk in TWRP and busy box in the OS once booted