Hello, first of all sorry for my lack of tech knowledge.
So, I rooted my phone and tried to use Magisk for Gcam. Could not make it work so I was going to unroot my phone and started by unistalling magisk.
When I did it, it went to restart and I got the "no command" massage. By reading articles I first went to factory reset. I didn't work.
Later I tried Installing the TWRP, firstly it got me a black screen, but now I used adb to try to get to fastboot again to unistall it got stuck with a Android One logo freeze and I can't get to the fastboot.
No idea on what to do.
Edit: got to fastboot again by pressing power and vol down for a couple of seconds
A guy on Reddit solved it. All I had to do was to flash the stock boot.img I had before the root. I tried a couple until It was the right one and my phone resurrected.
FOR OTHER USERS WITH THE SAME PROBLEM: IF YOU GET "NO COMMAND" AFTER UNROOTING WITH MAGISK : flash the stock boot.img
If you are bricked with magisk then dont waste your time on flashing via fastboot sideload because nothing can unbrick.
The only way to recover your phone is via EDL mode ,
Search in the fourm and go through test point , your phone will be alive .
luizfernandosc said:
I tried a couple until It was the right one
Click to expand...
Click to collapse
This is probably one of the reasons why you bricked it in the first place. Don't just "try some", but read the forum over and over again until you're 100% sure you flash the right thing (rom, recovery, boot,..) for your particular phone version from the first time!
You were lucky to be able to resurrect it now, but flashing wrong things doesn't always give you that second chance!
That being said, rooting your phone with magisk and getting gcam to work is pretty easy, if you find the right tutorial for your specific device and follow their steps.
Related
Long story short: Phone won't boot past "Unlocked Bootloader" warning; Recoveries won't stick; Unknown Error & Freezing when trying to Flash System.img
I own an ATT Locked Moto X, but went ahead and unlocked it by purchasing the oem code. No issues there.
I decided to go ahead and try rooting it too, and was able to flash TWRP as my recovery. Still, everything seemed to be looking good, until I tried hard rebooting (to see if root would last). Upon rebooting, I could not get past the warning sign, notifying me that the bootloader was unlocked. I waited, and waited, and restarted again, but all progress stopped there. I would be the first to admit that whatever happened was probably my fault; perhaps I flashed some files in the wrong order, or entered a wrong command into fastboot. I don't know, and frankly don't care. My only question is how to get out of this mess and back to rooting, or at the very least, back to stock ROM now that I'm unlocked.
Booting into recovery only leads to the red triangle over an open android mascot, with the "Android Recovery" title. So clearly TWRP didn't stick; I tried reflashing, but nothing lasts past reboot. Then I tried flashing Philz Touch instead, which, upon exit, notified me that root was not enabled. So I rooted, rebooted, and was finally able to see Philz Tough again, even though I still can't boot normally. That time, both Philz Touch as well as root seemed to have stuck.
With that minor victory I downloaded the latest firmware for my model and tried to flash the components over, thinking I had somehow corrupted the existing OS files, but here's where it gets particularly frustrating. I am able to flash every file except for system.img, even though I am using moto-fastboot, which I understand is a common mistake. I get no specific error code, simply "Unknown Error," upon which the phone is frozen in fastboot. The phone remains unresponsive until I hard reboot [back into fastboot], and see that, once again, Recovery is back to stock. So now I'm baffled. I can't seem to find a way to flash the system file, factory resetting doesn't work, and my recoveries are constantly reverted back to stock. Does anyone have any advice, or suggestions for what I could try next?
You try RSD lite?
Sent from my XT1058 using xda app-developers app
southern87 said:
You try RSD lite?
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I was already downloading it just as I saw your post, as my last-ditch effort. It also failed, but it gave me "Unknown USB Error," which is all I needed, it seems. I tried a different USB slot on another side of the computer, and lo-and-behold, the flash finished.
I'm not sure what saddens me more, the fact that I pushed off making this post for hours, only to have the solution less than an hour after I do, or the fact that I never thought to try a different USB port... In any case, sorry for the uselessness of this post. I think I'll save rooting for another day though...
I am able to unlock bootloader via the htcdev method, I show I am s-off, I flash twrp and it says it succeeded. hold volume- and power to get to bootloader no prob. select recovery it gives me one of two errors. 1) this htc device is for blah blah blah or 2) I get a red triangle with a hard drive symbol and after a miniute or so it will reboot to normal. I have not been able yet to get into recovery for both twrp or cwm
Some-what Solved
Just for the sake of others, Ive been messing with this for a few days. finally found someone mention using an older version of twrp. I was using twrp-3.0.2-0-mystul so I tried the version mentioned openrecovery-twrp-2.5.0.0-mystul and that solved the problems I was having.
Next question. I was reading that I had to downgrade to
RUU_MYST_UL_Cingular_US_1.08.502.1_Radio_1.15.40.00.13_2_10.64.40.33AL_release_316579_signed_2
to make mooshine's s-off tool work but i could never get it to work, ended up being easier to input it all maually.
question is can I upgrade back to
RUU_MYST_UL_Cingular_US_1.08.502.4_Radio_1.19.40.00.09_10.69.40.33IL_release_327090_signed_2
or is there something better
and can I do this with out losing root and twrp or will I have to redo all of this again, I have seen these are difficult devices with little support.
Also, I am seeing that after I am rooted and all, I have also deleted ALL "AT&T" apps, I now have the problem of the stock chrome app crashes and causes a reboot every time it is opened. Should I just remove this and then download it from the app store so it doesnt have any dependancies on at&t if that is what is going on?
Thanks in advance
I have update my rooted OP 3T by flashing the complete rom through TWRP.. But the problem is whenever I flash the Supersu version : SuperSU-v2.79-201612051815 or SR3-SuperSU-v2.79-SR3-20170114223742, I am getting bootloop.
Please anyone advise me.
I checked that without flashing SuperSU phone is able to Boot safely.
Thank you in advance.
It's normal if it bootloops once or twice
But if it's more than that then it's problematic
So which one is it
Another thing you can try is try magisk root instead of supersu and see if gets the same result
Phone was stucked in bootloop for an hour without any reboot.
I am not fond of magisk yet... So dont have any plan for it.
Just want to know if this happens to only me or there are many others with same issue.
Edit:
Finally installed Magisk for root... Issue closed.
help!?
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
plzz can anyone help me
amber sachdeva said:
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
Click to expand...
Click to collapse
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
redpoint73 said:
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
Click to expand...
Click to collapse
well i tried unlocking bootloader but it says failed (remote: oem unlock not allowed)
Iam i stuck here for ever ?
can u tell me the command that i can try on an phone with a locked bootloader
I forgot this is an edit the first time Gentlemen, I am absolutely at wit's end now I am no geek with a capital G however I have been modifying phones for some 3 years now and I can't even tell you how many times I flashed ROMs my beloved 3T 3T has had been acting glitchy lately like when I would reboot the circle that turns - instead of just turning evenly it would twitch, it was such a small thing I ignored it but I think now that that's must be have been indication something was not right few other things like that. I flashed the Freedom ROM cuz I'm so sick a Google and Google Assistant when I came out I was in a bootloop so I wiped everything except OTG everything and formatted data did the ROM Flash again the a boot Loop still abides and I've done it a dozen times now sometimes a couple of times it it just it kept recycling the bootloop another time and got hung up on the OnePlus it just sat there on the logo and if I miss something obvious I do apologize I'm tired and I'm at wits end because I'm not used to not being able to solve my own problems I guess so any help at all or just even a heading in the right direction would be so much appreciated that I don't even know how to call it quantify it thank you
By the way I seldom post or even post questions but when I do I always pretty much say the same thing you guys are the best this is the one place I can come for Andrew Android advice or or guidance and I just I absolutely trust what I read so thank you thank you thank you thanks for being there
Edit - I'm so tired I forgot the first time I went to reflash the ROM it told me that my 3T was in fact not a 3T that it was a three and I read someplace so I'm XDA that that's just Corruption of the install script so I downloaded it again I ran 7-Zip it said it was coherent so I flash it again if that's important but thanks again
Help required
kunal1540 said:
it's normal if it bootloops once or twice
but if it's more than that then it's problematic
so which one is it
another thing you can try is try magisk root instead of supersu and see if gets the same result
Click to expand...
Click to collapse
sir, i have oneplus 3t a3010. Last night my phone was crashed and after crashing it restarts and jumps to recovery mode. In recovery mode i wipe all data and restart my phone. But i still doing the restart thing. Please help, what to do now.
Plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
My oneplus 3 is stuck in recovery mode
My bootloader is locked
Everytime i switch on my phone there is a message
Which is on photo below
Hi, well it looks like i have probably hard bricked my phone. After updating to nougat i decided to do afresh clean install. I wanted my phone to as if i had just bought it and came with nougat/emui 5 installed. So i did a factory reset from within the settings menu. But then i thought i would completely erase everything and start from the latest build before nougat, so emui 4.1.2/ marshmallow. So after wiping all the partitions in twrp and then doing a volume up + power to do complete factory wipe followed by using the three button method to install the B130 UPDATE.APP in dload folder on my sdcard, all worked as expected. The update completed at 100% and then rebooted. So there i am waiting for my phone to boot to start the setup process as i have done dozens of times before...BUT...my phone will not boot to the initial setup wizard. It just stays stuck on the Honor logo pulsing animation for ever and ever and ever!!!!!!
So i do the volume up + power button to get to stock recovery and do factory wipe and cache wipe as well. It works as expected so i reboot and once again use the 3 button method to install the update.app on my sdcard. That works as expected and at 100% says its succeeded and reboots. Once again i wait for it to boot to the initial setup wizard but....ALAS...it stays on that DAMN pulsing Honor logo. Ive tried rebooting it several times, redoing the factory wipe and install several times, but nothing. Ive gone into fastboot mode (volume down + power) to try and flash the boot.img and system.img ive extracted from update.app but get the error message -- remote: command failed -- and the same if i try to unlock bootloader. Obviously its not going to work because my bootloader isnt unlocked and nor can i got in to developer settings to enable oem unlock and turn USB debugging on because my phone wont boot past that bloody honor logo.
The only thing i havent done yet is to use eRecovery but i dont have broadband and i doesnt seem to work over public wifi! So i will go to my friends tomorrow and use their broadband and hopefullly eRecovery will download/restore the latest firmware. The only other thing i can think of is to download the original nem-l51c432B102 that came with my phone when bought, extract the update.app file and replace the B130 i have on my sdcard dload folder at present.
Sorry for such a long post but i wanted to expalin evrything in detail to hopefully resolve my problem without going backwards and forwards with questions and answers and taking for ever.
So ANYONE and EVERYONE who managed to read the whole post, if you have even the slightest idea of how to get my phone working, please oh please share it with me. Also my phone is still under warranty so if i needed to send it to a huawei centre to get it fixed would they do it and do it for free??? because eseentialy all i did was a factory wipe/reset and install a frmware and it goes KAPUT!! thats not my fault right????!!???
Thank you to one and all for any wisdom you can share. :crying::crying:
iantechie1979 said:
Hi, well it looks like i have probably hard bricked my phone. After updating to nougat i decided to do afresh clean install. I wanted my phone to as if i had just bought it and came with nougat/emui 5 installed. So i did a factory reset from within the settings menu. But then i thought i would completely erase everything and start from the latest build before nougat, so emui 4.1.2/ marshmallow. So after wiping all the partitions in twrp and then doing a volume up + power to do complete factory wipe followed by using the three button method to install the B130 UPDATE.APP in dload folder on my sdcard, all worked as expected. The update completed at 100% and then rebooted. So there i am waiting for my phone to boot to start the setup process as i have done dozens of times before...BUT...my phone will not boot to the initial setup wizard. It just stays stuck on the Honor logo pulsing animation for ever and ever and ever!!!!!! So i do the volume up + power button to get to stock recovery and do factory wipe and cache wipe as well. It works as expected so i reboot and once again use the 3 button method to install the update.app on my sdcard. That works as expected and at 100% says its succeeded and reboots. Once again i wait for it to boot to the initial setup wizard but....ALAS...it stays on that DAMN pulsing Honor logo. Ive tried rebooting it several times, redoing the factory wipe and install several times, but nothing. Ive gone into fastboot mode (volume down + power) to try and flash the boot.img and system.img ive extracted from update.app but get the error message -- remote: command failed -- and the same if i try to unlock bootloader. Obviously its not going to work because my bootloader isnt unlocked and nor can i got in to developer settings to enable oem unlock and turn USB debugging on because my phone wont boot past that bloody honor logo. The only thing i havent done yet is to use eRecovery but i dont have broadband and i doesnt seem to work over public wifi! So i will go to my friends tomorrow and use their broadband and hopefullly eRecovery will download/restore the latest firmware. The only other thing i can think of is to download the original nem-l51c432B102 that came with my phone when bought, extract the update.app file and replace the B130 i have on my sdcard dload folder at present.
Sorry for such a long post but i wanted to expalin evrything in detail to hopefully resolve my problem without going backwards and forwards with questions and answers and taking for ever.
So ANYONE and EVERYONE who managed to read the whole post, if you have even the slightest idea of how to get my phone working, please oh please share it with me. Also my phone is still under warranty so if i needed to send it to a huawei centre to get it fixed would they do it and do it for free??? because eseentialy all i did was a factory wipe/reset and install a frmware and it goes KAPUT!! thats not my fault right????!!???
Thank you to one and all for any wisdom you can share. :crying::crying:
Click to expand...
Click to collapse
Can you please edit your post ? Add some space, here and there if you want some help... It is nothing but pain for both eyes and mind to read you.
Onto related topic, did you manage to get your phone back to a functionnal state ? Note that the boot sequence can take time after a wipe so maybe it's not broken at all.
As for eRecovery, it never helped me to restore my device, tried on two different Wi-Fi networks after two completely unrelated issues.
Concerning warranty, I guess it depends on your country and where you bought your phone. I went to the carrier which provided me mine this morning since I ended up with a strong brick last night and I'll get a new phone in a couple of weeks.
Zarou said:
Can you please edit your post ? Add some space, here and there if you want some help... It is nothing but pain for both eyes and mind to read you.
Onto related topic, did you manage to get your phone back to a functionnal state ? Note that the boot sequence can take time after a wipe so maybe it's not broken at all.
As for eRecovery, it never helped me to restore my device, tried on two different Wi-Fi networks after two completely unrelated issues.
Concerning warranty, I guess it depends on your country and where you bought your phone. I went to the carrier which provided me mine this morning since I ended up with a strong brick last night and I'll get a new phone in a couple of weeks.
Click to expand...
Click to collapse
finally a reply! okay so ill edit my post once ive finished replying to you. First off thanks for taking your time to read my post, i am most greatfull. In response to your questions,suggestions i can tell you:
i went to my friends, connected to their broadband and attempted to use eRecovey to update/restore my device. ALAS it did not work! I tried several times and it gets to downloading package from server only to end in a FAIL.. I got home tried connecting to public wifi and doing eRecovery but it just fails. So like you I have never managed to get eRecovery to work.
As for the booting sequence, as i explained before, whether i access stock recovery and wipe cache and wipe phone it does this no problem, reboots, only to get stuck on the honor logo boot animation. The same goes for installing updatte.app with three button method. it says its installed succesfully but does not get past the honor logo boot animation. Unfortunately your suggestion that it might just take a long time to boot is not the case I have left it for hours you see and it never gets to the setup wizard :crying:
As for warranty, i am in uk, bought the phone via amazon, and it was unlocked, so not from a carrier like you. So i guess ill just have to find my nearest huawei service centre and have them look at it.
Does anyone know the procedure as far as doing this. Do i phone them or email my problem and then send my phone to them or what?? Any help is very welcome.
Thanks for your time and patience.
Please, please help...i'm desperate
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small! :good: :fingers-crossed: :angel:
iantechie1979 said:
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small! :good: :fingers-crossed: :angel:
Click to expand...
Click to collapse
How comes you have TWRP with a locked bootloader ?
Zarou said:
How comes you have TWRP with a locked bootloader ?
Click to expand...
Click to collapse
??? hi, I.m sorry, i think you must of misread some of my post. I dont blame you, it was bloody long and confusing!
I only mentioned twrp in the very beggining to run you through the steps to my never ending being stuck on honor logo boot animation. I used TWRP to wipe all partitions and format. From there i used 3 button method to install the update.app(B130) on my sd-card. this was succesfull, no errors and rebooted. I didn't expect any problems. But as i explained it never gets past boot logo.
Obviously now, twrp has gone, i am back to stock recovery and my bootloader is locked.
*I can access stock recovery to wipe cache and wipe the phone no problem and all works with no error messages.
*I can access fastboot(bootloader) but the fastboot commands are useless because my bootloader is locked once again and i cant turn on usb debugging or oem unlock in developper options....because my phone wont boot past honor logo...
*Three button method works everytime, 100% success, no errors, reboots but guess what?? IT WONT GET PAST THAT DAMN HONOR BOOT LOGO!!!!!!!!!
Ive tried everything, but NO LUCK. I came up with this idea today though--- download theB130 rollback from nougat to MarshMallow update.zip. Extract the update.app and put that in my sd-card/dload folder and do 3 button install method.
I might even do the same with the nougat B350 just to cover all bases. So i am downloading now, gonna cross my fingers and any other body parts, pray to all the gods...and hopefully i wont be a crying,sniveling,howling piece of mess by tomorrow.
UNLESS OF COURSE SOMEONE HAS THE KNOWLEDGE I SEEK AND IS WILLING TO SHARE IT :fingers-crossed:
thanks Honor-able friends....
iantechie1979 said:
??? hi, I.m sorry, i think you must of misread some of my post. I dont blame you, it was bloody long and confusing!
I only mentioned twrp in the very beggining to run you through the steps to my never ending being stuck on honor logo boot animation. I used TWRP to wipe all partitions and format. From there i used 3 button method to install the update.app(B130) on my sd-card. this was succesfull, no errors and rebooted. I didn't expect any problems. But as i explained it never gets past boot logo.
Obviously now, twrp has gone, i am back to stock recovery and my bootloader is locked.
*I can access stock recovery to wipe cache and wipe the phone no problem and all works with no error messages.
*I can access fastboot(bootloader) but the fastboot commands are useless because my bootloader is locked once again and i cant turn on usb debugging or oem unlock in developper options....because my phone wont boot past honor logo...
*Three button method works everytime, 100% success, no errors, reboots but guess what?? IT WONT GET PAST THAT DAMN HONOR BOOT LOGO!!!!!!!!!
Ive tried everything, but NO LUCK. I came up with this idea today though--- download theB130 rollback from nougat to MarshMallow update.zip. Extract the update.app and put that in my sd-card/dload folder and do 3 button install method.
I might even do the same with the nougat B350 just to cover all bases. So i am downloading now, gonna cross my fingers and any other body parts, pray to all the gods...and hopefully i wont be a crying,sniveling,howling piece of mess by tomorrow.
UNLESS OF COURSE SOMEONE HAS THE KNOWLEDGE I SEEK AND IS WILLING TO SHARE IT :fingers-crossed:
thanks Honor-able friends....
Click to expand...
Click to collapse
OK, sorry for the misunderstanding. Yeah, try that and if this is still not working, I guess all you can do is try the same with other packages.
I am having a hell of a time rooting this phone. (Motorola Nexus 6 XT1100)
I am trying to follow this guide: https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
If anyone can offer some suggestions, they would be greatly appreciated.
I managed to get as far as unlocking the bootloader in fastboot mode.
The next step, obtaining root, is where all my problems started.
I downloaded CF Root and extracted the files, as instructed, allowed the root tool to run, (I'm using Linux, if it matters).
When the process was finished, and my phone attempted to reboot, it got stuck on the Google screen with the little lock (showing unlocked).
I allowed the phone to stay in this mode for around 30 minutes thinking it just needed time.
It never did anything. I attempted to let it try and start up again (a couple times actually) and it never goes past the Google lock screen.
I powered down the phone and restarted in fastboot mode, and attempted to run the CF Root tool again, with the same result.
I am currently stuck with only having access to fastboot.
I tried to flash a recovery and boot into that, but it won't allow that either. Perhaps this isn't even possible (YET), as it's not in the instructions to flash a recovery until after the rooting process, but I thought I would try it anyway.
I have tried flashing TWRP and Lineage recovery. No success with either, although the terminal is saying
sending 'recovery' OKAY
writing 'recovery' OKAY
But when trying to reboot recovery I get hit with
unknown reboot target recovery
Anyone know what's going on and how I can get this resolved? I just want to install a recovery and flash a custom ROM.
In that guide you can follow my journey to root starting in post# 929. I had & have had a LOT of help from my fellow XDAers. They're great & thank you all.
Thanks!
I'll check it out.
Boy, oh, boy.
I don't know what is going on.
I finally managed to get out of the bootloader screen.
I don't know what/how it worked. I downloaded Nexus Root Toolkit to a windows computer and tried the Flash Stock + Unroot option.
It keep saying waiting on device or device not detected or something ( I cant remember exactly, it was hours/many error screens ago!)
Next, I tried the option for Root + Add a Custom Recovery and directed it to where my TWRP file.
Again it acted like it was doing something. Even found my connected ADB device. Went through a couple processes, said it would need to restart a couple/few times. Everything was trucking along just fine until suddenly, it got hung up 'Waiting on device"
Not sure what happened, but all of a sudden, it could no longer find my device.
For chits and giggles, I decided to try and reboot recovery from the bootloader screen. I had attempted this many times and all it did was start back up in bootloader, BUT, this time, it actually started up in some recovery program I have never seen before. It wasn't stock and it certainly wasn't TWRP!
At this point, I hooked my device back into my computer running Linux and attempted to push TWRP, and reboot in recovery.
It worked!
Now that I had a recovery I was comfortable using, I proceeded to push my ROM.
Wanted to try Lineage with MicroG, but I am not advanced enough to go that route. I could not get a fake app store to work.
Guess I'll have to stick with what I know. I love the idea of MicroG, but it apparently doesn't work with Pure Nexus.
Anyway, just wanted to post some closure for this thread. I know the Motorola Nexus 6 is an old phone, but I like it. This is my second one. My first one, screen finally cracked and it was cheaper to just purchase a new one from Amazon than to replace the screen.