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 all!
Today my Oppo Reno 5G 10x Zoom arrived. As my previous phones I would like to root my new phone too to use e.g. Titanium Backup.
I have currently installed Color OS V7.1, Android 10, Model CPH1921, Build CPH1921EX_11_C.35.
I did the following:
Enable the Developer Options on your device. To do this, go to Settings>>About Phone>>tap on the Build Number 7 times till you see a toast message “You are now a developer”.
Under the Developer Options, you need to enable the OEM Unlock option as well. To do that again head to the Settings>>Developer Options>>enable OEM Unlock.
Download and set-up the ADB and Fastboot tools on our PC.
Now, head to the Platform-tools folder and open the CMD or command prompt.
Now, in the command prompt, enter the below command and press the Enter button on your keyboard;
adb devices
You will get a pop-up on your smartphone with a message “Always allow from this computer”. You need to press OK
Type the below command to enter the bootloader mode, and press Enter;
adb reboot bootloader
After rebooting the fastboot window (this window) appears for about 1s an the phone immediatelly reboots.
So I am unable to finnish the steps from this guide.
What am I doing wrong or what is the problem causing this?
Thanks for any help in advance!
Try to see if your device supports bootloader unlock.
You'll need an app (deep testing) to apply for permission before you can unlock it.
I'm also looking for a way to unlock my bootloader... Same model cph1921. Mine unfortunately says it's a carrier phone so I can't go ahead with the unlock. I'll tinker around to change region and unlock if that be possible.
Let me know how you get along @htcdesire-hd
Hnk1 said:
Try to see if your device supports bootloader unlock.
You'll need an app (deep testing) to apply for permission before you can unlock it.
I'm also looking for a way to unlock my bootloader... Same model cph1921. Mine unfortunately says it's a carrier phone so I can't go ahead with the unlock. I'll tinker around to change region and unlock if that be possible.
Let me know how you get along @htcdesire-hd
Click to expand...
Click to collapse
Hi,
thanks for the suggestion with this app, that might be useful for me in the future!
That the Oppo Reno was not unlockable (or at least I did not find a way) was a dealbreaker for me! So I sent it back to the retailer a few days after writing the post above.
That means I am not able to test the app you suggested with the Oppo Reno 5G anymore.
Now I have a Xiaomi Poco F2 Pro 256GB and I am very happy with my device. Unlocking and rooting was even supported by the manufacturer (after 1 week mandatory waiting time) and the Hardware is also very good. So I am glad I sent back the Oppo Reno...
htcdesire-hd said:
Hi,
thanks for the suggestion with this app, that might be useful for me in the future!
That the Oppo Reno was not unlockable (or at least I did not find a way) was a dealbreaker for me! So I sent it back to the retailer a few days after writing the post above.
That means I am not able to test the app you suggested with the Oppo Reno 5G anymore.
Now I have a Xiaomi Poco F2 Pro 256GB and I am very happy with my device. Unlocking and rooting was even supported by the manufacturer (after 1 week mandatory waiting time) and the Hardware is also very good. So I am glad I sent back the Oppo Reno...
Click to expand...
Click to collapse
I hadn't have an oppo before so was unaware they are so strict with the bootloader. I ordered a OnePlus as well but still have the oppo. I'll try sometime and let you know.
For me, not having ad free experience and unable to change dpi is a deal breaker
Hnk1 said:
I hadn't have an oppo before so was unaware they are so strict with the bootloader. I ordered a OnePlus as well but still have the oppo. I'll try sometime and let you know.
For me, not having ad free experience and unable to change dpi is a deal breaker
Click to expand...
Click to collapse
Yes same for me, I also thought that Oppo is not that restricted! Ok, thanks, I will look forward to that.
Everyone has their own preferences. For me the adds in the system apps are barely annoying and I don't have any reason to change my DPI (battery performance is enough at my point of view). At most not having a 10x zoom is a little bit annoying but there are versions of my phone which have a 10x zoom instead of a macro camera.
I wonder if it would be possible to install the "update" with the modified Magisk boot.img to gain root access. Unpacking boot.img is hassle-free, but despite the "codecs" for 7zip, I can't repack the archive with the modified file. There is also the issue of bricking the oppo .. Has anyone tried something? Any other ideas?
Did anyone come to a solution for this , its such a great phone
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
TLDR; I am wondering if all U.S. phones with Snapdragon cannot be normally rooted by just enabling OEM unlock/unlocking bootloader and must be rooted in an expert/costly method. Or if accounts from people saying they enabled OEM unlock on their Moto G Powers I read were not just fictional or with non-U.S. phones.
Click to expand...
Click to collapse
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked. I found this to be the case with the (unlocked, not carrier-specific) U.S. Moto G Power 2021 phone I just bought. I cannot tick OEM Unlocking in Developer settings, it's greyed out. I found users here and on other forums saying that it's possible to conventionally root Moto G Power 2021 phones, which I thought up till recently because I easily got an ID from the Motorola website, but obviously couldn't proceed with fastboot because OEM Unlocking is disabled and I can't change that. (in CMD fastboot said exactly this: OEM must be unlocked to proceed.)
Oddly, some users said that the option stopped being greyed out after a few days or a week. I contacted Motorola to see if this is a design thing but they were of no help, just telling me not to root as if I was unaware it voids warranty. Notably, just as many users said that the option would always be disabled, which began to make sense given what I learned next.
It was soon after I found people saying that all U.S. Android phones with Snapdragon consciously lock bootloader. All carrier-specific and unlocked varieties. (Consequently, there are services that do it for you, but this costs money and I'm interested in a phone I can root myself for free.) I was surprised it took me as long as I did to hear of this, and afterwards I searched for this specifically to get more clarity but didn't find any articles or documentation. It explains everything, of course, except for why I read some people (including here) were able to enable OEM Unlocking on their Moto G Power 2021 devices. (perhaps they were not U.S. phones but this was not mentioned.)
At this point if there's no way to enable OEM unlock I'm simply going to return the phone as I want a phone that I can root.
Snapdragon Androids disabling OEM unlock/bootloader unlocking is simply because of U.S. company decisions, because non-U.S. Android phones with Snapdragon do allow it. Because of this, I'm looking at international/European GSM Androids with Snapdragon, (such as the Xiaomi Mi A3) which the majority of anywhere-near-recent Androids clearly have, that would allow me to do this. I'm going to be as sure as I can it will be compatible in the U.S. (I use AT&T) and that it will be feasible to root for free.
Thanks for reading, especially if you got this far.
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
jwoegerbauer said:
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
Click to expand...
Click to collapse
Motorola system partition is write-protected, the bootloader must be unlocked for permanent root.
KindleMatchLight said:
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked...
Click to expand...
Click to collapse
See the CID and OEM unlock posts
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
If you get the bootloader unlocked
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
Motorola system partition is write-protected, the bootloader must be unlocked for permanent root.
Click to expand...
Click to collapse
Absolute nonsense.
KindleMatchLight said:
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked. I found this to be the case with the (unlocked, not carrier-specific) U.S. Moto G Power 2021 phone I just bought. I cannot tick OEM Unlocking in Developer settings, it's greyed out. I found users here and on other forums saying that it's possible to conventionally root Moto G Power 2021 phones, which I thought up till recently because I easily got an ID from the Motorola website, but obviously couldn't proceed with fastboot because OEM Unlocking is disabled and I can't change that. (in CMD fastboot said exactly this: OEM must be unlocked to proceed.)
Oddly, some users said that the option stopped being greyed out after a few days or a week. I contacted Motorola to see if this is a design thing but they were of no help, just telling me not to root as if I was unaware it voids warranty. Notably, just as many users said that the option would always be disabled, which began to make sense given what I learned next.
It was soon after I found people saying that all U.S. Android phones with Snapdragon consciously lock bootloader. All carrier-specific and unlocked varieties. (Consequently, this there are services that do it for you, but this costs money and I'm interested in a phone I can root myself for free.) I was surprised it took me as long as I did to hear of this, and afterwards I searched for this specifically to get more clarity but didn't find any articles or documentation. It explains everything, of course, except for why I read some people (including here) were able to enable OEM Unlocking on their Moto G Power 2021 devices. (perhaps they were not U.S. phones but this was not mentioned.)
At this point if there's no way to enable OEM unlock I'm simply going to return the phone as I want a phone that I can root.
Snapdragon Androids disabling OEM unlock/bootloader unlocking is simply because of U.S. company decisions, because non-U.S. Android phones with Snapdragon do allow it. Because of this, I'm looking at international/European GSM Androids with Snapdragon, (such as the Xiaomi Mi A3) which the majority of anywhere-near-recent Androids clearly have, that would allow me to do this. I'm going to be as sure as I can it will be compatible in the U.S. (I use AT&T) and that it will be feasible to root for free.
Thanks for reading, especially if you got this far.
Click to expand...
Click to collapse
You must wait, I believe it was several days of the device being online (wifi at least) to get it to permit unlocking the bootloader. I know with mine (US Xfinity Wireless), out of the box, it was gray, but 2 or 3 days later it was able to be toggled and I unlocked and got Magisk installed easily, using the patch stock boot.img method, and flashing it via fastboot beyond that. So you can do it, just can't do it before you activate the thing properly I think is the main block there you're describing. So perhaps those outside the US (with US models they can't toggle) can connect to a VPN'd wifi network and have it look like it's in the US, maybe.
There's a lot that can be done on these with just tinkering to get it there is all. But make sure you have your stock firmware is all, so you can quickly get it back into bootloader and just a flash away to fix anything really.
jwoegerbauer said:
Absolute nonsense.
Click to expand...
Click to collapse
Okay. Legit question here... How does one go about injecting SU binary to the system on the moto g 2021 series with secured boot?
Why should SU binary get housed in /system/... ? It's irrelevant where it's located, the main thing is that it's available and executable. Even Magisk doesn't store it in /system/.. but in /data/..
Because folder /data/local/tmp by default is mounted as RW my recommendation is to store it there. Using this storage place isn't conflicting with SELinux and/or AVB.
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC-HERE> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
When you have to run a shell command what requires elevated rights, then you run
Code:
adb devices
adb shell "/data/local/tmp/su -c '<SHELL-COMMAND-HERE>'"
Deleted member 1890170 said:
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
Click to expand...
Click to collapse
it needs to be unlock
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.
First of all, i need to say that my english is not the best since im from brazil, anyway that said, im trying to unlock my realme bootloader, ive already tried to use Deep test. But every time that i try to install the app i recive this error messange "An app with the same signature has already been installed", and i also have tried using ADB and Fastboot, but every time that i try to reboot my cellphone in fastboot, it only gives me a black screen and restarts the cellphone, if anyone know some way to resolve this, or know what to do, would help me a lot
It's possible that some fastboots have a timeout if you don't talk to them.
Are you sure that you're not getting fastboot at all?
Are you using Linux or Windows? lsusb or devmgmt.msc?
Renate said:
It's possible that some fastboots have a timeout if you don't talk to them.
Are you sure that you're not getting fastboot at all?
Are you using Linux or Windows? lsusb or devmgmt.msc?
Click to expand...
Click to collapse
im using windows, my primary suspect is that im in fact not getting to the fastboot at all
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016 I was surprised to not find this information in any of the forums. This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone...
forum.xda-developers.com
Wow, 2016? And they haven't gone out of business yet?
aIecxs said:
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016 I was surprised to not find this information in any of the forums. This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone...
forum.xda-developers.com
Click to expand...
Click to collapse
wow i didnt have read or found anything about this, but that gives me a little question, how do ppl actually flashs custom ROM's on realme phones?
you can unlock with official In-Depth Test apk
or
unofficial unlock method without fastboot (mtkclient)
aIecxs said:
you can unlock with official In-Depth Test apk
or
unofficial unlock method without fastboot (mtkclient)
Click to expand...
Click to collapse
When i try to use in-depth test says "Device incompatible"
of course that was just example possibility, I don't know if apk exist or unlocking seccfg works. do your homework
[DISCUSSION] A thread to collate and share what is known about unlocking fastboot on Oppo devices
Admin: Please move/delete this thread if it is in the wrong place or against the rules. I wanted to create a thread to discuss unlocking fastboot mode on Oppo devices in general, rather than discussing it in terms of any one device in...
forum.xda-developers.com
when i use Deep Test 1.0.1 it says that my device dosent suport deep test, when i try to install the 1.1.0 version thats happens
try this