Database Users

How to Root without flashing custom recovery

HOW TO ROOT YOUR DEVICE WITHOUT FLASHING RECOVERY
This can be done with two methods.
ADB or FASTBOOT.
I have tested both methods and they worked for me.
I tested this on JSS15J. I am not sure about any other versions but I guess it should work.
SOME BASIC INFORMATION
Usually when you want to root your device, you must have UNLOCKED BOOTLOADER.
A CUSTOM RECOVERY is usually used to flash SuperSU to gain root access.
CUSTOM RECOVERIES ARE USUALLY FLASHED (they permanently replace your stock recovery)
In this guide, You BOOT into custom recovery by going into BOOTLOADER and then using fastboot/adb tools to flash SuperSU .
Booting is temporary and thus once you restart from recovery, the custom recovery will be gone
Make sure, you have USB debugging mode enabled. To go into bootloader you can either use adb commands ( Type [adb reboot bootloader] in cmd in platform tools directory with your device connected) or do it manually by turning it off and then holding power and volume down.
You must also have platform tools of SDK (Fastboot and ADB) for this to work. MAKE SURE YOU OPEN CMD into the folder where platform tools are present.
Try it on OWN risk. I will not be responsible for bricked devices or any damage.
ADB METHOD
Connect to your PC and make sure USB debugging is on.
COMMANDS IN BRACKETS. DON'T WRITE THEM. COMMAND WOULD BE LIKE : fastboot boot recovery.img
MAKE SURE YOUR DEVICE HAS UNLOCKED BOOTLOADER
(fastboot boot [recovery.img])--------------------- Name of recovery to be here
Mount /system and push the necessary files once the recovery has started:
(adb push su /system/xbin)
(adb push Superuser.apk /system/app)
Set correct permissions:
(adb shell)------------------------------ You have got into your device's shell
(chmod 06755 /system/xbin/su)
(chmod 0644 /system/app/SuperSU.apk)
(exit)
Reboot:
(adb reboot)
FASTBOOT METHOD
This is relatively easier as you will boot into custom recovery temporarily and then flash ZIP of SuperSU. Afterwards I recommend to clear davik cache and restart.
UNLOCKED BOOTLOADER REQUIRED
Boot into bootloader.
Type these commands to boot into custom recovery. This will not flash recovery and you will have stock recovery once you restart.
fastboot boot recovery recovery.img where recovery.img will be the file name of recovery
(After 4.4, use this command "fastboot boot recovery.img" instead of above mentioned)
After booting into reccovery, flash SuperSU and you are done.
I recommend clearing dalvik cache before leaving and restart.
And you are done.
YOU CAN ALSO USE A PREROOTED KERNEL WHICH YOU CAN FLASH VIA FASTBOOT. I AM NOT SURE IF THERE IS ANY
For information on how to retain root after OTA, please refer to this :
Update Super SU is also taken from this guide.
http://forum.xda-developers.com/showthread.php?t=2415497
For Recovery/SuperSU/TWRP
http://forum.xda-developers.com/showthread.php?t=2382051
CWM
http://forum.xda-developers.com/showthread.php?t=2381544
PLATFORM TOOLS:
http://www.androidfilehost.com/?fid=9390355257214632011
If you are stuck in a bootloop, make sure you have cleared dalvik cache in custom recovery.
I got bootloop when i tried with fastboot method as I was new to twrp, I explored it a bit and tried to remove system and tried overwriting data to see how it is different from CWM and check its strength. I got an error clearing cache so I rebooted into custom recovery to clear dalvik and my nexus booted fine (DON'T TRY THIS, JUST CLEAR CACHE AND WIPE DATA and restart)
REMEMBER, UNLOCKING BOOTLOADER WILL DELETE ALL YOUR DATA AND DOING WIPES WILL ALSO DELETE ALL YOUR DATA.
DALVIK WON'T DELETE YOUR DATA BUT
MAKE SURE YOU HAVE MADE A BACKUP using BACKUP PRO (non rooted) or Helium (non rooted) and Titanium Backup Pro (Daah, you are not rooted so this won't work)
GOOD LUCK

Booting into custom recovery to install root works fine.
As you mentioned unlocking bootloader is still a prerequisite.
You may want to just use the SuperSU install zip though. Though I haven't tried Superuser on this tablet, it is my understanding it hasn't been modified to work with 4.3 security. That may have changed since I last looked so if you find differently please post. SuperSU added a daemon mode to deal with 4.3 security changes.

sfhub said:
Booting into custom recovery to install root works fine.
As you mentioned unlocking bootloader is still a prerequisite.
You may want to just use the SuperSU install zip though. Though I haven't tried Superuser on this tablet, it is my understanding it hasn't been modified to work with 4.3 security. That may have changed since I last looked so if you find differently please post. SuperSU added a daemon mode to deal with 4.3 security changes.
Click to expand...
Click to collapse
I got bootloop but then realised it might due to trying to wipe system in twrp. Clearing dalvik worked fine .SuperSU used

So you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my Nexus 7 (2013)

Muikkuman said:
So you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
The trick here is to BOOT into custom recovery BUT not FLASH recovery permanently. Once you restart, the CUSTOM recovery will be gone.
You can use simple commands if using Fastboot
fastboot boot recovery [recovery name.img]
This way you will install SuperSU using recovery which is relatively easier than ADB commands.
You will only go into recovery temporarily.
I also read a forum where you can preserver root even after OTA/ Updates.
[UPDATE]
http://forum.xda-developers.com/showthread.php?t=2415497
Do check that out as well.
I tried this with Twrp and superSU.
I got bootloop as I have been always CWM person so I accidently tried to delete system too with dalvik cache and hard reset and I got an error
However, I boot again into recovery and cleared wipes and the bootloop was gone

Hnk1 said:
The trick here is to BOOT into custom recovery BUT not FLASH recovery permanently. Once you restart, the CUSTOM recovery will be gone.
You can use simple commands if using Fastboot
fastboot boot recovery [recovery name.img]
This way you will install SuperSU using recovery which is relatively easier than ADB commands.
This way you will only go into recovery temporarily.
I also read a forum where you can preserver root even after OTA/ Updates.
Do check that out as well.
I tried this with Twrp and superSU.
I got bootloop as I have been always CWM person so I accidently tried to delete system too with dalvik cache and hard reset and I got an error
However, I boot again into recovery and cleared wipes and the bootloop was gone
Click to expand...
Click to collapse
Thanks for your reply I'll make sure to check everything out.
Sent from my Nexus 7 (2013)

Muikkuman said:
Thanks for your reply I'll make sure to check everything out.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Anytime mate

How do we clear dalvik without a custom recovery?

Master619 said:
How do we clear dalvik without a custom recovery?
Click to expand...
Click to collapse
You restart your device. Boot into bootloader and use fastboot to Boot into custom recovery(command given in post above).Once Into recovery, you can easily clear dalvik cache.
And remember, it might not require clearing cache because I was exploring twrp n overwriting data n tried To delete system to see how powerful the recovery is. I will update guide now

muikkuman said:
so you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my nexus 7 (2013)
Click to expand...
Click to collapse
master619 said:
how do we clear dalvik without a custom recovery?
Click to expand...
Click to collapse
guide updated. Check it.
Platform tools are being attached

The "fastboot boot recovery recovery.img" command is not working anymore. The command prompt returns with a "cannot load recovery" error. At least that's what it does on my Nexus 7 running Android 4.4.2.
This seems to affect Android 4.3 and upwards according to this Nexus 4 thread: http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
There's a workaround with a different fastboot command line as mentioned in the thread. I wonder if there's also a fix for the Nexus 7. Any replies would be greatly appreciated.

gunner49 said:
The "fastboot boot recovery recovery.img" command is not working anymore. The command prompt returns with a "cannot load recovery" error. At least that's what it does on my Nexus 7 running Android 4.4.2.
This seems to affect Android 4.3 and upwards according to this Nexus 4 thread: http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
There's a workaround with a different fastboot command line as mentioned in the thread. I wonder if there's also a fix for the Nexus 7. Any replies would be greatly appreciated.
Click to expand...
Click to collapse
Did you try: fastboot boot recovery.img ?

mdamaged said:
Did you try: fastboot boot recovery.img ?
Click to expand...
Click to collapse
That worked a treat! Thanks a lot mate!

Those who finding difficulty in rooting Nexus 7 (2013) can use Wugfresh Nexus Root Toolkit. It is so powerful that you would find every function you would like to do on your Nexus 7, from the comfort of your PC. Also watch qbking77 's video on using the Toolkit for further information.

Help Me Root This Thing! XT1575

I've done a lot of research on a reliable way to root my Moto X Pure Edition XT1575 and want someone to check my plan before I pursue this. I'm gonna download TWRP for Clark and superSU 2.78 and put them in the same folder and open up the command prompt in that folder. Then hook up to the PC and enter the following command "fastboot boot twrp.img" then I'm gonna replace the twrp.img with the name of the twrp file and backup to the SD. Then reboot into the bootloader again and flash twrp with fastboot "fastboot flash recovery twrp.img" then start recovery and go to reboot into recovery again to lock it in. Then I'm booting back into twrp and going to Advanced & Terminal and entering the following command "echo SYSTEMLESS=true>>/data/.superSU then back home then flash superSU 2.78.
Please correct me on everything that may be wrong. If there's a better way to root, tell me how to do it your way.
My device info:
Moto X Pure Edition XT1575 (clark)
Build# MPH24.49-18
Kernel version 3.10.84
Android version 6.0
Bootloader OxAo48
Sent from my Moto X Pure Edition

ElectroJoe said:
I've done a lot of research on a reliable way to root my Moto X Pure Edition XT1575 and want someone to check my plan before I pursue this. I'm gonna download TWRP for Clark and superSU 2.78 and put them in the same folder and open up the command prompt in that folder. Then hook up to the PC and enter the following command "fastboot boot twrp.img" then I'm gonna replace the twrp.img with the name of the twrp file and backup to the SD. Then reboot into the bootloader again and flash twrp with fastboot "fastboot flash recovery twrp.img" then start recovery and go to reboot into recovery again to lock it in. Then I'm booting back into twrp and going to Advanced & Terminal and entering the following command "echo SYSTEMLESS=true>>/data/.superSU then back home then flash superSU 2.78.
Please correct me on everything that may be wrong. If there's a better way to root, tell me how to do it your way.
My device info:
Moto X Pure Edition XT1575 (clark)
Build# MPH24.49-18
Kernel version 3.10.84
Android version 6.0
Bootloader OxAo48
Sent from my Moto X Pure Edition
Click to expand...
Click to collapse
You've researched well. Couple things: The command is "echo SYSTEMLESS=true>>/data/.supersu", you added capitols on supersu. Next your first command of "fastboot boot twrp.img (or whatever you rename the TWRP recovery image to)" will live boot TWRP, which for our device is not necessary. Live booting is essentially booting into a custom recovery environment without actually installing the recovery. This is useful for devices that DO NOT have factory images available, which allows you to make a backup in the live environment prior to altering your device. We have factory images and factory recovery images, so you can skip this step and go right into "fastboot flash recovery twrp.img (or again, whatever you rename the recovery image to). Then after the recovery flash from within fastboot, you must reboot into recovery using the button select options within fastboot or your recovery will be overwritten by the stock recovery. Upon first boot of TWRP you'll have an option to keep your device read only or read/write. I personally choose NOT to keep it read only, rather read/write, because I don't care about taking OTA's with a custom recovery, but this is up to you. Then you'll want the supersu.zip on your device already (you want the regular standard current version, not a modded one from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703), either on your internal or external sd. And yes, prior to flashing supersu enter the command in TWRP without quotes "echo SYSTEMLESS=true>>/data/.supersu" (this prevents the bootloop that our device gets when flashing supersu in systemless mode). And your good to go. I just did this a few weeks ago from clean fastboot flashing the latest factory image, works perfectly.
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.

Thanks for taking the time to educate me on this. I'm gonna give it a try in a few minutes. Will I be a developer if I get it right? Hahaha I'll let you know how it goes
Sent from my Moto X Pure Edition

annoyingduck said:
You've researched well. Couple things: The command is "echo SYSTEMLESS=true>>/data/.supersu", you added capitols on supersu. Next your first command of "fastboot boot twrp.img (or whatever you rename the TWRP recovery image to)" will live boot TWRP, which for our device is not necessary. Live booting is essentially booting into a custom recovery environment without actually installing the recovery. This is useful for devices that DO NOT have factory images available, which allows you to make a backup in the live environment prior to altering your device. We have factory images and factory recovery images, so you can skip this step and go right into "fastboot flash recovery twrp.img (or again, whatever you rename the recovery image to). Then after the recovery flash from within fastboot, you must reboot into recovery using the button select options within fastboot or your recovery will be overwritten by the stock recovery. Upon first boot of TWRP you'll have an option to keep your device read only or read/write. I personally choose NOT to keep it read only, rather read/write, because I don't care about taking OTA's with a custom recovery, but this is up to you. Then you'll want the supersu.zip on your device already (you want the regular standard current version, not a modded one from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703), either on your internal or external sd. And yes, prior to flashing supersu enter the command in TWRP without quotes "echo SYSTEMLESS=true>>/data/.supersu" (this prevents the bootloop that our device gets when flashing supersu in systemless mode). And your good to go. I just did this a few weeks ago from clean fastboot flashing the latest factory image, works perfectly.
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.
Click to expand...
Click to collapse
It worked! I'm rooted and looking for a stable rom with a lot of features and customizations that works with Verizon LTE. I also want viper4android. I'm glad I backed up because I tried flashing a viper4android zip and it caused my phone not to boot. It just sat at the unlocked bootloader warning so I just restored it. Evidently, I was supposed to unzip the file in esfile Explorer and install the apk. I think I also needed the selinux mode changer app.
What would I gain by installing a custom Kernel to my rooted stock rom? Can I even do that?
Sent from my XT1575 using Tapatalk

ElectroJoe said:
It worked! I'm rooted and looking for a stable rom with a lot of features and customizations that works with Verizon LTE. I also want viper4android. I'm glad I backed up because I tried flashing a viper4android zip and it caused my phone not to boot. It just sat at the unlocked bootloader warning so I just restored it. Evidently, I was supposed to unzip the file in esfile Explorer and install the apk. I think I also needed the selinux mode changer app.
What would I gain by installing a custom Kernel to my rooted stock rom? Can I even do that?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Flash ViPER4Android from here, no SELinux changing app needed: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
As for custom kernel, Frankenclark. Features available is in the post: http://forum.xda-developers.com/moto-x-style/development/kernel-frankenclark-t3289939

annoyingduck said:
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.
Click to expand...
Click to collapse
I literally did this to a fresh MXPE two weeks ago... misspelled the filename so it wasn't recognized (it isn't supersy apparently), and flashed SuperSU 2.78-SR1, rebooted and stuck at boot logo for 20 minutes. Rebooted into TWRP and entered the correct echo command to create the .supersu file and reboot, it looped twice quickly and then went to the lockscreen after a 2-3 minutes.

help for p8 lite's Root

hello, for first thing i need say sorry for my english, because it isn't good. (now i using google translate for write this problem)
My model is ALE-L21 in B585, I had run all the instructions to root. they are:
1)unlock the bootloader with the code.
2)download the recovery TWRP for p8 lite, adb tools and supersu.zip
3)reboot phone to fastboot,and run the adb.exe with cmd.exe, after run the code adb devices for controll if device is connected.
4)ricalled recovery TWRP in 1.img and copy it in adb tools' folder.
5)flash recovery with code fastboot flash recovery 1.img.
6)reboot the devices in recovery twrp for istall supersu.zip saved in sd card.
my problem is in 6), when i went to recovery, After 5-45 seconds the device will restart automatically, even if I do not do anything. At this time I can still get into the system.
If fortunately succeeded in installing supersu.zip, during the reboot I remain in huawei's logo.
i need to reflash the stock firmware to save it.
I would like to have this problem compared to others, help me, thank you.

