I have a Sony Xperia L3 and i have tried to root but it seems impossible. How can i do it? I have tried to root the phone with Sony Xperia C Root but it could not do it. Kingo Root is the same, fail. Also tried dr.fone but it did not support l3.
You must unlock the bootloader and then follow this steps: https://topjohnwu.github.io/Magisk/install.html
I have check and my phone can be unlocked, i have downloaded fastboot but i do not understand what to do next. I got to step 8 https://www.xda-developers.com/install-adb-windows-macos-linux/ i can see my phone in the command line, what to do next?
I cannot find the fastboot icon under devices and printers
I got to https://mobilewithdrivers.com/unlock-bootloader/sony-xperia-l3-32gb-3gb-ram i got it into fastboot mode but no commands works, fastboot flashing unlock, fastboot oem unlock. Unknown command, command not allowed.
Should i have a unlock code? I only see Xpeira L2 on the site for getting a unlock code, no L3 https://www.getdroidtips.com/unlock-bootloader-xperia-device/
It seems to be something wrong in developer mode, oem do not turn on, no green, it is just off.
Oldschool297 said:
I have a Sony Xperia L3 and i have tried to root but it seems impossible. How can i do it? I have tried to root the phone with Sony Xperia C Root but it could not do it. Kingo Root is the same, fail. Also tried dr.fone but it did not support l3
Click to expand...
Click to collapse
What's phone's Android version? Android 8.1 ? If so, look inside here:
[HOW TO] Root Android 8.1 - DevPreview 1 - OPP5
There are probably already a couple guides up, but I wanted to post about how I went about doing this and have everything working. It may not work for everyone, but for me, it worked the first time. 0: Yep, there is a step zero here. :good...
forum.xda-developers.com
Thanks. I cannot unlock the bootloader to try. I do not get the oem under development mode to work. It is only off. I can't get it on to unlock the bootloader.
Why not contact Sony ?
Sony Support Consumer Electronics
services.sony.co.uk
I tried the guide https://www.kingoapp.com/root-tutorials/how-to-unlock-bootloader-android-device.htm i get it to fastboot and the light is blue but i only get. Failed remote: Command not allowed, Finished. total times 0.045s.
What Fastboot command did you run?
BTW: Install the suitable Fastboot driver provided by Sony, if not already done yet.
I tried
Use the Command Prompt window to retrieve your unlock key as described by your manufacturer. If you own a Motorola device run the command: fastboot oem get_unlock_data, HTC run the command: fastboot oem get_identifier_token.
Select the token which is spit out by the Command Prompt window and copy and paste it into the applicable box of the form on your manufacturer's website without any spaces.
And: fastboot -i 0x0fce oem unlock 0x07B7BFEA7AC879F0 https://www.getdroidtips.com/unlock-bootloader-sony-xperia-x-f5121f5122/
I downloaded android_winusb.inf were should i add it?
Don't understand what you've downloaded. It's an ADB driver.
Contents of relevant ADB driver 's .ZIP-file is
{
"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"
}
To install the suitable ADB driver:
Open the Device Manager. To do this, click Start and type Device Manager. Then click Device Manager.
In Device Manager, right-click the name of your computer at the top of the device list, and then click Add Legacy Hardware.
In the Welcome to the Add Legacy Hardware Wizard dialog box, click Next.
Select Select and install hardware manually from a list and click Next.
Select Show all devices and click Next.
Click Disk....
In the Disk... dialog box, click Browse... click Browse, and then select the driver file with the extension adb (written like this: xxxxxadb, where xxxxxx is the unique file name). Click Open.
In the Disk... dialog box, click... Click OK.
Highlight the Sony xxxxxx ADB Interface Driver file and then click Next twice. The installation starts.
Click Finish and restart the computer.
I get this.
I also tried https://techbeasts.com/how-to-unlock-bootloader-of-sony-xperia-devices-guide/ the problem in fastboot seems to be that i- becomes and unknown option
https://forums.androidcentral.com/t...tloader-fastboot-exe-unknown-option-i.895276/ fastboot R26 seems to work for the most i have the 34. platform-tools v 28.0.0 does not work with the provided command from the official manual.
Yes it was the version, it is the second time i try to mess with andriod phones. I learn more and more. I tried fastboot.exe i- 0x0fce getvar version and i got version 0.5, finished, total time 0.000s
I tried fastboot.exe -i 0x0fce oem unlock 0x and got FAILED, command not allowed. I did only find Sony L, L1 and L2 on sony oem https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code can it be that? I remeber i had a Sony Xperia X code.
I also tried fastboot flashing unlock, FAILED unknown command. with fastboot devices i got my phone visable.
Related
OK, so i am really lost at this point. I have been trying for the past couple of days with no luck.
I used Minimal adb and fastboot, downloaded Lg drivers (LGMobileDriver_WHQL_Ver_4.0.3), sdk google drivers and looked at many comments to figure this out.
i type adb device and my phone shows, I type fastboot device and last couple of my phone shows. I used Mininimal adb and fasboot to unclock the the bootloader and i followed all the commands but when i get to fastboot flash recovery twrpxxxx.img, it tells me cannot load twrpxxxx.img. Also, when i type in adb reboot bootloader in brings me the an LG screen with powered by android at the bottom instead of the correct screen.
So, i tried the other way. Power phone off, hold down the volume down button and plug in usb and bootloader/fastboot opens up ( the screen with the line in the top left, with a blank page). it shows unlocked, few lines in white, and then few lines in red. I type fasboot devices and my phone shows up displaying last couple of the phone sn#. but when i go to type fasboot flash recovery twrpxxxx.img, i get the same message cannot load twrpxxxx.img. and on the phone is shows fastboot getvar partition recovery.
Any idea on what this is and how can i solve this?
Thanks in advance.
Rename it to recovery.img and try again.
I renamed it and I still get the same error. Cannot load recovery.img
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Elu_sama said:
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Click to expand...
Click to collapse
It is in the same folder.
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Figured it out.
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
I suggest you remove and reinstall sdk or install nexus root tools and run a cmd within the updated tools. Make sure you installed the right drivers, delete all others, reinstall, although your error seems more a problem with the tools, permissions perhaps, did you run cmd as admin?
Unable to load tells me it can't find your file.. Perhaps it has a hidden extension? Recovery.img.txt
Whats the complete exact command you're typing?
"fastboot flash recovery recovery.img"
http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
Sounds like this is not enabled
{
"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"
}
Sent from my LG-H901 using Tapatalk
papatoon3 said:
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Click to expand...
Click to collapse
SIM unlocked (tmo has no code, its an app) and bootloader unlocked isnt the same thing.
Never mind got it
papatoon3 said:
Figured it out.
Click to expand...
Click to collapse
What was the solution i need it please and thanks
tanked89 said:
Never mind got it
What was the solution i need it please and thanks
Click to expand...
Click to collapse
When your phone is turned on and plugged in, type command adb devices, Does it show?
Put phone in fastboot mode, type command fastboot devices, does it show?
I figured it out. I had to install motorola and g4 drivers to get fast boot to read when I only had one or the other it was only reading adb when I had both on pc it read and adb & fastboot and worked. Thank you.
Hi sir I am facing a problem I rooted my v10 first I unlocked bootloader and then I rooted it by using fwul I hard reset it but when I turned it on a twrp recovery menu appeared please help that how it fix
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.
Hey all,
--> I'm trying to flash TWRP to my Sony Z5 Compact, but the flash fails during the writing process of the .img file
--> It gives me the following error: FAILED (remote: Command not allowed)
--> I am currently running build number 32.3.A.2.33
--> The phone is NOT rooted (but this should not matter I think... because I cant do that either if I cant write anything to my phone...)
Things that I have already done:
1. I enabled OEM unlocking in the developer options.
2. I enabled USB-Debugging in the developer options
3. The ADB and Fastboot drivers are working correctly
Does anyone know how I can fix this issue? I have already browsed the web for a fix, found a lot of people having the same issue, but nothing has worked for me.
Thanks in advance!
Horizon
i didnt see you unlocked the bootloader, i guess this is the problem
Here link:
https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
its the easy part,
besure you backup everything bootloader for me did factory rest
i did with CMD terminal
{
"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"
}
its always good idea to backup also DRM keys also unlock takes your warranty
A. Install the Android SDK and the device drivers
1. Download and install the Android SDK. The SDK Manager is included in Android Studio, but you don’t need to install more than the basic Android command line tools. These can be found at the bottom of the page.
Tip: Take note of the installation path, you may need to access specific files later.
a. If you are running Windows: You need to install additional drivers.
1. When completing the installation, open the Android SDK Manager and go to the Extras folder to install the Google USB driver.
2. Download and install an updated Fastboot driver. This is the standardandroid_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony devices.
3. Replace the original android_winusb.inf-file with the downloaded file in theusb_driver folder, located in the Android >sdk > extras > google folder on your computer.
b. If you’re running OSX or Linux, you are not required to install any additional drivers.
2. On your device, turn on USB debugging by going to Settings > Developer options and click to enable USB debugging.
a. If your device is Android Jelly Bean 4.2 or newer: Developer options are hidden by default. To enable, tap on Settings > About Phone > Build Version multiple times. Then, turn on USB debugging by going to Settings > Developer options.
B. Connect to Fastboot
1. Turn off your Xperia™ Z5 Compact.
2. Connect a USB-cable to your computer.
3. On your Xperia™ Z5 Compact, press the Volume up button at the same time as you connect the other end of the USB-cable.
a. Windows users: When asked for a driver, open the Devices and Printers directory, click on the fastboot driver and press Update. Browse and point towards the location of the new android_winbus.inf file.
4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder.
5. Enter the following command:
fastboot devices
Click to expand...
Click to collapse
6. Verify that you get an answer back without any errors.
C. Enter unlock key
WARNING! The command below contains your unlock key. If you perform this step, you will unlock the boot loader. This may void your warranty and/or any warranty from your operator.
1. If you still want to unlock the boot loader of your device, enter the following command:
fastboot -i 0x0fce oem unlock 0x(here your code you got by sony)
Click to expand...
Click to collapse
2. Verify that you get an answer back without any errors.
D. Done!
You have now unlocked the boot loader of your device
good luck, update if got it right
PS .i posted my imei by mistake hope i didnt miss to remove another :X
Hey man! Thanks for the quick response! Went right to work with it this morning... and it fixed it!
--> I completely missed the next steps from Sony. for some reason I thought that OEM unlocking option would do the magic lol..
--> After I unlocked it through cmd it was a breeze from there! Got my TWRP on there and the Lineage ROM
Thanks!
Hey!
I am having difficulties unlocking the bootloader of my Redmi Note 5. I have already rooted a meizu phone and a lenovo tablet before and had no problems. However, with this one, I am able to enter the bootloader using the following command.
Code:
adb reboot bootloader
However, when I do this:
Code:
fastboot oem unlock
It outputs the following:
Code:
FAILED (remote: 'Token Verify Failed, Reboot the device')
fastboot: error: Command failed
The command
Code:
fastboot oem unlock-go
outputs the same results and rebooting my phone doesn't resolve the issue.
Additionnaly, using the Miui Unlock App doesn't work because it doesn't recognise my phone when in bootloader.
Please help!
Thanks in advance.
PS: I am using a Win10 64bits PC
Edit: I tried an older version of Miui Unlock and it detected my device, but couldn't unlock it. It stopped at 99% and output "couldn't unlock"
IMHO it's always recommended to check for boot-loader can get unlocked
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
0
Seppppx said:
You are supposed to use the mi unlock tool. Not these simple fastboot commands (xiaomi wants to make unlocking complicated)
Here is a steb-by-step guide
1. Make a Mi account
2. Apply for an unlock here https://en.miui.com/unlock/
3. Download Mi unlock by clicking on the unlock now and then download Mi Unlock.
4. Download the Mi Unlock app to PC, and sign in with your Mi Account;
5. Shut down your phone manually, and hold Volume down key and Power button to enter Fastboot.
6. Connect your phone to PC using USB cable and click "Unlock".
You will probably have to wait some time (3 days, maybe a week or even a month).
it's been some time since I have unlock my Xiaomi phone so these steps might be wrong. If yes point that out please.
Click to expand...
Click to collapse
As I said in my post, I have tried using Mi Unlock. I have done all your steps up to the 6th because the app doesn't allow me to click unlock. I am guessing that it doesn't detect my phone in fastboot mode. About the time I have to wait, is it the time between when I apply for an unlock and when I can unlock my phone? This would explain why I can't unlock it. However I saw on another thread that Xiaomi removed the need to apply and wait to be able to unlock a phone. I don't really know how to feel about this one...
0
Seppppx said:
Do you have fastboot/adb drivers installed?
Click to expand...
Click to collapse
I'm pretty sure I do, because I have already rooted devices before. How do I check?
0
Seppppx said:
To check your drivers (and install) do this.
1. Plug your phone to the Pc.
2. Boot to fastboot (use googles platform tools, download below)
3. Open CMD as an administrator.
4. Navigate to the folder there you have platform tools in.
5. Type "fastboot devices" if you see no output you either have the wrong drivers installed or not installed
(Download the Google USB driver linked down)
6. To install drivers you open your Device Manager in windows.
7. Look for something like "Android Device" there. If it also has a warning sign that means that there are no drivers.
8. Right click on "Android Device"
9. Click on "Update driver"
10. Click on "Browse my computer for driver software"
11. Click on "Let me pick from a list of available drivers on my computer"
12. Click on "Have Disk..."
12. Browser for a driver under "Copy manufacturer's files from:"
13. Find the driver folder in the folder you saved it to and open it.
14. Double click on "android_winusb.inf
15. Click on "OK"
16. Click on "Next"
Done, you have installed a driver.
Download the Google fastboot/adb here https://developer.android.com/studio/releases/platform-tools
Direct download https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Download the google fastboot/adb driver here https://developer.android.com/studio/run/win-usb
Direct download https://dl.google.com/android/repository/usb_driver_r12-windows.zip
Click to expand...
Click to collapse
Well, I tried and went up to step 5 and there was no output. So I continued the steps, on step 7 I saw that my Adroid Device Driver had no warning sign, meaning that I have the wrong drivers. I continued on with your steps. After step 11, the control pannel shows 2 drivers named as "Android Bootloader Interface", however before step 15, the control pannel shows 3 different drivers named as "Android ADB Interface", "Android Bootloader Interface" and "Android Composite ADB Interface". The second one is selected by default, so I click ok and it installs. However, the "adb devices" and "fastboot devices" commands still show nothing in the command prompt. Is there something I am doing wrong?
0
Seppppx said:
You should reboot your phone after installing these drivers. I had the same problem, that fixed it.
Click to expand...
Click to collapse
Still nothing... There is no output to "adb devices" even after I install the driver and reboot my phone.
0
DemonBlu3000 said:
Still nothing... There is no output to "adb devices" even after I install the driver and reboot my phone.
Click to expand...
Click to collapse
{
"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"
}
Xiaomi USB Drivers are essential while connecting your smartphone in Fastboot Mode & Emergency Download Mode [EDL].
Seppppx said:
Do you get an output to "fastboot devices" that's the thing that matters when unlocking. I managed to my redmi note 4 to unlock without adb.
You also can get adb in the classic system where you boot. That works for me.
Click to expand...
Click to collapse
No, "fastboot devices" has no output on my computer, but it has one on another computer for some reason. On mine it doesn't and I need it to on mine.
0
Okay guys I figured it out. I was missing a step. I indeed had to use the Mi Unlock tool, but before doing so I had to enable an option beneath the "OEM unlock option", I don't remember how it was called but everything's fine now!
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