Related
Hi,
I have once rooted my google pixel, but I changed my mind, and decided to unroot it and lock the bootloader.
I chose "lock" in the twrp menu, and I entered an endless loop.
Now the bootloader is locked and won't boot. The phone just splashes the initial screen and off, a few seconds after that, splashes the screen, and off,.....repeatedly. It looks like as soon as the initial "GOOGLE" screen appears, the phone resets itself.
I turned on with the volume down button on, and connect to the desktop computer (I use linux with adb and fastboot installed which work perfectly) and enter "fastboot flashing unlock", but it returns
Code:
$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.009s
I also tried to enter recovery mode, but it began to splash initial screen on and off again.
How can I recover from this situation?
Thanks in advance!
edit:
"fastboot flash recovery twrp-3.3.0-0-sailfish.img" now returns like this.
Code:
$ fastboot flash recover twrp-3*img
Sending 'recover' (31000 KB) OKAY [ 0.892s]
Writing 'recover' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.074s
edit2:
Looks like I unchecked "OEM UNLOCK" in Development Option and locked......can I recover from this?
Have a search using "bricked pixel locked bootloader" and trawl through the threads it throws up for workarounds etc. Some people have had some success depending on what the device was running but it's usually a non recoverable scenario.
Thanks. I'll give it a try. I'm almost abandoning.....
junglism93 said:
Have a search using "bricked pixel locked bootloader" and trawl through the threads it throws up for workarounds etc. Some people have had some success depending on what the device was running but it's usually a non recoverable scenario.
Click to expand...
Click to collapse
I tried it now. Most of the procedures were fine, but the important parts (write .img) failed. I attach the logfile. I abandoned....
maverick6664 said:
Looks like I unchecked "OEM UNLOCK" in Development Option and locked......can I recover from this?
Click to expand...
Click to collapse
I am on Android Q beta 5 now and i do not have that option in the development options at all.
I also have Nexus 3, 4 & 5 and i played so much with them i can't even remember. Never had any problems. I have repartitioned them, changed mac addresses and many things but they never bricked. Do i have to worry about google pixel when i'll unlock bootloader? I got it about 3-4 days ago. I thought they are as cool to play with as Nexus 4 & 5 were. Is it not right?
matusala said:
I am on Android Q beta 5 now and i do not have that option in the development options at all.
I also have Nexus 3, 4 & 5 and i played so much with them i can't even remember. Never had any problems. I have repartitioned them, changed mac addresses and many things but they never bricked. Do i have to worry about google pixel when i'll unlock bootloader? I got it about 3-4 days ago. I thought they are as cool to play with as Nexus 4 & 5 were. Is it not right?
Click to expand...
Click to collapse
I've learned. "Don't root. Don't unlock bootloader."
@matusala you can unlock the bootloader and flash stuff as you did on the nexus line of devices. I'm on Q beta 5 with bl unlocked, I've had lineage running on it for a while and also had magisk etc installed. The key with these pixel A/B slot devices is that your system must be 100% stock before relocking the bootloader. If it is not It will end up bricked as you will no longer have a working boot image or recovery as they are in the same partition. The rule is to never relock the bootloader unless you are 100% sure that your system is 100% back to full stock.
I certainly won't be re locking my bootloader, ever!
@junglism93 How did you unlock on Q beta 5? There is no "OEM UNLOCK" option in Development Options in here. Do i have to just run fastboot flashing unlock and that's it?
I know this pixel A/B slot thing. My router has exactly same layout and when i flash system on it i get to choose where to flash. I can have different version in A/B slot of my router. Is on google pixel the same? Do you have to choose which slot to flash? Can you have custom rom on A slot and full stock rom on B slot?
matusala said:
@junglism93 How did you unlock on Q beta 5? There is no "OEM UNLOCK" option in Development Options in here. Do i have to just run fastboot flashing unlock and that's it?
I know this pixel A/B slot thing. My router has exactly same layout and when i flash system on it i get to choose where to flash. I can have different version in A/B slot of my router. Is on google pixel the same? Do you have to choose which slot to flash? Can you have custom rom on A slot and full stock rom on B slot?
Click to expand...
Click to collapse
I unlocked my bootloader back on stock pie, i have it on mine but it's greyed out as already unlocked so no idea on that one! My knowledge on A/B slot ain't great, it's just what I've read on here re the pixel bricking scenario so I didn't do the same when I unlocked my bootloader etc. I doubt running a separate ROM on each slot works as when you perform an update it will write to slot a or b (the slot you aren't using) and then hop onto the updated slot upon reboot, alsoif the update borks you can roll back to the previous slot and still have a working system.
That's about as far as my knowledge of it goes mate
Leaving the bootloader unlocked doesn't void the warranty or things like that, also it's a life saviour if *anything* goes wrong, even with official updates. Why not leaving that on?
The lesson here is not "don't root" or "don't unlock the bootloader", cause with an unlocked bootloader you can recover from pretty any kind of software malfunction.
Unfortunately, with a locked bootloader I've never seen anyone succesfully recover the device, cause you cannot send commands.
maverick6664 said:
I've learned. "Don't root. Don't unlock bootloader."
Click to expand...
Click to collapse
Hmmm......correction.
I would say:
"Root with caution. Otherwise don't root."
Rooting doesn't necessarily cause a trouble. Usually it helps. But my Google Pixel used to show alert screen message upon every boot. It's a bit messy.
@TENN3R I have Android Q beta 5 on my pixel and i can't unlock bootloader. OEM unlock is not in my developer options menu. How can i unlock it's bootloader?
I tried unlocking and now i see that option in developer options, but it's greyed out and i can't press it. What can i do.
It seems these pixel phones are garbage compared to nexus line. Those were so much better!
matusala said:
@TENN3R I have Android Q beta 5 on my pixel and i can't unlock bootloader. OEM unlock is not in my developer options menu. How can i unlock it's bootloader?
I tried unlocking and now i see that option in developer options, but it's greyed out and i can't press it. What can i do.!
Click to expand...
Click to collapse
I think I read somewhere in the android beta subreddit that is a Q beta related problem, and in Pie should work.
How did you unlock it since it wasn't there? Is the toggle grayed out in "off" position or "on"? Cause if it's enabled than you're ok
TENN3R said:
I think I read somewhere in the android beta subreddit that is a Q beta related problem, and in Pie should work.
How did you unlock it since it wasn't there? Is the toggle grayed out in "off" position or "on"? Cause if it's enabled than you're ok
Click to expand...
Click to collapse
I followed this guide and it worked. It unlocked my bootloader. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
Now option is greyed out again in "off" position but it says "Bootloader already unlocked"
Maybe i got verizon model but in cell-unlocked state, because seller had written that it's unlocked. He meant provider lock of course.
@matusala Happy days mate, have fun and remember the first rule of pixel club 'Never re lock the bootloader'
junglism93 said:
@matusala Happy days mate, have fun and remember the first rule of pixel club 'Never re lock the bootloader'
Click to expand...
Click to collapse
Good luck @matusala from me also, and don't give in the first "Don't keep bootloader unlocked' alert screen!! Otherwise you might fall into a bad luck "bricked pixel" like me!
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
matusala said:
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
Click to expand...
Click to collapse
Nice to hear that. It was a good lesson to me. I have two xperia's (after google pixel dies, I bought one.) Somehow xperia's are not re-lockable. It is also mentioned in Sony Xperia forum. I guess it must be a warning from Sony. :laugh:
matusala said:
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
Click to expand...
Click to collapse
But reading this page, relocking by "adb oem lock" looks safe. At least this is a google's page. Google is responsible for it. And you can avoid the annoying boot message.:laugh:
BTW, "adb oem lock" doesn't work with xperia. Sony seems to like leaving their products unlocked.
maverick6664 said:
But reading this page, relocking by "adb oem lock" looks safe. At least this is a google's page. Google is responsible for it. And you can avoid the annoying boot message.:laugh:
I'm sure that is safe if you're updating from full stock to full stock, with mods on board a relock is almost suicidal and the threads about bricked pixels back that up.
If you don't like the warning screen, do what I do, don't watch your phone reboot
Click to expand...
Click to collapse
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
7 days what? Tmo A326U doesnt have the option to unlock the bootloader, you need to pay the people here that provide the service. They are the only ones that seemingly know how to get it unlocked, and I can vouch for it.
Seriously... So there's no way to unlock for free, or by waiting...?
Not a bootloader unlock. Its not just Tmo that are locking these down tighter.
You can unlock it for free if you can figure out whatever they do ;-)
Nah idc about a network unlock since I don't have service for this phone, I just wanna know if its possible to unlock the bootloader... I've tried everything
Who is talking about a network unlock?
TimmyP said:
Who is talking about a network unlock?
Click to expand...
Click to collapse
You said not a "bootloader unlock" so I was assuming you're talking about network unlock... Sorry, but should I just give up, there's seemingly NO WAYY to unlock the bootloader of a T-Sh*t phone.
Oh just misunderstanding my bad. I meant you cant wait for a bootloader unlock, but you can wait and maybe they would carrier unlock it later... but thats not what you want anyways.
TimmyP said:
Oh just misunderstanding my bad. I meant you cant wait for a bootloader unlock, but you can wait and maybe they would carrier unlock it later... but thats not what you want anyways.
Click to expand...
Click to collapse
That's kinda sad, I think I'm gonna just give up, but thanks for the information... Hopefully something happens in the future that allows it to be unlocked soon... Thanks man
I doubt they'll bring it back. OEM unlock that is. My phone is over 7 days old and I did the factory reset by holding the volume down and power buttons and then the volume up and power button and did the full factory reset. OEM unlock is still gone. Yes I got the developer options turned on. I rooted a couple of Nexus 6p's which of course are obsolete now since they were 3G and there is no backward capability. At least I got them used, replaced the batteries myself and can use them as WiFi phones with Talkatone through my WiFi. Read some blurbs about Kingo root working but I'd like to see that someone has pulled it off with the A32. Am under a 2 year obligation but I bought a second one to experiment on. I did that before I found out there was no OEM unlock. Well, if I break one, I'll have a backup. Except the phone is tied to the SIMM and I'd have to bring the backup in to have it reprogrammed.
TimmyP said:
Who is talking about a network unlock?
Click to expand...
Click to collapse
Any good service to network unlock SM-A236U or U1. Flashed XAA t no avail the Carrier_ID stays at DSH...
iabhua said:
Any good service to network unlock SM-A236U or U1. Flashed XAA t no avail the Carrier_ID stays at DSH...
Click to expand...
Click to collapse
I am working on unlock for it but I need root or a device on low security update. I am almost close to an solution if your device security patch is low please let me know
TimmyP said:
7 days what? Tmo A326U doesnt have the option to unlock the bootloader, you need to pay the people here that provide the service. They are the only ones that seemingly know how to get it unlocked, and I can vouch for it.
Click to expand...
Click to collapse
Do you have any device with an unlock bootloader or unlock? I am trying to get a ram dimp for days nobody have an device.
andioshelp said:
I am working on unlock for it but I need root or a device on low security update. I am almost close to an solution if your device security patch is low please let me know
Click to expand...
Click to collapse
I have two SM-A236U’s but unfortunately one has binary 6 FW and the other binary 7.
1.fuxk_ said:
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
Click to expand...
Click to collapse
There was a similar procedure to unlock bootloader on a samsung mtk (A125U) same carrier as yours (T-Mobile TMB and the same applies to MetroPCS TMB) basicaly, you had to flash BL files from the A125W (canadian version) then unlocking bootloader using testpoint (bootrom mode) then using any paid or free app (in my case i use a paid one because i run a repair shop). even if you unlock bootloader using paid tools, it gets locked again when it turns on. (i tested it without flashing BL files)
sadly, i dont have a A326U lying arround to test said procedure.
1.fuxk_ said:
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
Click to expand...
Click to collapse
Did you tried, instead of fastboot oem unlock, fastboot flashing unlock
DjoFight said:
Did you tried, instead of fastboot oem unlock, fastboot flashing unlock
Click to expand...
Click to collapse
In case people need the procedures for those processes, I wrote this up recently to help others do it easier than it was for me to figure out.
How to un-freeze an unresponsive Samsung Galaxy A32 5G with reboot, reset, factory reset, odin mode, download mode, android recovery mode & debug mode
Has any one made any progress regarding the missing oem unlock? I know what parameters to add to our kernel v1 to v3 during building to enable oem unlock and add access to fastbootd. Because of project treble our options have changed.
Sources:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
Sign in
DOCUMENTATION
Docs
More
Getting Started
Security
Core Topics
Compatibility
Android Devices
Reference
GO TO CODE ➚
Overview
Architecture
Overview
Hardware Abstraction Layer (HAL)
Kernel
HIDL (General)
HIDL (C++)
HIDL (Java)
Configuration
Device Tree Overlays
Vendor NDK
Vendor Interface Object
AIDL
Bootloader
Overview
Boot Reason
Boot Image Header
Implementing Bootconfig
Recovery Images
DTB Images
Supporting OTA Updates
Locking and Unlocking the Bootloader
Version Information in AVB Properties
Fastboot in Userspace
Partitions
Audio
Camera
Connectivity
Data
Display
Fonts
Graphics
Interaction
Media
Performance
Permissions
Power
Runtime
Settings
Storage
Virtualization
Tests
Updates
AOSP
Docs
Core Topics
Was this helpful?
Locking/Unlocking the Bootloaderbookmark_border
On this page
Unlocking the bootloader
Locking the bootloader
Setting lock/unlock properties
Protecting critical sections
By default, most Android devices ship with a locked bootloader, meaning that users can't flash the bootloader or device partitions. If needed, you (and device users with Developer options enabled) can unlock the bootloader to flash new images.
Unlocking the bootloaderTo unlock the bootloader and enable partitions to be reflashed, run the fastboot flashing unlock command on the device. After setting, the unlock mode persists across reboots.
Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the get_unlock_ability to 1). After setting, this mode persists across reboots and factory data resets.
When the fastboot flashing unlock command is sent, the device should prompt users to warn them that they might encounter problems with unofficial images. After the user acknowledges the warning, the device should perform a factory data reset to prevent unauthorized data access. The bootloader should reset the device even if it can't reformat it properly. Only after a reset can the persistent flag be set so that the device can be reflashed.
All RAM not already overwritten should be reset during the fastboot flashing unlock process. This measure prevents attacks that read leftover RAM contents from the previous boot. Similarly, unlocked devices should clear RAM at every boot (unless this creates an unacceptable delay), but should leave the region used for the kernel's ramoops.
Locking the bootloaderTo lock the bootloader and reset the device, run the fastboot flashing lock command on the device. Devices intended for retail should be shipped in the locked state (with get_unlock_ability returning 0) to ensure that attackers can't compromise the device by installing a new system or boot image.
Setting lock/unlock propertiesThe ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.
If the device supports flashing unlock, set ro.oem_unlock_supported to 1.
If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0.
If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or to 0 if unlocked. This variable must be set in bootconfig instead of in the kernel command line in Android 12.
For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.
I have the A32 5G (64Gb Int. Stg.) & it's the Tracfone Only version or SM-S326DL. After recently receiving word that Android 13 was awaiting us, I quickly allowed my device to receive this very kool OTA operating system update. I mention this, because a week earlier I received an email from my prepaid wireless provider instructing me in detail how to manually unlock my A32 5G handset. So, to be clear, Tracfone notified me in their email how to unlock my device, but whan
this happens to often, to write this off as an app-mishap xda...why?!
(pls. explain this to me, what is really going on)?
evnStevn said:
I have the A32 5G (64Gb Int. Stg.) & it's the Tracfone Only version or SM-S326DL. After recently receiving word that Android 13 was awaiting us, I quickly allowed my device to receive this very kool OTA operating system update. I mention this, because a week earlier I received an email from my prepaid wireless provider instructing me in detail how to manually unlock my A32 5G handset. So, to be clear, Tracfone notified me in their email how to unlock my device, but whan
this happens to often, to write this off as an app-mishap xda...why?!
(pls. explain this to me, what is really going on)?
Click to expand...
Click to collapse
I'm wondering too. Could you please pm me what you were trying to post?
I have a pixel 3a with a locked bootloader and a very barebones android os on it. It has basically no apps, the only ones shown are clock and settings, the settings app is very stripped down from a regular settings app too. For example, and maybe most importantly, there is no build number so I can't unlock the bootloader. I've tried pressing everything that sounds somewhat related, nothing enabled developer options. The recovery is very barebones as well, it only has reboot or power off options. So this phone is basically bricked.
Is there any hope? Any tools that can force unlock the bootloader? I did find some that claim they can but they seem very sketchy so idk if I want to try those.
Any other solutions are welcome as well of course
Android Flash Tool
flash.android.com
Here's the easiest option - back to stock. This site from google does all the work. As long as you can get to bootloader - you are good.
mmead1143 said:
Android Flash Tool
flash.android.com
Here's the easiest option - back to stock. This site from google does all the work. As long as you can get to bootloader - you are good.
Click to expand...
Click to collapse
That was the first thing I tried, but like I said, there's no way to unlock the bootloader (as far as I can tell) so it doesn't work
If you can get to the bootloader screen you can unlock it there via ADB and Fastboot:
Here's an article: https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-3a-0198625/
Try this command: fastboot flashing unlock
mmead1143 said:
If you can get to the bootloader screen you can unlock it there via ADB and Fastboot:
Here's an article: https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-3a-0198625/
Try this command: fastboot flashing unlock
Click to expand...
Click to collapse
That command only works if you allow the bootloader to be unlocked from the developer options, and like I said, I can't enable developer options on this phone
I'm having the same problem.
Did you somehow resolve it yet?
Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
smartasiankid said:
Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
Click to expand...
Click to collapse
Why is OEM Unlocking greyed out?
In theory, because you are already unlocked.
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
notmyrealhandle said:
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
Click to expand...
Click to collapse
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
smartasiankid said:
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
Click to expand...
Click to collapse
I'm not sure then.
If I was in your situation and I didn't mind wiping my data, I'd probably try booting into the bootloader and trying `fastboot flashing unlock` just to see what happens. If this command works, it will wipe your data so be sure about your backups. If it does unlock, you could try rebooting, check the OEM lock (I expect it will still be greyed out with an unlocked bootloader), and then relock and check again. Regardless if you can unlock inspite of the OEM toggle you shouldn't have much to worry about (at least until the next update).
If this doesn't work then I'd just wait a week or so. Alternatively, you could try the moto site, request your unlock key (again) and then wait a few days. It would be silly if this works, but maybe moto just needs to send a reminder to your device to enable the OEM unlocking toggle.
If none of this works, then I'd try posting to the moto official forums.
HTH
Never mind guys!! Just wait three maybe four days and it will automatically be toggle able again!! Thanks to all of those who tried to help me out!
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
smartasiankid said:
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
Click to expand...
Click to collapse
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
MrCamby said:
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
Click to expand...
Click to collapse
it is greyed out for me. i am on at&t network. it has been greyed out ever since android 11. not sure why that is happening.
Hey I am trying to root my sm-a037w, fully updated.
I remember having OEM unlocked it using the developer option which is now gone completely.
I'm using Magisk to patch the AP file
Then use ODIN to flash it and it stops at vbmeta with a error.
I'm new to this and have googled alot but now I'm really stuck.
So it fails, corrupt phone, I reflash oem AP and it restarts.
I have adb and fastboot ready to go,
Thank you.
Johnhek said:
Hey I am trying to root my sm-a037w, fully updated.
I remember having OEM unlocked it using the developer option which is now gone completely.
Click to expand...
Click to collapse
This is your problem, right here. If you closely read the Magisk installation instructions:
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Click to expand...
Click to collapse
If you can't see OEM Unlocking in Developer Options, and you see KG STATUS: PRENORMAL on the download mode screen, Vaultkeeper is still active and will reject custom images.
V0latyle said:
This is your problem, right here. If you closely read the Magisk installation instructions:
If you can't see OEM Unlocking in Developer Options, and you see KG STATUS: PRENORMAL on the download mode screen, Vaultkeeper is still active and will reject custom images.
Click to expand...
Click to collapse
Yea I've been trying for the last 48 hours and I can't figure it out how to get it back.
I did have developer mode active and had seen and allowed oem unlocking, not sure when I disappeared, I think it was the latest update.
Don't know how to proceed.
Tried setting the date back , disabling system update and software update, still no OEM Unlocking.
I have read those instructions many times, I have no prior experience rooting or modding android :/
Should I reflash original firmware?
Where do I go from here?
Johnhek said:
Yea I've been trying for the last 48 hours and I can't figure it out how to get it back.
I did have developer mode active and had seen and allowed oem unlocking, not sure when I disappeared, I think it was the latest update.
Don't know how to proceed.
Tried setting the date back , disabling system update and software update, still no OEM Unlocking.
I have read those instructions many times, I have no prior experience rooting or modding android :/
Should I reflash original firmware?
Where do I go from here?
Click to expand...
Click to collapse
Did you ever see the OEM Unlocking toggle after you unlocked the bootloader?
I assume you -did- unlock the bootloader, correct?
OEM Unlocking does not unlock the bootloader, it simply allows you to.
Reflashing the firmware might be a good idea. Keep in mind that Samsung is notorious for trying to disallow custom binaries on newer bootloaders. This is all speculation though, I'd need to see the error you got to have a better idea what the issue is.
flashing firmware is bad idea, this won't reset vaultkeeper. check RMM/KG state from download mode screen first. btw it's called odin mode (not fastboot mode)
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
aIecxs said:
flashing firmware is bad idea, this won't reset vaultkeeper. check RMM/KG state from download mode screen first. btw it's called odin mode (not fastboot mode)
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
Click to expand...
Click to collapse
Knox Guard has to be disabled by connecting to the Internet and checking for updates, and you have to be on stock firmware to do it.
Flashing the OEM firmware won't hurt anything, and is the only way to unlock KG.
Vaultkeeper is disabled by flashing the multidisabler in TWRP.
V0latyle said:
Did you ever see the OEM Unlocking toggle after you unlocked the bootloader?
I assume you -did- unlock the bootloader, correct?
OEM Unlocking does not unlock the bootloader, it simply allows you to.
Reflashing the firmware might be a good idea. Keep in mind that Samsung is notorious for trying to disallow custom binaries on newer bootloaders. This is all speculation though, I'd need to see the error you got to have a better idea what the issue is.
Click to expand...
Click to collapse
Hey thank you once again for your help.
To be clear this is how I recall the events .
1. I did enable OEM unlocking in developer options.
2. I updated the phone through the user interface.
3. OEM unlocking option dissapeared entirely after updating to android 12.
4. Downloaded XAC region firmware using SamFirm
5. Copied AP to my phone storage
6. Patched AP with Magisk, then transferred patched file to my PC.
7. Flashed BL, patched AP, CP and CSC(not home) using ODIN 3.14
ODIN said AUTH fail at Vbmeta on my PC and on the phone iirc.
8.Reflashed using stock AP to make the phone usable again.
At downloader screen I never saw hold volume up to unlock bootloader, only press up to continue. (after booting holding volume up+down+power)
Are KG and Vaultkeeper the same thing?
I guess my bootloader is locked and now OEM Unlocking option is gone.
This is the phone currently on latest firmware.
ODIN MODE reads:
FRP LOCK:ON
KG STATUS: CHECKING
MTK SECURE BOOT: ENABLE (0)
sec ctrl status (1)
SECURE DOWNLOAD: ENABLE
Baseband version A037WVLS 3 BVJ1 (bootloader version 3?)
Thanks for all the info, sorry for the messy post and not including all the info required.
I will provide you with the info you request, I do not know how to verify my KG status, it reads checking in ODIN MODE.
I am also not sure of how to identify the region firmware I need, the software version in my about phone says:
SAOMC_SM-A037W_OYV_BMC_12_0004
BMC/BMC/XAC/BMC
I have downloaded both XAC and BMC, both have worked for me.
Ohhh, it's a Mediatek device
Johnhek said:
At downloader screen I never saw hold volume up to unlock bootloader, only press up to continue. (after booting holding volume up+down+power)
Click to expand...
Click to collapse
The proper way to enter device unlock mode is thus:
Unplug any USB cables, power device off completely
Connect a USB cable to your PC, don't connect it to your phone yet
Hold both Volume buttons, do not press Power, and plug in the USB cable.
The screen should turn on with 3 options: Volume Up for download mode, long press Volume Up for device unlock mode, Volume Down for restart. Release both Volume buttons, then hold Volume Up.
Device should prompt you to confirm you want to unlock. If it prompts you to confirm you want to re-lock, stop! The bootloader is already unlocked.
Johnhek said:
Are KG and Vaultkeeper the same thing?
Click to expand...
Click to collapse
More or less...Vaultkeeper is the process that determines the Knox Guard status, which in turn is what actually allows custom binaries
Johnhek said:
I guess my bootloader is locked and now OEM Unlocking option is gone.
Click to expand...
Click to collapse
We'll see...
Johnhek said:
KG STATUS: CHECKING
Click to expand...
Click to collapse
This means that KG (Knox Guard)/Vaultkeeper hasn't yet verified your device is supposed to be unlocked.
Johnhek said:
MTK SECURE BOOT: ENABLE (0)
sec ctrl status (1)
SECURE DOWNLOAD: ENABLE
Click to expand...
Click to collapse
Is there nothing on there that says OEM LOCK?
Johnhek said:
Thanks for all the info, sorry for the messy post and not including all the info required.
I will provide you with the info you request, I do not know how to verify my KG status, it reads checking in ODIN MODE.
Click to expand...
Click to collapse
That's exactly how - it tells you in download/Odin mode.
Since it says CHECKING, there are two things we need to do:
Ensure the bootloader is indeed unlocked, using the steps I gave above
Once bootloader is confirmed to be unlocked, you need to boot into Android, connect to the Internet (use a WiFi network), go into Settings > System > System update and check for software updates. This also checks Vaultkeeper/KG.
After checking for software update, enable developer options (if not already enabled) and verify OEM Unlocking is present; it should be grayed out with the message "Bootloader is already unlocked".
The proper way to enter device unlock mode is thus:
Unplug any USB cables, power device off completely
Connect a USB cable to your PC, don't connect it to your phone yet
Hold both Volume buttons, do not press Power, and plug in the USB cable.
The screen should turn on with 3 options: Volume Up for download mode, long press Volume Up for device unlock mode, Volume Down for restart. Release both Volume buttons, then hold Volume Up.
Device should prompt you to confirm you want to unlock. If it prompts you to confirm you want to re-lock, stop! The bootloader is already unlocked.
Click to expand...
Click to collapse
I just tried this and there is no mention of unlock bootloader, same as before (volume up to continue) I click to continue and it reads;
PRODUCT NAME: SM-A037WCURRENT BINARY: SAMSUNG OFFICIALFRP LOCK: ONKG STATUS: CHECKING (I never created a samsung account on this phone if that means anything)MTK SECURE BOOT: ENABLE (0)sec ctrl statu (1)WARRANTY VOID: 0x0 (0x0)RP SWREV: B3 NS3 Kb3, Kr3, Vb3, Vbs3 S3SECURE DOWNLOAD: ENABLEMaybe I have to wait 7 days as I have read somewhere before I get the OEM Unlock option back?Thank you for your help
your device is FRP locked. you have to unlock with google account first.
as you updated stock ROM and downgrade is impossible, I doubt you will ever get OEM unlocking back. updating stock ROM was bad idea.
BOUNTY; fix for persistent RMM state lock after 7 days
I've had a situation where RMM state has always been prenormal and OEM unlock been absent for months on Oreo. After updating to Pie, OEM unlock appeared immediately on first boot, but RMM state prenormal was still there and flashing twrp give me...
forum.xda-developers.com
aIecxs said:
your device is FRP locked. you have to unlock with google account first.
as you updated stock ROM and downgrade is impossible, I doubt you will ever get OEM unlocking back. updating stock ROM was bad idea.
BOUNTY; fix for persistent RMM state lock after 7 days
I've had a situation where RMM state has always been prenormal and OEM unlock been absent for months on Oreo. After updating to Pie, OEM unlock appeared immediately on first boot, but RMM state prenormal was still there and flashing twrp give me...
forum.xda-developers.com
Click to expand...
Click to collapse
I am using the device normally and bought the phone new, using the google account i created for it , so i dont understand how this is possible.
Idk maybe FRP LOCK: ON disappears once you removed all bonded samsung and google accounts (maybe not caused by Google Factory Reset Protection but Samsung Reactivation Lock)?
V0latyle said:
I assume you -did- unlock the bootloader, correct?
OEM Unlocking does not unlock the bootloader, it simply allows you to.
Click to expand...
Click to collapse
No he didn't unfortunately. For bootloader unlocking and passing vaultkeeper one have to repeat that step twice, before and after unlocking/factory reset in odin/download mode.
https://forum.xda-developers.com/t/magisk-root-for-the-galaxy-s10-series.3918699
aIecxs said:
your device is FRP locked. you have to unlock with google account first.
as you updated stock ROM and downgrade is impossible, I doubt you will ever get OEM unlocking back. updating stock ROM was bad idea.
BOUNTY; fix for persistent RMM state lock after 7 days
I've had a situation where RMM state has always been prenormal and OEM unlock been absent for months on Oreo. After updating to Pie, OEM unlock appeared immediately on first boot, but RMM state prenormal was still there and flashing twrp give me...
forum.xda-developers.com
Click to expand...
Click to collapse
Upgrading firmware shouldn't cause problems with OEM Unlocking or unlocking the bootloader. You've stated this a couple of times but have yet to provide any source for your claim.
FRP Lock is simply on because he has a Google account logged in, and has absolutely nothing to do with OEM Unlocking.
@Johnhek you have already connected your device to WiFi, yes? If not, you need to do so, then go to Settings > System > Software update to trigger a check. Once done, go back to Developer Options to see if OEM Unlocking is visible.
If the bootloader wasn't unlockable, the OEM Unlocking toggle would never be present. The toggle controls the state of sys.get_unlock_ability which tells the bootloader it can be unlocked. There are a couple of props that control whether OEM Unlocking is available, ro.oem_unlock_supported which is supposed to be baked into the ROM at build time, and ro.oem_unlock_allowed which determines whether the toggle is available.
I will admit I'm not very familiar with MediaTek Samsung devices, but I don't see why the process would be any different. Still, here is a guide on using MTKClient
Let's just see if we can get the OEM Unlocking toggle back and make KG happy.
V0latyle said:
Upgrading firmware shouldn't cause problems with OEM Unlocking or unlocking the bootloader. You've stated this a couple of times but have yet to provide any source for your claim.
Click to expand...
Click to collapse
I don't know for SM-A037W but I know about people selling their Samsung phones on Android 10 for buying same model on Android 9 for reason.
Johnhek said:
I did have developer mode active and had seen and allowed oem unlocking, not sure when it disappeared, I think it was the latest update.
Click to expand...
Click to collapse
There is no official information but there are rumors that from certain security patch Samsung removed OEM unlocking forcefully (USA/Canada devices).
It's also my experience with SM-T555 region DBT still not unlockable as of today.
I think it's common sense when it comes to rooting/unlocking that older android versions are easier to root.
V0latyle said:
FRP Lock is simply on because he has a Google account logged in, and has absolutely nothing to do with OEM Unlocking.
Click to expand...
Click to collapse
For other brands it's not possible to flash anything when FRP Lock is on. Furthermore that state means device is actually FRP locked. Didn't know about Samsung FRP LOCK ON is only information about device is ready for FRP locking, sorry about that...
nevertheless FRP lock is contradictory to OEM unlock, both together is afaik not possible (except for Xiaomi).
btw flashing stock firmware won't unlock RMM/KG prenormal
we will know more about in 7 days...
V0latyle said:
Upgrading firmware shouldn't cause problems with OEM Unlocking or unlocking the bootloader. You've stated this a couple of times but have yet to provide any source for your claim.
FRP Lock is simply on because he has a Google account logged in, and has absolutely nothing to do with OEM Unlocking.
@Johnhek you have already connected your device to WiFi, yes? If not, you need to do so, then go to Settings > System > Software update to trigger a check. Once done, go back to Developer Options to see if OEM Unlocking is visible.
If the bootloader wasn't unlockable, the OEM Unlocking toggle would never be present. The toggle controls the state of sys.get_unlock_ability which tells the bootloader it can be unlocked. There are a couple of props that control whether OEM Unlocking is available, ro.oem_unlock_supported which is supposed to be baked into the ROM at build time, and ro.oem_unlock_allowed which determines whether the toggle is available.
I will admit I'm not very familiar with MediaTek Samsung devices, but I don't see why the process would be any different. Still, here is a guide on using MTKClient
Let's just see if we can get the OEM Unlocking toggle back and make KG happy.
Click to expand...
Click to collapse
@V0latyle hey I have tried those suggestions still no luck. Thank you and happy holidays, I will try waiting 7 days ND let everyone know
aIecxs said:
I don't know for SM-A037W but I know about people selling their Samsung phones on Android 10 for buying same model on Android 9 for reason.
There is no official information but there are rumors that from certain security patch Samsung removed OEM unlocking forcefully (USA/Canada devices).
It's also my experience with SM-T555 region DBT still not unlockable as of today.
I think it's common sense when it comes to rooting/unlocking that older android versions are easier to root.
For other brands it's not possible to flash anything when FRP Lock is on. Furthermore that state means device is actually FRP locked. Didn't know about Samsung FRP LOCK ON is only information about device is ready for FRP locking, sorry about that...
nevertheless FRP lock is contradictory to OEM unlock, both together is afaik not possible (except for Xiaomi).
btw flashing stock firmware won't unlock RMM/KG prenormal
we will know more about in 7 days...
Click to expand...
Click to collapse
@Alecxs Yea I probably should have left it android 11.
V0latyle said:
I will admit I'm not very familiar with MediaTek Samsung devices, but I don't see why the process would be any different. Still, here is a guide on using MTKClient
Let's just see if we can get the OEM Unlocking toggle back and make KG happy
Click to expand...
Click to collapse
I will read the link tonight , much appreciated
Johnhek said:
@V0latyle hey I have tried those suggestions still no luck. Thank you and happy holidays, I will try waiting 7 days ND let everyone know
Click to expand...
Click to collapse
You can also try disconnecting from the Internet (take out your SIM as well) and set the date back by at least a week. Or you can set it forward.
Johnhek said:
@Alecxs Yea I probably should have left it android 11.
Click to expand...
Click to collapse
It shouldn't matter, honestly, although I generally prefer to do one thing at a time - unlock the bootloader, THEN update.
I have a feeling that the MediaTek aspect of things may be the issue here, although I have no way of knowing.
Johnhek said:
I will read the link tonight , much appreciated
Click to expand...
Click to collapse
Hopefully it will be of some help to you. It's not beginner friendly - you have to install Python and compile it, but if you can get MTKclient working, you can see if it's what you need.
V0latyle said:
I have a feeling that the MediaTek aspect of things may be the issue here, although I have no way of knowing.
Hopefully it will be of some help to you. It's not beginner friendly - you have to install Python and compile it, but if you can get MTKclient working, you can see if it's what you need.
Click to expand...
Click to collapse
Reading it now, I think I can handle it, the instructions seem clear.
As for the date trick.
I tried it while connected to wifi, I dont even have a sim card in this phone lol.
Tried setting to last month, havent tried forward in time though, will try disconnected as well.
The mediatek thing seems promising, I think the sec ctrl status (1) in the download screen is MTK related...
I will let you know.
I have read in one of the linked threads that SIM card plays a role here. I recommend to enable mobile data for 7 days, although there is less hope.
from what I have learned from elliwigy one can't cheat samsung bootloader not even with mtkclient. there is however paid service for devices with DID token on download screen (afaik Qualcomm only). but try mtkclient first it's a good exercise and maybe you're lucky and it works.
aIecxs said:
I have read in one of the linked threads that SIM card plays a role here. I recommend to enable mobile data for 7 days, although there is less hope.
from what I have learned from elliwigy one can't cheat samsung bootloader not even with mtkclient. there is however paid service for devices with DID token on download screen (afaik Qualcomm only). but try mtkclient first it's a good exercise and maybe you're lucky and it works.
Click to expand...
Click to collapse
I tried mtkcient but I kept getting unauthorized handshake when trying to connect phone :/
Followed instructions as per link but I encounter one error in the process:
Get latest UsbDk 64-Bit
Install normal MTK Serial Port driver (or use default Windows COM Port one, make sure no exclamation is seen)
Get usbdk installer (.msi) from here and install it
Test on device connect using "UsbDkController -n" if you see a device with 0x0E8D 0x0003
Works fine under Windows 10 and 11
I'm on windows 11 and when I put the command "UsbDkController -n" in terminal it doesn't recognize it.
I installed the usbdk drivers from git hub, a .msi fil, from the guide.
Another problem is I don't know how to set windows default COM Port one.