yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Johnhek:
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.
[General Questions and Answers] V0latyle:
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.
[General Questions and Answers] Johnhek:
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?
[General Questions and Answers] V0latyle:
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.
[General Questions and Answers] alecxs:
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)

https://xdaforums.com/t/guide-17-06...all-twrp-on-exynos-samsung-after-2018.3747535
[General Questions and Answers] V0latyle:
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.
[General Questions and Answers] Johnhek:
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.
[General Questions and Answers] V0latyle:
Ohhh, it's a Mediatek device

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.

More or less...Vaultkeeper is the process that determines the Knox Guard status, which in turn is what actually allows custom binaries

We'll see...

This means that KG (Knox Guard)/Vaultkeeper hasn't yet verified your device is supposed to be unlocked.

Is there nothing on there that says OEM LOCK?

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".
[General Questions and Answers] Johnhek:
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-A037W​

CURRENT BINARY: SAMSUNG OFFICIAL​

FRP LOCK: ON​

KG 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 S3​

SECURE DOWNLOAD: ENABLE​

​

​

Maybe I have to wait 7 days as I have read somewhere before I get the OEM Unlock option back?​

​

Thank you for your help :)​
[General Questions and Answers] alecxs:
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.

https://xdaforums.com/t/bounty-fix-for-persistent-rmm-state-lock-after-7-days.3886716
[General Questions and Answers] Johnhek:
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.
[General Questions and Answers] alecxs:
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)?

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://xdaforums.com/t/magisk-root-for-the-galaxy-s10-series.3918699
[General Questions and Answers] V0latyle:
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.
[General Questions and Answers] alecxs:
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...
[General Questions and Answers] Johnhek:
@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

@Alecxs Yea I probably should have left it android 11.
[General Questions and Answers] Johnhek:
I will read the link tonight , much appreciated :)
[General Questions and Answers] V0latyle:
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.

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.

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.
[General Questions and Answers] Johnhek:
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.
[General Questions and Answers] alecxs:
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.
[General Questions and Answers] Johnhek:
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 :D

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.
[General Questions and Answers] alecxs:
device must powered off completely and unplugged for handshake
[General Questions and Answers] Johnhek:
I will try again, pretty sure I did that :/

Should I revoke previously connected devices?

Thank you for helping out :)
[General Questions and Answers] Johnhek:
UPDATE:

mtk client error running command " python mtk da seccfg unlock " and other commands

DeviceClass - [LIB]: Couldn't get device configuration.

Still no oem unlocking option...

I've tried holding volume up, volume down, volume up + down, volume up + down + power, volume up + power, volume down + power.

Nothing works, volume down + up brings me to Odin mode...
[General Questions and Answers] Johnhek:
Tried that,nothing works.

In the mtkclient loader/preloader files I see the 6765 is missing from the repertoire...

For now I'm putting this aside, unless someone comes in with a revelation lol...

I've put many hours in!
[General Questions and Answers] alecxs:
do you see VCOM preloader drivers installed in windows device manager for a second when plugging in powered off phone?

it should be possible to unlock... at least @r1pp3d2 claimed that, and some other guy was able to dump ROM too.

maybe bootrom mode requires test point (although he didn't)?
[General Questions and Answers] Johnhek:
Hello :)

Yes I have installed them manually in advanced startup (win 11) to allow unsigned drivers install, also ran install package of signed drivers, USB mtk, preloder mtk and some other drivers.

Will read Test point link, I see that "testpoint" mention in mtk gui but I don't know how.

I am new to all this, I am possibly screwing something up.

I see VCOM preloader even with the phone unplugged, its always in my device manager.

@Alecxs

When I plug the phone in, I see:

Portable Devices>MTP

Android Device>SAMSUNG Android Device ADB Interface

Still no luck getting mtk client to connect to the phone....
[General Questions and Answers] Johnhek:
@Alecxs @V0latyle

Hey guys I was thinking my problem connecting the mtk client is UsbDk driver install... I am on windows 11.

I followed the guide from github bkerler/mtkclient

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 :D

When I run the linked file nothing happens, the windows opens and closes super fast.

When I run the "UsbDkController -n" command in CLI it is unrecognized?

I am thinking of trying other option at beginning of the guide...

Use Re LiveDVD (everything ready to go, based on Ubuntu):​

User: user, Password:user (based on Ubuntu 22.04 LTS)

Live DVD V4

