Develop Bugs

How to Root Nexus 10 on Win/Mac/Linux! [Step-by-Step VIDEO Tutorials]

Here's a video tutorial on how to root your Nexus 10 for noobs!
Windows video tutorial:
Mac video tutorial:
Linux video tutorial:
All the files you need in one zip (adb+SuperSU+fastboot+Windows drivers):
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
Step-by-Step tutorial with photos here:
http://nexus10root.com/nexus-10-root/how-to-root-nexus-10-easiest-method/
Also, if you get stuck on bootloop after unlocking bootloader (This happened to me couple times), do a factory reset in stock recovery to fix:
Thanks to shimp208 for the sideload method and working CWM, ChainFire for awesome SuperSU and to all the developers who are worked on CWM recovery!

So the CWM that was just updated by Koushik on CWM does not work properly or does it work? Was asking based on this
While CWM Recovery is still being fixed
Click to expand...
Click to collapse
Edit: There's no driver issue if it were on a Mac right? Especially adb sideloading the CWM SuperSu zip?

How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..

johno86 said:
How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..
Click to expand...
Click to collapse
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!

I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. No red triangle. It boots into CWM and then after 20 seconds restarts itself and hits the bootanimation loop. Any clue what to do next? Trying to flash the stock image but having issues using cmds in windows cmd
*edit
I cleared cache through cmd and i got to the red triangle...thank ****ing the lord. DTWAZERE, I will remember tonight. Thank you for your help.

johno86 said:
I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. Any clue what to do next? Trying to flash the stock image but having issues getting it into fastboot now...
Click to expand...
Click to collapse
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk

dtwazere said:
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk
Click to expand...
Click to collapse
Yeah this is exactly what I did and it worked. I'll wait on flashing anything until there's a stable recovery. I was fairly confident in what I was doing until that happened. Not being able to input commands from cmd prompt made me sick so I'll wait for a dev to release something that works without having to quickly install the drivers again within a 15-20 second timeframe. Too much stress.

cant boot
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?

lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
Heh im having the same issue.

lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.

deevooneh said:
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.
Click to expand...
Click to collapse
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.

i did everything, and it all went successfully after a few tried. Now i am stuck with the JB X load screen.
How do i get the stock google rom and how do i flash it?

lc684760 said:
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.
Click to expand...
Click to collapse
Ok. Let me know if you figure something out. Hopefully we didnt brick it.

deevooneh said:
Ok. Let me know if you figure something out. Hopefully we didnt brick it.
Click to expand...
Click to collapse
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!

lc684760 said:
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!
Click to expand...
Click to collapse
How do we get back to stock? Might need to reattempt this.

If you are stuck on the boot animation (X) screen... power off your device and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely

dtwazere said:
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!
Click to expand...
Click to collapse
deevooneh said:
How do we get back to stock? Might need to reattempt this.
Click to expand...
Click to collapse
Stock is here
https://developers.google.com/android/nexus/images#mantarayjop40c
Still need a way to get CWM stable, so we have time to copy to sd

craigacgomez said:
If you are stuck on the boot animation (X) screen... power off you devices and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely
Click to expand...
Click to collapse
THIS WORKED!!
Youre a genius. thanks!

When I try to install the manta drivers manually and tell it to search the same area that it searched and found the android bootloader drivers for fastboot mode it says that the drivers couldn't be found and installed. Am I missing something? Also if i try to do fastboot flash recovery it gives me an error message stating that it cannot determine the image filename for the recovery image.

Well i guess i did it the long way around.
Went to https://developers.google.com/android/nexus/images#mantarayjop40c
and downloaded the Nexus 10 file. extracted, and the actual files in the Nexus10Root folder.
Opened the flash-all.sh and entered each command manually because it was erroring out running the script.
After the 3rd command it booted right into android!

[Q] ClockWorkMod - Stuck in Odin Mode!

Hello Everyone,
I'm hoping someone can help me out.
I installed ROM Manager on my phone, and (honestly not sure why!) but I did. When I launched the application, it told me that v. 6.0 was available if I wanted to update - Stupid me, updated ClockWorkMod to v6.0.
Well, everything was fine.. until I decided to use the ROM Manager Backup option - When I rebooted, it got stuck on
"Could not do normal boot"
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFI_LSB: 0X30
WRITE PROTECTION: Enable
Downloading....
Do not turn off target!!
I'm not sure what to do at this point. I've tried VOL UP + HOME + POWER - but it goes right back to this spot. I've pulled the battery waited for 5 mins - then tried the same VOL UP + HOME + POWER - still nothing.
Any help would be greatly appreciated.
Thanks,
Jay

