Hi, after going to bootloader from In-depth test app, when I connect to my PC, and use fastboot devices, it lists as ????????? device and when I use fastboot flashing unlock, it just throws command failed, unknown error. Any solutions to this? I am on RUI C13
first try to give usb debugging permission while your devices turned on (in RUI C.13) then after you allowed that you can type (adb reboot bootloader) then follow the unlocking steps given on the realme community page
Related
I recently purchased 2 Asus TF103C stocked with Android 4.4.2 and running on an Intel processor. I'd like to load a custom OS/ ROM to them for work however I have not had any success finding a process that allows me to do so. I have managed to root the tablet successfully but that is the extent of my accomplishment to date. I understand that this is a fairly new device and not much has been uncovered yet to achieve this task. Asus is also hesistant to release an unlocked bootlooder update. If anyone is aware of a process whether through adb or the likes please raise your voice to help the community out on this one.
Vibestarter said:
I recently purchased 2 Asus TF103C stocked with Android 4.4.2 and running on an Intel processor. I'd like to load a custom OS/ ROM to them for work however I have not had any success finding a process that allows me to do so. I have managed to root the tablet successfully but that is the extent of my accomplishment to date. I understand that this is a fairly new device and not much has been uncovered yet to achieve this task. Asus is also hesistant to release an unlocked bootlooder update. If anyone is aware of a process whether through adb or the likes please raise your voice to help the community out on this one.
Click to expand...
Click to collapse
Before following steps bellow mentioned don't forget to install USB and ADB drivers
Also download minimal ADB and Fastboot tools ( for links use google search its easily available)
Configure your compute for fastboot Enable USB debugging on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode
$*adb*reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing*
fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>",
fastboot is not configured properly on your machine.
If you see "no permissionsfastboot", try running
fastboot as root.
From the same terminal, type the following command to get info of the bootloader:
fastboot oem-info
To unlock type
fastboot oem unlock
And press enter
May this will unlock your boot loader in general
Press Thanks Button If You like My Work & Posts?
fastboot oem unlock Failed
The-Immortal said:
Before following steps bellow mentioned don't forget to install USB and ADB drivers
Also download minimal ADB and Fastboot tools ( for links use google search its easily available)
Configure your compute for fastboot Enable USB debugging on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode
$*adb*reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing*
fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>",
fastboot is not configured properly on your machine.
If you see "no permissionsfastboot", try running
fastboot as root.
From the same terminal, type the following command to get info of the bootloader:
fastboot oem-info
To unlock type
fastboot oem unlock
And press enter
May this will unlock your boot loader in general
Press Thanks Button If You like My Work & Posts?
Click to expand...
Click to collapse
Hello, I tried your command suggestions to unlock the bootloader and they failed. The command 'fastboot oem-info' does not return anything and 'fastboot oem unlock' returns RESULT: FAIL (unkown OEM command) on the tablet and in the cmd window. Thanks for the suggested attempt nonetheless.
Still having this problem
fastboot oem unlock fails on the TF103C and it says RESULT:FAIL(unknown OEM command). It would be great if Asus could release a tf103c_unlock.apk utility like they have for other Asus tablets (for instance the TF701T has tf701_unlock.apk which works).
Asus, please help!
Hello
A newbie here ...
My new phone "Lenovo Vibe C (A2020)" does not allow me to install any kind of custom recovery on it, I tried the following methods ...
1- SP Flash Tool: doesn't detect my phone at all, even after installing all drivers (Qualcomm, MTK, Etc ,,, ).
2- Adb and fastboot: whenever I try to flash a recovery, it only shows (waiting for a device) command, even after being detected by "adb devices" command, and showing device ID.
3- flashing apps: I used flashify and thrasher, at the beginning they both show a successful flashing process, up until rebooting to recovery, then only shows "Lenovo" logo for a second right before turning the phone off.
that's what i did, any help would be appreciated.
Note: the phone isn't even indexed in the site's database ... I wonder why!
You should unlock the bootloader first after rooting your device
Hello there. I do hope that you can still boot your device normally. If you can, please do make a backup of your rom.
(a) Download and install the latest driver for your device
(b) Download the latest adb and fastboot tool (I recommend Minimal ADB and Fastboot)
(c) Download the custom recovery image. Save/copy it on the root directory of your ADB and Fastboot folder.
(d) In your device, go to settings > developer > enable oem unlocking and usb debugging (which is I guess you already did).
(e) Now open your terminal/cmd: adb reboot bootloader (this will boot your device in fastboot)
(f) In terminal/cmd: fastboot oem unlock (or fastboot oem unlock-go)
(g) Now flash the custom recovery: fastboot flash recovery "recovery.img"
***I suggest you try first if the custom recovery image works: fastboot boot recovery.img
(h) Reboot into recovery and check if it works.
Ospider said:
Hello
A newbie here ...
My new phone "Lenovo Vibe C (A2020)" does not allow me to install any kind of custom recovery on it, I tried the following methods ...
1- SP Flash Tool: doesn't detect my phone at all, even after installing all drivers (Qualcomm, MTK, Etc ,,, ).
2- Adb and fastboot: whenever I try to flash a recovery, it only shows (waiting for a device) command, even after being detected by "adb devices" command, and showing device ID.
3- flashing apps: I used flashify and thrasher, at the beginning they both show a successful flashing process, up until rebooting to recovery, then only shows "Lenovo" logo for a second right before turning the phone off.
that's what i did, any help would be appreciated.
Note: the phone isn't even indexed in the site's database ... I wonder why!
Click to expand...
Click to collapse
Check my thread for custom marshmallow rom and twrp recovery .
https://forum.xda-developers.com/android/general/bliss-rom-lenovo-vibe-c-a2020a40-t3567812
rolland.arriza said:
Hello there. I do hope that you can still boot your device normally. If you can, please do make a backup of your rom.
(a) Download and install the latest driver for your device
(b) Download the latest adb and fastboot tool (I recommend Minimal ADB and Fastboot)
(c) Download the custom recovery image. Save/copy it on the root directory of your ADB and Fastboot folder.
(d) In your device, go to settings > developer > enable oem unlocking and usb debugging (which is I guess you already did).
(e) Now open your terminal/cmd: adb reboot bootloader (this will boot your device in fastboot)
(f) In terminal/cmd: fastboot oem unlock (or fastboot oem unlock-go)
(g) Now flash the custom recovery: fastboot flash recovery "recovery.img"
***I suggest you try first if the custom recovery image works: fastboot boot recovery.img
(h) Reboot into recovery and check if it works.
Click to expand...
Click to collapse
But how about a person WITHOUT PC? Including me.
Hello there. I have a Nokia 6.1 with android 9.0 and i tried to root it. I enabled the developer mode, then enabled usb debugging.
But when i tried to unlock the bootloader, i couldn't because the OEM unlocking option stays greyed out on off. So when i installed adb and fastboot, i tried to boot by adb reboot bootloader but the fastboot can't do anything because it says device is locked.
I even factory reset the device, nothing. Same thing.
What should i do? Preferably not the paid unlock...
Thanks in advance.
Try this (It will wipe the phone, so create a backup of all important files before proceeding):
1. Connect your phone to your PC with an USB cable (make sure you have activated USB debugging in developer options)
2. Run adb
3. Type in adb reboot bootloader
4. Once your phone has rebooted type in fastboot flashing unlock or fastboot oem unlock
You should have unlocked your bootloader and you should be good to go, if it doesn't work then you'll need an unlock key, which unfortunately you'll have to pay for
If you think that you have misunderstood some steps then feel free to reply
Is it possible to install twrp recovery and root using magisk in this phone or not possible because of mediatek processor?
Bhai have patience , this is Mediatek we all know but another thing to notice is This is MT- g95 SoC ?
Orange state in realme 7 when bootloader unlocked but unable to use fastboot.
I have unlocked my realme 7 bootloader with in-depth test built for realme 6 pro. It is working. But now after unlocking the phone factory resets itself and when trying to go into fastboot mode with ADB command ADB reboot bootloader the fastboot verify check fails all the time. So how to go into fastboot mode after bootloader unlock. This issue never happened when I start in-depth test after permissions. It's very strange that even after unlocking the phone is not booting into fastboot mode while giving error in verification. Guys can anyone knows how to solve this. Please reply asap.
Realme 7 After unlocking the bootloader is not going into fastboot mode again.
Can anyone tell when twrp for realme 7 wipp be available
I think i made a mistake by choosing mtk soc because it's hard chance to get twrp for mtk soc
Simple solution realme 7
Senxco said:
I have unlocked my realme 7 bootloader with in-depth test built for realme 6 pro. It is working. But now after unlocking the phone factory resets itself and when trying to go into fastboot mode with ADB command ADB reboot bootloader the fastboot verify check fails all the time. So how to go into fastboot mode after bootloader unlock. This issue never happened when I start in-depth test after permissions. It's very strange that even after unlocking the phone is not booting into fastboot mode while giving error in verification. Guys can anyone knows how to solve this. Please reply asap.
Click to expand...
Click to collapse
I think your adb driver not working please install adb driver reinstall and verfiy fails problem solve, thanks
No no adb driver is working and tested on other devices. I think the problem is with smartphone serial key ( It shows serial key mismatch and therefore fastboot unlock verify fail in fastboot mode).
To Root you phone:-
Download your device boot image > download magisk manager > patch your device boot image > go to fastboot mode > type in command >fastboot --disable-verity--disable-verification > flash vbmeta (fastboot flash vbmeta (put your vbmeta path here) > flash magisk patched image (fastboot flash boot (put your patched file path here) now reboot your phone it will be rooted if on First boot it didn't then reboot your device
I'm at a total loss here...
phone has unlocking and USB debugging toggled on.
phone is not a US phone and unlocking is allowed.
phone goes into fastboot mode (by turning on while holding volume)
"fastboot devices" command returns my phone is in fastboot and connected
"fastboot oem unlock 0xPASSWORD" returns FAILED (remote: 'Command not supported in default implementation')
and fastboot: error: Command failed
I have no idea what to do or try from here.
If I try to flash an image i get:
FAILED (remote: 'Download is not allowed on locked devices')
so, defiantly still locked out of the bootloader
Try below steps
1. Ensure you have platform tools 33.x , 34 has issues.
2. Try to reboot to bootloader from pc.
adb reboot bootloader
3. Try running
fastboot flashing unlock unlockcode
Try it :
fastboot oem unlock
or
fastboot flashing unlock
SOLVED I am so happy. I'm on day 3 of trying to get the phone to bootload.
there is definitely a difference between going into fastboot through the phone itself and through adb commands on PC.
fastboot through the phone shows the drop down menu and no blue light illuminated on phone.
fastboot through adb phone is black screen with a blue light on right corner on the phone.
the windows drivers behave differently between the two. I am running windows 10. phone model XQ-CT72
steps that solved the issue. For anyone in the future.
I downloaded and used platform tools version 33.0.3 NOT version 34.
"adb reboot bootloader" used from windows PC
opened windows device manager found my "discovered device" and forced it to use the SONY driver downloaded from sonys website. It would not detect it on its own, or even use the SONY driver without me telling it to specifically. device manager> "andorid" > properties > update driver > browse computer for driver > installed sony driver
everything worked following these instructions here https://www.droidwin.com/unlock-bootloader-and-root-sony-xperia-1-iv/
alexriethmeier said:
There is definitely a difference between going into ...
Click to expand...
Click to collapse
fastboot, part of the android bootloader, abl
fastbootd, part of recovery
I had same issue and same solution fixed it what you showed and did. I was terrified, after investing so much money on this phone and not getting it unlocked.
You won't need to go through such hassle if you just use Linux VM (a Ubuntu distro will do). The driver works out of the box.