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
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.
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
64875585 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.490s
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
{
"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"
}
Thanks in advance for your help!
dimxr said:
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
Thanks in advance for your help!
Click to expand...
Click to collapse
I had same problem once all I could do was reboot fastboot but since the bootloader was locked but luckily I found this thread https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/ on oneplus forums this really helped hope this will help you
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Are you ready to start? Type y[yes] or n[no]:y
Device mode detected: Fastboot Mode
Device Serial Number: 64875585
Checking bootloader state..
Device bootloader state is: Locked
Do you want to unlock the bootloader? Type y[yes] or n[no]:y
When prompted, Press the Volume Up/Down button to select Yes on the screen, then
press the Power button to Unlock the Bootloader. If it is already unlocked this
will just be skipped and your device will not be wiped.
Sending oem unlock command to device..
Device bootloader is already unlocked so no data will be wiped
Rebooting back to Android..
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
dimxr said:
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Click to expand...
Click to collapse
Being in the same situation right now. Did you manage to come out of it?
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Kéno40 said:
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Click to expand...
Click to collapse
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
MrEasy666 said:
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
Click to expand...
Click to collapse
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Kéno40 said:
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Click to expand...
Click to collapse
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
MrEasy666 said:
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
Click to expand...
Click to collapse
Lucky you. There was no way for me to get to recovery. Something was wrong there.
The only thing that really worked in the end was the Mega Unbrick Guide. I've got my phone back on track and working.
Glad you managed.
This tutorial is based on the Lenovo Z5 Pro(L78031 - NO-GT version) tutorial By BadCluster
.Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here https://devsjournal.com/usb-drivers-for-all-android-devices.html
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here https://devsjournal.com/download-minimal-adb-fastboot-tool.html
Scrolling through the page you will have 2 options: Download or Portable
(choose the one that you prefer)
Pre-Requisite 3
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device (read all tutorial before do it, because it will be wiped all data from the phone)
Settings -> Advanced settings -> Developer Options
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
IMPORTANT NOTE: Before doing this, know that this operation completely reset your device and after rebooting, you will find the phone as if he had just left out of the box. So you'll need to configure your phone again and reinstall all apps.
.Unlock Bootloader
1) Go to: http://developer.zuk.com/bootloader_2
2) Get unlock_bootloader.img:
{
"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"
}
3) Go to your email download file:
4) After getting the unlock file put it in the same ADB folder
5) Now start the phone in bootlader by doing this:
Connect the phone to the PC
Start the Minimal ADB & Fastboot program from the PC
On the PC screen, type:
adb reboot bootloader
(A request may appear on the phone screen with permission of USB debugging, accept it)
The phone will now restart in Bootloader mode.
6) Now that you are in bootloader mode, from the PC, from the screen
Minimal ADB and Fastboot type:
fastboot flash unlock unlock_bootloader.img
sending 'unlock' (0 KB)...
OKAY [ 0.004s]
writing 'unlock'...
OKAY [ 0.019s]
7)Then type:
fastboot oem unlock-go
OKAY [ 0.019s]
8) This is very important: Ready now your bootloader is UNLOCKED however your smartphone will have BootLoop and to arrange you need to do this tutorial: HERE
Done !
----------------------------------------------------------
.How to Lock bootloader again:
IMPORTANT NOTE: Before doing this, know that this operation completely reset your device and after rebooting, you will find the phone as if he had just left out of the box. So you'll need to configure your phone again and reinstall all apps.
1) Now start the phone in bootlader by doing this:
Connect the phone to the PC
Start the Minimal ADB & Fastboot program from the PC
On the PC screen, type:
adb reboot bootloader
(A request may appear on the phone screen with permission of USB debugging, accept it)
The phone will now restart in Bootloader mode.
2) Now that you are in bootloader mode, from the PC, from the screen
Minimal ADB and Fastboot type:
fastboot flashing lock
OKAY [ 0.019s]
6) This is very important: Ready now your bootloader is LOCKED however your smartphone will have BootLoop and to arrange you need to do this tutorial: HERE
Done !
Hi,
I followed the instructions and got "FAILED (remote: Serial number not matched)"
I checked and the SN in Device Info matches the one I've used to generate the file on their site.
Any help is appreciated, thanks.
Adr215 said:
Hi,
I followed the instructions and got "FAILED (remote: Serial number not matched)"
I checked and the SN in Device Info matches the one I've used to generate the file on their site.
Any help is appreciated, thanks.
Click to expand...
Click to collapse
I updated the post, try again now
Hello
My mobile phone has only 7 digits of serial number
Do you know what to do?
yuzu1222 said:
Hello
My mobile phone has only 7 digits of serial number
Do you know what to do?
Click to expand...
Click to collapse
Thanks!
I could do it because of you tought me how to do it.
how to lock lenovo z6 pro again ?
I do not receive a mail. Tried many times with different addresses.
BlueIce84 said:
I do not receive a mail. Tried many times with different addresses.
Click to expand...
Click to collapse
same here
So you can use https://www.zui.com/iunlock instead because "http://developer.zuk.com/bootloader_2" is not working.
1IMEI wont get accepted
0z4ck said:
So you can use https://www.zui.com/iunlock instead because "http://developer.zuk.com/bootloader_2" is not working.
Click to expand...
Click to collapse
I tried the link above and when I input my 1IMEI, is say please put the right 1IMEI.. tried it a couple of times but it wont work.
Before this, my phone have a global rom and rooted.. so what I did is flashed the CN rom, relocked the booteloader to get the update, updated it to latest version then tried to unlock again the bootloader. And btw, I got the phone with unlock bootloader already..
hristcroixqwerty said:
I tried the link above and when I input my 1IMEI, is say please put the right 1IMEI.. tried it a couple of times but it wont work.
Before this, my phone have a global rom and rooted.. so what I did is flashed the CN rom, relocked the booteloader to get the update, updated it to latest version then tried to unlock again the bootloader. And btw, I got the phone with unlock bootloader already..
Click to expand...
Click to collapse
You need to insert a sim card into Sim(Slot1) and connect to the internet and wait a couple of hours. (I waited arround 6 hours)
0z4ck said:
You need to insert a sim card into Sim(Slot1) and connect to the internet and wait a couple of hours. (I waited arround 6 hours)
Click to expand...
Click to collapse
Anyone tried it? I've sold my Z5, because of no root and no custom recovery.
If there is a way to use twrp and root that works 100% I want to buy a new one
After two years I need to replace my Motorola Z2 Force...
How long will i wait for the SN.img be sent to my email.thanks.
Charlemagne Palma said:
How long will i wait for the SN.img be sent to my email.thanks.
Click to expand...
Click to collapse
edited...used gmail and it was sent instantly
i've locked the bootloader, now i'm on a bootloop with oem off, somenone can HELP PLEASE
I used you guide to lock bootlader of my Lenovo Z5 GT Pro.
As written, after bootloaderlock, I had bootloop problem, which I solved using the linked guide.
ALL perfectly working: THANK YOU!
Hi guys,
I received my Z5 with the bootloader already unlocked, but I can't lock it again. I tried the post's method, but it didn't work. When i set the command at the cmd, no message shows in the smartphone. Can someone help me?
Thanks
delete
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?
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.