Related
Just as the title states...
I have completed the process on the HTCDev site many many times. The process itself works fantastic. Each step responds exactly how they state it should. I submit the token code and get a Bin file. Using fastboot to flash the Bin file results in the phone prompting me to unlock the bootloader. I select yes using the volume up and then hit power. The phone powers off and reboots restoring everything to factory. So it would seem that everything works correctly. I get no error messages during the process. I get nothing but the results that I should be expecting...EXCEPT...
The bootloader remains locked.
I'm beyond frustrated at this point. I've followed every single set of instructions just thinking maybe there's a step missing in one of them. Yet they all perform the same. End result...Bootloader still locked. No idea what is going on. Called HTC Tech Support and they weren't any help at all. Basically they said to leave a comment on the HTCDev site.
Any ideas???
Have you tried flashing anything even though it still says locked? It is a longshot, but there is a chance it is unlocked but just still says locked.
rultin said:
Just as the title states...
I have completed the process on the HTCDev site many many times. The process itself works fantastic. Each step responds exactly how they state it should. I submit the token code and get a Bin file. Using fastboot to flash the Bin file results in the phone prompting me to unlock the bootloader. I select yes using the volume up and then hit power. The phone powers off and reboots restoring everything to factory. So it would seem that everything works correctly. I get no error messages during the process. I get nothing but the results that I should be expecting...EXCEPT...
The bootloader remains locked.
I'm beyond frustrated at this point. I've followed every single set of instructions just thinking maybe there's a step missing in one of them. Yet they all perform the same. End result...Bootloader still locked. No idea what is going on. Called HTC Tech Support and they weren't any help at all. Basically they said to leave a comment on the HTCDev site.
Any ideas???
Click to expand...
Click to collapse
Since it's getting wiped anyway, exchange the phone for a new one.
MrSmith317 said:
Since it's getting wiped anyway, exchange the phone for a new one.
Click to expand...
Click to collapse
I second that, I had a problem Unlocking my Rezound, I called HTC they said they dont replace phones and to call VZW. I called VZW told them that HTC told me to call for a replacement, they gave me a hard time. I told them as a developer, not being able to unlock my phone is a detrimental to my livelyhood. They sent me a refurb (standard) and I had no problems unlocking it. I posted my saga over in general you can see it here http://forum.xda-developers.com/showthread.php?t=1416472
I was just given a tf201 in excellent condition, running stock Jelly Bean 4.1.1.
I have it rooted; but, also want to unlock the bootloader, so I can put a better ROM on it.
Every video or forum thread I have found says to use the Asus UnLock Device App v6.
A few threads say that it now only supports ICS; and, that may be the root of my problem:
Despite following every recommended step for installation and unlock, the Unlock Device App will not recognize my Google Password (a requirement). I do not use 2-step authentication, I went into Google Settings, and changed "Allow less secure apps" to 'ON'. I even changed my password, deleted/recreated my account in the tablet. Despite all of this, the Unlock Device App will not accept my Google Password...and, won't unlock the Transformer Prime.
Does anyone know of an alternative method to unlock the tablet; or, or a 'fix' for my Google Password issue?
Thanks, in advance!
PJ Arts
Madmanmoose said:
I was just given a tf201 in excellent condition, running stock Jelly Bean 4.1.1.
I have it rooted; but, also want to unlock the bootloader, so I can put a better ROM on it.
Every video or forum thread I have found says to use the Asus UnLock Device App v6.
A few threads say that it now only supports ICS; and, that may be the root of my problem:
Despite following every recommended step for installation and unlock, the Unlock Device App will not recognize my Google Password (a requirement). I do not use 2-step authentication, I went into Google Settings, and changed "Allow less secure apps" to 'ON'. I even changed my password, deleted/recreated my account in the tablet. Despite all of this, the Unlock Device App will not accept my Google Password...and, won't unlock the Transformer Prime.
Does anyone know of an alternative method to unlock the tablet; or, or a 'fix' for my Google Password issue?
Thanks, in advance!
PJ Arts
Click to expand...
Click to collapse
EDIT: Everything I've read says the unlock tool is the only option. The serial number on the device apparently gets checked against a database in the Asus China servers, which unlocks encryption so the bootloader can be unlocked.
I had a similar experience when I unlocked my Prime last weekend. I can't remember exactly what I did to get it to work, but it finally did work for me after I tried different things. The device is on firmware 4.1.1 JB/ 10.4.2.18.... so it definitely does work on JellyBean.
I didn't have 2 step verification activated either, but if I recall I had the issue where Google was not allowing less secure apps. Since you allowed that.... I'm not sure why it's not completing the process for you. I think I had received some sort of notification on the Tablet after typing in my Google password... and I had to confirm the notification to allow the app to have full account access.... but I honestly can't remember. I do remember looking through all the troubleshooting tips here: ( https://support.google.com/accounts/answer/6010255?hl=en ) and here ( https://support.google.com/accounts/answer/6009563 ).
I also remember using ES File explorer to see if there were any leftover files from the unlocking attempt, and I remember seeing a text file named "Unlock" or something like that, which I believe the app had created. (I've got to head out the door to get to work in a moment, so don't have time to look for it again right now)... but see if you can find that file and delete it... then try wiping data and cache in the Manage App settings, reboot the phone, and try to run it again.
The process was a pain in the butt for me too, but it finally worked, so hopefully you can get it to work for you too.
Thanks! Was given a really simple solution at another forum: Factory Reset/DO NOT register any Google account/use the UnLock Device App v6.
Worked like a charm.
Madmanmoose said:
Thanks! Was given a really simple solution at another forum: Factory Reset/DO NOT register any Google account/use the UnLock Device App v6.
Worked like a charm.
Click to expand...
Click to collapse
Cool man. Good tip for everyone. I'm sure that will help a lot of people. Happy flashing!!
Madmanmoose said:
Thanks! Was given a really simple solution at another forum: Factory Reset/DO NOT register any Google account/use the UnLock Device App v6.
Worked like a charm.
Click to expand...
Click to collapse
You seriously rock for this one. They oughta include this info in the KatKiss ROM update doc for the TF201. Thanks! -- Chuck
Options for not Unlocked device
Hi,
I tried multiple times to unlock the bootloader in the last 2 years (unsuccessfully), then few days ago I contacted Asus and they replied to me that "The unlock tool has been discontinued since 2014", so no way to unlock.
What are my options now? No way to install new roms, but there is any known method for at least rooting the device (with the latest firmware)?
Thing is, that I really liked the transfomer (especially the keyboard) but it's always been too slow to browse the internet, and actually there is no replacement I can buy (asus make some similar products but are all windows based and most of them have a quite cheap look).
Thanks a lot for the help!
BitJockey82 said:
What are my options now? No way to install new roms, but there is any known method for at least rooting the device (with the latest firmware)?
Click to expand...
Click to collapse
I rooted with motochopper, so now I have root access. I installed and used fstrim, seems like there was a small performance improvement. Not sure if I have anything else I can do to speed it up with root but no custom rom.
Hi i used the unlock tool last night, and it was a pain, as it wouldn't accept my google password! I found a solution on here, after reading what seemed like have the board posts for the TF201. So basically what I did was -
1. Go to the tablet settings, and set a pin code as the unlock method.
2. In Google, set the less secure apps permission.
3. Load the unlock app again, and accept the warnings.
4. When it asks for verification, use the unlock code option.
5. Wait for it to do its thing, and Tablet will reboot.
6. Once finished, restart the Tablet, in top left hand corner during boot it will say this device is unlocked.
Hopefully this will help.
Regards Bill
Thanks Bill,
I tried again today, following your steps, but this didn't worked. My problem is that the unlocker just fails, it never prompted me for the google account password. It saves a file with the unlock date.
I think I need to try again with the factory reset (that I tried in the past actually, and didn't worked).
BitJockey82 said:
Thanks Bill,
I tried again today, following your steps, but this didn't worked. My problem is that the unlocker just fails, it never prompted me for the google account password. It saves a file with the unlock date.
I think I need to try again with the factory reset (that I tried in the past actually, and didn't worked).
Click to expand...
Click to collapse
Does anyone have a working download link for the unlock tool? It seems to no longer be available on ASUS's website.
---------- Post added at 04:04 AM ---------- Previous post was at 03:58 AM ----------
Desverger said:
Does anyone have a working download link for the unlock tool? It seems to no longer be available on ASUS's website.
Click to expand...
Click to collapse
Never mind, I found this thread: https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237
Which points to this archive full of useful stuff, including the unlock too: https://drive.google.com/file/d/0B0wnQregW3ZgZ0o5X3Vidnp3MFU
Sorry for the spam. :silly:
winnerz said:
Hi i used the unlock tool last night, and it was a pain, as it wouldn't accept my google password! I found a solution on here, after reading what seemed like have the board posts for the TF201. So basically what I did was -
1. Go to the tablet settings, and set a pin code as the unlock method.
2. In Google, set the less secure apps permission.
3. Load the unlock app again, and accept the warnings.
4. When it asks for verification, use the unlock code option.
5. Wait for it to do its thing, and Tablet will reboot.
6. Once finished, restart the Tablet, in top left hand corner during boot it will say this device is unlocked.
Hopefully this will help.
Regards Bill
Click to expand...
Click to collapse
Just tried this tonight and it worked. No Google account activation but I did set a screen lock. I setup the wifi in the beginning setup screens. and Used the Unlocker from the Asus Tf201 Download
Installed unlocker and opened the program and asked for asus tf201 pin code. System accepted settings and rebooted.
As in the title, I have an, Alcatel Tcl Lx A502dl, Android phone, originally purchased from Walmart with a Trackfone Sim card (Now there is no sim card insterted).
I have spent all day, up until now, figuring out how to link abd and fastboot to the phone using USB debugging, and I have been successful this far. I had downloaded latest "platform-tools_r29.0.1-windows" from here on XDA, and I downloaded latest "fatsboot" from "HighonAndroid.com", for a quicker experience, without wasting time and effort on Java downloads. In addition to all this, I let the computer search the network for updating driver software, for my Alcatel phone. I also downloaded "UniversalAdbDriverSetup", from the former link, @highonandroid.com.
I linked both file pathways for corresponding "Fastboot", and "platform-tools", into the environment variables, under the term: "Path", yes, using a ";" with no spaces to add the new pathways.
I had success linking my phone onto the "abd" program, the phone is listed under "abd devices" command. I could not seem to get a listing of my phone serial number, under the "fastboot devices" command?
I have tried to get "platform-tools" to put the phone into "fastboot/bootloader" mode, but the phone simply reboots, back to the lockscreen. I have also tried on "Fastboot", to "fastboot reboot bootloader", and my Alcatel again reboots to the lockscreen. All the while, I activated the OEM unlocking switch/setting in the "developer options" of my phone, from the beginning, before I ever gave any commands?
Why won't my Alcatel phone reboot into the "fastboot/bootloader" screen, where I could command "fastboot oem unlock"? Why does my phone respond to both programs, yet still she loads the lockscreen?
I am new to all this, not really a tech savvy individual, just wanted a liberated operating system for my line of work...
I need bootloader unlocked in order to root my device via computer, correct?
I can not check to see if my bootloader is unlocked, not by abd tools, or by numerical code in my "dialer app". The app crashes, and any time I attempt the "fastboot oem device-info" command, no device is listed, only a <looking for a device> prompt of sorts appears. I have been told this may be because, the drivers were not installed properly, or the device was not properly connected under some other issue, and I can try to fix this error by reinstalling drivers... what would the issue be?
I need help, and I would appreciate some guidance on rooting my Android, as there are not any threads in the forum, on this model of Alcatel, that I am aware of?
I am doing all of this on a Windows 7 computer, in a Library, just so you all know. I ask for administrative approval for most things.
Thank you.
tcl trackfone
Hello i was wondering if you ever got your phone rooted?
me to i have that problem on my tcl lx
to
Temporary mtk- root. Use init.d for always root
Sonjouten said:
Temporary mtk- root. Use init.d for always root
Click to expand...
Click to collapse
I can't possibly express how much I would love for you to elaborate on the 'use init.d for always root' part. Anyone else who knows, please jump in. Start by pretending I am an idiot. Then stop pretending and explain it to me as if I were an adult who needs a full-time minder. First one to help me achieve "always root" on this terrible, wretched, little excuse for an electronic device gets my undying gratitude and um, maybe some Google Play money? I am open to ideas here on that score. To reiterate, need help rooting my Tracfone TCL LX A502DL that has a castrated recovery (seriously, you can't flash anything from adb, the option is flat-out missing) and apparently no fastboot access AT ALL. I could do another seriously in parentheses, but you need to take my word for it w/o a bunch of examples. The bright spot is the vulnerability the device has to the mtk-su exploit. Get a # in like no time at all. Time elapsed from executing the file to getting the prompt is too short for my flesh computer to register (unless you -v, then about 1.5 seconds.) So how do I turn a root prompt into full root?
I can't possibly express how much I would love for you to elaborate....
Click to expand...
Click to collapse
WHAT HE SAID
+1
X2
etc
Thank you, H
Did he get that?
So did he earn that Google Play Store money or was he just full of it?
Just bumping this thread in case anyone has ideas for me. Seems like Alcatel has bootloader mode hidden on some phones. Here's my story: https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
BTW - I am using mtk-su and have root and Magisk via init.d scripts, but still can't touch /system or flash recovery because of
Code:
/dev/block/dm-0' is read-only
which won't change unti bl unlocked...
I never did get her to root. Alas she is a broken phone now RIP. Sorry for the disappointments. But I move on more hopeful. ?
As posted by Viva La Android in another thread about the tcl a501dl:
The TCL A1 (A501DL) cannot be bootloader unlocked. Although the OEM Unlocking option can be enabled in the Developer Options menu, fastboot mode has been made inaccessible by TCL. Because the bootloader cannot be unlocked, it simply is not possible to flash a custom recovery or a patched boot image for systemless root support. System-wide root is not possible due to TCL's secure boot chain configuration and dm-verity. Until an exploit is found to bootloader unlock this device, rooting is not possible.
Click to expand...
Click to collapse
levone1 said:
Just bumping this thread in case anyone has ideas for me. Seems like Alcatel has bootloader mode hidden on some phones. Here's my story: https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
BTW - I am using mtk-su and have root and Magisk via init.d scripts, but still can't touch /system or flash recovery because of
Code:
/dev/block/dm-0' is read-only
which won't change unti bl unlocked...
Click to expand...
Click to collapse
I have tried everything, and can't even get temporary root on my A502DL. How did you do this, if you don't mind? Thanks!
fliproc said:
I have tried everything, and can't even get temporary root on my A502DL. How did you do this, if you don't mind? Thanks!
Click to expand...
Click to collapse
Sorry, I honestly don't remember now - I just happened to have tje phone for a short time at that moment, so I was messing around with it... I remember there was nothimg special about it. I jist followed the instructions from the mtk-root thread and it worked.
Amazing Temp Root for MediaTek ARMv8 [2020-08-24] | XDA ...
Braadleyah said:
As in the title, I have an, Alcatel Tcl Lx A502dl, Android phone, originally purchased from Walmart with a Trackfone Sim card (Now there is no sim card insterted).
I have spent all day, up until now, figuring out how to link abd and fastboot to the phone using USB debugging, and I have been successful this far. I had downloaded latest "platform-tools_r29.0.1-windows" from here on XDA, and I downloaded latest "fatsboot" from "HighonAndroid.com", for a quicker experience, without wasting time and effort on Java downloads. In addition to all this, I let the computer search the network for updating driver software, for my Alcatel phone. I also downloaded "UniversalAdbDriverSetup", from the former link, @highonandroid.com.
I linked both file pathways for corresponding "Fastboot", and "platform-tools", into the environment variables, under the term: "Path", yes, using a ";" with no spaces to add the new pathways.
I had success linking my phone onto the "abd" program, the phone is listed under "abd devices" command. I could not seem to get a listing of my phone serial number, under the "fastboot devices" command?
I have tried to get "platform-tools" to put the phone into "fastboot/bootloader" mode, but the phone simply reboots, back to the lockscreen. I have also tried on "Fastboot", to "fastboot reboot bootloader", and my Alcatel again reboots to the lockscreen. All the while, I activated the OEM unlocking switch/setting in the "developer options" of my phone, from the beginning, before I ever gave any commands?
Why won't my Alcatel phone reboot into the "fastboot/bootloader" screen, where I could command "fastboot oem unlock"? Why does my phone respond to both programs, yet still she loads the lockscreen?
I am new to all this, not really a tech savvy individual, just wanted a liberated operating system for my line of work...
I need bootloader unlocked in order to root my device via computer, correct?
I can not check to see if my bootloader is unlocked, not by abd tools, or by numerical code in my "dialer app". The app crashes, and any time I attempt the "fastboot oem device-info" command, no device is listed, only a <looking for a device> prompt of sorts appears. I have been told this may be because, the drivers were not installed properly, or the device was not properly connected under some other issue, and I can try to fix this error by reinstalling drivers... what would the issue be?
I need help, and I would appreciate some guidance on rooting my Android, as there are not any threads in the forum, on this model of Alcatel, that I am aware of?
I am doing all of this on a Windows 7 computer, in a Library, just so you all know. I ask for administrative approval for most things.
Thank you.
Click to expand...
Click to collapse
I have heard elsewhere that it's not possible to unlock the bootloader of a Tracfone. Sorry. But at least we know why Tracfones are sold for so cheap lol
$cronos_ said:
I have heard elsewhere that it's not possible to unlock the bootloader of a Tracfone. Sorry. But at least we know why Tracfones are sold for so cheap lol
Click to expand...
Click to collapse
unlock bootloader and root with https://github.com/bkerler/mtkclient
This device cannot be rooted. To date, there has not been a single validated claim of a rooted TCL A509DL. The bootloader cannot be unlocked, preventing root, custom ROM installs,etc.
UPDATE: After hearing from some members regarding the Hydra Tool, and doing a little bit of research on the method, it appears that I was completely wrong on my.statement. Members here on XDA as well as Hovatek have confirmed that the A509DL bootloader can indeed be exploited with the Hydra Tool method, opening the door to systemless root with Magisk. Thanks guys for the info and guidance. I have one of these devices and look forward to unlocking & rooting soon. Thanks @PrivyetCyka for the info.
Yes it can .. it was extremely easy to do so also..i have a rooted one in my hand as we speak the only issue is I was stupid and tried to flash the magisk zip in twrp and it set off secureboot so in working on fixing that .. but .. if you just use MTKClient you can pull the entire firmware , magisk patch then reflash the boot.img using the same tool and you can even install twrp I have the entire firmware , twrp, and magisk patched boot imgs for the device saved ,. If someone knows how to disable secureboot I would really appreciate it
Viva La Android said:
This device cannot be rooted. To date, there has not been a single validated claim of a rooted TCL A509DL. The bootloader cannot be unlocked, preventing root, custom ROM installs,etc.
Click to expand...
Click to collapse
I sure would like to give it a whirl, but I haven't had that phone in over a year
Anyway, I decided to stop buying devices made deliberately less functional by their manufacturers.
PrivyetCyka said:
Yes it can .. it was extremely easy to do so also..i have a rooted one in my hand as we speak the only issue is I was stupid and tried to flash the magisk zip in twrp and it set off secureboot so in working on fixing that .. but .. if you just use MTKClient you can pull the entire firmware , magisk patch then reflash the boot.img using the same tool and you can even install twrp I have the entire firmware , twrp, and magisk patched boot imgs for the device saved ,. If someone knows how to disable secureboot I would really appreciate it
Click to expand...
Click to collapse
I stand corrected on my statement. I was incorrect. Out of curiosity, does the Hydra tool require the dongle in order to unlock the bootloader?
@PrivyetCyka send me the Magisk packed boot image and I will unpack it and disable secure boot. I can then pack it back up and link it to you. Are you referring to only secure boot or also AVB 2.0/dm-verity?
I didn't use hydra tool I used MTKClient from GitHub and did an entire system read back to have a backup then just renamed boot.bin to boot.img used magisk to patch it and then used the same MTKClient tool to reflash it... I have a twrp I made for it also but I don't know how functional it is as far as flashing things and backups , the only thing I tried to flash was the magisk zip just to see what would happen and that tripped the secureboot , I used the mediatek secureboot tool and it says it's disabled but it's still not booting past the secureboot fail screen.. when I get home I'll get the files and upload them tonight
Hello All,
Hope you and yours are doing fine in these worldwide complicated days.
Regarding the subject, I have a Xiaomi Mi Play mobile that was working fine, with official MIUI, never rooted, never done something else than usual "office" daily usage.
One day, came the famous Security Update notification and as usual, I've confirmed.
Since then big headaches...
Next morning I found the phone in the loop reboot, Fastboot being the only available feature, no more recovery, no more OS, no more personal stuff... Everything has been deleted by the update.
When trying to go to recovery only the magnificent message with the red triangle, saying "The system has been destroyed. Press the power button to shutdown" stays for 10-15 secs and then the whole crap reboots again and again.
No, Developer Settings haven't been enabled, OEM Unlock has not been enabled, USB Debugger neither, bootloader has not been unlocked, MIUI account has not been added in Developer Settings or elsewhere... and no I haven't wrote to Xiaomi support yet.
I've tried around 60-80 different methods to unlock whatever could be unlocked on Xiaomi phone, EDL, bootloader, with dozens and dozens of methods proposed, so far nothing worked. Impossible to install anything, impossible to unlock anything, impossible to do anything.
I've applied for the phone unlock, but since 2 months, impossible to finish the process, it says "Couldn't Unlock - Please add your account in MIUI's Settings > Developer options > Mi Unlock Status"
But I CANNOT access the system anymore at all....
This is it...
Thank you for reading and if you have any other ideas out of everything I've tried, feel free to let me know about.
Take care of you and yours
Kind Regards,
SK
ooophhh no. did you ever get a solution? i had my mi play brick just oputta the blue.. its on communist lockdown fighting the war on capitalism ..... well the hardware wasnt bad for the price and it ran well.,but im not buying a phone from them ever again.
It's very sad. Did you get any update?
Hello All,
No update since March, still looking and trying to unbrick the device....
I'll keep you posted if I find anything that could be called a solution.
Thanks for your support.
Be safe all, you and yours.
Kind Regards,
SK
Same here, bricked device since March by the same update, "The System has been destroyed", fastboot doesn't load.
I guess i've lost 150$.
Produkt87 said:
Same here, bricked device since March by the same update, "The System has been destroyed", fastboot doesn't load.
I guess i've lost 150$.
Click to expand...
Click to collapse
There are many thread for issues like this, for example:
https://forum.xda-developers.com/mi-9-se/help/lock-bootloader-destroyed-help-t3965825
It seems that in some way, same issue was fixed on a different model, but most likely it will work also with Mi Play.
Af far as I have understood, basically the solution is to download the official firmware and flash it back. The main issue is that by default the bootloader is locked so nothing can be written. The point here is how to unlock the phone, and there is an official procedure from Xiaomi:
https://forum.xda-developers.com/mi-9t/how-to/guide-unlock-bootloader-flash-xiaomi-eu-t3952443
I have the same issue for a couple of hours and I am struggling now, so as first step I am trying to unlock the bootloader, but the problem is that per Xiaomi instructions it may take up to 7 days.
So, I will apply for that, while in the meantime I will look for any alternative solutions (if any).
Regards,
Thanks a lot!
But, the're now way to get my phone into fastboot mode.
I've tried all button combinations and there's no response, just the same loop "your system has been destroyed"
Produkt87 said:
Thanks a lot!
But, the're now way to get my phone into fastboot mode.
I've tried all button combinations and there's no response, just the same loop "your system has been destroyed"
Click to expand...
Click to collapse
After some tests on my device, I have found out that it's not easy as I have believed, but if you don't get even in Fastboot mode it's more complicated.
However, can you please clarify what's your cellphone model?
Regards,
I have exactly the same problem since early May, if I just unlock the boot loader before they fall down :c
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.