Magisk Rooting Unlocked Galaxy A10e(SM-A102W/Canada) SOL/XAC No OEM Unlock Option ? - Samsung Galaxy A10 Questions & Answers

Magisk Rooting
Unlocked Galaxy A10e(SM-A102W/Canada)​No OEM Unlock Option​Device Details
Hardware
Model: Samsung Galaxy A10e(SM-A102W/Canada)
Android version: Android 9(Pie)
System Partition Type: A-Only System Partition
Chipset: Exynos 7884
CPU Architecture: ARM 32-bit(NOT ARM64)
System-as-root: Supported
Software
Baseband version: A102WVLS3ATB1
Kernel version: 4.4.111-16763710
#1 Fri Feb 28 18:33:54 KST 2020
Build number: PPR1.180610.011.A102WVLS3ATB1
SE for Android status: Enforcing
SEPF_SM-A102W_9_0009
Fri Feb 28 18:21:51 2020
Knox Version: Knox 3.3
Knox API level 28
TIMA 4.1.0
Service provider SW version: SAOMC_SM-A102W_OYV_SOL_PP_0008
RF8N20K9RSJ
SOL/SOL/XAC
I've recently purchased an unlocked Samsung Galaxy A10e(SM-A102W) from Walmart and had it set up with Lucky Mobile, I purchased this device with intentions to root/modify after a quick Google search before I took off. I had asked the salesperson who had sold me the phone if it could be done, he told me yes and so far I've spent the last 5 days fixated on trying to get this phone rooted.​
So far I've tried,
Enabling Developer Options
Enabling OEM Unlock | No option in Developer tools even after removing Google/Samsung accounts, Auto Updates > Off, playing with date/time settings, Auto Updates > On and re-flashing stock firmware
Enabling USB Debugging
Downloading stock firmware with frija and SamFirm *DEPRECATED applications.
Extracting AP file from stock firmware, copying to Internal Storage on Galaxy A10e Device
Downloading and installing MagiskManager.apk(7.5.1)
Patching AP file from stock firmware with Magisk Manager app on Galaxy A10e Device
(I have tried multiple patched AP files, from ones containing just /Meta-data/, boot.img, recovery.img and vbmeta.img to ones containing every .img)
Copying Patched AP file(magisk_patched.tar) from Internal Storage onto PC
Booting into stock recovery, Download/Bootloader mode | Is Bootloader already unlocked?
Flashing Patched AP file with Odin3B PatcheD/ModdeD v3.14.1 | Options set are "F. Reset Time", although I've tried "DeviceInfo", "Flash Lock", and "Decompress Data"
(I've heard with this model not to use "Auto Reboot"; using "Nand Erase" or "Re-Partition" will most likely damage your device!)
Galaxy A10e device returns message "SECURE CHECK FAIL : (BOOT)", "SECURE CHECK FAIL : (VBMETA)" and depending on the nature of the Patched AP file I used, I may or may not have to re-flash the stock firmware
In short, I'd really like to figure out if I can and/or how to root this device as of now.
Is there a reason my OEM unlock option isn't showing up in the developer tools?
Is going through the stock recovery(Pwr + Vol. UP, release Pwr on logo) and selecting Bootloader, proceeding to go into Download mode, mean my Bootloader is unlocked?
Tools and Resources
Patching/Flashing Software
- MagiskManager
- Odin
Official Samsung Stock firmware Applications
- frija
- SamFirm | *DEPRECATED
Official Samsung Stock firmware
- A102WVLS3ATB1

I also need to unblock the bootloader of this Samsung A10E to try to root.
I have tried to enable oem unlock with some manuals but this model has resisted.

Any luck?

Well, i also need help on that. I've successfully modded phones in the past, but i can't seem to find the hang of that particular model.
Any help appreciated. Thanks !

Related

[J5108/J7108][GUIDE]how to root the Galaxy J5/J7 2016 models J5108/J7108

Hi Evryone.
Because I didn't found CWM or TWRP Recovery or any root method for the galaxy J5 J5108 and the J7 J7108, I made a pre-rooted firmwares for those models.
This firmware base on the hong kong firmware which include the Google apps, this a full firmware exactly like the original, except the root.
After flash you will see the SuperSU app in the app drawer.
Also, this firmware contains the bootloader from the china firmware which doesn't have frp lock.
The root include the binary files in the system, and a pathed boot. (from Android 6.0 or samsung 5.1.1 pathing the boot is necessary for the root work properly)
Flashing this firmware will not wipe data automaticly. you should not lose anything.
This file will work on any firmware/baseband/csc. you can always flash it like a stock firmware.
J5 - base on - J5108ZHU1APD2.
Android version: 5.1.1
J7 - base on - J7108ZHU1APD1.
Android version: 5.1.1
Downloads
J5
http://www.mediafire.com/download/o8hfu81j3j4irjt/J5108ZHU1APD2_Rooted_by_avicohh.exe
J7
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Installation instructions
Before flashing check the CROM Service status in Download mode, if it locked you will need to unlock the bootloader first with the app attached.
Install samsung usb drivers from here.
Download the self extracting 7z file above and extract it (just double tap) to some folder, you should receive a tar.md5 file.
Open odin 3 (attached in the zip)
Put the tar.md5 file in AP.
Put the device in download mode. (vol down + home + power button, and then click on vol up)
Connect your phone to usb and wait for odin detect the device.
Click start.
After it finish choose reboot system now in recovery.
Enjoy.
If you want to thank me for this work, you can do this by donating.. :good:
Thanks a lot avicohh. This was simple and painless. I now have google services on my mainland China phone. And root too! And like you said - I did not loose anything.
well now i am stuck. I enabled my google account, installed and updated my apps through google play, shutdown and now I can't boot. The message in red on the top of the boot screen is:
"KERNEL IS NOT SEANDROID ENFORCING
Custom Binary blocked by FRP lock."
I also cannot reflash the same HK rooted firmware using Odin
apparently I should have enabled developer options then enabled OEM unlocking before rebooting. But I didn't know that so for now I am bricked
Also apparently, the fix for it is to reflash the original firmware using Odin. I am now downloading the firmware from http://updato.com/firmware-archive-select-model?record=1F170CA05E5611E6B055FA163EE8F90B but it is still another 2-3 hours to complete the download (yes, poor internet connection here.)... So I'll see how that goes...
OK, that didn't work. Now the message on the download mode screen says:
SW REV. Invalid type.
FRP is enabled, not allow download non FRP bootloader binary
Well..
I just recently had the same problem in another device.
I don't think the "Oem unlock" has nothing to do with this. the problem is that when you're adding Google account the frp (factroy reset protection) is automaticly enabled, and then it blocks the pathed boot.
The reason reflash the original firmware didn't work for you is because you tried to flash the china version, that doesn't have google service and also doesn't have frp in the bootloader. (apparently once frp is enabled this kind of operation is not allowed because you are actually trying to remove the frp lock by flashing bootloader..)
I think the solution will be to flash the original hong kong firmware with the frp bootloader and original boot. (or just the original boot)
http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Then, try to enable the "Oem unlock" option and finally flash the rooted firmware again.
maybe it will work, I'm not sure about it but I would like to know.
If this won't work, I'll try to combine the rooted hong kong firmware with the non-frp bootloader from the china firmware.
Thanks so much for replying avicohh
avicohh said:
Well..
The reason reflash the original firmware didn't work for you is because you tried to flash the china version, that doesn't have google service and also doesn't have frp in the bootloader. (apparently once frp is enabled this kind of operation is not allowed because you are actually trying to remove the frp lock by flashing bootloader..)
Click to expand...
Click to collapse
This makes sense. I was actually suspecting this and was considering trying the 6.01 HK version since that is the only one I could find: http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Now that you've posted a link to your original 5.1 HK firmware I'll try what you suggest. I'll wait to get home before I start the download.
But I still wonder if the 6.01 would work on my phone?
It's a mistake.
This link above is 5.1.1, not 6.0.1.
There is no 6.0.1 fro this model for now.
yes, I see, the website says its 6.01, but its actually 5.1.1. How do I know? BECAUSE IT WORKED!!! It took 7 hours to download but when I got up this morning it was done, I flashed and it worked!!!
I'm going to read up some more on this FRP business before flashing the rooted version again. My old phone (very old) had no such thing. I'd never heard of it till this unpleasant way of learning about it.
downloading
Same problem downloading the stock firmware from http://forum.xda-developers.com/gal...108-how-to-root-galaxy-j7-2016-model-t3426967
I hope this works....
---------- Post added at 12:27 AM ---------- Previous post was at 12:26 AM ----------
Tukuvai said:
Same problem downloading the stock firmware from http://forum.xda-developers.com/gal...108-how-to-root-galaxy-j7-2016-model-t3426967
I hope this works....
Click to expand...
Click to collapse
I meant http://updato.com/firmware-archive-s...55FA163EE8F90B
Hi guys.
Thanks for your replies.
I've just checked it now on another device.
As it turn out after a several tests, this "custom binary blocked by frp lock" problem occurs only if the oem unlock option is disabled.
Here is what I did, step by step:
First, I enabled the oem unlock option and then I added Google account - nothing happened. frp lock in Download mode is still off and everything working fine.
I removed the google account, turned off the oem unlock option and finally added the google account again - frp lock in download mode immediately switch to on, and when I tried to restart, the device has stuck on the boot. (custom binary..)
I flashed stock firmware (from the link above), the device now bootup normally but the frp lock in download mode is still on. (I didn't remove the google account yet)
Final check - I enabled the oem unlock again, and the frp lock in download mode switch to off.
So..
I can safely say that all you need to do is just enable oem unlock in developer options, and then flash the rooted firmware.
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
avicohh said:
Hi guys.
Thanks for your replies.
I've just checked it now on another device.
As it turn out after a several tests, this "custom binary blocked by frp lock" problem occurs only if the oem unlock option is disabled.
Here is what I did, step by step:
First, I enabled the oem unlock option and then I added Google account - nothing happened. frp lock in Download mode is still off and everything working fine.
I removed the google account, turned off the oem unlock option and finally added the google account again - frp lock in download mode immediately switch to on, and when I tried to restart, the device has stuck on the boot. (custom binary..)
I flashed stock firmware (from the link above), the device now bootup normally but the frp lock in download mode is still on. (I didn't remove the google account yet)
Final check - I enabled the oem unlock again, and the frp lock in download mode switch to off.
So..
I can safely say that all you need to do is just enable oem unlock in developer options, and then flash the rooted firmware.
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
Click to expand...
Click to collapse
Hey, How do I enable OEM unlock when I can't even boot my device. it simply refuses to boot.
Hi
First flash the original HK firmware from here. the device should boot up normally.
http://updato.com/firmware-archive-select-model?record=5C13445B54D811E6B055FA163EE8F90B
Then, enable oem unlock.
Thanks for making the root version of mainland firmware. I'm going to stick with the HK version as I want to have google services. and thanks for testing the oem unlock
I informed myself some more about FRP and OEM unlock and I am now feel safe to use the rooted HK firmware. Except, I came across one note for which I want further clarification before proceeding. The note is from http://www.androidcentral.com/factory-reset-protection-what-you-need-know and it says:
"A couple notes need added here. This doesn't undo Samsung's (or anyone else's) version of Reactivation Lock. If you've enabled data reset protection through your Samsung account, you'll need to turn that off in your Security settings. You can find the switch under the "Find My Mobile" section."
So, I want to be sure I don't have this samsung Reactivation Lock enabled. and that I am in no danger of it auto-enabling. I believe I am safe but I would like to know if anyone has more clear information.
What I do know is before I flashed to HK ROM, when I went into download mode, there displayed a setting:
"REACTIVATION LOCK: OFF"
now, using the HK ROM, it is gone, but in that exact same location is the setting:
"FRP LOCK: OFF"
I think, that means the mainland version of the FRP lock (Samsung Reactivation Lock), is now replaced with the google FRP lock and as I don't have to worry about the samsung reactivation lock anymore. Is that so?
even so, as the article says, I look in "Settings" >> "Lock screen and security" >> "Find my mobile" >> log into Samsung Account when prompted, then it does not display the "Reactivation Lock" option that is shown in at least one guide that I found. I really think this is further proof I don't have to worry about Samsung Reactivation Lock. Can anyone confirm?
Yes I can confirm.
But pay attention that because of the FRP, is not possible to make a pre-rooted firmware for Android 6.0 and above or 5.1.1 Samsung devices, from firmware contains FRP protection like the HK one.
From those android versions (and above), a pre-rooted firmware (or any root method) must include a patched kernel.
Due to the FRP protection, once it turn on, it detect the custom kernel (boot) and not allow the device to boot. (custom binary blocked by FRP lock)
That's the reason I had to replace the HK bootloader which contain FRP protection, with the China bootloader which contain the Samsung reactivation lock. (instead of FRP, because china firmwares doesn't include any google services)
I don't know what the policy of the Samsung reactivation lock, about custom kernels.
And also I don't know if the Samsung reactivation lock turns on automaticly if you are adding Samsung account. (Like the FRP lock)
And one more thing, I beleive most people don't use Samsung account at all.
So after all this,
If it come to decision what to use, the FRP lock or the Samsung one (depends only in the bootloader), I'm pretty sure that in this case (custom boot), the best is to use the Samsung lock, and just dont add Samsung account, or add Samsung account if needed but turn off the Reactivation lock in the Find my mobile settings.
I hope it help you a bit.
Good luck.
btw, If you can check the Samsung lock after root and report here, it would be great.
avicohh said:
Anyway, to be even more sure, I made a new firmware with the china bootloader, frp now is not even exist in download mode.
You can download the new firmware from here
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Good luck!
Click to expand...
Click to collapse
Oh, at first I thought you meant you rooted the mainland firmware. Now, based on your later post, I believe what you did was to put the mainland bootloader in the rooted HK firmware. Is this the case? If so, that means I can still have google services, and root, and no possibility of FRP issues because its a mainland bootloader. OK, I will try tonight. The Samsung reactivation lock is off by default. Even adding a Samsung account does not turn it on, you have to go into "find my phone" to turn it on. So it should be safe. I will confirm tonight after I download your new firmware.
Yes, this is exactly what i did.
Thanks for testing the samsung account. so it is pretty safe.
yes, this new version with mainland bootloader is good. It seems almost impossible to lock.
Now when I go to download mode, there is no more "FRP LOCK: OFF". in its place is "REACTIVATION LOCK: OFF".
Just for fun I tested by going inter developer options and turned off OEM unlock - then I tried to reboot = success. Enter download mode = still "REACTIVATION LOCK: OFF". Of course I turned it back on again after the test.
and in settings, find my mobile, there is still not a setting for "REACTIVATION LOCK". I have seen an example on the web that this reactivation lock setting should be at the bottom of the options under find my mobile. So, actually now I cannot find any way to turn on the reactivation lock - this is good, its what we want.
Of course to even enter the "find my mobile" section I can do nothing at all (in fact it does not even show me what the options are) untill I give my samsung account credentials. Once I give credentials I can see the options but there is no option to turn on reactivation lock. There is just one thing, maybe, is that in "find my mobile", there a place that says: for more information go to findmymobile.samsung.com. When I go there I have 2 options:
-1) FIND - Find, Lock, Wipe my device
-2) PREPARE - Ready device for Find my Mobile
this "prepare" option I am afraid to try, I am afraid it may be the one to enable reactivation lock. Clearly it is not required to actually find my mobile because I just click the "Find" button and it it finds it for me. So, what would be the use of "prepare"?
At any rate, we know that just creating a samsung account does not activate the lock. I never had a Samsung account before. When I set up this new phone I never did enter developer mode to turn on oem unlock but i did create the samsung account. It was after that I flashed version 1 of avicohh's rooted firmware and when I went into download mode, it said REACTIVATION LOCK: OFF, so creating the Samsung account does not turn it on.
avicohh said:
Hi Evryone.
Because I didn't found CWM or TWRP Recovery or any root method for the galaxy J5 J5108 and the J7 J7108, I made a pre-rooted firmwares for those models.
This firmware base on the hong kong firmware which include the Google apps, this a full firmware exactly like the original, except the root.
After flash you will see the SuperSU app in the app drawer.
Also, this firmware contains the bootloader from the china firmware which doesn't have frp lock.
The root include the binary files in the system, and a pathed boot. (from Android 6.0 or samsung 5.1.1 pathing the boot is necessary for the root work properly)
Flashing this firmware will not wipe data automaticly. you should not lose anything.
This file will work on any firmware/baseband/csc. you can always flash it like a stock firmware.
J5 - base on - J5108ZHU1APD2.
Android version: 5.1.1
J7 - base on - J7108ZHU1APD1.
Android version: 5.1.1
Downloads
J5
http://www.mediafire.com/download/o8hfu81j3j4irjt/J5108ZHU1APD2_Rooted_by_avicohh.exe
J7
http://www.mediafire.com/download/z7bh4sdmzqer6nb/J7108ZHU1APD1_rooted_by_avicohh_v2.exe
Installation instructions
Before flashing check the CROM Service status in Download mode, if it locked you will need to unlock the bootloader first with the app attached.
Install samsung usb drivers from here.
Download the self extracting 7z file above and extract it (just double tap) to some folder, you should receive a tar.md5 file.
Open odin 3 (attached in the zip)
Put the tar.md5 file in AP.
Put the device in download mode. (vol down + home + power button, and then click on vol up)
Connect your phone to usb and wait for odin detect the device.
Click start.
After it finish choose reboot system now in recovery.
Enjoy.
If you want to thank me for this work, you can do this by donating.. :good:
Click to expand...
Click to collapse
sir, you are awesome!!
I'll try to install in my J5108. I will give to my daughter. Is there a form to unroot the phone? Thanks!
Yes.
Just install stock rom.
http://updato.com/firmware-archive-select-model?record=A097D215549D11E6B055FA163EE8F90B

