Database Info

Help unlocking/rooting Lenovo Vibe C2 K10a40

So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!

Matt1355 said:
So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!
Click to expand...
Click to collapse
Just because you have the "OEM unlock" option in settings doesn't necessarily mean you can unlock bootloader, the manufacturer or your carrier may have disabled that option in fastboot. Not all devices can be unlocked.
Sent from my SM-S903VL using Tapatalk

still waiting for rooting app, too...

Why God! Why??!! Why Google & Lenovo d'nt just make possible 4 rooting?

Kirzoczek said:
Why Godzin why??!! Why Google d'nt just make possible 4 rooting?
Click to expand...
Click to collapse
Well i'm pissed of. Lenovo just turn off vol up button. U just can't press it in fastboot mode to unlock bootloader. F...... ?

Kirzoczek said:
Why God! Why??!! Why Google & Lenovo d'nt just make possible 4 rooting?
Click to expand...
Click to collapse
Google isn't the the one that has control of that, that's controlled by the device manufacturers and/or each mobile carrier. In this case, it's controlled by Lenovo
The only devices that Google has control over whether they're rootable or not is only the Nexus and Pixel devices, not any of the others.
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
---------- Post added at 04:01 PM ---------- Previous post was at 03:47 PM ----------
Matt1355 said:
So guys, the thing is: I haven't found a way to root nor to unlock the bootloader in this phone.
Focusing on the bootloader, there is an option in the Developer options which says "OEM unlocking", that supposedly allows the bootloader to be unlocked. Plugging the phone on the pc USB and using adb to get into fastboot works fine, but after typing "fastboot flashing unlock" the command prompt keeps on waiting with "..." for the next phone's action, that's where the problem begins: on the cellphone screen, right after the warnings about the consequences of unlocking the bootloader, appears: "Press the Volume UP/Down buttons to select Yes or No." If Volume_Down is pressed, it returns to fastboot, but if Volume_UP is pressed nothing happens, literally nothing, Power button also does nothing, the only one who works is Volume_Down, making it unable to unlock the bootloader via this method.
I tried to use "adb shell input keyevent 24" (knowing it wouldn't work) to try to send the Volume_Up command from the pc.
So I wanna know if there is a way that, through that fastboot waiting instance (the three dots "..."), I can send the Volume_Up command from the pc, enabling the Bootloader to be unlocked, making the root easy or even possible.
Thanks in advance!
Click to expand...
Click to collapse
The command is supposed to be
fastboot OEM unlock
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Yes, you have right. But what with this vol+ button?

Volume+ button is not working on Lenovo C2 ?

GPSSlovakia said:
Volume+ button is not working on Lenovo C2 ?
Click to expand...
Click to collapse
I mean that vol up did' t work in fastboot mode. When u try to unblock bootloader u have two options. U may choose yes or no. Offously vol up is for "yes" answer. And whoop!!! It don't work

How to restore the imei number of this phone ..i tried several methods to restore..pls help me

rijukrishnan said:
How to restore the imei number of this phone ..i tried several methods to restore..pls help me
Click to expand...
Click to collapse
If you didn't make an IMEI backup then we can't discuss restoring your IMEI at XDA, it's in the Forum Rules.
Sent from my SM-S903VL using Tapatalk

then what can i do next to make it in stock condetion

What is this message means

rijukrishnan said:
What is this message means
Click to expand...
Click to collapse
I think it is saying that the connection between PC and your device was interrupted for some reason. I was probably a problem with your cable being loose and losing connection where it plugs into your device.
It is not very likely but it could also be an unstable electrical supply grid in your area, the power in the building where you are could have dropped momentarily, I doubt this was the cause though, but it is one possibility.
Use a different cable or find a way to make sure it connects and stays connected, then try flashing again.
The error you have is described in the attachment below, it explains how to solve.
For future reference, the link below has a list of all flash tool errors and how to solve them.
https://forum.hovatek.com/thread-439.html
Sent from my SM-S903VL using Tapatalk

Droidriven said:
If you didn't make an IMEI backup then we can't discuss restoring your IMEI at XDA, it's in the Forum Rules.
Click to expand...
Click to collapse
i have a bckup of imei number

Eh..,,.... no unlock oem ... no root , bad phone

Droidriven said:
Just because you have the "OEM unlock" option in settings doesn't necessarily mean you can unlock bootloader, the manufacturer or your carrier may have disabled that option in fastboot. Not all devices can be unlocked.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
You can access the recovery for this model after you send the command (ADB and fastboot commands): "Adb reboot recovery" where "Adb reboot boot loader" and then you have to click on the volume up and the power button at the same time and its success
* But the problem is that I have not found the trwp compatible with this model to make the root that can help us

medzbody said:
You can access the recovery for this model after you send the command (ADB and fastboot commands): "Adb reboot recovery" where "Adb reboot boot loader" and then you have to click on the volume up and the power button at the same time and its success
* But the problem is that I have not found the trwp compatible with this model to make the root that can help us
Click to expand...
Click to collapse
TWRP for your device probably doesn't exist, you'll have to wait for someone to be interested in building TWRP for your model (not likely to happen if it hasn't already) or you can port or build your own TWRP.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
TWRP for your device probably doesn't exist, you'll have to wait for someone to be interested in building TWRP for your model (not likely to happen if it hasn't already) or you can port or build your own TWRP.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I do not know how to build twrp for my device you can help me

What about making a TWRP and then flashing it thru modified scatter file in flash tool

[Guide] RCA Voyager RCT6873W42 Unlock Boot loader and root

Root has been achieved for rca tablet, With the intel atom chip
Basic steps are Just like many android devices.
1. Unlock boot loader
2. Flash modified stock recovery
3. Test boot a permissive boot.img
4. Flash permissive boot.img (if test boot was ok)
5. Boot into Custom recovery and flash superSu.
The modified recovery has adb active. This is needed to get back into bootloader mode if flashing goes wrong.
Because on the RCA tablet there is no button combination for bootloader boot mode.
Steps that the included tool performs:
First step tool does is ask soc type. (intel or MTK) for this guide it needs to be intel.
1. Guides user through the bootloader unlock steps.
adb reboot fastboot
verifies the status of unlocked or not
verifies the ability to do unlock in not already unlocked
fastboot flashing unlock
fastboot format userdata
fastboot format cache
fastboot reboot
2. Fastboot boot generic CWM recovery. To use its root shell for copying devices boot.img and recovery.img
3. Use Carliv Android Image kitchen tools to unpack the pulled boot.img and recovery.img
RECOVERY
4. copy adbkey.pub from pc running the patch to stock-recovery\ramdisk\data\misc\adb\adb_keys
copy adbkey.pub from pc running the patch to stock-recovery\ramdisk\adb_keys
this s done to ensure an authorized adb connection to device even after factory reset and data format
5. Edit recovery\ramdisk\default.prop as follows:
"ro.secure=1" to "ro.secure=0"
"ro.debuggable=0" to "ro.debuggable=1"
"persist.sys.usb.config=mtp" "persist.sys.usb.config=mtp,adb"
add line: persist.service.adb.enable=1
add line: persist.service.debuggable=1
6. Use Carliv Android Image kitchen tools to re-pack recovery
BOOT
7. copy adbkey.pub from pc running the patch to stock-boot\ramdisk\data\misc\adb\adb_keys
copy adbkey.pub from pc running the patch to stock-boot\ramdisk\adb_keys
this s done to ensure an authorized adb connection to device even after factory reset and data format
8. Edit boot\ramdisk\default.prop as follows:
"ro.secure=1" to "ro.secure=0"
"ro.debuggable=0" to "ro.debuggable=1"
"persist.sys.usb.config=mtp" "persist.sys.usb.config=mtp,adb"
add line: persist.service.adb.enable=1
add line: persist.service.debuggable=1
9. Edit boot\ramdisk\*fstab* as follows:
"forceencrypt" to "encryptable"
10. Add these lines to boot/ramdisk/init.rc after the line that starts: "on init"
# root use Permissive
write /sys/fs/selinux/enforce 0
11. Swap sepolicy and /sbin/adbd with permissive (insecure) versions included in tool "/img" folder
12. Use Carliv Android Image kitchen tools to re-pack boot
CWM
13. Use Carliv Android Image kitchen tools to unpack the generic CWM
14. copy stock-recovery\recovery.img-kernel to unpacked generic CWM folder (replacing file that is there)
copy stock-recovery\recovery.img-second to unpacked generic CWM folder (replacing file that is there)
15. Use Carliv Android Image kitchen tools to re-pack CWM
SECOND / FLASH MENU
16. fastboot boot patched boot.img
used to verify patched image does not cause device to brick
17. fastboot flash boot patched-boot.img
flashes patched-boot (user must have verified boot image works in previous step)
then formats /data to remove encryption
18. fastboot flash recovery patched-recovery
stock recovery does not seem to work when booted, so test booting pached image not done
this modified recovery is needed to be able to get back to bootloader mode if trouble occurs.
19. Load patched CWM
loads patched recovery to be used to flash SuperSu and also to make device "back-ups"
Updated 2-4-2018 Multi-platform-patch-tool
==>>Multi-platform-patch-tool
Downloads Needed:
Download adb=fastboot 15 second instal == https://forum.xda-developers.com/showthread.php?t=2588979
Download intel drivers == https://software.intel.com/en-us/protected-download/385047/494732
Download SuperSu.zip == https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Thanks:
@vampirefo for most of the needed parts to make this work. CWM, permissive su-policy, without that this would not be possible
@bluefirebird For the image unpack tool
Youtube video I found , of someone explaining how he used the files to root his device.
Video is from before patch tool written. Video was from when individual build files were available.
New method of patching individual device files , removes possibility of flashing files from wrong device.
History of this root method started in this thread.
https://forum.xda-developers.com/general/help/rca-voyager-rct6873w42-rooting-help-t3485625

Tablet hangs on bootloader unlock screen due to the volume keys not responding. Also, on first connect with fastboot flashing unlock, tablet responds with power key every time unless unplugged from usb. Upon second attempt, the power button key issue stops, but the volume keys do not function on the bootloader unlock screen.

Grishak said:
Tablet hangs on bootloader unlock screen due to the volume keys not responding. Also, on first connect with fastboot flashing unlock, tablet responds with power key every time unless unplugged from usb. Upon second attempt, the power button key issue stops, but the volume keys do not function on the bootloader unlock screen.
Click to expand...
Click to collapse
Are you using this with correct drivers?
And with working voyager tablet, with an Intel soc. This does not work with an m version tablet(mtk soc)
I never had problems with volume key not recognized

It's the RCT6873W42 with the Intel Atom. I'll check the drivers, but it reads the power button, just not the volume buttons.
---------- Post added at 04:45 PM ---------- Previous post was at 04:28 PM ----------
I have verified driver installation. Fastboot will not recognize volume up or down. Power button is the only one registering a key event. (4) EV_POWER received.

Grishak said:
It's the RCT6873W42 with the Intel Atom. I'll check the drivers, but it reads the power button, just not the volume buttons.
---------- Post added at 04:45 PM ---------- Previous post was at 04:28 PM ----------
I have verified driver installation. Fastboot will not recognize volume up or down. Power button is the only one registering a key event. (4) EV_POWER received.
Click to expand...
Click to collapse
What about the allow OEM unlock toggle in the developer options screen?
I do not know how to verify key presses as you refer to.
So cannot compare on my end.
There may be different versions released with same model number.
I will make note in the op with the model and build number of my tablet, and can also include a link to the thread where the boot.img was built and tested.
But your problem seems to be before you can even get to that point.

OEM Unlock is enabled. This is my fourth android root, I have yet to ever run into an issue with the volume keys not registering during fastboot. The confirmation screen to unlock the bootloader is visible, but I am unable to select yes or no. The only button that functions is the power key, it times out after 70 seconds. Perhaps if there were a way to extend that timeout period, the volume keys could function. I have attempted removing the usb cable after initiating the flash unlock command, also plugging it into an alternative charger, removed and entered headphones to trigger the volume control. I turned up a search on an individual that had an issue with RCA not programming the volume keys into the Bootloader Unlock screen. Different model, but that was the only thing I managed to find. Strange.

Grishak said:
OEM Unlock is enabled. This is my fourth android root, I have yet to ever run into an issue with the volume keys not registering during fastboot. The confirmation screen to unlock the bootloader is visible, but I am unable to select yes or no. The only button that functions is the power key, it times out after 70 seconds. Perhaps if there were a way to extend that timeout period, the volume keys could function. I have attempted removing the usb cable after initiating the flash unlock command, also plugging it into an alternative charger, removed and entered headphones to trigger the volume control. I turned up a search on an individual that had an issue with RCA not programming the volume keys into the Bootloader Unlock screen. Different model, but that was the only thing I managed to find. Strange.
Click to expand...
Click to collapse
I did see that same issue with an earlier release on an rca tablet.
My build number is :
RCT6873W42-ANDROID6.0-V19-V1.16.50-E04
Kernel:
3.14.0+
Patch level:
June 1, 2016
Also the directions I had when unlocking was to hold volume up button before giving the "fastboot flashing unlock" command to avoid a timing problem.
I did not have the problem either way.

https://forum.xda-developers.com/android/general/firmware-rca-viking-pro-rct6303w87dk-t3325158
That RCA Viking Pro tablet, that was the reference to the volume keys not being programmed.
---------- Post added at 10:34 PM ---------- Previous post was at 10:01 PM ----------
Android Version: 6.0.1
Kernel Version: 3.14.0 Aug 22 19:31:40 CST 2016
Build number: RCT6873w42-ANDROID6.0-V31-V1.17.70-W01
Patch Level: June 1, 2016

I had a dream that it was an SD card holding me back. Sure enough, there was an SD card installed in the tablet which was preventing me from unlocking the bootloader. So as of now, it is unlocked and I will proceed with your directions and post an update shortly.

After flashing the modified boot file on step B, my tablet screen is black with the backlight. I can not interact with the tablet except for volume down disconnecting the device and turning the backlight off. Also
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set;
So basically if the authorization for ADB is gone AND my screen is gone...

I have the RCA Voyager RCT6973W43 will this work on it

Wphall said:
I have the RCA Voyager RCT6973W43 will this work on it
Click to expand...
Click to collapse
Well I have the same model, my screen is now useless after unlocking the bootloader and flashing the first image. Am now searching for a new tablet. The issue immediately began right after rebooting from the successful flashing. Black screen, android set up the os and configured itself, screen still inactive. Debug is disabled now and I have no way to access the tablet via ADB/fastboot now. Out of ideas.
Update
After attempting to blindly access recovery *nothing will display on screen* and I have learned that my volume down button shuts off the screen and disconnects the tablet from my pc for a moment. Also I am positive the touch screen is no longer active, windows picks up the tablet as a storage device. I am thinking that it is the end of for this tablet.

Grishak said:
Well I have the same model, my screen is now useless after unlocking the bootloader and flashing the first image. Am now searching for a new tablet. The issue immediately began right after rebooting from the successful flashing. Black screen, android set up the os and configured itself, screen still inactive. Debug is disabled now and I have no way to access the tablet via ADB/fastboot now. Out of ideas.
Update
After attempting to blindly access recovery *nothing will display on screen* and I have learned that my volume down button shuts off the screen and disconnects the tablet from my pc for a moment. Also I am positive the touch screen is no longer active, windows picks up the tablet as a storage device. I am thinking that it is the end of for this tablet.
Click to expand...
Click to collapse
;;
That is unfortunate. I would have expected you to stop when knew the build numbers and kernel versions were different.
recovery has nothing to do with the boot.img, so your stock recovery should still be there. From powered off hold volume button closer to the usb cable, and the power button for about 10 seconds. the wait for the warning screen to count down. (30 seconds)
should be at recovery.
Do you have the bootloader untrusted screen after unlocking.?
What do you mean "android set up the os and configured itself" ?
did you do the userdata format? that is needed to decrypt the tablet. as the /data area from factory is force-encrypted.

Basically after unlocking the bootloader and flashing the first image... my tablet screen has been rendered useless. It is completely unusable and all of this happened before you posted the version number.
---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------
I followed all instructions described up to the end of Step B. Upon completion of step B, my tablet screen has been rendered useless. Either it conveniently died at the worst time, or something during the flashing caused it. Either way, I have removed the battery, checked connections and can't find anything. Backlight, black screen. 24/7 can't get anything else to display. Can't do a thing with it.
---------- Post added at 12:32 PM ---------- Previous post was at 12:28 PM ----------
Well, I hope this brick helps others not make the same mistake, LOL!
I picked up the tablet for $20 months ago and have been waiting for a root.
Now it's dead so I guess it's time for a better tablet until this one is on sale again!

Wphall said:
I have the RCA Voyager RCT6973W43 will this work on it
Click to expand...
Click to collapse
No, this root is device specific.
Sent from my Life_Max using Tapatalk
---------- Post added at 08:50 AM ---------- Previous post was at 08:49 AM ----------
Grishak said:
Basically after unlocking the bootloader and flashing the first image... my tablet screen has been rendered useless. It is completely unusable and all of this happened before you posted the version number.
---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------
I followed all instructions described up to the end of Step B. Upon completion of step B, my tablet screen has been rendered useless. Either it conveniently died at the worst time, or something during the flashing caused it. Either way, I have removed the battery, checked connections and can't find anything. Backlight, black screen. 24/7 can't get anything else to display. Can't do a thing with it.
---------- Post added at 12:32 PM ---------- Previous post was at 12:28 PM ----------
Well, I hope this brick helps others not make the same mistake, LOL!
I picked up the tablet for $20 months ago and have been waiting for a root.
Now it's dead so I guess it's time for a better tablet until this one is on sale again!
Click to expand...
Click to collapse
Bricking your tablet would be the expected outcome, as this root was never ever meant for your tablet.
Sent from my Life_Max using Tapatalk

Looks like I'll have a nice battery and screen for a raspberry pi.

vampirefo said:
No, this root is device specific.
Sent from my Life_Max using Tapatalk
---------- Post added at 08:50 AM ---------- Previous post was at 08:49 AM ----------
Bricking your tablet would be the expected outcome, as this root was never ever meant for your tablet.
Sent from my Life_Max using Tapatalk
Click to expand...
Click to collapse
I was rooting my tablet from "out of the box" according to the directions, and everything was fine up until the same point. After flashing the modified boot img, formatting userdata and cache, and issuing the fastboot reboot command, now all I get is a backlit screen. Volume down does turn the screen black for a moment then lights back up. The pc sees it as a flash drive, but adb devices doesn't see it at all (not even as an unauthorized device).
My tablet is the correct model. RCT6873W42
I haven't figured out how to get into the recovery. Holding volume up + power, etc doesn't do anything.
---------- Post added at 09:33 AM ---------- Previous post was at 09:17 AM ----------
Grishak said:
Looks like I'll have a nice battery and screen for a raspberry pi.
Click to expand...
Click to collapse
I'm having the identical problem on the identical step you did, and I have the correct model/version.

icaruspony said:
I was rooting my tablet from "out of the box" according to the directions, and everything was fine up until the same point. After flashing the modified boot img, formatting userdata and cache, and issuing the fastboot reboot command, now all I get is a backlit screen. Volume down does turn the screen black for a moment then lights back up. The pc sees it as a flash drive, but adb devices doesn't see it at all (not even as an unauthorized device).
My tablet is the correct model. RCT6873W42
I haven't figured out how to get into the recovery. Holding volume up + power, etc doesn't do anything.
---------- Post added at 09:33 AM ---------- Previous post was at 09:17 AM ----------
I'm having the identical problem on the identical step you did, and I have the correct model/version.
Click to expand...
Click to collapse
All I can think to do at this point is to add an md5 to verify the files downloaded are the ones intended to be used.

It would seem before people try to root their device they should first know and be able to get into recovery before they attempt to root.
If you can't get into recovery via hardware keys, there is no point to continue trying to root your device until you figure that part out.
I don't have the exact tablet in this thread, Mine is close enough though.
to get into my recovery.
press and hold volume down and power until splash screen pops up, I get a splash screen just before count down screen, release and when 30 second count down finishes tablet boots into recovery.

vampirefo said:
It would seem before people try to root their device they should first know and be able to get into recovery before they attempt to root.
If you can't get into recovery via hardware keys, there is no point to continue trying to root your device until you figure that part out.
I don't have the exact tablet in this thread, Mine is close enough though.
to get into my recovery.
press and hold volume down and power until splash screen pops up, I get a splash screen just before count down screen, release and when 30 second count down finishes tablet boots into recovery.
Click to expand...
Click to collapse
I have 49 more of these tablets, still in their boxes, to test with.

[GUIDE][WINDOWS][LINUX] How to unlock your bootloader ! Official and Unofficial way

Hi all,
The main advantage of unlocking the bootloader on Android is rooting. If you want your Android is rooted or if you want a custom ROM to install the unlocking bootloader is an initial step.
/!\ This will erase all of your data !!
You are using Windows ?
Simple but unofficial method :
1) On your device, enable developer options by going to Settings > About Phone, scroll down to Build number and tap 5-7 times to enable developer option.
2) Once you enabled the Developer Options. Returned back to Settings > Developer Options > USB Debugging and OEM Unlock. Just Enable there options.
3) Proceed to put your Xiaomi Mi A2 Lite into Fastboot mode by powering it on while holding Volume Down and Power buttons simultaneously. Hold until you see your phone is booted into Fastboot mode, now connect your phone to your computer.
4) Download Minimal ADB and Fastboot here : https://androidfilehost.com/?fid=962187416754459552
5) Now it’s time to unlock your phone,
Open in operator mode Minimal ADB and Fastboot and enter this command :
Code:
fastboot oem unlock
Your phone will reboot and your data will be erased but your bootloader is now unlocked !
Long but official method :
This method require some days because you have to ask xiaomi to send you an unlock code.
You need Windows it doesn't work on Linux.
1) On your device, enable developer options by going to Settings > About Phone, scroll down to Build number and tap 5-7 times to enable developer option.
2) Once you enabled the Developer Options. Returned back to Settings > Developer Options > USB Debugging and OEM Unlock. Just Enable there options.
3) Proceed to put your Xiaomi Mi A2 Lite into Fastboot mode by powering it on while holding Volume Down and Power buttons simultaneously. Hold until you see your phone is booted into Fastboot mode, now connect your phone to your computer.
4) Go to http://en.miui.com/unlock, click on Unlock button on the webpage now you have to login and then proceed to tap on Download Mi Unlock from the resulting page.
5) After the successful login, the validation process will start on your phone, and for the first time, you will get a message that “You don’t have the permission to Unlock the device”
4) Now click on the “Go” button or use Go to MIUI Unlock page to receive the unlocking permission.
5) Now click on the Unlock Now and log in with your Mi account details and fill all details.
6) You will get a password for confirmation use it to complete the process.
7) Now wait until your application gets approved, you will receive the password on your phone number once it’s approved.
8) Now Open the Mi Flash tool click on unlock and pass the two pop-up.
Your phone will reboot and your data will be erased but your bootloader is now unlocked !
You are using Linux*?
Simple and unofficial methods, official methods doesn't work on linux :
1) On your device, enable developer options by going to Settings > About Phone, scroll down to Build number and tap 5-7 times to enable developer option.
2) Once you enabled the Developer Options. Returned back to Settings > Developer Options > USB Debugging and OEM Unlock. Just Enable there options.
3) Proceed to put your Xiaomi Mi A2 Lite into Fastboot mode by powering it on while holding Volume Down and Power buttons simultaneously. Hold until you see your phone is booted into Fastboot mode, now connect your phone to your computer.
4) Enter these commands in the Terminal :
Code:
sudo apt-get install fastboot
Code:
sudo apt-get install adb
5) Now it’s time to unlock your phone,
In terminal enter this command :
Code:
fastboot oem unlock
Your phone will reboot and your data will be erased but your bootloader is now unlocked !
PS: Sorry for my bad English
Pierre
If I help you, drop a thanks

