Database Users

I got the T-Mobile LYZ28J update. How to get off phone?

I just got the new T-Mobile update, but I haven't flashed it. How do I get it off the phone? I looked in /cache and /download and it's not in either. I am rooted so I have access to all the folders.
Thanks

Same here. Trying to figure out how to pull the OTA for you guys.

Have you guys tried this method? Starting from #6 on.
http://forum.xda-developers.com/showthread.php?p=56859170

https://android.googleapis.com/pack...amu-ota-LYZ28J-from-LYZ28E-superblock-fix.zip

Sweet! Thanks. Now I have to try and flash it

Downloaded and Sideloaded. Just waiting for it to finish booting.
Finished boot. Took a minute but seems to respond fine after initial startup.

biggiestuff said:
https://android.googleapis.com/pack...amu-ota-LYZ28J-from-LYZ28E-superblock-fix.zip
Click to expand...
Click to collapse
Can we flash this with TWRP? If we have the stock but rooted rom?

samomamo said:
Can we flash this with TWRP? If we have the stock but rooted rom?
Click to expand...
Click to collapse
I used wugs to flash stock rom with no wipe. Then took the OTA. You can side load it as well. Then used wugs to re-root
Sent from my Nexus 6 using Tapatalk

samomamo said:
Can we flash this with TWRP? If we have the stock but rooted rom?
Click to expand...
Click to collapse
no

simms22 said:
no
Click to expand...
Click to collapse
Thank you

The full LYZ28J image is now available for download directly from Google.

does anyone know if there's a boot.img without forcencrypt for LYZ28J?

What's the difference, please, between the file posted by @biggiestuff
https://android.googleapis.com/pack...amu-ota-LYZ28J-from-LYZ28E-superblock-fix.zip
and the one posted by @jcsww
https://dl.google.com/dl/android/aosp/shamu-lyz28j-factory-0530e1e3.tgz ?

PhilipTD said:
What's the difference, please, between the file posted by @biggiestuff
https://android.googleapis.com/pack...amu-ota-LYZ28J-from-LYZ28E-superblock-fix.zip
and the one posted by @jcsww
https://dl.google.com/dl/android/aosp/shamu-lyz28j-factory-0530e1e3.tgz ?
Click to expand...
Click to collapse
Mine is the OTA and the other is the full factory image
Sent from my Nexus 6 using Tapatalk

vivanshah said:
does anyone know if there's a boot.img without forcencrypt for LYZ28J?
Click to expand...
Click to collapse
Looks like not yet. I tried using Wug's toolkit just now and got the attached error.

vivanshah said:
does anyone know if there's a boot.img without forcencrypt for LYZ28J?
Click to expand...
Click to collapse
allen099 said:
Looks like not yet. I tried using Wug's toolkit just now and got the attached error.
Click to expand...
Click to collapse
There is now I had made one earlier today for my new N6Shamu rom which uses the LYZ28J as a base. I de-odexed it as well. While I was making the rom, I edited the kernel so it does not force encrypt. Try this flashable zip and let me know how you get on.

Stephen said:
There is now I had made one earlier today for my new N6Shamu rom which uses the LYZ28J as a base. I de-odexed it as well. While I was making the rom, I edited the kernel so it does not force encrypt. Try this flashable zip and let me know how you get on.
Click to expand...
Click to collapse
Cool! Trying it now.
*EDIT* I can simply extract the .img, rename it, and drop it into the toolkit, correct?

allen099 said:
Cool! Trying it now.
*EDIT* I can simply extract the .img, rename it, and drop it into the toolkit, correct?
Click to expand...
Click to collapse
Its a fully flashable zip, but yes you can.

