yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A12] LAST_krypton:
@R0GUEEE

Here I will share these links and documents that could help.

[CLOSED][Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices

Important notice: If you are already updated post February 2021, do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates...

xdaforums.com

How to unlock Unisoc (SPD) bootloader using Identifier Token

This tutorial will explain how to unlock a Unisoc / Spreadtrum (SPD) Android device's bootloader using its Identifier Token. This guide is ideal for those who had tried the generic fastboot bootloader

forum.hovatek.com

Where is the "download mode" code stored?

At least Samsung Galaxy series devices support download mode(also known as Odin mode or flash mode) which usually can be accessed by pressing down specific buttons while powering on the phone. Is t...

android.stackexchange.com

How I can downgrade from U3 to U1 "oreo to nougat"

I want to downgrade my phone from Oreo to Nougat My phone is Samsung J730F. But the problem is that Samsung locked the boot-louder. Can I go back by flashing the phone combination ROM then flash my

android.stackexchange.com

http://newandroidbook.com/21-Security.pdf?aboot

Reverse Engineering Android's Aboot

How to use MTK Bypass to backup or flash secure boot MTK

This is a step-by-step guide showing how to flash or backup a Mediatek (MTK) secure boot device without using a custom download agent (DA). This tool disables the SLA / DAA bootrom protection A little

forum.hovatek.com

How to use an MTK Secure Boot Download Agent (DA) file

This tutorial will explain how to use that DA file you just downloaded for your Mediatek (MTK) device with Secure Boot. You'll need the DA file to backup, flash, bypass Factory Reset Protection (FRP)

forum.hovatek.com
[Samsung Galaxy A12] R0GUEEE:
Yeah, I've pretty much gone around and around in circles with this. The thing that makes it curious though is after running adb shell getprop and looking through the build, I noticed most of the properties relating to oem unlocking were actually set to allow, the one outlier was sys.oem_unlock_allowed. Which kinda pushes me back towards the KG/RMM. Athough, I'm not sure if that's because I have the unlocked U1 FW flashed (it's actually an a125u), or if its the same on both. Either way, running an MTK exploit to unlock the bootloader (which I've done) doesn't actually contribute anything to whether or not OEM Unlocking is visible in dev settings, which is the primary prereq for unlocking the bootloader.

I did consider trying to update the sys.oem within build.prop in /system, but obviously without a root it's impossible, which lead me to possibly unpacking the stock FW super.img and trying to pre-edit the build within so I could re-pack and flash using the MTK Bypass exploit, but those necessary oem properties aren't even listed on either of the build files I did manage to find.

So as of now I've got one more test I'm going to try before I give up. All things considered, the most likely issue is the KG/RMM state, so I'm going to test a few different methods to try and circumnavigate those and possibly unlock the missing OEM Unlock option.

I can at least say that it's likely not an issue of manufacturer locked loaders, considering that's primarily a snapdragon issue, whereas the A12 runs on MediaTek, so fingers crossed.
[Samsung Galaxy A12] LAST_krypton:
If you were able to see the settings are enabled through ADB that is the same as it showing in settings. KG/RMM state could also be the factor of why it isn't beeing shown as of what you have said. Samsung has came a long way with these dumb knox securities which just makes everything worse, you might be able to find a clue for this within their KNOX documents ( I sent a link in a post above). Maybe you can find a profesional, a person that has worked for samsung and can maybe help you with this. It just gets too complicated at one point. If you have telegram or something were we can talk further about this it would be nice because some exploits and stuff if you mention can violate xda rules... So I don't know what else to tell you, I never really was in a situation where I was required to do these type of stuff, only if I had to because of some problems I had. Maybe you can find answers for all of this on some really old forums where people use to do everything to brake apart samsungs and mediateks security locks but still dout it.

For now, hope you learned something and dm me if you want to chat on telegram or etc about this. Don't think something is impossible because you can't find a answer for it, everything is possible.
[Samsung Galaxy A12] R0GUEEE:
Well after trial and error, I finally got it. I had to hunt down an Android 10 firmware with a matching binary to allow a downgrade, and after a couple of tries, using the auto-date/time method, OEM unlocking finally decided to show itself in dev settings. Specifically, I used this FW, flashed with Odin https://samfw.com/firmware/SM-A125U/USC/A125USQS2AUF3
[Samsung Galaxy A12] LAST_krypton:
Well, you couldev done that allready out of the start. But even do you got OEM_UNLOCKING shown doesn't really mean anything on U model, unless you have exploits and methods for unlocking PBL. Which as said wasn't very sucessful at all for you. I recomend to you that you check our DMs. mtkclient has some bugs which are on the way to be fixed.
[Samsung Galaxy A12] Warlockguitarman:
I've been working with mtkclient for months, before it even unlocked bootloaders, I was the first to unlock the stylo 6 bootloader and I had a bit of a hand in working out some of the bugs with the tool, I'm doing a full backup of the A125U model right now with mtkclient and after it's done I plan to try the unlock without having oem unlock option in dev options, but first I'll check to see what binary version I'm on, not sure if it's on android 10 or 11 right now. But I will sheet the backup
[Samsung Galaxy A12] Warlockguitarman:
I finally finished my tutorial for the stylo 6 bootloader unlock and root so now I'm working with the A125U. I'm on 2nd binary and i think i got the bootloader unlocked, but if I flash the patched boot.img it won't boot. I'm gonna try a few ideas i have, so far no luck but I'm not gonna give up, I may crossflash, but I'm trying to find the easiest way to do this.
[Samsung Galaxy A12] Warlockguitarman:
GitHub - MTK-bypass/bypass_utility

Contribute to MTK-bypass/bypass_utility development by creating an account on GitHub.

github.com

I'm glad to see Hovatek being suggested, i worked with them on my stylo 6 project, they even gave me a shout out if you look in the mtkclient instruction for the K51.
[Samsung Galaxy A12] Warlockguitarman:
Here's the scatter file for the A125U model

MT6765_A12_scatter.txt

drive.google.com
[Samsung Galaxy A12] Fly WhiteGuy16:
I own a a125u with FW A125USQU2BUI3. Would I be able to use this method to make oem unlock appear and then root? If so could you please assist me and help with the steps? I've been attempting to root this thing for a week and my girl friend is starting to hate me because I'm obsessed and paymore attention to this than her lol
[Samsung Galaxy A12] rockypiccolosr:
Still looking for testers? I have an a125u hit me up if you are still looking
[Samsung Galaxy A12] rockypiccolosr:
Ok so just fill me in exactly what your gonna do and what I need to do and I'm down for that
[Samsung Galaxy A12] LAST_krypton:
Because a method was found thread can be officially closed. more information in the discord server...

Guide by marioz17

Unlock bootloader and root A125U u3

Requirements: -Tested working on firmware A125USQS3BVA2 -A MTK bootloader unlocking tool, tested working with UnlockTool -This is for A125U on binary 3 ONLY Special thanks to @Boster27 for translate guide and test method Steps: 1- Boot into...

xdaforums.com

Also again, thanks to everyone that cooperated in this project. Even tho the method by marioz17 is samsungs fault which we shouldev checked in the beginning.
[General Topics] sarthak.whenever:
I wanted to install TWRP custom recovery in my SM-A205F. I tried flashing it using odin but each time I flash, it gives error

error validating footer auto-opening download mode while booting. I tried that almost 7 times, didnt work.

I actually wanted to install pixel experience custom rom.

If it is possible to install without twrp, please suggest a way, else please make it such that twrp installation in my phone would be possible.

Details:

Flashed using: Odin

Flashed Twrp file: twrp-3.5.2_9-0-a20.img.tar

Flashed no. of times: 7

Baseband no.: A205FDDUACUF3

Build no.: RPA[xxxxxxxx].[xxx].A205FXXUACUF3
[General Topics] Oswald Boelcke:
@sarthak.whenever I don't have this device i.e. I can't help but did you already check the device forum?

Samsung Galaxy A20

xdaforums.com
[Android Auto General] d3viou5:
I've read on some forums that Android Auto does not support swiping and multitouch. I have Android Auto working on my headunit with a carplay / AA dongle, and it will only let me interact with it by using the arrow buttons at the top and bottom of the scroll bars, as well as using the + / - to interact with maps. Basicaly prodding the screen is the only way to do anything. Any sort of more "advanced" gesture like a swipe doesn't work.

Is this regular behaviour for Android Auto? I had a hire car last month that had AA and I could swipe and pinch to zoom on maps without any issue.

I'm wondering at the moment if this is the carplay dongle and whether headunit reloaded would offer a better experience.

Thanks for your advice.
[Android Auto General] d3viou5:
So, to answer my own question and for anyone that may have similar issues, head unit reloaded on my unknown Chinese branded android car stereo works as expected. In fact it works great. Multitouch, swipe etc, all working.

Must be my carplay dongle that doesn't work correctly with android auto, though it was good for carplay.
[Touch Dual, MDA Touch Plus General] rikc34:
i am tired of searching through a nike thread for neon programs and such. would be appreciate if there was a neon thread but for now this will work.
[Touch Dual, MDA Touch Plus General] ajb303:
Many have asked, there has been a poll also. I dont know why they dont add one, possibly because its still a relatively newer phone, Neon that is. I have the Neon 300
[Touch Dual, MDA Touch Plus General] rikc34:
i just got my neon 300 and already have a bunch of **** on it, i used to have the juno, and i liked that i could go to one place for everything but this is annoying
[Touch Dual, MDA Touch Plus General] skodazek:
rikc, how did you unlock your neon300?

I have a CDMA neon400 and have yet to find a way to unlock it, since its CDMA it doesn't use a sim card.

Would the same method you used on your neon300 work for my neon400 likely? if so, I would love to know how you did it.
[Touch Dual, MDA Touch Plus General] ajb303:
Yes, same way with the 300. http://xdaforums.com/showthread.php?p=2110312 Follow the same precedure :)
[Touch Dual, MDA Touch Plus General] haensgn:
bump

I have bumped about three our four of these threads now.

Welcome btw, robot:rolleyes:

I honestly doubt it is because of the newness of the phone. A lot newer phones have their own thread b4 they are released.

the only thing we really need are roms. all other programs work for the nike as well as all models of neon.

ps robot watch your language. gratuitous curse words accomplish nothing
[Touch Dual, MDA Touch Plus General] ajb303:
Ah, yes. I would love some newer roms. I wish i knew how to cook, havent really looked into it. I will when i get a chance. I want to look into seeing the TF3D on the Neon.
[Touch Dual, MDA Touch Plus General] big papa rich:
TF3D

Yeah, touch flo would be nice. I've been looking into cooking, but so far can't find the right Kitchen or other junk.

I know that as soon as I start playing with cooking rom's, I will be hooked.
[Touch Dual, MDA Touch Plus General] ajb303:
Right on :D Good to see someone who wants to :)
[Touch Dual, MDA Touch Plus General] Romantok:
Touch Dual NEON