Don't press the home button is the first thing I can think of.
Power + Volume up = Custom Recovery
Power + Volume down = ODIN/Download mode
To get into Recovery mode:
Pull battery
Insert battery but Don't turn phone on.
Press Power + Volume up buttons and hold them until you see the custom recovery prompt in blue lettering in the upper left corner of the S4, and then immediately release the buttons. You should enter into Recovery.
I don't use CWM so I'm not that familiar with its installation, etc. But there are a few threads that go into CWM in detail.

Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..

JayCapo1-8125 said:
Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..
Click to expand...
Click to collapse
Here's the TWRP 2.5.0.2 file:
https://hotfile.com/dl/230303459/7ce1553/openrecovery-twrp-2.5.0.2-jfltexx.tar.html
Install with ODIN.
Steps to follow........
Method #1 -
Place file in PDA box*
Uncheck all other boxes.
Press start.
When installation is complete, unplug usb cord and pull the battery.
Insert the battery but Don't turn on the phone.
Place phone in Recovery mode via the Power + Volume up buttons.
Method #2 -
The other way I've read to install TWRP Recovery is:
Place the TWRP 2.5.0.2 tar in the PDA box*
Check the auto reboot box and f time reset box.
Start the installation and let the phone reboot.
I believe the above method is method of choice, but sometimes the Recovery doesn't take, so Method #1 is then recommended.
Here is an explanation why:
http://forum.xda-developers.com/showpost.php?p=41166759&postcount=28

TWRP been having some issues, even the one people claim to be stable. Be caution with that one as well. Let us know how it works out if not can direct you to other recoveries. There are several out there all working flawlessly. Just matter of what you want you know?

mgbotoe said:
TWRP been having some issues, even the one people claim to be stable. Be caution with that one as well. Let us know how it works out if not can direct you to other recoveries. There are several out there all working flawlessly. Just matter of what you want you know?
Click to expand...
Click to collapse
TWRP looks to have worked for me.
But I can see what you mean. I no longer get stuck in ODIN MODE - but I was having issues after dropping a ROM on my phone. Even after successful setup of the ROM, if I decided to reboot just for giggles. It would freeze on Samsung S4 Logo.
Well, I have since fixed this issue:
I believe the reason why I was getting stuck on Samsung S4 Logo on reboot was because in addition to wipe data/wipe cache/wipe dalvik - I also formatted the internal_sd - this is just a theory but my internal_sd regardless of me dumping a ROM on there, after reboot would do nothing - When I went in recovery - internal_sd showed 0MB. Thus, stuck boot screen. Nothing to boot too.
FIX: Installed STOCK ROM, and KERNEL - Confirmed, that reboot works after setting up phone. My understanding is that it installs all the necessary folder structure required. Got the STOCK ROM from: http://galaxys4root.com/galaxy-s4-stock-firmware/
Then followed this root process and recovery:
http://galaxys4root.com/galaxy-s4-ro...g-twrp-method/
Once I did that, booted to recovery did the normal (wipe data/wipe cache/wipe dalvik) then dropped ALPHA ROM on my phone, along with Infamous KERNEL, and everything is great. Reboots like a champ now. -- Still using TWRP, but v. 2.5.0 - (no issues as of yet! )

Glad to see all working out for you

JayCapo1-8125 said:
Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..
Click to expand...
Click to collapse
When you say "plugged it back up to ODIN" what exactly are you doing. Do I need to download an app to my PC? I am new to this... I'm stuck on the same screen.
Thanks in advance!

sincity said:
When you say "plugged it back up to ODIN" what exactly are you doing. Do I need to download an app to my PC? I am new to this... I'm stuck on the same screen.
Thanks in advance!
Click to expand...
Click to collapse
Install ODIN 3.07 to your pc
Install drivers for your device onto your pc
I'll post a link to the ODIN thread so you can see how it's done
Update:
Here ya go:
http://forum.xda-developers.com/showthread.php?t=2258628
Please read the above thread in the link carefully.
If your device is stuck on a screen, what were you doing prior to get to that state.
First, boot into custom recovery and Wipe cache and dalvik cache, reboot, and see if that helps.
Either way, you should have ODIN on your pc

