Database Info

[GUIDE] Installing and Rooting H950PR 5.1.1 from 5.0.1 10b

I caught the deal on ebay for an inexpensive Flex 2 not so long ago and, of course, the first thing I set out to do was update and root it.
The stock image ran 5.0.1, w/ firmware H950 v10b. I attempted an OTA update several days in a row, being told each time that none was available (the phone is AT&T branded and my service is through AT&T), but eventually grew impatient to get that sweet, sweet 5.1.1 action going.
After attempting to flash the 5.1.1 v11x rooted system image provided by randrew87 (here), I was greeted with a nifty little 'Security Error' boot screen and pursuant loop. Sadly, I wound up flashing the stock system dump I created following that tutorial to get back into a usable state.
Left with no other options (assuming, correctly, that I'm being impatient with OTA), I decided to try the 5.1.1 H950PR v15a firmware.
NOTE: Though I chose to flash the unrooted 5.1.1 H950PR image first, you may not have to complete this step; I'm not sure, but it's possible that you could simply write the rooted image instead.
First, I followed this wonderful tutorial by Sj12345: [KDZ] H950PR 5.1.1 compatible with ATT H950 with Video!!!
My initial plan was to write the unrooted system image and root using any of the available tutorials. Unfortunately, I couldn't get any of the tutorials to work for me as my device simply refused to allow r/w operations to /system while using the COM interface, regardless of my approach.
After a little trial and error, I discovered I could write the rooted H950PR-v15A image, provided here by Sj12345, and achieve root.
Here's how:
Download rootedsystem.img (from Sj12345's post)
Download LG Root Tools.zip (attached) and extract to a folder
Copy to the root of your internal sdcard via means of your choice (I used MTP mode and Explorer to drag and drop)
Power off your device
While holding VOLUME UP, insert a USB cable.
Open a Command Prompt window where you extracted the archive (easiest way is by holding Shift then right clicking within the folder > Open Command Prompt Here)
Double click ports.bat (included in the archive). Find the diagnostics port (in my case, COM4)
Type the following:
Code:
Send_Command.exe \\.\COM4
(replacing 4 w/ your com port)
You'll be greeted with a '#' prompt, terminal-style. From there, issue the following command (thanks to randrew87's thread):
Code:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=53248 count=534528 of=/dev/block/mmcblk0
The operation will take a couple of minutes. Once complete, you'll again be greeted with the '#' prompt.
Type LEAVE (all capitals), and hit enter. Your phone will reboot and have a clean, rooted image installed.
Profit.
This guide is obviously very specific, requiring H950v10b 5.0.1 firmware on an AT&T flex 2, no OTA availability, and a myriad of other issues (such as /system being readonly). My hope is that this will aid others who don't fall exactly into the parameters described in existing tutorials.
Thanks again to randrew87 and Sj12345 for their great posts and work; this thread is merely a slightly different approach to their pre-existing methods. They did the work, not me!
Hope this helps someone!
Regards
Smith

Any reason to go with h950pr instead of Ota 5.1.1 or simply just out of frustration of waiting? I'm asking cause I should get my att flex 2 tomorrow.

bL33d said:
Any reason to go with h950pr instead of Ota 5.1.1 or simply just out of frustration of waiting? I'm asking cause I should get my att flex 2 tomorrow.
Click to expand...
Click to collapse
PR rom does not have all of the AT&T bloat. However, the main drawback that I'm aware of is that there is currently no way to go back to official AT&T. Seems everyone who has tried to do so has ended up with a bricked phone. You may also run into issues trying to get warranty honored once you move off the official AT&T version. So.. caveat emptor and all.
Most folks who really want the 5.1.1 OTA have managed to do so by laying down the minimum amount of cash for an AT&T gophone plan then getting on the horn with AT&T's tech support to have them manually push the update through.

Hi smithisize, thank you for your guide A very basic question, how do I know which version of root file to use? I just check in About Phone > Hardware Info and it said the phone was LG-H950.

Smithisize,
Thank you for the guide. I have a question.
My H950 has H950v10d 5.0.1 on it. I am just guessing that it would work for any 5.0.1 version.
Is this right?
Thanks again,
MB

Same here...
As Meatbag_1 written, I have the H95010d release witch rom we take???

Yes it will work for atnt g flex2 on atnt firmware 5.0.1 all subversions
Sent from my Lenovo P780 using Tapatalk

Isn't the latest software version for the US h950 the "v11x" version? Is it possible to flash that instead of the PR firmware?

No
Only OTA from AT&T
No flash
Sent from my LGLS996 using Tapatalk

I tried rooting my newly flashed 5.1.1pr with this method and got authentication error 11. I had to reflash to get out of the boot loop. What am i doing wrong?

Thanks man. How can i root it in the first place?
I was trying HERE but i do not know which to dowload, if H950 V11X or H950 V11Z ... can you help me with that?

H950v10d 5.0.1 not rooted. Tried method from OP using H950PR 5.1.1 rootedsystem.img. Now I am stuck at Security Error bootloop. Where to go from here?
Nevermind... Phone started non stop bootlooping with no way to shut it off. So, I smashed it to bits.

For Android 5.1.1 PR (Puerto Rico)
First Flash the KDZ file from here: http://forum.xda-developers.com/g-flex2/general/kdz-compatible-att-h950-t3180847 using LG Flash Tool. I use Build 03/07/2014 Offline with modded hosts file.
Then download the Rooted H950PR-v15A image file from the link provided and continue with the guide.
btw: thanks for adding; you type: "LEAVE" in caps. No other guide seemed to mention that and when I did, it was the only time it actually rebooted my phone..:good:

dustindavidson900 said:
H950v10d 5.0.1 not rooted. Tried method from OP using H950PR 5.1.1 rootedsystem.img. Now I am stuck at Security Error bootloop. Where to go from here?
Nevermind... Phone started non stop bootlooping with no way to shut it off. So, I smashed it to bits.
Click to expand...
Click to collapse
My Phone did that too but I caught it quickly between boots and got into download mode so I missed the satisfaction of smashing it..

twiice said:
My Phone did that too but I caught it quickly between boots and got into download mode so I missed the satisfaction of smashing it..
Click to expand...
Click to collapse
I was able to get to download mode, but it would just go into bootloop after entering download mode. I have another on the way, so hopefully things go better this time. Will try the method posted above.
Can you send me a link to download "LG Flash Tool Build 03/07/2014 Offline with modded hosts file?"
thanks

Your can download it from here:
http://forum.xda-developers.com/showthread.php?t=2797190
I ignore the warning about the kdz having to be in the flash tool directory. I just browse to the location I downloaded it to, never fails.
And about the hosts file, this version doesn't seem to need a modded hosts file as it won't try to connect. That was sth I had to do from an earlier version a long time ago and forgot.
Fyi: I soft-bricked my phone like many others having the same security error because of tring to install the rooted system image file for 5.1.1 over the top of 5.0.1. And to reboot from download mode I had to hold all three back-buttons.
To install Xposed framework follow this guide: http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593 but USE Flashfire 0.24 or earlier as the latest beta version won't flash sh*t on this phone (or the G4)
If you need detailed instructions let me know.
Good luck!
PS: I bought the AT&T version(5.0.1) for the 3GB of RAM but I live in Australia so couldn't get the 5.1.1 OTA which is why I had to do this way, but apparently if you flash the 5.1.1PR kdz over the 5.1.1 AT&T OTA update(just to avoid AT&T bloatware) it will brick your phone.

so i just purchased the the g flex 2 much like yourself and i have everything ready to go. My only concern before doing so is what to do after the soft brick. Once you reboot from download mode is, doesthe phone start normally? or is there an extra step since you talked about USE flashfire
PS. i dont care to root the phone or is it necessary for this all to work?

Updated H950 5.0.1 ATT to H950PR 5.1.1
had the lg drivers which i downloaded using the lg suite from the LG website ( i originally tried to update my phone using this method...didnt work obviously so i came here)
Used lg flash tool 2014 as provided from this forum.
Placed H950PR15a_00.kdz in the place where it asks in the tool
followed the guide, i had the phone in debugging mode and it was just on my homescreen unlocked, phone shut off restarted into download mode and started the firmware update, phone itself reset at 100% ( keep it plugged in)
Lg flash tool was still going at this point it was around 90%, phone was resetting when the lg flash tool hit 100% and then crashed ( had a panic attack really ) i kept the phone plugged in and it reset to the lg boot screen
Leaving it plugged in , in spanish i saw that it was optimizing my apps, went to the tutorial within the phone and it resarted again... so i started having another attack, i then saw the boot screen claro at this point i unplugged my phone and it is now on 5.1.1 h950PR i have not rooted the phone before hand it was stock from ATT.
Thought i put my experience in here with this phone in hope to ease some tension. it was easier than i thought even though the tool crashed at the end, phone had already accepted the KDZ at that point

twiice said:
For Android 5.1.1 PR (Puerto Rico)
First Flash the KDZ file from here: http://forum.xda-developers.com/g-flex2/general/kdz-compatible-att-h950-t3180847 using LG Flash Tool. I use Build 03/07/2014 Offline with modded hosts file.
Then download the Rooted H950PR-v15A image file from the link provided and continue with the guide.
btw: thanks for adding; you type: "LEAVE" in caps. No other guide seemed to mention that and when I did, it was the only time it actually rebooted my phone..:good:
Click to expand...
Click to collapse
Thanks mate. Ran into this problem when flashing the ATT version before flashing the PR version like I was going to. This solved it, thought I'd wrecked the phone for a sec.
Much appreciated

[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.

[Guide] LG V20 Back to Life [Download mode] [LG Flash tool] [Unknown model in LGUP]

Overview:
Did you got that annoying "Unknown Model" in LGUP and now are struck download mode. This usually happens when you try to root with dirty and do something wrong to mess up entire process.
What Actually happened in my case:
I had a friend who tried to root his H990ds with dirtysanta but due to some issues the whole process messed and his phone was struck in download mode. Phone was unable to go pass LG logo and boot. LGUP was unable to recognize the phone. We tried different ways, different drivers but all in vain. So, we were able to do this process and it worked finally.
This process was tested with H990ds. Here files for H990ds are provided. You need files respective for your model.
Possible Cases:
So I will not waste the time. Possible cases:
1: LG V20 stuck on download mode and it is now not being recognized by LGUP and you can’t do anything, because no other tool is available.
2: You installed a custom ROM and now LGUP is not recognizing it. You want to go back to stock and can’t do it.
3: Anything bad happened during flashing process, PC restarted, phone went off or whatever. And now you can’t bring it back to life.
¬ Or
Other cases you faced.
Read 4th post before proceeding,
Before asking a question, first, see FAQ in 3rd post. In that way you can save a lot of time.
Things You need:
1: LG UP
2: Uppercut
3: Drivers
4 : LG Flash tool (the one used to bring LG G2, G3 back to stock).
5: LG Firmware extract tool
(All above files can be found in 2nd post)
6: Stock ROM for your device.
I used V10g KDZ for H990ds. You need to download KDZ of your specified model.
7: Dll specified for your model (in 2nd post H990ds dll is provided)
Process:
First:
Uninstall all other tool, previous driver (including other phone’s too). Restart PC
Just to avoid problems. I tried this process many times on Windows 10 64-bit and it always worked for me. So it has no problems with new Windows OS.
Now follow procedure in exact order.
1: Install Latest LG drivers.
Put Phone in download
(Hold Vol+ and connect to PC while it was powered off).
Wait until it finishes installing drivers. Change COM Port to 41.
{
"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"
}
( Refer here for changing this, If you can’t understand that.)
Now DC it from PC and keep it staying in Download mode.
2: Install LG Flash tool and copy megalock.dll to installation directory or it won’t work.
3: Install LGUP_Store_Frame_Ver_1_14_3.
4: Extract LG Firmware Extract and copy Stock KDZ to that folder.
5: Run WindowsLGFirmwareExtract.exe. Click on Open.
6: Select your KDZ. Select all content off kdz.
7: Click on extract kdz. Wait for kdz to extract. You will notice a dz and LGUPc.dll.
8: Run LG Flash Tool. Select Manual Mode.
9: Select LGUPc.dll in dll section.
10: Select .kdz in S/W section (You will have to select show all files to make .kdz visible).
11: Now Begin downloading by pressing "Yellow Right Arrow". Connect phone in download mode.
The step will fail at 4%. Now Disconnect phone. Do not turn off phone. Just disconnect it.
12: Now exit and start LG Flash Tool again. Select Manual Mode. This time Select LGUP_H990ds.dll this time for dll section
(You need different dll for different model. For example, "LGUP_VS995.dll" for VS995 variant )
13: Now select that extracted dz in S/W section this time. Click on Start Arrow. Connect phone.
14: This time the flashing will begin. It will go upto 150%. Wait for it to complete.
After flashing phone will boot into a screen with a big 2 on screen. After some time it will change into big 3.
15: When it changes into big 3. Pull the battery and start the phone.
Your phone should start after some time. It should be detected by LGUP.
For Phone Stuck at Big 2:
If your phone stuck at big 2 during process then you will have 2 choice, either restart process from start or flash this time with LGUP. Because phone is now running a fully stock firmware it should be detected by LGUP completely. You can simply flash kdz with LGUP and it will not show big 2 on screen. You need to start LGUP with uppercut.

Attachments:
1: LG FlashTool
2: LG Firmware Extract 1.2.5
3: Uppercut
4: LGUP 1.14.3
5: Driver 4.2
or Mirror for Drivers (All Version) (Use latest)
DLL Files:
LG H990DS DLL
LG VS995 DLL

FAQ​
I got confused on which Flash tool to use and with this megalock stuff?
Ans: Thanks, you asked, Just download LG Flash Tool attached in 2nd post, unzip, install tool, there will be a megalock.dll too, copy that to installation folder (by default that's "C:\LG\LGFlashTool") and overwrite, (written in install. Instructions too inside zip).
This method isn't working for me, what shall I do?
Ans: The possible reasons, for that not working, might be,
A: You didn't installed drivers properly, try uninstalling old drivers and restarting after that.
B: LG COM PORT isn't set to COM41, here is guide for that.
C: And Most important, You are not following steps in the order in which they are written, so read carefully.
Where I can download stock KDZ or dll for my LG Phone (other than V20)
Ans: Most LG Phone KDZs can be found at this website.

First of All:​After Flashing let me know about your experience by answering the poll, this will help me in updating this post. Also tell me about you experience in comments.
Disclaimer:​
Before proceeding, remember I’m not responsible for anything bad happened to your device by following this or any of my guide. I’m just trying to help. So always do it on your own risk…
Don’t blame me or Any other developer.
All tools here are developed by different personalities. I’m just providing a guide on using these tool. Always say thanks to me and them. And If possible, donate them. They really deserve it.
Thanks be to:
@AutoPrime for All.
@Hyelton for post on LG Flash tool.
@bullghost for lg firmware extractor.

Last one. Sorry for using too much space

dksoni411 said:
Last one. Sorry for using too much space
Click to expand...
Click to collapse
I followed this guide through all the steps since my device was unknown in LGUP (patched).
Now I'm stuck with nice LG boot logo (not even the warning screen), TWRP and unlocked bootloader with working fastboot commands.
No matter whichever rom I flash through TWRP, I end up on the LG logo when I reboot, rooted or not. I have tried H910_10r, LOS 15.1, LOS 14.1 with respective gamma kernels or without and I can't get past the LG logo. Also, there is no LG Flash tool compatible DLL for H915 / H910 / H910PR. Just only H918 on the website you mentioned.
I have 3 USB Type-C cables which all work with QPST factory reset for Lenovo ZUK Z2 and I've tried both USB 2.0 as well as USB 3.0 ports on my two laptops. Both have drivers test-signing enabled and I've flashed kdz's in the past without any hassle.

dark_prince said:
I followed this guide through all the steps since my device was unknown in LGUP (patched).
Now I'm stuck with nice LG boot logo (not even the warning screen), TWRP and unlocked bootloader with working fastboot commands.
No matter whichever rom I flash through TWRP, I end up on the LG logo when I reboot, rooted or not. I have tried H910_10r, LOS 15.1, LOS 14.1 with respective gamma kernels or without and I can't get past the LG logo. Also, there is no LG Flash tool compatible DLL for H915 / H910 / H910PR. Just only H918 on the website you mentioned.
I have 3 USB Type-C cables which all work with QPST factory reset for Lenovo ZUK Z2 and I've tried both USB 2.0 as well as USB 3.0 ports on my two laptops. Both have drivers test-signing enabled and I've flashed kdz's in the past without any hassle.
Click to expand...
Click to collapse
Try using dll from common folder in patched lgup. Use that dll with dz. Extracted dll from kdz with kdz.

dksoni411 said:
Try using dll from common folder in patched lgup. Use that dll with dz. Extracted dll from kdz with kdz.
Click to expand...
Click to collapse
Alright I used the LGUPc.dll with the kdz and ended up with error at 4%
then I selected common dll and the extracted .dz file.
I ended up in the error as shown in the picture.

dark_prince said:
Alright I used the LGUPc.dll with the kdz and ended up with error at 4%
then I selected common dll and the extracted .dz file.
I ended up in the error as shown in the picture.
Click to expand...
Click to collapse
You said you were rooted before. Which means you aboot is from us996. So you need to flash us996 kdz (along us996 dz) using this method. If you want to use that kdz you have then you need to restore your abootbackup.
I recommend download us996 and flashing it. After that you're phone will be detected then lgup then you can flash stock original kdz if you want to.

dksoni411 said:
You said you were rooted before. Which means you aboot is from us996. So you need to flash us996 kdz (along us996 dz) using this method. If you want to use that kdz you have then you need to restore your abootbackup.
I recommend download us996 and flashing it. After that you're phone will be detected then lgup then you can flash stock original kdz if you want to.
Click to expand...
Click to collapse
I have US996_10f kdz as well and its in the same boat. Same error at 4%
I'm now fully stock but the download mode shows 633A B50 on the status screen.

Can I use this to convert ls997 into us996 for bootloader unlock and root purposes?

rayulove69 said:
Can I use this to convert ls997 into us996 for bootloader unlock and root purposes?
Click to expand...
Click to collapse
Only if you haven't taken the update which bumps anti-rollback up. In that case you can't unless there is us996 kdz with same ARB.

dark_prince said:
I have US996_10f kdz as well and its in the same boat. Same error at 4%
I'm now fully stock but the download mode shows 633A B50 on the status screen.
Click to expand...
Click to collapse
Can you get on some instant message platform. Whatsapp, facebook or Skype

dksoni411 said:
Can you get on some instant message platform. Whatsapp, facebook or Skype
Click to expand...
Click to collapse
check PM

633A B50
dksoni411 said:
Can you get on some instant message platform. Whatsapp, facebook or Skype
Click to expand...
Click to collapse
Did you solve this problem?

Big 2- vs995
I can't get past the Big 2. I am wondering if my boot.img is gone.

wakko222 said:
I can't get past the Big 2. I am wondering if my boot.img is gone.
Click to expand...
Click to collapse
So what I figured out was, run LGUP, but instead of clicking "UPGRADE", run it as "REFURBISH."

wakko222 said:
Did you solve this problem?
Click to expand...
Click to collapse
No.

Nice Write-up! Thank God this hasn't happened to me, I have only needed to use the LGUP to unbrick my phone. I did have trouble getting Download Mode after millions of various upgrades. What I found out is that if you have a flaky cable you might never get into download mode, so make sure to try a couple of USB-C cables before you give up and start from scratch. It just might be your USB cable.

how to adapt for h910 ?
dksoni411 said:
This process was tested with H990ds.
Click to expand...
Click to collapse
How would it work for a h910 in this state of display whitenoise static (link to first of several posts)?
What would be different for my bricked h910? and e.g. This site has only files for the 918.

[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.