Related
This is a problem, and it's doing my nut. I have a Vodafone Smart Mini 7, which I desperately want to root, to get all of Google's bloatware and the stuff the original network provider put on it.
I've already unlocked it to all networks, but the bootloader is being a PITA. I've done the usual with adb and fastboot, namely put it into USB Debugging, and then done this;
Code:
adb devices
adb reboot bootloader
fastboot getvar all
When I get to the section on the bootloader, it advises me that it's Secure.
I tried to use
Code:
fastboot oem unlock
and when I confirm on the phone that I want to unlock it, I get told that Remote Unlock is not allowed.
I assume that the fact that fastboot getvar all says that the bootloader is secure, means I need some sort of key to get it off. My old network provider don't know where to get it from, my tech team don't know where to get it from and I'm screwed.
Anyone got any ideas on whether I can get round the "secure" part of this, like some way of finding the key for it? Thanks
TootyRooty said:
This is a problem, and it's doing my nut. I have a Vodafone Smart Mini 7, which I desperately want to root, to get all of Google's bloatware and the stuff the original network provider put on it.
I've already unlocked it to all networks, but the bootloader is being a PITA. I've done the usual with adb and fastboot, namely put it into USB Debugging, and then done this;
When I get to the section on the bootloader, it advises me that it's Secure.
I tried to use
and when I confirm on the phone that I want to unlock it, I get told that Remote Unlock is not allowed.
I assume that the fact that fastboot getvar all says that the bootloader is secure, means I need some sort of key to get it off. My old network provider don't know where to get it from, my tech team don't know where to get it from and I'm screwed.
Anyone got any ideas on whether I can get round the "secure" part of this, like some way of finding the key for it? Thanks
Click to expand...
Click to collapse
I have the exact same issue I read some threads and nothing solid has come out of it some say they managed to get root but others say they bricked the phone
Any news on this topic? I too have one i desperately would like to root because it is permanently full and you cant do anything wih it. The Google apps and the apps installed by my service provider take up all the onboard storage space. I downloaded only Whatsapp and Facebook Lite and bam,the phone is completely full and useless as it cant do updates,runs extremely slow and does all sorts of random stuff like restarting on its own etc. driving me utterly insane.
hi!
after reading all related post in this forum and searching google for ages, i am still not able to unlock my z5c's bootloader. it is not a lack of skills or know-how - i have successfully unlocked my z1c and z3c - but this one simply does not unlock.
i have tried both windows and linux, used shell and flashtool, all drivers properly installed, phone is correctly recognized, bootloader unlock is positive, oem unlock and usb-debugging are activated, phone is in fastboot but i still end up with error "command did not succeed". flashtool additionally shows "oem unlock not activated?". it is, but doesn't seem to have any effect.
i also tried to include the .txt file with the unlockcode into flashtools filestructure: flashtool does something but can't finish the unlock proccess and my phone is not resetting.
i even tried those one-click unlocker without success.
and there is something fishy about this phone: three month ago i got it brandnew from a vendor in china via ebay and first thing i did was connecting it to the pc companion to upgrade the firmware which was 5.1 and it told me, firmware was up to date... so i tried the repair option and it told me "that due to it's prototype status it can only be upgraded from certain ips" - although the phone does not show any hints of being a prototype, neither software- nor hardwarewise and even if it was, it wouldn't prevent the bootloader from being unlocked (afaik).
so you guys are my last hope! any further ideas???
regards,
andi
Hmm... Possibly not the solution but have you tried enabling "Unknown Sources" as well?
Another thing is - you can try flashing a later version of the firmware with Flashtool - one that is common. Afaik there are some versions that have trouble unlocking. Try flashing something like Nordic Unbranded, boot it up, make the settings again.
P.S. Flashing does NOT remove the old leftover firmware - it just writes on top. So you should format the partitions (/system, /data, /cache, /dalvik-cache) before flashing in order to start clean.
when i couldn't upgrade the firmware via pc-companion i used flashtool to flash 7.1.1 (some german version) which i kept ever since. so flashing a different firmware before unlocking is something worth trying? i thought of this as well but never actually tried it because i was just too lazy going though all the setup process again if the attempt failed just like the others... but i'll give it a try then!
and thanks for the input!
Hy,
For me i had to make two steps :
- Flash a non-branded firmware from Xperifirm
- Network unlock it (actually for me it unlocked automatically at the end of the warranty ). This step it is critical (as i was informed in the Sony store)
Then the normal cmd command through adb worked fine.
Basically for me the network lock / warranty was the issue that prevented me to unlock the bootloader
thank you very much for your Input! but there is no network lock...
what i was going to do was flashing a different firmware and try again - and there is something else i didn't think of: the usb2 connector of my mainboard is blocked by an infrared device to power up my pc by voice command via alexa and a harmony hub. and to still be able to use the front usb ports of my case i connected them with an adapter cable to a free usb3 socket on the mainboard…
so it might have been the firmware, the usb2 port on a usb3 socket or prototype-status that caused the trouble - but i'll never know cause basically i'll give up on that phone since more issues occured… i contacted the vendor yesterday and it seems i'll get a full refund!
i now got my hands on a shiny new galaxy s7 and hopefully i'll experience the joys of oreo 8.1 and lineage 15.1 anywhere soon without the hazzle!
thanks again for your help and regards,
andi
So I got this Sony Xperia X model F5121 from one of my relatives, and I ran into quite a few issues when I tried rooting it. it says Bootloader Unlock Allowed: NO, which would mean that i couldn't get into fastboot mode and unlock my bootloader but here's the very specific and weird part: I can get into fastboot mode, at least I believe so. My phone was carrier locked to Vodafone but I payed a professional to unlock that and now I can use every SIM I want. I looked online and the first XDA page said that unlocking the SIM meant that fastboot mode is unlocked as well. So I tried, I plugged my phone in while holding the volume key, a blue light popped up and it meant I was currently using fastboot mode, but when i try doing anything it says "waiting for devices" and doesnt end up working at all. Am I missing some drivers? Is it just impossible? Could one of you be kind enough to provide the needed files and some instructions for this procedure? i'm asking for a lot, I know but if there's anyone kind enough. I'm running the absolute latest version of Android 8 Sony provides.
EDIT: YEs, used adb shell, I have the ADB drivers, I tried the szuzu install or what the TWRP codename for it is, but everything just stops at "waiting for devices" and I can't do anything.
Since you are not allowed to unlock the bootloader - Bootloader unlock allowed - No, there is no way to unlock it and root it. Sorry.
even if you want to try again, make sure to force install googles drivers
instead of sonys
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.