I have also a new CDMA neon400 from Telus which has a 528 MHz like the diamond but it has the memory of the Touch Vogue and it seems that there is many different model on the market (different speed and some have 2 cameras).

This thread started in oct 2008 and ended in jan 2009, I think that there should be more thread coming (I hope) and that some new ROM will be made for it.

I had a Touch Vogue before, but it was stolen and I bought this Touch Dual NEON400 to replace it because it was on sales. On sales for what reason I don't know, is it because it is buggy? They told me that the Diamond was so popular that they were clearing this one.

I anyone knows about something coming for the Dual Neon400 please advice me. I hate that cube and it went so good before with Manila2D and the new ROM I had for the Touch Vogue... but it is gone now.

Thanks...
[Touch Dual, MDA Touch Plus General] hellsmasher:
I've been wasting a lot of time trying to find out something about all this stuff.. The bottleneck Is definitely there, people who got a CDMA Neon 400 are very little compared to it's cousins. To write roms and build sspl is pretty much hard stuff, and people who have the knowledge to do this stuff are smart enough not to buy that Phone...

It has the same cpu speed as the diamond, but not as much ram (or Internal mem? wtever)

It doesn't have two cams... unlike any other versions

It comes (from telus) With the same acessories than the Diamond

What's that? Offered with a 0$ Promotion for 3 ys contract!