Biker1 said:
Install ODIN 3.07 to your pc
Install drivers to your device.
I'll post a link to the ODIN thread so you can see how it's done
Update:
Here ya go:
http://forum.xda-developers.com/showthread.php?t=2258628
Click to expand...
Click to collapse
Thanks a million... I'll give it a try! Wish me luck!

sincity said:
Thanks a million... I'll give it a try! Wish me luck!
Click to expand...
Click to collapse
I edited my link above.
You'll be fine.
Any questions, ask in the thread after you read about ODIN and how it works.
Once you install it on to your pc, along with the drivers which enable youropc totrecognize your device you'll find it very helpful when needed.
I have, and so have almost everyone who have ever rooted their devices and/or flashed ROMs, etc
By the way, you are not rooted?
I ask because if you are, you would have used ODIN.
What is exactly wrong now with your device?
---------- Post added at 11:58 PM ---------- Previous post was at 11:43 PM ----------
JayCapo1-8125 said:
Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..
Click to expand...
Click to collapse
If you go with TWRP, don't use Goo Manager as that will install 2.6.0.0 which has some issues for some, as you probably know.
Install TWRP 2.5.0.2 with ODIN, which I did many months ago, and have had zero issues.
You can install with Mobile ODIN also I believe.

Biker1 said:
I edited my link above.
You'll be fine.
Any questions, ask in the thread after you read about ODIN and how it works.
Once you install it on to your pc, along with the drivers which enable youropc totrecognize your device you'll find it very helpful when needed.
I have, and so have almost everyone who have ever rooted their devices and/or flashed ROMs, etc
By the way, you are not rooted?
I ask because if you are, you would have used ODIN.
What is exactly wrong now with your device?
Click to expand...
Click to collapse
Ok I figured it out... I really appreciate your help! My blood pressure went down! LOL!
Yes my cell was rooted... I used GX4EX by:
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***

Bootloader - No Command Error [solved]

Here are the steps that got me to where I am.
1. Stock Pixel XL March 2017
2. Installed TWRP
3. Installed SU
4. All worked correctly for the last month
5. Saw that there was a new April release
a. It would not install as I was rooted
b. I installed the April OTA using TWRP
c. Rebooted
6. Saw that I was no longer rooted
7. Tried to go to Bootloader
8. Got dead droid with no command error
9. Went to recovery (Power + up vol) to enter sideload
10. Sideloaded the April updated
11. Rebooted
a. Same no command error
b. Went to recovery (Power + up vol) to enter factory restore
c. Rebooted
12. Tried to go into boot loader
a. Same no command error
13. Problem is that twrp was not asking for pattern And would not install correctly with image file. Solution was to keep loading the twrp image file until it asks for pattern. Then follow standard twrp /su instructions.
Thanks.

Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk

This should be posted under Q&A not development

wyrdtrtle said:
Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Bootloader does not load.

When you get the dead Droid just hit vol up, no power button.
Sent from my Pixel XL using Tapatalk

Then what?

bschatzow said:
Then what?
Click to expand...
Click to collapse
I think I know where you went wrong you installed an incremental OTA with TW RP. If I'm not mistaken that new firmware had an updated bootloader and I believe that's dangerous to do. You may be out of luck

Why would the built in factory restore fix it?

bschatzow said:
Why would the built in factory restore fix it?
Click to expand...
Click to collapse
Can you get into fastboot?

So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?

To use fastboot you need to be in bootloader mode.

mikaole said:
So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?
Click to expand...
Click to collapse
If it is, I don't know how. I would need it to be able to load from Sideload.

Does phone boot at all? To OS?

Yes it does. Only thing not working is bootloader. Without out this I can't root.

bschatzow said:
Yes it does. Only thing not working is bootloader. Without out this I can't root.
Click to expand...
Click to collapse
Ok..if phone boots ur bootloader is still there. Phone wouldnt boot without it. You on stock rom? Hit me up on hangouts and I will try to help you if you want. For the sake of time. Im sure you wanna get this resolved ASAP.

Sent you a pm requesting contact info.

Moderator Close
Worked for a long time with BDogg718. He generously spent a great deal of his time with me and opened several Chats with Developers and No one had a solution. He is very knowledgeable and really did not want to give up. For now the solutions seems to be send it back to Google and get a replacement. It would be nice if someone could talk to Google, as a phone that has a recovery built in firmware should be able to restore itself. The dual slots seems to be a problem for them as well.