[Doogee X6 S] getting rid of OEM adware

Hi.
I have a Doogee X6 S.
It is currently flashed with stock ROM¹, which runs Android 6.0 with a 3.4.5 kernel and contains OEM adware, and maybe worse.
I'd like to be able to flash a more trustworthy rom of android.
I was unable to root the device with kingoroot app. The bootloader is locked, I can't flash TWRP.
I tried to unlock the bootloader:
- I unlocked and enabled developer options,
- I checked the "oem unlocking" option ("allow the bootloader to be unlocked"),
- "adb reboot bootloader" rebooted the phone in fastboot mode
- "fastboot oem unlock" asked me confirmation for unlock, VOL_UP for "Yes", VOL_DWN for "No", but none of the keys have any effect when pressed.
I tried flashing older versions of the stock ROM with SP Flash Tool, but this resulted in a softbick (solved by flashing back last stock ROM).
I tried contacting Doogee support, to no avail.
I don't know what to try next, so here I am!
While I'm not an Android hacker, I know my Linux, and I'm not affraid of complex solutions.
¹ available from official support page: community.doogee.cc/forum.php?mod=viewthread&tid=4872
Since I didn't get any answer here in one week, I opened a thread on the official support forum :
community.doogee.cc/forum.php?mod=viewthread&tid=7544&page=1&extra=#pid50966
If I get a solution there, I'll relay it here.

