[Recovery][Stock OOS 10.0.3BA]Oxygen OS Stock recovery with ADB enabled

[vooze]

Anyone tested this with 1.0.4 HD01BA?

 

[ricky886]

Anyone tested this with 1.0.4 HD01BA?

Not work with 10.0.4
Still finding patchboot:crying:

 

[yo_honey]

Not work with 10.0.4
Still finding patchboot:crying:

Do you want 10.0.4 patchedboot.img for root??

 

[ricky886]

Do you want 10.0.4 patchedboot.img for root??

Yes, I need root..

 

[yo_honey]

Yes, I need root..

https://forum.xda-developers.com/7t...ot-image-oneplus-7t-pro-t3986351/post80894389

Here from nd patched & original boot img 10.0.4

 

[ricky886]

https://forum.xda-developers.com/7t...ot-image-oneplus-7t-pro-t3986351/post80894389

Here from nd patched & original boot img 10.0.4

That I tried, and it doesn't work.
Maybe OTA update and full update package are different:silly:
And I go back to 10.0.3 now

 

[yo_honey]

That I tried, and it doesn't work.
Maybe OTA update and full update package are different:silly:
And I go back to 10.0.3 now

What you have tried? Please explain

 

[ricky886]

What you have tried? Please explain

I used the command to boot the patchedboot, then I go to magisk manager.
And it show there is no magisk detect
So I can't get root to install magisk to my boot

 

[s3axel]

I used the command to boot the patchedboot, then I go to magisk manager.
And it show there is no magisk detect
So I can't get root to install magisk to my boot

Hi
thanks for pointing this out, although I am a bit confused and fear you may have mixed things a bit , so please let me explain a bit:
This thread is for installing a modified recovery that allows you to access the phones file system and e.g. remove a incompatible magisk module. This recovery does not root the phone in any way nor change the bootloader !

If you want to root your phone you need the method explained in this thread from Holychickenguy, there you will also find a patched boot image and can proceed as your text indicated that you tried to do.

HTH, cheers,
Axel

 

[ricky886]

Hi
thanks for pointing this out, although I am a bit confused and fear you may have mixed things a bit , so please let me explain a bit:
This thread is for installing a modified recovery that allows you to access the phones file system and e.g. remove a incompatible magisk module. This recovery does not root the phone in any way nor change the bootloader !

If you want to root your phone you need the method explained in this thread from Holychickenguy, there you will also find a patched boot image and can proceed as your text indicated that you tried to do.

HTH, cheers,
Axel

My issue same as this member
https://forum.xda-developers.com/showpost.php?p=80934691&postcount=178

 

[yo_honey]

I used the command to boot the patchedboot, then I go to magisk manager.
And it show there is no magisk detect
So I can't get root to install magisk to my boot

Youhave to install magisk again from magisk manager for root. Below are the steps from another thread.
(Use proper boot.img as per your current software version)

3. Type: fastboot boot pathtomagisk_patched.img

4. Once booted into the phone open the magisk manager app (if not installed manually install it)

5. Go to Magisk's settings and make sure your Update Channel is set to Stable

6. Click the advanced button and made sure preserve force encryption & preserve avb 2.0/dm-verity are turned ON

7. Install Magisk and select Direct Install!

 

[ricky886]

Youhave to install magisk again from magisk manager for root. Below are the steps from another thread.
(Use proper boot.img as per your current software version)

3. Type: fastboot boot pathtomagisk_patched.img

4. Once booted into the phone open the magisk manager app (if not installed manually install it)

5. Go to Magisk's settings and make sure your Update Channel is set to Stable

6. Click the advanced button and made sure preserve force encryption & preserve avb 2.0/dm-verity are turned ON

7. Install Magisk and select Direct Install!

This is not work with 10.0.4 global full rom.
After use the patchboot boot, the magisk manager still show there have no install magisk.
So you can't install magisk to stock boot.
End

 

[liver20]

Anyone Can upload Kernel backup rooted ?

Backup with ex Kernel manager

Enviado desde mi GM1913 mediante Tapatalk

 

[yo_honey]

This is not work with 10.0.4 global full rom.
After use the patchboot boot, the magisk manager still show there have no install magisk.
So you can't install magisk to stock boot.
End