I think I had the same thing happen with me! I installed the update via TWRP. The update installation seemed to crash at the end, resulting in a reboot. The phone did install 7.1.2 successfully, but I lost root and the ability to successfully boot into any recovery. I tried flashing TWRP again, but it failed "FAILED (remote: partition recovery doesn't exist). It appeared to attempt to flash it into slot "_b", if that means anything.

TWRP will not boot on 7.1.2. At least that's the conclusion formed last night in #twrp while the devs were working with someone else with this issue. I don't think they know why yet, but I doubt it will be overly long til they figure it out.
Sent from my Pixel XL using Tapatalk

Glad to hear someone is on the case. I will be sure to send a few shekels their way for my clumsiness.

Pixel 2 xl stuck on white screen with G on it and status bar underneath

Phone is stuck on this white screen with the G on it and the status bar scrolling over and over. Phone is unlocked and rooted and i was having trouble installing a recovery onto it. I just spent 3 hours setting everything up. Do i have to wipe and start again?

equlizer said:
Phone is stuck on this white screen with the G on it and the status bar scrolling over and over. Phone is unlocked and rooted and i was having trouble installing a recovery onto it. I just spent 3 hours setting everything up. Do i have to wipe and start again?
Click to expand...
Click to collapse
What did you flash to cause this?? Did you try a hard restart by holding the power button down until it starts rebooting?

Tried a hard restart and same thing happens. I was trying to install TWRP using skipsoft toolkit #6 option.

equlizer said:
Tried a hard restart and same thing happens. I was trying to install TWRP using skipsoft toolkit #6 option.
Click to expand...
Click to collapse
Since I'm not familiar with toolkits, or their interface, I'll let someone else take over. Have you considered using adb and fastboot commands to accomplish your task?

I would if i knew what i was doing I just tried the wipe everything option and now it says "cant load android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device"
Well i did that and i get that same message over and over again. How do i start fresh? I have the image on my computer

equlizer said:
I would if i knew what i was doing I just tried the wipe everything option and now it says "cant load android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device"
Well i did that and i get that same message over and over again. How do i start fresh? I have the image on my computer
Click to expand...
Click to collapse
If you want to continue using the toolkit, I would post your problems in that thread. The folks that made it will be more qualified to help you than I could.

i went into bootloader mode and did the flash all. The phone reboots and comes back with the same message "cant load android"
I dont care what i use to get things working again. pls help.

equlizer said:
i went into bootloader mode and did the flash all. The phone reboots and comes back with the same message "cant load android"
I dont care what i use to get things working again. pls help.
Click to expand...
Click to collapse
I will try my best.
1. You have definitely unlocked_critical correct. If you haven't, you need to.
2. Have you downloaded SDK on your pc? You need this as well. You can find a link to it on Google's factory image page.
3. You have downloaded the latest factory image and unzipped it with the 7zip program.
4. Inside the SDK program, look for a file called platform tools.
5. You need to take the contents you extracted from the factory image, and place them in the platform tools folder. That includes: Radio, bootloader, the flash-all.bat file, and another large zip file that contains the boot, system, vendor and about 16 other things.
6. Put your phone into bootloader mode and plug it into the pc. Open a command prompt from the platform tools folder and type "fastboot devices" if your phone ID comes up, your good.
7. Double click the flash-all.bat file, and that should start the installation process. It will take a little while to install the OS, so be patient. If all goes well, your phone should automatically boot up.
8. I will try and find a link for all this installation stuff.
9. Good luck!
---------- Post added at 01:23 PM ---------- Previous post was at 01:16 PM ----------
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Here is a link to instructions written by one of the best kernel developers out there. Read it carefully if what I gave you doesn't make sense.

Tried it this morning and when i go to root with magisk (followed every step) i get the white screen with the G and the bar scrolling

equlizer said:
Tried it this morning and when i go to root with magisk (followed every step) i get the white screen with the G and the bar scrolling
Click to expand...
Click to collapse
Did you ever get your phone to boot up on stock system?

Badger50 said:
Did you ever get your phone to boot up on stock system?
Click to expand...
Click to collapse
Not sure how i did it but it seems to have reverted back to complete stock. Everything setup after but when it rebooted it said "this device cannot be trusted, hit the power button to continue" so i do and it seems to boot back into the phone. How do i get rid of that message?
Ive never had so many issues with a phone before.

How do i get rid of that message?
once you had the Bootloader unlocked in this phone it will display that message in every boot, there is no way to get rid of it at this moment.