I don't really know what they tried to do with that kind of TOuch Dual version...

But I was looking for ways to enable wifi on it but I think I'll forget that.... If they saved on production cost over a front camera, they probably would have saved on an WIfi antenna also... Got the phone since a month and did everything legit so far... There's NOTHING ''Funny'' you can do with that model yet....

Fack on va etre pogné avec un osti de phone de marde pendant 3 ans a cause dun écoulement de stock d'un modele qui lui manque une couille...

Anyone sells miracles?
[Touch Dual, MDA Touch Plus General] Romantok:
Touch Dual de Telus
[Touch Dual, MDA Touch Plus General] tootall2:
we really need a seperate classifiaction for Neon

There seem to be more and more Neons around, mine is a gsm Neon 400 with a Qualcomm MSM7201-400mhz. The Nike phone and the Neon phone are only the same in initial looks, whats inside is totally different. It is about time a seperate heading was available for Neons. There is enough trouble just dealing with the many different Neon models.
[Touch Dual, MDA Touch Plus General] cbstryker:
Why would you say that? That thread has MANY people stating that the procedure does NOT work with the Neon 400!

Edit: Never mind, I saw your post was on October, but I read it as 2009 instead of 2008, which was BEFORE the majority of the posts on the other thread.
[Introductions] kamaraMike:
Hello, I am Michael Kamara. I think it is suffice to say that problems with my phone drew me to xda (phone problems still going on by the way). I am also a student 3.1, Computer science. I look forward to keeping up with emerging technologies now that I am here.