lorloff said:
Downloaded and Sideloaded. Just waiting for it to finish booting.
Finished boot. Took a minute but seems to respond fine after initial startup.
Click to expand...
Click to collapse
samomamo said:
Can we flash this with TWRP? If we have the stock but rooted rom?
Click to expand...
Click to collapse
Not sure if these two posts are related and I'm probably doing something wrong trying to apply this update. I am stock rooted with the MultiROM version of TWRP 2.8.7. When I go into ADB Sideload, ADB loses the connection so I can't sideload. I just updated to Windows 10 Pro too, so I don't know if that is related either.
These are the commands I used after I connected my phone:
adb devices (works)
adb reboot recovery (works)
In TWRP - Advanced, then ADB Sideload (works)
Swipe to Start Sideload (connection lost)
Cancel (connection restored)
Any tips or help to get this installed would be greatly appreciated.

JimSmith94 said:
Not sure if these two posts are related and I'm probably doing something wrong trying to apply this update. I am stock rooted with the MultiROM version of TWRP 2.8.7. When I go into ADB Sideload, ADB loses the connection so I can't sideload. I just updated to Windows 10 Pro too, so I don't know if that is related either.
These are the commands I used after I connected my phone:
adb devices (works)
adb reboot recovery (works)
In TWRP - Advanced, then ADB Sideload (works)
Swipe to Start Sideload (connection lost)
Cancel (connection restored)
Any tips or help to get this installed would be greatly appreciated.
Click to expand...
Click to collapse
I had the same issue. I found this somewhere and it worked:
From a command prompt (administrator):
adb devices and be sure it shows your device serial number.
adb reboot recovery
Use the Power button and Volume + button to get past the green droid with the red sign.
Unplug the usb cord from the PC and then plug it back in.
In W10, go to Device Manager.
Find your phone under Other Devices with a Yellow !.
Right click on it and choose "Update Driver Software"
Choose "Browse my computer", then "Let me pick from a list."
If you see categories, select "Android Device", then select "Android ADB Interface".
The driver will install and adb sideload should proceed with the update.
What a PITA but it worked.

[GUIDE] Sideload NOF27B/C on Stock, TWRP, Custom Kernel, Mods, Root - Updated 3/6/17

Follow at your own risk, I take no responsibility. This guide is for any stock(seems to work with mods) rom. I used TWRP RC1, but could possibly work with alpha 2(for adb sideload only). Not sure if this method is "better" than using flash-all.bat without -w, but the file download was smaller.
Required Files and Locations they should be placed:
TWRP RC1 Image placed in the same folder as your FASTBOOT executable
TWRP RC1 zip installer placed on phones internal storage
SuperSU 2.79 SR3 zip installer placed on phones internal storage
NOF27B or NOF27C - Rogers OTA placed in the same folder as your ADB executable
Ensure the TWRP and SuperSU zip installers are loaded onto the phones internal storage and the OTA zip and TWRP image are in the ADB/FASTBOOT executables folder.
Boot into current TWRP recovery
Make a full backup in TWRP
Connect the phone to the computer
In TWRP select the Advanced menu, click ADB sideload option
On the computer open a command window and navigate to the location of your ADB executable/OTA zip
Only execute one adb sideload command for your specific device
Execute the following command(Non-Rogers): adb sideload sailfish-ota-nof27b-8130b5a8.zip
Execute the following command(Rogers): adb sideload sailfish-ota-nof27c-fb487658.zip
Only execute one adb sideload command for your specific device
The command window should be displaying a percentage and the TWRP should be displaying the standard OTA step 1 and 2 - Let this complete
Click Reboot System and let the OTA finish installing
At this point TWRP and Root are gone, but can be restored
With the device powered off, hold volume down and turn on the device. Your device should now be in the bootloader.
With the device connected to the computer run the following command from the previous step's command window: fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Install twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip in TWRP
Install SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
Click Reboot System
Install Kernel/Mods
Remember to restore any /system specific edits such as the tether build.prop edit, host file edits, or custom boot animations.

This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed

bush911 said:
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
Click to expand...
Click to collapse
Just remove the -w argument from the flash-all.bat and flash the factory image...

