Database Develop

Bricked Nexus 6 please help ASAP!

I just bought a Nexus 6... Unlocked the bootloader and rooted the phone.... after realizing there were some issues with the phone I decided I would try and download the PURE rom for the phone... I installed TWRP recovery and tried to flash the image. When the phone booted back up it said that the data was corrupt, and to enter a password. Entering anything seemed to work and I would then reset the phone... but the same thing would come back up.
So I decided to try and wipe the phone again and re-install the ROM... after that it wouldn't load at all, came back with some kind of error.
Then I decided to do a full wipe of the phone and try and re-install the factory image... Problem is... I haven't tried to do anything with a phone in like 2 years and well... i'm having trouble on trying to figure out how I can restore the factory image. I have the SDK tools installed, the phone drivers are also obviously installed, but can someone help me try to reset to the factory image.
I only have like 3 hours to try and accomplish this from now because after this I have to get on a plane and won't be around and will also leave me without a phone... Can someone please help me as soon as possible? Thank you so much!! I could use somewhat detailed instructions but not crazy

http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Try nexus toolkit by wugfresh can't go wrong. If you get error missing system.img while flashing go to options then flash then click force flash. The toolkit will download all needed steps and flash without a problem

dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.

Nexus device can almost never be bricked, I say almost never because of the people variable, but if you can get it into bootloader mode it is easy to bring back. just follow the instructions above.
I agree that even though wugfresh tools is the best out there. I have used it before. You learn nothing about what needs to be completed.
I could never get the drivers to work for me in most cases. I use ubuntu and it always works running the manual commands.

Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!

jwleonhart said:
Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!
Click to expand...
Click to collapse
first thing to do in adb is run the command "adb devices" to make sure that adb sees your device, does adb see your device?

It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....

jwleonhart said:
It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....
Click to expand...
Click to collapse
wait.. you are flashing the factory img, you do not use adb for that. you boot into the bootloader then use fastboot for that. adb doesnt work in the bootloader anyways, use fastboot while youre in the bootloader, and type fastboot devices to make sure fastboot sees your device.

@simms22 is correct, tool kits make you learn nothing, and you get posts like this.
However if you are time contained. As much as it pains me to say this. Use the tool kit. And learn on a time when you can.
Download Wugs toolskit and flash back to stock images. And you'll be fine.

Update your SDK if u haven't already.
Unzip factory images and place in platform tools folder of SDK. (Unless you have environmental variables set correctly)
Open a command prompt from that directory (place cursor in empty space, hold shift and right click on mouse)
Boot into bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Sent from my Nexus 6

simms22 said:
dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.
Click to expand...
Click to collapse
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app

doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.

dparrothead1 said:
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
jwleonhart said:
doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.
Click to expand...
Click to collapse
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.

simms22 said:
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.
Click to expand...
Click to collapse
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app

dparrothead1 said:
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
with a silly post like "Different strokes for different folks!!!!" you definitely arent posting like someone your age, as thats what a child would say. im not young myself. anywho, you can not tell me not to respond, lol. ill respond to anyone who posts as silly as you. i have nothing against you, nor are trying to get at you, im simply responding to your silliness.

OP... The password was a numerical representation of your pattern unlock since you were still encrypted. The key is in the first post of the TWRP thread.
Now...extract the factory image until you have boot.img radio.img system.img and recovery.img if there is a bootloader img flash that first.
Flash bootloader with fastboot flash bootloader bootloader.img
Reboot with fastboot reboot-bootloader
Flash boot system and radio respectively with fastboot flash boot/radio/system boot.img/radio.img/system.img one at a time.
Finish with fastboot reboot and you sgould be all set.

op got it flashed, and ended up flashing his rom as well. so, he was successful

I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..

jiv101 said:
I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..
Click to expand...
Click to collapse
no, it didnt start an argument. but he ended up doing it the right way, then flashed his rom. then flashed a different rom because his rom was so so. but really, even if theres a time restraint, if your driver is installed properly, it takes about 3-4 minutes to flash the boot.img

[Q] 5.0.1 and ADB not finding device

