Database Develop

[ODIN] J700T Nougat 7.1.1

https://www.androidfilehost.com/?fid=889964283620761169
Grabbed straight from SamMobile. Flash using Odin.

Not for j700t1 though, correct?

AngryManMLS said:
Grabbed straight from SamMobile. Flash using Odin.
Click to expand...
Click to collapse
But how do you root after flashing this Nougat in J700T?

deloj said:
But how do you root after flashing this Nougat in J700T?
Click to expand...
Click to collapse
There's all sorts of knowledge in the thread
https://forum.xda-developers.com/galaxy-j7/j700t-development

Anything you see for the J700T is compatible with the J700T1. The phones are exactly the same minus 4 apps inside the system.
ctindell1981 said:
Not for j700t1 though, correct?
Click to expand...
Click to collapse

Is this Nougat stock rom for the samsung J700T? And how do I root it?

I have a J700T with twrp and root. Is there a nougat ROM that I can download and flash via twrp?
I would rather not go back to stock, flash nougat, and then re-root.

nimbus22 said:
I have a J700T with twrp and root. Is there a nougat ROM that I can download and flash via twrp?
I would rather not go back to stock, flash nougat, and then re-root.
Click to expand...
Click to collapse
There is no such rom for this model in nougat yet

nimbus22 said:
I have a J700T with twrp and root. Is there a nougat ROM that I can download and flash via twrp?
I would rather not go back to stock, flash nougat, and then re-root.
Click to expand...
Click to collapse
I'm writing this up in case anyone else needs help.
1) Couldn't get the 7.1.1 download to work from sammobile. Ended up downloading the firmware from another source and flashing through Odin. Took a couple of minutes to reboot after the flash.
2) Wanted to get TWRP and Root back on the phone and followed these instructions.
https://forum.xda-developers.com/galaxy-j7/j700t-development/recovery-galaxy-j7-sm-j700t-t1-t3560342
Now have twrp and root. Everything seems to be working fine.

nimbus22 said:
I'm writing this up in case anyone else needs help.
1) Couldn't get the 7.1.1 download to work from sammobile. Ended up downloading the firmware from another source and flashing through Odin. Took a couple of minutes to reboot after the flash.
2) Wanted to get TWRP and Root back on the phone and followed these instructions.
https://forum.xda-developers.com/galaxy-j7/j700t-development/recovery-galaxy-j7-sm-j700t-t1-t3560342
Now have twrp and root. Everything seems to be working fine.
Click to expand...
Click to collapse
followed the steps on the thread. can't make it work. always getting stuck at tmobile logo
here are the steps i used.
1. flash firmware through odin
2. flash twrp through odin
3. flash supersu through twrp
4. flash dm-verify.zip through twrp
5. stuck on tmobile logo.
any ideas?

Once it's been on the screen saying t mobile for at least 10 mins, pull battery, boot to stock recovery, mount system, factory reset, reboot. There. Now u will hear t mobile jingle and it will reach set up wiz

nikkosaurus said:
followed the steps on the thread. can't make it work. always getting stuck at tmobile logo
here are the steps i used.
1. flash firmware through odin
2. flash twrp through odin
3. flash supersu through twrp
4. flash dm-verify.zip through twrp
5. stuck on tmobile logo.
any ideas?
Click to expand...
Click to collapse
I flashed supersu after the dm verity had no problems

benny3 said:
I flashed supersu after the dm verity had no problems
Click to expand...
Click to collapse
Which TWRP version is people using?

https://forum.xda-developers.com/ga...ecovery-galaxy-j7-sm-j700t-t1-t3560342/page30
Same as mm

Does anyone know if Xposed works on it yet? Wanting to update but don't want to lose Xposed

uklele1234 said:
Does anyone know if Xposed works on it yet? Wanting to update but don't want to lose Xposed
Click to expand...
Click to collapse
Yes, it does
.

uklele1234 said:
Does anyone know if Xposed works on it yet? Wanting to update but don't want to lose Xposed
Click to expand...
Click to collapse
I would recommend using the magisk modified Xposed installer from the magisk stable threads, and install Xposed via magisk. The other xposed doesn't work as well, it says some modules are installed and running, but actually not doing anything. Just a heads up
hightech316 said:
Yes, it does
.
Click to expand...
Click to collapse

