Related
i don't know what to do... i think i read every tutorial for unbrick my phone but nothing works...
my situation:
-i unlocked my fone by unnoficial method, instaled twrp and everything was ok.
i decided to instal sMIUI, but nowhere i read that is necesary to delete emmc file... so i bricked my phone.
bootloader got relocked, i can't turn on my phone, mi logo appears during 1 sec > screen off > again mi logo during 0.001s > screen off
when i plug in my phone into my pc, i have black screen and red led, but it's not adb mode.
i can't enter adb, my pc (windows 10 x64), i use command "adb devices" and list is empty
i can't edl
i can enter in fastboot mode.
i can't flash nothing, "failed: device is locked"
anyone can help me?
if i unlock officialy my bootloader, can i flash again stable rom or something? i just had my phone during 2 weeks.
can i do anything?
thanks.
one more thing: i had guaranty, so, if i unlock my bootloader officialy, i lose it?
i don't want to try testpoint method, because of guaranty.
Well, welcome to the party.
Irrespective of how much u search, cry for help or open millions of threads like this instead of doing a little search, there is no solution except test point method. Now don't ask how to do it. Search and read a little u will get the necessary info.
sanjib734 said:
Well, welcome to the party.
Irrespective of how much u search, cry for help or open millions of threads like this instead of doing a little search, there is no solution except test point method. Now don't ask how to do it. Search and read a little u will get the necessary info.
Click to expand...
Click to collapse
thanks a lot for this kind help, i will do it, don't worry. :good:
Don't worry bro u will certainly do what is required. I was the first who reported a bricked device while unlocking bootloader by unofficial method. After extensive search and trying different methods I came to this conclusion.
This is the official FunkyHuawei support thread.
FunkyHuawei is a (mostly) paid service which allows you to do the following:
1. Install the latest system software, even before it's released by OTA.
2. Install beta/prerelease system software, without needing to be a beta tester.
3. Recover a bricked phone.
4. Rebranding / Change the region of your phone (China -> Europe, for example, to get Google and so on.)
5. Root your EMUI 8 phone, even with stock recovery (This feature is free)
Except for rooting, all of these features are supported even if you cannot unlock your phone's bootloader.
To find FunkyHuawei, please Google it. Or you can find a link to the service within the following XDA Portal article.
https://www.xda-developers.com/android-oreo-emui-6-huawei-mate-9/
We are pleased to announce FHUnbrickFlashTool -- You can now repair any recent Huawei phone via fastboot, even if you cannot access eRecovery or boot the phone! Even if it doesn't show the Huawei logo, as long as you can get a fastboot connection to your computer, you can recover the phone! Google FHUnbrickFlashTool or check FunkyHuawei's reddit for details.
In cooperation with XDA, FunkyHuawei is offering a free credit to Recognized Developers and Recognized Contributers on XDA.
Please PM me for more details.
We will continue posting in this thread with updates regarding new software versions and releases regarding this device.
We will also be monitoring it so we can help anyone who has issues.
For device-specific information, please see the next post.
P10 Device-Specific Information
The P10 now has a relatively mature community with many methods to do many things.
However, there are still some things only possible with FunkyHuawei, so it would be most useful for:
1. Installing updates on bootloader-locked devices, even if the update is not approved by Huawei for your device.
2. Rebranding bootloader-locked devices, or rebranding to obscure carrier brandings.
3. Restoring bricked devices.
Note that even though the Mate 10 Root tool is designed for the Mate 10, it works perfectly on the P10 running Android O betas.
This tool is FREE, and might be easier than installing TWRP and rooting that way.
Frequently Asked Questions
Q: How much does FunkyHuawei cost?
A: You need to buy credits on the FunkyHuawei website. The price per credit varies depending on the number of credits you buy. Different operations cost different amounts of credits. However, the Root feature of the Mate 10 tool is free, and as mentioned above, Recognized Developers/Contributors of XDA can ask for a free credit.
Q: My phone is bootloader locked, and FRP locked. My bootloader unlock code dosen't work. It won't boot. eRecovery doesn't work. Can you help?
A: Yes. With the Mate 10 this is now a common situation. Contact FunkyHuawei for help in this situation. We'll need to access your computer remotely and the procedure is a little bit complicated, but the phone can be unbricked.
Q: I can't get my bootloader unlock code/don't want to unlock my bootloader, but I want to change my phone to something other than Chinese. Can you help?
A: Yes. Our new FunkyHuawei Rebrand Tool works on ALL recent Huawei phones, to rebrand them to another region even when the bootloader is locked.
Q: I'm not seeing the latest version listed on FunkyHuawei or elsewhere as an OTA. Why not?
A: Huawei has a very odd and unpredictable way of rolling out OTA updates. You can use FunkyHuawei to install the new version immediately, or can wait for the update to be rolled out. It might be a month or more after release until the update reaches your device from Huawei directly. We have no idea why.
Q: Why isn't FunkyHuawei free?
A: Because many of FunkyHuawei's features cost FunkyHuawei money to provide. Features that don't cost FunkyHuawei money to provide, like rooting the Mate 10 or our TWRP build for Mate 9/Oreo, for example, are generally made available for free. There are also bills to pay, kids to put through school, and so on.
Q: I noticed FunkyHuawei in an XDA Portal article!
A: FunkyHuawei loves XDA, and is cooperating with them as much as possible. Recognized Developers and Contributors on the XDA forums are welcome to claim a free credit from FunkyHuawei as well.
Q: I have a different question.
A: This is what this thread is for! Post away!
duraaraa said:
P10 Device-Specific Information
The P10 now has a relatively mature community with many methods to do many things.
However, there are still some things only possible with FunkyHuawei, so it would be most useful for:
1. Installing updates on bootloader-locked devices, even if the update is not approved by Huawei for your device.
2. Rebranding bootloader-locked devices, or rebranding to obscure carrier brandings.
3. Restoring bricked devices..
Click to expand...
Click to collapse
Luckilly the P10 community here is mature enough that there is no longer a need for Funky's services. However effective Funky may be, we can save ourselves the 30bucks and do it ourselves
We are pleased to announce FHUnbrickFlashTool -- You can now repair any recent Huawei phone via fastboot, even if you cannot access eRecovery or boot the phone! Even if it doesn't show the Huawei logo, as long as you can get a fastboot connection to your computer, you can recover the phone! Google FHUnbrickFlashTool or check FunkyHuawei's reddit for details.
We have added a brand new Android O build for the Chinese P10.
You will need to rebrand your phone to VTR-AL00 (all/cn) to install it.
Best to use HiSuite to install it -- check out Mate 10 rebranding information to find the correct version of HiSuite and instructions.
We now have Android O for International P10 and P10 Plus.
Check FunkyHuawei reddit for install instructions, or google for "Android O Builds for International P10 and P10 Plus now available! Instructions inside"
This is great news!!
If I only got some $:crying: but nice news
Does this include Treble?
tiktok1 said:
Does this include Treble?
Click to expand...
Click to collapse
Yes, of course.
Hey all, I'm having a problems to which i've been pulling my hair out and not sure what to do. Essentially, I had my phone rooted, although later decided I wanted to unroot. To unroot I used an app called "simply unroot" however it did not fully unroot my device, just made it worse, my phone does not pass the safety net, however "root checker apps" suggest my phone is not rooted, although some apps recognise my phone as being rooted. My phone bootloader is unlocked, but the OEM toggle in the developer options is not set as enabled, and is NOW greyed out so i cant click it, meaning i do not have access to any fastboot commands and thus cannot flash a recovery.img. Although, believe after having trying to unroot it had automatically disable OEM. I have tried to lock the bootloader in the hopes that OEM toggle would no longer be greyed out, but cannot do this as i dont have access to fastboot commands. Even with TWRP i cannot flash anything just promps me with Error 9. I have tried storing the UPDATE.app within the dload folder, but that doesnt work either. I have no idea how i can recover this device. Fell like i've tried everything. Please help.
rustymole said:
Hey all, I'm having a problems to which i've been pulling my hair out and not sure what to do. Essentially, I had my phone rooted, although later decided I wanted to unroot. To unroot I used an app called "simply unroot" however it did not fully unroot my device, just made it worse, my phone does not pass the safety net, however "root checker apps" suggest my phone is not rooted, although some apps recognise my phone as being rooted. My phone bootloader is unlocked, but the OEM toggle in the developer options is not set as enabled, and is NOW greyed out so i cant click it, meaning i do not have access to any fastboot commands and thus cannot flash a recovery.img. Although, believe after having trying to unroot it had automatically disable OEM. I have tried to lock the bootloader in the hopes that OEM toggle would no longer be greyed out, but cannot do this as i dont have access to fastboot commands. Even with TWRP i cannot flash anything just promps me with Error 9. I have tried storing the UPDATE.app within the dload folder, but that doesnt work either. I have no idea how i can recover this device. Fell like i've tried everything. Please help.
Click to expand...
Click to collapse
Why you pose this question in the "official funkyhuawei support" thread is beyond me....
Only thing that comes to mind is: do you have USB debugging enabled in the developers options? It should be enabled if you want to use ADB or Fastboot.
rustymole said:
Hey all, I'm having a problems to which i've been pulling my hair out and not sure what to do. Essentially, I had my phone rooted, although later decided I wanted to unroot. To unroot I used an app called "simply unroot" however it did not fully unroot my device, just made it worse, my phone does not pass the safety net, however "root checker apps" suggest my phone is not rooted, although some apps recognise my phone as being rooted. My phone bootloader is unlocked, but the OEM toggle in the developer options is not set as enabled, and is NOW greyed out so i cant click it, meaning i do not have access to any fastboot commands and thus cannot flash a recovery.img. Although, believe after having trying to unroot it had automatically disable OEM. I have tried to lock the bootloader in the hopes that OEM toggle would no longer be greyed out, but cannot do this as i dont have access to fastboot commands. Even with TWRP i cannot flash anything just promps me with Error 9. I have tried storing the UPDATE.app within the dload folder, but that doesnt work either. I have no idea how i can recover this device. Fell like i've tried everything. Please help.
Click to expand...
Click to collapse
You can use FunkyHuawei eRecovery method to return it to stock.
I recently updated my P10 VTR L29 C432 from nougat to Oreo B360 via oreoupgrade script method as posted in forum but after update my bootloader seems to be locked again i wanted to root my phone via installing TWRP but it's not allowed by fastboot
Any solution or any solution to unlock bootloader or root the phone without losing data !? I have too much files and apps on phone that i won't lose
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
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.
ahsvanz
try
C:\ADB >fastboot devices
C:\ADB >fastboot OEM device-info
etc
replacing
C:\ADB with where ever you fastboot file is located
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
have you tried the code above ??
cant you just download the official original firmware and flash that ? im not familiar with the oneplus flashing techniques, ive always had samsungs except for the htc evo 3d back in the day
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
slimmynine said:
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
Click to expand...
Click to collapse
how does the one plus flash firmware ? for samsung we use a tool called odin, do you not have a similar tool for your device ?
I don't recall having any toolkit like that, but in order for the toolkit to work.. do you need to have an unlocked bootloader?
Cause the main issue is that I can't unlock it.
i dont think so, if your flashing an official firmware, but for your device i cant be sure of that
?
did you try running your commands as an su , is your device rooted ? you could try sideloading an update.zip maybe
what does it say when you flash this command ? true, true false ?
C:\ADB>fastboot OEM device-info
maybe this will help https://forum.xda-developers.com/t/...us-2-back-to-stock-100.3269543/#post-64279667
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
yeah i think some phone makers lock down the bootloader, like its unlocked but when i try to flash a gsi it says device locked state
jamsandpeabug said:
alcatel has a program to download and install firmware but the device is not listed, cannot find fw on the net
Click to expand...
Click to collapse
OK try
c:\adb
Adb fastboot oem device-info
Replacing
C:\adb
With where ever your fastboot is located
Just to check if your device is showing is oem locked or unlocked, it will display with a true or false option. I can't really advise to much as I don't have experience with that device
You could also try
fastboot oem unlock_critical
Not sure if that will work for your device though
Idk what else to recommend, are you stuck at boot ? Can u boot into recovery mode ? Do u have an ext sd card slot
OT-6025D | GSMSERVERPRO
gsmserverpro.com
Is that your firmware
Alcatel 1s Flash File Download [Stock ROM or Firmware
You can Download latest flash file and flash tools for Alcatel 1s phone here. Original stock ROM or Firmware available for free.
mobilereset99.com
Have youlooked at that
if you can confirm your phone has a mtk chipset use mtkclient to bootloader unlock it https://github.com/bkerler/mtkclient
otherwise youre out of luck
But
jamsandpeabug said:
im not stuck at boot, i want to flash gsi but it says device is in locked state even with oem unlocked in dev options, adb debugging enabled etc , and just wont let me flash.. its starts flashing and then fails due to locked state
Click to expand...
Click to collapse
If the flashing starts, and fails, the os would be overwritten and you wouldn't be able to boot. So what you mean is the process trys to start but fails, right yh then I don't know what else I can say to try and help, let's hope mtkclient is an avenue you can pursue
MOD ACTION:
Thread closed since OP has no content.