Please read .

After booting patched boot.img You have to click on install in magisk manager again & also do the settings as mentioned ( if magisk manager is not showing then install magisk manager apk manually & follow the instructions

 

[liver20]

Please read .



After booting patched boot.img You have to click on install in magisk manager again & also do the settings as mentioned ( if magis manager is not showing then install magisk manager apk manually & follow the instructions

Upload backup of your Kernel rooted with ex Kernel manager

Enviado desde mi GM1913 mediante Tapatalk

 

[ricky886]

Please read .

After booting patched boot.img You have to click on install in magisk manager again & also do the settings as mentioned ( if magis manager is not showing then install magisk manager apk manually & follow the instructions

If this method is work, I don't need flash back to 10.0.3
I can use this method on 10.0.3 but this is not working on 10.0.4

---------- Post added at 12:24 AM ---------- Previous post was at 12:20 AM ----------

Upload backup of your Kernel rooted with ex Kernel manager

Enviado desde mi GM1913 mediante Tapatalk

I think need backup on twrp with USB stick to restore

 

[liver20]

If this method is work, I don't need flash back to 10.0.3
I can use this method on 10.0.3 but this is not working on 10.0.4

---------- Post added at 12:24 AM ---------- Previous post was at 12:20 AM ----------





I think need backup on twrp with USB stick to restore

With ex Kernel manager

Enviado desde mi GM1913 mediante Tapatalk

 

[chiiiiiiippppppp]

I was in a bootloop, because of the GCam aux Magisk module. For me it was the same at first attempt. I installed with

fastboot flash recovery OP7TP_StockRecovery_ADB_nosec.img

After that I rebooted to recovery. I also did not get a password prompt. I connected with

adb shell

but /data was empty. Because I wanted to see if my system still works without Magisk, I booted with the unmodified boot.img by using

fastboot boot boot.img

System came up without Magisk and was usable. After that I rebooted and it got stuck at fastboot screen again. I tried one more time to select recovery from fastboot screen and it asked me for password. Since I don't have encryption I just tried to connect again with

adb shell

This time /data was properly mounted and I was able to delete the Magisk module. After that I rebooted to system with

adb reboot

and now I have my fully functional system back. I don't know why it didn't work in the first attempt but this is awesome.
@s3axel you made my day! Thank you very much!!! Your work is appreciated!

I've got a similar problem to this now.

I updated to 10.0.4 and kept root.

I then installed Viper again and then the driver and got in to the expected bootloop going to fastboot screen.

I used adb to try and remove the rouge magisk module from /data/adb/modules but I could not see anything inside the /data folder.

I had to use recovery to do a full wipe which then got me back to a working 10.0.4 system.

I've rooted again and have installed Root Explorer which works great.

I can see the contents of the /data folder from within Root Explorer, but when I boot to Recovery and use adb shell I can't see anything in there. It also does not ask me for pin code when going in to recovery which seems strange.

This basically means I cant get Viper working as I need to be able to remove one of the files from /data/adb/modules/ via adb .

What have I done wrong?

Any help would be most appreciated.

 

[HolyChickenGuy]

I've got a similar problem to this now.



I updated to 10.0.4 and kept root.



I then installed Viper again and then the driver and got in to the expected bootloop going to fastboot screen.



I used adb to try and remove the rouge magisk module from /data/adb/modules but I could not see anything inside the /data folder.



I had to use recovery to do a full wipe which then got me back to a working 10.0.4 system.



I've rooted again and have installed Root Explorer which works great.



I can see the contents of the /data folder from within Root Explorer, but when I boot to Recovery and use adb shell I can't see anything in there. It also does not ask me for pin code when going in to recovery which seems strange.



This basically means I cant get Viper working as I need to be able to remove one of the files from /data/adb/modules/ via adb .



What have I done wrong?



Any help would be most appreciated.

Check my posts, I have a post on how to delete magisk modules

Sent from my HD1913 using Tapatalk

 

[chiiiiiiippppppp]

Check my posts, I have a post on how to delete magisk modules

Sent from my HD1913 using Tapatalk

I've read that post.

The problem is I can't access anything inside /data from adb.

I can't delete them if I can't even see them.