Guys,I was using Miui now I wish to unlock the boot loader and install custom
But the mi unlock tool is not detecting the device
Tried adb devices..it's detecting the phone but the fastboot devices is not detecting the phone..and the device manager either in when phone is in fastboot
Help guys
Nb:installed latest drivers,windows 10
Did you find any solution?, i am stuck in a similar situation please help me out
1st of all: To unlock the bootloader you have to accept the OEM unlocking from the developer settings (if you dont know how to access them google it)
2nd: while in fastboot on the fastboot driver execute the command " fastboot devices"
the output should be something like xxxxxxxx fastboot
If the pc or mi unlock tool doesnt see the phone the change your fastboot &/or adb drivers
If it still doesnt recognise it then you should change cable or go to a technician to fix the phone.
Related
I'm trying to unlock the bootloader of my U8650. When i run adb devices i see it so i can say that the driver are correctly installed. i run adb reboot bootloader anf here i get stuck, since the phone restarts but hangs on the huawei logo and if i try to run fastboot oem unlock it says <waiting for devices>...this is done becouse the phone is not recognized by windows anymore, i have a yellow triangle on the Fastboot interface in my devices.
Could somebody tell me why?
Hello to everyone that read and thanks you for the time passing to read my problem.
First of all : this is not my native language so excuse me for my english ... :/
After that, this is my first thread ... :/
And then , i'm tryin to learn but i'm pretty newbie on computing ... :/
(i'm trying to root my phone like every newbie does first by following slowly and accurately this tutorial: https://www.getdroidtips.com/root-wiko-view-3-lite/
i'm gonna details all i did step by step but at the end cause i don't think that the problem come from here)
so after etablishing the connection between my device and the PC using a wiko usb driver
i tried to flash my Wiko View 3 Lite ROM to boot the patched "boot.img" via Minimal ADB and Fastboot V1.4.3 (latest version)
so once i enter the command : fastboot flash boot "MyPatchedBootFile".img
i got a :
Failed.(flashing lock flag is locked. Please unlock it first!)
so i should able the flashing option somehow somewere ?
i tried several fastboot command but nothing... (btw i is there a way to kow all the comandes i can do on my PC cause i see the command changing depending phones or fastboot )
that's what i have :
FAILED (remote :Not implemet.)
i'm not sure to understand what "no implemet" mean ??
I can't find any useful info exept this one unfortunately that could be the same for my phone's model :
Rooting a wiko jerry is impossible due to all fastboot commands lock the phone
On Linux: All fastboot commands lock. Particularly fastboot oem unlock or fastboot flashing unlock. After removing and re-attaching the phone to the usb port (without turning it off), the phone bec...
android.stackexchange.com
i'm continuing to look for anwsers, can someone have an idea ??
( that's what i did:
1/ i've downloaded magisk.apk's last vertion on my phone
2/ found a Wiko View 3 Lite full ROM online for the rom.pac file
3/ converted it w the SPD flash tool (i didn't really understood this step :/) : https://www.getdroidtips.com/patch-boot-img-root-spreadtrum-device/
4/ sent it to my phone
5/converted it agan via magisk.apk on my phone
6/ took it back from my computer to the same folder that i launch the ADB and fastboot comand prompt
7/last step normally :/ i should write the command: fastboot flash boot xxxxxxxxx.img and i gotstuck here ....
)
thanks again for all your help guys ))
Hakodu13 said:
...
so once i enter the command : fastboot flash boot "MyPatchedBootFile".img
i got a :
Failed.(flashing lock flag is locked. Please unlock it first!)
so i should able the flashing option somehow somewere ?
i tried several fastboot command but nothing... (btw i is there a way to kow all the comandes i can do on my PC cause i see the command changing depending phones or fastboot )
that's what i have :
FAILED (remote :Not implemet.)
i'm not sure to understand what "no implemet" mean ??
I can't find any useful info exept this one unfortunately that could be the same for my phone's model :
Rooting a wiko jerry is impossible due to all fastboot commands lock the phone
On Linux: All fastboot commands lock. Particularly fastboot oem unlock or fastboot flashing unlock. After removing and re-attaching the phone to the usb port (without turning it off), the phone bec...
android.stackexchange.com
i'm continuing to look for anwsers, can someone have an idea ??
...
Click to expand...
Click to collapse
Before trying to deal with phone's bootloader, will say running any Fastboot commands, you have to enable "OEM unlock" option in phone's Android Settings->Developer option. If done so, reboot phone. Afterwards run Fastboot commands
Code:
fastboot devices
fastboot oem unlock <- or: fastboot flashing unlock
jwoegerbauer said:
Before trying to deal with phone's bootloader, will say running any Fastboot commands, you have to enable "OEM unlock" option in phone's Android Settings->Developer option. If done so, reboot phone. Afterwards run Fastboot commands
Code:
fastboot devices
fastboot oem unlock <- or: fastboot flashing unlock
Click to expand...
Click to collapse
Hey
Thanks for your awnser,
i did it already, i've activated EOM unlock , USB debug and also desactivated the standby when the phone is plugged
also i think all fastboot command work cause i can reboot my phone using "fastboot reboot"command
fastboot devices reconize my phone
fastboot flashing unlock dosn't work
it is writed: FAILED (remote: Not implemet.)
fastboot oem unlock dosn't work,
it is writed: FAILED (remote: unknown cmd.)
something interesting is when i write fastboot "AnithingElse" unlock
it says: fastboot: usage: unknown command "AnithingElse"
and no: FAILED (remote: unknown cmd.)
like if adbandfastboot know the commannd " fastboot oem unlock " somehow but not my phone.
thanksthanksthanks again for your awnser!!!
My guess is that running Fastboot commands is denied by OEM/Carrier. And that's not wondering me because phone is based on UniSoc chipset.
AFAIK to get Fastboot working on such phones you have to request from OEM/Carrier the unlock-code as 1st thing of all things and when received have to flash it to phone.
jwoegerbauer said:
My guess is that running Fastboot commands is denied by OEM/Carrier. And that's not wondering me because phone is based on UniSoc chipset.
AFAIK to get Fastboot working on such phones you have to request from OEM/Carrier the unlock-code as 1st thing of all things and when received have to flash it to phone.
Click to expand...
Click to collapse
Ye i guessed the commands is denied on purpose
but why ? just for me not to have root acces ?
and what if i want to flash or reflash my ROM just to have back a new fresh boot ?
do a lot of phone constructor use that radical trick ?
and what is OEM/Carrier ? where can i find this ? i can't find anything online ...
merci ))
OEM is an acronym and stands for Original Equipment Manufacturer ( e.g Samsung )
Carrier is the is cell phone company that provide cellular service to cell phone users ( e.g. AT&T, Verizon )
I have an OPPO F9 pro ,OPPO devices don't have any fastboot/bootloader mode given by manufacturer ,i have tried all methods like ADB commands(adb reboot bootloader) , power off+volume up/down ,,nothing works my phone boots into system normally ,this is because there do not exist the fastboot mode.
So can someone plz help me with how can i unlock bootloader of my oppo f9 pro any help would be really appreciated a lot
If in phone's Android -> Settings -> Developer options the option "OEM unlock" is available then enable it and re-start phone afterwards.
On PC-side you also have to install Oppo F9 Pro MediaTek VCOM Driver
jwoegerbauer said:
If in phone's Android -> Settings -> Developer options the option "OEM unlock" is available then enable it and re-start phone afterwards.
On PC-side you also have to install Oppo F9 Pro MediaTek VCOM Driver
Click to expand...
Click to collapse
Thanks for replying,
I would like 2 tell that i have already installed all drivers for my phone and my phone is fully connected via adb to my pc plus the OEM unlock is available and is of no use(the OPPO official service themselves says that OPPO phones don,t have any bootloader) ,then it simply means the OEM unlock is useless ,and i have tried it a million times using that vol.up/down + power button (OR) by adb commands nothings works.
So since my phones doesn't have any fastboot mode then how can i even unlock bootloader plz help
armankang said:
Thanks for replying,
I would like 2 tell that i have already installed all drivers for my phone and my phone is fully connected via adb to my pc plus the OEM unlock is available and is of no use(the OPPO official service themselves says that OPPO phones don,t have any bootloader) ,then it simply means the OEM unlock is useless ,and i have tried it a million times using that vol.up/down + power button (OR) by adb commands nothings works.
So since my phones doesn't have any fastboot mode then how can i even unlock bootloader plz help
Click to expand...
Click to collapse
Wondering - because you stated your phone doesn't have a bootloader what OPPO officials confirmed - why then you try to unlock phone's bootloader?
BTW: ADB commands operate on Android OS, not on phone's bootloader what in fact Fastboot commands do.
Example commands sequence:
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot 2>nul
adb get-state
ok bro i got my answer thx
armankang said:
ok bro i got my answer thx
Click to expand...
Click to collapse
Did you root your oppo f9?
I just purchased a OnePlus Nord N10 5G (BE2026)
Originally it was running OxygenOs 10.x.x.x
Following guides from oneplus website and here on XDA I was able to successfully unlock the bootloader and of course ADB worked fine as well as Fastboot in the bootloader etc...
After unlocking the bootloader I realized that OxygenOs 11.0.2.BE86AA was available via OTA. Which is now what the phone is currently running.
***MAIN ISSUE***
after unlocking the bootloader in order to gain root access via TWRP and Magisk my PC fails to find any devices while the phone is in Fastboot mode... ADB still works just fine but as soon as I run "adb reboot bootloader" or boot to bootloader via buttons the PC will not detect the phone any longer while in the bootloader or Fastboot mode...
I have triple checked that:
SDK USB drivers
ONEPLUS USB DRIVERS
Windows Universal USB drivers
USB Debugging
OEM Unlocking
PC is granted developer access
newest version of ADB & Fastboot
and everything else I can find on this issue searching Google & XDA for the past 3 days
* one issue that I found strange, only when the phone was booted into the bootloader Windows device manager showed Android as an unknown device. Which I could only solve by using Zadig and installing Winusb driver... but still running "fastboot devices" while phone is in bootloader / Fastboot mode still shows no devices....
I've been trying to solve this about 4 days now scouring the internet for any information I could find and nothing seems to work. But everything worked just fine before I unlocked the bootloader / flashed OxygenOs 11 via OTA and now windows to see the phone while in the bootloader....
When phone is got booted into bootloader / fastboot mode then phone can't get seen / accessed by ADB. Point.
jwoegerbauer said:
When phone is got booted into bootloader / fastboot mode then phone can't get seen / accessed by ADB. Point.
Click to expand...
Click to collapse
@jwoegerbauer not entirely sure what you are trying to imply with your message...
If you are trying to point out that ADB doesn't work in bootloader / fastboot mode, I am completely aware of this. And never mentioned otherwise in my original message.
With my phone booted up into Android
And I run "adb fastboot bootloader" the phone will reboot into bootloader mode but my PC still shows waiting for devices... Or if I boot into bootloader / fastboot mode manually and run “fastboot devices" it shows no connected devices. And no fastboot Commands work either... I am not trying to run ADB Commands in fastboot mode.
AFAIK starting with Android 10 the command sequence should be as this
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
...
fastboot reboot
because fastbootd got moved to Android's userspace.
So I want to unlock the bootloader of my poco f2 pro. I installed minimal adb and fastboot, google usb drivers and the mi unlocker tool. Adb does register my device, fastboot will only recognize my device if I use the adb reboot fastboot command. If I use adb reboot bootloader fastboot wont recognize my device and the device manager will show a missing driver. The unlocker tool wont recognize my phone neither in fastboot nor in bootloader mode. I tried using the xiaomi usb drivers but they appear to be too outdated (2011) or something else but I cant install these drivers. Any ideas what driver to use or how else to bypass the problem? I also tried reinstalling minimal adb and fastboot while my device was in bootloader mode hoping it would install the driver but still no success. The drivers coming with the mi unlocker tool were also useless. To rule easy things out, I tried different ports, cables and even pcs, every time the exact same problem. Usb debugging and oem unlock were obviously enabled and my device is registered for unlock.
Rainbow_Chameleon said:
So I want to unlock the bootloader of my poco f2 pro. I installed minimal adb and fastboot, google usb drivers and the mi unlocker tool. Adb does register my device, fastboot will only recognize my device if I use the adb reboot fastboot command. If I use adb reboot bootloader fastboot wont recognize my device and the device manager will show a missing driver. The unlocker tool wont recognize my phone neither in fastboot nor in bootloader mode. I tried using the xiaomi usb drivers but they appear to be too outdated (2011) or something else but I cant install these drivers. Any ideas what driver to use or how else to bypass the problem? I also tried reinstalling minimal adb and fastboot while my device was in bootloader mode hoping it would install the driver but still no success. The drivers coming with the mi unlocker tool were also useless. To rule easy things out, I tried different ports, cables and even pcs, every time the exact same problem. Usb debugging and oem unlock were obviously enabled and my device is registered for unlock.
Click to expand...
Click to collapse
Delete all drivers.
reinstall them.
All my drivers are 2016(W10/W11).
Try another version.
https://c.mi.com/thread-2262302-1-0.html