Thank you dude, so what's the difference between full factory image and full ota zip, and ota automatically downloaded to phone.
the factory image is around 1.8 G and full ota zip is around 800 M, but the ota automatically downloaded to phone is only 47 M
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse

I had good luck with this method getting to NMF26O. Just a couple of things to note. Make sure you have the latest ADB files, and while it probably is assumed that you are using TWRP RC1 I'm pretty sure this did not work in Alpha2. Also, when the OP mentions losing TWRP it actually completely removes recovery so don't freak out if you try to boot into it expecting stock recovery and get a no data (or something like that if I remember correctly) error. There is no reason to check, but last time I was curious to see if it would leave TWRP in place. All is fine as long as you can get to bootloader. One other thing is the fact that this is an OTA. I would not do this unless coming from NMF26O but that is just me.
I am in no hurry to do this update since by all accounts it adds no functionality, but I was going to try it this way again. I wonder if anyone has any reason other than habit to continue to use the flash all method.

Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
so should we sideload the OTA over Q or download the factory image and remove the -w flag and run flash all.bat?

can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks

quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
This is only for updating stock. If you want of weta then use the full image and remove the -w from the flashall bat file.

thank you! worked great!

quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
Because I'm groovy like that... (And had a nandroid backup) I went ahead and took the jump of sideloading the OTA update over weta 2.2.1. Personally, I wasn't too concerned about botching up the system, as the weta ROM is going away. Instead the author is now compiling his mod(s) to layer over this stock build. I'm assuming that the OTA sideload went without a hitch because weta is designed around the stock image. Of course, I had to install some of my mod's again that were lost in the "update"
**DISCLAIMER**
I'm not claiming or declaring the OTA update is safe to install over weta 2.2.1. I'm only giving my experience so others can weigh out the risks for themselves, if they decide to roll the dice. :silly:

I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay

rohitece06 said:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
Click to expand...
Click to collapse
I don't use Pay, but did you update to the latest Elemental kernel 1.03?

spiller37 said:
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
Click to expand...
Click to collapse
Yes I did.

rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
Try Franco's, his is patched for pay. Just to try and narrow it down here.

rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
You might also try the patched stock kernel that was just updated.

spiller37 said:
You might also try the patched stock kernel that was just updated.
Click to expand...
Click to collapse
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.

Is something up with the OP or is it just my XDA app causing it to show like this..

aholeinthewor1d said:
Is something up with the OP or is it just my XDA app causing it to show like this..
Click to expand...
Click to collapse
Not sure why it displays this way in the two XDA apps. If anyone knows how to fix the formatting I would be grateful for the solution.

rohitece06 said:
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Click to expand...
Click to collapse
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.

spiller37 said:
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
Click to expand...
Click to collapse
it was working before this January pixel update

How do I update my 6T rooted without erasing datas?

