Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Bencaill said:
Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Click to expand...
Click to collapse
Hello, are you sure you have the boot.img also in the direcotry?
DallasCZ said:
Hello, are you sure you have the boot.img also in the direcotry?
Click to expand...
Click to collapse
yes, I am sure I have it
Bencaill said:
yes, I am sure I have it
Click to expand...
Click to collapse
i tried it again and it works well for me.
can you post a creen of the folder where you extracted the files?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you have to run the root.bat file, you cannot dir the boot.img
I know I have to run the bat file but you asked me a screen of the folder
I have this message:
strange... idunno for me its working well (windows 7 pro) and the boot.img is in the same directory... do you have some antivirus, anti spam apps running?
A other member of Frandroid forum has exactly the same issue. But he is running W8.1
That is really strange.
I am running win 8.1 as well
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
The problem seems to be resolved by using Windows 7 instead.
http://forum.frandroid.com/topic/223905-tuto-root-de-l-idol-3-55/?p=3417628
using win 7 is not a solution... there have to be a way how to do it, because there are thousands of users with win 8.1 who using fastboot and adb commands...
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
is your bootloader unlocked?
And I take it you've enabled Developer Options and USB Debugging?
After all my talk about the ease of communicating with Android devices from a Mac, I'm now unable to successfully issue fastboot commands when in the bootloader. I've tried using sudo, making sure to include arguments that address the device, etc. I can execute adb commands when the phone's system is booted, though. But fastboot commands either get me a "waiting for device" or nothing at all. I thought I was able to do this successfully yesterday, when I was just testing it out. Today, I was going to root by booting into TWRP and flashing SuperSU.
maigre said:
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
Click to expand...
Click to collapse
If it was a driver issue, my phone would not restart with the command, every drivers are OK
ractar28 said:
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
Click to expand...
Click to collapse
Your method worked !!!!!!!!!!!!!!! THX !!!!!
Related
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
quantum94 said:
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
Click to expand...
Click to collapse
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
root-expert said:
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
Click to expand...
Click to collapse
nopes...on typing "fastboot code", it redirects me to the current directory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what to do?
Are you sure you are in fastboot mode?
root-expert said:
Are you sure you are in fastboot mode?
Click to expand...
Click to collapse
pretty sure...u can see the pic at:
What now!? :crying:
quantum94 said:
pretty sure...u can see the pic at:
What now!? :crying:
Click to expand...
Click to collapse
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
root-expert said:
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
Click to expand...
Click to collapse
sorry for the late reply....
I tried the same thing on different pc and it worked!
But i have another problem!
I installed cm11 nightly for my on my x plus from here:
http://get.cm/get/qG0
After that my imei has gone blank along with the baseband version.
I did a bit of research and found that by using ruu, u can get the imei back.
So for that i needed turn my s-on to s-off by the foll commands:
adb reboot
if i am not mistaken, while the phone is rebooting i am supposed to put the 2nd command:
adb wait-for-device push firewater /data/local/tmp
The problem here that I think is the phone reboots so fast that i guess the command fails to execute and i get an error saying :
error protocol fault (no status)
So, how to turn off fastboot or quickboot in cm11? There is absolutely no option in the phone. I tried battery settings,power settings, everything!
is there a way to disable fastboot/quickboot in bootloader mode?
plz help!
Hey bros. This might sound like a noob question but I just cannot get the phone to show up in command prompt. I booted the thing into fastboot, I have all of them adb goodies installed (alright not all of them, only the minimal installation) and I also have the Nokia driver installed but the thing simply refuses to show up. I type "fastboot devices" and I just get another line of text. Interestingly enough though I did manage to unlock the bootloader, even though when I typed "fastboot devices" I got nothing, just like the first time. When I try to flash TWRP I get the legendary "<waiting for device>" message. Although like I was saying, unlocking the bootloader worked just fine, which is strange
Brilliant99 said:
Hey bros. This might sound like a noob question but I just cannot get the phone to show up in command prompt. I booted the thing into fastboot, I have all of them adb goodies installed (alright not all of them, only the minimal installation) and I also have the Nokia driver installed but the thing simply refuses to show up. I type "fastboot devices" and I just get another line of text. Interestingly enough though I did manage to unlock the bootloader, even though when I typed "fastboot devices" I got nothing, just like the first time.
Click to expand...
Click to collapse
i think it's ok, it doesn't matter if other adb and fastboot commands work properly.
SkaboXD said:
i think it's ok, it doesn't matter if other adb and fastboot commands work properly.
Click to expand...
Click to collapse
Problem is, when I try to flash TWRP I get the legendary "<waiting for device>"
Brilliant99 said:
Problem is, when I try to flash TWRP I get the legendary "<waiting for device>"
Click to expand...
Click to collapse
I am sorry I forgot to mention that in the main post. Let me edit it
Brilliant99 said:
Problem is, when I try to flash TWRP I get the legendary "<waiting for device>"
Click to expand...
Click to collapse
try to install other adb. I recommend to install platform-tools as it have only 5mb. If that doesn't work, try to reinatall Nokia 3 driver.
SkaboXD said:
try to install other adb. I recommend to install platform-tools as it have only 5mb. If that doesn't work, try to reinatall Nokia 3 driver.
Click to expand...
Click to collapse
I did all of that too and it still doesn't work. I have Windows 10 if that helps. I also have another computer on Windows 8.1
Brilliant99 said:
I did all of that too and it still doesn't work. I have Windows 10 if that helps. I also have another computer on Windows 8.1
Click to expand...
Click to collapse
I also have access to macOS, but I doubt it's any useful
Brilliant99 said:
I did all of that too and it still doesn't work. I have Windows 10 if that helps. I also have another computer on Windows 8.1
Click to expand...
Click to collapse
maybe a stupid question, but did you enable usb debugging and usb file transfer (mtp)?
SkaboXD said:
maybe a stupid question, but did you enable usb debugging and usb file transfer (mtp)?
Click to expand...
Click to collapse
I enabled those too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
idk then, try on other system, I'm using Windows 7 and i never had problem with it.
Try this
fastboot.exe -i 0x2e04 [Your_Command]
i had same issued but it fixed after use that command
lordschleger said:
Try this
fastboot.exe -i 0x2e04 [Your_Command]
i had same issued but it fixed after use that command
Click to expand...
Click to collapse
Thank you , you saved me hours of problem solving
I'm pretty new to stuff like rooting phones and such so I figured out that I'd be trying to see if I could manage to get my bootloader unlocked so I can once and for all install TWRP, which my dumbass has been trying to install without an unlocked bootloader.
I've got the basics going, like how should I do the unlocking (my phone's model is 5054S, yes it's an alcatel phone) and found a website which tells what commands you should do to unlock it
Well...
It just gets stuck there without further response. Amazing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could you guys help me on this one?
Command
Code:
fastboot reboot fastboot
is only to be used if Fastboot server is located in Android's user-space what only is case when Android OS has Dynamic Partition Layout.
jwoegerbauer said:
Command
Code:
fastboot reboot fastboot
is only to be used if Fastboot server is located in Android's user-space what only is case when Android OS has Dynamic Partition Layout.
Click to expand...
Click to collapse
Oh no, this happens with every piece of code that needs some input from a phone (with this i mean the part where the command line just gets stuck)
And this is essentially the same with every code I have to utilize in the guide for unlocking
jwoegerbauer said:
Command
Code:
fastboot reboot fastboot
is only to be used if Fastboot server is located in Android's user-space what only is case when Android OS has Dynamic Partition Layout.
Click to expand...
Click to collapse
Extra thing:
There's also this
Code:
fastboot -i 0x1bbb devices
Which when actually used, it kinda does work?? Just doesn't recognize the -i as a parameter in the programs. And yes, this happens with both CMD and PowerShell
Okay,
Code:
adb reboot-bootloader
DOES work. But it only restarts the phone.
And there's also this
Polaroid. said:
Okay,
Code:
adb reboot-bootloader
DOES work. But it only restarts the phone.
And there's also this View attachment 5348201
Click to expand...
Click to collapse
You are contradicting yourself: The applied ADB command of course DID NOT WORK, you got an error.
Reason: ADB got inproperly configured on phone.
Try this to get rid off of the error:
1. Disconnect phone from computer.
2. Revoke "USB debugging authorizations" in Android's Developer options on the phone.
3. Reconnect the phone to the computer and allow USB debugging on phone again.
4. Confirm the RSA-key in Authorization popup.
jwoegerbauer said:
You are contradicting yourself: The applied ADB command of course DID NOT WORK, you got an error.
Reason: ADB got inproperly configured on phone.
Try this to get rid off of the error:
1. Disconnect phone from computer.
2. Revoke "USB debugging authorizations" in Android's Developer options on the phone.
3. Reconnect the phone to the computer and allow USB debugging on phone again.
4. Confirm the RSA-key in Authorization popup.
Click to expand...
Click to collapse
Ah, thanks for correcting me. Didn't know about that. Gonna try if it works now
jwoegerbauer said:
You are contradicting yourself: The applied ADB command of course DID NOT WORK, you got an error.
Reason: ADB got inproperly configured on phone.
Try this to get rid off of the error:
1. Disconnect phone from computer.
2. Revoke "USB debugging authorizations" in Android's Developer options on the phone.
3. Reconnect the phone to the computer and allow USB debugging on phone again.
4. Confirm the RSA-key in Authorization popup.
Click to expand...
Click to collapse
Okay, I tried doing this and it does not resolve the problem, still restarts the phone
Yes. It is the same command and all but it still just doesn't work properly.
Q1: What is returned by command
Code:
adb devices
Q2: What is returned by command
Code:
fastboot devices
Hint: Add Alcatel 5054S to this thread's title thus mainly owners of such phone get addressed.
Good morning,
I'm new here, and i hope you can help me with my problem.
I have a mi MJJGYY02FM projector and i did a update with USB stick with files from Xiaomi.
Now after the update the projector start with MI logo and than shuts down, after that he start up with no screen and do nothing.
Can someone help me how to fix this. i can't get the projector in a boot menu with the remote, maybe he dont recognize the remote.
Kind Regards,
Bas
Reflash projector's Stock ROM.
jwoegerbauer said:
Reflash projector's Stock ROM.
Click to expand...
Click to collapse
I have the stock ROM on USB now, but hè will not install it. When i press the home and enter button and plug the power cable. Hè start up with the MI logo and shuts down, then start up with no screen.
Are there other ways to install the stock ROM?
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Thanks
Im gonna search out and try that option.
I let it know when it works. maybe i have some questions.
jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Im trying something, but do you have a discription how to make that USB with the Stock Rom?
I got your files on my pc. I have a 16GB USB format FAT32.
What is the way to make that sideload with the ROM version?
Im sorry for the questions, but i have never done this before.
I have done thist thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.
jwoegerbauer said:
The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.
Click to expand...
Click to collapse
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?
Vross46 said:
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?
Click to expand...
Click to collapse
My drive letter is :e
Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name
jwoegerbauer said:
Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name
Click to expand...
Click to collapse
ah ok. lets try.
It seems not so difficult but, for the first time is everything more difficult
What do i wrong. sorry! I do really my best
1, i have a format 16gb usb FAT32
2. i have install ADB installer.
3. i have download the stock rom (see picture)
4. my drive name is e:
5. When i zip my stock rom file, i got an another zip file, and an file of 1kb
in the next picture is what i do in CMD
anglee_full_9.0.0.1911 is my zipped stock rom downloadfile
the other 2 are the unzipped files from the first file
1st screenshot provided above shows
1. Device isn't connected via USB-cable with PC or, if, not powered on
2. The ROM's archive name you entered is without fileextension -> required :ZIP
If ROM's archive is packed as .RAR file then you have it to repack to .ZIP file
I think it will not gonna help.
When i connect my projector to the pc, the pc dont recognize him.
What i try, nothing works.
but thanks for your help anyway
Have you ever enabled "USB Debug" in Android's Settings -> Developer otions?
I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check
Vross46 said:
I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check
Click to expand...
Click to collapse
Hello Vross46, have you been able to solve your problem? I’m stuck with the logo as well
hey ya,
lets look into a very common error faced by many of us , sometime during bootloader unlock or flashing custom recovery in fastboot mode.
i recently flashed rmx1851(realme 3 pro) and constantly got a error in fastboot mode in (fastboot devices command)
After typing "FASTBOOT DEVICES" in the cmd in platform tool we get this type of error and
the phone instantly show a message " hold on power button to shut down the phone"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also this error "fastboot error command failed write to device failed (unknown error))"
After this if we want to execute any other fastboot command also,(like flashing custom recovery)the device constantly pops up same message and ultimately we fail.
TO SOLVE THIS ERROR , YOU CAN FOLLOW CERTAIN CHECKS
1. Check whether the adb drivers are properly installed on the pc
2.Both windows 10 and 7 have certain difference in the fastboot command
3.Try using different USB CABLE for the process.
4.Use USB 2.0 port , sometimes it might help.
5.If you are using amd based ryzen processor machine try using the same process on intel based system(still amd devices are not fully supported )
IF EITHER OF THE METHOD DOSEN'T WORK TRY USING THIS "ULTIMATE METHOD" WHICH ALSO WORKED FOR ME.
{{DOWNLOAD THIS FILE -- amd fix.bat {fix error}
--and run this file as administrator
--you will get this output
--and after that run try to execute fastboot commands , and hopefully now your error will be fixed}}
---credit to Safwan (youtube channel "TechCycle") for sharing us this wonderful fix
" video link"
anee1291 said:
hey ya,
lets look into a very common error faced by many of us , sometime during bootloader unlock or flashing custom recovery in fastboot mode.
i recently flashed rmx1851(realme 3 pro) and constantly got a error in fastboot mode in (fastboot devices command)
After typing "FASTBOOT DEVICES" in the cmd in platform tool we get this type of error and
the phone instantly show a message " hold on power button to shut down the phone"
View attachment 5442833
Also this error "fastboot error command failed write to device failed (unknown error))"
After this if we want to execute any other fastboot command also,(like flashing custom recovery)the device constantly pops up same message and ultimately we fail.
TO SOLVE THIS ERROR , YOU CAN FOLLOW CERTAIN CHECKS
1. Check whether the adb drivers are properly installed on the pc
2.Both windows 10 and 7 have certain difference in the fastboot command
3.Try using different USB CABLE for the process.
4.Use USB 2.0 port , sometimes it might help.
5.If you are using amd based ryzen processor machine try using the same process on intel based system(still amd devices are not fully supported )
IF EITHER OF THE METHOD DOSEN'T WORK TRY USING THIS "ULTIMATE METHOD" WHICH ALSO WORKED FOR ME.
{{DOWNLOAD THIS FILE -- amd fix.bat {fix error}
--and run this file as administrator
View attachment 5442843
--you will get this output
--and after that run try to execute fastboot commands , and hopefully now your error will be fixed}}
---credit to Safwan (youtube channel "TechCycle") for sharing us this wonderful fix
" video link"
Click to expand...
Click to collapse
i had a error for some reason
Brilliant solution bat file fixed fastboot for me! Thanks!
anee1291 said:
2.Both windows 10 and 7 have certain difference in the fastboot command
3.Try using different USB CABLE for the process.
4.Use USB 2.0 port , sometimes it might help.
Click to expand...
Click to collapse
thanks so much for your post. Not sure why but I disconnected all my other USB ports and tried another port. FINALLY got it to write the damn recovery file (different device).