Not sure if its really bricked or not but Its all messed and wont fully boot so it doesnt have lan access anymore for ssh and adb over wifi. I have a male to male usb cable and my pc is recognizing when its plugged in but there are no device drivers installed and adb/fastboot wont recognize (no usb debugging enabled?) so it just hangs on <waiting on device> any idea how I can install devices drivers and move forward with restoring backup of the file I fuxored? Thx guys!
Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.
Havnt got that far yet myself but the way i tinker i will be there shortly .. but as a warning to others, if you are not 100% sure what you are doing, dont muck around especially if you remount /system as rw.
Playing around will be much safer once we get recovery..
Building a recovery shouldnt be too difficult.. its booting a custom recovery that will be the trick.. Jcase had allready said he has figured it out perhaps he will share now that root is out.
roustabout said:
Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.
Click to expand...
Click to collapse
Ive got fastboot connected now so it appears it was some funky unknown issue. Fastboot isnt like adb tho and the only time ive ever used it was to re-write whole img files so is that my only option or is there some way I can push stuff through fastboot? The OTA firmware links posted a few weeks back are now dead too..
You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.
Luxferro said:
You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.
Click to expand...
Click to collapse
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Im not have any luck with those links either ive even tried assigning a static public dns to make sure my opendns stuff was no longer blocking. Does anyone have an alternate link?
alwaysbless said:
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Click to expand...
Click to collapse
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.
I had a similar instance. Gained root messed around too much and got it to not boot. Amazon is sending a replacement... But if there is a way around that in the future I would love to just fix it my self.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Luxferro said:
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.
Click to expand...
Click to collapse
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.
alwaysbless said:
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.
Click to expand...
Click to collapse
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk
Luxferro said:
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Got you now. So this is def the first bricked fire tv lol. Guess ill just sit it to the side and see if someone smarter than I can figure something like this out in the future.
Have you tried fastboot boot commands? Like fastboot boot blahblahblah.img? If it is softbricked i guess it can't hurt to try rite?
I don't know if this will work or not, but if you've already tried pulling the power, pulling USB and powering on the next thing I'd try is to obtain a 1 gig or so USB drive, format it fat32 and copy the OTA update to it.
- Leave it zipped.
- Name it update.zip
- pull the plug on the FTV
- put the USB stick in
- power it on and leave it for a bit. Watch it - is the power LED going out? If so, it may doing a recovery install of the signed OTA and rebooting - many Android devices will install anything on the sdcard called Update.zip if it's there at boot time.
What you're hoping is that the USB mass storage is mounted as a possible recovery source at power on and that the OTA is isntalled via the stock recovery. If it works, great, if it doesn't, too bad.
another brick on the wall ?
Dear OP ' i think you are not the only one .
im not sure if im bricked or plain noob
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su
pm disable com.amazon.dcp" . all was good and i had an issue with audio in xbmc and in my great wisdom i did a reset to factory settings.
since then i can not register to amazon i believe because it can not accsses amazon site for verification. so im stuck in there.
i tried to SSH and through command line no device was recognized .
any assistance to this stupidity will be much appericiated
thanks yigo
Yigo said:
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su pm disable com.amazon.dcp" .
Click to expand...
Click to collapse
Afraid I can't help you, but in light of preventing other people (and me) to have the same issues:
I assume the /etc/hosts file will survive factory-resets, it's a file that probably is not restored (so immediatly removed the host-lines from mine), but wonder if the pm disable dcp will also survice a reset ? I assume not (core funcationality for amazon, likely in factory-reset group), but you never know, esp. not in the v1 versions we are running.
Anybody knows if this is the case ? I like the pm disable solution, but if this means that borking up my installation will prevent me from ever restoring it (as unable to connect to amazon), I'll have to fall back to the router-blockage solution, and would suggest other ppl to do that as well
Deregistering AFTV may help with registration issue.
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
To de-register your Fire TV-
1 - log on to your amazon account
2 - Hold the mouse over where it says 'Your Account" but do not click. You will get a list of options.
3 - Click "Manage Your Content and Devices"
4 - Click the center tab "Your Devices"
5 - Click on your Fire TV.
6 - Click "Deregister" right below your Fire TV.
You will ge a message saying it there may be a delay for it to take effect.
[email protected] said:
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
Click to expand...
Click to collapse
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Still Learning - Passing it on.
JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I read your other posting about update blocking.
Seems I did not have my amazon.dcp disabled.
I was not in SU mode when executing command and amazon.dcp was just killed not disabled.
Sorry for any confusion. Thanks
JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I hope one of the folks with a softbricked device gets a chance to see what happens with the over the air update file copied to a fat32 formatted USB stick and renamed update.zip.
With luck, at power on if there is media present, the stock recovery is looking to removable media to see if there's a file named update.zip it can process.
I don't want to softbrick mine to test, though.
So if I am understanding correctly, you should enable updates before you factory reset?
Related
I noticed that the screenshot for recovery mode (accessed by following steps here) has an option to "Update from ADB". I assume this would use ADB sideload. However, since the FTV doesn't have an accessible USB client port, I'm not sure how or if this would work (unless Amazon built network drivers into the recovery partition).
Has anyone tested this out? Basically, just seeing if you can get ADB access while in Recovery mode. If it is possible, this may be a viable route for downgrading from un-rootable firmware releases.
elmerohueso said:
I noticed that the screenshot for recovery mode (accessed by following steps here) has an option to "Update from ADB". I assume this would use ADB sideload. However, since the FTV doesn't have an accessible USB client port, I'm not sure how or if this would work (unless Amazon built network drivers into the recovery partition).
Has anyone tested this out? Basically, just seeing if you can get ADB access while in Recovery mode. If it is possible, this may be a viable route for downgrading from un-rootable firmware releases.
Click to expand...
Click to collapse
It's part of stock android recovery. No network drivers and no working ADB over USB.
rbox said:
It's part of stock android recovery. No network drivers and no working ADB over USB.
Click to expand...
Click to collapse
If we theoretically got ADB over USB working, would that stock android recovery prompt install the update.bin files?
Since fastboot over USB works, it may not be too difficult to get ADB over USB to work if the device is already rooted. It wouldn't help anyone with rooting blocked or with a bricked device, but it would be a good downgrade method for anyone who accidentally updates (assuming the modifications made to achieve ADB over USB survive an update).
Thoughts?
rbox said:
It's part of stock android recovery. No network drivers and no working ADB over USB.
Click to expand...
Click to collapse
Amazon has to have provided a way, if for no one but themselves, to access the device via recovery. And it seems like any solution that involved opening the case to get direct access would require an unnecessary amount of work for them.
Even AppleTV allowed DFU access via USB
AFTVnews.com said:
If we theoretically got ADB over USB working, would that stock android recovery prompt install the update.bin files?
Since fastboot over USB works, it may not be too difficult to get ADB over USB to work if the device is already rooted. It wouldn't help anyone with rooting blocked or with a bricked device, but it would be a good downgrade method for anyone who accidentally updates (assuming the modifications made to achieve ADB over USB survive an update).
Thoughts?
Click to expand...
Click to collapse
Unfortunately with a locked bootloader there is no theoretically. I've spent many days screwing around with the kernel code trying to get it to go into USB client mode without much success. So if I can't do while updating the kernel, it's definitely not possible without changing code. I have no clue what's causing it to not work. It's just the stock CAF msm otg driver. I've tried forcing it into client mode and it just gets hung in the USB statemachine.
elmerohueso said:
Amazon has to have provided a way, if for no one but themselves, to access the device via recovery. And it seems like any solution that involved opening the case to get direct access would require an unnecessary amount of work for them.
Even AppleTV allowed DFU access via USB
Click to expand...
Click to collapse
I would guess that they work with unlocked bootloaders, so they can use fastboot to flash updates all day long.
AFTVnews.com said:
I would guess that they work with unlocked bootloaders, so they can use fastboot to flash updates all day long.
Click to expand...
Click to collapse
So I was finally able to get ADB over USB working. Unfortunately it requires tweaking the kernel, so it doesn't really help anyone right now.
rbox said:
So I was finally able to get ADB over USB working. Unfortunately it requires tweaking the kernel, so it doesn't really help anyone right now.
Click to expand...
Click to collapse
Regardless, that's pretty cool. Any progress, even if not too useful right now, is great.
I followed the AFTV guide to a T. Flashed 51.1.4.0, had the boot menu, CWM and everything was golden. Pushed 51.1.5.3 to the SD, rebooted to CWM, flashed, now stuck in a loop. I cant even connect to it with the adb connect command. Am I screwed? Is this thing done? I dont understand. It doesnt even show the boot menu anymore. Just straight to the looping firetv logo. Was i supposed to reflash the boot menu after installing prerooted 51.1.4.0? This sucks if it's done for.....
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Calibaan said:
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Click to expand...
Click to collapse
Thanks man. Hopefully one of those methods works. I've been at this for 4 hours carefully working my way through every single step. The highest high of the one last flash to go, turning into the gut wrenching sickness of a boot loop is too much for tonight and I'll try tomorrow.
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
supremekizzle said:
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
Click to expand...
Click to collapse
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
AFTVnews.com said:
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
Click to expand...
Click to collapse
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
supremekizzle said:
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
Click to expand...
Click to collapse
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
AFTVnews.com said:
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
Click to expand...
Click to collapse
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
supremekizzle said:
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
Click to expand...
Click to collapse
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
AFTVnews.com said:
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
Click to expand...
Click to collapse
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
supremekizzle said:
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
Click to expand...
Click to collapse
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
supremekizzle said:
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
Click to expand...
Click to collapse
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
AFTVnews.com said:
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
Click to expand...
Click to collapse
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
supremekizzle said:
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
Click to expand...
Click to collapse
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
Any suggestions?:
http://forum.xda-developers.com/fire-tv/help/fire-tv-boots-white-amazon-logo-screen-t3139511
supremekizzle,
Glad it worked out for you.:good:
supremekizzle said:
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
Click to expand...
Click to collapse
Glad it all worked out and glad I could help!
For future reference, when you edit a post, it doesn;t trigger XDA to send out a notification to the user you're quoting (me). That's why I didn't respond to your last message until now (when I manually checked it). Post a reply and use the '@' symbol (like this: @supremekizzle ) to ensure the user gets notified.
I just see black screen with fire tv now. It doesn't show up when I type adb devices anymore. I was running commands on it left and right. I was able to unlock bootloader after hardware mode then was trying to install a custom rom ??? The command I know was something like abcde .......wipe/ system ._. Yea I know. Tried to do the hardware mod again but not picking it up. Is it gone ?
tune345 said:
I just see black screen with fire tv now. It doesn't show up when I type adb devices anymore. I was running commands on it left and right. I was able to unlock bootloader after hardware mode then was trying to install a custom rom ??? The command I know was something like abcde .......wipe/ system ._. Yea I know. Tried to do the hardware mod again but not picking it up. Is it gone ?
Click to expand...
Click to collapse
TWRP is still there when you restart/boot the stick? (you have to use OTG y cable + mouse in order to check that).
If TWRP is still there, then you can use it to restore a full stock rom or flash the system image.
tune345 said:
I just see black screen with fire tv now. It doesn't show up when I type adb devices anymore. I was running commands on it left and right. I was able to unlock bootloader after hardware mode then was trying to install a custom rom ??? The command I know was something like abcde .......wipe/ system ._. Yea I know. Tried to do the hardware mod again but not picking it up. Is it gone ?
Click to expand...
Click to collapse
What custom rom (there isn't one available for the 4k)? From a linux install try a lsusb and see if anything is there (preloader or phone). When you were running commands, were you in the hacked fastboot? As @Pretoriano80 said, get in into twrp and flash, here is a link to the latest to flash to restore, but hopefully you made a backup for you started.
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777
Pretoriano80 said:
TWRP is still there when you restart/boot the stick? (you have to use OTG y cable + mouse in order to check that).
If TWRP is still there, then you can use it to restore a full stock rom or flash the system image.
Click to expand...
Click to collapse
TWRP was there but after performing /systemwipe i just see that black screen with firetv logo on the screen it skips the TWRP :/ nothing shows up when i type in adb devices (Minimal ADB and Fastboot) like before it would give a serial number and connected status. nothing in adblink either.
i did ordered that cable like 1 month ago it's not here yet. I might ordered another one today from amazon. I was wondering isn't there any software which can turn laptop keyboard to firestick keyboard from some commands? Adb link has remote which i can use ONCE it's inside the fireOS. A physical keyboard with OTG cable is must for this ? Any alternative ?
and i did search all the first 3 pages of the forum to find the stock rom for 4k firestick but couldn't may be because its was 3 am lol
Thanks for the reply!
Michajin said:
What custom rom (there isn't one available for the 4k)? From a linux install try a lsusb and see if anything is there (preloader or phone). When you were running commands, were you in the hacked fastboot? As @Pretoriano80 said, get in into twrp and flash, here is a link to the latest to flash to restore, but hopefully you made a backup for you started.
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777
Click to expand...
Click to collapse
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?
tune345 said:
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?
Click to expand...
Click to collapse
Why you installed tank rom in mantis...
Redo kamakiri and flash prerooted.
tune345 said:
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?
Click to expand...
Click to collapse
Sounds like you unlocked. Did you make it to twrp?
Lsusb is a Linux command in terminal that will show what is connected. This will tell what mode it is in. I broke a chip off one of mine too (tweezers were a bad thought), but that was 7 months ago missing it and it still runs like the rest of mine sticks. The 4k is called mantis, tank is the fire stick2. Totally different.
---------- Post added at 02:30 PM ---------- Previous post was at 02:26 PM ----------
tune345 said:
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?
Click to expand...
Click to collapse
Rortiz2 said:
Why you installed tank rom in mantis...
Redo kamakiri and flash prerooted.
Click to expand...
Click to collapse
You never know how deep the water is until you jump head first. I admire people who try!
Rortiz2 said:
Why you installed tank rom in mantis...
Click to expand...
Click to collapse
¯\_(ツ)_/¯
Rortiz2 said:
Redo kamakiri and flash prerooted.
Click to expand...
Click to collapse
I just literally just did that process again after like 7th try but it's still the same not showing up anywhere and black screen with firetv logo. Attaching the picture of the final process, does that mean it's good? it doesn't look like the first process ending.
Thanks !
tune345 said:
¯\_(ツ)_/¯
I just literally just did that process again after like 7th try but it's still the same not showing up anywhere and black screen with firetv logo. Attaching the picture of the final process, does that mean it's good? it doesn't look like the first process ending.
Thanks !
Click to expand...
Click to collapse
That shows you an obvious error in the fastboot step.
Try using a different cable and be sure to do the process from an 2.0 Port.
Since the bootROM part is already done, just type:
Code:
sudo ./boot-fastboot.sh
Connect the stick WITHOUT SHORT ANYTHING and the script will ask to the Preloader to boot to Hacked Fastboot Mode.
When you see "Hacked Fastboot Mode" in the screen of the device, try running fastboot-step.sh again.
Rortiz2 said:
That shows you an obvious error in the fastboot step.
Try using a different cable and be sure to do the process from an 2.0 Port.
Since the bootROM part is already done, just type:
Code:
sudo ./boot-fastboot.sh
Connect the stick WITHOUT SHORT ANYTHING and the script will ask to the Preloader to boot to Hacked Fastboot Mode.
When you see "Hacked Fastboot Mode" in the screen of the device, try running fastboot-step.sh again.
Click to expand...
Click to collapse
sorry where am i entering that code exactly ? because that window was still open with the final error in the instructed directory and i entered that it said command not found so i connected it back to my other laptop and ran Minimal ADB and Fastboot and ran that command there...nothing..
then i went back to linux laptop and close the terminal and re opened a new one and ran that command again said command not found.
tune345 said:
sorry where am i entering that code exactly ? because that window was still open with the final error in the instructed directory and i entered that it said command not found so i connected it back to my other laptop and ran Minimal ADB and Fastboot and ran that command there...nothing..
then i went back to linux laptop and close the terminal and re opened a new one and ran that command again said command not found.
Click to expand...
Click to collapse
You have unlocked and flashed recovery. Do you have a OTG (google if if you don't)? looks like you have TWRP now...
Michajin said:
You have unlocked and flashed recovery. Do you have a OTG (google if if you don't)? looks like you have TWRP now...
Click to expand...
Click to collapse
i have ordered last month, still not here yet. Might order another one from amazon today. isn't there any software which can convert laptop keyboard temporarily for firestick?
and this might be thinking too oddly but lets say i have a micro usb to usb adapter after i plug that in firestick can i take a usb to usb cable and plug it into usb hub? and then plug keyboard mouse usb drive in it ....all going to firestick via usb to usb cable finally converting the signal from usb to usb micro adapter. i believe i have a usb hub which can be powered...
X_X
tune345 said:
i have ordered last month, still not here yet. Might order another one from amazon today. isn't there any software which can convert laptop keyboard temporarily for firestick?
and this might be thinking too oddly but lets say i have a micro usb to usb adapter after i plug that in firestick can i take a usb to usb cable and plug it into usb hub? and then plug keyboard mouse usb drive in it ....all going to firestick via usb to usb cable finally converting the signal from usb to usb micro adapter. i believe i have a usb hub which can be powered... _X
Click to expand...
Click to collapse
No, it has to be a otg. On boot, it will detect it and automatically give you the option for recovery. If you can get into fastboot (you were there before when you ran fastboot.sh you might be able to boot into recovery with fastboot reboot recovery or something simalar. But being in recovery you wont be able to do much unless you have adb connections, or a mouse/keyboard with OTG. Amazon is basically shipping a week for everything right now. I think you really need a OTG to pull it out. ADB and fastboot commands can really screw things up from my novice experience. Get that OTG and try it. I will warn, get one that says it will work for the firestick4k, they dont all work....Make you you give a thanks to the people trying to help, no one is getting paid here...
Michajin said:
No, it has to be a otg. On boot, it will detect it and automatically give you the option for recovery. If you can get into fastboot (you were there before when you ran fastboot.sh you might be able to boot into recovery with fastboot reboot recovery or something simalar. But being in recovery you wont be able to do much unless you have adb connections, or a mouse/keyboard with OTG. Amazon is basically shipping a week for everything right now. I think you really need a OTG to pull it out. ADB and fastboot commands can really screw things up from my novice experience. Get that OTG and try it. I will warn, get one that says it will work for the firestick4k, they dont all work....Make you you give a thanks to the people trying to help, no one is getting paid here...
Click to expand...
Click to collapse
Thank you for that information. Appreciate it. Yea everything is late on amazon now even prime :/ but hopefully i find one which works on the first try otherwise it would be a super bumber...
..but then again how would i know if it's the otg NOT working OR the firestick software/hardware? i did broke one capacitor and was running commands on it like a mad man lol , i believe the CLK one on the picture. what it is for ? why was the firestick still working almost normally after i broke it ? attaching the picture
Thanks again !
tune345 said:
Thank you for that information. Appreciate it. Yea everything is late on amazon now even prime :/ but hopefully i find one which works on the first try otherwise it would be a super bumber...
..but then again how would i know if it's the otg NOT working OR the firestick software/hardware? i did broke one capacitor and was running commands on it like a mad man lol , i believe the CLK one on the picture. what it is for ? why was the firestick still working almost normally after i broke it ? attaching the picture
Thanks again !
Click to expand...
Click to collapse
There are some that say they work. The ones i have had issues with are the OTG hubs. Depending on which chip was damaged, but i broke one off of mine too about 7 months ago (tweezers are bad) but it has been working the same as the rest of mine. could be a heat thing?
Aaahhhhh hit that virus with a brick because i was able to finally fix my firestick last night, pheww!!
thank you everyone for helping
now i need to research the fastest way to clone my ENTIRE setup. I rooted it.
tune345 said:
Aaahhhhh hit that virus with a brick because i was able to finally fix my firestick last night, pheww!!
thank you everyone for helping
now i need to research the fastest way to clone my ENTIRE setup. I rooted it.
Click to expand...
Click to collapse
I have a similar problem with my firestick, How did you manage to fix yours?
Had to do the hardware mode multiple times until i landed at TWRP screen then used adb to flash the stock rom
tinybilbo said:
I have a similar problem with my firestick, How did you manage to fix yours?
Click to expand...
Click to collapse
Were you unlocked? Unless you were playing with recovery, If you have a OTG plugged in from a power off state you should get a recovery option.
Michajin said:
Were you unlocked? Unless you were playing with recovery, If you have a OTG plugged in from a power off state you should get a recovery option.
Click to expand...
Click to collapse
Hi Michajin (Thanks for the reply)
Yes I have an unlocked bootloader, TWRP, and was rooted.
I can get into TWRP via OTG, but it doesn't matter what I flash (Stock or Pre-Rooted), all I get is a black screen (I've left it overnight just to be sure).
I was thinking maybe I should try to flash directly from bootloader rather than TWRP, or making a backup from my other firestick and trying that (the data partition at least).
Either way I'll have to do a little more research first, so any thoughts would be greatly appreciated....
Hey guys, so I used googles flash tool to update December patch and it keeps failing at writing to phone 1 of 11.
It's now in a bootloop but can access fastboot.
Ive tried to completely reset the phone manually using adb but it fails. It just doesn't work and aborts basically the phone rejects all data transmission.
What am I doing wrong or can I get a more detailed way to reset the phone completely.
-Edit-
I was also rooted and was following the guide for rooted December 12.
The main error is
(Error reading sparse file)
Why did you use the flash tool? General recommendation is, as long as you're running stock, just use the full OTA packages.
For the flash tool to be usable you need to OEM unlock your phone (while it's in a working state!).
If you can access fastboot you should be able to access recovery as well, where you can flash the full OTA, which should fix your issue.
fonix232 said:
Why did you use the flash tool? General recommendation is, as long as you're running stock, just use the full OTA packages.
For the flash tool to be usable you need to OEM unlock your phone (while it's in a working state!).
If you can access fastboot you should be able to access recovery as well, where you can flash the full OTA, which should fix your issue.
Click to expand...
Click to collapse
Because I'm rooted and recovery doesn't work.
I should have just done it manually instead of the flash tool method published here.
I just don't get why the system image isn't flashing now, the bootloader and radio flash work, but not the actual update. It's the correct version and all.
If the online flash tool isn't working for you, download the factory image from google's website and use the flash-all.bat to flash the device. Ensure that you modify the flash-all.bat file to not wipe data before running. This can be done by modifying one line in the file. Which is the following:
Code:
fastboot -w update image-raven-....zip
to
Code:
fastboot update --disable-verity --disable-verification image-raven-....zip
When flashing ensure that phone is in bootloader first.
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
So i got a lil problem. i updated the pixel 6 pro to december update but upon booting up it says your phone is corrupted and sits at the google bootup screen. i can still use fastboot and whatnot but every img i tried i get the same message and it sits again?
holla420 said:
So i got a lil problem. i updated the pixel 6 pro to december update but upon booting up it says your phone is corrupted and sits at the google bootup screen. i can still use fastboot and whatnot but every img i tried i get the same message and it sits again?
Click to expand...
Click to collapse
edit---
first try this method that was posted - sometimes you can save your phone this way. if that doesn't work: you can download the factory image and remove the "-w" command in the flash-all.bat file (save it properly) - this will prevent wiping your phone. you'll need adb/fastboot tool and drivers. if you need help with this just reply.
if that doesn't work, you can go this route (but it will wipe your phone) you can use the "flash" link on the factory image page here. if you press the "flash" link in blue, it will take you to the correct build at flash.android.com (click on the build version 12.0.0 (SD1A.210817.037, Nov 2021) - that's the one that worked for me.
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
holla420 said:
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
Click to expand...
Click to collapse
What method did you use to update? Are you rooted? If so, what version of Magisk did you use?
V0latyle said:
What method did you use to update? Are you rooted? If so, what version of Magisk did you use?
Click to expand...
Click to collapse
no root, just unlocked bootloader i manually installed using adb
holla420 said:
no root, just unlocked bootloader i manually installed using adb
Click to expand...
Click to collapse
Use the Android Flash Tool to flash the latest December update. Don't check any of the boxes.
ayye thanks this method worked
holla420 said:
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
Click to expand...
Click to collapse
You'll always get this message upon reboot once the bootloader is unlock.
It's normal, and you can disregard it entirely (unless you want the absolutely most secure device possible, then you should lock the bootloader, and this message will go away)
Az Biker said:
You'll always get this message upon reboot once the bootloader is unlock.
It's normal, and you can disregard it entirely (unless you want the absolutely most secure device possible, then you should lock the bootloader, and this message will go away)
Click to expand...
Click to collapse
oh i know but this was a different message. it was in red and wouldnt boot pass the bootup screen,
coilbio said:
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
Click to expand...
Click to collapse
sounds like a user error; if it's fixed you might want to update your first post with solutions in case others have similar issues.
coilbio said:
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
Click to expand...
Click to collapse
There are definitely better and worse USB-C cables. I've successfully fully flashed my P6P connected to a powered USB-A (3.2 Gen 2) Hub in one room through a USB extension cable 10-15 feet from my computer in another room. The hub and the extension cable are reasonably "robust", and I've found them reliable, but they're not particularly reputable name brands by any means. The USB-A -> USB-C cable I have connected to that hub is from my old HTC 10, too.
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
mkhcb said:
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
Click to expand...
Click to collapse
Doesn't your phone have to be unlocked to use the flash tool?
The data is all backed up so it's not a problem to lose it. The problem is actually making the phone to boot past the logo... I will try that Android Flash Tool but I fear that the phone should be unlocked first
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Maybe try sideloading OTA again. Are you able to do that?
mclarence said:
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
Click to expand...
Click to collapse
McNaccken said:
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Click to expand...
Click to collapse
Unfortunately, someone else in another thread reported that the Pixel Repair site (not the Android Flash Tool) hasn't been updated for the P6P.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Lughnasadh said:
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Click to expand...
Click to collapse
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
znel52 said:
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
Click to expand...
Click to collapse
Oh crap, didn't think about that.
I know not everyone has access to a laptop but if you do always use that over a desktop. In the event of something like this you will have the battery power to carry you through.
I'm sorry this happened to you. The only option may be to send it to Google for repairs.
Sorry for your phone. I experienced this on a nexus 6 that didn't have USB debugging or OEM unlock enabled. I tried sideload, put the update package on the phone storage, try to update with Android recovery. Nothing worked. Stuff happens with phones. I hope you can get a new phone.
God bless.
Sorry to hear this. It seems that I need to open USB debugging option just in case for my Pixel 6, which finally arrived across the ocean after a month.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
Since the Repairtool has not been updated for your needs and considering that your device is not unlocked, your only option is to contact Google (/your seller). Maybe they can offer you an updated version of the tool (unlikely) or replace your device.
You just described, btw, my horror scenario when updating the BIOS of my PC. The lights going out, when doing a firmware update o.o
Oh my. I'm so sorry for you to have experienced that.
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
My apologies for asking the obvious - did you select "adb sideload" in the recovery menu ? At least I was blind enough to oversee that I need to select this option first
Can you boot into fastboot from the recovery ? If yes you could also try installing a factory image instead of the update package.... I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
I had a similar issue with applying ota updates and have seen quite a few reports of users having trouble. Not sure what the deal is, but for some reason this phone seems super finicky with updates. Are you still in the return window? You may want to reach out to Google support or one of their "authorized repair shops".
For me, I ran the flash all bat, rebooted, got a message saying my device can't be trusted. So I rebooted, wiped data, rebooted again and got the same thing. So I rebooted, ran the flash all bat file again, rebooted phone, and screen went black and it never powered on again. Suspect circuit board may have fried some how. Anyways, long story short, contacted Google and had a replacement sent out with minimal hassle.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
so you can get through this... you'll be fine. pick adb sideload and it will say waiting, then run the command.
you can also change slots at the bootloader menu or try running the unlock oem command to see if it will allow you to unlock..... not sure if you can change slots without unlocking bootloader. try different USB ports on your computer (and restart your computer just in case) along with using the latest platform tools (adb/fastboot) and USB driver directly from Google (not third party apps or websites.
download the OTA zip again (and just open and close it quickly to verify it isn't corrupt).. and also make sure you have 5-10GB of space free on your computer.
usually the boot slot is changed whenever an OTA is flashed. it will tell you what slot you're in at the bootloader menu (where it says fastboot and device state locked).
can you try holding power button (when it's not plugged in) and as soon as you see then Google logo, hold volume down. that will get you to safe mode. and as quickly as you can, enable "OEM Unlocking" - which will allow you to flash a full factory image.
sorry for this comment being all over the place. if you need help, just reply, and I'll be more methodical next time
s3axel said:
I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
Click to expand...
Click to collapse
I don't think the problem is that his bootloader is locked - it's unlocked, however, they factory reset the device which likely caused USB Debugging to be turned off, as it defaults to after a factory reset.
I'm so glad years ago I swore to use Uninterruptible Power Supplies (UPS) for all the PCs I build for myself or my wife.