Dear all,
first of all I would like to be sorry if I'm saying something worng. I'm not so expert about Android world.
I've got a OnePlus 6T that I've rooted with the help of a friend some months ago.
Not it's a lot that I keep see the notification abount the OS update and I keep skipping it but it's bothering me so... I searched for a guide and I found this (https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/) (I hope I can post it also if it's from another website).
It seems so simple, I've downloaded the OTA update, the TWRP and the Magisk. My issue is that whene I reboot to the recovery I'm not booting into TWRP but I suppose into the OnePlus recovery instead.
I searched angain and found this other guide (https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953) that is more complete but I can't understand if it's the proper guide I need to follow to update my device keeping it rooted and most of all without loosing any data.
Thanks,
Riki

The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.

OhioYJ said:
The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.
Click to expand...
Click to collapse
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Thanks again,
Riki

RikiBez said:
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Click to expand...
Click to collapse
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.

OhioYJ said:
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.
Click to expand...
Click to collapse
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
Old_video_link_removed
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.

RikiBez said:
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
https://youtu.be/7Re-p7Z1yhc
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.
Click to expand...
Click to collapse
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?

OhioYJ said:
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?
Click to expand...
Click to collapse
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.

RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app

RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.

CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app

i7vSa7vi7y said:
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fastboot was working until I reinstalled adb and OnePlus drivers.

CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.

RikiBez said:
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.
Click to expand...
Click to collapse
Try uninstalling adb. Delete the whole folder and install it again. Try updating your netframework on your PC and the latest C++
Sent from my OnePlus 6T using XDA-Developers Legacy app

I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.

RikiBez said:
I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.
Click to expand...
Click to collapse
Use the msm tool for that
Sent from my OnePlus 6T using XDA-Developers Legacy app

Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.

OhioYJ said:
Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.
Click to expand...
Click to collapse
Those fastboot roms have sure saved me from raging before
I would also recommend using migrate, it's in the play store and it backs up all your data and then puts it in a flashable zip

i7vSa7vi7y said:
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Do a factory reset from TWRP and flash the full ROM.

One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.

sanjeev7 said:
One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.
Click to expand...
Click to collapse
So I don't have to wipe my system data or anything. I heard some people had the problem of getting stuck or that there was a red warning screen that popped up when booting, and I'm not talking about the bootloader message. I'm currently on 9.0.11. Also should I download the latest version of TWRP or should I use the one I'm using currently. Don't wanna mess anything up. Another guide I read said I should flash the oos rom, then TWRP, than magisk

can I root my mi 9t temperorly

Is there a way to get temp root for some time then disable it

Why don't you flash Magisk and then uninstall it?

Depends on what you want to achieve with getting temporary root. If you want to make a backup of your untouched phone, you could try to boot into the latest twrp (test) version or and get temporary root trough an adb shell.

for what purpose?

flamedrops said:
for what purpose?
Click to expand...
Click to collapse
Like to access net cut to remove hackers for some Intruders on my network

Medeon said:
Depends on what you want to achieve with getting temporary root. If you want to make a backup of your untouched phone, you could try to boot into the latest twrp (test) version or and get temporary root trough an adb shell.
Click to expand...
Click to collapse
No I mean on Android not twrp if correctly understood.
And that adb shell how to do this ?? Please answer me

batman957 said:
No I mean on Android not twrp if correctly understood.
And that adb shell how to do this ?? Please answer me
Click to expand...
Click to collapse
First I would like to say, do your research before you post a question here. The answers to your questions are literally one Google or XDA search away from you. Having said that, your best bet would probably be Kingoroot although I can't promise you it will work. I have tried it once on an older phone, but I did not succeed. But you could try.
If it's not working, the only way to gain root access is to unlock the bootloader of your phone. This will void your warranty. It's up to you to decide whether it's worth it or not. It will probably take a week or longer for Xiaomi to grant you to unlock the bootloader.
Here is a noob friendly guide on how to install and use adb and fastboot
Ones installed go and download this version of twrp recovery and put it inside your adb (or platform tools) folder. Download the latest version of Magisk, Magisk manager and Magisk uninstaller from here and put it inside of your phone's internal storage.
Inside your settings tap the MIUI version 7 times to "become a developer". Then go to developer options and switch adb debugging on.
Follow the adb and fastboot guide, but don't flash this recovery to your phone. Instead in your cmd or terminal type:
Code:
adb devices
Code:
adb reboot bootloader
This will boot your phone in fastboot mode, then type:
Code:
fastboot boot <your_downloaded_twrp.img>
Replace <your_downloaded_twrp.img> with the actual name of the image. This will boot you into twrp recovery without flashing it to your phone. Probably you will be welcomed with a menu with a slider that says "swipe to allow modifications" don't swipe, just choose "keep system read only". In the menu choose Install (install a zip) and flash the latest Magisk from your internal storage.
Reboot to system and you have root access. If Magisk manager is not installed yet, install the .apk file you downloaded. If you want to unroot the phone boot into twrp ones again and flash the Magisk uninstaller.

batman957 said:
Like to access net cut to remove hackers for some Intruders on my network
Click to expand...
Click to collapse
I used netcut also and i used magisk root.

Medeon said:
First I would like to say, do your research before you post a question here. The answers to your questions are literally one Google or XDA search away from you. Having said that, your best bet would probably be Kingoroot although I can't promise you it will work. I have tried it once on an older phone, but I did not succeed. But you could try.
If it's not working, the only way to gain root access is to unlock the bootloader of your phone. This will void your warranty. It's up to you to decide whether it's worth it or not. It will probably take a week or longer for Xiaomi to grant you to unlock the bootloader.
Here is a noob friendly guide on how to install and use adb and fastboot
Ones installed go and download this version of twrp recovery and put it inside your adb (or platform tools) folder. Download the latest version of Magisk, Magisk manager and Magisk uninstaller from here and put it inside of your phone's internal storage.
Inside your settings tap the MIUI version 7 times to "become a developer". Then go to developer options and switch adb debugging on.
Follow the adb and fastboot guide, but don't flash this recovery to your phone. Instead in your cmd or terminal type: This will boot your phone in fastboot mode, then type: Replace <your_downloaded_twrp.img> with the actual name of the image. This will boot you into twrp recovery without flashing it to your phone. Probably you will be welcomed with a menu with a slider that says "swipe to allow modifications" don't swipe, just choose "keep system read only". In the menu choose Install (install a zip) and flash the latest Magisk from your internal storage.
Reboot to system and you have root access. If Magisk manager is not installed yet, install the .apk file you downloaded. If you want to unroot the phone boot into twrp ones again and flash the Magisk uninstaller.
Click to expand...
Click to collapse
Alright thanks for the help an effort

batman957 said:
Alright thanks for the help an effort
Click to expand...
Click to collapse
Sure, no problem. Forgot to mention, if you decide to unlock the bootloader all your personal data (including internal storage) and apps will be wiped. So make a backup beforehand. Helium is a non root app that you could use for that purpose.
You could also relock the bootloader again, but that's a whole other tutorial by itself.

Medeon said:
Sure, no problem. Forgot to mention, if you decide to unlock the bootloader all your personal data (including internal storage) and apps will be wiped. So make a backup beforehand. Helium is a non root app that you could use for that purpose.
You could also relock the bootloader again, but that's a whole other tutorial by itself.
Click to expand...
Click to collapse
Just I forgot to ask can i use twrp temperorly as you said to install magisk then return back to the stock recovery and still have magisk available

batman957 said:
Just I forgot to ask can i use twrp temperorly as you said to install magisk then return back to the stock recovery and still have magisk available
Click to expand...
Click to collapse
Yes, you don't flash twrp recovery to the phone if you just boot into twrp recovery. It boots the image in your phone's RAM.

Medeon said:
Yes, you don't flash twrp recovery to the phone if you just boot into twrp recovery. It boots the image in your phone's RAM.
Click to expand...
Click to collapse
What about magisk

batman957 said:
What about magisk
Click to expand...
Click to collapse
When you install magisk trough twrp, you flash the zip file which cleverly patches parts of your boot and data partition. It does it systemlessly, so it won't modify the system. You can easily reverse this procedure by flashing the magisk uninstaller. It will bring your phone back in the state it was before rooting.

[GUIDE] Root Android 12/OOS12 (T-Mobile)

Requires Bootloader to be unlocked (Tutorial for unlocking T-Mobile bootloader)
INSTRUCTIONS
- Download the latest Magisk.zip from github, it will be an apk file. Rename it to a ".zip" file. (link below)
- Download attached recovery.img and boot into it using fastboot on a PC. (command below)
- Once booted into recovery choose "Apply Update" then "Apply from ADB"
- In adb on your PC, push the magisk.zip with the command "adb sideload Magisk-vXXX.zip" Make sure the magisk zip file is in your fastboot folder if you don't have fastboot system-wide.
- It will give signature verification error on your phone, choose "INSTALL ANYWAY"
- Reboot to system and install the Magisk Manager app. Choose install at the top, select direct install, and allow the app to install and reboot.
To flash recovery
Code:
fastboot boot recovery recovery.img
DOWNLOADS
- Latest Magisk
- Recovery.img

Awesome easy as can be, worked great. Thank you!

Does it need unlocked bootloader?

remialfa said:
Does it need unlocked bootloader?
Click to expand...
Click to collapse
Yes sir

So simple & fast... no fussy boot.img patching with specific Magisk versions, etc!
How will you install updates?
Thanx

mobile_sensei said:
So simple & fast... no fussy boot.img patching with specific Magisk versions, etc!
How will you install updates?
Thanx
Click to expand...
Click to collapse
Can we update magisk from the magisk app?

TeamHackura said:
Can we update magisk from the magisk app?
Click to expand...
Click to collapse
Yes my friend working like a charm

FoxyDrew said:
Yes my friend working like a charm
Click to expand...
Click to collapse
Excellent! Thank you.
For others when installing oos update; disable magical modules, install oos update, before restarting install Magisk to both slots using the app, reboot, enable modules if any.

Using tmobile oneplus 8 unlocked bootloader
Can you break this down a bit more? So I'm on a mac I downloaded both files. Typed the command into the terminal and get disk image is corrupted

Rms44 said:
Using tmobile oneplus 8 unlocked bootloader
Can you break this down a bit more? So I'm on a mac I downloaded both files. Typed the command into the terminal and get disk image is corrupted
Click to expand...
Click to collapse
No experience with fastboot on mac, but try to re-download the image.

FoxyDrew said:
No experience with fastboot on mac, but try to re-download the image.
Click to expand...
Click to collapse
it worked thank you

I'm stuck on the part where you have to side load the magisk file in recovery. When i do the command i get his error
adb: failed to read package block: Is a directory

Rms44 said:
I'm stuck on the part where you have to side load the magisk file in recovery. When i do the command i get his error
adb: failed to read package block: Is a directory
Click to expand...
Click to collapse
Are you sideloading the zip, or maybe when you downloaded the magisk zip, your Mac automatically unzipped it so you now have a directory.
I haven't used this root method, but I use Macs once in a while, and that's one of my annoyances with one of the Macs I use.

trinidude4 said:
Are you sideloading the zip, or maybe when you downloaded the magisk zip, your Mac automatically unzipped it so you now have a directory.
I haven't used this root method, but I use Macs once in a while, and that's one of my annoyances with one of the Macs I use.
Click to expand...
Click to collapse
What would I do to remove the directory just delete the file ?

Rms44 said:
What would I do to remove the directory just delete the file ?
Click to expand...
Click to collapse
You have to just make sure you have the magisk zip file instead of an unzipped version. Next time I'm working on a mac, I can play around to see if I can replicate your problem.

Rms44 said:
What would I do to remove the directory just delete the file ?
Click to expand...
Click to collapse
I finally had some time to try this out on a Mac and everything worked out for me. I couldn't get the same error message you were getting. I did use Magisk v22 though. The only thing you'll have to do is rename the .apk to .zip.

Hey there, bro. seems like the Recovery link is down, please help me out

aperisimo said:
Hey there, bro. seems like the Recovery link is down, please help me out
Click to expand...
Click to collapse
Nvm i extracted recovey.img from the crdroid rom myself. hope it works

Thank you.
Works on OnePlus 8 India.
Since the recovery link in OP is deleted, I extracted the latest one myself.
Here's the recovery from crDroidAndroid-11.0-20210517-instantnoodle-v7.6

This didn't work for me, I got this error after running sideload. Any idea how to resolve this?
"E: Failed to find update binary META-INF /com/google/android/update-binary"