Qmy1997 said:
hello, for first thing i need say sorry for my english, because it isn't good. (now i using google translate for write this problem)
My model is ALE-L21 in B585, I had run all the instructions to root. they are:
1)unlock the bootloader with the code.
2)download the recovery TWRP for p8 lite, adb tools and supersu.zip
3)reboot phone to fastboot,and run the adb.exe with cmd.exe, after run the code adb devices for controll if device is connected.
4)ricalled recovery TWRP in 1.img and copy it in adb tools' folder.
5)flash recovery with code fastboot flash recovery 1.img.
6)reboot the devices in recovery twrp for istall supersu.zip saved in sd card.
my problem is in 6), when i went to recovery, After 5-45 seconds the device will restart automatically, even if I do not do anything. At this time I can still get into the system.
If fortunately succeeded in installing supersu.zip, during the reboot I remain in huawei's logo.
i need to reflash the stock firmware to save it.
I would like to have this problem compared to others, help me, thank you.
Click to expand...
Click to collapse
Flash Magisk v13.3 (all instructions and files here -> https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) and you're ready to go

Sonofapo said:
Flash Magisk v13.3 (all instructions and files here -> https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) and you're ready to go
Click to expand...
Click to collapse
thank you for moment

Sonofapo said:
Flash Magisk v13.3 (all instructions and files here -> https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) and you're ready to go
Click to expand...
Click to collapse
thank you, very much. i had rooted my p8 lite with succesed. But the application always starts automatically, even if it is blocked with rom toolbox lite.

