Database Develop

Help in sideloading custom ROM from ADB

Hey everyone. I just got my new OnePlus 3T a week back. I was loving it till today but I wanted to mess with my phone and I guess I did just that. Long story short, I was on 7.1.1 and unlocked OEM and installed TWRP. Phone booted up and i went into recovery and installed Super SU and the dm verity. After this step, my phone is stuck on the boot animation. I'm able to access TWRP as well as Fastoot ADB. I want to sideload the stock OxygenOS ROM into my phone through ADB, but i'm unsure which file to flash and the exact process. Could someone please help me out? :crying:

That's why you always make a nandroid back up

I figured out why the adb sideload wasn't working. I tried to do the sideload directly from the ADB cmd while my phone was in fastboot mode. So, I tried an alternate method by going into TWRP and doing the sideloading from the advanced menu. It worked and I'm setting up my OP 3T now Guess I jumped the gun by posting here without thinking.
On a side note, my device doesn't have root access now. Maybe it never got installed properly before getting bricked. I think it had to with the fact that I had updated to 7.1.1 by using a VPN. I'm pretty good at following instructions so i couldn't have gone wrong. Can anyone tell me if i can go ahead and root my device now that I'm back on stock OS?

You dont flash supersu and dm verity files at the same time
No wonder you end up in bootloop
Multiple threads are already there about the same issue.
For root just flash supersu

kunal1540 said:
You dont flash supersu and dm verity files at the same time
No wonder you end up in bootloop
Multiple threads are already there about the same issue.
For root just flash supersu
Click to expand...
Click to collapse
Damn, I didn't know that. I only searched for the bootloop issue and didn't really find something that seemed simple enough for me. Almost all the guides I read had similar instructions so I flashed the Dm-verity first and then the Super SU immediately after that. What does dm verity do if it doesnt need to be flashed? And just so that I'm clear - flashing Super SU is enough and no need to bother with the dm verity?

Rahulsingh9367 said:
Damn, I didn't know that. I only searched for the bootloop issue and didn't really find something that seemed simple enough for me. Almost all the guides I read had similar instructions so I flashed the Dm-verity first and then the Super SU immediately after that. What does dm verity do if it doesnt need to be flashed? And just so that I'm clear - flashing Super SU is enough and no need to bother with the dm verity?
Click to expand...
Click to collapse
There's a much much simpler solution, you just use magisk. There's no need to flash supersu or dm-verity fix, just flash the latest magisk zip file in TWRP -> reboot -> install Magisk manager from playstore and you have perfectly working rooted phone.

fluster84 said:
There's a much much simpler solution, you just use magisk. There's no need to flash supersu or dm-verity fix, just flash the latest magisk zip file in TWRP -> reboot -> install Magisk manager from playstore and you have perfectly working rooted phone.
Click to expand...
Click to collapse
Tried flashing the Magisk v9 zip and checked the option that goes something like "verify after flashing" and it failed. Should I uncheck both those options before flashing or flash the phh super user zip too?

Azar_98 said:
Try the latest version of magisk, v11.6.
http://tiny.cc/latestmagisk
Click to expand...
Click to collapse
Worked perfectly and no hassle at all. Thank you so much!

Rahulsingh9367 said:
Tried flashing the Magisk v9 zip and checked the option that goes something like "verify after flashing" and it failed. Should I uncheck both those options before flashing or flash the phh super user zip too?
Click to expand...
Click to collapse
Always flash the latest magisk, and you don't need to flash phh or anything else. Magisk now comes with magisksu that works great with OOS 4.1.1.
Check the link below for latest magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless
If you don't mind losing your data, you can try this 100% clean but slightly painful install. It might be overkill for most but you can start from a clean slate. Backup your stuff to the PC before you do this.
1. Flash compatible stock recovery (stock recovery for android N) in fastboot
2. Now choose to wipe everything (even music, photos) from stock recovery. You will lose everything on your phone.
3. Sideload OOS 4.1.1 rom
4. Reboot and complete phone setup
You are now completely stock except with a unlocked bootloader. In order to gain root, continue further -
5. Enable developer options in Settings and then enable Advanced Reboot and USB debugging
6. Reboot to fastboot and flash twrp 3.0.4.-1
7. Reboot to twrp and flash Magisk v11. 1 zip
8. Reboot and install Magisk Manager from playstore.
Congratulations, you have a stock 4.1.1 with working root and it will even pass safety net check (enable magisk hide in magisk manager)