Problem flashing the combination file

Ok, so, I have an S9+ model G9650ZHS6CSK4 (Android 9.0, I only found one firmware version that matched my bootloader version and it was a 9.0 one)
It took me a long while, but I've downloaded this combination firmware G9650ZCU6ASJ2 (FA80)
Everything fine there, but, when I go to Odin and load the combo file in the AP slot of Odin, connect the phone and then click start it immediately stops, and in the phone it says:
FRP is enabled, ignore PIT download.
FRP is enabled, not allowed to download non-FRP abl binary
Here is the log of Odin when it happens: https://m.imgur.com/a/dEAwC26
What am I doing wrong? I know the phone is FRP locked, I want to bypass it.
Can you guys help me?

HUAWEI PRALX1 - please instructions on how to unlock bootloader and root

hello please advice! How do I unlock the bootloader at this point and do root with magisk? please describe step by step instructions or link to instructions. sorry because this thread must be here, but I didn't find anything current. I think it's better to get advice than to do wrong and then look for how to restore your phone from a broken state.
my build: Andoid 8.0.0 Emui 8.0.0 PRA-LX1 8.0.0.401 (C432)
Phone locked, FRP unlocked
Thank you very much
niki.rsb said:
hello please advice! How do I unlock the bootloader at this point and do root with magisk? please describe step by step instructions or link to instructions. sorry because this thread must be here, but I didn't find anything current. I think it's better to get advice than to do wrong and then look for how to restore your phone from a broken state.
my build: Andoid 8.0.0 Emui 8.0.0 PRA-LX1 8.0.0.401 (C432)
Phone locked, FRP unlocked
Thank you very much
Click to expand...
Click to collapse
Huawei doesn't unlock bootloader's any more.
You'll have to find a pay service that supports your model.
Sent from my HD1907 using Tapatalk
@niki.rsb
In order to root device's Android unlocking device's boot-loader isn't a pre-requisite.
Rooting a phone's Android means giving user and/or applications administrative rights, will say unrestricted access to Android's system files.
jwoegerbauer said:
@niki.rsb
In order to root device's Android unlocking device's boot-loader isn't a pre-requisite.
Rooting a phone's Android means giving user and/or applications administrative rights, will say unrestricted access to Android's system files.
Click to expand...
Click to collapse
Wrong... you can't flash a patched boot.img without an unlocked bootloader
the only way to root the device is with a Magisk_patched boot.img
clsA said:
Wrong... you can't flash a patched boot.img without an unlocked bootloader
the only way to root the device is with a Magisk_patched boot.img
Click to expand...
Click to collapse
You should carefully read instead of replying nonsense.
I don't understand English well. I don't understand it now. I think everyone writes something different. i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
niki.rsb said:
I don't understand English well. I don't understand it now. I think everyone writes something different. i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
Click to expand...
Click to collapse
You can only unlock bootloader with a paid service.
Once the bootloader is unlocked you can use magisk and patch and then flash a rooted boot.img
Instructions for making the patched boot.img are here > https://topjohnwu.github.io/Magisk/install.html
you get the correct stock boot.img from a full firmware update.zip for your version
Bootloader Unlock Instructions found here > https://techelucid.com/unlock-bootloader-huawei/
Pre-Requisites for unlocking bootloader
Enable USB Debugging
Install USB Drivers for Huawei 98 Lite:
USB Debugging:
Goto Settings> About Phone Tap 7 Times on Build Number
Then In Settings>Developer Options and enable USB Debugging
Tick The “Oem Unlock” Checkbox
Download the following things for Huawei Device
Get and Install USB Drivers on your computer from here
Download DC Huawei Bootloader Codes from here.
Get DC Unlocker client app from here.
Buy Dc Unlocker Credit With Android App
Download and install “DC Huawei Bootloader Codes Android app“ from the link given above in downloads section.
Open the downloaded apk file and install it on your device.
Click on DC Unlocker Account.
Type your email id and complete the payment processes.
After successful payment; save the user password. You will need this while using DC unlocker pc app.
Get Huawei Bootloader Unlock Code With Dc Unlocker
Extract the downloaded DC Unlocker client app zip file.
Double click or Run dc-unlocker2client.exe.
Move to the server tab and log in. use the user password which you got in DC Huawei Bootloader Codes Android app.
Connect your device to pc and enable Manufacturer Mode (You can easily enable manufacturer mode by Typing *#*#2846579#*#* in the dial pad. After that click on Background settings > USB port settings > Manufacturer Mode).
Select the Manufacturer type “Huawei Phones” Model “Auto Detect”. After that click on the search button.
Click on Unlocking Tab. After that choose Read Bootloader Code.
Wait for some time to Unlock code to arrive. When it does, copy the data and save it in a notepad file.
Last step to Unlock Bootloader
Turn off your device.
Put it in Fastboot mode by pressing Volume down + Power button at the same time.
Connect your device to a PC with the USB cable.
Enter The Unlock Code In Code In Command prompt Window and press Enter.
Wait for a few seconds and your device will restart.
You can now go ahead and customize your device by installing TWRP or then flash SuperSu Magisk to root it. So you have succeeded to unlock your Huawei bootloader. .
Click to expand...
Click to collapse
with the bootloader unlocked you don't actually need TWRP
you can fastboot flash the patch_boot.img
just use the command
fastboot flash boot patched_boot.img
thank you for the instructions. But unfortunately the bootloader is still locked. I followed the instructions. it wrote me the bootloader number. But when I opened the command line and wrote the number, then nothing did. where should i open the dashboard? classic C: \ Windows \ system32>?
I will also provide a transcript of the dc unlocker
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
=============================================== ================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type * # * # 2846579 # * # * for Qualcomm and Kirin based models, or * # * # 14789632 # * # * for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
Unlock Auto detect (recommended) cost 4 Cr
Service text tutorial: https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Reading bootloader code ...
Bootloader code: 9x9x2x2x2x8x5x3x
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone: PRA-LX1
Model: Huawei phone in fastboot mode
IMEI: 866386030063396
Serial NR. : 9DC7N17728006152
Firmware: PRA-LX1 8.0.0.401 (C432
IMEI1: 866386030090407
FB LockState: LOCKED
USER LockState: LOCKED
locked
Battery state: 4068mv
=============================================== ================
Check account status
User: bl21816
Credits left: 0
Activated features:
Software debugger
Unlock Huawei phone in fastboot mode (866386030063396) cost 15 cr
Server message:
Check prices at: https://www.dc-unlocker.com/buy/user_prices
Insufficient credits!
=============================================== ================
niki.rsb said:
i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
Click to expand...
Click to collapse
Right after you root Android OS, Google Pay will stop working. How to bypass this in detail is explained here.
Again:
It's a misconception if people like you think the bootloader of a device has to be unlocked in order to root device's Android OS. These people just don't know what role the bootloader has, just don't know what rooting Android OS means.
niki.rsb said:
I will also provide a transcript of the dc unlocker
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
=============================================== ================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type * # * # 2846579 # * # * for Qualcomm and Kirin based models, or * # * # 14789632 # * # * for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
Unlock Auto detect (recommended) cost 4 Cr
Service text tutorial: https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Reading bootloader code ...
Bootloader code: 9x9x2x2x2x8x5x3x
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone: PRA-LX1
Model: Huawei phone in fastboot mode
IMEI: 866386030063396
Serial NR. : 9DC7N17728006152
Firmware: PRA-LX1 8.0.0.401 (C432
IMEI1: 866386030090407
FB LockState: LOCKED
USER LockState: LOCKED
locked
Battery state: 4068mv
=============================================== ================
Check account status
User: bl21816
Credits left: 0
Activated features:
Software debugger
Unlock Huawei phone in fastboot mode (866386030063396) cost 15 cr
Server message:
Check prices at: https://www.dc-unlocker.com/buy/user_prices
Insufficient credits!
=============================================== ================
Click to expand...
Click to collapse
Simply getting the code isn't enough you have to flash it see below and see the tutorial for dc unlocker here > https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
Using your Unlock Code:
1. Turn off your phone, Boot your device into Fastboot mode with Vol down and power button.
2. CD to where you downloaded ADB/Fastboot Tools
Run these commands when inside ADB tools directory
a) fastboot devices. (your device should bee listed. If not reinstall drivers/reboot)
b) fastboot oem get-bootinfo (just to confirm everything is detected correctly
c) fastboot oem unlock 9x9x2x2x2x8x5x3x
3. Acknowledge the prompt on your phone. Device will be WIPED!
4. Once the wipe finishes it will take several minutes for phone to boot up. Do not panic. Once you See Huawei logo you are OK!
Click to expand...
Click to collapse
Note: I just read that whole thread (below) and the tutorial is out of date.
it's much easier to root now using the magisk patched_boot.img
see my post earlier on how it's done
instructions for unlocking and rooting your phone here > https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
He even has a free method to get the bootloader unlock code (Seems you already have yours above)
Other useful links I found during my search
HiSuite 5.0.2.300 - https://androidmtk.com/download-huawei-hisuite
Multi-Tool for Huawei - https://pro-teammt.ru/multi-tool-for-huawei-honor/
Firmware Database > https://pro-teammt.ru/en/online-firmware-database-ru/
Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
How to extract Huawei firmware and its UPDATE.APP > https://nerdschalk.com/extract-huawei-firmware-update-app/
jwoegerbauer said:
Right after you root Android OS, Google Pay will stop working. How to bypass this in detail is explained here.
Again:
It's a misconception if people like you think the bootloader of a device has to be unlocked in order to root device's Android OS. These people just don't know what role the bootloader has, just don't know what rooting Android OS means.
Click to expand...
Click to collapse
Yes you're right. I don't know exactly how it works and I don't understand it. But that's why I turned here and ask for advice on how to proceed. If I had knowledge, I wouldn't bother anyone to help me. I don't think this is anything new.
clsA said:
Simply getting the code isn't enough you have to flash it see below and see the tutorial for dc unlocker here > https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
Note: I just read that whole thread (below) and the tutorial is out of date.
it's much easier to root now using the magisk patched_boot.img
see my post earlier on how it's done
instructions for unlocking and rooting your phone here > https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
He even has a free method to get the bootloader unlock code (Seems you already have yours above)
Other useful links I found during my search
HiSuite 5.0.2.300 - https://androidmtk.com/download-huawei-hisuite
Multi-Tool for Huawei - https://pro-teammt.ru/multi-tool-for-huawei-honor/
Firmware Database > https://pro-teammt.ru/en/online-firmware-database-ru/
Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
How to extract Huawei firmware and its UPDATE.APP > https://nerdschalk.com/extract-huawei-firmware-update-app/
Click to expand...
Click to collapse
Yes there are a lot of versions and procedures for how to root them on the internet. Some don't work, others worked, but currently they don't either. Or there may be new better practices. For a person who does not have much knowledge, it is very difficult to choose the right one. If what you are saying is new and mainly functional, I will look and try to proceed
niki.rsb said:
Yes there are a lot of versions and procedures for how to root them on the internet. Some don't work, others worked, but currently they don't either. Or there may be new better practices. For a person who does not have much knowledge, it is very difficult to choose the right one. If what you are saying is new and mainly functional, I will look and try to proceed
Click to expand...
Click to collapse
first just get the bootloader unlocked
I'll show you how to extract and create a rooted boot.img
clsA said:
first just get the bootloader unlocked
I'll show you how to extract and create a rooted boot.img
Click to expand...
Click to collapse
I have the bootloader unlocked. Is it now necessary to install twrp for magisk? and how do you please proceed?
niki.rsb said:
I have the bootloader unlocked. Is it now necessary to install twrp for magisk? and how do you please proceed?
Click to expand...
Click to collapse
Excellent !!
We need your firmware version to get the correct ramdisk.img
look in settings / about phone for the firmware version or just post a screen shot of that screen
this is your file (I got it from your first post) > PRA-LX1 8.0.0.401 (C432) FullOTA-MF > https://pro-teammt.ru/en/online-fir...mware_model=PRA-LX1+8.0.0.401&firmware_page=0
download the update.zip (I'm downloading it also)
Next download the Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
I posted the guide here for using the extraction tool > https://nerdschalk.com/extract-huawei-firmware-update-app/
and then follow this guide to root the ramdisk.img
Huawei
Huawei devices using Kirin processors have a different partitioning method from most common devices. Magisk is usually installed to the boot partition of the device, however Huawei devices do not have this partition. Depending on what EMUI version your device is running, the instructions will be slightly different.
Obtain Stock Images
Huawei does not release official factory images, however most firmware zips can be downloaded from the Huawei Firmware Database. To extract images from UPDATE.APP in the zip, you have to use Huawei Update Extractor (Windows only!)
EMUI 8
For EMUI 8 devices, your device has a partition named ramdisk, which is where Magisk is going to be installed.
If you plan to use custom recoveries, simply follow the instructions for custom recovery and you’re all set.
If you plan not to use custom recoveries, you will have to extract RAMDISK.img from your firmware. Follow the instructions for boot image patching above, but use the RAMDISK.img file instead of a boot image.
To flash the patched image to your device, here is the fastboot command:
fastboot flash ramdisk /path/to/magisk_patched.img
Be aware you are flashing to ramdisk, not boot!
Click to expand...
Click to collapse
Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don’t want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock RAMDISK.img, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet. The following instructions will guide you through the process after you have the copy of boot/recovery image.
Copy the RAMDISK.img to your device
Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock RAMDISK.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched RAMDISK.img to your device and reboot. For most devices, here is the fastboot command:
fastboot flash ramdisk magisk_patched.img
fastboot flash boot /path/to/magisk_patched.img or
fastboot flash recovery /path/to/magisk_patched.img if you are patching a recovery image
Click to expand...
Click to collapse
now use fastboot reboot
at this point your phone should be rooted
I uploaded the patched ramdisk.img here if you have trouble > https://www.androidfilehost.com/?fid=8889791610682890848
the unpatched RAMDISK.IMG is also their > https://www.androidfilehost.com/?w=files&flid=314978
You also have TWRP 3.11 available for your phone > https://androidfilehost.com/?fid=1899786940962602140
it's ease to flash TWRP and then root your phone with a Magisk.zip in TWRP
it's also nice if you like to flash roms or make backups of your system and data
clsA said:
this is your file (I got it from your first post) > PRA-LX1 8.0.0.401 (C432) FullOTA-MF > https://pro-teammt.ru/en/online-fir...mware_model=PRA-LX1+8.0.0.401&firmware_page=0
download the update.zip (I'm downloading it also)
Click to expand...
Click to collapse
I did not find a download file or a link where I can download, so I download here
https://androidhost.ru/1iXE is it ok?
yes build number is PRA-LX1 8.0.0.401 (C432) Emui 8, Android 8
And what is the difference between when I run through that ramdisk.img or when I make a flash twrp and install magisk.zip??
niki.rsb said:
I did not find a download file or a link where I can download, so I download here
https://androidhost.ru/1iXE is it ok?
yes build number is PRA-LX1 8.0.0.401 (C432) Emui 8, Android 8
And what is the difference between when I run through that ramdisk.img or when I make a flash twrp and install magisk.zip??
Click to expand...
Click to collapse
I posted the patched ramdisk.img for you
all you need to do is copy it to your adb/fastboot folder and reboot your phone to fastboot mode and flash it
fastboot flash ramdisk magisk_patched.img
their is no difference in the end result, either method will work to Root your phone
clsA said:
I posted the patched ramdisk.img for you
all you need to do is copy it to your adb/fastboot folder and reboot your phone to fastboot mode and flash it
fastboot flash ramdisk magisk_patched.img
their is no difference in the end result, either method will work to Root your phone
Click to expand...
Click to collapse
I did exactly and just what you wrote. the flash completed without error, but I don't know what the result should have been. I don't even have root, magisk, I didn't know the change.
niki.rsb said:
I did exactly and just what you wrote. the flash completed without error, but I don't know what the result should have been. I don't even have root, magisk, I didn't know the change.
Click to expand...
Click to collapse
Install magisk manager if it's not in your app drawer

Are there custom roms for Galaxy A14 that you can flash through ODIN?

Tale as old as time. Have a phone given, factory reset with a Google account that wasn't properly removed.
So FRP lock is in play.
Seems like all the old tricks & tips I knew years ago don't seem to work on this device. Seems like the A14 on Android 13 is lock tight.
What I can do is use ODIN to flash back to stock rom, but that didn't really help.
And what I can also do is go through User License agreements, and somehow fumble my way through Learn More links that I can eventually lead to Google Search
But this method doesn't have Java Script enabled, so I can't login to Google account and add my own account that way.
I'm looking towards roms for the previous model since they're so similar but this feels like a dead end before I even think of a download since incompatible roms can't be flashed.
All I really need is Bootable Android 11 or 12 regardless of how functional or broken it is so I can try exploits for those versions. Just enough to activate OEM unlocking and USB debugging is the end goal
Any tips y'all have?
According to this list
LineageOS 20 Supported Phones: All Models For 2023 [UPDATED]
Here's a quick breakdown of ALL the Android phones that can run LineageOS 20...
www.knowyourmobile.com
the popular Lineage OS isn't available for the Galaxy A14
Rottytops said:
Tale as old as time. Have a phone given, factory reset with a Google account that wasn't properly removed.
So FRP lock is in play.
Seems like all the old tricks & tips I knew years ago don't seem to work on this device. Seems like the A14 on Android 13 is lock tight.
What I can do is use ODIN to flash back to stock rom, but that didn't really help.
And what I can also do is go through User License agreements, and somehow fumble my way through Learn More links that I can eventually lead to Google Search
But this method doesn't have Java Script enabled, so I can't login to Google account and add my own account that way.
I'm looking towards roms for the previous model since they're so similar but this feels like a dead end before I even think of a download since incompatible roms can't be flashed.
All I really need is Bootable Android 11 or 12 regardless of how functional or broken it is so I can try exploits for those versions. Just enough to activate OEM unlocking and USB debugging is the end goal
Any tips y'all have?
Click to expand...
Click to collapse
You can't do anything because the bootloader lock is on.
I bypassed frp with sp flash tool but a14 has exynos processor so sp flash tool will not work.
There is no offical previous android, So downgrade will not work too.
Was able to bypass FRP unlock using one of those paid tools, but it may have been unnecessary to pay. (SamFW to be specific)
I'll explain for future googlers dealing with the same issue.
So I had the ATT model of the device. Specifically model SM-A146U. It comes with an Exynos or Mediatek SoC.
Mine was specifically the MT variant.
I used Odin3 to revert to the stock build. Build dated November 29/Dec 1 2022; despite the official release date of the device being Jan 2023.
The emergency code *#0*# does not work, but *#*#88#*#* does.
Obviously you needed Samsung USB, ADB, drivers installed. Additional troubleshooting has me download Microsoft Visual C++ 2015 ; and MT65XX Preload Drivers.
The SamFW tool claims it's free to remove the FRP lock on security patches pre-dating December 2022.
The SamFW tool only suggests you needed Samsung driver's and Visual C++. So I tried several times using the SamFW tool to push it's exploit, and it kept failing.
So in a moment of weakness, I bought the $15 credit pack because it promised "All models", ran the tool again, and still it failed. It required a credit card number for a service called coffee break or something, which is exactly the shady **** I have a cash app card for. I was not going to use my real bank account.
Because it runs a ADB exploit, I reboot into Recovery. Then in recovery menu, I select to Reboot into Bootloader, which puts the device into fastboot.
This is where I discover that I had no ADB drivers.
So I install ADB, and open Terminal/shell, whatever you call it. (Hold Shift and right click in ADB folder to shortcut ADB terminal)
I type:
Fastboot Devices
Didn't get a serial. I reboot Fastboot again, this time with Device Manager open on Windows, and notice for 5 seconds, a device called MT65xx preloader was lacking driver, and unloaded to reload ADB drivers. This is where I find out I'm using a MediaTek SoC
So I finally googled and install MT65xx Preload. Reboot to Fastboot 1 more time. I type
Fastboot Devices
I get a serial.
So not I reboot to system, then on phone in emergency dial type *#*#88#*#* then do another device check. Looks good.
Because I already paid $15 for the premium unlock, that's the first option I pick it finally unlocks. But because all this time I was missing critical mediatek drivers, the free option still could have worked. So I can't confirm if being free would have sufficed, or if I needed that paid service.
But what's done was done, and I was able to get into the phone.
So to recap I used:
SM-A146U ATT stock Rom (5.5GB), earliest build Nov-Dec 2022 (Google it)
Odin v3 Flash Tool (Hold Vol+ Vol- & Power to access)
Samsung USB Drivers (Latest and official)
Google ADB Drivers (Mini installer)
Microsoft Visual C++ 2015
MT65xx preloader Drivers (Google it)
And SamFW 4.6 FRP Tool
Emergency Dial code : *#*#88#*#*
To bypass FRP Lock on Galaxy A14 ATT version, Model SM-A146U ; MediaTek variant.
and to reiterate, Recovery and Fast Boot are not necessary in any part of the process.
I use Recovery to boot into Fastboot, and I only use FastBoot + ADB to personally confirm that my computer recognizes the device connected in several boot modes

Resources