Related
Hello all,
First of all let me tell you that I am a total noob when it comes to Android phones, rooting, flashing, bricking (and all other terms that I have seen on my screen the last couple of days! )
I have an LG L5 from my sisters husband which in turn got this phone from a client (which is in fact LG). I understand that this is some sort of developers model, as there is a message in the screen that says 'User Debug Mode'.
The phone works (well... ), but not like you would expect. First of all there is not much on the phone (just: Camera, Cell Broadcast, Contacts, FM Radio, Messages, Phone, Options). The camera does not seem to work. Although I can make pictures, it seems they are not stored anywhere. Also, when I press the 0 button in Phone, I get this menu 'AAT Device Test'.
All I want at this time is to be able to use the phone, but I have no idea on how to proceed,..so.....H E L P!
I downloaded the LG Suite, drivers, new .kdz (V10b) and the kdz updater, but trying to update this phone does not seem to work.
Model Nr.: LG E610
Android version: 4.0.3.
Kernel version: 3.0.8-perf+
Software version: LG-E610-V09d_pre2-APR-21-2012
I hope someone can help me get rid of this User Debug Mode and enable me to use this phone! If anymore info is needed, please let me know and I'll try to provide you with as much as I can!
Thanks in advance!!
[email protected] said:
Hello all,
First of all let me tell you that I am a total noob when it comes to Android phones, rooting, flashing, bricking (and all other terms that I have seen on my screen the last couple of days! )
I have an LG L5 from my sisters husband which in turn got this phone from a client (which is in fact LG). I understand that this is some sort of developers model, as there is a message in the screen that says 'User Debug Mode'.
The phone works (well... ), but not like you would expect. First of all there is not much on the phone (just: Camera, Cell Broadcast, Contacts, FM Radio, Messages, Phone, Options). The camera does not seem to work. Although I can make pictures, it seems they are not stored anywhere. Also, when I press the 0 button in Phone, I get this menu 'AAT Device Test'.
All I want at this time is to be able to use the phone, but I have no idea on how to proceed,..so.....H E L P!
I downloaded the LG Suite, drivers, new .kdz (V10b) and the kdz updater, but trying to update this phone does not seem to work.
Model Nr.: LG E610
Android version: 4.0.3.
Kernel version: 3.0.8-perf+
Software version: LG-E610-V09d_pre2-APR-21-2012
I hope someone can help me get rid of this User Debug Mode and enable me to use this phone! If anymore info is needed, please let me know and I'll try to provide you with as much as I can!
Thanks in advance!!
Click to expand...
Click to collapse
Mate head here so that all your issues can be addressed:
Lg Optimus L5
prasad12ka4 said:
Mate head here so that all your issues can be addressed:
Lg Optimus L5
Click to expand...
Click to collapse
I did at first, but there were so many subjects in just one thread, that I thought it might get cluttered. I'll repost it in that thread. :good:
Have you tried this? http://forum.xda-developers.com/showpost.php?p=36688645&postcount=808
And followed it's steps exactly?
If so, you can also try this:
Follow step 1-4 from previous linked tutorial
5. Remove the battery of your phone and re-insert it (don’t turn it on).
6. Connect the USB cable to your PC, wait to connect it to the phone.
7. Press and hold volume up and volume down together, while connecting the USB cable to the phone. A screen will appear with a message
saying something about downloading.
Continue with previous linked guide from step 8 to 14
ldeleeuw said:
Have you tried this? http://forum.xda-developers.com/showpost.php?p=36688645&postcount=808
And followed it's steps exactly?
If so, you can also try this:
Follow step 1-4 from previous linked tutorial
5. Remove the battery of your phone and re-insert it (don’t turn it on).
6. Connect the USB cable to your PC, wait to connect it to the phone.
7. Press and hold volume up and volume down together, while connecting the USB cable to the phone. A screen will appear with a message
saying something about downloading.
Continue with previous linked guide from step 8 to 14
Click to expand...
Click to collapse
Yes, I did and I keep getting the wparam 100 and lparam 6 error. The phone will say on 'Downloading blabla...Do not remove cable'.(I did run it as administrator)
As for Step 5. The phone does not go into Emergency mode. When I do it, the phone will say it is in Safe Mode (maybe the same?).
[email protected] said:
Yes, I did and I keep getting the wparam 100 and lparam 6 error. The phone will say on 'Downloading blabla...Do not remove cable'.(I did run it as administrator)
As for Step 5. The phone does not go into Emergency mode. When I do it, the phone will say it is in Safe Mode (maybe the same?).
Click to expand...
Click to collapse
I'm afraid you'll have to go trough a process similar to this: http://forum.xda-developers.com/showthread.php?t=1861942
It was written for another LG phone, but the situation is comparable
ldeleeuw said:
I'm afraid you'll have to go trough a process similar to this: http://forum.xda-developers.com/showthread.php?t=1861942
It was written for another LG phone, but the situation is comparable
Click to expand...
Click to collapse
Thanks mate! That does all sound very familiar. My phone also has Not For Sale engraved on the inside and also the KDZ updater does not seem to work. I have posted a reply in/on that thread to see if anyone can tell me if this works for the L5 too. :good:
This phone is nearly 2-3 weeks old, I had been transferring stuff over to a sd card cause I had filled up the internal space so quickly. I than realized that I had certain apps still downloading to my internal storage and it filled up to near capacity and the OS began to misbehave, ASUS launcher would not respond and crash, as well as various background applications as you would assume would crash due to low memory allowed. Before I had a chance to delete or transfer anything more ASUS launcher kept crashing repeatedly so I restarted it. At first it came back on with a blank screen but I could feel the pattern to unlock the encryption during the boot, so I hard restarted it, and it will show the first AT&T logo then allow me to decrypt with a pattern then it goes to another AT&T logo where it just sits, it doesn't freeze you can see the subtle animation of the logo, but it doesn't proceed any further. When I go into recovery I'm only allowed 3 options, restart, update via adb, update via microSD, there is no factory reset, or clean cache.? In fast boot mode I'm presented with the following information if it is of any use:
Product_Name - ATT_Phone
VARIANT - ASUS ZenF
HW_VERSION - 4
BOOTLOADER VERSION - 2.52
IFWI VERSION - 91.37-DEV
IMEI - 0123456789ABCDEF
SKU VERSION - ZE500CL_EU_US
SECURE_BOOT - ?
----
Any advice or help would be deeply appreciated, I'm going to try and reinstall the firmware or upgrade it, but is there any way to wipe the cache with fast boot? Or something else I'm not thinking of? Thank you.
cmd: fastboot erase cache
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
From fastboot obviously
Sent from my ASUS_Z00AD using Tapatalk
I hadn't yet enable debug mode on the phone yet am I still able to use adb?
I should mention an important bit of information I am currently using mac osx the most current version, and I'm getting various errors when I attempt to use fast boot for example;
ERROR: Unable to create a plug-in (e00002be)
No one can assist? Or point in a direction? I've scoured a range of threads pertaining to this very issue with luck in only finding fragments of information that has been helpful.
frivolous said:
No one can assist? Or point in a direction? I've scoured a range of threads pertaining to this very issue with luck in only finding fragments of information that has been helpful.
Click to expand...
Click to collapse
unplug all other devices. fastboot is a little finicky on recent OSX versions. Just remove all other devices and re-plug your phone.
I have tried that but the keyboard is usb, the mouse is bluetooth. I can input the commands but I don't know how I can press enter when I unplug the keyboard. Any ideas?
Hmm have you tried charging then turn it on
Hello Guys
My friend ask me for get a Lineage OS to his H815 with Nougat. I agreed as I made few successful changes from stock to Lineage OS with Samsungs and older LGs (like L3 E400). But G4 is really more complicated, more than I expected . Firstly I wanted to unlock this phone with FWUL, so I download a VirtualBox emulated image with FWUL and after it boots I opened SALT program and it detects the phone. I made a basic backup and then I choosed Unlock G4 (UsU). After that some windows pop up. Last window was a pre-checking, when the bar gets to the end window closed and nothing more was happening. So after almost hour of waiting I just turned off the phone - I thought its all. After that while phone is booting I have those messages in the left top corner:
[820]-----------------------
[870]
[920] Secure boot error!
[970] Error code : 1009
[1020[ OFFICIAL !!
[1070]
[1120]-----------------------
Its booting, but only sometimes its normal boot, most starts are with bootloop, sometimes its start after 10 restarts, sometimes after 2nd restart, sometimes after plug in/plug out USB cable it starts boot normally (connecting cable only to phone, not to PC), sometimes only thing that helps is to take out the battery. I made full wipe to be sure that its not a software problem, but only thing I achived with that is fact that phone has a Nougat and now it have a Marshmallow. It is (was?) H815, but now model name is LGLS991 (?), it gets very long until it shows software version (V20g), IMEI is unknow, even when I type *#06# I get the null response.
I can get into recovery, can put phone into download mode. But i'm not able to do anything to get LOS or a least Nougat.
I've read many, many tutorials how to get G4 working properly after unsuccessful unlock, but nothing helps. What I've tried:
1. Flashing stock Nougat for H815 with LGUP, installed USB drivers, proper DLL, set com to 41, but when I trying to flash, after a 4% i get error: KDZ file is invalid. Downloaded few KDZ firmwares, dont belive that every single one is invalid, there is something wrong with LGUP or with settings, but I cant find what
2. Flashing with LG Flash Tool 2014: tried both normal flash and cse flash and always stoping in the same moment, with "Connection to server failed. Try again in a moment". Read many tutorials about this error, none was helpful in my case.
3. Flashing with LG Flash Tool v1.8.1.1023 and a TOT file, but after select of dll and tot file and press the yellow arrow I get an error: "Failed PreviousLoad()"
Tried all this methods on second computer but without a luck.
What else can I try to get this G4 working properly? Maybe try to install some rom from stock recovery? But which rom will be ok and dont get things worst?
If you need more info dont hesitate to ask. Would be very greatful for any advices .
you definitely didn't read enough... go to read again the UsU thread and as you've read the whole tutorial, you can also read the whole FAQ and the OP, because 90% of what you pointed out in your publication (which incidentally is in the wrong section) is explained there.
A quick advice: Don't try to flash any KDZ/TOT again.
I'm sorry if the post is not in the right place.
I own a z2 force that turned itself off and the rear camera did not work.
Putting the "power low" message on the recovery screen, even when the full charge appeared, after a time off "power ok" was displayed.
One moment he did not call any more and I tried bootloader, but without being able to activate usb debugging (my fatal error!), Now the message "your device is corrupted. It can not be trusted and it does not boot" and I can not unlock bootloader nor flash a new rom to boot the device.
obs: camera and battery problems appeared after the upgrade via ota to 8.0 actions
Solved.
eriton carlos said:
I'm sorry if the post is not in the right place.
I own a z2 force that turned itself off and the rear camera did not work.
Putting the "power low" message on the recovery screen, even when the full charge appeared, after a time off "power ok" was displayed.
One moment he did not call any more and I tried bootloader, but without being able to activate usb debugging (my fatal error!), Now the message "your device is corrupted. It can not be trusted and it does not boot" and I can not unlock bootloader nor flash a new rom to boot the device.
obs: camera and battery problems appeared after the upgrade via ota to 8.0 actions
Click to expand...
Click to collapse
I was able to start the device after hours looking for a solution, now I'm flashing a new rom to try to fix the camera problem and automatic shutdown.
How do you solve it?
I usually buy second hand Motorola phones (also this ATT Z2F), but I've never met the problem on individual hardwares yet (like camera, fingerprint sensor). Almost errors can be solved via flashing a right firmware. I think you can now flash fw via Lenovo Moto Smart Assistant (LMSA). If you use flashall.bat method, just take a look at the xml file and compare it to the content of flashall.bat (two types can be opened by Notepad, Notepad++ is recommended). The xml one shows what will be flashed.
For example: in the xml one has oem.img_sparsechunk.0-1-2, but in flashall.bat only has: fastboot flash oem oem.img
If you continue, your phone won't boot.
You have to edit flashall.bat:
fastboot flash oem oem.im_sparsechunk.0
fastboot flash oem oem.im_sparsechunk.1
fastboot flash oem oem.im_sparsechunk.2
Save and continue your works.
The xml is the standard file for RSD Lite. But, RSD seems not to be supported on recent PC hardwares, so step-by-step fastboot or flashall.bat is recently used. Therefore, just take a look before flashsing (other preparations won't be mentioned here). You should flash the equal or higher version to your current fw version on your phone.
Hope this works for you all.
i'm facing same problem,
eriton carlos said:
I was able to start the device after hours looking for a solution, now I'm flashing a new rom to try to fix the camera problem and automatic shutdown.
Click to expand...
Click to collapse
how you get repaired your phone?
I am following the instructions from motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
I've downloaded Motorola drivers for Mac, as well as platform-tools. I am booting the phone to booloader but then a weird barcode shows up: imgur.com/a/8sT2lds
Any idea how to make progress from there? By the way my phone model is XT2029-2
Nycticorax said:
I am following the instructions from motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
I've downloaded Motorola drivers for Mac, as well as platform-tools. I am booting the phone to booloader but then a weird barcode shows up: imgur.com/a/8sT2lds
Any idea how to make progress from there? By the way my phone model is XT2029-2
Click to expand...
Click to collapse
Would like to know it too. Passed some days searching the web for a answer, and got none. The only thing I get when scanning the barcode is a number that AFAIK doesn't match any serial nor anything at all in the phone; just a number from what I can tell. Using fastboot oem get_unlock_data doens't work at all too, I just get a "command unknown" error returned from fastboot. Tried different drivers, none seemed to work, and the only ones that did, gave me the barcode and the fastboot error when trying to unlock. A very weird error, this one; fastboot devices work just fine, fastboot getvar all too, so it really doesn't seem like a fastboot or driver issue. My last try was this article (https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/) to see if I could get a list of the phones OEM commands and figure out how to unlock it. Tried to extract the bootloader from the firmware I downloaded online, using a tool I found on the forum, but no success until now. Will try to root the phone and extract it as it is shown in the tutorial to see if I can get more lucky. I saw somewhere that there's an app called sunshine that was used to unlock some older models, maybe you wanna try that too. I won't, because it's paid and I don't have the money to pay for it . Anyway, I'll try the bootloader extracting and see how that works, and depending on the output, maybe I'll post a tutorial here.
Def4lt_ said:
Would like to know it too. Passed some days searching the web for a answer, and got none. The only thing I get when scanning the barcode is a number that AFAIK doesn't match any serial nor anything at all in the phone; just a number from what I can tell. Using fastboot oem get_unlock_data doens't work at all too, I just get a "command unknown" error returned from fastboot. Tried different drivers, none seemed to work, and the only ones that did, gave me the barcode and the fastboot error when trying to unlock. A very weird error, this one; fastboot devices work just fine, fastboot getvar all too, so it really doesn't seem like a fastboot or driver issue. My last try was this article (https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/) to see if I could get a list of the phones OEM commands and figure out how to unlock it. Tried to extract the bootloader from the firmware I downloaded online, using a tool I found on the forum, but no success until now. Will try to root the phone and extract it as it is shown in the tutorial to see if I can get more lucky. I saw somewhere that there's an app called sunshine that was used to unlock some older models, maybe you wanna try that too. I won't, because it's paid and I don't have the money to pay for it . Anyway, I'll try the bootloader extracting and see how that works, and depending on the output, maybe I'll post a tutorial here.
Click to expand...
Click to collapse
Ok so after analysis the barcode just the IMEI associated with my SIM card's slot. (This phone has two SIM card slots.) Nothing interesting about it, I think.
Also it seems that Motorola does not support unlocking this bootloader as it does for other phones; in fact "motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a" is just a hub for any phone listed at "support.motorola.com/us/en/solution/MS87215", and this one is not on the list. I am not aware of any way to unlock the bootloader in these circumstances.
Please let me / us know if you are more successful than me. For now I will consider this phone not rootable via this method.
PS: The furthest I've been: `fastboot oem get_unlock_data` returns a blank line as if the mobile was working. No error message or anything.
PPS: What do you mean by "extracting the bootloader"? What rooting method is extracting the bootloader part of?
The official list of devices that can be unlocked has never been complete.
Usually all moto models can be unlocked, except Carrier branded devices or those on Amazon software channel.
Those getting the barcode screen, is that from
Pressing the volume down button and power on, or
adb reboot bootloader
?
Sent from my ali using XDA Labs
Nycticorax said:
Ok so after analysis the barcode just the IMEI associated with my SIM card's slot. (This phone has two SIM card slots.) Nothing interesting about it, I think.
Also it seems that Motorola does not support unlocking this bootloader as it does for other phones; in fact "motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a" is just a hub for any phone listed at "support.motorola.com/us/en/solution/MS87215", and this one is not on the list. I am not aware of any way to unlock the bootloader in these circumstances.
Please let me / us know if you are more successful than me. For now I will consider this phone not rootable via this method.
PS: The furthest I've been: `fastboot oem get_unlock_data` returns a blank line as if the mobile was working. No error message or anything.
PPS: What do you mean by "extracting the bootloader"? What rooting method is extracting the bootloader part of?
Click to expand...
Click to collapse
That's weird. My barcode number doesn't seem to match any numbers at all, serial, IMEI, nothing. I'll double check it to see if I have missed something. Never got this blank line, would be happy if you shared how you achieved it, maybe there could be some insight I can get from the process. Answering the question about the bootloader, the extraction isn't a part of a rooting method, it's only something I'm trying in order to get the list of oem fastboot commands of the phone. Those are manufacturer-specific, aren't listed anywhere, and differ from model to model. The method I'm using is the one from the article I pointed in my previous answer. Anyway, if it takes me anywhere, I'll bring an update about it with details.
---------- Post added at 23:36 ---------- Previous post was at 23:04 ----------
sd_shadow said:
The official list of devices that can be unlocked has never been complete.
Usually all moto models can be unlocked, except Carrier branded devices or those on Amazon software channel.
Those getting the barcode screen, is that from
Pressing the volume down button and power on, or
adb reboot bootloader
?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
The barcode is from entering the bootloader. Any method that gets you there shows it. At first I thought it was a driver-related bug, but after some experimentation it seems like whenever the device is recognized by fastboot, it shows this barcode; So it appears to be a bootloader-related thing (I never saw nothing like it, so just guessing for now). Also tried the method from the Motorola website, and I really wish it had worked as expected, but what it seems to me is that MediaTek devices are a pain in the ass in general for this kind of thing. The device doesn't recognizes the oem commands sent through fastboot as valid (And yes, OEM Unlocking is properly enabled under Developer Settings). Here's a screenshot from a powershell session showing the results of trying the commands. Notice how the device is correctly recognized by both adb and fastboot, only the unlocking commands doesn't work: https://pasteboard.co/JnW4cvK.png
sd_shadow said:
The official list of devices that can be unlocked has never been complete.
Usually all moto models can be unlocked, except Carrier branded devices or those on Amazon software channel.
Those getting the barcode screen, is that from
Pressing the volume down button and power on, or
adb reboot bootloader
?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
In my case the barcode shows up whenever I reach fastboot, whether via booting with [vol up + power] and then selecting fastboot, or via adb reboot bootloader. I've tried several barcode recognition apps and 2 out of 3 confirm it's my IMEI.
Nycticorax said:
In my case the barcode shows up whenever I reach fastboot, whether via booting with [vol up + power] and then selecting fastboot, or via adb reboot bootloader. I've tried several barcode recognition apps and 2 out of 3 confirm it's my IMEI.
Click to expand...
Click to collapse
Did you try
Code:
fastboot flashing unlock_critical
according to this thread... it is for e6 plus. May be it works with e6 play.
https://old.reddit.com/r/androidroot/comments/f6c5k5/unlock_bootloader_moto_e6_plus/fupyalw/
No,
Code:
fastboot flashing unlock critical
does not work. And no, we shouldn't assume that a method meant for the e6 plus works for the e6 play.
Phone in red state not able to change settings
I have struggled with the same problems as above. I am not able to get into the developer mode as I only have access to the recovery screen. Anybody who knows how to do that from the recovery screen - perhaps using terminal?
I have been able to enter into the phone by adb sideload filename.zip and the phone acknowledged connection, but the upload failed, probably due to I am not able to unlock the phone from the red state/Android Recovery. It is running bali-reteu/bali9/POAS29.550-81-1/
glensbo said:
I have struggled with the same problems as above. I am not able to get into the developer mode as I only have access to the recovery screen. Anybody who knows how to do that from the recovery screen - perhaps using terminal?
I have been able to enter into the phone by adb sideload filename.zip and the phone acknowledged connection, but the upload failed, probably due to I am not able to unlock the phone from the red state/Android Recovery. It is running bali-reteu/bali9/POAS29.550-81-1/
Click to expand...
Click to collapse
It is not clear to me what you did exactly. The step where we -- the others participants to this post and I -- are stuck is [2] here below:
boot to fastboot by running `adb reboot bootloader` from a command line on a connected and turned on device
get the OEM unlock code by doing `fastboot oem get_unlock_data` from a connected device under the fastboot interface
exchange the unlock code on the motorola support site and input that code to confirm bootloader unlock
glensbo said:
I have struggled with the same problems as above. I am not able to get into the developer mode as I only have access to the recovery screen. Anybody who knows how to do that from the recovery screen - perhaps using terminal?
I have been able to enter into the phone by adb sideload filename.zip and the phone acknowledged connection, but the upload failed, probably due to I am not able to unlock the phone from the red state/Android Recovery. It is running bali-reteu/bali9/POAS29.550-81-1/
Click to expand...
Click to collapse
Got a little further as the code:
#fastboot flash unlock_critical Filename.zip#
the phone replied - Transferring and Transmission OK .... time etc
But I got an error sadly to say:
Failed (remote: not allowed in locked state) so I'm back to basics as I cannot open the state from the recovery mode (as of yet)
glensbo said:
Got a little further as the code:
#fastboot flash unlock_critical Filename.zip#
the phone replied - Transferring and Transmission OK .... time etc
But I got an error sadly to say:
Failed (remote: not allowed in locked state) so I'm back to basics as I cannot open the state from the recovery mode (as of yet)
Click to expand...
Click to collapse
Okay, I would like to be positive and call that a progress but the whole point of steps (2-3) is to have it unlocked so that you can proceed to root to flashing it the way you're trying to.
So I am pretty pessimistic on that one. To me it looks like a case of a cheap phone a company has no real urge to make easy to unlock.
Nycticorax said:
It is not clear to me what you did exactly. The step where we -- the others participants to this post and I -- are stuck is [2] here below:
boot to fastboot by running `adb reboot bootloader` from a command line on a connected and turned on device
get the OEM unlock code by doing `fastboot oem get_unlock_data` from a connected device under the fastboot interface
exchange the unlock code on the motorola support site and input that code to confirm bootloader unlock
Click to expand...
Click to collapse
Sorry got carried away finding a group dealing with the same problem as I have. And not skimming but reading the text I can confirm that I am stuck at the same place. Sorry for the interruption. I will revert if/when I have something new.
glensbo said:
Sorry got carried away finding a group dealing with the same problem as I have. And not skimming but reading the text I can confirm that I am stuck at the same place. Sorry for the interruption. I will revert if/when I have something new.
Click to expand...
Click to collapse
It's okay. I hope one of us can find something useful. Let Root, the God of Hacks, send His best love waves to you guys
wow No Help
Biniesuschristos said:
wow No Help
Click to expand...
Click to collapse
Just curious do you know what software Channel your phone is on?
The software Channel might be listed in
Settings/ about phone.
Or try
Code:
fastboot getvar all
While in fastboot mode
ro.carrier = Software Channel
Sent from my ocean using XDA Labs
You didn't ask me but perhaps it might help you help us:
Code:
reteu
for me.
I'm don't actually know anything regarding rooting mobile devices but i'm going to post some of my experience thinking it might help someone who actually knows what to do.
I've been having the same issue while trying to unlock the bootloader.
As it seems all of the fastboot commands are working fine except the OEM ones which is strange considering that i'm sure i toggled the OEM Unlock on the dev. options, just like some members commented already.
Regarding the barcode it shows as soon as i connect the device via USB in Fastboot mode, and it shows up when i use "adb reboot bootloader" too, but it wasn't showing before i updated the USB Drives so i could find the device via "fasboot devices" (the phone wasn't showing before i did it).
pontiacus said:
I'm don't actually know anything regarding rooting mobile devices but i'm going to post some of my experience thinking it might help someone who actually knows what to do.
I've been having the same issue while trying to unlock the bootloader.
As it seems all of the fastboot commands are working fine except the OEM ones which is strange considering that i'm sure i toggled the OEM Unlock on the dev. options, just like some members commented already.
Regarding the barcode it shows as soon as i connect the device via USB in Fastboot mode, and it shows up when i use "adb reboot bootloader" too, but it wasn't showing before i updated the USB Drives so i could find the device via "fasboot devices" (the phone wasn't showing before i did it).
Click to expand...
Click to collapse
Windows 10?
Sent from my ocean using XDA Labs
@sd_shadow: Do you think it looks like a bootloader you could unlock?