There's a difference between official and unofficial method? If I unlock my bootloader using the unofficial method what happen? Can I relock it?

[GUIDE][WINDOWS][LINUX] How to unlock your bootloader ! Official and Unofficial way

Hi all,
The main advantage of unlocking the bootloader on Android is rooting. If you want your Android is rooted or if you want a custom ROM to install the unlocking bootloader is an initial step.
/!\ This will erase all of your data !!
You are using Windows ?
Simple but unofficial method :
1) On your device, enable developer options by going to Settings > About Phone, scroll down to Build number and tap 5-7 times to enable developer option.
2) Once you enabled the Developer Options. Returned back to Settings > Developer Options > USB Debugging and OEM Unlock. Just Enable there options.
3) Proceed to put your Xiaomi Mi A2 Lite into Fastboot mode by powering it on while holding Volume Down and Power buttons simultaneously. Hold until you see your phone is booted into Fastboot mode, now connect your phone to your computer.
4) Download Minimal ADB and Fastboot here : https://androidfilehost.com/?fid=962187416754459552
5) Now it’s time to unlock your phone,
Open in operator mode Minimal ADB and Fastboot and enter this command :
Code:
fastboot oem unlock
Your phone will reboot and your data will be erased but your bootloader is now unlocked !
Long but official method :
This method require some days because you have to ask xiaomi to send you an unlock code.
1) On your device, enable developer options by going to Settings > About Phone, scroll down to Build number and tap 5-7 times to enable developer option.
2) Once you enabled the Developer Options. Returned back to Settings > Developer Options > USB Debugging and OEM Unlock. Just Enable there options.
3) Proceed to put your Xiaomi Mi A2 Lite into Fastboot mode by powering it on while holding Volume Down and Power buttons simultaneously. Hold until you see your phone is booted into Fastboot mode, now connect your phone to your computer.
4) Go to http://en.miui.com/unlock, click on Unlock button on the webpage now you have to login and then proceed to tap on Download Mi Unlock from the resulting page.
5) After the successful login, the validation process will start on your phone, and for the first time, you will get a message that “You don’t have the permission to Unlock the device”
4) Now click on the “Go” button or use Go to MIUI Unlock page to receive the unlocking permission.
5) Now click on the Unlock Now and log in with your Mi account details and fill all details.
6) You will get a password for confirmation use it to complete the process.
7) Now wait until your application gets approved, you will receive the password on your phone number once it’s approved.
8) Now Open the Mi Flash tool click on unlock and pass the two pop-up.
Your phone will reboot and your data will be erased but your bootloader is now unlocked !
You are using Linux ?
Simple and unofficial methods, official methods doesn't work on linux :
1) On your device, enable developer options by going to Settings > About Phone, scroll down to Build number and tap 5-7 times to enable developer option.
2) Once you enabled the Developer Options. Returned back to Settings > Developer Options > USB Debugging and OEM Unlock. Just Enable there options.
3) Proceed to put your Xiaomi Mi A2 Lite into Fastboot mode by powering it on while holding Volume Down and Power buttons simultaneously. Hold until you see your phone is booted into Fastboot mode, now connect your phone to your computer.
4) Enter these commands in the Terminal :
Code:
sudo apt-get install fastboot
Code:
sudo apt-get install adb
5) Now it’s time to unlock your phone,
In terminal enter this command :
Code:
fastboot oem unlock
Your phone will reboot and your data will be erased but your bootloader is now unlocked !
Thanks Kineceleran for a solution to avoid the erasing data (I don't test it),
When you get in to fastboot mode hold to volume down button before and write "fastboot oem unlock" don't release until phone shows mi logo at the startup.
PS: Sorry for my bad English
Pierre
If I help you, drop a thanks

Actually you could avoid the erasing data
When you get in to fastboot mode
hold to volume down button before and write "fastboot oem unlock" code
dont release until phone shows mi logo at the startup.

Kineceleran said:
Actually you could avoid the erasing data
When you get in to fastboot mode
hold to volume down button before and write "fastboot oem unlock" code
dont release until phone shows mi logo at the startup.
Click to expand...
Click to collapse
Thanks for that I added this in the main post

Pierre_C said:
Thanks for that I added this in the main post
Click to expand...
Click to collapse
Usually i select the option "clean all and lock" on mi flash when i flash stock rom(for being pure).
I tried vol down method several times you can try this
sorry for my bad english tho :/

ohh no, the 100st thread about unlocking bootloader on original android-devices. And that in double

harvey said:
ohh no, the 100st thread about unlocking bootloader on original android-devices. And that in double
Click to expand...
Click to collapse
Yes but not for the Mi A2 lite and double post is a mistake

Pierre_C said:
Yes but not for the Mi A2 lite and double post is a mistake
Click to expand...
Click to collapse
And whats the difference between "fastboot unlock oem" for windows/linux or unlocking mia2 or mia2lite or google-pixels? There is no.
by the way: your tip on linux to make an "apt-get install fastboot/adb" could load an older version of this apps (depends on the distribution) which are not able to handle a/b formatted phones. so be careful!
Everybody who wants to root looks at the "rooting" threads, and in the a2lite threads for rooting in their 1st posts you can read how to unlock bootloader. No necessary for another "tutorial" imho.
And another by the way: Why is the fastboot-method "inofficial"? That are the tools from google themself for developing android.
Your "official way" is only needed if you have xiamoi-phone with miui on it.

What's the point of requesting the bootloader unlocking code from Xiaomi if it's as simple as running a command in fastboot with no strings attached?! Am I missing something?
Can someone clarify if the Mi A2 Lite, not being a MIUI device, needs the Xiaomi Unlocking procedure?
NOTE: Afaik, avoiding the data-wipe after unlocking the bootloader works for as long as you don't go into recovery mode, because the wiping task stays pending forever and some day you'll enter recovery and get your phone wiped anyway.

joint.striker said:
What's the point of requesting the bootloader unlocking code from Xiaomi if it's as simple as running a command in fastboot with no strings attached?! Am I missing something?
Can someone clarify if the Mi A2 Lite, not being a MIUI device, needs the Xiaomi Unlocking procedure?
NOTE: Afaik, avoiding the data-wipe after unlocking the bootloader works for as long as you don't go into recovery mode, because the wiping task stays pending forever and some day you'll enter recovery and get your phone wiped anyway.[/QUOTE
yes sounds not too good ending up with a wiped storage all of a sudden, but if after unlocking bootloader you install twrp and root the phone iam pretty sure the pending wipe will be gone, cheers
Click to expand...
Click to collapse

just to be clear whats the difference between the official and unofficial way?
does warranty status change depending on which way you use?

joint.striker said:
NOTE: Afaik, avoiding the data-wipe after unlocking the bootloader works for as long as you don't go into recovery mode, because the wiping task stays pending forever and some day you'll enter recovery and get your phone wiped anyway.
Click to expand...
Click to collapse
Can someone confirm this? I'm about to root one A2 Lite and would love to keep the data on.
Thanks!

Does this unlock process on linux works for xiomi MI redmi note 5 pro or not...!

Hi.
I'm trying to unlock A2 Lite from EndeavourOS (Arch Linux).
Installed ADB/fastboot (sudo pacman -S android-tools):
Android Debug Bridge version 1.0.41
Version 33.0.3p1-android-tools
However when executing "fastboot oem unlock" command, it hangs with the below:
< waiting for any device >
The device itself is visible when checking with "adb devices" command:
List of devices attached
3e334c3d0205 device
Are there perhaps some additional steps or soft I'm missing? Any idea what could be wrong?
Thanks in advance.

Hi,
Here is a great way to do it. Worked very well for me:
https://forum.xda-developers.com/t/guide-vm-xiaomi-unlock-bootloader-using-linux-and-mi-unlock-tool-or-any-other-virtual-machine.4569985/

Samsung Xcover6 unlock bootloader (SM-G736B) before rooting

Wanting to root the device via magisk, I tried first to unlock the bootloader of my phone but apparently failed.
I started by activating the developer mode, set oem unlocking developer option in the settings then tried adb reboot bootloader : no success, the phone simply rebooted. A fastboot oem unlock just hung out waiting for a device.
I can go into download mode or recovery mode if that may help...
Any idea how to unlock this bootloader ? How can i check it is effectively unlocked ?
Thanks in advance for any help

It's well known that SAMSUNG mobiles don't have the Fastboot feature: there it's the Download mode.
FYI:
Power off your device. Press Volume Up + Volume Down and plug in your device to a PC to boot into download mode
When you enter download mode, Long press Volume Up button to unlock the bootloader.

ok well, let's forget about fastboot command then.
I'll answer myself on the original question, to unlock the bootloader:
switch off the phone
press volume up and volume down key
plugin a usb cable
choose "device unlock" with a long press volume up
after released the key up, choose "unlock" with volume up again
Now I'm looking to enter the download mode which I can't reach anymore. Any idea xXx yYy ?

Answer myself again
Apply the 3 first steps of my previous answer, you'll be in the same unlock screen as before but the first option will be "Continue". Choose it with volume up and you will end up in download mode !
Now I'll try rooting with magisk...

Rooting with magisk 25.2 done by a classical patching of AP from november release: AP_G736BXXU1BVK2_G736BXXU1BVK2_MQB58744363_REV00

It appears that this is the only thread on the entire forum for this phone?
Having just bought one for the removable battery and the dual SIM, I discovered that samsung in their infinite wisdom disabled the multiple users feature in their oneUI ROM, which really sucks because that was part of the reason I wanted the phone, to segregate certain apps into their own user account.
This all made me realize Root + custom ROM is probably the only way I will ever get that basic functionality returned.
So here I see that rooting is doable, but there appears to be zero results for un-samsung'd ROMs.

Which market is G736B? I was looking at ordering but I am in the US and the Samsung site is giving me the SM-G736UZKEXAA. Would the classical patching work on that?

The G736B model is sparsely distributed in EU, Asia, Africa and Oceania (see here). Your G736W US model is also based on Snapdragon 778G, it is probably the same phone with a few subtleties concerning 5G support (if any, can't find out) and software bloatware. I'd be surprised the above patching doesn't work but ... it's only a guess !

geekall said:
Wanting to root the device via magisk, I tried first to unlock the bootloader of my phone but apparently failed.
I started by activating the developer mode, set oem unlocking developer option in the settings then tried adb reboot bootloader : no success, the phone simply rebooted. A fastboot oem unlock just hung out waiting for a device.
I can go into download mode or recovery mode if that may help...
Any idea how to unlock this bootloader ? How can i check it is effectively unlocked ?
Thanks in advance for any help
Click to expand...
Click to collapse
you da real mvp bro