OMG!!! I've hit the end of my rope with this. Let me start off by saying I don't post things, I find answers to them but this problem is killing me.
I have a Sprint Nexus 6 that I am trying to update to 5.0.1. However its being terrible, I reboot into bootloader with with power and volume - or adb reboot bootloader, and attempt to adb sideload (updatefile.zip) and error device not found. I do adb devices and sure enough its not there, however fastboot devices shows it. If I reboot into the OS and issue ADB devices OH **** THERE IS MY PHONE, adb reboot bootloader, and its gone again.
I've tried drivers froom google search direct google usb drivers, naked drivers 0.73, I've uninstalled inside of the os and reinstalled I've uninstalled in bootloader and reinstalled nothing works. I can issue fastboot commands but adb just eats a bag of ****. I also have an issue where adb gives an error that it is out of date and must restart, it then restarts and everything is peachy. I've tried to download something called adb fix, but it says there is nothing wrong. So I have no idea what is going on and if anyone could possibly help me get my phone updated so this notification goes away and I don't go into an OCD rage on everyone around me I would be much appreciative.
Side note
I cannot update via ota, no idea why it says installing then just errors out, I assumed it was because of the unlock, also when I'm in bootloader and I attempt to go into recovery there is just an android dude with his chest open. Now its been a while since I've had a nexus but shouldn't there be like a menu or something there? I also did the whole no encrypt boot.img nonsense here. I thought that was the problem so wiped data and flashed the stock boot.img... I'm seriously out of ideas......

well first off you have the stock recovery... that is the android dude.
I dont really have answers for you but the two things i would try would be a different computer and just using WUG http://www.wugfresh.com/nrt/ i have had issues in the past using an old ADB/fastboot.
If you have modified anything the OTA is going to fail.

Tried on two different computers,I'll try wug. Thanks