fullofhell said:
I would recommend using the magisk modified Xposed installer from the magisk stable threads, and install Xposed via magisk. The other xposed doesn't work as well, it says some modules are installed and running, but actually not doing anything. Just a heads up
Click to expand...
Click to collapse
How strange for me the official xposed works better than the Magisk version, the Magisk version makes my phone restart when I try to rotate the screen.

carlosbalbuena_ said:
How strange for me the official xposed works better than the Magisk version, the Magisk version makes my phone restart when I try to rotate the screen.
Click to expand...
Click to collapse
That is bizarre. I tried official first and nothing would activate

fullofhell said:
That is bizarre. I tried official first and nothing would activate
Click to expand...
Click to collapse
I have all these modules active and it works perfectly

When will the Android One moto x4 get TWRP?

??

chandypandy said:
??
Click to expand...
Click to collapse
TWRP
https://forum.xda-developers.com/moto-x4/development/root-moto-x4-t3696180

icarolessa said:
TWRP
https://forum.xda-developers.com/moto-x4/development/root-moto-x4-t3696180
Click to expand...
Click to collapse
Tried, doesn't work for the google fi variant

chandypandy said:
Tried, doesn't work for the google fi variant
Click to expand...
Click to collapse
TWRP Official
https://dl.twrp.me/payton/twrp-3.2.1-0-payton.img.html

It doesn't work

Works for my Android One X4

I think it is probably better to start with
https://twrp.me/motorola/motorolamotox4.html

chandypandy said:
It doesn't work
Click to expand...
Click to collapse
What problem are you having? Did you enable usb debugging?

The hardware is the same.

Twski said:
The hardware is the same.
Click to expand...
Click to collapse
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error

icarolessa said:
What problem are you having? Did you enable usb debugging?
Click to expand...
Click to collapse
https://dl.xda-developers.com/4/4/6....png?key=wua4zgqvFDcsrdLnpuLl_w&ts=1522291710

Our devices don't have a recovery partition to flash to.
Read the install instructions correctly:
https://twrp.me/motorola/motorolamotox4.html
You should use "fastboot boot twrp-3.2.1-0-payton.img" instead.
Then, follow along:
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your password, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
Click to expand...
Click to collapse

chandypandy said:
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error
Click to expand...
Click to collapse
I think the right command is this:
fastboot flash boot [file name].img

No,
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image.
Click to expand...
Click to collapse

chandypandy said:
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error
Click to expand...
Click to collapse
I could be wrong but it seems like you are trying to flash TWRP to the recovery partition and there's no such thing on this phone. You have to temporarily boot TWRP and the keep following the instructions.

Is anybody able to backup / restore the phone with android one on encrypted file system??, im using the official twrp, but restoring backups just cause bootloops

is it necessary to unlock the bootloader before?

If you're asking if the bootloader needs to be unlocked to install magisk, absolutely!

Sorry for the dumb question but how do you unlock the bootloader on the Fi Android one Version?

Potential fix
chandypandy said:
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error
Click to expand...
Click to collapse
If you are still haven't fixed this yet the issue is you need to fastboot boot the boot twrp image and then flash the flash image inside twrp. The guide on TWRP official will give you a guide on how to do this, the files required are also there.

Strange situation

I have an Mate 10 AL-L29. 4 days ago l tried to rebrand it to chinese model android 8.1, firmware 321. After rebrand l saw my emei is 0000000000. l did it some days ago and all was fine! Now if l make downgrade to a old firmware, my imei is fine, but if l do an upgrade to a new firmware, it doesn't matter ALP-L29 or ALP-AL00, my imei is gone! Right now l'm on the newest android 8.1- 325 firmware. All works good.....root, phone, google play etc..
The only problem is my Imei 000000000 , but MEID is ok.
Any solution guys? Thanks!

Try factory data reset.

badmania98 said:
Try factory data reset.
Click to expand...
Click to collapse
It was the first thing that l did... It isn't so simple....seems oeminfo don't do its job when l try to restore it. I have 2 backups of oeminfo, with twrp and with HwOta8_Mate10..

Root works on ALP-AL00 8.1.0.326(C00) , how? I tried Magisk but the device gets stuck on 'your device is booting'.