From Kenya, with love.
[Introductions] orb3000:
Hello Michael welcome to XDA!
[Samsung Galaxy S9  Questions & Answers] gluons:
I have a SM-G965U. There is no "OEM unlock" after seven days, and modified Odin always fails to flash.

Is it possible to root this device?
[Samsung Galaxy S9  Questions & Answers] lewmur:
If you have the US version of the S9, you can't unlock the bootloader, so you can't root or install custom ROM. As I found out the hard way.
[Redmi 9 / Poco M2 Questions & Answers] juuly:
Idk if im breaking the rules here, but i've been wondering where is redmi 10 forums ? The phone launched 2 months ago.

I chose this forum cus its the closest one to redmi 10

P.S : I don't own redmi 10 but i do own redmi 9, im planning on buying it .
[Google Pixel 6 Pro] roirraW "edor" ehT:
Disabling Verity and Verification isn't required except for use with some custom kernels, but just rooting those custom kernels with the latest Magisk Stable v24.1 or higher should make them not require disabled Verity and Verification anymore.

A reminder that disabling Verity and Verification, at least if you've never disabled them before, will cause you to need to factory reset the device otherwise there will be corruption.

The usefulness of having Verity and Verification enabled

(now that it's not needed for root but IS still required for some custom kernels):
[Google Pixel 6 Pro] roirraW "edor" ehT:
Regarding P6P 5G model numbers and capabilities

:

There are three hardware versions:

G8VOU (AU, US); also listed as G8V0U - zero instead of "oh" on some sites, Google shows the former, G8VOU) - has mmWave 5G support

GF5KQ (JP) - has mmWave 5G support

GLUOG (CA, DE, FR, GB, IE, TW) - no mmWave 5G support

For instance, my factory unlocked direct from Google in the United States Pixel 6 Pro 512 GB is a G8VOU. As far as I know, all other variations in each individual phone are controlled by software (which firmware is loaded) and over the internet (which IMEIs are Carrier Unlocked or not, and OEM Unlockable or not).

Check carriers, their 5G networks & their 5G roaming support for Pixel phones. Make sure and choose your country from the drop-down to see the list of carriers beneath.

There's also the section above that Learn which Pixel phones can work with which kinds of 5G.
[Google Pixel 6 Pro] roirraW "edor" ehT:
My personal advice for how to get your device back up and running like you had it previously after a factory reset:

I use Nova Launcher Prime, so I do backups anytime I change my home screen or app drawer/tabs setup, so widgets and app icons and other Nova-specific configurations are easier to restore.

Go to Android Settings and use Settings' search box for Backup. Make sure that your Google account is set up to backup your apps (and app data for the apps that developers have configured to use Google's Backup API). Make sure things are backed up. Note, this doesn't backup the apps themselves, only the list of apps, so only applies to apps installed from the Play Store. As I said in parentheses, developers have to choose to integrate Google's Backup API into their app, and those apps only will get their app data backed up into Google's cloud.

