Database Info

V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide

WARNING: By following these direction/procedure, you are agreeing to taking full responsibility and accountability for your devices . This guide revolves around model conversion for H915 users, and usually avoided due to risk of bricking.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are model jumping, as of now it is irreversible until a proper H915 recovery rom is developed.
H915 Owners please be advised to check you network carriers frequency band as they are slightly different. As of now, can confirm a KDZ converted H915(US996) is functional using LTE B4 (1700/2100 AWS 1) with Rogers/Fido.
H910/H915
Networks: GPRS, EDGE, UMTS, HSDPA, HSUPA, HSPA+, LTE, LTE-A
LTE Cat12 700/800/850/1700/1800/1900/2100/2300/2600 (Bands 1,2,3,4,5,7,12,17,20,30) Max Download Speed: 600 Mbps Max Upload Speed: 150 Mb
US996
Networks: GPRS, EDGE, CDMA2000 EV-DO Rev A, UMTS, HSDPA, HSUPA, HSPA+, LTE, LTE-A
*LTE Cat12 700/800/850/1700/1800/1900/2600 (Bands 2, 3, 4, 5, 7, 12, 13, 17, 20, 25) Max Download Speed: 600 Mbps Max Upload Speed: 150 Mbps
Benefits:
Unlocked,rooted. -For official US996 owners, could bypass using LG unlocking software so that you do not lose warranty.
Disadvantages:
-Lose FM Radio (Possible 3rd party app solution)
- Can't revert back to H915 which means it would lose warranty until H915 rom is created.
- Static on boot for a few seconds then need to cover second screen sensor (fixable with some kernel) process could soft/hard brick
Uncertainty:
- Support for 66 LTE
-Carrier unlock. (The Freedom V20 was unlocked first so please confirm if converting carrier unlocked your phone.)
This guide will unlock and root the H915 by completely converting it to a US996. (As the serial won't match, I believe it wouldn’t be possible to unlock it with the official LG software. For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead. However as of now, there is static on the boot for a few minutes when android first loads, but after it should only be for a few seconds. Once covering the 2nd screen sensor, it will go back to normal. Static will reappear next boot. Some kernels can fix this issue.
The process might take some time and as of now irreversible until a flashable H915 Stock Recovery Rom is created. (A H915 recovery rom would probably have the network disabled problems but with once recognized as a H915 instead of a US996, Autoprime's LGUP uppercut should be able to flash the H915 stock KDZ.
The unlocking/rooting ,model conversion process:
Backup-> Dirtysanta method step 1-4.5 -> Flash with UPPERCUT LGUP to US996 KDZ = Fully converted H915 to US996
H915 converted US996 OR Official US996 -> Dirtysanta method step 1 - 4.5.
General Overview for H915 owners:
- Backup then update/downgrade to H91510d firmware with Uppercut with .KDZ
- Me2141's Dirtysanta unlock/rooting
○ At Step 3 ,TWRP backup everything except data to microsd , then Format DATA
○ step 4.3(Sprint LS997) -> flash Tilde88's US996 100% Stock deODEXEd Rom instead of a LS997. (Around 15min static boot first time reconfiguration)
- UPPERCUT LGUP should recognize phone as a US996, flash stock US99610f .DZ or .KDZ.
- Fully functioning H915 that is converted to a US99610f with network connection.
- Me2141's Dirtysanta unlock/rooting
○ At Step 3 ,TWRP backup everything except data to microsd , then Format DATA
○ step 4.3(Sprint LS997) -> flash Tilde88's US996 100% Stock deODEXEd Rom instead of a LS997. (Around 15min static boot first time reconfiguration)
- H915 converted to a rooted and unlocked US996. OR LG factory bootloader bypassed rooted US996
General Overview for official US996 owners:
- Backup
- Me2141's Dirtysanta unlock/rooting
○ At Step 3 ,TWRP backup everything except data to microsd , then Format DATA
○ step 4.3(Sprint LS997) -> flash Tilde88's US996 100% Stock deODEXEd Rom instead of a LS997. (Around 15min static boot first time reconfiguration)
- Rooted and unlocked US996
Detailed H915/US996 root/unlock procedures:
1. Download All-IN-ONE Organized V20 rooting package without KDZ and ROM
https://goo.gl/e43Qdf
1. Download Individual
a. H91510d kdz, https://lg-firmwares.com/download-file/?fileId=4449
b. US99610f kdz, https://lg-firmwares.com/download-file/?fileId=5252
c. LGMobileDriver_WHQL_Ver_4.2.0.exe , http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427
d. LGUP_Store_Frame_Ver_1_14_3 .http://downloads.codefi.re/autoprime/LG/Flash_Tools/LGUP/
e. Autoprime's Uppercut.exe LGUP, http://downloads.codefi.re/autoprime/LG/Flash_Tools/LGUP/
f. Android SDK Platform Tools, https://developer.android.com/studio/releases/platform-tools.html
g. Me2141's Dirtysanta , https://www.androidfilehost.com/?fid=457095661767122821
h. TWRP 3.0.2-1 US996, https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-us996.img
i. Tilde88's US996 100% Stock deODEXEd Rom https://mega.nz/#!LAFXxTgL!VsqcMx8PNhagWRN50gWALnskcyfqDwKQaGURhYuyZtU
2. Highly recommend disabling anti-virus/ Windows Defender Real-time Protection for Autoprime's uppercut.exe to function properly with LGUP
3. Backup your sms, apps,contacts preferred way as the process will erase everything.
4. DirtySanta bootloader unlock/root method:
a. Install terminal emulator APK to phone , enable developer options by going to setting >about phone>Software info>Tap Build Number 7 times until confirmation. Back> Developers options> Enable OEM Unlock and USB Debugging.
b. Move platform-tool folder to your C directory
c. Connect phone through USB and allow USB debugging .
d. Double click RUNMEFIRST.bat, DO NOT CLOSE THE LOG WINDOW THAT OPENS, then double-click "Step1.bat"
e. Leave Step1.bat CMD window until shell prompt (about 40 seconds) then type:
i. run-as con
ii. chmod 0777 /storage/emulated/0/*
f. Terminal Emulator App on phone type:
i. id
- if it says context=u:r:untrusted_app you may proceed and type: applypatch /system/bin/atd /storage/emulated/0/dirtysanta
g. Watch the RUNMEFIRST dialog for when it tells you to run Step2 then double click Step2.bat
h. Once phone reboots to Fastboot mode, you can run Step3.bat.(MAKE SURE TWRP img file is in the same folder and not renamed)
i. If not you can access fastboot mode by taking out the battery, usb, re-insert battery (screen shouldn’t be on) , hold volume down while inserting usb c into the phone.)
i. Once Step3.bat finishes, you can enter TWRP by:
i. Take out battery for a few seconds
ii. Press and hold Volume Down, then press and hold power button for 2 seconds.
iii. When LG logo appears, let go only of the power button for half a seconds and repress and hold power button.
iv. When Factory Mode menu appears, let go of both buttons and select yes by volume key and confirm with power button.
v. Instead of factory resetting it will boot you into TWRP by welcoming you with a corrupt red triangle ,if step3.bat was successful
j. Once in TWRP, Press Cancel on the password prompt and then swipe to allow system modifications.
k. Make a backup with TWRP to your micro SD card, check everything except data.
l. Once Backup completes, return to main menu>wipe> format data >yes
i. Go to Wipe > Advanced > Check Dalvik, System, Data, Internal Storage and Cache > Slide to wipe [IF STOCK US996 DON’T WIPE INTERNAL STORAGE]
ii. Go back to Wipe > [Format Data] > Type ?Yes?
iii. Go back to Main menu > Install > Tilde88's US996 100% Stock deODEXEd Rom ZIP file
iv. Main menu > Install >SuperSU-v2.79-201612051815.zip
v. Go back to Main-menu > Reboot > System(you will get static on boot. this is normal and android reconfiguration will take around 15 minutes.)
vi. For Official US996 owners, you are done.
5. For H915 owners, after android finishes reloading, you will notice signal disabled.
i. Re-enable developer options, OEM unlock and USB Debugging.
ii. Power off the phone, remove then reinsert battery , hold the volume up button (screen should be off) then connect the USB C to enter download/firmware update mode. It's okay if there is static.
iii. Real-time protection off, LGUP installed, open Uppercut.exe as UAC then should recognize the phone as US996.
- If it doesn’t recognize the phone, go to C:\Program Files (x86)\LG Electronics\LGUP\model you can place the common folder I have uploaded.
-Battery remove, re-enter download update mode.
iv. Uppercut LGUP update not refurbished mode, for bin file you can either choose [US99610f] .DZ or .KDZ. Sometimes .DZ works better when model hopping,.
v. After updating, the "Get started page" crashes a lot. Now Factory restore it by using the Factory Restore mode. (Previously used to enter TWRP)
vi. This will fix the crashing and you should have a fully functional H915 converted to US996 with signal. [Unrooted State]
vii. Repeat Step 4 but when wiping, do not wipe internal storage.
viii. H915 Owners should have a fully rooted unlocked US996 with LTE connection.
Big Thanks to:
@autoprime
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
@bullghost
https://forum.xda-developers.com/showthread.php?t=2600575
@ahlok_hk
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
@TheDantee
https://forum.xda-developers.com/v20/development/h915-root-guide-restore-bricked-lg-v20-t3529649
@KedarWolf
https://forum.xda-developers.com/v20/how-to/v20-kdz-restore-failing-9-completing-fix-t3546817
@me2151
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
@jcadduono
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
@Tilde88
https://forum.xda-developers.com/v20/development/us996-100-stock-deodexd-rom-t3520131
@markbencze

Excellent and very detailed write up. Well done man!

Just to confirm, is this for the US Cellular version?

The H915 is Canadian but US996 is American. If you own a US996 you can follow steps 1-4 without wiping internal storage. Only H915 owners need to wipe internal storage at step 4 before the conversion and step 5.

I own the US Cellular version, which I thought I wouldn't be able to root. Thank you.

You made the google plus xda feed! Great job
https://plus.google.com/+xda/posts/EnWK7taUFaE

I followed these instructions but I made a mistake by not disabling secure startup and now I'm stuck. Could use anyone's help. I have the 996 variant and followed the instructions till the end of 4. When booting the deodexed rom it boot into the secure startup password screen. My old secure startup password no longer worked and so I just went through all 30 tries to let it wipe itself. It did however now system refuses to load and now just bootloops back into TWRP every time. I can access TWRP and Fastboot at the moment but nothing else. Thanks again for your help.

After some more forum reading, I found out I need to use the hardware buttons to get into TWRP instead of it automatically entering it. I was able to reflash the rom and it boots now however now I'm getting a white encryption unsuccessful screen. Can anyone point me in the right direction to fix this situation?
Edit: I got it working by formatting data in TWRP. I was able to successfully boot finally.

talltree said:
After some more forum reading, I found out I need to use the hardware buttons to get into TWRP instead of it automatically entering it. I was able to reflash the rom and it boots now however now I'm getting a white encryption unsuccessful screen. Can anyone point me in the right direction to fix this situation?
Edit: I got it working by formatting data in TWRP. I was able to successfully boot finally.
Click to expand...
Click to collapse
Sorry for the late reply, I'll upload a US996 stock boot.img with secureboot disabled, works well with the Weta ROM with magisk. Were you able to root it successfully?

Thanks for your help. I was able to get it to work! Formatting data did the trick to fix the encryption, just wiping it wasn't enough. Will the current instructions work with Weta ROM? I was considering trying it out. Also if I used LGUP with the US99610f kdz would that bring take it back being a locked bootloader and stock recovery incase I want to use the official LG bootloader unlocking method?

talltree said:
Thanks for your help. I was able to get it to work! Formatting data did the trick to fix the encryption, just wiping it wasn't enough. Will the current instructions work with Weta ROM? I was considering trying it out. Also if I used LGUP with the US99610f kdz would that bring take it back being a locked bootloader and stock recovery incase I want to use the official LG bootloader unlocking method?
Click to expand...
Click to collapse
Yes, as long as LGUP with or without uppercut recognizes your device as a us996. I'm currently using Weta , you should use the stock patched us99610f boot.img I uploaded in the zip.;

Thor_BR said:
I own the US Cellular version, which I thought I wouldn't be able to root. Thank you.
Click to expand...
Click to collapse
I would double check on this some how. I do believe that teh US Celluar, while also using the US996 model number, is in fact a different phone from the US Unlocked US996 phone.
I'm not sure how you'll know for sure if it'll work until someone tries it on a US Celluar model.

Has anyone successfully went back to full stock after using this method with the US996 unlocked model? I'm trying to debate on doing this or the official way.

jal3223 said:
Has anyone successfully went back to full stock after using this method with the US996 unlocked model? I'm trying to debate on doing this or the official way.
Click to expand...
Click to collapse
Well if you don't mind losing your warranty, you should do it the official way. But if you are unsure, you should try it this way but as of now theres a little static just when it boots up for 2-3 seconds.

FijNNY said:
Well if you don't mind losing your warranty, you should do it the official way. But if you are unsure, you should try it this way but as of now theres a little static just when it boots up for 2-3 seconds.
Click to expand...
Click to collapse
Thanks for the reply. I don't mind a little static, especially if that's all that is wrong with doing the process.
I guess my question should have been is there even a way to go back to stock if needed? I have heard other variants saying that there are no stock files available anyways for them. So I was just going to check before making compromises. Thanks again.

jal3223 said:
Thanks for the reply. I don't mind a little static, especially if that's all that is wrong with doing the process.
I guess my question should have been is there even a way to go back to stock if needed? I have heard other variants saying that there are no stock files available anyways for them. So I was just going to check before making compromises. Thanks again.
Click to expand...
Click to collapse
Yes you can go back to US996 stock. If you download the package I zipped, it will give you all the tools necessary. The kdz download location is listed also. Maybe take an hour to download.

FijNNY said:
Yes you can go back to US996 stock. If you download the package I zipped, it will give you all the tools necessary. The kdz download location is listed also. Maybe take an hour to download.
Click to expand...
Click to collapse
Awesome! Thanks for the help.

Guys, could use some help here..I have a US996, using the latest WETA. It is rooted using DirtElf method . On this afternoon, was trying to install a new kernel. The back cover was out and, by mistake, the battery slipped went out while I was on AROMA to do the flashing, but without any actual flashing going on, only on the inicial dialog. I inserted battery, and the phone booted system and behaved normally. After that, I tried to boot in recovery to finish the process. Then, the screen went static as in the first boot, non responsive. Only it stays this way. Even pulling out the battery doesn't change it, phone boots up to the same state. The only thing I can acess is fastboot mode. Tried to flash TWRP again this way, but no sucess. Any advices? Thanks a lot!

https://forum.xda-developers.com/v20/how-to/h915-lg-vtrvideotron-rooted-unlocked-t3576637

empat said:
Guys, could use some help here..I have a US996, using the latest WETA. It is rooted using DirtElf method . On this afternoon, was trying to install a new kernel. The back cover was out and, by mistake, the battery slipped went out while I was on AROMA to do the flashing, but without any actual flashing going on, only on the inicial dialog. I inserted battery, and the phone booted system and behaved normally. After that, I tried to boot in recovery to finish the process. Then, the screen went static as in the first boot, non responsive. Only it stays this way. Even pulling out the battery doesn't change it, phone boots up to the same state. The only thing I can acess is fastboot mode. Tried to flash TWRP again this way, but no sucess. Any advices? Thanks a lot!
Click to expand...
Click to collapse
You do have access to firmware update mode right? If you do, open up lgup through uppercut.exe then try to restore it back to stock with the us99610f kdz file. All the files should be posted above. If that works, you need to root it again. Good luck!

[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]

Good day,
Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation.
Before you begin:​(Your phone's internal storage will be wiped or simply formatted or more simply erased)
(You will observe a static boot screen on each boot on some variants)
(These instructions are specifically done using root package 4.0. Some steps will be different if you use other version)
Read this carefully and completely. In this tutorial, I will show you how to root your LG V20 using DirtySanta method.This method is currently working for devices mentioned below in working device headings. So, you are warned not to try this on any other device (or not mentioned device) because this might brick your device. If you're on stock rom with Google's security patch of January 2017 or later then you need to flash a firmware with December 2016 or earlier security patch. This method flashes a debug bootloader, So, if you try to re-lock your bootloader it will brick your device.*
And most important before beginning, read 4th post carefully.
Currently, LS997 (Sprint Variant) cannot return to stock because there is no KDZ available for these devices (they mostly don't release TOT, KDZ).
For H910:
If your phone is on non-rootable firmware you can cross flash a H915 or US995 kdz with December 2016 patch by using Patched LGUP and then proceed to root.
If you are faced any problem you can ask help, I will try my best to help but can't promise and blamed if your device is bricked. Always process is root only if you have enough patience and experience to deal with brick and bring phones back to life.
Working Devices:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915) --> Follow this Method (Specially for H915)
again don't try on others you may face a brick. But if you're so desperate to try it on others devices then tell me your experiences.. DO NOT TRY THIS ON ANY OTHER VARIANT, YOUR PHONE WILL BRICK (INCLUDING BUT NO LIMITED TO H918)
Required Things:​All things that you require for this process can be found in 2nd post.
Preparation:
1: Download files from download section. (Always download latest root package)
2: Install Terminal Emulator on your phone.
3: Extract root package.
4: Install “ADB” through “ADBSteup.exe” from Software Folder
Optional Either copy root zip (SuperSU or MAGISK) to external Sdcard (memory card) or wait till process to end so you can copy it after formatting internal storage from TWRP
6: LG Driver can be found in Software folder of root package (Install it, if not installed already)
Steps:
Bootloader Unlocking:​1: Navigate to extracted Root Toolkit
2: Run "JustRunMe.cmd".
3: Enter "1" to begin process and follow on-screen information. All steps will start automatically one-by-one.
4: When prompted open terminal emulator and perform following commands. (Commands are also described in respective scripts).
Code:
id
check it output if it says ”Context = untrusted_app”. If it say so then you're fine to go to next step or you will have to began from step 1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
5: Now bring Logcat window to front and wait till it says you to start step 2.
Press any key on main "JustRunme.cmd" and it will start 2nd step automatically.
it will boot your device into bootloader after success.
When done, step2 window will close automatically. Press any key on main window to begin 3rd step.
It will flash TWRP on your device. Your phone will reboot and boot into system after some time. If it takes more than 15 minutes or your kept seeing static window then reboot back into fastboot mode.
To boot into fastboot (or bootloader) mode simply turn off phone by taking battery out then press volume down and plug-in USB cable while holding the button.
Flash Boot2 image by entering “2” then “1” from JustRunMe window. (Different for root package 6.0)
It will reboot and phone should boot now.
(If you're faced with any secure boot password then you will have to format data within TWRP. Just power-off your device and boot into TWRP)
Rooting, Removal of Encryption, Installation of SuperSU or Magisk:
​8: Now boot into recovery mode either by entering “5” then “1” or by key method,
Cancel password prompt.
To Remove Encryption Error (It'll wipe all your internal data)
9: On TWRP. Swipe to allow modification.
Click → Wipe → Format Data → type “yes” → enter.
Now you will have access to internal storage from TWRP. Connect your phone to PC with USB cable while in TWRP.
10: Now copy your Supersu or Magisk to phone (Whatever you prefer).
11: Flash this zip by
Press → Install → (Select copied zip) → swipe to flash and wait till it is finished.
12: If you're faced with any secure boot password then you will have to format data again by
Boot into TWRP –> Wipe → Format Data → yes → enter
after that
Press → Wipe → check Cache, Dalvik Cache, Data → Swipe.
Press → Home → Reboot → System.

Download Links:
1: LG V20 Root Package
Old iterations
LG V20 Root Package Here
LG V20 Root Package 3.0 Here
Current iterations:
a: LG V20 Root Package 4.0 Drive | DropBox
b: LG V20 Root Package 6.0 Drive | Mega
2: Terminal Emulator PlayStore or Mirror
3: LG Drivers Here (No need to download from here. From Root Package 4.0, driver can be found in Software folder of extracted files)
OPTIONAL FILES​Patched LGUP (If you want to cross flash firmwares. Use with extreme cautions and don't blame anyone if you hard brick the device)
extract it to "C:\Program Files (x86)\LG Electronics\LGUP" (different for 32-bit windows)
Rootable Firmware
US996 10f KDZ (rootable) (Flash it through Patched LGUP on H910 if your current firmware is not rootable, as no kdz is available for H910 by carrier)
US 996 KDZ
LG US996 KDZ all Available versions

FAQ​
Will this work on the lg v20 H918 10q and up?
Well, Short answer = No.
Long Answer = This guide is just beginner friendly. Which means that It is just more easier version of dirtysanta with FAQ, Video Tutorial (probably) and less anxiety. The reason behind creating this is simply to help new V20 user root and install TWRP more easily. This is no upgrade to method. It is just a modification. It will do only what @me2151's method can do.
Is there any way to revert my phone to a the version before att security patch. I am not super tech savvy so I wouldn't know where to start. I am very frustrated
I did it by flashing a H915 kdz on H910 which had December 16 security patch. After that phone had TWRP by this method. You can try flashing either an H915 or US996 firmware with December 2016 or earlier security patch. US996 10f kdz link is given in 2nd post which is rootable. You can try with that if you have H910 phone.
Here's the link for that tutorial to cross-flash a kdz rom on H910 using patched LGUP. (You can give a try to other variants but H918 which is highly brickable)
Here or Here
How do I find out if my firmware is rootable?
If security patch of your phone says it's December 2016 or earlier then it is rootable using dirtysanta method.
Does that mean I can flash h915 or US996 firmware on h910 even without rooting the device?
I have H910. I can confirm directly flashing H915 and US996 kdz directly using patched LGUP (in 2nd post attachments).
If yes, are there any software requirements/restrictions (be it the AT&T firmware version required, or the h915/US996 kdz I can install - eg. only install version XYZ of h915/US996 firmware if at&t firmware is before/after a certain version)?
Currently there are no software restriction. By flashing firmware from US996 or h915 firmware you can get rid of ATT bloatware and WiFi Hotspot will work without any further enhancements. If you want to root your non-rootable firmware (H910 with firmware along January 2017 or later security patch) then try flashing an US996 firmware with December 2016 (or earlier) security patch to root.
I had the latest US996 firmware (10p) installed, and it worked but I had signals problems (once 4G enabled, connection dropped randomly).
I then tried to flash h915 10e firmware, and I'm now stuck in a bootloop. I tried re-flashing the US996 firmware that worked before, but it no longer works. The phone is still detected as US996 in LGUP (even if I flash h915 firmware).
Try doing a factory reset using button method (The same used to enter TWRP).
This procedure just completely bricked my H918. Everything went perfect until step 2 finished - and then instead of rebooting to bootloader, it simply died/crashed. Now it won't respond in any way whatsoever. I have no download mode, no fastboot - the thing won't even charge. Was on 10d. So that's cool
That's really sad situation.
(No where in the OP does it say that this works on the H918 therefore you bricked your phone.)

Disclaimer
As always, this method is simplified to work more easily. It does have risks same as other rooting method (even more). There might be many problems, if you don't read thread carefully. I will try my best to assist you for any issue but still there are things about which I can't help. There can be situations which needs to be handled with patience. So, I'm not responsible for bricked, faulty or non-operational devices. SDcard not working is not my concern. Any other problem/situations that you faced after following this guide or before following it is not my problem. If you have enough patience, reading ability and the talent of asking questions with more details, and love, then you're always welcome to try, ask and share your experience. Always read FAQ first because most of your questions might be answered there. Searching thread for your issues is best as someone already may have faced and fixed that problem before you. Again Me and @me2151 or any other person isn't responsible for bad outcomes, even your friend who is doing you a favor by rooting your device for you (for free) as you are afraid or not experienced.
Anyways, have happy rooting.
Credits:
I am not author or developer of this method. A very talented XDA member @me2151 found this method. I am just writing it here. All credit goes to him and his fellows. So, if you want to donate and say thanks then he and his fellows deserve it.

Video Tutorial

will this work on the lg v20 H918 10q and up?

dudeawsome said:
will this work on the lg v20 H918 10q and up?
Click to expand...
Click to collapse
Well, Short answer = No.
Long Answer = This guide is just beginner friendly. Which means that I is just a more easy version of dirtysanta with FAQ, Video Tutorial (probably) and less anxiety. The reason behind creating this is simply to help new V20 user root and install TWRP more easily. This is no upgrade to method. It is just a modification. It will do only what @me2151's method can do.
(Let me add this to FAQ)

dksoni411 said:
Well, Short answer = No.
Long Answer = This guide is just beginner friendly. Which means that I is just a more easy version of dirtysanta with FAQ, Video Tutorial (probably) and less anxiety. The reason behind creating this is simply to help new V20 user root and install TWRP more easily. This is no upgrade to method. It is just a modification. It will do only what @me2151's method can do.
(Let me add this to FAQ)
Click to expand...
Click to collapse
ahh okay

phone gives that red hazard symbol (debug bootloader thing) and then boots into twrp every time i restart the phone. What should I do now? I want to install alpha rom. I apologize I guess I'm even worse than noob x(

Hi i would just like to verify my understanding of your first post .
my phone is h915 with firmware 10a (h91510a) has security patch feburary 1 2017
This Dirtysanta method will not work anymore because it is after january 2017 is that correct .
Thank you

I have an lg-ls997 and i can't get the applypatch command to work when i enter it all i get is what i think is a usage error reply any idea what i am doing wrong? Also forgive my noobness also what is the [/strike] thing? any help would be awesome as i have been banging my head against the wall trying to root this phone for months. couldn't do it the factory way because no matter what i do i can't get it into fastboot to get the device id it always just boots back to system no matter what adb reboot command i use. so this is kind of my last hope.

atomikkid said:
I have an lg-ls997 and i can't get the applypatch command to work when i enter it all i get is what i think is a usage error reply any idea what i am doing wrong? Also forgive my noobness also what is the [/strike] thing? any help would be awesome as i have been banging my head against the wall trying to root this phone for months. couldn't do it the factory way because no matter what i do i can't get it into fastboot to get the device id it always just boots back to system no matter what adb reboot command i use. so this is kind of my last hope.
Click to expand...
Click to collapse
Have you typed commands in terminal emulator correctly.
Is USB debugging on and computer set as always allowed.
Is context being shown as untrusted_app when you typed id in terminal emulator.
Check your anti-virus is disabled.
Make sure ditrycow and dirtysanta exist in extracted folder

H990ds
will this work on H990ds model? I saw the other posts that dirtysanta root works on this model too. I tried and the root processes were successful but the screen was showing white patches(like a hardware failure!!) I reverted back.

Your warning about the H910 and LS997 not being able to return to stock is no longer correct. While it is correct that they don't have KDZs, there are TWRP flashable zips that will return them to stock.
-- Brian

runningnak3d said:
Your warning about the H910 and LS997 not being able to return to stock is no longer correct. While it is correct that they don't have KDZs, there are TWRP flashable zips that will return them to stock.
-- Brian
Click to expand...
Click to collapse
Oops. I saw some flash-able zip but I thought even if your flash stock rom through TWRP, you can't get full stock. With full stock, I meant stock (locked) bootloader and stock recovery with no modification. If full stock is possible then please let me know, I would love to learn how to return back to full stock on H910 (and might write a guide for others)

can i root h91010m with this method ?

Is this working on v20 h910pr claro ??

Can you root F800L if you on April 2017 security patch and F800L10y? Also, If not can I downgrade?

Just bought this phone with a security patch of October 2017 (Verizon variant). So outside of Dirty Santa there is no way to root or unlock Bootloader??

Downgrade with LGUP
Download .kdz firmware file of any <=December 2016 security update & downgrade to it using LGUP.

[Root] [guide] Samsung Galaxy A20 rooting guide

Read the first 3 posts before you proceed.
For Android 10 go here
https://forum.xda-developers.com/galaxy-a20/how-to/android-10-q-guide-a20-t4095589
For a20e go here
A20e Root,Kernel, TWRP and custom ROM
Root & TWRP from Xyn XDotnest https://forum.xda-developers.com/galaxy-a20/development/recovery-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767 Orange Fox Recovery from @Royna...
forum.xda-developers.com
WARNING: Rooting your phone may be dangerous.
Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing!

Advantages of rooting:
Once you root your device you can install flashable zip files and custom ROMs.
You can backup all your apps and data using Titanium Backup.
You can customize your device according to your needs by deleting unwanted system apps and using Deathly Adiutor to modify the kernel.
View attachment 4802662
Disadvantages of Rooting:
Once you root your device, your device warranty will be void.
After rooting yourndevice may become unstable.
You may not be able to upgrade OTA in the future.

This method should root your Samsung Galaxy SM-A205X (all models except SM-A205U and SM-A205DL).
It was developed for the U2 bootloader (June 2019 firmware)
This method does not work for the a20s (A207X)
This method can be used to root other Samsung phones including the a20e( post#77 post#180, post#256)
Quick Root and TWRP for A205xx
https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
You'll find it much quicker.
Repair Firmware
This site contains
1. Full repair firmware
2. Combination firmware
3. Fix dm verify
4. Root instructions and unpatched boot images
https://www.full-repair-firmware.com/search?q=A20
More firmware (some are even prerooted)
https://www.needromarab.com/1/122/SAMSUNG
Samfirm Tool for really fast downloads
https://samfirmtool.com/samfirm-v0-5-0

Useful videos
Instructions
A. Prepare boot image
1. Download magisk manager apk
2. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
https://samfw.com/
3. Use zarchiver to copy AP_20xxxxxxxx.md5 to download directory. It will extract it from the zip.
4. Rename AP_20xxxxxxxx.md5 to AP_20xxxxxxx.tar and extract using zarchiver
5. Copy boot.img.Iz4 to download directory and extract (resulting in boot.img)
6. Use magisk manager to patch boot.img (use top install) result magisk_patched.img
(If using Magisk (Canary) patch, options should be remove dm-verity and not via recovery, but allowing Persist Encrypt.)
7. Rename magisk_patched.img to boot.img
9. Use zarchiver to compress boot.img to boot.tar. If you have a A205xx June firmware (U2 bootloader), you can use my one of you're willing to take a risk. View attachment boot.zip. Just unzip it first.
9a. For a20e users, try this boot.img https://forum.xda-developers.com/showpost.php?p=81649257&postcount=260
10. Copy boot.tar to Windows pc or Windows Virtualbox.
11. On phone developer options in settings unlock OEM and enable usb debugging
(If using Linux
9. Don't compress `boot.img`
10. install heimdall flash with `sudo apt install heimdall-flash`, if you want front-end install it with `sudo apt install heimdall-flash-frontend`)
B. Unlock bootloader
Useful video
12. Backup data. It will be wiped.
13. Turn phone off
14. Hold vol- and vol+ and plug in power cable attached to pc then release vol up to enter unlock screen.
15. Follow the instructions to unlock
(You might need to long press vol up to unlock bootloader)
vol + to select yes to confirm.
17. Press power key to unlock bootloader.
18. Reboot and reactivate developer options and enable usb debugging. Don't enter too much data at this stage as you will lose it again later.
C. Flash boot image.
19. Turn phone on in bootloader (download) mode (Hold power and vol+ to enter recovery mode then select bootloader download mode)
20. Connect phone to computer.
21. Use Odin in Windows to add boot.tar to phone. (Select AP). Some people recommend adding the other firmware parts to their slots at the same time.
22. Restart phone
23. select bootloader
24. Select factory reset (this will wipe data)
25. Restart phone
26. install data
26. install magisk manager
27. If green phone is rooted.
View attachment 4802665
28. Of red select install/direct install
29. Advanced tick both.
30. Install root checker and verify root
If Something Goes Wrong
Go here
https://forum.xda-developers.com/galaxy-a20/how-to/crash-recovery-t4068369
If you get a DTBO error after updating Magisk, flash this vbmeta https://drive.google.com/file/d/1-dogButfxKGlx_x2tSROOBDiq90SDlmc/view
(If using Linux
To flash:
20. Detect device with `heimdall detect`
21. Flash the `boot.img` with `heimdall flash --BOOT {location of the boot.img, you can also just drop the file into terminal and terminal should auto-fill it}` ex: `heimdall flash --BOOT '/home/utku/Programlar/ext/boot.img'`
P.S: an easy way to boot into download mode is `adb reboot bootloader`)
If you want to remove the warning messages on the boot screen
try this.
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
The images shown on the A30 thread aren't suitable for the A20 so I have included some better ones here.
View attachment 4803752
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can use this param.tar to make these changes easier.
https://forum.xda-developers.com/showpost.php?p=80169262&postcount=91
You can now move on to install TWRP
This TWRP was originally designed for Android 9 but works perfectly with Android 10 and also has MTP built-in.
https://forum.xda-developers.com/ga...overy-twrp-3-3-1-0-galaxy-a10-exynos-t4013481
physwizz collection
A collection of guides, kernels and ROMs. Guides Complete Guide to the A20 GSIs for the A20 Quick Root and TWRP for the A20 Making my First Kernel for the A20 A20 Rooting Guide Making Your Own ROM Making Your Own Version of QwizzROM-a20...
forum.xda-developers.com

Mine
Discussion page.
https://forum.xda-developers.com/t/samsung-galaxy-a20

On the lighter side of rooting....
From the A30 forum:
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
Works for A20 too

jajk said:
On the lighter side of rooting....
From the A30 forum:
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
Works for A20 too
Click to expand...
Click to collapse
Another reason to merge. This is a procedure for removing those annoying error messages on startup screens.

A205U owners complaining about not being able to oem unlock bootloader might want to study this:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
It looks like a way to switch to another unlockable firmware version.

Please, need magisk_patched.img file for SM-A205F.

jajk said:
A205U owners complaining about not being able to oem unlock bootloader might want to study this:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
It looks like a way to switch to another unlockable firmware version.
Click to expand...
Click to collapse
Yeah tried that option. Samsung has our model on a bootloader 2, means our device won't accept flashing from any other firmware but the original non-modded firmware only.
Tried prince Odin,patched Odin all versions, tried Heimdall etc..
Error is ...boot secure check failed..
I've tried to flash firmware a205G only with fail error Everytime.
Psa I've had my a205u for 10 days no OEM unlock option.
Main reason why I'm not buying another Samsung phone.
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .

jhjhjhjhjhjh said:
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^THIS ALL DAY. I swapped mine out for the G7 Power and already done rooted, flashed, and wrote a guide while all the 205u users are waiting for the mythical OEM Unlock to magically appear which it ain't gonna. Sammy can kiss my techie ass...we are officially divorced. I won't even go back and buy an old Sammy like I wanted to (was thinking about getting that S7 edge). It's me and Moto for now.

jhjhjhjhjhjh said:
Yeah tried that option. Samsung has our model on a bootloader 2, means our device won't accept flashing from any other firmware but the original non-modded firmware only.
Tried prince Odin,patched Odin all versions, tried Heimdall etc..
Error is ...boot secure check failed..
I've tried to flash firmware a205G only with fail error Everytime.
Psa I've had my a205u for 10 days no OEM unlock option.
Main reason why I'm not buying another Samsung phone.
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
Click to expand...
Click to collapse
Maybe Samsung has an issue with US tariffs.

Samsung have certainly turned an essentially good piece of hardware into a pile of rubbish with mega-invasive bloatware. I have barely started to strip back the garbage and the phone is springing to life. Need a working TWRP before getting too keen as the path back to functionality is long and arduous without a way of restoring partitions if anything gets screwed up. Here is what the phone looks like with Google Play junk removed plus a bit of Samsung bloat removed - not everyone is ready to kick the Alphabet addiction I know, but it has become an absolute monster that eats battery and cpu cycles....apart from the privacy invasion side of it
I am finding that many unknown, non-visible apps with innocent sounding names or "security" inferred in the name are likely to be ad server or data mining software - I got wise to this with my first and last Xiaomi device

jajk said:
Samsung have certainly turned an essentially good piece of hardware into a pile of rubbish with mega-invasive bloatware. I have barely started to strip back the garbage and the phone is springing to life. Need a working TWRP before getting too keen as the path back to functionality is long and arduous without a way of restoring partitions if anything gets screwed up. Here is what the phone looks like with Google Play junk removed plus a bit of Samsung bloat removed - not everyone is ready to kick the Alphabet addiction I know, but it has become an absolute monster that eats battery and cpu cycles....apart from the privacy invasion side of it
I am finding that many unknown, non-visible apps with innocent sounding names or "security" inferred in the name are likely to be ad server or data mining software - I got wise to this with my first and last Xiaomi device
Click to expand...
Click to collapse
I used titanium backup first. Now I'll debloat.

physwizz said:
Maybe Samsung has an issue with US tariffs.
Click to expand...
Click to collapse
The US doesn't have an issue with South Korea on tariffs, despite Trump's big mouth.
The problem is that Sammy wants to be essentially Apple Android. And that is what's driving this crap in the same of "security". Knox has been like the devil and even sentient since it came to power almost like Skynet. And all of this started when Verizon offered Sammy big bucks to lock it down ala Kyocera with the S5 era - which coincidentially is the last great breath of air they had to give.
They don't care about the developer models either - look in the forums, many of them are just as locked down.
Sammy knows ain't that many phone companies left in the US; Tmobile done bought out half the cell companies and AT&T got the other half in a duopoly, meaning they and other companies can continue this path of nanny phones on the general public that are going for more personalized computers they can't control than actual phones that work. Most Americans aren't going to turn to GooPhone nor will many XDA devs develop any type of TWRP or rom for those types. And that means they can dangle a bells and whistle carrot while their demographic signs their privacy away.
I ain't a fan of Lenovo-Moto, but at least they let half the phone companies unlock the variant to their devices. Sammy, on the other hand, does not and is playing Xiaomi type of games on that bootloader.

Articul8Madness said:
The US doesn't have an issue with South Korea on tariffs, despite Trump's big mouth.
The problem is that Sammy wants to be essentially Apple Android. And that is what's driving this crap in the same of "security". Knox has been like the devil and even sentient since it came to power almost like Skynet. And all of this started when Verizon offered Sammy big bucks to lock it down ala Kyocera with the S5 era - which coincidentially is the last great breath of air they had to give.
They don't care about the developer models either - look in the forums, many of them are just as locked down.
Sammy knows ain't that many phone companies left in the US; Tmobile done bought out half the cell companies and AT&T got the other half in a duopoly, meaning they and other companies can continue this path of nanny phones on the general public that are going for more personalized computers they can't control than actual phones that work. Most Americans aren't going to turn to GooPhone nor will many XDA devs develop any type of TWRP or rom for those types. And that means they can dangle a bells and whistle carrot while their demographic signs their privacy away.
I ain't a fan of Lenovo-Moto, but at least they let half the phone companies unlock the variant to their devices. Sammy, on the other hand, does not and is playing Xiaomi type of games on that bootloader.
Click to expand...
Click to collapse
I find it strange that the US version is the only one that can't unlock the bootloader.
The rest of us are all unlocked and rooted.

physwizz said:
I find it strange that the US version is the only one that can't unlock the bootloader.
The rest of us are all unlocked and rooted.
Click to expand...
Click to collapse
It aint strange, its common. Before it was locked exclusively to Verizon; after the S3 it became more and more carriers. Then the dev models started being locked up but "open".

Articul8Madness said:
It aint strange, its common. Before it was locked exclusively to Verizon; after the S3 it became more and more carriers. Then the dev models started being locked up but "open".
Click to expand...
Click to collapse
Mine is locked to Vodafone but I can still unlock the bootloader.

physwizz said:
Mine is locked to Vodafone but I can still unlock the bootloader.
Click to expand...
Click to collapse
Same here.
Did you mod your param.tar (to change the warnings at startup) file by any chance? Would you be able to attach it at all? I was gonna download the firmware but it's taking 9 hours.
Thanks.

burningcreation said:
Same here.
Did you mod your param.tar (to change the warnings at startup) file by any chance? Would you be able to attach it at all? I was gonna download the firmware but it's taking 9 hours.
Thanks.
Click to expand...
Click to collapse
I've downloaded the 2 pics and I modified one to contain my name.
I will try the mods shortly.

How To Guide How To: Root Galaxy A12 | SM-A125F/DSN

This is the Method how i Root my Galaxy A12 .
This method is very easy if you take your time. THIS WILL ALSO WIPE YOUR DEVICE. I AM NOT RESPONSIBLE FOR ANY DEVICE OR SD CARD DAMAGE.
BEFORE PROCEEDING, UNLOCK BOOTLOADER.
YOU CAN FIND THE FIRMWARE YOU NEED ON SAMMOBILE.
1. Download the firmware for your device.
2. Load Zarchiver from playstore.
3. Open Zarchiver and locate the firmware you downloaded.
4. Click on the firmware, a menu will appear at the bottom. You will then have option to extract.
5. Extract the firmware and you will have files..AP..BL..CP..CSC..and HOME_CSC. The only file we need is AP
6. Click on AP file and rename AP_A125FXX.md5 to AP_A125FXX.tar - so your just highlighting the file and removing md5 so it only says .tar at the end.
7. Once you have renamed AP file click and again you will be given the option to extract. Once extracted, locate boot.img.lz4
8. Then extract boot.img.lz4 leaving you with boot.img
9. You should have Magisk manager installed on device. Use Magisk to patch the boot.img. once patched locate magisk_patched.img and rename to boot.img
10. Return to Zarchiver locate the patched boot.img and compress to boot.tar.
11. Move compressed boot.tar to computer and rename to boot.img.tar
12. Put device in download mode, open Odin and put the boot.img.tar in AP and click start. Once odin says pass, your device will boot to stock recovery and you will have to do a factory reset so save anything you need before doing this.
13. Once Device boots - RE-install Magisk Manager and follow prompts.
Congatulations, Youre Rooted Now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It worked! Thank you so much for this tutorial!

Will This Affect OTA Updates (Will OTA Functionality Work After Root) And Will OTA Updates Unroot My Phone

cldkrs said:
BEFORE PROCEEDING, UNLOCK BOOTLOADER
Click to expand...
Click to collapse
can you please give a walk through on this , just starting out and need some help

cl3vin said:
can you please give a walk through on this , just starting out and need some help
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/how-to-unlock-bootloader.4244757/

But, does only flashing TWRP instead just need an OEM bootloader unlock, and doesn’t need to follow those above firmware steps like rooting on a stock ROM?

Just rooted my phone yesterday, by the way Safety net fails the basic integrity test, i guess there's no way to circumvent this since this device uses Hardware Backed attestation to detect an unlocked bootloader.

28.3.2021: Download of patched boot.img.tar failed with error:
SW REV CHECK FAIL : [boot]Fused 1 > Binary
Only official released binaries are allowed to be flashed : boot
KG STATUS : PRENORMAL was the culprit. For naive users inexperienced with Samsung devices like myself might be usefull to have warning in the rooting guide to avoid PRENORMAL state and link to instructions how to do it.
Update 8.4.2021: To get rid of PRENORMAL state is enough to wait for a week with sim, active data connection and maybe also logged into google account. Do not reboot or disconnect network during wait time. Check the OEM ulocking state in developer settings time to time (to trigger status verification on Samsung servers).
Flashing unofficial binary succeeded afterwards.
Sources:
https://milankragujevic.com/how-to-avoid-rmm-state-prenormal-when-unlocking-samsung-phones
https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/

After using Odin to flash a Magisk modified version of boot.img.lz4, my smartphone stayed in a boot loop. After flashing the unmodified version of boot.img.lz4 (uncompressed and tarred) I could boot again and I could also turn of OEM Unlocking in the development options. So I returned the Smartphone to the seller, giving the true reason.

Hi, where I can found the firmware for my Galaxy A12 (SM-A125F/DSN) for the root?

forumarbeit said:
Hi, where I can found the firmware for my Galaxy A12 (SM-A125F/DSN) for the root?
Click to expand...
Click to collapse
You can download it on SamMobile

forumarbeit said:
Hi, where I can found the firmware for my Galaxy A12 (SM-A125F/DSN) for the root?
Click to expand...
Click to collapse
cldkrs said:
[...]
YOU CAN FIND THE FIRMWARE YOU NEED ON SAMMOBILE.
[...]]
Click to expand...
Click to collapse
Download Samsung Galaxy A12 SM-A125F firmware
Download the latest Samsung firmware for Galaxy A12 with model code SM-A125F. Check out our free download or super fast premium options.
www.sammobile.com

Thanks @jkaltes, I download the firmware from sammobile.
After install is then an new OS on my rooted mobile phone or stays the same original OS only with root rights?
How can I unlock the bootloader?
cldkrs said:
BEFORE PROCEEDING, UNLOCK BOOTLOADER.
Click to expand...
Click to collapse
thanks for your feedback.

Ive tried searching for my firmware on sammobile however im not finding it. Its model sm-a125u doesnt even show up on their list.

fixapixa said:
Update 8.4.2021: To get rid of PRENORMAL state is enough to wait for a week with sim, active data connection and maybe also logged into google account. Do not reboot or disconnect network during wait time. Check the OEM ulocking state in developer settings time to time (to trigger status verification on Samsung servers).
Flashing unofficial binary succeeded afterwards.
Sources:
https://milankragujevic.com/how-to-avoid-rmm-state-prenormal-when-unlocking-samsung-phones
https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
Click to expand...
Click to collapse
IF I get one of these things - I'm understanding (?) though we can get root - in order to keep root, one has to have a google acct?
2nd Q? is after the "wait to clear PRENORMAL" can the google acct be removed?
3rd Q? Can the phone be set up using WiFi (before buying a SIM) (?) then after the wait, put the SIM in? (reason I've asked is my carrier SIM "does ****" ...)
4th Q? Does the device need to be CARRIER unlocked to UL bootloader -- otherwise, I should buy a fully unlocked one, right?
Thanks in advance
VW

1) I guess it's not necessary to keep google account. Haven't confirmed myself however.
2) After unlocking the bootloader you should restart to system, connect to network and let the device verify status with Samsung servers. This way you avoid PRENORMAL status (without waiting) and will be allowed to flash patched AP. After the flash your device will be wiped so any existing google account is deleted anyway but after first boot into system you have to connect to network once again else device gets locked and you can start over. After your device succesfully synchronises itself with Samsung servers, you can disconnect from network and I don't see reason why you would need to have Google account if you don't want one.
3) You'll have to find out yourself. Personally I think that if you follow process from 2), wifi might be enough and no Google account would be needed at all but I cannot confirm that. In worse case if anonymity is paramount for you, just plug in some cheap prepaid SIM if such things are still availabe in your country and throw it away afterwards.
4) By carrier do you mean AT&T, Vodafone and such? No idea about your provider. Devices from open market are unlockable for sure but try to search the forum whether anybody encountered trouble with your provider.
As I wrote before, I have no previous experience with Samsung so I followed linked instructions and didn't experiment. If you want to help others, try to find out yourself and don't forget to report your findings here

fixapixa said:
..... if anonymity is paramount for you, just plug in some cheap prepaid SIM if such things are still availabe in your country and throw it away afterwards.
4) By carrier do you mean AT&T,
Click to expand...
Click to collapse
Thanks so much - Yeah, I'm that "anonymity paramount" user... Replacing a Blackberry Passport only because of that diabolical VoLTE...
Carrier = MetroPCS-T-Mobile
HOPEFULLY I'll be back with MetroPCS (runs on T-Mobile towers) by this time tomorrow ... If they'll re-activate the Passport. I've got a fallback android if that fails, but...
They might refuse the devices I have, and the A21 seems the best option in my price range, Rather than suffer from "bought in Store" sabotaged unit, I'll get one FACTORY unlocked.
US Carriers have gotten pretty evil, I've suddenly learned "Better the Devil you KNOW than meet a new one"
Thanks again for the feedback - VW

fixapixa said:
28.3.2021: Download of patched boot.img.tar failed with error:
SW REV CHECK FAIL : [boot]Fused 1 > Binary
Only official released binaries are allowed to be flashed : boot
KG STATUS : PRENORMAL was the culprit. For naive users inexperienced with Samsung devices like myself might be usefull to have warning in the rooting guide to avoid PRENORMAL state and link to instructions how to do it.
Update 8.4.2021: To get rid of PRENORMAL state is enough to wait for a week with sim, active data connection and maybe also logged into google account. Do not reboot or disconnect network during wait time. Check the OEM ulocking state in developer settings time to time (to trigger status verification on Samsung servers).
Flashing unofficial binary succeeded afterwards.
Sources:
https://milankragujevic.com/how-to-avoid-rmm-state-prenormal-when-unlocking-samsung-phones
https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
Click to expand...
Click to collapse
I am on samsung a10, I cant unlock my bootloader as my kg status is PRENORMAL. I have waited more than 168 hours for the oem unlock option to appar however nothing happend. I found that to unlock the bootloader I need to have my kg state to be normal. I have no idea what to do, i have tried reflashing may times, did all the updates and still nothing. Is there absolutely any hope?

cldkrs said:
This is the Method how i Root my Galaxy A12 .
This method is very easy if you take your time. THIS WILL ALSO WIPE YOUR DEVICE. I AM NOT RESPONSIBLE FOR ANY DEVICE OR SD CARD DAMAGE.
BEFORE PROCEEDING, UNLOCK BOOTLOADER.
YOU CAN FIND THE FIRMWARE YOU NEED ON SAMMOBILE.
1. Download the firmware for your device.
2. Load Zarchiver from playstore.
3. Open Zarchiver and locate the firmware you downloaded.
4. Click on the firmware, a menu will appear at the bottom. You will then have option to extract.
5. Extract the firmware and you will have files..AP..BL..CP..CSC..and HOME_CSC. The only file we need is AP
6. Click on AP file and rename AP_A125FXX.md5 to AP_A125FXX.tar - so your just highlighting the file and removing md5 so it only says .tar at the end.
7. Once you have renamed AP file click and again you will be given the option to extract. Once extracted, locate boot.img.lz4
8. Then extract boot.img.lz4 leaving you with boot.img
9. You should have Magisk manager installed on device. Use Magisk to patch the boot.img. once patched locate magisk_patched.img and rename to boot.img
10. Return to Zarchiver locate the patched boot.img and compress to boot.tar.
11. Move compressed boot.tar to computer and rename to boot.img.tar
12. Put device in download mode, open Odin and put the boot.img.tar in AP and click start. Once odin says pass, your device will boot to stock recovery and you will have to do a factory reset so save anything you need before doing this.
13. Once Device boots - RE-install Magisk Manager and follow prompts.
Congatulations, Youre Rooted Now.
View attachment 5244935
Click to expand...
Click to collapse
i flow this setup bue i can root heeeeeeeellp i need open bootloder ??

Just to elaborate on the Bootloader unlocking.
You will always need to connect to the internet, either wifi or sim card data.
Open Developer Options, Enable OEM unlock. (without internet, this option won't appear under developer)
boot to Download mode , confirm OEM unlock. This will wipe your phone.
go through start up, just skip everything, you phone will be wiped again anyway.
Connect to the internet, Open Developer Options, check that the "Enable OEM unlock" is greyed out!
By doing so, your bootloader is now unlocked. So yes, don't miss any steps stated above.
Samsung has a service called VaultKeeper to prevent unoffical firmware. Checking the "Enable OEM unlock" option is greyed out after Bootloader unlock will ensure the VaultKeeper to accept unoffical firmware. This requires internet connection. I suggest you to give the phone more time to check bootloader unlock state if you have a very slow / unstable internet connection.
If the outcome of the above steps does not appear to be true for you, your phone maybe cannot unlock bootloader.

HCU Unlocking credits (no longer) available

I accidentally purchased credits for dc-unlocker/HCU instead of the three day option (which I have since purchased and used to unlock my bootloader using a hardware TP) so if these are of any use to someone else let me know.

Hello. Can i use that to unlock my P20 Pro?

flaryx said:
Hello. Can i use that to unlock my P20 Pro?
Click to expand...
Click to collapse
Unfortunately they're no longer available, but you can use the same software to unlock the P20 Pro like I did. It's a little bit of a process, but I've got notes from when I did it if you are interested and I think I spent about 20 EUR for the 3 day licence of dc-unlocker/HCU. In the end I did it with the hardware test point because my back cover was loose and I intended to replace the battery anyway (it was bulging)

asozio said:
Unfortunately they're no longer available, but you can use the same software to unlock the P20 Pro like I did. It's a little bit of a process, but I've got notes from when I did it if you are interested and I think I spent about 20 EUR for the 3 day licence of dc-unlocker/HCU. In the end I did it with the hardware test point because my back cover was loose and I intended to replace the battery anyway (it was bulging)
Click to expand...
Click to collapse
Can you tell me the process please. I was thinking of buying the 3 day license or MOS but i don't know if I can do it or not (don't have any expertise on anything hardware related)

flaryx said:
Can you tell me the process please. I was thinking of buying the 3 day license or MOS but i don't know if I can do it or not (don't have any expertise on anything hardware related)
Click to expand...
Click to collapse
I unlocked my P20 Pro using a hardware testpoint, the HCU software, and a lot of time. I would suggest reading the information below, gathering all the tools/software/ROMS/IMGS you need and asking any questions before you purchase a licence or attempt this process.
WARNING!!!! THIS WILL ERASE YOUR PHONE COMPLETELY!!!
I would suggest making sure if you are going to purchase the 3 day license (this is what I did) that you are available to work on the phone for a couple of days (maybe buy it just before the weekend?) as if you run into any issues you won't have much time to fix them.
WARNING!!!! THIS WILL ERASE YOUR PHONE COMPLETELY!!!
BE CAREFUL TO PURCHASE THE THREE DAY LICENSE AT THE CHECKOUT NOT THE CREDITS (I MADE THIS MISTAKE AS YOU CAN PROBABLY TELL FROM THIS THRED)
Otherwise, the steps I went through are below, as well as some of the links to things I found helpful during the process:
1. SOFTWARE VERSION - It was not possible to unlock the bootloader on version 10 of the OS, so you will require HiSuite (https://consumer.huawei.com/au/support/hisuite/) to downgrade or dc-phoenix to flash an earlier version. I used 9.0.0.168 for my phone (Model: CLT-L29) so will reference that in all the steps below, but use the corresponding version for your phone (whichever you downgrade to from HiSuite should be fine?)
2. TESTPOINT - I used the hardware test point (next to the camera once the back cover is removed) but apparently this is possible using the software test point process (I am uncertain of the exact process for this, but there is a guide on the dc-unlocker site somewhere)
3. ADP/FASTBOOT RECOVERY UNLOCKING - Once the HCU software has provided a new code (or if you already have one) you can use fastboot oem unlock <code> where the <code> is the bootloader unlock code to unlock.
WARNING!!!! THIS WILL ERASE YOUR PHONE COMPLETELY!!!
4. ALTERNATIVE OS INSTALLATION - In my case I installed LineageOS 16 using an old guide (https://web.archive.org/web/20210726230701/https://depl0y.com/posts/P20-Pro-LineageOS-Guide/) which will only work (even the official version) if you patch the Lineage installation (update-script requires editing or replacement)
Install TWRP
Enable USB debugging
adb reboot bootloader
fastboot flash recovery_ramdisk twrp-3.7.0_9-0-charlotte.img
Hold VOL-UP & VOL-DOWN
fastboot reboot
You should now be in TWRP.
Flash LineageOS (and gapps)
In TWRP go to Advanced > ADB Sideload
adb sideload adb sideload lineage-16.0-20210211-nightly-charlotte-signed-modified.zip
adb sideload open_gapps-arm64-9.0-nano-20220215.zip
In TWRP go to Reboot > Bootloader
fastboot flash recovery_ramdisk RECOVERY_RAMDISK_9.0.0.168.img
fastboot reboot recovery
You should now be in the stock recovery. If not, boot into stock recovery
Select Wipe data / factory reset
Reboot system now
THE P20 WILL ONLY BOOT WITH THE STOCK RECOVERY, SO REPLACE IT AFTER USING TWRP
5. WEBVIEW FIX FOR GOOGLE APPS - DO NOT SET UP WIFI DURING INSTALL!
Download com.google.android.webview.apk from apkmirror and copy to the device. Install using the default file manager and reboot the phone. Sign in to Google and update webview, google apps, etc
6. ROOT ACCESS - MAGISK
Install apk (copy to storage and run from files) for Magisk and patch RECOVERY_RAMDISK_9.0.0.168.img.
Reboot into bootloader and flash to recovery: fastboot flash recovery_ramdisk RECOVERY_RAMDISK_9.0.0.168_magisk_patched-25200_8akQl.img
TO BOOT PHONE WITH ROOT BOTH VOLUME UP AND POWER BUTTONS NEED TO BE HELD AT STARTUP!