equlizer said:
Not sure how i did it but it seems to have reverted back to complete stock. Everything setup after but when it rebooted it said "this device cannot be trusted, hit the power button to continue" so i do and it seems to boot back into the phone. How do i get rid of that message?
Ive never had so many issues with a phone before.
Click to expand...
Click to collapse
A lot of trouble people have with these phones has to do with the A/B partitions, glitches in cables, sdk, PC's, ghosts in the machine, and users not taking the time to read and learn what to do. Anyway, glad you got it going. Your welcome.

Everything else worked except for the rooting with magisk. when it patches the image using manager 5.4.3 it says its downloading version 14.0 not 14.5. I go to flash the patched boot img then it just reboots to the white screen with the G and it hangs there till i shut it off.

equlizer said:
Everything else worked except for the rooting with magisk. when it patches the image using manager 5.4.3 it says its downloading version 14.0 not 14.5. I go to flash the patched boot img then it just reboots to the white screen with the G and it hangs there till i shut it off.
Click to expand...
Click to collapse
Manually download 14.5 and flash it in twrp. Or, take the stock boot.img, place it on your phones internal storage, open magisk, hit install, and select patch boot (I think) Then take the patched_boot.img and flash that with fastboot. Either way should give you root.

I already said I patched it using the magisk I installed but when I flash it I get the G on the white screen. I can't even get twrp to stick. This was all using 8.1 but now I'm on 8.0. I guess I'll try again?

equlizer said:
I already said I patched it using the magisk I installed but when I flash it I get the G on the white screen. I can't even get twrp to stick. This was all using 8.1 but now I'm on 8.0. I guess I'll try again?
Click to expand...
Click to collapse
What twrp version are you using? So, you can fastboot the twrp-3.1.1-beta2-taimen-img but then are unable to flash the twrp.zip once you enter temporary twrp?

I just downloaded twrp 3.1.1 beta 2 taimen.img and the zip
how do i fastboot the img?
then from there do i flash magisk 14.5.zip then reboot and install magisk manager 5.4.3 then check for root?

equlizer said:
I just downloaded twrp 3.1.1 beta 2 taimen.img and the zip
how do i fastboot the img?
then from there do i flash magisk 14.5.zip then reboot and install magisk manager 5.4.3 then check for root?
Click to expand...
Click to collapse
Go to fastboot and type: fastboot boot twrp-3.1.1-beta2-taimen.img
That should immediately take you temporary twrp where you then flash the twrp.zip, and then flash your magisk zip. That should also install the magisk app as well.

it takes me to the screen where it says "this devices cannot be trusted" so i hit the power button then it just reboots into android 8.0. I appreciate all the help

What have I done to my phone? - TWRP.

Good evening all.
I must have done somethingto my phone... as, when I install TWRP, it boots for the fist time, but then it disappears and all recovery boots go to stock recovery
Could it be a matter of partitions?
Thanks a lot.

manoloyloles said:
Good evening all.
I must have done somethingto my phone... as, when I install TWRP, it boots for the fist time, but then it disappears and all recovery boots go to stock recovery
Could it be a matter of partitions?
Thanks a lot.
Click to expand...
Click to collapse
As long as you are flashing twrp & not booting twrp image there's no reason why it shouldn't perminatly be there
Full instructions on my twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
To access recovery after you have
fastboot flash recovery recovery.img
Hold power and volume down
At bootloader menu use volume keys to navigate to recovery option
Press power button to select recovery option
Any other questions read the faq on the second post first

TheFixItMan said:
As long as you are flashing twrp & not booting twrp image there's no reason why it shouldn't perminatly be there
Click to expand...
Click to collapse
Many thanks for your reply. This is why I am so disoriented about the cause...
I have flashed twrp for years on various phones: HTC, Samsung, Motorola... I do exactly as per your instructions, I get the OK after the flash, reboot and it is there. Reboot again.... and back to stock

manoloyloles said:
Many thanks for your reply. This is why I am so disoriented about the cause...
I have flashed twrp for years on various phones: HTC, Samsung, Motorola... I do exactly as per your instructions, I get the OK after the flash, reboot and it is there. Reboot again.... and back to stock
Click to expand...
Click to collapse
Once you entered twrp for the first time did you swipe to allow modifications?
If using stock rom you also need to disable dm-verity or your phone will not boot

Maybe the stock rom is flashing stock recovery whenever you boot into it? Try flashing twrp while using a custom rom and see if it still boots to stock recovery instead of twrp.