Happy Holidays:)
[General Questions and Answers] V0latyle:
I do not know how to help at this point. I see you already asked in the MTKclient thread. Hopefully they are able to help you.
[General Questions and Answers] Johnhek:
Thank you for you time and information shared.

I haven't rooted yet but learned a lot :)
[General Questions and Answers] alecxs:
that's how it looks like on windows 7 device manager (last second)
[General Questions and Answers] Johnhek:
Yep, although on mine It appears grayed out or "translucent"

I am going to try unintalling all drivers and reinstalling only the mtk USB vcom ones.

Still not certain if m UsbDk drivers are installed correctly though.

Going to try using Samsung remote assists see if they can make it happen🤔

Give LIVE DVD 4 setup if all else fails.

I'll be back.
[General Questions and Answers] alecxs:
I have good experience with linux, kernel will handle drivers itself no need to worry about connection issues (can't speak for Live DVD v4)
[General Questions and Answers] Johnhek:
Live DVD 4 worked, somewhat.

I waited 7 days that didnt work, but my KG STATUS went from checking to completed.

I then got the live DVD 4 and ran the command to unlock bootloader.

Phone reset itself, it gives me a dm verity error message when it restarts.

Phone is corrupted etc press power to start device within 5 seconds or it powers off.

So the phone still works normally. But now KG status changed back and still no oem unlock.

Not sure what to do next.
[General Questions and Answers] orang_the_fruit:
Were you ever able to unlock your bootloader? I have a galaxy a03s and I tried using mtkclient but I wasnt able to get it to work. I used the live dvd and while it completed successfully, when booting to download mode KG status says checking and my bootloader is still locked. I also have never seen oem unlocking in my developer settings. Model is SM-A037W (canada)!

Thanks in advance
[Moto G General] Richiie89:
Hello i have a Motorola Moto G31 (W) XT273-3

OEM Locked - Android 11

FRP Locked

AP fastboot Flash Mode (Secure)

BL: MBM-2.1-Cofud_g-3e4f6a263-22075

Baseband: <not found>

Product/Variant: Cofud XT2173-3 64GB PVT

Serial Number: ZY22DXWR2G

CPU: MT6769V/CZ

eMMC: 64GB MICRON G1J9R8 RV=08 PV=00

FV=0000000000000204

DRAM = 4GB MICRON LP2 DIE=4GB M5=FF M6=06 M7=00 M8=18

CONSOLE=[NULL]: null

TOOLS MODE CONFIG: DISABLED

BATTERY OK

TRANSFER MODE: USB CONNECTED

Access - Summary of within RECOVERY MODE: NO COMMAND (DROID IMAGE with Error Sign) - can though with Vol up get into inside the recovery mode.

IMEI1: 3564200662778950

IMEI2: 3564200662778968

Within normal operational mode, it can access to wifi

the wifi address is 192.168.1.75

MAC Address to WI-FI card is 4a: 5e: 8f: 58: da: oc

FRP: 0X2F08000 - 0X100000

Pattern: 0X30B0000000 - 0XC0000000

i read another article https://firmwarespro.com/frp/motorola-moto-g31-detail where they describe a potential method to bypass FRP (Without having EMAIL and password information) i have not been able to sucess with that yet though, that's why i ask professionals here for advice and guidance how / if i can write the EEeProm chipset or someway reinstall custom ROM to the phone internal storage - and from that point bypass / get rid of previous stored Google FRP data.

Thanks in advice

Best regards

Richiie
[Moto G General] Richiie89:
View attachment 5790615
[Moto G General] Richiie89:
View attachment 5790617
[Moto G General] Richiie89:
https://mirrors.lolinet.com/firmware/motorola/cofud/official/ i found this foreign archive including ROM files for various phones. Could this perhaps be something that can be used in order to succeed properly?

https://custom-rom.org/download-custom-rom-for-moto-g31-android-12/ found this aswell but i don't know it's integrity if its a trusted source?

Here below is the link i mentioned previously found the unofficial method to bypass FRP.

Motorola Moto G31 FRP Bypass Android 11 Google Account Unlock Without PC & APK Free

In this post, I share the latest step-by-step tutorial to Motorola Moto G31 FRP Bypass Android 11 Google Account Unlock Without PC & APK Free

www.bypassfrpfiles.com

best regards
[Moto G General] overtube:
Hello every one, I have same phone, maybe some make custom system for this device, or pls how I can do it myself for share, maybe some linageos avaliable for this device?

pls some help me about assembling custom of for this phone how I can do it?

Also I have all needed for compile, but I cant know how make custom firmware from sources, pls help some one
[Moto G General] Richiie89:
Anybody got anything, any information or advice what to do or how to proceed?

Best regards
[Moto G General] veseihaty:
I would buy this phone if it had custom rom and unlockable bootloader.
[Moto G General] Richiie89:
I wish there would be more guides and how-to's how to proceed / reinstall the bootloader for this phone and make it work properly again.
[Moto G General] xdauser1620:
If motorola not publishing source code then i don't think custom roms will be released for this phone. Maybe some ported GSI exist for it and that will be the end of it. Mediatek not really custom rom friendly SOC or hardware.
[Moto G General] PaulAtradies988:
You can get the boot.img file and the rest of the stock rom for this phone using the motorola smart rescue and assistant tool which I used to root my phone using Magisk. Motorola also let you unlock to boot loader. This device has a a/b partition layout and uses vendor_boot-as-recovery instead of the normal boot-as-recovery. Also since the phone was released it has revived an update to android 12. It uses a Mediatek chip and

fastboot boot

doesn't work
[Moto G General] xdauser1620:
Usually you use that command to boot TWRP recovery (which i think not exist for G31) or magisk patched img.
[Galaxy S 4 Q&A, Help & Troubleshooting] tuxayo:
Hi :)

