Related
Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks
i use windows but i also get problems when i didnt had a break after the flash parts/ update parts
brosenz said:
Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks
Click to expand...
Click to collapse
I know nothing about using Macs but have you installed the device drivers? As you are getting no serial number returned when using fastboot devices im guessing not.
Mark.
On a side note please do not post questions in the Development Forums as that is not the place for them.
Thanks.
The device is being detected while running in normal mode, meaning I do have the drivers, the problem is when I go into FASTBOOT MODE, I can no longer see the phone
Craiq said:
i use windows but i also get problems when i didnt had a break after the flash parts/ update parts
Click to expand...
Click to collapse
But for the simple command ./fastboot-mac devices should work and it's not
in bootloader mode u need other drivers
but dont know how to install them on mac
First thing, make sure your fastboot file is executable
from the folder containing fastboot-mac:
chmod a+x fastboot-mac
You do not need further drivers on a mac. Just make sure you are using the correct fast boot and have all of the images in the same folder. Try using a different USB port. I renamed my fastboot file to fastboot and copied it into usr/local/bin folder so it can be accessed without the ./ ...Hope this helps...I actually just got done restoring mine because its gotta go back to the store because the internal storage is all sorts of jacked up...Since you clearly have a mac, have you had any issues using android file transfer?
dhemke17 said:
First thing, make sure your fastboot file is executable
from the folder containing fastboot-mac:
chmod a+x fastboot-mac
You do not need further drivers on a mac. Just make sure you are using the correct fast boot and have all of the images in the same folder. Try using a different USB port. I renamed my fastboot file to fastboot and copied it into usr/local/bin folder so it can be accessed without the ./ ...Hope this helps...I actually just got done restoring mine because its gotta go back to the store because the internal storage is all sorts of jacked up...Since you clearly have a mac, have you had any issues using android file transfer?
Click to expand...
Click to collapse
I just checked and Fastboot is executable, as a matter of fact it's running, the problem is that the phone cannot be seen from the FASTBOOT mode, and I can see from the phone screen that IT IS in Fastboot Mode, it says in RED letters "FASTBOOT MODE"
brosenz said:
I just checked and Fastboot is executable, as a matter of fact it's running, the problem is that the phone cannot be seen from the FASTBOOT mode, and I can see from the phone screen that IT IS in Fastboot Mode, it says in RED letters "FASTBOOT MODE"
Click to expand...
Click to collapse
Well reboot your phone. Once up, try and boot into boot loader the manual way by powering off the device, holding both vol + and -, and press power... then try your fastboot commands. Are you rooted or no?
dhemke17 said:
Well reboot your phone. Once up, try and boot into boot loader the manual way by powering off the device, holding both vol + and -, and press power... then try your fastboot commands. Are you rooted or no?
Click to expand...
Click to collapse
I've done that, going into FASTBOOT MODE manually and the same result. Yes I am rooted.
I just want to go back to stock and re-lock the phone, is there other way to accomplish that ?
NOTE: I've tried Mac and PC (Galaxy Nexus Root Toolkit 1.3), different USB cables, different USB ports, reinstalled all the drivers on the Windows computer, NOTHING, the phone it's not being detected in FASTBOOT MODE.
Is it possible to go back to stock and re-lock from the Recovery Mode ?, I have ClockWorkMode 5.5.0.2 installed and working fine.
You can flash a Stock Rom via cwm but you can only relock the phone via fastboot mode.
Has this problem only surfaced recently?
You say that you are rooted and have cwm flashed so how did you do that?
Do you have another usb cable that you can try?
Mark.
mskip said:
You can flash a Stock Rom via cwm but you can only relock the phone via fastboot mode.
Has this problem only surfaced recently?
You say that you are rooted and have cwm flashed so how did you do that?
Do you have another usb cable that you can try?
Mark.
Click to expand...
Click to collapse
I used FASTBOOT to unlock and Root, no problem at all, use the phone for 10 days and them decided to go back to Stock and Re-Lock. If I connect the phone in normal operating mode to the computer it will be recognized and I can see the phone from the computer connected via USB, so the cabe, port on the phone and port on the computer are OK. I've tried different computer (Mac and PC), different OS (Mac OS X and Windows 7), different USB cable, different USB port.
Just make sure USB debugging is on...try getting on a PC and running the ODIN file from someone was kind enough to post us...to get into odin mode, just hold up while the phone is off and hit power. You need the drivers installed and the latest version of ODIN on your desktop as well.
dhemke17 said:
Just make sure USB debugging is on...try getting on a PC and running the ODIN file from someone was kind enough to post us...to get into odin mode, just hold up while the phone is off and hit power. You need the drivers installed and the latest version of ODIN on your desktop as well.
Click to expand...
Click to collapse
I have Odin3 V1.85 installed in the PC, what I have to do with it ?, thanks
brosenz said:
I have Odin3 V1.85 installed in the PC, what I have to do with it ?, thanks
Click to expand...
Click to collapse
Plug your phone in and then turn it off...download the odin file from xda...not sure who posted it...it will be a 7z file...inside there are two separate .tar files. Extract these from the .7z file but do not fully unzip them. Place the one without LTE in the name in PDA and the one with LTE in phone, turn your phone on while holding vol -... there is a box that turns yellow in odin once your phone is connected. then check your screen against the one posted where you get the odin full restore file from and verify it matches, then flash it...
dhemke17 said:
Plug your phone in and then turn it off...download the odin file from xda...not sure who posted it...it will be a 7z file...inside there are two separate .tar files. Extract these from the .7z file but do not fully unzip them. Place the one without LTE in the name in PDA and the one with LTE in phone, turn your phone on while holding vol +... there is a box that turns yellow in odin once your phone is connected. then check your screen against the one posted where you get the odin full restore file from and verify it matches, then flash it...
Click to expand...
Click to collapse
I do not know why but Vol + does not work in my phone
brosenz said:
I do not know why but Vol + does not work in my phone
Click to expand...
Click to collapse
My bad lol...down...volume down
I made a video on how to root and unroot the nexus s 4g using a Mac and also works with galaxy nexus. Just follow the video but make sure the files u are flashing are for your phone and not a ns4g. Here's the link
https://www.youtube.com/watch?v=mIWEM8zBnTM&feature=youtube_gdata_player if u have questions u can pm me.
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
I made a video on how to root and unroot the nexus s 4g using a Mac and also works with galaxy nexus. Just follow the video but make sure the files u are flashing are for your phone and not a ns4g. Here's the link
https://www.youtube.com/watch?v=mIWEM8zBnTM&feature=youtube_gdata_player if u have questions u can pm me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I just used your video to unroot my galaxy nexus 4.0.4 thanks a lot!
Hi, I recently bought a factory cable because my Kindle is bricked. I'm stuck at the kindle fire logo with no adb shell and fastboot says "waiting for device". I got in this situation by doing a wipe from twrp and then flashing the stock recovery (dumb, I know).
Anyway, with a regular cable I can do basic adb commands (adb reboot, etc).
With the factory cable my kindle isn't showing up under adb devices. Windows recognizes it and it shows up in the device manager. I've already re-installed the drivers and everything.
Here's an outline of what happens when I plug in the factory cable. This is starting with the kindle off.
Kindle turns on and goes tot he kindle fire logo and freezes. The power button is green with the factory cable. I noticed that with the normal cable it's orange. I'm not sure if this has any relevance at all.
Anyway, I'm wondering what I can do to get my kindle to show up in adb while using the factory cable.
If you need more info from me let me know and I'll add it.
A factory cable puts the device in fastboot mode, therefore will only accept fastboot commands.
soupmagnet said:
A factory cable puts the device in fastboot mode, therefore will only accept fastboot commands.
Click to expand...
Click to collapse
I'm not sure if I'm missing something, but fastboot commands aren't working either. It's not showing up under fastboot devices and fastboot flash recovery hangs at "waiting for device".
WhatTheFiber said:
I'm not sure if I'm missing something, but fastboot commands aren't working either. It's not showing up under fastboot devices and fastboot flash recovery hangs at "waiting for device".
Click to expand...
Click to collapse
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
The second post is about device drivers and what to look for in the device manager when your device is in fastboot mode.
It's also possible that you aren't including the vendor ID in your fastboot command. That's covered in the third post.
kinfauns said:
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
The second post is about device drivers and what to look for in the device manager when your device is in fastboot mode.
It's also possible that you aren't including the vendor ID in your fastboot command. That's covered in the third post.
Click to expand...
Click to collapse
Thank you so much! I was able to flash twrp by using fastboot -i 0x1949. Now I've just got to choose a new rom to flash .
Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!
Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.
Here is screenshot from minimal adb...
Phone must be in MTP mode.
And here is phone in fastboot
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
try upgrade your android sdk on your pc
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful
i am trying to flash twrp there is no folder called adb i have installed the 15 second adb and all so i have got this minimal adb flashboot and i tried with that and got this ---- FAILED (remote: Flashing is not allowed in Lock State). i have granted all usb and oem unlocking. please help with this
Phone shows unlocked during the boot?
I had the same Problem,after a Factory Reset works for me.
I am on Miglobe-Rom Miui10 8.6.28.
Minimal ADB is enough.
Or use this from Attachment.
Unpack with Win.zip and copy Twrp in this Folder.
Conect the Phone with your Pc ,boot into Bootloader and click "cmd-here.exe"
Use this Command
fastboot flash recovery twrp-3.2.1-3-whyred.img
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
gamebenchjake said:
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
Click to expand...
Click to collapse
Have you fixed your app to run on Magisk-SU ?
otonieru said:
Have you fixed your app to run on Magisk-SU ?
Click to expand...
Click to collapse
Hey Otonieru,
Not yet, but I've got one of the engineers working on it - hopefully it'll be up in the next 30 days or so
Same problem here after updating my gcam was not working was enabling hall again but it is not booting into twrp
Redmi Note 5 pro
So my Bootloader is locked,
My phone stuck in MI recovery idk how.
I cant install MIUI via fastboot. Im stuck ..
Can anyone please help me here not sure how to proceed further.
If you have made sure that you have all the drivers installed and still have not solved, you need to use an Intel-based PC / notebook and use a usb 2.0.
”Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful”
i did that but it is showing failed（too many links）and "press any key to reboot" showing on my phone's fastboot screen
Fastboot boot recovery.img flashing problem on Redmi note 5 pro
My bootloader is unlocked and my oem as well as usb deb is on. After i connect my phone in fastboot mode to my pc. The cmd shows fastboot devices but when it comes to fastboot boot recovery.img flashing device get disconnected. Plzzzzzz let me know a solution for this. A solution for this will be highly appreciateable.
Hello, I have two unlocked Pixel 2XL, one works without a problem, it is detected by adb and fastboot. The second one during boot has bootloop. When I try to turn it into fastboot mode, the screen of this mode is shown, but after connecting the cable (which works on the first fully working phone) and entering the command "fastboot devices" nothing happens. In device manager I only have 'device not detected or working incorrectly (code 43 or sometimes code 10). When trying to enter TWRP, the phone completely stutters and displays only the TWRP start screen without any other symptoms. I have good drivers installed because the computer detects this working phone without a problem ... Do I have a damaged USB port on the phone? Is there another explanation and solution for this?
binarnh said:
Hello, I have two unlocked Pixel 2XL, one works without a problem, it is detected by adb and fastboot. The second one during boot has bootloop. When I try to turn it into fastboot mode, the screen of this mode is shown, but after connecting the cable (which works on the first fully working phone) and entering the command "fastboot devices" nothing happens. In device manager I only have 'device not detected or working incorrectly (code 43 or sometimes code 10). When trying to enter TWRP, the phone completely stutters and displays only the TWRP start screen without any other symptoms. I have good drivers installed because the computer detects this working phone without a problem ... Do I have a damaged USB port on the phone? Is there another explanation and solution for this?
Click to expand...
Click to collapse
Most likely the culprit is either out of date platform-tools or TWRP...
What version of adb, fastboot, & TWRP are you using? Also, how are you booting TWRP -- there have been many cases where people would use the command "fastboot flash boot twrp.img" instead of booting temporarily...
Hope this ends up being helpful as that means it resolves it...
Are you able to fastboot boot the latest twrp.img?
Might want to give Deuces script a whirl. I've seen this fix situations like yours.
ADB version: 1.0.41 29.0.5-5949299, TWRP: twrp-pixel2-installer-taimen-3.3.0-0 Latest Rom istalled on this phone is Havoc OS 2.8 for P2XL. I trying to enter TWRP via fastboot and choose recovery there, but stuck on TWRP logo... When I try to enter a command: "fastboot boot twrp.img" receives a message: <waiting for any device>
edit: Deuces script log says: "Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version 29.0.5-5949299
Installed as C:\Users\marek\Desktop\platform-tools\fastboot.exe
Fastboot Detected!
Checking if device is detected via Fastboot.
Error: Device not detected via Fastboot.
Check device cables and fastboot drivers..."
But cable and drivers is good because other pixel 2xl works fine with it...
binarnh said:
ADB version: 1.0.41 29.0.5-5949299, TWRP: twrp-pixel2-installer-taimen-3.3.0-0 Latest Rom istalled on this phone is Havoc OS 2.8 for P2XL. I trying to enter TWRP via fastboot and choose recovery there, but stuck on TWRP logo... When I try to enter a command: "fastboot boot twrp.img" receives a message: <waiting for any device>
edit: Deuces script log says: "Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version 29.0.5-5949299
Installed as C:\Users\marek\Desktop\platform-tools\fastboot.exe
Fastboot Detected!
Checking if device is detected via Fastboot.
Error: Device not detected via Fastboot.
Check device cables and fastboot drivers..."
But cable and drivers is good because other pixel 2xl works fine with it...
Click to expand...
Click to collapse
This might sound crazy, but, at least try another USB A to C cable, and other ports on your pc. The P2XL is notorious for being finicky when it comes to cables and ports. What might work for one phone, doesn't necessarily mean it will for the other. Make sure it's a 2.0 USB cable as well :good:
I checked four different cables and all ports on my computer and still not lucky... I even checked on another computer and still the same
binarnh said:
I checked four different cables and all ports on my computer and still not lucky... I even checked on another computer and still the same
Click to expand...
Click to collapse
Then it's likely a hardware/port issue would be my guess.
Meh, so I will look for a workshop nearby that will exchange the port for me and check later
I would also suggest that you re-download EVERYTHING...
You may be stuck with a "buggy" TWRP image file or platform tools....and/or go against conventional thinking and download and try an older version of TWRP to see if it does it at that point as well...
In either case, hopefully you get it figured out and good luck to you...hope this ends up being helpful!
There were a number of Pixel 2 XL's that did suffer from charging port issues, including my original. Luckily I was still under warranty and was issued a replacement. The phones would charge fine but data did not transfer as with adb/fastboot, nor would Android Auto work.
https://forum.xda-developers.com/pixel-2-xl/help/pixel-2-xl-charging-port-damaged-t3783638
Update: fastboot and adb detect device but when I try flash factory image fastboot says: "fastboot: error: cannot determine image filename for"
binarnh said:
Update: fastboot and adb detect device but when I try flash factory image fastboot says: "fastboot: error: cannot determine image filename for"
Click to expand...
Click to collapse
What fastboot command did you give?
Badger50 said:
What fastboot command did you give?
Click to expand...
Click to collapse
I use flash all script
binarnh said:
I use flash all script
Click to expand...
Click to collapse
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?
Badger50 said:
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?
Click to expand...
Click to collapse
Yes for all your questions. I try 3 different cables
binarnh said:
Yes for all your questions. I try 3 different cables
Click to expand...
Click to collapse
Not running platform-tools through power shell either are you?
What happens when you try double clicking on the flash-all.bat file with your mouse?
binarnh said:
Badger50 said:
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?
Click to expand...
Click to collapse
Yes for all your questions. I try 3 different cables
Click to expand...
Click to collapse
Based on your error, I'm guessing all the files in the Full Factory .zip file (all 6 of them) aren’t residing there with the adb & fastboot .exe files within the platform-tools folder. Make sure you’re seeing those 6 files (you will have a two .sh files, two .img files, one .zip file, etc.) with the .exe adb & fastboot file.
Then, also make sure that you are directing your powershell or command prompt to the correct “platform-tools” folder, because many other people seem to have multiple “platform-tools” folders and they end up directing to a wrong folder…
Hope this ends up being helpful…
I fixed it! The error in fastboot mode probably came from a file that I extracted from winrar, when I downloaded the factory image again and extracted the files this time through 7zip and copied them to the platform-tools folder and double-clicked flash-all.bat fastboot started and the installation was successful! Thanks to everyone who wanted to help me solve this problem <3
ps. btw, I haven't replaced this broken port on the phone... just started working again...