Hey all!
So I have a LG Tribute Empire, and I want to put LineageOS or some other variant. Its sprint locked and I can't get the bootloader to unlock.
This is what I do on my PC.
Code:
PS C:\Users\****\Desktop\platform-tools> .\adb devices
List of devices attached
LMX220PM89R84PAUZ9 device
Then,
Code:
PS C:\Users\****\Desktop\platform-tools> .\adb reboot bootloader
But all it does is just reboot.
Code:
PS C:\Users\****\Desktop\platform-tools> .\fastboot oem unlock
< waiting for any device >
I can't find anything on the internet to help me. So please help!
To prepare phone for unlocking its boot-loader you must have enabled "OEM unlock" in Settings->Developer option and then have rebooed the phone.
To unlock phone's boot-loader you run this command sequence
Code:
adb devices
adb disable-verity
adb shell "setenforce 0"
adb reboot bootloader
fastboot devices
fastboot flashing unlock [color=red]<- fastboot oem unlock is not applicable for all devices[/color]
fastboot reboot
@jwoegerbauer
I have the "OEM unlocking" turned on already.
When I try
Code:
adb disable-verity
I get
Code:
disable-verity only works for Userdebug builds verity cannot be disabled/enabled - USER build
@That_One_Dude_
Ignore it, proceed with next commands
@jwoegerbauer
Okay so I put them all in order and these are the results.
Code:
[****@****-******** ~]$ adb devices
List of devices attached
LMX220PM89R84PAUZ9 device
[****@****-******** ~]$ adb disable-verity
disable-verity only works for userdebug builds
verity cannot be disabled/enabled - USER build
[****@****-******** ~]$ adb shell "setenforce 0"
setenforce: Couldn't set enforcing status to '0': Permission denied
[****@****-******** ~]$ fastboot devices
[****@****-******** ~]$ fastboot flashing unlock
< waiting for any device >
then,
Code:
[****@****-******** ~]$ fastboot reboot
< waiting for any device >
I have been able to successfully root my Moto G7 without any problem, I don't know why this isn't working.
That_One_Dude_ said:
@jwoegerbauer
Code:
[****@****-******** ~]$ fastboot devices
Click to expand...
Click to collapse
If this command doesn't deliver an output similar to this
{
"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"
}
then your Fastboot driver isn't working at all.
This isn't surprising me because the phone is based on Mediatek chipset what requires to use a conformant Fastboot driver.
@jwoegerbauer
Okay so do I need to install a new Fastboot driver?
@That_One_Dude_
I no longer participate this thread. May be other fellow members will successfully guide you.
I have that phone as well and I am trying to get past the starting area. This chick I got it from didn't give me the pattern after she reset it and gave it to me and so I have no way to turn on ads or click on oem unlocking. So can I even proceed further. Or is the phone just a paperweight now??? I want to try a custom rom if there is any for this sprint variant which I don't even know anything about it's firmware or software and a custom recovery like the twrp touch wiz version. And hopefully root. I heard about its hardware but don't really understand whats wrong with mediatek ik 64bit? Uhmm, so I'm kinda in a worse boat than the other fellow. But if anyone hears this post and I hopefully didn't break any posting rules, I really could or would love the info on it. Thank you. Member newbie
[email protected] said:
I have that phone as well and I am trying to get past the starting area. This chick I got it from didn't give me the pattern after she reset it and gave it to me and so I have no way to turn on ads or click on oem unlocking. So can I even proceed further. Or is the phone just a paperweight now??? I want to try a custom rom if there is any for this sprint variant which I don't even know anything about it's firmware or software and a custom recovery like the twrp touch wiz version. And hopefully root. I heard about its hardware but don't really understand whats wrong with mediatek ik 64bit? Uhmm, so I'm kinda in a worse boat than the other fellow. But if anyone hears this post and I hopefully didn't break any posting rules, I really could or would love the info on it. Thank you. Member newbie
Click to expand...
Click to collapse
Add. Oops
[email protected] said:
Add. Oops
Click to expand...
Click to collapse
Adb dam spell checker.
[email protected] said:
I have that phone as well and I am trying to get past the starting area. This chick I got it from didn't give me the pattern after she reset it and gave it to me and so I have no way to turn on ads or click on oem unlocking. So can I even proceed further. Or is the phone just a paperweight now??? I want to try a custom rom if there is any for this sprint variant which I don't even know anything about it's firmware or software and a custom recovery like the twrp touch wiz version. And hopefully root. I heard about its hardware but don't really understand whats wrong with mediatek ik 64bit? Uhmm, so I'm kinda in a worse boat than the other fellow. But if anyone hears this post and I hopefully didn't break any posting rules, I really could or would love the info on it. Thank you. Member newbie
Click to expand...
Click to collapse
Hey sorry for such a late reply, but i looked and looked and I couldn't find anything about the damn phone almost anywhere.
I have not been able to unlock the bootloader of my LM-X220PM, but I was able to achieve temporary and limited root by following this thread. You will not be able to install a custom ROM on it, but you could block ads, use Titanium Backup, etc.
Related
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
@lost101, Need your expert advice on this. Others, please do help.
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices
lost101 said:
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices
Click to expand...
Click to collapse
Live booted uBuntu Raring Ringtail 13. Added the necessary repositories first ;
sudo add-apt-repository ppa: phablet-team/tools && sudo apt-get update
Click to expand...
Click to collapse
. Further installed the ADB & Fastboot ;
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
. Got success messages.
Further using the terminal, used two commands ;
sudo adb devices
Click to expand...
Click to collapse
sudo fastboot devices
Click to expand...
Click to collapse
The result was exactly the same which i get in Windows command prompt. The list of devices shows a blank. I've installed the drivers and rechecked them, the device is listed as "Motorola ADB Interface" under Device Manager :
and; shows as Fastboot condor S in hardware eject box.
I fail to understand why it isn't showing as connected only in the fastboot menu. Fastboot reason is given as "fall through from not charger boot mode". The device shows only the fastboot screen by default. If any other option like recovery etc is selected, it throws the error message as bootup failed. Scenario is exactly of the same pic which was posted in #1.
Please suggest the next step.
@BBThumbHealer - Starting to look like Bootloader corruption. An unbrick method could be applied to potentially restore a functional Bootloader. One exists for Falcon 5.1 - unsure about Condor at this time.
I would try to eliminate the USB cable as the problem by trying alternatives.
BBThumbHealer said:
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
Click to expand...
Click to collapse
I was stucked in the same problem yesterday. I succeeded and recovered my Moto E to live again.
As in the screenshot you posted. Your bootloader is locked. You need to unloack the bootloader. To do so follow the steps in the link given below :
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Login or create your Moto ID and follow the steps as described.
After that you'll have to flash the firmware again. hope this helps.
Hi guys,
I was following tutorial in order to install stock international FW on my Amazfit 2. However something has failed at step 11, when I was trying to "adb shell reboot bootloader". I got
- exec '/system/bin/sh' failed: Not a directory (20) -
using port=5555
Click to expand...
Click to collapse
Watches are now stuck at amazfit logo and I cannot seem to get to fastboot. Does anybody knows, how to get to fastboot via some key combo on Amazfit 2? I could find just Amazfit solution (this "4 seconds" hint), however it does not seem to work for Amazfit 2...
Any help appreciated, thanks!
Try just this instead:
Code:
adb reboot bootloader
or
Code:
adb reboot-bootloader
Hi thanks for the help,
However I got this idea as well before (based on my general android devices experience) however what it does is that it just reboots normally leading to splash screen stuck. It does not matter whether I issue adb reboot bootloader, adb reboot-bootloader or adb reboot lalala. I think it just grasps adb reboot part only and does normal reboot. However, thank you!.
lfom said:
Try just this instead:
Code:
adb reboot bootloader
or
Code:
adb reboot-bootloader
Click to expand...
Click to collapse
Well, if your watch gets into a bootloop after you use reboot, then something else is wrong... Normal reboot works, just "reboot bootloader" fails?
No, unfortunatelly both normal reboot and reboot bootloader lead to bootloop with Amazfit logo :/
Fastboot finds your device? Can you wipe both data and cache?
{
"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"
}
Only adb devices sees it. But as I cannot get to bootloader, fastboot does not see it, so I cannot do anything...
Have you ever tried to flash another ROM? It seems that system is broken, that's why you get bootloops and cannot get to bootloader. You have to find a way to do it manually, most devices has some combination at start up to activate recovery and/or fastboot...
Make sure fastboot drivers are installed:
https://forum.xda-developers.com/showthread.php?t=2588979
Then check this for manually activate fastboot:
https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
Hi Ifom, thanks again for your energy and willingness to help me.
I would like to flash another ROM, however right for that I would need to get to bootloader. Guide in second link does not work, probably it is intended just for Amazfit 1. This is actually my original question, whether there is something like this for Amazfit 2, because I cannot find it anywhere.
lfom said:
Have you ever tried to flash another ROM? It seems that system is broken, that's why you get bootloops and cannot get to bootloader. You have to find a way to do it manually, most devices has some combination at start up to activate recovery and/or fastboot...
Make sure fastboot drivers are installed:
https://forum.xda-developers.com/showthread.php?t=2588979
Then check this for manually activate fastboot:
https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
Click to expand...
Click to collapse
Poborak said:
Hi Ifom, thanks again for your energy and willingness to help me.
I would like to flash another ROM, however right for that I would need to get to bootloader. Guide in second link does not work, probably it is intended just for Amazfit 1. This is actually my original question, whether there is something like this for Amazfit 2, because I cannot find it anywhere.
Click to expand...
Click to collapse
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
You were right! I can confirm now that this method work also for Amazfit 2, however it is kind of tricky. Took me 20 mins to do it right.
Thank you both for helping me out, I appreciate your friendliness very much!
Quinny899 said:
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
Click to expand...
Click to collapse
Quinny899 said:
Be aware that the method is really hard to get right, it's unlikely you'll get it immediately. It took me maybe 10 minutes of testing to get it to work
Click to expand...
Click to collapse
Take the "Huami_AMAZFIT_Tool_1.0.1.1" and click on "reboot bootloader". This works!
schroepfer said:
Take the "Huami_AMAZFIT_Tool_1.0.1.1" and click on "reboot bootloader". This works!
Click to expand...
Click to collapse
That requires ADB, which requires the watch to at least get to that stage, which isn't the case if you break the kernel
I cannot enter Fastboot Mode.
Quinny899 said:
That requires ADB, which requires the watch to at least get to that stage, which isn't the case if you break the kernel
Click to expand...
Click to collapse
I have an Amazfit and I can't get into Fastboot Mode at all. I have tried all of the alternatives described here many, many times. One question: can Windows / USB port influence not being able to enter Fastboot? Should I try on a Windows 7 for example?
I have searched everywhere and have found nothing does a anyone know of a root method for the T-Mobile REVVL 4 model number 5062z
Texasblazed said:
I have searched everywhere and have found nothing does a anyone know of a root method for the T-Mobile REVVL 4 model number 5062z
Click to expand...
Click to collapse
Because phone is based on Mediatek MT6761 Helio A22 chipset you can use either MTK Easy SU or MTK-SU tool
jwoegerbauer said:
Because phone is based on Mediatek MT6761 Helio A22 chipset you can use either MTK Easy SU or MTK-SU tool
Click to expand...
Click to collapse
wrong, its a qualcomm
So can this device be rooted or not? Correct replies only would be great.
I am actively working towards it. The phone is def TCL....a lot of the package-names give that away. I installed a new Linux distro yesterday in hopes of getting to the bootloader. There might be an added advantage to loading a DSU in Developer Opyions...will update ASAP.
{
"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"
}
like this?
krayzieiyian23 said:
View attachment 5351809like this?
Click to expand...
Click to collapse
I can't get the DSU loader to work on mine. It downlaods and says it's ready so I tap on the PROCEED button or whatever and it just reboots back to my Android 11 Stock over and over.
(
I know little about Android development but I have the device it's not my daily driver so I can test stuff on it and if it goes south it's no big deal. Btw the revvl 4+ is the Qualcomm model, the 4 is the mediatek soc.
clintongsan said:
I am actively working towards it. The phone is def TCL....a lot of the package-names give that away. I installed a new Linux distro yesterday in hopes of getting to the bootloader. There might be an added advantage to loading a DSU in Developer Opyions...will update ASAP.
Click to expand...
Click to collapse
Have you had any luck on this yet???
I selected the first DSu , let it install and now the bootloader is corrupt. ( which im pretty sure means its inoperable) so the verity is definitly disabled. I can load into fastboot and baout to test the fastboot oem unlock.
clintongsan said:
I can't get the DSU loader to work on mine. It downlaods and says it's ready so I tap on the PROCEED button or whatever and it just reboots back to my Android 11 Stock over and over.
Click to expand...
Click to collapse
I was bale to let it install. You gotta downgrade to the first firmware it came with and let the DSU install. My dm-verity is corrupted which is, Im pretty sure disabled, and im able to boot into fastboot
Official Bootloader Unlock for T-Mobile REVVL 4G (TMRVL4G)
Unlock DeVops by selecting build number 5 or 6 times. get usb debugging and fastboot oem unlock. if it is not there go to about phone and select the first DSU. itll reboot and say your dm-verity is corrupted. Was then able to boot fastboot by adb reboot fastboot getting the Android with an exclamation coming out of his chest, held power vol + then pressing vol - fastbootd prompted. once your in fastbootd select reboot recovery and then youll get a recovery, fastboot and reboot selection. select fastboot and then you will be able to fastboot devices. once you get an indication your device is there then I used tiny adb with the command: fastboot flashing unlock_critical. An, are you sure? prompt in adb and press y then enter. it'll unlock the bootloader. and boot Orange_state and tell you your device is unlocked.
Anyone found a stock firmware for this yet?
sketchscarz said:
Official Bootloader Unlock for T-Mobile REVVL 4G (TMRVL4G)
Unlock DeVops by selecting build number 5 or 6 times. get usb debugging and fastboot oem unlock. if it is not there go to about phone and select the first DSU. itll reboot and say your dm-verity is corrupted. Was then able to boot fastboot by adb reboot fastboot getting the Android with an exclamation coming out of his chest, held power vol + then pressing vol - fastbootd prompted. once your in fastbootd select reboot recovery and then youll get a recovery, fastboot and reboot selection. select fastboot and then you will be able to fastboot devices. once you get an indication your device is there then I used tiny adb with the command: fastboot flashing unlock_critical. An, are you sure? prompt in adb and press y then enter. it'll unlock the bootloader. and boot Orange_state and tell you your device is unlocked.
Click to expand...
Click to collapse
I tried this with no luck.
OEM unlock and usb debugging is on.
adb reboot fastboot
This brings me to fastbootd which seems to be the only place for running fastboot commands. I tried going to recovery but theres no option to go to fastboot. I think mine is running anewer version.
fastboot oem unlock gives this error:
FAILED (remote: Command not supported in default implementation)
fastboot flashing unlock and unlock_critical gives this error:
FAILED (remote: Unrecognized command flashing unlock_critical)
Any thoughts or ideas?
mfoster978 said:
I tried this with no luck.
OEM unlock and usb debugging is on.
adb reboot fastboot
This brings me to fastbootd which seems to be the only place for running fastboot commands. I tried going to recovery but theres no option to go to fastboot. I think mine is running anewer version.
fastboot oem unlock gives this error:
FAILED (remote: Command not supported in default implementation)
fastboot flashing unlock and unlock_critical gives this error:
FAILED (remote: Unrecognized command flashing unlock_critical)
Any thoughts or ideas?
Click to expand...
Click to collapse
when yourein fastboot d, in adb type fastboot reboot bootloader
sketchscarz said:
when yourein fastboot d, in adb type fastboot reboot bootloader
Click to expand...
Click to collapse
hmm this justs boots the phone back into the android os
then select reboot to bootloader when in fastbootd
or you can hold the volume up while plugging into your computer until you get fastboot mode at the bottom of the screen, you gotta select the dsu at least once to be able to enable orange state on tmobile boot screen
let it sit there forlike 20 minutes itll say android annd ot boot for a long time.... i let it sit there for about 15-20 minutes
im trying to figure out how to make a twrp for this device ow that the bootloader is unlocked
Hi there! I need some help, I am trying to root my device and need a boot.img, but I cannot find a Rom for the x9 anywhere online.
This is my first time doing this, I got this phone just to mess around with rooting. But maybe I bought a bad phone for it.
If there are no Flash Roms online, what are the next steps? Can I use a Rom for the e9 which released alongside this phone? Sounds like it wouldnt work.. but IDK.
Looking for help from the experts ^^
Any help is appreciated.
Finally found one! Took over 2 hours to download a 2gb file O,O but it's finally done.
Now I am having problems getting into bootloader mode.
In developer mode with both OEM unlocking and USB debugging enabled.
Used the correct cmd prompt (adb reboot bootloader) but the phone just restarts.
I've tried restarting while holding the volume buttons.
VOL Down = Factory Test Mode, nothing works as expected there.
VOL UP = A boot menu letting me select from ~10 options, one of them is Boot to Bootloader. Selecting that simply boots normal, nothing special.
I have followed three guides:
How TO Root Vodafone Smart X9 Magisk without TWRP Recovery
If your Smart X9 is rooted using Magisk without TWRP Recovery. You can control a lot of features such as you can remove unwanted software.
www.getdroidpro.com
Vodafone Smart E9 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Vodafone with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
All seem logical enough, many similarities between them. I just cannot get into fastboot mode.
I've seen LOADS of threads with this same problem on this forum. And none of them have any solutions. So I think this is the end of the road. If nobody has figured it out .. then I am just out of luck I guess?
HalpNeeded said:
Forget, your phone have only 3 buttons
Click to expand...
Click to collapse
Hi @joke19 !
I havnt seen any of the guides mentioning needing a certain amount of buttons :O
How does that factor in - does that mean it cannot be rooted for some reason?
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
{
"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"
}
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
HalpNeeded said:
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
View attachment 5671635
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
Click to expand...
Click to collapse
did you manage to get this working?
For the last few days, I've wanted to install lineage on my phone, because the stock OS is very bad and uses 90% of the ram on idle, and it is full of bloatware and stupid issues. and the UI is not very good.
This whole post is long explaing about my failed efforts, you should read it all to avoid telling me stuff that i tried already.
What i tried?I tried using the basic way, for any android device. I got adb, and fastboot, and did the required steps. When i get into fastmode (after a whole day of fixing why my device is not detected by fastboot by the way), i tried many commands, they all DO NOT WORK in a confusing way, they are not recognized by the phone.
The following are the commands i tried, the response is always the same.
Bash:
fastboot oem unlock
fastboot flashing unlock
fastboot unlock
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
fastboot oem device-info # Yes! even this doesn't work...
And all of them give me the EXACT same response
Bash:
FAILED (remote: unknown command)
finished. total time: 0.002s # The time changes obviously
Ok then i got accross this post. According to the post, i had to use their fastboot. Which.. did not work, because it was stuck at < waiting for device >.
But i did not give up and i looked a bit through github, and i found this repository. I tried it and hopefully it detected my phone. However, the commands mentioned by the post, also gave me the same output of the previous commands, so it was not helpful.
Attempts #2So after this massive and confusing failure, i decided to try again, my friend told me i can use mediatek flash tool (stuff that i can barely understand currently) to flash TWRP, and use it to flash lineage. (Note: The Processor is MT6768)
So. i did a bit of research and i tried a few tools, for example TFTUnlock, SP Flash Tool. We managed to get the scatter file, and it should have worked... but it never did
So the problem with them is when i tried the fastboot method in TFTUnlock, it would try but also get unknown command, even the get device info button had the same problem. I tried the BROM Unlock which did not end up working, because the phone is probably not detected, when i plug it in (even while holding VOL+ and VOL-) i just hear window's sounds about device connection (actually multiple) then it continues charging, as if nothing happened. the application was still waiting for device. (and yes i got the drivers installed, and i had testmode on with driver enforcement disabled).
Wait but only one app did something different. The Smart Phone flash Tool had a special error when i connected usb (even if i do not hold VOL+ and VOL-) i had a special error, instead of just stuck at waiting. here's the error:
{
"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"
}
Other Notes
I tried both Windows 10 and Windows 11
I tried Fedora (fastboot method) and i got the same results
Flashing with fastboot will end up in error Verify State Locked
fastboot getvar command actually gives an output which includes some information, in which says that the bootloader is locked.
I did not forget to enable OEM Unlocking, in case this is on your mind
I had kaspersky on my phone which gave me a weird warning about a firmware change (although i did not success in anything). Here's the screenshot
Thanks in advance for the absolute masters who will help me get this done!
To unlock this phone's bootloader this command is the correct one
Code:
fastboot bbk unlock_vivo
If you get a confirmation message on your screen, reply in affirmative (‘Yes’, ‘I agree’, Unlock the Bootloader’, etc).
jwoegerbauer said:
To unlock this phone's bootloader this command is the correct one
Code:
fastboot bbk unlock_vivo
If you get a confirmation message on your screen, reply in affirmative (‘Yes’, ‘I agree’, Unlock the Bootloader’, etc).
Click to expand...
Click to collapse
I tried that, it says unknown command, as i mentioned already
If Fastboot returns
FAILED (remote: unknown command)
Click to expand...
Click to collapse
then the Fastboot driver you use is a wrong one, means not suitable to phone. Point.
jwoegerbauer said:
If Fastboot returns
then the Fastboot driver you use is a wrong one, means not suitable to phone. Point.
Click to expand...
Click to collapse
Sorry I've been struggling for DAYS about drivers, could you send me the right drivers for my phone?
To be on the safe side request it directly from Vivo.
vivo Support - User Guides, FAQs, Service Center, System Update | vivo Global
Home of official the vivo support services. Here you can check the service center, IMEI, query spare parts prices, system updates, FAQs, and more.
www.vivo.com
jwoegerbauer said:
Request it directly from Vivo.
vivo Support - User Guides, FAQs, Service Center, System Update | vivo Global
Home of official the vivo support services. Here you can check the service center, IMEI, query spare parts prices, system updates, FAQs, and more.
www.vivo.com
Click to expand...
Click to collapse
Interesting, but why would they provide me that? I mean, I'm not a technician or a shop I'm just a user trying to improve my personal phone
jwoegerbauer said:
To be on the safe side request it directly from Vivo.
vivo Support - User Guides, FAQs, Service Center, System Update | vivo Global
Home of official the vivo support services. Here you can check the service center, IMEI, query spare parts prices, system updates, FAQs, and more.
www.vivo.com
Click to expand...
Click to collapse
I tried using the driver but same results