Database Info

help root

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 !!!!!

Windows cannot detect that the phone is in fastboot mode

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

fastboot error_Fixed: fastboot error command failed write to device failed (unknown error))

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).

Question ROG phone 5s not recognized in fastboot mode, but ADB works... Windows driver issue?

Hi All,
I bought a ROG phone 5s (ZS676KS) direct from ASUS and I've been trying to root it all week. The firmware version is WW_18.1220.2111.160.
So far, I have been able to unlock the bootloader using Asus' app. My phone displays the unlocked bootloader warning on every boot.
I can't make fastboot work... the "adb reboot bootloader" command does work. I can also boot using the power + volume up button. But the "fastboot devices" command always comes up empty.
I found two possible reasons why fastboot doesn't work. So far I failed to fix either one.
First, the "OEM unlocking" option is missing in my developer options menu. I have the "USB debugging" option checked off. But many of the guides I read online say to allow OEM unlocking and I can't do that. But I've also seen people say that it doesn't matter. So, I don't know if this is a real problem. I can't find any reference to this problem except in Samsung phones. I tried the recommended fix but it didn't work.
Second, something's wrong with the fastboot driver on my computer. When get my phone into fastboot mode and plug it into the computer, device manager shows a device called "ASUS_I005D" with an orange caution icon on it. The error message in the properties menu says "The drivers for this device are not installed. (code 28)". This is probably the real problem.
{
"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"
}
Windows isn't finding a driver with its online driver search. I spent a few hours playing with Windows drivers to no avail. But maybe I missed something. I did find "ASUS_Android_USB_drivers_for_Windows_20150212" online and it didn't help.
I have tried different wires and USB ports and I'm using the side port of the phone instead of the bottom (although I tried the bottom port too). I tried another computer and that didn't work. But this was before I realized what was happening with windows drivers so I didn't check the device manager. I'm away from home now so I just have access to the one computer for now.
Does anyone know where I can find the correct driver? Or is there another approach I haven't considered? I hope there's nothing fundamentally wrong with the phone. I kind of just bought it without explicitly verifying, assuming the 5s is rootable since the 5 is...
Thanks Everybody,

Success is disgusted by some people, and will not share any files for free in the future.

It's not your device but likely Win 10 playing games with you. First completely uninstall the device driver to clean things up. Reboot your pc into Safe Mode. Plug in your phone from the side connector with a good data capable USB cable. From Device Manager choose "Add Legacy Hardware" from the menu and point the location to where you have saved the latest official Android USB drivers and install. Reboot Windows normally. If things have gone well, you should be able to both ADB & Fastboot into your device.

What a relief.
I am now able to flash my patched boot.img.
Thanks to both of you. I'm off to the races...

For me I just get a Ubuntu iso, boot your computer off a USB stick, install adb and fastboot via apt, and boom, no crappy drivers needed

Question MiUnlockTools doesn't detect my phone

Hi everyone,
I wanna unlock bootloader of my phone, but MiUnlockTools doesn't detect it, however `fastboot devices` command show device. I tried different versions of MiUnlockTools (6.5.314.7, 5.5.224.24, 4.5.814.51), different bootloader interface drivers: by Google of 2013 and by Xiami of 2016, nothing changed.
Also I tried to install XiaoMiTool V2, it recognize device and switch from fastboot to system with adb, and Mi PC Suite, all was useless.
I use Windows 10.0.19044 with Test Mode and with disabled driver signification, stock USB Cable with USB 2.0 port, usb debugging and OEM is enabled in MIUI, all tools was executed in administrator mode.
I read lot of threads with same issues, tried all suggested solutinons, bot nothing works. Does anyone can help me?
{
"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"
}

ulanzetz said:
Hi everyone,
I wanna unlock bootloader of my phone, but MiUnlockTools doesn't detect it, however `fastboot devices` command show device. I tried different versions of MiUnlockTools (6.5.314.7, 5.5.224.24, 4.5.814.51), different bootloader interface drivers: by Google of 2013 and by Xiami of 2016, nothing changed.
Also I tried to install XiaoMiTool V2, it recognize device and switch from fastboot to system with adb, and Mi PC Suite, all was useless.
I use Windows 10.0.19044 with Test Mode and with disabled driver signification, stock USB Cable with USB 2.0 port, usb debugging and OEM is enabled in MIUI, all tools was executed in administrator mode.
I read lot of threads with same issues, tried all suggested solutinons, bot nothing works. Does anyone can help me?
View attachment 5565555
Click to expand...
Click to collapse
try with another PC.

had the same issue with an amd pc... if you can try iy on a intel pc.
use this mi flash tool to install drivers *2021.02.26
and i use this unock tool

Change your usb chord

wendale1231 said:
Change your usb chord
Click to expand...
Click to collapse
read the post, it's already done.

ulanzetz said:
Hi everyone,
I wanna unlock bootloader of my phone, but MiUnlockTools doesn't detect it, however `fastboot devices` command show device. I tried different versions of MiUnlockTools (6.5.314.7, 5.5.224.24, 4.5.814.51), different bootloader interface drivers: by Google of 2013 and by Xiami of 2016, nothing changed.
Also I tried to install XiaoMiTool V2, it recognize device and switch from fastboot to system with adb, and Mi PC Suite, all was useless.
I use Windows 10.0.19044 with Test Mode and with disabled driver signification, stock USB Cable with USB 2.0 port, usb debugging and OEM is enabled in MIUI, all tools was executed in administrator mode.
I read lot of threads with same issues, tried all suggested solutinons, bot nothing works. Does anyone can help me?
View attachment 5565555
Click to expand...
Click to collapse
thats not what you are supposed to be using
Follow this guide

d_g_m_2000 said:
had the same issue with an amd pc... if you can try iy on a intel pc.
Click to expand...
Click to collapse
Thanks, I also used AMD PC. Just installed Windows on my Intel MacBook Pro and all works.
Seems to be bug on AMD

ulanzetz said:
Thanks, I also used AMD PC. Just installed Windows on my Intel MacBook Pro and all works.
Seems to be bug on AMD
Click to expand...
Click to collapse
I think more that it's some version of Windows because I had exactly the same problem with a w10 Intel pc and it worked with a w10 AMD pc.