Related
So yesterday I went to flash a Kernel and needless to say it didn't work. So just like my Galaxy Nexus, I held down the special key combo and got into the Bootloader, scrolled to Boot Recovery and it went to the Google screen but never went to recovery. I figured it just froze so rebooted into Bootloader and tried again, with the same result. So I tried it again to see if I could even boot normally from the Bootloader and it wouldn't even get past the Google screen doing just a normal boot.
Is anyone else having this issue? May try a full fastboot restore back to stock and re root, but I would like to know if anyone else is having this issue before I move on.
Connect your N7 to a computer via usb and then boot into bootloader and you should be able to get in. It is a known issue that you can't get into recovery unless you send a command via adb or you are connected to a pc via usb.
evonc said:
Connect your N7 to a computer via usb and then boot into bootloader and you should be able to get in. It is a known issue that you can't get into recovery unless you send a command via adb or you are connected to a pc via usb.
Click to expand...
Click to collapse
I just booted to Bootloader, fastbooted my recovery, and without rebooting had no issues just using the Boot Recovery option. Just wandering if anyone else was having this issue.
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
What happens when u choose reboot in fastboot mode in the bootloader??
cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
Can you reboot into recovery again and enter to fastboot mode?
Can go between fast boot and the Bootloader menu but if I hit reboot, it just comes back to Bootloader. If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.
cknuth said:
If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.
Click to expand...
Click to collapse
fastboot erase cache
nkk71 said:
fastboot erase cache
Click to expand...
Click to collapse
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"
cknuth said:
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"
Click to expand...
Click to collapse
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)
nkk71 said:
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)
Click to expand...
Click to collapse
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB
cknuth said:
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB
Click to expand...
Click to collapse
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...
nkk71 said:
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...
Click to expand...
Click to collapse
ok so the guide walks me up to the point of installing fastboot for unbuntu using a couple cmd lines but for my specific situation will I need any files saved in specific locations? I have never used Ubuntu or Linux before so youll have to bear with me.
Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.
cknuth said:
Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.
Click to expand...
Click to collapse
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.
nkk71 said:
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.
Click to expand...
Click to collapse
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?
cknuth said:
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?
Click to expand...
Click to collapse
doesn't sound like a brick at all, as long a hboot (ie bootloader is fine) no brick should be involved.
but i have to call it a night, hopefully someone will be along shortly, and take over... (timezones ) take it ease, DO NOT PANIC, DO NOT RUSH things!!
Cool, all your help is greatly appreciated. So I should hold off on the trip to the phone store?
Any other ideas to get communication to the phone?
Different Computer, USB Port, and USB Cable. Without saying FASTBOOT USB on the phone, can't do anything.
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
08G8V8 said:
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
Click to expand...
Click to collapse
First, Status code 3 is normal - that indicates an unlocked bootloader.
You should be able to use the 4.4.4 FXZ to flash back to 100% stock. Afterwards, you can flash TWRP, and re-root. Use the latest TWRP from here: http://techerrata.com/browse/twrp2/ghost
The important thing about TWRP is that immediately after flashing it, you have to "fastboot reboot-bootloader" and immediately boot into recovery - otherwise it doesn't 'stick'. We don't know why, but as long as you do it that way, you will be fine.
Here is the link for the 4.4.4 FXZ: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you follow the instructions, you will be on stock, rooted 4.4.4 in less than 20 minutes.
Good Luck, and let me know if you need additional assistance :good:
Also, please remember to post your questions to Q&A - not General. Don't worry as I have already requested that the Mods move it to the appropriate sub-forum.
EDIT: The problem I see with "rootjunky"s video is that first, he advises that "Status code 1" is required to flash recovery -- this is incorrect. Status code 3 works fine for custom recovery.
Additionally, he did not "fastboot reboot-bootloader" before booting into recovery. This is necessary. I'm not sure why he left that step out....likely he already had custom recovery flashed when he made the video.
Thanks for the quick response. Sorry about posting in the wrong section. I should have known better.....
I will look at this, but probably won't do it until after work tomorrow. I will post back tomorrow, hopefully with success.
Thanks!
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
08G8V8 said:
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
Click to expand...
Click to collapse
Either will work fine. If you don't care about keeping your data, you can use RSD Lite (will wipe everything). If you use one of the tools in the thread I linked you to, make absolutely sure you follow the instructions -- you can't have any spaces in any folder-names. If you use RSD Lite, you just select the zip file and flash (no worries about directory structure).
Ok, I just assumed those were the methods to flash it. I will look into the RSD Lite method, as if don't mind wiping the data.
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
08G8V8 said:
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
Click to expand...
Click to collapse
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
samwathegreat said:
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
Click to expand...
Click to collapse
Sorry, the "adb reboot bootloader" sends me into the bootloop.
I hadn't tried the "fastboot reboot bootloader" or "fastboot reboot-bootloader". Now when I try that, with USB debugging checked I just get "<waiting for device>" It does nothing.
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Travisdroidx2 said:
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
Click to expand...
Click to collapse
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
08G8V8 said:
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
Click to expand...
Click to collapse
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Once you are in the boot loader screen does "fastboot devices" recognize your device?
samwathegreat said:
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Click to expand...
Click to collapse
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
samwathegreat said:
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Click to expand...
Click to collapse
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Travisdroidx2 said:
Once you are in the boot loader screen does "fastboot devices" recognize your device?
Click to expand...
Click to collapse
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
08G8V8 said:
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Click to expand...
Click to collapse
OK, glad you didn't flash to bootloader. That is tricky to fix...but I've dealt with people who have done it before.
Try another PC...or re-install the drivers. Also, DO NOT use a usb 3.0 port, always use 2.0.
Bootloader = AP fastboot mode. They are one and the same. Try to get it recognized with "fastboot devices", on any PC. If you can get to that point, you can flash back to stock and recover everything. The FXZ can actually FIX a corrupted or damaged filesystem. It replaces all the relevant partitions.
Remember you do NOT use adb or usb debugging. They have nothing to do with fastboot.
---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------
08G8V8 said:
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
Click to expand...
Click to collapse
YES!!!!
It seems you were confusing adb and fastboot. As long as "fastboot devices" recognizes your device, SO WILL RSD LITE!!!
Now follow my initial instrucitons, and you will be up and running in no time...
Thanks guys! I am going to do this tomorrow, but I feel pretty good that it is going to work.
Yes, I got VERY confused, and definitely need to go study up some more. I thought I had it, but obviously not.
Will report back tomorrow.
Happy to help
Absolutely get the Dev Edition for the same price. While Safestrap is out for other Galaxy devices with locked bootloaders (not sure if the S5 got SS yet) it allows customs Roms....but not kernel changes. With a Dev edition, there may be less development, but I'm sure there will still be some development out there.
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
TAGTRAUM said:
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
Click to expand...
Click to collapse
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Circaflex said:
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Click to expand...
Click to collapse
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
TAGTRAUM said:
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
Click to expand...
Click to collapse
Nope.. If adb doesn't work and volume buttons are broken, you're stuck. Get the buttons repaired.
rootSU said:
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Click to expand...
Click to collapse
No luck with running this commands in boot process
TAGTRAUM said:
No luck with running this commands in boot process
Click to expand...
Click to collapse
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
Adb should work from part way through the boot process and any mode. in custom recovery.
gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
TAGTRAUM said:
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Tech said:
Try this
Click to expand...
Click to collapse
Will try, but decide to repair my Vol- button myself, i have no mind what can be broken in this part, watching video of N6 dissassembly, its pretty simple part indeed Walking w/o Vol- for a month, and this situation is frustrating me and other situations can happen, in certain cases i still need Vol- :cyclops:
I have not received the OTA update to Marshmallow yet and getting impatient so I'm attempting to sideload the update myself. I've installed the SDK and drivers. The device is listed when I use 'adb devices' at the command prompt and it allows me to boot into the bootloader. But from there it disconnects from my computer and I'm not able to push the update to the device. I get "error: device '(null)' not found". Any advice?
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Didgeridoohan said:
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Click to expand...
Click to collapse
Ok, but all the instructions I'm finding online to sideload the OTA say to type "adb sideload [the full name of the file].zip". This is after enter Recovery Mode and select "apply update from adb"
I typed "fastboot devices" and my device came up in the bootloader. I click into Recovery Mode and the computer makes the disconnect sound. That's where I'm cut off.
Have you tried unplugging and plugging in the usb again after entering recovery?
Didgeridoohan said:
Have you tried unplugging and plugging in the usb again after entering recovery?
Click to expand...
Click to collapse
I ended up trying NRT and caused even more problems at first, so I ended up just flashing the update instead of sideloading it. I was freaked out for a while because it was stuck in the boot sequence but as of right now, it's working and I have 6.0.
Yay!
ok, sideloading is for twrp recovery. but thats not needed anymore as you can just move files in and out of twrp without adb. flashing factory images is only via fastboot while you are in bootloader. adb and fastboot are different.