[Kernel] Stock Kernel + SafetyNet Patch + DRM Fix /FW Nougat 2.33

Stock Kernel + SafetyNet Patch + DRM Fix​
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- Now You can use Android Pay with an unlocked bootloader.
Installation:
- Installation using TWRP
- Installation via the bootloader
Code:
fastboot flash boot boot.img
Downloads: Dropbox (E6633,E6653,E6683)
Current version: 32.3.A.2.33 -perf-g1016077
I compiled the stock kernel and applied the SafetyNet patch by sultanxda.
DISCLAIMER:
No one is responsible for any damage caused to your device except You. You have been warned.
TWRP 3.1.1 for Xperia Z5, Z5C, Z3+
Vulkan API for Adreno 430

please port for E6853

anjelz2012 said:
please port for E6853
Click to expand...
Click to collapse
Try the Zach's Kernel, in it the SafetyNet check is partially disabled.

Great work!

delete

Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.

rrdna said:
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
Try to install TWRP 3.1.1.

grayleshy said:
Try to install TWRP 3.1.1.
Click to expand...
Click to collapse
Thanks, 3.1.1 worked for me

rrdna said:
Thanks, 3.1.1 worked for me
Click to expand...
Click to collapse
It's great that TWRP came up and Magisk hides root.

Thanks for the work!!! Any chance for E6633?

christis said:
Thanks for the work!!! Any chance for E6633?
Click to expand...
Click to collapse
If the kernel don't work for You, give me Kernel.sin, then I will do it for E6633.

Thanks for the work. @grayleshy
SIN Files : https://drive.google.com/drive/folders/0B9v3aNFonkyMWlFMbF9yME5EaTg
Did you use sultanxda safetynet patch?

Added kernel for E6633.
sceryavuz said:
Did you use sultanxda safetynet patch?
Click to expand...
Click to collapse
I will soon lay out the source code. There and see, what patch is applied.

Thanks a lot. Can't wait to see the source code! Do you have an eta?

rrdna said:
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
I've the same issue...

MichaMichaMicha said:
Can't wait to see the source code!
Click to expand...
Click to collapse
Patch in kernel from @Sultanxda . Patch of may 23.
Earlier I didn't publish information on a patch as checked this patch.

Looks like you're working on an all in-built kernel ?
If you're making an progress towards in-built MHL please, please let us know
The magic seems to be in the configuration or additional patches (I had it working in the SunKernel Corona source)
but it doesn't seem to work out of the box with Sony's source [or I missed something],
anyway:
Keep up the good fight !

rrdna said:
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
When you install magisk is the drmfix still active? The last time I installed magisk I was facing issues where I'd get white noise when taking pictures and no post processing being done

Thank you!
Now I can use OTA updates for my Z5!!

The_Miggs said:
Thank you!
Now I can use OTA updates for my Z5!!
Click to expand...
Click to collapse
This is not about OTA. SafetyNet : https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/

[Q] (Dumb) Can Magisk work with zips for TWRP/Flashfire?

Sorry, I'm new to using Magisk, and I want to ask if I can install a zip designed for TWRP/FlashFire through Magisk and expect it to work?
Sorry for the likely blatant stupidity. Thanks.

The Magisk Manager can only flash Magisk modules. Trying to flash anything else will simply fail with the message "this is not a Magisk module".

Didgeridoohan said:
The Magisk Manager can only flash Magisk modules. Trying to flash anything else will simply fail with the message "this is not a Magisk module".
Click to expand...
Click to collapse
Is it possible to flash a zip file in twrp that alters system files such as the pixelexperience. zip which changes bootanimation, ui sounds , etc?

matrix0027 said:
Is it possible to flash a zip file in twrp that alters system files such as the pixelexperience. zip which changes bootanimation, ui sounds , etc?
Click to expand...
Click to collapse
You kind of answered your own question there, didn't you? The answer is: yes.

Didgeridoohan said:
You kind of answered your own question there, didn't you? The answer is: yes.
Click to expand...
Click to collapse
I should have been more specific. What I meant was after flashing Magisk in Twrp can we still flash other zip files in twrp that are not Magisk modules or will Magisk no longer work after that? Sorry for being somewhat clueless on this subject. I understand that Magisk is systemless but not sure if flashing a zip from recovery would mess up Magisk or cause a boot issue.