If you're rooted also, then you could use something like Swift Backup to backup to the cloud. I do so, although I still restore as much as possible through Google's backup, and I only restore through Swift on a case-by-case basis, as needed when I discover an app that's tough to set back up doesn't have it's data restored by Google.

If you've used Google Photos to backup your photos to Google's cloud, then hit the button in Google Photos to free up space. This will automatically and only delete your local copies of photos and videos that it's already backed up.

Once that ^ is done, look at your internal storage with your favorite File Manger and see if there's anything left that you want to back up manually, since a factory reset will wipe everything. Copy them to your computer or a flash drive.

When you're just starting the out of the box setup after the reset, when it asks you if you want to use a cable to restore things from an old phone, choose No, and that will lead you to Google's cloud backup where you can choose to restore everything, or you can select what you want to restore.

I think you can figure out the rest.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Reserved.
[Google Pixel 6 Pro] dj24:
If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.
[Google Pixel 6 Pro] roirraW "edor" ehT:
This one's kinda long for what it is, and this is for the Pixel 1, but it should be similar for the Pixel 6/Pro. I won't add it to the first post just yet in case there are differences, and I don't want to recommend something I can't actually try on the 6 Pro (since I won't get mine for likely another two days). Unlocking the Bootloader of the Pixel and Pixel XL

Good luck!
[Google Pixel 6 Pro] dj24:
This is great. I won't be getting mine for a while as well so please come back and update this thread.
[Google Pixel 6 Pro] Pekempy:
Generally YouTube video guides for software related things aren't particularly helpful, as they can often get outdated very quickly; especially in the early days of a device as they can't be updated when new things are found out.

It would probably be best to carefully read through guides
[Google Pixel 6 Pro] roirraW "edor" ehT:
@sidhaarthm reports here (be sure to thank him on his original post):
[Google Pixel 6 Pro] roirraW "edor" ehT:
FYI, I'm reminded by several members in these forums that unlocking the bootloader (the first step before being able to root your Carrier-Unlocked Pixel 6 Pro) wipes the device - so does re-locking it. So I highly recommend unlocking it as the first step when you get the phone, otherwise, you'll have to back up anything that doesn't normally get backed up, and go through the initial setup process again. Not a big deal for some, but would likely not be optimal for a new user.
[Google Pixel 6 Pro] Ghisy:
This! It's the first thing you should do out of the box if you plan on rooting later.
[Google Pixel 6 Pro] roirraW "edor" ehT:
@V0latyle posted a new thread with some very important and fascinating information about the increased difficulty to root Android 12: Read this before rooting. Be sure to thank him there.
[Google Pixel 6 Pro] galaxys:
That's great news about Unlocking the bootloader! I'll be doing that first thing to be ready for the future...:)
[Google Pixel 6 Pro] biTToe:
Does this mean to say there is no OEM unlocking switch in the developer options screen?
[Google Pixel 6 Pro] 96carboard:
There is, its there and you need to flip it.
[Google Pixel 6 Pro] 96carboard:
The unlock process works like this;

1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.

2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.

3) Settings --> About --> Build number. Tap it until it says you're a developer.

4) Back --> Network --> Wifi and connect it.

5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.

6) # adb reboot-bootloader

7) # fastboot flashing unlock

Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.
[Google Pixel 6 Pro] michaelrager:
Thanks it helped. When I went into command prompt, I get error is not a recognized internal or external command operable program or batch file.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I usually just open the command prompt in the same folder as where I have the Platform Tools (ADB, Fastboot, etc) extracted to, or you can CD (Change Directory) to the path you have them in, or there are other ways such as adding the path to Windows/Command Prompt's "Path" variable so that it always knows to look for commands there if it doesn't find them anywhere else that's already in the Path variable first.
[Google Pixel 6 Pro] Golf c:
The only way I can think of would be if someone incorporated the safety net fix into a custom ROM. That's what I did last year without root. Worked really well. Stock ROM you would have to root.
[Google Pixel 6 Pro] michaelrager:
Thanks got through reboot bootloader but when I put in fastboot flashing unlock, the prompt says waiting on device but nothing happeds on pixel. Do you know what might be wrong.?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Did you install the drivers I have linked to in the first post?
[Google Pixel 6 Pro] michaelrager:
the flash tool and platform tools? yes