first, make sure that you can see the device when it's booted up (assuming usb debug is enabled and the computer is trusted).
other than that, i'm not sure what to say as i've never had that problem (i don't use the updater.zip files though). might be best to just flash the whole 5.0.1 image (minus the cache and userdata).

Maybe I am reading this wrong, but you are trying to adb while in the bootloader?

PaisanNYC said:
Maybe I am reading this wrong, but you are trying to adb while in the bootloader?
Click to expand...
Click to collapse
If you're reading it wrong so am I. Definitely sounds like he is incorrectly trying to use Adb in the bootloader.
---------- Post added at 11:15 PM ---------- Previous post was at 11:13 PM ----------
Lucke said:
first, make sure that you can see the device when it's booted up (assuming usb debug is enabled and the computer is trusted).
other than that, i'm not sure what to say as i've never had that problem (i don't use the updater.zip files though). might be best to just flash the whole 5.0.1 image (minus the cache and userdata).
Click to expand...
Click to collapse
USB debug mode has nothing to do with boot loader or recovery. I'm sure you know this as you said it when booted, but many will read this and think you need debug in recovery or bootloader which wouldn't be true.

Deleted the whole os

I recently formatted everything on my nexus 6 and I mean everything, the OS too. And I can't fix it, there was nothing on the forums or threads about this and how to fix it. Could you please help me?

Boot into the boatloader and flash the fastboot image.
Sent from my DROID Turbo 2

I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!

Big-Blunt said:
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Click to expand...
Click to collapse
you cant use the flash-all, you need to flash each part separately. ynzip the file, then flash each .img file sepately. btw, ive deleted the whole os before. if you already have twrp installed, it wouls be a much easier fix using twrp instead.

How do I unzip the file in the boot loader?

Big-Blunt said:
How do I unzip the file in the boot loader?
Click to expand...
Click to collapse
i dont remember the program i used on my laptop, maybe 7zip.

The file downloaded from Google has a second zip inside. Unzip twice with 7 zip. The system image is inside the embedded zip file.
I assume you have the SDK from Google... Place all image files in the platform tools folder. I rename the images boot, radio, system, etc. to simplify typing the commands when actually flashing the images. DO NOT add the, " .IMG" when renaming.
Then:
Fastboot flash bootloader bootloader.IMG
Fastboot reboot-boitloader
Then same for system, radio, data and cache with out the reboot line.
When all files are flashed then fastboot reboot and enjoy

My brains are exploding rn, idk what or how to do anything, maybe u will think I'm dumb but I don't know what u guys are saying, could anyone post full instructions on how I would do it

The ONLY thing that you need to revive your device is alive bootloader. Every OS has its bootloader, and it determines what to load before system loaded.
I guess you did that foolish things on recovery. Then it won't kill itself of bootloader for sure.
Then there's always a chance. Try to boot into bootloader and switch it to fastboot mode.
Just flash stock rom image provided by google as described above.

You need to do some googling about fastboot and/or look for the beginners guide posted in the forums. You could use wugsfresh toolkit as well. I'm not being a douche not linking them,I'm to stoned
Google anything you don't understand
Sent from my Nexus 6 using Tapatalk

Do you know if your bootloader is unlocked?
You say you're an Apple guy - are you using a Mac? If you have access to a Windows machine I suggest you install Wugfresh's Nexus Root Toolkit and use the "Install & test drivers" button to set up the required drivers to connect your Nexus 6 to the computer. The walkthrough is comprehensive and extraordinarily simple - brilliant piece of programming. There is no Mac version.
Download the factory image (https://developers.google.com/android/nexus/images?hl=en#shamu image MMB29K).
Find the Fastboot/ADB programs on the web (I may have used the Minimal ADB & Fastboot tool, I can't remember exactly) and create a directory containing both programs plus their associated bits and pieces. I recommend making the path as simple as possible - e.g. C:\ADB for ease of navigation ( see below).
(While reading up on this, I came across this, which you may find useful - http://www.android.gs/install-set-up-adb-mac-os-x-linux/).
Unzip everything in the factory image, including the zip inside the zip as Larzzzz82 said, then copy the unzipped *.img files into the ADB Fastboot directory.
Boot your N6 into bootloader.
Open a CMD window and navigate to the ADB directory.
To check that you're connected, type (you don't need caps, this is just to make it clearer) FASTBOOT DEVICES. You should see something like "djdgkdjhgkdfj device" in response; if it's blank you're not connected - go through the driver setup again to see what you've missed.
Once you're successfully connected, you can install your new image following the instructions in this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
I did ask for an expert to run a more experienced eye over them to correct any errors or to remove any pointless reboot commands, but nobody did either, so I guess they're ok. It's what I did and it worked for me. I've just noticed that it includes a line "fastboot flash recovery twrp.img" which you can ignore for the moment - though you may want to do this later when you have a working device.
Come back if you want any clarifications.
Happy new year (and, I hope, device...)

I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,

Big-Blunt said:
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Click to expand...
Click to collapse
No no no you do not flash images through the recovery

Use Wugfresh's Nexus root and toolkit to restore it. Pretty easy.

@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.

dahawthorne said:
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
Click to expand...
Click to collapse
That's OK if people disagree with my recommendation. People are entitled to their opinions.
I tried for hours to do it the manual way and could never get it to work. And I'm a person who is VERY tech savvy. I had a computer repair business and have written advanced linux tutorials. I gave up and started using wugfresh. Has worked great for me. Others are free to do what works for them.

If you dont flash the images through the recovery mode then how do you flash it? I cant flash through command because the phone dosent have usb debugging enabled and its not in developer mode. I tried the nexus root toolkit as well and that didnt work either. Plz i need help!

So how much of my instruction did you follow? What exactly have you tried? Step by step. If you're vague then we can't help you. Error messages?

How did you delete the OS if your phone isn't unlocked?
Sent from my DROID Turbo 2

So i put it in recovery mode and when i tried resetting to factory i accidentally clicked advanced wipe and deleted everything so now its stuck in the boot loop. What i have tried was i downloaded the img file 6.0 shamu from googles site and drag and dropped on internal memory with my pc. Then in recovery mode i went mount and selected the img and it said error.

Inexperienced and messed up big time

I heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.

mikeos89 said:
I heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.
Click to expand...
Click to collapse
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.

mikeprius said:
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.
Click to expand...
Click to collapse
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.

Can't you just drag and drop a ROM and gapps while in twrp... Ive.done it before...good luck

Not likely as the phone plugged into the computer may not read it as a "USB" drive. I have windows and I have no idea what the command prompts are for Mac. Also if your understanding is virtually nothing, you need at least understand the basics of fastboot and custom recovery in order to fix your situation.
The good news is that your phone isn't messed up. The bad news is you need to roll up your sleeves and learn the basics of how the commands work so you can reboot the phone back. Everyone here can describe to you what to do but since you don't know the fundamentals it won't mean anything until you do. Sorry.
Btw, jailbreaking isn't the Apple version of "root". They are 2 completely different things.
What I would do is fastboot erase TWRP and re-flash it as it sounds like you are having problems, then adb pull a custom ROM into your internal storage. Reboot into TWRP and flash it. That's what you need to do.

mikeos89 said:
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.
Click to expand...
Click to collapse
I don't know anything about flashing a phone from a Mac but if you can boot your phone into bootloader mode and get fastboot to work on the Mac I would follow the steps under Step 5, Method 2 at http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I use that method to upgrade my phone every time a new ROM comes out and it works great.
Note:
1. You this will get you back to stock, you'll still have to flash your custom ROM after you get your phone working.
2. The .img files can be downloaded from https://developers.google.com/android/nexus/images#shamu.

Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk

bushako said:
Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This, easiest way for you probably. I've done it this way before too. I suppose you could ask someone to TeamView your pc, but you should probably try the usb otg method first.

Booting TWRP through fastboot doesn't work

Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is going wrong here!

Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.

ptn107 said:
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
Click to expand...
Click to collapse
Thanks for your reply, the file sizes are correct, I tried these from twrp download page: twrp-3.2.3-1-payton.img (29.5M) and twrp-3.2.3-0-payton.img (25.9M) - same result.

Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?

gee one said:
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
Click to expand...
Click to collapse
Will give this a try tomorrow, thanks a lot!
Edit: Still no luck. Tried it with linux mint and even there the same sh!t... wtf

Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?

Neffy27 said:
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Click to expand...
Click to collapse
Latest drivers from Motorola Device Manager are installed and phone is properly recognized in device manager (used usb 2.0, 3.0 and 3.1 ports, nothing changes, same behavior). I tried it now with mfastboot but still nope..

Are you using minimal or full sdk (by Google) platform tools?

Neffy27 said:
Are you using minimal or full sdk (by Google) platform tools?
Click to expand...
Click to collapse
Minimal, I have also a Moto G5 and I don't face this kind of problems - only with Payton.

I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.

Neffy27 said:
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Click to expand...
Click to collapse
Unfortunately still no progress with full sdk and latest platform-tools, I'm giving up (for now).. I don't get it man, I'm not able to do anything in bootloader... for example when I try "fastboot flash partition gpt.bin" it freezes at sending OR it throws instant failed, the bootloader log menu shows that something is downloading but nothing happens... I relocked the bootloader (locking and unlocking is no problem) again and I am going to use it for a while... otherwise I will do a mistake somewhere and will brick it... Thanks for taking the time to help me haha

I'm having this same exact issue, just got this phone (XT1900-1) for my wife and she wants a custom rom, my own phone booted into twrp no problem.

https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Maybe try the fastboot in that link. I read through the thread and no specific reason why they suggest that version but it allowed people to flash back to stock. I used it last week to go back to stock before Lineage.

No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.

Sorry, beyond my expertise. Maybe it's USB c port on the phone issue? Intermittently dropping the connection? Or have to tried flashing the 8.1 sick from the thread I posted? Maybe the factory ROM is messed up some how. I honestly don't know and those suggestions aren't based in any real knowledge.

Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?

Slayer5934 said:
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Click to expand...
Click to collapse
Had exactly the same behavior like you (especially Edit 3), I tried it on a different computer from 2013 with usb 2.0 ports and it worked..
No other cable, no usb port, no adb and fastboot changes and no other drivers - just put all the stuff on a other computer and run the commands from there :good:
ptn107 said:
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Click to expand...
Click to collapse
Yeah, I'm on 1:7.0.0+r33-2 too.. I guess it has something to do with my mainboard or usb controller, weird weird weird

A different pc solved the issue.. wtf.. thank you..

I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.

dirktacular said:
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
Click to expand...
Click to collapse
Yeah I wish we knew the exact problem and solution but you might just be stuck trying new computers for eternity sadly..