25Swagat said:
Root works on ALP-AL00 8.1.0.326(C00) , how? I tried Magisk but the device gets stuck on 'your device is booting'.
Click to expand...
Click to collapse
Try patching ramdisk.img from Manager but make sure Preserve AVB/DM-Verity is checked, then flash it from fastboot.

ante0 said:
Try patching ramdisk.img from Manager but make sure Preserve AVB/DM-Verity is checked, then flash it from fastboot.
Click to expand...
Click to collapse
Do you mean the stock ramdisk.img of the software I'm in? If so, then I did that and checked Preserve AVB/DM-Verity in Magisk, then flashed the patched ramdisk.img in fastboot. After rebooting, I opened Magisk but it says Magisk is not installed.
Also, after that didn't work, tried installing it from Magisk.zip but it only downloads but doesn't get installed.

25Swagat said:
Do you mean the stock ramdisk.img of the software I'm in? If so, then I did that and checked Preserve AVB/DM-Verity in Magisk, then flashed the patched ramdisk.img in fastboot. After rebooting, I opened Magisk but it says Magisk is not installed.
Also, after that didn't work, tried installing it from Magisk.zip but it only downloads but doesn't get installed.
Click to expand...
Click to collapse
You have to flash the zip from TWRP. It doesn't flash if you aren't rooted already.

ante0 said:
You have to flash the zip from TWRP. It doesn't flash if you aren't rooted already.
Click to expand...
Click to collapse
I can't boot into twrp after flashing patched ramdisk. Do I have to flash twrp again? Somehow, while trying to get into TWRP, I can't but after rebooting Magisk is installed and works but after rebooting it isn't installed. Never mind mate I got it to work. Thanks!

25Swagat said:
I can't boot into twrp after flashing patched ramdisk. Do I have to flash twrp again? Somehow, while trying to get into TWRP, I can't but after rebooting Magisk is installed and works but after rebooting it isn't installed. Never mind mate I got it to work. Thanks!
Click to expand...
Click to collapse
If it's working do explain how you did, in case others with the same problem see this

ante0 said:
If it's working do explain how you did, in case others with the same problem see this
Click to expand...
Click to collapse
I followed @Tecalote instructions posted at https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389

Can't get TWRP to work and can't get into OS

I really messed up when trying to root my phone.
I think i accidently flashed an incorrect boot.img to my phone.
Now I can't get it to boot anymore.
After this I now can't even let my XZ3 boot into twrp recovery also.
Everytime I do a fastboot boot twrp.img i get this:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
Click to expand...
Click to collapse
So i'm stuck and don't know how to boot it.
any ideas?

r3v0 said:
I really messed up when trying to root my phone.
I think i accidently flashed an incorrect boot.img to my phone.
Now I can't get it to boot anymore.
After this I now can't even let my XZ3 boot into twrp recovery also.
Everytime I do a fastboot boot twrp.img i get this:
So i'm stuck and don't know how to boot it.
any ideas?
Click to expand...
Click to collapse
Did you apply the vbmeta parameters?
Did you tried magisk 19.x? (19 may generate bootloops, I recommend my bundled 18.1)
You can always get the stock boot.img from the boot.sin in the stock firmware (April, the may twrp is not published).
Just unsin.exe the file (unsin.exe from XDA).

MartinX3 said:
Did you apply the vbmeta parameters?
Did you tried magisk 19.x? (19 may generate bootloops, I recommend my bundled 18.1)
You can always get the stock boot.img from the boot.sin in the stock firmware (April, the may twrp is not published).
Just unsin.exe the file (unsin.exe from XDA).
Click to expand...
Click to collapse
Where can I find the latest stock firmware?
I've been searching for it for hours now.
The unsin.exe I found already

r3v0 said:
Where can I find the latest stock firmware?
I've been searching for it for hours now.
The unsin.exe I found already
Click to expand...
Click to collapse
The latest (without twrp support, because I shared the first build on telegram for testing) is downloadable via Emma.
You could also use xperifirm and newflasher from XDA
In xperifirm you can choose the region, hopefully one region has still the April firmware.
PS: I see notifications for new posts or answers easily in my big threads, but it gets difficulty for the different device sections on XDA (in the app).

