Related
Has anyone been able to get adaway to work on N with su2. 70? It loads, gets root, tries to copy host files.. Then says "host files cannot be copied".. Select target directory. What is the target directory for N?
I'm on su2.69 and it worked just fine
chapelfreak said:
I'm on su2.69 and it worked just fine
Click to expand...
Click to collapse
I flashed this to get on N.. http://forum.xda-developers.com/nexus-6/general/android-n-preview-npc56p-twrp-recovery-t3332599 is this what you used?
Same error here - with latest TWRP, SuperSU 2.70, and elementalX kernel 4.01... :/
There is a flashable zip for usage with systemless root in the adaway Thread, flash that one too and everything is fine.
Edit: this file https://www.androidfilehost.com/?fid=24438995911977059
Gesendet von meinem Nexus 6 mit Tapatalk
It needs Busybox for mine to work.
kwdan said:
I flashed this to get on N.. http://forum.xda-developers.com/nexus-6/general/android-n-preview-npc56p-twrp-recovery-t3332599 is this what you used?
Click to expand...
Click to collapse
I took the ota pushed to me from marshmallow.
Same thing here Adaway doesn't work.
I installed android N with the beta enrollment OTA.
I Used the SuperSU 2.70 AutoRoot, then install Adaway and then busybox; not working :/
bluetigger68 said:
There is a flashable zip for usage with systemless root in the adaway Thread, flash that one too and everything is fine.
Edit: this file https://www.androidfilehost.com/?fid=24438995911977059
Gesendet von meinem Nexus 6 mit Tapatalk
Click to expand...
Click to collapse
Thank you... Working perfectly now. I never knew how many ads were on this phone.
Dreadk said:
Same thing here Adaway doesn't work.
I installed android N with the beta enrollment OTA.
I Used the SuperSU 2.70 AutoRoot, then install Adaway and then busybox; not working :/
Click to expand...
Click to collapse
same steps here.
tried with the zip to prep the OS and still no work
Work around for ad blocking on Android Preview 5 (latest NPD90G)
#Windows PC download the following:
'SuperSU' ("UPDATE-SuperSU-v2.76-20160630161323.zip") https://download.chainfire.eu/969/SuperSU/
MoaAB_ADBlocking_06082016_R1.zip http://forum.xda-developers.com/showthread.php?t=1916098
TWRP 3.0.0-1 from https://dl.twrp.me/angler/
Install Android N 7.0 NPD90G on Nexus 6P
reboot into bootloader (Power Button and Vol Down)
fastboot flash recovery twrp-3.0.0-1-angler.img <------ Download from TWRP (3.0.2 seems to always get stuck on TWRP splash screen)
#Boot to recovery
#if TWRP asks for a password to decrypt you will need to format userdata (THIS WILL FACTORY RESET YOUR PHONE!!!)
#ONLY do the following if you can not get directly into TWRP and are asked for a decrypt password
Reboot into bootloader
fastboot format userdata
fastboot format cache
#boot into TWRP recovery
Manually add the files you downloaded via Windows PC to Nexus 6P while in TWRP (put them in the / or /sdcard/Download directory *or a directory of your choice)
#Windows PC unzip MoaAB_ADBlocking_06082016_R1.zip and go MoaAB_ADBlocking_06082016_R1 > system > etc >
# There should be 2 files here hosts, and hosts.defaults
TWRP > Advanced > Terminal
cat /system/etc/hosts
#note that stock only the following should be displayed.
127.0.0.1 localhost
::1 ip6-localhost
# The following will copy the hosts file you got from MoaAB zip to /system/etc
cp /sdcard/Download/hosts /system/etc/
^ This is the 'hosts' file you downloaded from MoaAB previously
cat /system/etc/hosts
#output should be rather large now...
Reboot phone and test ad blocking on apps 'speedtest' is a good app to test on... No ad after speedtest ad blocking is working....
#profit
bluetigger68 said:
There is a flashable zip for usage with systemless root in the adaway Thread, flash that one too and everything is fine.
Edit: this file https://www.androidfilehost.com/?fid=24438995911977059
Gesendet von meinem Nexus 6 mit Tapatalk
Click to expand...
Click to collapse
Yes it work! perfect!!!
kwdan said:
Has anyone been able to get adaway to work on N with su2. 70? It loads, gets root, tries to copy host files.. Then says "host files cannot be copied".. Select target directory. What is the target directory for N?
Click to expand...
Click to collapse
Flash this in Recovery, Reboot Handy, Start Adaway: https://www.androidfilehost.com/?fid=24438995911977059
To get Adaway working in Android N, All you need to do is...
1. Install the Adaway apk
2. Flash this zip in TWRP, https://www.androidfilehost.com/?fid=24438995911977059
And that's it!!!
Don't **** around with updating SuperSU, or installing busybox, or any other suggestions made here.
CLOSE THREAD!
pr0ndigy said:
To get Adaway working in Android N, All you need to do is...
1. Install the Adaway apk
2. Flash this zip in TWRP, https://www.androidfilehost.com/?fid=24438995911977059
And that's it!!!
Don't **** around with updating SuperSU, or installing busybox, or any other suggestions made here.
CLOSE THREAD!
Click to expand...
Click to collapse
No mirrors found for that file on filehost.. Can you provide an alternative location please?
Edit: Link eventually worked after refreshing the page a few times..
I'm Just bumping this up so I don't have to make a new thread. The latest update seems to have broken this. The hosts file gets replaced automatically on reboot. Anyone else have this problem?
You're just genius! Works perfectly on Nexus 5X (NBD90W) without even formatting userdata (twrp 3.0.2-2)
Found another way. Mount system r/w in terminal or use root explorer after that adaway should work normally till next reboot.
Hi guys
if anyone is interested in testing out this boot image i created for my c636b172
removes all encrypt, perfect mounting options for all partitions (this took a while to figure since some caused bootloops)
also reduced voltages for wifi module (may be unstable, if anyone has problems let me know i can try and adjust, otherwise if im not getting problems ill just keep decreasing it)
how to install
1. make sure twp is installed
2. in data/dalvik-cache delete arm and arm64 folders.
3. boot into twrp > wipe cache and dalvik
4. flash the boot image in twrp (flash image select image flash to boot)
5. if you had su installed, flash the zip again
6. go to wipe cache and dalvik again (just in case)
7. reboot and enjoy, theoretically should be slightly faster, and less overhead.
Download
https://www.dropbox.com/s/msda9a3smy9lqb4/modBootv2.img?dl=0
if anyone has a request for their specific boot image let me know and ill add the same values.
Thank you for your work. Is this only for C636 devices or would this work on any device.
Could your reassemble it to add features like DT2W (doubletap to wake)?
audioralf said:
Thank you for your work. Is this only for C636 devices or would this work on any device.
Could your reassemble it to add features like DT2W (doubletap to wake)?
Click to expand...
Click to collapse
i think DT2W is disabled, no flags of it in the boot image, you can try this guide.
https://forum.xda-developers.com/mate-9/how-to/enable-double-tap-to-wake-mate-9-t3580764
the boot image is for the c636, im not sure if you can flash it on another base you can try just have a stock boot.img handy
or to be safe you can send me your boot.img and ill edit it the same.
Thank you for your friendly offer!
I am back on C432B156 with supersu modified boot. The original boot img linked here
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
Mine is https://mega.nz/#!EABCVJwb!wopFOGqJzbpIX6edxM5Y9IVeZAIJ_CAJYUn3q4cc074
I recognized that I have no adb access in TWRP 3.02.2
I can not mount my pc connection. Would this be fixed?
Gesendet von meinem MHA-L29 mit Tapatalk
audioralf said:
Thank you for your friendly offer!
I am back on C432B156 with supersu modified boot. The original boot img linked here
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
Mine is https://mega.nz/#!EABCVJwb!wopFOGqJzbpIX6edxM5Y9IVeZAIJ_CAJYUn3q4cc074
I recognized that I have no adb access in TWRP 3.02.2
I can not mount my pc connection. Would this be fixed?
Gesendet von meinem MHA-L29 mit Tapatalk
Click to expand...
Click to collapse
no, twrp 3022 doesnt have MTP access right now.
Thank you for the info.
Which advantage is on daily usage. I guess I would have to install supersu again, for it modifies the boot.
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Mount does work in 3.1.0. Though you have to tap on "Mount USB Storage", then unmount before it actually mounts..
ante0 said:
Mount does work in 3.1.0. Though you have to tap on "Mount USB Storage", then unmount before it actually mounts..
Click to expand...
Click to collapse
ill try this
always thought it didnt work since it worked fine in 303
Hi Virtyx,
I very appreciate your work, good hope to use,
but i have some not understand the installation in STEP 2 (in data/dalvik-cache delete arm and arm64 folders) what to do?
Hope you can help explain more STEP 2 detail.
I have L29-C636b172 and unlocked Bootloader.
A lot of Thanks.
xjeepnsk said:
Hi Virtyx,
I very appreciate your work, good hope to use,
but i have some not understand the installation in STEP 2 (in data/dalvik-cache delete arm and arm64 folders) what to do?
Hope you can help explain more STEP 2 detail.
I have L29-C636b172 and unlocked Bootloader.
A lot of Thanks.
Click to expand...
Click to collapse
Using a file Explorer with root support, navigate to /data/dalvik-cache and remove those 2 folders. Alternatively use a terminal app and 'rm -rf /data/dalvik-cache/arm*'.
I guess you could use the file manager or terminal in twrp.
ante0 said:
Using a file Explorer with root support, navigate to /data/dalvik-cache and remove those 2 folders. Alternatively use a terminal app and 'rm -rf /data/dalvik-cache/arm*'.
I guess you could use the file manager or terminal in twrp.
Click to expand...
Click to collapse
Hi ante0,
I succeeded, Thank you so much
Hello sir,
My mate 9 stuck in boot loop....
And I can't access to recovery too
Can u make scatter file for mate 9 to fix boot loop
I know how to root with magisk and enable camera2api module. (by flashing patched_boot.img) but then , phone wont update, it shows up error. Is there a way to have google camera working and OTA enabled? many thanks
djavo22 said:
I know how to root with magisk and enable camera2api module. (by flashing patched_boot.img) but then , phone wont update, it shows up error. Is there a way to have google camera working and OTA enabled? many thanks
Click to expand...
Click to collapse
No you temporarily have to flash stock boot, do the update, flash patched boot image and enable camera2api again
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
minnuss said:
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
Click to expand...
Click to collapse
Did you relock bootloder or get the ota with unlock bootloader?
minnuss said:
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
Click to expand...
Click to collapse
can you please post further instructions step by step?
ki69 said:
Did you relock bootloder or get the ota with unlock bootloader?
Click to expand...
Click to collapse
Not needed.
minnuss said:
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
Click to expand...
Click to collapse
Bro can u shw us step by step process !!
Sid.Boi said:
Bro can u shw us step by step process !!
Click to expand...
Click to collapse
X2
Sid.Boi said:
Bro can u shw us step by step process !!
Click to expand...
Click to collapse
Follow what he said, it's not hard and all the information can be found easily.
Can any of you that have enabled Cam2API tell us, does it make a difference in the OEM Cam app? I know it allows a GCam port to work, which is awesome, but any difference in OEM app?
thnx
You can all do it if you are still in software version 9.6.10.0 (Android One August update), or if you knew how to root your phone on the version that you have right now.
Go to this tool, https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Then follow this steps.
https://forum.xda-developers.com/showpost.php?p=77611720&postcount=51
I edited this quote for all of you for better understanding.
"Then I tried to use number 7. enable camera2 api, and the problem is that it did not install root correctly, when phone reboots, the user must download full magisk, then the proper root will function.
After enabling camera2 api, which i did manually with adb shell, it will pop up on screen to allow access with root privileges.
adb shell
su
When you enter su, it will pop up on phone screen to allow access with root privileges, allow it for one time, if it is not pop upping on the phone for root, then the root on the phone is not properly installed.
And then type
setprop persist.camera.HAL3.enabled 1
After that, complete uninstall of magisk from option within magisk itself, and when magisk reboot the phone in the process of uninstalling, quickly hold power and down volume button, go to fastboot and flash on both partitions stock boot.img.
Put the stock boot.img of the version of the phone you currently have to adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Check is the camera2 api enabled after the restart.
That was the correct steps for me."
For me I used MagiskHide props config module to enable camera2
you don't need to fully uninstall magisk to receive otas, just restore images from magisk, receive the update and then install magisk to the inactive slot and use the reboot option in magisk (don't reboot normally)
Does anybody know if the Video is also improved when using Gcam apk?
I can't find any online samples.
Nebrassy said:
For me I used MagiskHide props config module to enable camera2
you don't need to fully uninstall magisk to receive otas, just restore images from magisk, receive the update and then install magisk to the inactive slot and use the reboot option in magisk (don't reboot normally)
Click to expand...
Click to collapse
Can You Please Tell Me The Proper Proceedure. .
I Don't want my phone bricked.
I'm in august patch and having magisk installed with some system changes.
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
Nebrassy said:
For me I used MagiskHide props config module to enable camera2
you don't need to fully uninstall magisk to receive otas, just restore images from magisk, receive the update and then install magisk to the inactive slot and use the reboot option in magisk (don't reboot normally)
Click to expand...
Click to collapse
Can U Please Tell The Steps Broadly?
rafihasan710 said:
Can You Please Tell Me The Proper Proceedure. .
I Don't want my phone bricked.
I'm in august patch and having magisk installed with some system changes.
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
Can U Please Tell The Steps Broadly?
Click to expand...
Click to collapse
If you only used magisk modules and didn't touch /system, just follow the instructions here
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you made any modifications to /system or just mounted it writable, you need to re flash the system image
Get the august fastboot image, unpack and flash system.img to your current slot, then follow the guide i linked
And don't worry you won't brick it, the update will just fail if you did anything wrong
Nebrassy said:
If you only used magisk modules and didn't touch /system, just follow the instructions here
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you made any modifications to /system or just mounted it writable, you need to re flash the system image
Get the august fastboot image, unpack and flash system.img to your current slot, then follow the guide i linked
And don't worry you won't brick it, the update will just fail if you did anything wrong
Click to expand...
Click to collapse
Thank You For The Instruction..
I've modified the system like camera2api and some magisk module....
If i flash the system.img what will change?
And how to do that?
How to flash system.img in current slot?
rafihasan710 said:
Thank You For The Instruction..
I've modified the system like camera2api and some magisk module....
If i flash the system.img what will change?
And how to do that?
How to flash system.img in current slot?
Click to expand...
Click to collapse
That restores the system to stock without modifications
Alternatively, you can just download the latest fastboot image and just flash the whole thing so you won't need to update after that
If you want to just flash system.img and then let your phone update, download the image I linked, extract it, open the images folder, it has system.img
open cmd/terminal, type fastboot getvar current-slot
if the current slot is a, then fastboot flash system_a <path to system.img>
like fastboot flash system_a D:\images\system.img
if the slot is b then use system_b
If you decide to just download the latest image instead, use miflash, instructions are on miui website, just be careful not to wipe data or lock the bootloader (it does that by default)
Nebrassy said:
That restores the system to stock without modifications
Alternatively, you can just download the latest fastboot image and just flash the whole thing so you won't need to update after that
If you want to just flash system.img and then let your phone update, download the image I linked, extract it, open the images folder, it has system.img
open cmd/terminal, type fastboot getvar current-slot
if the current slot is a, then fastboot flash system_a <path to system.img>
like fastboot flash system_a D:\images\system.img
if the slot is b then use system_b
If you decide to just download the latest image instead, use miflash, instructions are on miui website, just be careful not to wipe data or lock the bootloader (it does that by default)
Click to expand...
Click to collapse
Thanks.....
Can You Give The Download Link Of August System.img file.
Jeez what a nightmare... I'm not able to flash the system image at all, fastboot keeps giving random errors on both linux and windows.
rafihasan710 said:
Thanks.....
Can You Give The Download Link Of August System.img file.
Click to expand...
Click to collapse
extract from this
http://bigota.d.miui.com/V9.6.10.0....0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz
can anyone provide steps to root and unable camera 2 api after latest update.
i am on September update version with stock rom.
look forward for best support.
Same as on any stock version of ROM.
First of all unlock your bootloader if you have not unlocked it already.
Download and extract stock ROM from en.miui.com for A2 (September build), after unpacking, enter folder "Images" and copy boot.img to your phone's internal storage.
Download and Install Magisk Manager application
In Magisk click install and select patch boot image. Navigate to your internal memory and select boot.img you have copied to your phone.
Magisk will create new patched_boot.img file on your phone, usually in the same place as your original image.
Copy patched_boot.img to your PC.
Use adb platform tools, enter fastboot and flash patched_boot.img to your phone:
fastboot flash boot patched_boot.img
fastboot reboot
After booting, use build.prop editor or any file explorer to navigate to system\build.prop
add line to build.prop : persist.camera.HAL3.enable=1
Save and reboot. Install Google Camera port app and enjoy
Mr.Nice.ba said:
Same as on any stock version of ROM.
First of all unlock your bootloader if you have not unlocked it already.
Download and extract stock ROM from en.miui.com for A2 (September build), after unpacking, enter folder "Images" and copy boot.img to your phone's internal storage.
Download and Install Magisk Manager application
In Magisk click install and select patch boot image. Navigate to your internal memory and select boot.img you have copied to your phone.
Magisk will create new patched_boot.img file on your phone, usually in the same place as your original image.
Copy patched_boot.img to your PC.
Use adb platform tools, enter fastboot and flash patched_boot.img to your phone:
fastboot flash boot patched_boot.img
fastboot reboot
After booting, use build.prop editor or any file explorer to navigate to system\build.prop
add line to build.prop : persist.camera.HAL3.enable=1
Save and reboot. Install Google Camera port app and enjoy
Click to expand...
Click to collapse
thanks for the elaborated process.
but after flashing of the patched image, would i
able to get future updates.
IjazCI said:
Hi i would advise to boot with a magisk patched boot image and enable camera2api via adb commands. Set prop method, without editing system partition. This way you can install ota updates flawlessly,if you didn't intend to root.
Edit :. You can find magisk patched September boot image and instructions here in the forum.
Click to expand...
Click to collapse
thanks,
my sole intend is to run gcam nothing else. thanks for your reply. wouldn't mind if you share exact instructions to follow
Abbey Bhatt said:
thanks for the elaborated process.
but after flashing of the patched image, would i
able to get future updates.
Click to expand...
Click to collapse
I think not. Thats why i has trying to enable camera2api witha workin TWRP for setember update. If i flash a patch boot i will lose OTA, and if i reflash with original boot i will loose Camera2api, thats why i has searching for an fix for this:
https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475
with september update that woks.
ki69 said:
I think not. Thats why i has trying to enable camera2api witha workin TWRP for setember update. If i flash a patch boot i will lose OTA, and if i reflash with original boot i will loose Camera2api, thats why i has searching for an fix for this:
https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475
with september update that woks.
Click to expand...
Click to collapse
Just flash stock boot again and ota works fine. Afterwards update, flash new patched boot, profit
IjazCI said:
d)setprop persist.camera.eis.enable 1 - enables EIS
Click to expand...
Click to collapse
Do not enable EIS like this, camera will have a problem with recording videos, and it will not work like it should.
minnuss said:
Do not enable EIS like this, camera will have a problem with recording videos, and it will not work like it should.
Click to expand...
Click to collapse
Really? First I've heard that. Do you have any more specific info on this? examples of it not working and how it should?
If that won't work, is there another way to enable it that will?
thnx
IjazCI said:
Could you explain a little bit more . Which camera stock Mi camera or GCam? I'm using Scrubber Gcam and i can record videos without any problem. And i recorded a really good 4k video with stock Mi camera.
Click to expand...
Click to collapse
For me it did not work, the stock camera would start recording after 5 times of pressing record circle, and gcam ports would crash after switching to video recording.
So I did a reverse command setprop persist.camera.eis.enable 0, and everything get back to normal. :good:
minnuss said:
For me it did not work, the stock camera would start recording after 5 times of pressing record circle, and gcam ports would crash after switching to video recording.
So I did a reverse command setprop persist.camera.eis.enable 0, and everything get back to normal. :good:
Click to expand...
Click to collapse
IjazCI said:
Strange. I have enabled it in my A1 and A2 with out any issues.
Click to expand...
Click to collapse
I also can verify that enabling it like that works. With my A2 and a GCam port, Snap Cam, and OEM app all work exactly as they should. That includes the OEM app video recording in 4K WITHOUT EIS, even though it's checked, and the Snap Cam working in 4k Vid with EIS working - as it should.
I don't think your problem was the Eis enable command.
Someone plss create a thread for rooting mi a2 on September update..... Or plss share the link to download September patch image file to root..
AsItLies said:
I also can verify that enabling it like that works. With my A2 and a GCam port, Snap Cam, and OEM app all work exactly as they should. That includes the OEM app video recording in 4K WITHOUT EIS, even though it's checked, and the Snap Cam working in 4k Vid with EIS working - as it should.
I don't think your problem was the Eis enable command.
Click to expand...
Click to collapse
OpenCamera works with 4k resolution when persist.camera.eis.enable 1 active?
marlontravagli said:
OpenCamera works with 4k resolution when persist.camera.eis.enable 1 active?
Click to expand...
Click to collapse
Sorry, I don't have opencamera so don't know. Snapcamera certainly does though, it does an awesome job.
use this app to enable HAL3
https://play.google.com/store/apps/details?id=com.proxdz.hal3enabler
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled.
Prerequisites:
Oneplus 8 Pro
unlocked bootloader
access to fastboot on the phone
adb and fastboot
Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery <filename>
(with <filename> being the name of the recovery in the format of "recovery.img" you wish to flash)
Uninstall:
Same as installation, but flash the original stock recovery instead.
Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.
Step-by-step this would be:
Code:
cd /data/adb/modules
to change to the Magisk modules directory
Code:
ls
to list the content of this directory, each module has its own directory, usually with a well-recognizable name
Code:
rm -r <directory>
to delete the directory in question. Tip: in console TAB-autocomplete works
Downloads:
10.5.4 BA Recovery
Modified 10.5.4 BA recovery from GDrive
Original 10.5.4 BA recovery from Gdrive
10.5.5 BA Recovery
Modified 10.5.5 BA recovery from GDrive
Original 10.5.5 BA recovery from Gdrive
10.5.6 BA Recovery
Modified 10.5.6 BA recovery from GDrive
Original 10.5.6 BA recovery from Gdrive
Notes of caution:
ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing
Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.
Description of method to modify recovery by yourself:
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash
Thanks for this...
On fastboot we have to flash the modified recovery img?
EDIT : Nevermind haven't read the whole OP
I have a noob question: this won't affect data or magisk right?
To remove a module , command should not be :
( rm -rf < directory> ) ?...
cultofluna said:
To remove a module , command should not be :
( rm -rf < directory> ) ?...
Click to expand...
Click to collapse
Thanks for your comment, but technically no
The - f flag is used to omit prompts before each removal, which may or may not be helpful - depending in how sure the user is on what he does
I chose the safer variety in my example, confident that users with more knowledge can always look at the "rm" man page to decide what command they want to use...
But again thanks, I do appreciate your help!
HottieLinus said:
I have a noob question: this won't affect data or magisk right?
Click to expand...
Click to collapse
Correct, the recovery resides in a separate partition and flashing it doesn't do anything anywhere else.
In fact the recovery looks and behaves the same when booting into it, the change only becomes apparent by being able to use adb in recovery.
@s3axel can we use this recovery to escape bootloop due to install unsupported theme or any issue from substratum?
Or maybe just flashing stock boot IMG on fastboot is enough...
cultofluna said:
@s3axel can we use this recovery to escape bootloop due to install unsupported theme or any issue from substratum?
Or maybe just flashing stock boot IMG on fastboot is enough...
Click to expand...
Click to collapse
It should be possible as the recovery gives you full access to your file system and so, given you know what to remove/change, it should also be possible to recover from issues as you mentioned.
My problem: I have no idea where themes or substratum additions are installed directory-location wise, will need to research a bit. Or maybe someone else can chime in on this, then I could update OP with info on that as well...
Ok one more question..
Can we flash zips through the recovery?...
Via ADB sideload?.. maybe..
cultofluna said:
..Can we flash zips through the recovery?...Via ADB sideload?..
Click to expand...
Click to collapse
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
s3axel said:
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
Click to expand...
Click to collapse
Ok...
Because on pixel4 XL you can reboot to stock recovery and choose the the option ADB sideload...
And from there you can flash a custom ROM...etc..
Updated OP with 10.5.5 recovery..
s3axel said:
Updated OP with 10.5.5 recovery..
Click to expand...
Click to collapse
That recovery looks like it's for BA. Does that recovery work on AA as well?
---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------
s3axel said:
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
Click to expand...
Click to collapse
Is the OnePlus 8 pro system partition dynamic? Meaning it'll be an absolute nightmare to ever get TWRP like the OP 7T series? I really hope not, flashing through ADB for everything sucks.
Burt Squirtz said:
That recovery looks like it's for BA. Does that recovery work on AA as well?
---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------
Is the OnePlus 8 pro system partition dynamic? Meaning it'll be an absolute nightmare to ever get TWRP like the OP 7T series? I really hope not, flashing through ADB for everything sucks.
Click to expand...
Click to collapse
Yep..
Definitely dynamic partitions...
Don't expecting a fully working twrp...
You can find a chinese twrp that boots and decrypt..
But sources are unknown...
cultofluna said:
Yep..
Definitely dynamic partitions...
Don't expecting a fully working twrp...
You can find a chinese twrp that boots and decrypt..
But sources are unknown...
Click to expand...
Click to collapse
do you have a link to that Chinese TWRP by chance? And how would I initially flash it, adb? Or Could I probably go through magisk manager?
Burt Squirtz said:
do you have a link to that Chinese TWRP by chance? And how would I initially flash it, adb? Or Could I probably go through magisk manager?
Click to expand...
Click to collapse
That Chinese TWRP violates glp so it cannot be shared here on xda..And if were you I woulnd be using that anyway..Just my two cents
pyry666 said:
That Chinese TWRP violates glp so it cannot be shared here on xda..And if were you I woulnd be using that anyway..Just my two cents
Click to expand...
Click to collapse
What an incredibly helpful response. Sorry but if there's something that'll decrypt and allow me to backup and recover, of course I'm going to try and find it. And I suspect most other people here would too.
Burt Squirtz said:
That recovery looks like it's for BA. Does that recovery work on AA as well?
Click to expand...
Click to collapse
I don't know presently, usually I compare recoveries or I (or other users) add recoveries for other regions which they made by themselves. When recoveries are the same of course they can be used
RIght now I cannot download the 10.5.5 AA firmware (download aborts after some time), I'll add the recovery once this is working... EDIT: seems OP pulled the downloads, so no luck at the moment...
If there is a working twrp in China then perhaps it's worth making contact with them to see if either:
A) they can let you have it
B) they can help you fix this one?
It's presume the former would make the most sense, with permission I see no problem in obtaining it or linking it, certainly not taking about it. Makes no sense to just avoid an obvious assist whilst we all struggle without twrp.