OK, So I purchased this LG Treasure about a month ago and of course. I'd like to root it, Problem is Tracfone has this thing locked down tight. the bootloader/Recovery is not accessable. If you do the volume down/power button combo, it only brings you to a Factory date rest option. . I went to LG support and had a chat with them. I was informed by the tech that the bootloader access has been disabled. I asked if there was a way to enable access and he said that there is a way but he is not allowed to tell me and suggested that i come here to inquire. So i am hoping some here might be able to help, I don't even care if brick this device , it's worthless as is. Adb will see the device but fastboot will not leading me to think it's disabled by the carrier as the tech suggested. So any help would be greatly appreciated. Some one please point me in the right direction with anything i can try . Thanks All.
thank you..
ramious2012 said:
OK, So I purchased this LG Treasure about a month ago and of course. I'd like to root it, Problem is Tracfone has this thing locked down tight. the bootloader/Recovery is not accessable. If you do the volume down/power button combo, it only brings you to a Factory date rest option. .
Click to expand...
Click to collapse
Thank you so much for posting this question as I have that same issue. Your question was well put. Yet no one has responded. I hope there is a solution to this issue. :good:
these questions regarding the rooting of the lg treasure, which is my phone ironically, brings us to 1 definate answer, and that is that tf already knows how to unlock the bootloader, and thus, root the phone. it seems logical if any other tf/st phone has a similar os/locked bootloader that has been rooted, we might try those, or find someone recently seperated from the employment of tf who may spill the beans perse. just my input.
pouchpopper said:
these questions regarding the rooting of the lg treasure, which is my phone ironically, brings us to 1 definate answer, and that is that tf already knows how to unlock the bootloader, and thus, root the phone. it seems logical if any other tf/st phone has a similar os/locked bootloader that has been rooted, we might try those, or find someone recently seperated from the employment of tf who may spill the beans perse. just my input.
Click to expand...
Click to collapse
Thank you for giving me some hope lol. But still I have had no luck rooting this phone. Pretty aggravating. It's a decent phone and all. Sad they ruin it by locking it.
oem unlock
Did you first go and turn on oem unlock in the developers section of the phone? It is required by many phones under loli to unlock the bootloader. Might need to turn on usb debugging too in order for fastboot to be able to access the bootloader to get root on the phone.
My OEM unlock option has been enabled. However I have had no luck at all rooting this phone. It's unfortunate. Again I'm asking any developers available to please work on this project. The LG treasure is a very popular phone. Not only because of the price, But the features the phone has. Please I have done my best getting this phone to root.. But I'm out of ideas.
I have the lg rebel 2 lte and same problem. There is of course a way, their official unlocking policy is they'll grant us the unlock after a year of service paid. So they charge you for the device then charge you for a whole year for full access to said device. $$$
But lg has an official developer thing now where they'll email you the unlock.bin file to unlock it.
However the only; and I can't stress this enough, the ONLY problem is they've coded the bootloader to skip fastboot entirely. Somewhere between the first and second splash screen the bootloader and fastboot are working, soon as it shows the tracfone logo that's when you know its booting android. I have yet to figure out how to read the logs of the boot process to see how.
Yes, enable oem unlock and usb debugging.
However everyone with a new lg phone under any of the tracfone subsidiaries will find that those options don't matter. There must be a dialer code for the bootloader deal.
A friend of mine got this phone recently, it's the "Special Edition" H840, but it's European.
I was checking the Developer Options and noticed that i was able to enable OEM Unlock.
My questions are:
Should I try to unlock the bootloader via fastboot?
Should I try another fastboot command first (or after) to see if they've been blocked like on the H830?
Would me confirming any of this help you guys out in any way?
Thanks in advance, I'd love to see development get started on the H840 if it's possible to unlock its bootloader.
Knochenfabrikant said:
A friend of mine got this phone recently, it's the "Special Edition" H840, but it's European.
I was checking the Developer Options and noticed that i was able to enable OEM Unlock.
My questions are:
Should I try to unlock the bootloader via fastboot?
Should I try another fastboot command first (or after) to see if they've been blocked like on the H830?
Would me confirming any of this help you guys out in any way?
Thanks in advance, I'd love to see development get started on the H840 if it's possible to unlock its bootloader.
Click to expand...
Click to collapse
The OEM unlock option is there on all G5's, it was even there on my ATT V10 that has yet to be unlocked. I suppose you could try to run the fastboot commands, but I doubt you'll actually get anywhere with it.
As Eric said, they're present in every G5 version. Don't waste your time, you can't unlock it without the IMEI associated .bin file.
I bought ANE-LX1 (P20 Lite) on June 2018 and immediately unlocked the OEM from the developer options (automatic factory reset was done then), but i never rooted or installed custom rom, recovery...etc.
All updates was normally arriving and i was updating my phone regularly (current build is: ANE-LX1 8.0.0.170(C185)).
I decided to root my device using fastboot, but when the device is in recovery mode i can see:
Code:
Phone Locked -- (in green font color)
FRP Unlock -- (in red font color)
When i try to flash using fastboot i got:
Code:
FAILED (remote: Command not allowed)
While searching online i found that Huawei decided to lock bootloader for all users (so we buy their hardware which contains an opensource software and then they lock it... PERFECT!), and it seems that the only way now is to get the unlock code by contacting third-party codes providers, pay money and they guarantee to provide the correct unlock code (pay and pray) + I will have to expose my device information.
My questions are:
-How can i see in the developer options that my OEM is already unlocked, while the recovery is not convinced?
-Do i really have to unlock it again with the code "after purchasing it ofcourse -- which i will never do" (e.g. using fastboot)?
-Is there any solution from xda experts for my case rather than buying codes and exposing my device information or stay with a Locked bootloader?
(attached evidence images for a clearer view)
drive.google.com/open?id=1e9CepsHp2O541ZKGS0E6uqS2hBwp8ry1
drive.google.com/open?id=119eCoO4Z0TvydupLIsEv-r5lsGHOD4o0
drive.google.com/open?id=1IBA1nYnw_PU25VLPTzqSLswTpGMQxuXP
Thanks in advance for your kind support.
and Thanks Huawei for putting us as a development community in this situation, where we have to pay for the black markets to unlock our own phones in an unofficial way.
Yes please, shoot some answers!
alimerdan said:
I will have to expose my device information.
Click to expand...
Click to collapse
What do you expose?
bouncingsoul said:
Yes please, shoot some answers!
What do you expose?
Click to expand...
Click to collapse
IMEI, product S/N (if i correctly understood the process, i have to provide my device info so they can extract the bootloader unlock key)
According to the information that's available, the code used to unlock the bootloader is unlocked in a very complicated way and it's basically unique for everyone. Now, I don't know how much this is true and how and why these people got their hands on the "method" of creating the code, but no one has been able to find a way that's guaranteed to work or even work at all, except for, of course, these sites that make you pay for it. I hope I'm not mistaken and forgive me if I am, but I don't think there is any way to obtain the bootloader code manually or without exposing your information to random strangers on the internet.
Need to unlock bootloader with dc unlocker to get unique unlock code. Look guide bootloader unlocking
I'm using samsung A10,i try to root my phone but not sure the step are correct or not. But now my bootloader is unlocked and my data was erase, how to lock the bootloader and recover my data's back.Please help me
Even if you manage to re-lock the bootloader the data are unrecoverably wiped.
So I've been having this issue for a while now. I would like to unlock the bootloader on my Samsung and I'm struggling severely. I've done so much research and attempts and phone calls and in the end, my hands always turn up empty. Could someone please give me some advice or a guide to what I'm supposed to do because it seems like this specific phone under the Tracfone carrier is a ghost when it comes to this and rooting. Once I get a lead I'm suppose to enable oem unlock, well my phone doesn't have one. I've waited more than a week with developer options on and I've even tried adb and fastboot. Still nothing, I really need an expert's help but I can't seem to find anyone. Not even XDA is helpful with this phone. Yeah they have the A10 or A10s but not the A10e under the Tracfone carrier with the model number SM-S102DL. Help would be much appreciated. Thank you
visit here
My A10 phone still in unlock bootloader condition, can i still recover the lost files?
UPDATE: This phone is money down the drain unless I can unlock and root it. If you can help me do that successfully, I'll pay you $20. Just to end this frustration.
UPDATE: Cash offer rescinded. I fixed the problem by buying a different phone and giving up on this one.
Question: How do I fix the OEM Unlocking option not appearing on a Samsung A01 (SM-S111DL)?
Answer: By giving up on it and buying a different phone.
Maybe this is a better forum to post this. I have a Samsung A01, SM-S111DL. I want to root. I want Magisk on there.
I have been searching, and searching, and searching for any useful tutorials on how to root this specific device. In addition to searching, I have also been searching. And besides that, completely apart from that, I have been searching. So nobody better tell me I haven't tried figuring this one out for myself.
So far, I can't find anything that works. I just can't. Partly because tutorials keep telling me I need to turn on the OEM Unlocking option, and it ain't there. I know where it's supposed to be, between Bluetooth HCI and Running Services, and it's not there. And I tried the Date & Time trick, and it didn't help.
So, if I can't turn that option on, what can I do? I was thinking about trying Heimdall. It was unable to print the PIT, but I managed to download a PIT that supposedly corresponds exactly to my device. It's labeled A01Q_USA_TFN.pit. I also downloaded the full firmware with Frija, and extracted stuff. I took the boot.img from the downloaded firmware and patched it with Magisk. I was thinking of installing it, but then I said, no, I better wait until some experts weigh in on this. Best case, the flash would go just fine. But then there are two bad cases. One, Heimdall won't even be able to flash, and that will mean more anger and frustration. Two, it'll brick the device. And I'm not even sure which is worse anymore.
This point, I don't even know what the hell to do. Please, someone help.
Also, I'd like to have TWRP on this device. But I don't know whether there's a version out yet. Sure, there's one for some other model of A01, but would it work with mine? I just don't know, and I'm feeling too discouraged to try.
Please, someone help.
Did you search before posting? I see many, many threads regarding rooting the Galaxy A01, including one you posted 7 days ago on the same topic.
V0latyle said:
Did you search before posting? I see many, many threads regarding rooting the Galaxy A01.
Click to expand...
Click to collapse
Did you read before replying? I told you many, many times that I searched.
FailSafeNow said:
Did you read before replying? I told you many, many times that I searched.
Click to expand...
Click to collapse
My point is, creating a new post isn't always the best course of action when there's already discussions on the topic. Secondly, do not create multiple threads on the same topic.
If OEM Unlock is not available, you won't be able to unlock the bootloader, which will prevent you from flashing custom images (such as the patched boot image). You could try using Odin to flash an older firmware version and see if OEM Unlock becomes available.
Here's a couple things you can try. First, remove your SIM and turn off WiFi. Then, disable Automatic Date & Time, and set the time ahead by at least 1 week. If the OEM Unlock toggle does not appear, just wait a while.
Apparently, this has something to do with Knox.
If you want to check whether unlocking the bootloader will be possible at all, you can use ADB:
Code:
adb shell getprop ro.oem_unlock_supported
If this returns 0, unlocking the bootloader is not possible at all.
If this returns 1, then you just need to be able to access the OEM Unlock toggle, which will set get_unlock_ability to 1 and permit unlocking the bootloader, at which point you should be able to flash a patched boot image.
See this article for more information.
V0latyle said:
My point is, creating a new post isn't always the best course of action when there's already discussions on the topic. Secondly, do not create multiple threads on the same topic.
If OEM Unlock is not available, you won't be able to unlock the bootloader, which will prevent you from flashing custom images (such as the patched boot image). You could try using Odin to flash an older firmware version and see if OEM Unlock becomes available.
Here's a couple things you can try. First, remove your SIM and turn off WiFi. Then, disable Automatic Date & Time, and set the time ahead by at least 1 week. If the OEM Unlock toggle does not appear, just wait a while.
Apparently, this has something to do with Knox.
If you want to check whether unlocking the bootloader will be possible at all, you can use ADB:
Code:
adb shell getprop ro.oem_unlock_supported
If this returns 0, unlocking the bootloader is not possible at all.
If this returns 1, then you just need to be able to access the OEM Unlock toggle, which will set get_unlock_ability to 1 and permit unlocking the bootloader, at which point you should be able to flash a patched boot image.
See this article for more information.
Click to expand...
Click to collapse
Thank you. I've tried various tricks with the date, to no avail so far. But I will try the trick the way you said it, and try waiting. Incidentally, I have no sim. Just got this phone off eBay. Never planned on putting a sim in it. Just wanted it for usage as a wifi device.
So far, no OEM Unlocking option has appeared. But I'll wait on it, like you said. And yeah, I've read that these devices are made to have some kind of waiting period.
I also read that you had to be on Android 11 before you could get the unlocking option. So that's what I'm on. As for Odin, it gets stuck on the analyzing phase and never actually writes anything. Heimdall gives me an error of -12 when I try to use it. I've tried installing drivers on my computer with Zadig, but it hasn't changed anything so far. And it has a lot of options for drivers and stuff, so I don't know which are even the right ones. (I'm on Windows 10 Pro.)
I tried the ADB code about a week ago, having found that direction in one of the threads. And yes, it gave me a 1, so good news.
Is there no other way to set unlock ability to 1? I mean, if Samsung had this phone in its lab, would they be able to force it to do things, or would they have to manually remove the MMC and put it on a special reader?
Also, the reason I created my own thread was that I thought piggybacking on other people's threads was frowned upon.
Edit: I also checked the article. I've seen it before, because when I want something, I keep searching for it until I either find it or destroy my nervous system trying. I tried putting together the combination firmware. But two problems. First, it lies about which files I'm going to find when I extract the various archives. boot.img.lz4: fine. system.img.lz4: no such file exists. sboot.bin.lz4: no such file exists. I'm guessing they would want me to use aboot.img.lz4 instead of sboot.img.lz4, and super.img.lz4 instead of system.img.lz4, but since the guide was made for phones that call their images different things, I don't honestly know. Second problem: Odin can't flash crap. Neither can Heimdall. The experts say, "Use one of these patched versions of Odin." So I try. No dice. And I try Heimdall, but that's no good either. Like I said, Error -12. What do I do about this? "Install stuff with Zadig." So I try that. I install every damn thing that Zadig has an option to install. Nothing changes. Nothing gets better. The tutorials have failed me.
Next time I buy a phone, painless rooting and unlocking is going to be my first criterion.
The option to unlock still has not appeared. I need more help.
I'm just about ready to give up on this phone completely. Can nobody save this situation?
are there any variants to this device? how would you match firmwares? or substitute the firmware to be able to flash, so that other options such as oem unlock become available? have we checked if any of the android 10 firmwares for a01 sm-s111dl have the oem option available?
FailSafeNow said:
UPDATE: This phone is money down the drain unless I can unlock and root it. If you can help me do that successfully, I'll pay you $20. Just to end this frustration.
UPDATE: Cash offer rescinded. I fixed the problem by buying a different phone and giving up on this one.
Question: How do I fix the OEM Unlocking option not appearing on a Samsung A01 (SM-S111DL)?
Answer: By giving up on it and buying a different phone.
Maybe this is a better forum to post this. I have a Samsung A01, SM-S111DL. I want to root. I want Magisk on there.
I have been searching, and searching, and searching for any useful tutorials on how to root this specific device. In addition to searching, I have also been searching. And besides that, completely apart from that, I have been searching. So nobody better tell me I haven't tried figuring this one out for myself.
So far, I can't find anything that works. I just can't. Partly because tutorials keep telling me I need to turn on the OEM Unlocking option, and it ain't there. I know where it's supposed to be, between Bluetooth HCI and Running Services, and it's not there. And I tried the Date & Time trick, and it didn't help.
So, if I can't turn that option on, what can I do? I was thinking about trying Heimdall. It was unable to print the PIT, but I managed to download a PIT that supposedly corresponds exactly to my device. It's labeled A01Q_USA_TFN.pit. I also downloaded the full firmware with Frija, and extracted stuff. I took the boot.img from the downloaded firmware and patched it with Magisk. I was thinking of installing it, but then I said, no, I better wait until some experts weigh in on this. Best case, the flash would go just fine. But then there are two bad cases. One, Heimdall won't even be able to flash, and that will mean more anger and frustration. Two, it'll brick the device. And I'm not even sure which is worse anymore.
This point, I don't even know what the hell to do. Please, someone help.
Also, I'd like to have TWRP on this device. But I don't know whether there's a version out yet. Sure, there's one for some other model of A01, but would it work with mine? I just don't know, and I'm feeling too discouraged to try.
Please, someone help.
Click to expand...
Click to collapse
ADB Fastboot OEM unlock? https://www.getdroidtips.com/how-to...-on-Samsung-Galaxy-Phones-via-PC-ADB-Fastboot
so i found out how to do this if anyone still needs this information for this phone. You go to software status and click the kernel version several times to activate developer mode and once thats activated there will be a developer options under "about phone" on the main settings menu and instead of being between bt hci and services it was down at the bottom under the debugging sub menu. There is USB debugging and wireless debugging(over wifi) simply toggle usb debugging and/or wireless debugging and continue from there on youre pc of choice with process of choice! Hope this has helped anyone. I have the exact same phone as OP, same model number.