MartinX3 said:
The latest (without twrp support, because I shared the first build on telegram for testing) is downloadable via Emma.
You could also use xperifirm and newflasher from XDA
In xperifirm you can choose the region, hopefully one region has still the April firmware.
Click to expand...
Click to collapse
xperifirm I can use. But Emma won't recognize the phone obviously as it doesn't boot.
You mentioned the april release. Is that necessary?

r3v0 said:
xperifirm I can use. But Emma won't recognize the phone obviously as it doesn't boot.
You mentioned the april release. Is that necessary?
Click to expand...
Click to collapse
Just if you want to install twrp on your phone.
The April twrp may "fastboot boot twrp.img" with broken decryption but an installation would only lead into a not working twrp.

MartinX3 said:
Just if you want to install twrp on your phone.
The April twrp may "fastboot boot twrp.img" with broken decryption but an installation would only lead into a not working twrp.
Click to expand...
Click to collapse
At this moment all I want is to be able to boot it again.
But everytime I try to fastboot a boot.img to the phone I get:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')

r3v0 said:
At this moment all I want is to be able to boot it again.
But everytime I try to fastboot a boot.img to the phone I get:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
Click to expand...
Click to collapse
Do you use the newest fastboot version?
And the xz3 twrp?
Execute
fastboot -v
Please

MartinX3 said:
Do you use the newest fastboot version?
And the xz3 twrp?
Execute
fastboot -v
Please
Click to expand...
Click to collapse
I use this version:
fastboot version 28.0.3-5475833
And I have the latest xz3 twrp

r3v0 said:
I use this version:
fastboot version 28.0.3-5475833
And I have the latest xz3 twrp
Click to expand...
Click to collapse
Oh. Maybe 28.0.2 or 28.0.1 are working better?
Did you boot the stock firmware without any modification once first?
Edit:
Interesting
28.0.3 must be so new that even google didn't publish a changelog.

MartinX3 said:
Oh. Maybe 28.0.2 or 28.0.1 are working better?
Did you boot the stock firmware without any modification once first?
Click to expand...
Click to collapse
When I got the phone I booted it.
After that I managed to unlock the bootloader.
Then I tried to root it.
And that's when I think I fastbooted the wrong boot.img.

r3v0 said:
When I got the phone I booted it.
After that I managed to unlock the bootloader.
Then I tried to root it.
And that's when I think I fastbooted the wrong boot.img.
Click to expand...
Click to collapse
Maybe yes.
I never saw this message. Hmmm.
At least one xz3 user I know from is happy with the twrp.
Weird, very weird.
I whish I could reproduce it.

MartinX3 said:
Maybe yes.
I never saw this message. Hmmm.
At least one xz3 user I know from is happy with the twrp.
Weird, very weird.
I whish I could reproduce it.
Click to expand...
Click to collapse
TWRP worked until I messed up the boot.
When I now try to fastboot flash boot boot.img I get this:
FAILED (remote: 'Error flashing partition : Volume Full')

I managed to get it to boot to twrp. I guess at some time I set-active it to b. Setting it back to a solved the not booting twrp.
Now I used the vbmeta.img from twrp to set vbmeta.
Gonna try rooting it again now.
OS not booting yet.

r3v0 said:
I managed to get it to boot to twrp. I guess at some time I set-active it to b. Setting it back to a solved the not booting twrp.
Now I used the vbmeta.img from twrp to set vbmeta.
Gonna try rooting it again now.
OS not booting yet.
Click to expand...
Click to collapse
I recommand flashing the entire firmware via newflasher.
Remove the userdata.sin so you don't wipe your phone.

MartinX3 said:
I recommand flashing the entire firmware via newflasher.
Remove the userdata.sin so you don't wipe your phone.
Click to expand...
Click to collapse
So, I just found out You're the developer of what I downloaded.
Can I flash this one:
H9436_Customized CE1_1316-3759_52.0.A.3.84_R9B.tar.gz
through newflasher?

r3v0 said:
So, I just found out You're the developer of what I downloaded.
Can I flash this one:
H9436_Customized CE1_1316-3759_52.0.A.3.84_R9B.tar.gz
through newflasher?
Click to expand...
Click to collapse
Muahahahaha [emoji14]
You mean my old uploaded firmware?
That's just the last version before Sony changed the DRM
Better you use the 52.0.A.8.25 , it is the April stock firmware and compatible with the newest twrp so far.
I hope it is still available through xperifirm.