matrix0027 said:
I should have been more specific. What I meant was after flashing Magisk in Twrp can we still flash other zip files in twrp that are not Magisk modules or will Magisk no longer work after that? Sorry for being somewhat clueless on this subject. I understand that Magisk is systemless but not sure if flashing a zip from recovery would mess up Magisk or cause a boot issue.
Click to expand...
Click to collapse
sure nothing will happen flashing any thing in twrp will be safe but the zip u will flash will touch ur system partition ...... i think so that

It all depends on what that zip does... Generally there shouldn't be any issues though.

matrix0027 said:
I should have been more specific. What I meant was after flashing Magisk in Twrp can we still flash other zip files in twrp that are not Magisk modules or will Magisk no longer work after that? Sorry for being somewhat clueless on this subject. I understand that Magisk is systemless but not sure if flashing a zip from recovery would mess up Magisk or cause a boot issue.
Click to expand...
Click to collapse
I get what you're trying to ask, you mean that flashing any mods via TWRP will break Magisk or not.
The answer is :No, they work perfectly
But flashing any mods via TWRP will modify your system partition and MAY stop Magisk Hide from working and will affect your ability to receive OTAs

Relock bootloader (with magisk) on the Oneplus 5?

Hello everyone, I've tried to search on the web about this issue since the OTA for Android O is finally out for the Oneplus 5 and couldn't get a satisfying solution. I rooted my OP5 a while ago with Magisk and now that this update is out and tried to install it, It just wouldn´t let me, searching I found that my locked swich to relock the bootloader was because I had to enable it on Magisk, so I opened magisk and couldn´t find that option, and now that I searched on how to enable the "Lock bootloader option" in the Magisk app and found nothing, I'm just out of ideas, so guys, could you help a (noob) brother out with this?
Ps.: If you could attach some screenshots about where to click or what to do, I'll apreciate it a lot (yeah, I'm that stupid when I freak out and don't find how to undo mi mess)

No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the full OTA zip, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.

Didgeridoohan said:
No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the update, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.
Click to expand...
Click to collapse
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?

Fosko Stock said:
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?
Click to expand...
Click to collapse
Yes.

My Device was Stucked in Bootloop [magisk]

Hello
My Device is running on Stock Android Q BN 11.0.5.0
Recently i installed magisk in my device (keeping OTA).
When i install Magisk Module for Internal audio recording and reboot device it was stucked in bootloop.
Then i flashed stock boot img
After flashing i reboot the device and it is rebooted successfully. But Magisk and Root Access has gone.
Then after i again flash Magisk patched img created by Magisk installer but this time it is again stucked in bootloop.
I tried to flash zip with temporary Twrp but problem is not solved.
Currently i dont have Magisk installed.
Please Help Me to gain root access again
Thank you.
Please reply or DM me https://t.me/adarsh_ad007

1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish

thank you bro it diid not work. i tried but not working
Aerobatic said:
1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish
Click to expand...
Click to collapse
not working

adarsh.ad007 said:
not working
Click to expand...
Click to collapse
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.

Aerobatic said:
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.
Click to expand...
Click to collapse
I did everything what you said but problem is still there.

adarsh.ad007 said:
I did everything what you said but problem is still there.
Click to expand...
Click to collapse
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?

Aerobatic said:
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?
Click to expand...
Click to collapse
Thanks for you support and attention dear.
Actually i flashed PE ROM and then install magisk. Now it works.
And i was booting correct patched img.
I created it via magisk manager myself.

adarsh.ad007 said:
..And i was booting correct patched img. I created it via magisk manager myself.
Click to expand...
Click to collapse
Maybe there was still something that skipped your attention. Pls look at scenario:
- patch stock boot image using MagiskManager with, let us say, Magisk 20.1; boot this patched image, make direct install - root got;
- update Magisk to. e.g., 20.3 installing Magisk-v20.3(20300).zip (root got, everything ok);
- play with new Magisk modules, install wrong version, get bootloop;
- make some otherwise correct steps, like reflashing stock boot;
- finally try to get root with boot image previously patched by Magisk 20.1.
Result: no root, MagiskManager does not accept Magisk 20.1., it expects boot image patched with 20.3