I have a i9505 that has a non repairable vol up button. The contact on the motherboard is broken. One repair shop told me it was done for. Another tried something but that didn't work out in the end. So repairing the button isn't an option.

I had to swap back and forth to another ROM and I might have restored the wrong image to the system partition (or maybe I should have also restored the boot one). So anyway, it stays frozen on boot screen for hours. It doesn't go the boot animation.

Vol down allows me to go to the prompt for download mode. But I can't accept it to actually go in download mode. And the device isn't reachable via ADB on this step.

Is there still some software way to make it boot in recovery? Or hardware way, like contacts somewhere else on the board that could directly or indirectly help.

I didn't realized how precarious the situation was without a vol up button 😱
[Galaxy S 4 Q&A, Help & Troubleshooting] ze7zez:
Can't you flash the system again via Odin/Heimdall or Kies?
[Galaxy S 4 Q&A, Help & Troubleshooting] tuxayo:
Is that possible without enabling download mode? I can get the prompt for download mode but can't confirm it. Because it's done via vol up.

And `heimdall detect` doesn't see the device.
[Galaxy S 4 Q&A, Help & Troubleshooting] tuxayo:
I just learned about USB jig dongles. If I buy or make one (maybe at a repair shop they have one) I could be able to save the situation!

However, I can't find if it's possible to flash a LineageOS zip with Heimdall. I only found mentions of the stock ROM. Which doesn't have the advanced reboot menu I think. (to go back to recovery)
[Galaxy S 4 Q&A, Help & Troubleshooting] ze7zez:
It seems that the opinion is true. IMHO, it is not worth it to buy JTag and specialized software to support it. The cheapest thing would be to buy a used i9505 with a working motherboard (or a used whole i9505) at a local auction and swap the MoBo.
[Galaxy S 4 Q&A, Help & Troubleshooting] nintendobuster420:
you can flash stock and then root to get the advanced boot menu, then flash your rom through recovery. USB jigs are really cheap anyway
[Tilt, TyTN II, MDA Vario III General] fifa_0304:
Hello all, just found a more specific forum for Kaiser so I thought it is worth posting this here again....

Some posts might have already discussed this, but I am not very good with gadgets, and I have a specific problem which I need help with, so I thought it is better to start a new thread.

So this is my story. (by the way, my phone is HTC TyTn II)

I unlocked my phone in other country and apparently the software on my phone is now for HTC touch dual (I think - because everytime I switched it on, it says Touch Dual).

I used to be able to use bluetooth before and now,I can't.

Then, I was trying to download a gps sofware (or whatever you call it) on my phone - it is called miomap. I can view the map but it does not detect where I am like a normal GPS/tomtom would.

My questions are:

(and I am sorry if this questions sounds too dumb. I try to read and get the answers from other thread and websites, but I am too dumb in this stuff to take them in)

1. Do i need GPS receiver to be able to use it as GPS system? As at the back of it, there is word saying GPs, andd looks like I can connect it to something.

2. If I don't need one, what should I do?

3. Do you reckon I should download the original software for TYtn II?

Please help me, and thanks for your help in advance.