Ok, thanks so far. You pointed me in the right direction. Hopefully I get my Xz3 running again. ??

r3v0 said:
Ok, thanks so far. You pointed me in the right direction. Hopefully I get my Xz3 running again. [emoji1303]
Click to expand...
Click to collapse
I'm optimistic, that you'll achieved success.

MartinX3 said:
I'm optimistic, that you'll achieved success.
Click to expand...
Click to collapse
In the end.
Now i'm struggling with an error with newflasher.
No usb device with vid:0x0fce pid:0xb00b
Click to expand...
Click to collapse
Oh yeah, I'm on linux. So I'll have to do all my windows stuff through a VM

[Updated/All Versions & Models!] Root OnePlus 7T Pro

How to root any version of the OnePlus 7T Pro!
1. Make sure your bootloader is unlocked!
2. Once you're unlocked enter the following ADB commands to extract your current boot image (Your phone needs to be on)
adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img
adb pull /boot_a.img pathinyourpc
Click to expand...
Click to collapse
3. Download & install Magisk Manager on your phone
4. Put the boot_a.img file on your phone
5. Open the magisk manager app and click the "Advanced Settings" button, then enable "Prserve AVB 2.0/dm-verity & Preserve force encryption", then select the top "Install" button and select "Patch to boot image" and select the boot_a.img
6. Now magisk will create a magisk patched boot image file, put that on your computer
7. Now enter the following ADB command
adb reboot fastboot
fastboot --set-active=a
fastboot boot pathtomagiskpatched.img
Click to expand...
Click to collapse
8. Now you'll boot into the system, reopen the magisk app and click the top install button again and select "Direct install", then reboot
Congratulations you've now successfully rooted your phone!

EDIT: This guide is wrong.
Check these references for the proper guide to root. OP refuses to acknowledge it's wrong even when I pointed it out to him with proof.
https://forum.xda-developers.com/showpost.php?p=81023631&postcount=144
^^^
Mainly this one.
https://forum.xda-developers.com/showpost.php?p=81105485&postcount=171
https://forum.xda-developers.com/showpost.php?p=81106827&postcount=173
-----
Now I have something so do for the weekend, thanks
Just a question, have you tried Viper4Android (if your use it)?: Use 2.7.1.6 stable version.

hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.

Dukynuky said:
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Click to expand...
Click to collapse
Yes it says its installed thats correct but you need to install it again in the magisk app so it stays after restarting the phone. I don't know about WLAN tho

Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.

I can confirm I have successfully rooted using this method, and WIFI is working fine. Thank you very much, OP and everyone involved, no wits time to set up my device

Ah! Will do this immediately when I get home.

I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left

Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
Click to expand...
Click to collapse
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...

Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!

Dukynuky said:
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Click to expand...
Click to collapse
please see my edited reply, i installed directry through viper4android app, no the module

Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
got ist working.. layer 8 error.. didnt had the ota update installed.
Updated oxygen os.. then wifi is working. also used canary magisk files.. works perfekt.. thanks

Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
my wifi works perfectly fine, I have the EU version too.
I attached screenshots of what to do with the installed, please select the direct install option and then reboot!

droidvark said:
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Click to expand...
Click to collapse
I have a warning above the instructions already, I think you might have missed it

Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Click to expand...
Click to collapse
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!

Lossyx said:
please see my edited reply, i installed directry through viper4android app, no the module
Click to expand...
Click to collapse
Use the module next time!

HolyChickenGuy said:
I have a warning above the instructions already, I think you might have missed it
Click to expand...
Click to collapse
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!

droidvark said:
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
Click to expand...
Click to collapse
Oh sorry, yeah I rewrote it to make it clearer. Unlocking the bootloader will wipe your data
Sent from my HD1913 using Tapatalk

HolyChickenGuy said:
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Click to expand...
Click to collapse
Damn, you are my hero. Did a factory reset and followed the OP again, now everything is fine and I'm rooted. Thank you again.
edit: also, for safety precaution, disable automatic updates in Developer options
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Great, I'll check back in on this tomorrow and see how everyone is getting on before I try. Had a skim through here this morning before mine arrived and didn't see anything so set up as is.