A2017G with flashed SuperSU but no root

Hello, i want to root my device with SuperSU but i can't.
Now there is:
bootloader: unlocked
fastboot: working
recovery: TWRP 3.3.1-0
rom: stock B12
I try to root through axon7toolkit, device boot to fastboot, then app shows:
HTML:
Checking ADB\Fastboot Connectivity...
ADB device connected!
Rebooting to bootloader...
Checking Fastboot Connectivity...
Fastboot device connected!
Booting TWRP...
downloading 'boot.img'...
OKAY [ 0.326s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.348s
Tap 'Keep read-only'" on startup!
then app shows error "ADB recovery device is not connected". I manually select Recovery mode from fastboot. TWRP launch without "Keep read-only" option. I click mount, selecting all options and checking "Keep read-only" option. Then I click OK in axon7toolkit error message and TWRP make a script. After that device boot twice. SuperSU app says SU is not installed.
I try to click OK in axon7toolkit error without mounting with "Keep read-only" (just clicking OK when TWRP launch) but it's the same.
I try to root by install SuperSU v2.82 SR5 through TWRP, script working and says done, but after confirm there is the same as above.
I must flash special bootstack or maybe B12 is possibile to root?
EDIT:
I try to download terminal, then type
HTML:
adb shell reboot disemmcwp
then device was rebooting. After that I type in emulator
HTML:
su
and SuperSU asks for root permission. I allow that, but terminal no go to root mode and typing
HTML:
reboot disemmcwp
don't change anything.

ColorfulPoland said:
Hello, i want to root my device with SuperSU but i can't.
Now there is:
bootloader: unlocked
fastboot: working
recovery: TWRP 3.3.1-0
rom: stock B12
I try to root through axon7toolkit, device boot to fastboot, then app shows:
Checking ADB\Fastboot Connectivity...ADB device connected!Rebooting to bootloader...Checking Fastboot Connectivity...Fastboot device connected!Booting TWRP...downloading 'boot.img'...OKAY [ 0.326s]booting...FAILED (remote: unknown command)finished. total time: 0.348sTap 'Keep read-only'" on startup!
then app shows error "ADB recovery device is not connected". I manually select Recovery mode from fastboot. TWRP launch without "Keep read-only" option. I click mount, selecting all options and checking "Keep read-only" option. Then I click OK in axon7toolkit error message and TWRP make a script. After that device boot twice. SuperSU app says SU is not installed.
I try to click OK in axon7toolkit error without mounting with "Keep read-only" (just clicking OK when TWRP launch) but it's the same.
I try to root by install SuperSU v2.82 SR5 through TWRP, script working and says done, but after confirm there is the same as above.
I must flash special bootstack or maybe B12 is possibile to root?
EDIT:
I try to download terminal, then type adb shell reboot disemmcwp
then device was rebooting. After that I type in emulator su
and SuperSU asks for root permission. I allow that, but terminal no go to root mode and typing reboot disemmcwp
don't change anything.
Click to expand...
Click to collapse
i always just ask, why SuperSU?
Don't use "Keep read only" on TWRP, that's useful when you have DM-verity enabled but SuperSU, Magisk, or the no verity zip disable that. I don't know if this is your problem but it might as well be.
Also, issue "reboot disemmcwp" from the TWRP terminal or via adb in TWRP. it might do the trick

When I type the post, I use SuperSU because Magisk no work. Now I know Magisk works to 16.7 but now the problem is because I have a problem with "corrupted SD card" after flashing (I have read and many other people have this problem). I don't know how to fix it, because formating don't help, so I still be with SuperSU
When I go home I try use terminal from TWRP, thank for your help
EDIT:
TWRP not recognize my commends

ColorfulPoland said:
When I type the post, I use SuperSU because Magisk no work. Now I know Magisk works to 16.7 but now the problem is because I have a problem with "corrupted SD card" after flashing (I have read and many other people have this problem). I don't know how to fix it, because formating don't help, so I still be with SuperSU
When I go home I try use terminal from TWRP, thank for your help
EDIT:
TWRP not recognize my commends
Click to expand...
Click to collapse
lol. Try using Magisk, then get all of your stuff out of the SD card and format it. If your files aren't bigger than 4gb you can use fat32, otherwise try formatting it from the phone

Bootloop after installing Busybox

Hello guys, I hope there is a solution for this, I have a rooted device, Android 11 european, I installed busybox through magisk and I'm stuck in a bootloop. I have a working connection to fastboot, what can I do now?
Edit: I have an extracted zip with payload dumper, tried to flash the boot.img only but it doesn't work, can I install the whole zip somehow through fastboot?

Perpatoura said:
Hello guys, I hope there is a solution for this, I have a rooted device, Android 11 european, I installed busybox through magisk and I'm stuck in a bootloop. I have a working connection to fastboot, what can I do now?
Edit: I have an extracted zip with payload dumper, tried to flash the boot.img only but it doesn't work, can I install the whole zip somehow through fastboot?
Click to expand...
Click to collapse
Follow the procedure in this thread:
https://forum.xda-developers.com/on...ecovery-oxygen-os-stock-recovery-adb-t4084487
Then reboot into recovery, then:
> cd /data/adb/modules
> rm -rf XXXXX (where XXXXX is the name of your module)
Then reboot via the recovery screen on your phone (use "exit" -> "reboot" -> "reboot")

foobar66 said:
Follow the procedure in this thread:
https://forum.xda-developers.com/on...ecovery-oxygen-os-stock-recovery-adb-t4084487
Then reboot into recovery, then:
> cd /data/adb/modules
> rm -rf XXXXX (where XXXXX is the name of your module)
Then reboot via the recovery screen on your phone (use "exit" -> "reboot" -> "reboot")
Click to expand...
Click to collapse
Thanks, did this and deleted busybox but it didn't fixed the bootloop.
Edit> Problem got solved, while in boot options I accidentally pressed chinese, then I tried to reboot but probably wiped data and cache, after that the phone started.