Develop Bugs

Korean variant bootloader unlock and root.

THIS THREAD IS FOR KOREAN VARIANT LG V30 TO GET THE SIGNAL
MODEL SUPPORTED : V300S, V300L V300K
FOLLOW THE GUIDE BELOW AND DONT MESS UP.
DONT DO ANY EXTRA STEP THAT IS NOT MENTION HERE.
WE WILL NOT HOLD ANY RESPONSIBLE IF YOUR DEVICE GO INTO WORLD WAR OR BOOM OR BRICK OR WHATEVER.
THANKS TO : @TxanMoe to found out how to root for most lgv30
: @ChazzMatt to guide everyone on the main thread
: @bilong9 to help Korean variant to get signal back
: @darkidz555 to whatever haha
To everyone if I forget mention please let me know
You need to enter the different boot menus (mainly factory data reset menu and fastboot menu) many times, so I just have notes here on the top of how it should happen
- Download mode
How to enter : Device power is off, hold volume up -> insert usb cable -> should go to download mode
- Factory data reset menu
Hold Power button and volume down button when boot starts. After some seconds (when phone vibrates or LG logo is visible) let go of power button for 1 second, and then click power button. (This caused me the most headaches, as if I were holding the buttons for too long, the device would cut power and reboot)
fastboot mode
- when device is shut down and without usb cable, hold volume down button for few seconds and plug in usb cable
--------------------------------------------------------------
First, Download files:
- LGup V30DLL_PATCHED
https://drive.google.com/file/d/1zvp...K5KjAQYm5/view
- LGup needs you to install download LG Mobile drivers
http://tool.cdn.gdms.lge.com/dn/down...=UW00120120425
- kdz H930
https://drive.google.com/file/d/1CbK...idtexwrXw/view
- kdz Us988
https://drive.google.com/file/d/151T...ztduIF_H5/view
- Adb.unlock.twrp.root
https://drive.google.com/file/d/1SvX...Myl199nwD/view
Depending on your variant (v300k / v300s / v300L) download one of the following files:
- For v300k: Rom zip v300k_21e (twrp) Rom running on us998 platform
https://drive.google.com/file/d/1DSC...m8skDBfty/view
OR
- For v300s & v300L: Rom zip v300s_21e (twrp) Rom running on us998 platform
https://drive.google.com/file/d/12wH...E6hXS7blr/view
Move files to microSD card of the phone
- Rom_LGv30_V300s_v21e_Oreo_full_stock.zip ( pick your variant )
- 1Magisk-v16.0.zip
- 2no-verity-opt-encrypt-6.0.zip
- 3lg-rctd-disabler-1.0.zip
Enable developer settings on Android settings
On Developer options
- Enable OEM unlock
- Enable USB Debugging
Connect Device to PC with USB. For me the usb mode had to be File Transfer (I read somewhere that it had to be Photo transfer, but that did not work with LGUP.exe for me
Start LGUP.exe
- If popup "Cant find handset", plug out and in usb on the phone.
- If popup "LGUP can't load the model[C:\Program Files(x86)\LG Electronics\LGUP\..." then create that LGUP folder and copy the model folder to it from LGUP V30DLL_PATCHED folder
- Choose PARTITION DL
- Select file H93020d_00_OPEN_EU_OP_0326.kdz
- Press Start
- From Partition List, tick Select All and press OK
- Phone will reboot to the flash menu
- LGUP_common popup will appear about Partition(s) changed "cache" etc. Press Yes
- Wait for it to finish
- When finished, and screen disappears, immediately hold both power and volume down button, when lg screen appears, stop pressing power button for 1 second, and then click power button once (If you don't time it right, you get stuckin LG life's good screen. Try again by holding volume down and power button for 8 seconds and device restarts)
- In Factory data reset menu delete all.
- Device will boot to android Setup
Setup Android
- Go through the setup steps
- Enable developer settings on Android settings
On Developer options
- Enable OEM unlock
- Enable USB Debugging
On computer, open cmd-here.exe
- enter command to check if device is found: adb devices
- enter command: adb reboot bootloader
- enter command: fastboot getvar all
- From the output: unlocked:no
- enter command: fastboot flash unlock unlock.bin
- Output will say "Failed (remote: Error!! Wrong unlock key size)", don't mind that
- Press Power button
- You will see error message on the device, hold volume down button until you can hear usb connection sound from computer (?)
- Device will boot
- Once booted, shutdown from android menu
- remove usb cable
- Enter download mode by holding Volume up button and then insert usb cable
Open LGUP.exe
- Choose PARTITION DL
- Select US99820a_04_0330.kdz
- Press Start
- From partition list, tick Select all and Ok
- Partition changed popup: press ok.
- As soon as it is done and screen goegoes black, Hold volume down and power button. when LG v30 screen is visible, let go of power button for 1 second, and then click power button.
- Erase all to factory settings
- Let device boot. As soon as it is booted, shut down android from menu
- When shut down, it starts to reboot, press volume down for few seconds to enter fastboot menu
In fastboot menu
- open cmd-here.exe again.
- Enter command: fastboot getvar all
- Output should now say "unlocked:yes"
- Enter command: fastboot flash recovery TWRP-3.2.1-joan-v0.1.img
- Output should say: "Ok"
- shutdown device by pressing power button. After power off, start holding powerbutton and volumedown button to enter Factory data reset menu. When logo appears or phone vibrates let go of power button, and after 1 second tap power button. Reset all
- Device should go to TWRP
- If device booted to Android, TWRP needs to be flashed again ( Do steps: turn of from power menu, enter fastboot menu, flash TWRP from command line, enter Factory reset on first boot and delete everything ).
In TWRP
- First press Cancel (on Mount: Decrypt Data screen)
- Swipe to Allow Modifications
- press Wipe
- press Format Data
- type: Yes
- Press Check on keyboard
- Output Data Format Complete
- Press back to get to Wipe screen
- Swipe to Factory Reset
- press Back and choose Advanced Wipe
- Tick: Dalvik / ART Cache, System, data, cache
- Swipe to Wipe
- Press home button
Take backup of stuff
press Install on TWRP home:
- Locate files that were copied to microsd card before
- If files are not on microSD card, they can be copied from computer using command: adb push localfile destination
(f.e: adb push Rom_LGv30_V300k_v21e_Oreo_full_stock_v1.zip /external_sd )
- Choose Rom_LGv30_V300k_v21e_Oreo_full_stock_v1.zip (or your variant)
- Swipe to confirm Flash
- Wait until finished
- Output should say: "Zip succesfully installed have fun"
Press Install on TWRP home:
- Choose 1Magisk-v16.0.zip
- Swipe to confirm Flash
- Output gives Failure for some reason( also happens in BiLong video, idk the reason )
- Install both:
2no-verity-opt-encrypt-6.0.zip
and
3lg-rctd-disabler-1.0.zip
- both outputs should say: Successful
From TWRP home press Reboot
- Press System
- Press Do Not Install
Phone should now reboot to Android and have mobile signal
- Go through setup
- Press shutdown
- Enter Factory data reset menu. When logo displays, let go of power, and after 1 second, click power button. Erase everything
Phone goes to TWRP
- Swipe to Allow Modifications
- Go to Install
- Locate files on microSD card
- Choose 1Magisk-v16.0.zip and swipe to flash
- Now it should install successful
- Install both:
2no-verity-opt-encrypt-6.0.zip
and
3lg-rctd-disabler-1.0.zip
- press reboot system

V300S with 8.0
Hi, I have the V30S (V300S) and I want to install the 8.1, which lineageos version should I use or what should I install? It's the 1st time I do this, if you could tell me the steps and links of all I need would be great!!!! I have 8.0 with Bluetooth issues and my device is not rooted, I don't even know how to root… Thanks!

Gera77 said:
my device is not rooted, I don't even know how to root… Thanks!
Click to expand...
Click to collapse
Read post #1 of this thread and you'll know how to root. There's even a section called "FLASH TWRP AND ROOT".
It seems like you posted without reading anything first...

Gera77 said:
Hi, I have the V30S (V300S) and I want to install the 8.1, which lineageos version should I use or what should I install? It's the 1st time I do this, if you could tell me the steps and links of all I need would be great!!!! I have 8.0 with Bluetooth issues and my device is not rooted, I don't even know how to root… Thanks!
Click to expand...
Click to collapse
If you don't understand what I write then the end of the thread have video for you to follow. If you really wanna root your device try to do some research at least a basic one.

I was following the video and it has link to file:
Rom_LGv30_V300s_v21e_Oreo_full_stock.zip
I have Android security patch level
May 1, 2018
And Software version:
V300K21g
On the video @bilong9 has March 1, 2018 security patch level and V300K21e software version. Other software info are the same. Can I use the Rom and other files on that video? Sorry for noob questions

defic said:
I was following the video and it has link to file:
Rom_LGv30_V300s_v21e_Oreo_full_stock.zip
I have Android security patch level
May 1, 2018
And Software version:
V300K21g
On the video @bilong9 has March 1, 2018 security patch level and V300K21e software version. Other software info are the same. Can I use the Rom and other files on that video? Sorry for noob questions
Click to expand...
Click to collapse
For me,
security patch level: May 1, 2018 and Software version:V300L21g
It worked

Thanks, worked for me too! Thanks to @bilong9 s video and @ChazzMatt advice on the original thread. I pretty much followed bilongs video, but I wasn't always sure which buttons @bilong9 pressed, so I took notes of what I did to better understand what is happening (last time I rooted Android was back in the days with note 3). It might be that I did something unnecessary, but in the end I got root. (I Had Security patch level: 1 May, 2018. Future security levels might not work)
I'll leave my (quite detailed) notes here if somebody finds it useful basically it is just text version of @bilong9 youtube video. All credit to him of the links and steps
You need to enter the different boot menus (mainly factory data reset menu and fastboot menu) many times, so I just have notes here on the top of how it should happen
- Download mode
How to enter : Device power is off, hold volume up -> insert usb cable -> should go to download mode
- Factory data reset menu
Hold Power button and volume down button when boot starts. After some seconds (when phone vibrates or LG logo is visible) let go of power button for 1 second, and then click power button. (This caused me the most headaches, as if I were holding the buttons for too long, the device would cut power and reboot)
fastboot mode
- when device is shut down and without usb cable, hold volume down button for few seconds and plug in usb cable
--------------------------------------------------------------
First, Download files:
- LGup V30DLL_PATCHED
https://drive.google.com/file/d/1zvpcaYC6oDmksqvgXqLw9B2K5KjAQYm5/view
- LGup needs you to install download LG Mobile drivers
http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
- kdz H930
https://drive.google.com/file/d/1CbKGw7TVQ-kLTfraEA39GJridtexwrXw/view
- kdz Us988
https://drive.google.com/file/d/151TbShPdh9VyV5RBXZEQitFztduIF_H5/view
- Adb.unlock.twrp.root
https://drive.google.com/file/d/1SvXeQK2xVk7N9yWEh7efYOZMyl199nwD/view
Depending on your variant (v300k / v300s / v300L) download one of the following files:
- For v300k: Rom zip v300k_21e (twrp) Rom running on us998 platform
https://drive.google.com/file/d/1DSCmNuL9gR6BhpEfv-rjWa4m8skDBfty/view
OR
- For v300s & v300L: Rom zip v300s_21e (twrp) Rom running on us998 platform
https://drive.google.com/file/d/12wHjqu_04ueeD77AgwtDrliE6hXS7blr/view
Move files to microSD card of the phone
- Rom_LGv30_V300s_v21e_Oreo_full_stock.zip ( pick your variant )
- 1Magisk-v16.0.zip
- 2no-verity-opt-encrypt-6.0.zip
- 3lg-rctd-disabler-1.0.zip
Enable developer settings on Android settings
On Developer options
- Enable OEM unlock
- Enable USB Debugging
Connect Device to PC with USB. For me the usb mode had to be File Transfer (I read somewhere that it had to be Photo transfer, but that did not work with LGUP.exe for me
Start LGUP.exe
- If popup "Cant find handset", plug out and in usb on the phone.
- If popup "LGUP can't load the model[C:\Program Files(x86)\LG Electronics\LGUP\..." then create that LGUP folder and copy the model folder to it from LGUP V30DLL_PATCHED folder
- Choose PARTITION DL
- Select file H93020d_00_OPEN_EU_OP_0326.kdz
- Press Start
- From Partition List, tick Select All and press OK
- Phone will reboot to the flash menu
- LGUP_common popup will appear about Partition(s) changed "cache" etc. Press Yes
- Wait for it to finish
- When finished, and screen disappears, immediately hold both power and volume down button, when lg screen appears, stop pressing power button for 1 second, and then click power button once (If you don't time it right, you get stuckin LG life's good screen. Try again by holding volume down and power button for 8 seconds and device restarts)
- In Factory data reset menu delete all.
- Device will boot to android Setup
Setup Android
- Go through the setup steps
- Enable developer settings on Android settings
On Developer options
- Enable OEM unlock
- Enable USB Debugging
On computer, open cmd-here.exe
- enter command to check if device is found: adb devices
- enter command: adb reboot bootloader
- enter command: fastboot getvar all
- From the output: unlocked:no
- enter command: fastboot flash unlock unlock.bin
- Output will say "Failed (remote: Error!! Wrong unlock key size)", don't mind that
- Press Power button
- You will see error message on the device, hold volume down button until you can hear usb connection sound from computer (?)
- Device will boot
- Once booted, shutdown from android menu
- remove usb cable
- Enter download mode by holding Volume up button and then insert usb cable
Open LGUP.exe
- Choose PARTITION DL
- Select US99820a_04_0330.kdz
- Press Start
- From partition list, tick Select all and Ok
- Partition changed popup: press ok.
- As soon as it is done and screen goes black, Hold volume down and power button. when LG v30 screen is visible, let go of power button for 1 second, and then click power button.
- Erase all to factory settings
- Let device boot. As soon as it is booted, shut down android from menu
- When shut down, it starts to reboot, press volume down for few seconds to enter fastboot menu
In fastboot menu
- open cmd-here.exe again.
- Enter command: fastboot getvar all
- Output should now say "unlocked:yes"
- Enter command: fastboot flash recovery TWRP-3.2.1-joan-v0.1.img
- Output should say: "Ok"
- shutdown device by pressing power button. After power off, start holding powerbutton and volumedown button to enter Factory data reset menu. When logo appears or phone vibrates let go of power button, and after 1 second tap power button. Reset all
- Device should go to TWRP
- If device booted to Android, TWRP needs to be flashed again ( Do steps: turn of from power menu, enter fastboot menu, flash TWRP from command line, enter Factory reset on first boot and delete everything ).
In TWRP
- First press Cancel (on Mount: Decrypt Data screen)
- Swipe to Allow Modifications
- press Wipe
- press Format Data
- type: Yes
- Press Check on keyboard
- Output Data Format Complete
- Press back to get to Wipe screen
- Swipe to Factory Reset
- press Back and choose Advanced Wipe
- Tick: Dalvik / ART Cache, System, data, cache
- Swipe to Wipe
- Press home button
Take backup of stuff
press Install on TWRP home:
- Locate files that were copied to microsd card before
- If files are not on microSD card, they can be copied from computer using command: adb push localfile destination
(f.e: adb push Rom_LGv30_V300k_v21e_Oreo_full_stock_v1.zip /external_sd )
- Choose Rom_LGv30_V300k_v21e_Oreo_full_stock_v1.zip (or your variant)
- Swipe to confirm Flash
- Wait until finished
- Output should say: "Zip succesfully installed have fun"
Press Install on TWRP home:
- Choose 1Magisk-v16.0.zip
- Swipe to confirm Flash
- Output gives Failure for some reason( also happens in BiLong video, idk the reason )
- Install both:
2no-verity-opt-encrypt-6.0.zip
and
3lg-rctd-disabler-1.0.zip
- both outputs should say: Successful
From TWRP home press Reboot
- Press System
- Press Do Not Install
Phone should now reboot to Android and have mobile signal
- Go through setup
- Press shutdown
- Enter Factory data reset menu. When logo displays, let go of power, and after 1 second, click power button. Erase everything
Phone goes to TWRP
- Swipe to Allow Modifications
- Go to Install
- Locate files on microSD card
- Choose 1Magisk-v16.0.zip and swipe to flash
- Now it should install successful
- Install both:
2no-verity-opt-encrypt-6.0.zip
and
3lg-rctd-disabler-1.0.zip
- press reboot system
- press Do not install (why?)
Now you are rooted and have Magisk Manager on desktop
Click to expand...
Click to collapse

defic said:
Thanks, worked for me too! Thanks to @bilong9 s video and @ChazzMatt advice on the original thread. I pretty much followed bilongs video, but I wasn't always sure which buttons @bilong9 pressed, so I took notes of what I did to better understand what is happening (last time I rooted Android was back in the days with note 3). It might be that I did something unnecessary, but in the end I got root. (I Had Security patch level: 1 May, 2018. Future security levels might not work)
I'll leave my (quite detailed) notes here if somebody finds it useful basically it is just text version of @bilong9 youtube video. All credit to him of the links and steps
Click to expand...
Click to collapse
Your written instructions are very detailed. Thank you
V300s works with v300L

bilong9 said:
Your written instructions are very detailed. Thank you
V300s works with v300L
Click to expand...
Click to collapse
Thanks, I fixed it on my notes.

defic said:
Thanks, worked for me too! Thanks to @bilong9 s video and @ChazzMatt advice on the original thread. I pretty much followed bilongs video, but I wasn't always sure which buttons @bilong9 pressed, so I took notes of what I did to better understand what is happening (last time I rooted Android was back in the days with note 3). It might be that I did something unnecessary, but in the end I got root. (I Had Security patch level: 1 May, 2018. Future security levels might not work)
I'll leave my (quite detailed) notes here if somebody finds it useful basically it is just text version of @bilong9 youtube video. All credit to him of the links and steps
Click to expand...
Click to collapse
Will copy the detail to the post thanks for detail !!

I wanted to get rid of the korean rom bloatware (and korean text all over the place) so I DL partition flashed h930 EU Rom without xbl1, xbl2, modem, recovery and recoverybak with the patched LGUP. For some reason, I still lost recovery (maybe because I did not manage to do the button dance on first boot?). Then in Fastboot mode I reflashed TWRP, got in to twrp and rooted the phone again.
Calls and data are both working. But when booting the phone, it seems to take longer time than before to get sim signal (around 30 seconds after inserting PIN code). Also when I made my very first call, signal disappeared but came back after a reboot. It has not occured anymore. Also Lte Multiband selection engineering menu is not working, but that was kinda expected.
I kept korean xbl1 and xbl2 because I found a post by @bilong9 when he first discovered how to get signal back. I don't know if signal would work with only korean rom modem.

defic said:
I wanted to get rid of the korean rom bloatware (and korean text all over the place) so I DL partition flashed h930 EU Rom without xbl1, xbl2, modem, recovery and recoverybak with the patched LGUP. For some reason, I still lost recovery (maybe because I did not manage to do the button dance on first boot?). Then in Fastboot mode I reflashed TWRP, got in to twrp and rooted the phone again.
Calls and data are both working. But when booting the phone, it seems to take longer time than before to get sim signal (around 30 seconds after inserting PIN code). Also when I made my very first call, signal disappeared but came back after a reboot. It has not occured anymore. Also Lte Multiband selection engineering menu is not working, but that was kinda expected.
I kept korean xbl1 and xbl2 because I found a post by @bilong9 when he first discovered how to get signal back. I don't know if signal would work with only korean rom modem.
Click to expand...
Click to collapse
You can use international rom ( BoomBox). in the following order
Flash rom v300x.zip > in twrp full wipe > flash rom boombox.
I am using rom boombox 20r

fastboot's not working on my v300L

nythawk23 said:
fastboot's not working on my v300L
Click to expand...
Click to collapse
Have you followed the instructions in post #1 yet?
You can't skip ahead. You'll get fastboot commands when you follow the instructions step by step.

Hello to all. I have been following the detailed instructions by Defic based on Bilong9 and watching also video in youtube, so I have got well prepared before unlocking bootloader in my LG V30 v300k. Thanks a lot, I could unlock bootloader and installed root and TWRP, but I faced at the end with a problem of missing carrier signal. I thought maybe I have done mistake and downloaded stock and flashed it in LGUP in Refurbished mode since Bilong9 has advised to somebody with the same issue. After that I have flashed KDZ US988 since I had already bootloader unlocked, then I installed again v300k file provided in the instruction. I don't have still carrier signal. Please, help me to resolve my issue with your advises, how can I bring back carrier signal? I don't want to brick my phone, may be the issue with modem, is there possibility of installing only modem seperatetly via TWRP, will this work? What if I install firmware in LG bridge, will this work and will I loose unlocked bootloader? Thank you all in advance.

Umedchik said:
Hello to all. I have been following the detailed instructions by Defic based on Bilong9 and watching also video in youtube, so I have got well prepared before unlocking bootloader in my LG V30 v300k. Thanks a lot, I could unlock bootloader and installed root and TWRP, but I faced at the end with a problem of missing carrier signal. I thought maybe I have done mistake and downloaded stock and flashed it in LGUP in Refurbished mode since Bilong9 has advised to somebody with the same issue. After that I have flashed KDZ US988 since I had already bootloader unlocked, then I installed again v300k file provided in the instruction. I don't have still carrier signal. Please, help me to resolve my issue with your advises, how can I bring back carrier signal? I don't want to brick my phone, may be the issue with modem, is there possibility of installing only modem seperatetly via TWRP, will this work? What if I install firmware in LG bridge, will this work and will I loose unlocked bootloader? Thank you all in advance.
Click to expand...
Click to collapse
I didn't have the same problem as you.
You could try to flash the stock v300k rom with LGUP to get to the beginning state (and lose unlock and twrp) to see if you get the signal back. Get the firmware here https://lg-firmwares.com/lg-mv300k-firmwares/firmwares/ . I have not done this and I am not an expert on this subject.

Thanks Defic, I will follow your advice, though I have done it last time with stock v300k21e, mine was v300k20e.

defic said:
I wanted to get rid of the korean rom bloatware (and korean text all over the place) so I DL partition flashed h930 EU Rom without xbl1, xbl2, modem, recovery and recoverybak with the patched LGUP. For some reason, I still lost recovery (maybe because I did not manage to do the button dance on first boot?). Then in Fastboot mode I reflashed TWRP, got in to twrp and rooted the phone again.
Calls and data are both working. But when booting the phone, it seems to take longer time than before to get sim signal (around 30 seconds after inserting PIN code). Also when I made my very first call, signal disappeared but came back after a reboot. It has not occured anymore. Also Lte Multiband selection engineering menu is not working, but that was kinda expected.
I kept korean xbl1 and xbl2 because I found a post by @bilong9 when he first discovered how to get signal back. I don't know if signal would work with only korean rom modem.
Click to expand...
Click to collapse
Is FM radio working on H930 firmware?

LGup V30DLL_Patched link is not working. :*(
Edit:
Rechecked and all links are down

So... I managed to get it working for awhile, then something happened...
I don't know if this will help but I installed an app called granular immersive mode and followed the instructions... then after some time my phone suddenly switched into airplane mode and when I switched airplane mode off I couldn't get a signal. So I rebooted the phone.... and still no signal. Tried to check the mobile network setting, network mode says null and couldn't search for provider, also tried the 4636 code and got into the setting found out that everything is dead, so I flashed back into stock (using LGUP refurbish), but still no signal. I, for some reason thought locking the bootloader back would help but no, it didn't help.
I'm on v300s.
{
"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"
}

[Guide] How to root your Samsung Galaxy A10 with Magisk [SM-A105xx]

THIS MIGHT WORK FOR YOUR DEVICE BUT IF ANY DAMAGE IS DONE TO YOUR DEVICE I AM NOT RESPONSIBLE! AND THIS WILL ONLY WORK ON A10. [SM-A105, SM-A107 AND MORE]
1. You need to install the exact firmware for your model onto your PC. [I recommend a website called updato or install samware and get the firmware there.]
2. Install Odin 3.14.1. If you already have it go to the next step.
3. Unlock your bootloader. If you have done this please go to the next step but if not please go to 3.a
3a. !UNLOCKING YOUR BOOTLOADER WILL FACTORY RESET YOUR DEVICE! - Go to settings and go to about phone, then tap the build number until a message comes on the bottom of the screen saying "You are now a developer!" or something close to that. Go to developer settings by going back to the settings menu and scrolling all the way down to see it. After going to developer options turn on "OEM Unlocking" and tap allow. Also just in case turn on USB Debugging. After that turn off your device. After your phone is turned off press "Volume Up"+ "Volume Down" and plug in a USB from your PC simultaneously, you should see a splash screen with a warning. Hold "Volume Up" for until 7 seconds or less and you should see another warning to confirm you want to unlock the bootloader. Press "Volume Up". You will get a warning when you boot up the phone, just press "Power".
4. After the phone booted up, do the normal setup. Then go to Chrome and download Magisk Manager.
5. Then, go to your pc, and locate the firmware you have downloaded and copy the AP tar file onto your phone.
6. Open magisk manager, tap install, and tap "Select and Patch a File".
7. Select the AP tar file you copied from your PC and wait for the process to be done.
8. You should see a new file called "magisk_patched.tar" and transfer the file to your PC.
9. Open Odin on your PC, and turn off your device and turn it on using "Volume Up", "Volume Down" and USB combination.
10. You should see the same warning sign. Just press "Volume Up" once. Do not hold it just press it once.
11. Your PC will make a sound alerting you that the phone has connected.
12. On the BL section on Odin, open your firmware location and select the file with BL in front of it.
13. On the AP section on Odin, open the "magisk_patched.tar" file you had transferred from the phone.
14. On the CP section on Odin, open your firmware location and select the file with CP in front of it.
15. On the CSC section on Odin, open your firmware location and select the file with CSC in front of it.
16. On Odin, look for a section called Options on the left-hand side. Click options, and turn off auto restart.
17. Click start and wait for the process to finish.
18. After the process is finished, please take the USB out.
19. !!THIS IS THE HARD PART!! - You need to hold down "Volume Down" and "Power". After the screen goes black immediately hold "Volume Up" and "Power". This will direct you to the stock recovery of the phone.
20. If the recovery says, "NO SYSTEM FOUND", don't worry as for then your phone is not A/B partitioned and that's okay and you will need to skip 21 for now and select Reboot System and do the normal setup. But if you can see options in the recovery, please use the "Volume keys" to scroll and "Power" to select. Select Wipe Data and confirm.
21. After the erasing process, just let the phone boot up, and do the setup.
22. Install Magisk Manager if your phone hasn't already downloaded it.
23. !!!FOR THE NON A/B PARTITIONED IF YOU ARE A/B PARTITIONED THEN PLEASE GO TO THE NEXT STEP!!! If you boot up normally - (System without magisk)
Booting up with "Volume Up" and "Power" - (System with magisk)
24. Enjoy Magisk!
If you have any questions please comment them down below!
Thanks to Topjohnwu for creating the method and MAKING magisk.

Downaroo said:
THIS MIGHT WORK FOR YOUR DEVICE BUT IF ANY DAMAGE IS DONE TO YOUR DEVICE I AM NOT RESPONSIBLE! AND THIS WILL ONLY WORK ON A10 ONLY [SM-A105xx].
1. You need to install the exact firmware for your model onto your PC. [I recommend a website called updato or install samware and get the firmware there.]
2. Install Odin 3.14.1. If you already have it go to the next step.
3. Unlock your bootloader. If you have done this please go to the next step but if not please go to 3.a
3a. !UNLOCKING YOUR BOOTLOADER WILL FACTORY RESET YOUR DEVICE! - Go to settings and go to about phone, then tap the build number until a message comes on the bottom of the screen saying "You are now a developer!" or something close to that. Go to developer settings by going back to the settings menu and scrolling all the way down to see it. After going to developer options turn on "OEM Unlocking" and tap allow. Also just in case turn on USB Debugging. After that turn off your device. After your phone is turned off press "Volume Up"+ "Volume Down" and plug in a USB from your PC simultaneously, you should see a splash screen with a warning. Hold "Volume Up" for until 7 seconds or less and you should see another warning to confirm you want to unlock the bootloader. Press "Volume Up". You will get a warning when you boot up the phone, just press "Power".
4. After the phone booted up, do the normal setup. Then go to Chrome and download Magisk Manager.
5. Then, go to your pc, and locate the firmware you have downloaded and copy the AP tar file onto your phone.
6. Open magisk manager, tap install, and tap "Select and Patch a File".
7. Select the AP tar file you copied from your PC and wait for the process to be done.
8. You should see a new file called "magisk_patched.tar" and transfer the file to your PC.
9. Open Odin on your PC, and turn off your device and turn it on using "Volume Up", "Volume Down" and USB combination.
10. You should see the same warning sign. Just press "Volume Up" once. Do not hold it just press it once.
11. Your PC will make a sound alerting you that the phone has connected.
12. On the BL section on Odin, open your firmware location and select the file with BL in front of it.
13. On the AP section on Odin, open the "magisk_patched.tar" file you had transferred from the phone.
14. On the CP section on Odin, open your firmware location and select the file with CP in front of it.
15. On the CSC section on Odin, open your firmware location and select the file with CSC in front of it.
16. On Odin, look for a section called Options on the left-hand side. Click options, and turn off auto restart.
17. Click start and wait for the process to finish.
18. After the process is finished, please take the USB out.
19. !!THIS IS THE HARD PART!! - You need to hold down "Volume Down" and "Power". After the screen goes black immediately hold "Volume Up" and "Power". This will direct you to the stock recovery of the phone.
20. If the recovery says, "NO SYSTEM FOUND", don't worry as for then your phone is not A/B partitioned and that's okay and you will need to skip 21 for now and select Reboot System and do the normal setup. But if you can see options in the recovery, please use the "Volume keys" to scroll and "Power" to select. Select Wipe Data and confirm.
21. After the erasing process, just let the phone boot up, and do the setup.
22. Install Magisk Manager if your phone hasn't already downloaded it.
23. !!!FOR THE NON A/B PARTITIONED IF YOU ARE A/B PARTITIONED THEN PLEASE GO TO THE NEXT STEP!!! If you boot up normally - (System without magisk)
Booting up with "Volume Up" and "Power" - (System with magisk)
24. Enjoy Magisk!
If you have any questions please comment them down below!
Click to expand...
Click to collapse
What about Samsung Galaxy A10s can you tell me please

Ragheb Aloqab said:
What about Samsung Galaxy A10s can you tell me please
Click to expand...
Click to collapse
I am sure you can, but before trying this method please take a full backup

works for a105m bit 5?

daniromerohn said:
works for a105m bit 5?
Click to expand...
Click to collapse
should work, but keep a backup just incase

Downaroo said:
THIS MIGHT WORK FOR YOUR DEVICE BUT IF ANY DAMAGE IS DONE TO YOUR DEVICE I AM NOT RESPONSIBLE! AND THIS WILL ONLY WORK ON A10. [SM-A105, SM-A107 AND MORE]
1. You need to install the exact firmware for your model onto your PC. [I recommend a website called updato or install samware and get the firmware there.]
2. Install Odin 3.14.1. If you already have it go to the next step.
3. Unlock your bootloader. If you have done this please go to the next step but if not please go to 3.a
3a. !UNLOCKING YOUR BOOTLOADER WILL FACTORY RESET YOUR DEVICE! - Go to settings and go to about phone, then tap the build number until a message comes on the bottom of the screen saying "You are now a developer!" or something close to that. Go to developer settings by going back to the settings menu and scrolling all the way down to see it. After going to developer options turn on "OEM Unlocking" and tap allow. Also just in case turn on USB Debugging. After that turn off your device. After your phone is turned off press "Volume Up"+ "Volume Down" and plug in a USB from your PC simultaneously, you should see a splash screen with a warning. Hold "Volume Up" for until 7 seconds or less and you should see another warning to confirm you want to unlock the bootloader. Press "Volume Up". You will get a warning when you boot up the phone, just press "Power".
4. After the phone booted up, do the normal setup. Then go to Chrome and download Magisk Manager.
5. Then, go to your pc, and locate the firmware you have downloaded and copy the AP tar file onto your phone.
6. Open magisk manager, tap install, and tap "Select and Patch a File".
7. Select the AP tar file you copied from your PC and wait for the process to be done.
8. You should see a new file called "magisk_patched.tar" and transfer the file to your PC.
9. Open Odin on your PC, and turn off your device and turn it on using "Volume Up", "Volume Down" and USB combination.
10. You should see the same warning sign. Just press "Volume Up" once. Do not hold it just press it once.
11. Your PC will make a sound alerting you that the phone has connected.
12. On the BL section on Odin, open your firmware location and select the file with BL in front of it.
13. On the AP section on Odin, open the "magisk_patched.tar" file you had transferred from the phone.
14. On the CP section on Odin, open your firmware location and select the file with CP in front of it.
15. On the CSC section on Odin, open your firmware location and select the file with CSC in front of it.
16. On Odin, look for a section called Options on the left-hand side. Click options, and turn off auto restart.
17. Click start and wait for the process to finish.
18. After the process is finished, please take the USB out.
19. !!THIS IS THE HARD PART!! - You need to hold down "Volume Down" and "Power". After the screen goes black immediately hold "Volume Up" and "Power". This will direct you to the stock recovery of the phone.
20. If the recovery says, "NO SYSTEM FOUND", don't worry as for then your phone is not A/B partitioned and that's okay and you will need to skip 21 for now and select Reboot System and do the normal setup. But if you can see options in the recovery, please use the "Volume keys" to scroll and "Power" to select. Select Wipe Data and confirm.
21. After the erasing process, just let the phone boot up, and do the setup.
22. Install Magisk Manager if your phone hasn't already downloaded it.
23. !!!FOR THE NON A/B PARTITIONED IF YOU ARE A/B PARTITIONED THEN PLEASE GO TO THE NEXT STEP!!! If you boot up normally - (System without magisk)
Booting up with "Volume Up" and "Power" - (System with magisk)
24. Enjoy Magisk!
If you have any questions please comment them down below!
Thanks to Topjohnwu for creating the method and MAKING magisk.
Click to expand...
Click to collapse
Does this work on the SM-A102U? Or is there any custom recovery for it?

Tyreethetruth said:
Does this work on the SM-A102U? Or is there any custom recovery for it?
Click to expand...
Click to collapse
Should work with any Samsung galaxy a10, so if it works, enjoy!

Odin keeps crashing when it is nearly complete
I have done this yet however it crashes when I follow your steps with a text box like "Odin Downloader has stop working". I have even gone to the extent where I have turned the magisk_patched.tar into a .tar.md5 file and still the same old error. How do I fix it?
If you require more info, I have a sm-a105fn/ds running android 9. Whenever it is on the "userdata" stage in odin, it crashes. I am using Odin 3 v3.13.1

error in boot and go back to download mode
Not working

I tried and once the flashing was done it rebooted to Download Mode instead and says "error verifying vbmeta image ok_not_signed (3)"

Bad Thread..
My older thread is way mor organized, and doesnt have the 16gb issue that you have... you just copied afanehs thread and made it look bad..

cmz6996 said:
Bad Thread..
My older thread is way mor organized, and doesnt have the 16gb issue that you have... you just copied afanehs thread and made it look bad..
Click to expand...
Click to collapse
I'm sorry, I wasn't copying as I thought of it myself but you're right it has the same steps as afanehs thread. Your thread is more organized and mine doesn't fix the 16gb issue that i had. I'm sorry for the inconvenience

Downaroo said:
I'm sorry, I wasn't copying as I thought of it myself but you're right it has the same steps as afanehs thread. Your thread is more organized and mine doesn't fix the 16gb issue that i had. I'm sorry for the inconvenience
Click to expand...
Click to collapse
No worries, I was abit rough, but try and fix it up. GL In the future!

What to do if it is stuck in recovery in odin. Help me please

.

I have a samsung galaxy a10e sm-a102u and I don't have oem unlocking as an option. Please help

[HOW-TO-ROOT] [G770F/DS] Galaxy S10 Lite International Model

Models:
SM-G770F or SM-G770F/DS
Frequently used key combinations keys:
FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.
Some facts:
1. S10 Lite uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S10 Lite uses A-only partition which means there is only one set of system partition.
3. S10 Lite uses 2 stage init (2SI).
4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).
Tools needed:
On your computer:
1. Odin 3.14.4 or newer
2. Samsung Android USB driver
3. SamFirm or other tools/websites to download official firmwares
4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
On your device:
1. Magisk Manager (Canary builds)
Stage 1: Know your model and carrier code (CSC)
1. Open "Settings"
2. Go to "About phone" -> "Software information"
3. Pay attention to "Service provider SW ver."
4. Starting with "SM-", for example "SM-G770F", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OXM_PHE". The second 3-letter code "PHE" is your CSC.
6. Remember your model and CSC.
Stage 2: Unlock the bootloader
WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
1. Open "Settings"
2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
11. Repeat step 6.
12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
13. You will see "Downloading" screen. On the top left, there are some important info.
14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
(Stage 4 and below are method to root your phone using your own odin files, if you wish to use a prepatched for a faster way to get root, go to OPTIONAL)
Stage 4: Obtain the official firmware and upgrade
1. Open SamFirm
2. Type in your model and your region (CSC) and click "Check Update"
3. "Download" and you will get a zip file.
4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
5. Check the version code, for example (G770FXXU2BTD2). The last 4 letters (BTD2) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
Your data will be preserved if you do it right but it is good to have a backup.
6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
Stage 5: Extract boot (kernel) image from firmware
If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
1. Extract boot.img.lz4 from the AP file.
2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
Stage 6: Patch the boot (Kernel) image via Magisk
1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
2. Open Magisk Manager.
3. Click top-right "Install" button
4. Make sure "Recovery Mode" is off in Options.
5. Click "Next" and select "Select and Patch a File" in Method.
6. Select the file you transferred to your phone in step 1.
7. Click "Next" and "LET'S GO".
8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
9. Reboot the device to DOWNLOAD mode.
10. Open Odin, put patched file to AP slot and then click "Start".
11. After reboot, Magisk is installed and you will have the root access.
HOW TO upgrade the firmware
Repeat stage 4-6.
(OPTIONAL) Use prepatched magisk boot
1. Make sure that the model and firmware version of the pre-patched image is the exact SAME as yours.
2. Open Odin on your computer.
3. Reboot your device to DOWNLOAD mode.
4. Put pre-patched image into AP slot.
5. "Start"
BEWARE: PREPATCHED BOOT ONLY TESTED ON BTD2 ONEUI 2.1 FIRMWARE
(https://drive.google.com/file/d/1chFXa2w_t2EgbfQIiVDOVR2KUeiwFpUs/view?usp=sharing)
Telegram Support Chat: https://t.me/joinchat/FrDuSBgUxDGSZ1vVmej7fw

*reserved*

Thank you for this amazing guide and the file without which it would not have been possible.

Be sure to join my TG group, if you are interested in AOSP, there's a lineage build testing currently running.

Thanks for this.
But it really is the most difficult way to root i have seen.. I'm not sure how many will try all this just to root a phone.

Awesome

sosimple said:
Thanks for this.
But it really is the most difficult way to root i have seen.. I'm not sure how many will try all this just to root a phone.
Click to expand...
Click to collapse
This will be done by absolutely everyone who wants to root his Galaxy S10 Lite. ABSOLUTLEY EVERYONE!

hey guys i ve just bought s10 lite and rootted it with method upside. but i was apple user for a 3 years before that i used to note 3-4-5 series and it was easy to rootable also i was getting useable stuff like grenify or nice equaliser type apps. ı would like to know how can i enjoy my phone with rooted ? for example i have iphone x with me still and its jailbreaked and there are repo sites that help to get to download app or modules to make you happy with your phone. do we have such stuff in android going on right now ? thanks again for rooting and helps.

4TheBesT said:
hey guys i ve just bought s10 lite and rootted it with method upside. but i was apple user for a 3 years before that i used to note 3-4-5 series and it was easy to rootable also i was getting useable stuff like grenify or nice equaliser type apps. ı would like to know how can i enjoy my phone with rooted ? for example i have iphone x with me still and its jailbreaked and there are repo sites that help to get to download app or modules to make you happy with your phone. do we have such stuff in android going on right now ? thanks again for rooting and helps.
Click to expand...
Click to collapse
If you are not sure what's the purpose of rooting a phone you shouldn't be doing it. "To make you happy with your phone" is a really subject question with no right answer, that depends on your specific needs.
If you ask about modules check out Magisk Modules.
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
Hello, just to confirm that the steps detailed in this guide works, thanks OP, at least this gives us more freedom.
{
"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"
}

no able to root with this method ! .. step ( v-meta disabler ) with system CP,AP,HOME CSC fail with official binary .. i follow you're steps !
i guess the file v-meta disabler u have attached is not compatible with my device ?! and yes i have same you'res BTD2 ONEUI 2.1 FIRMWARE

teenoo said:
This will be done by absolutely everyone who wants to root his Galaxy S10 Lite. ABSOLUTLEY EVERYONE!
Click to expand...
Click to collapse
In my case, I flashed latest FW (July 2020), Magisk Manager (the "install" buttons were not visible at first, but after some reboots they were). Created patched boot with Magisk Manager, unlocked bootloader (in settings & in bootloader), flashed modified boot image and it worked. At first boot, it restarted, and wen back to recovery, stating that system is corrupted, gave option to factory reset, so I did, it restarted again, and again, and then it booted fine. No VMBETA flashing needed. The trick, was (I suppose) doing the factory reset after flashing the modded kernel. Finally, when the phone booted, I did the usual first-run setup and enabled developer settings / adb installed Magisk Manager - it completed the setup, everything was fine after that.

Is there any way to unlock the bootloader and root SM-G770U1?

kamill85 said:
In my case, I flashed latest FW (July 2020), Magisk Manager (the "install" buttons were not visible at first, but after some reboots they were). Created patched boot with Magisk Manager, unlocked bootloader (in settings & in bootloader), flashed modified boot image and it worked. At first boot, it restarted, and wen back to recovery, stating that system is corrupted, gave option to factory reset, so I did, it restarted again, and again, and then it booted fine. No VMBETA flashing needed. The trick, was (I suppose) doing the factory reset after flashing the modded kernel. Finally, when the phone booted, I did the usual first-run setup and enabled developer settings / adb installed Magisk Manager - it completed the setup, everything was fine after that.
Click to expand...
Click to collapse
I was about to give up on the July update until I read this and tried a few more things. Bad internet caused missing "Install" buttons and I tried patched the WHOLE AP...instead of just patching a boot.tar like in Stage 5. So gooder internet, Odin-ing only the AP with the Magisk patched boot.tar, another wipe,
Code:
adb install .\MagiskManager-v7.5.1.apk
and I was rooty tooty.
I didn't care about burning everything on the phone. I think that some of the extra steps here were for trying to minimize the wipes. Thanks for the extra hope @kamill85 !

Are there download links for official images somewhere without paying? Everywhere i searched you needed to sign in and pay..
Thanks,

SamFirm
sosimple said:
Are there download links for official images somewhere without paying? Everywhere i searched you needed to sign in and pay..
Thanks,
Click to expand...
Click to collapse
Did you look up SamFirm like in the instructions? It pointed me to this page: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 That says it's deprecated but it was able to get me the July 2020 FW for the S10e. I didn't try the other thing, Updato that it points you to. I ran the exe in the zip and pushed a few buttons and it worked for me. No waiting 20 hours. Hope that helps!

dim42 said:
Did you look up SamFirm like in the instructions? It pointed me to this page: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 That says it's deprecated but it was able to get me the July 2020 FW for the S10e. I didn't try the other thing, Updato that it points you to. I ran the exe in the zip and pushed a few buttons and it worked for me. No waiting 20 hours. Hope that helps!
Click to expand...
Click to collapse
Thanks. What Deprecated meant? What iis the difference from original?

the show stopper said:
Is there any way to unlock the bootloader and root SM-G770U1?
Click to expand...
Click to collapse
+1
Also curious if anyone's gotten this working with the US version

So if i do this ill never ever be able to use Samsung pay ever again?

Vaughnn said:
Models:
SM-G770F or SM-G770F/DS
Frequently used key combinations keys:
FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.
Some facts:
1. S10 Lite uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S10 Lite uses A-only partition which means there is only one set of system partition.
3. S10 Lite uses 2 stage init (2SI).
4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).
Tools needed:
On your computer:
1. Odin 3.14.4 or newer
2. Samsung Android USB driver
3. SamFirm or other tools/websites to download official firmwares
4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
On your device:
1. Magisk Manager (Canary builds)
Stage 1: Know your model and carrier code (CSC)
1. Open "Settings"
2. Go to "About phone" -> "Software information"
3. Pay attention to "Service provider SW ver."
4. Starting with "SM-", for example "SM-G770F", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OXM_PHE". The second 3-letter code "PHE" is your CSC.
6. Remember your model and CSC.
Stage 2: Unlock the bootloader
WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
1. Open "Settings"
2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
11. Repeat step 6.
12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
13. You will see "Downloading" screen. On the top left, there are some important info.
14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
(Stage 4 and below are method to root your phone using your own odin files, if you wish to use a prepatched for a faster way to get root, go to OPTIONAL)
Stage 4: Obtain the official firmware and upgrade
1. Open SamFirm
2. Type in your model and your region (CSC) and click "Check Update"
3. "Download" and you will get a zip file.
4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
5. Check the version code, for example (G770FXXU2BTD2). The last 4 letters (BTD2) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
Your data will be preserved if you do it right but it is good to have a backup.
6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
Stage 5: Extract boot (kernel) image from firmware
If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
1. Extract boot.img.lz4 from the AP file.
2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
Stage 6: Patch the boot (Kernel) image via Magisk
1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
2. Open Magisk Manager.
3. Click top-right "Install" button
4. Make sure "Recovery Mode" is off in Options.
5. Click "Next" and select "Select and Patch a File" in Method.
6. Select the file you transferred to your phone in step 1.
7. Click "Next" and "LET'S GO".
8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
9. Reboot the device to DOWNLOAD mode.
10. Open Odin, put patched file to AP slot and then click "Start".
11. After reboot, Magisk is installed and you will have the root access.
HOW TO upgrade the firmware
Repeat stage 4-6.
(OPTIONAL) Use prepatched magisk boot
1. Make sure that the model and firmware version of the pre-patched image is the exact SAME as yours.
2. Open Odin on your computer.
3. Reboot your device to DOWNLOAD mode.
4. Put pre-patched image into AP slot.
5. "Start"
BEWARE: PREPATCHED BOOT ONLY TESTED ON BTD2 ONEUI 2.1 FIRMWARE
(https://drive.google.com/file/d/1chFXa2w_t2EgbfQIiVDOVR2KUeiwFpUs/view?usp=sharing)
Telegram Support Chat: https://t.me/joinchat/FrDuSBgUxDGSZ1vVmej7fw
Click to expand...
Click to collapse
Anyway to get to pass the safety nets?

Yes i pass safety net, but i use systemizer and with it i cant pass.
When I switch off systemizer in magisk I pass safety net

[Mi A2][Unlock Bootloader][TWRP][ROM] Ressurection Remix v8.6.5 | Xiaomi Mi A2 (jasmine_sprout)

Greetings Readers,
Today you will learn how to unlock bootloader of your Mi A2 device along with flashing latest(as per now) TWRP(v3.5.0) subsequently flashing the latest(as per now) Resurrection remix OS(v8.6.5).
Your Phone's warranty would void. So you might wanna think again before going forward.
All of your device data would be wiped so create a backup beforehand.
Your device might get stuck in bootloop.
Your device might get damaged.
I won't be responsible for any ruckus you create.​
Pre-requisites:
- Your phone's battery must be charged at least to 70%.​- Keep your PC plugged into power as well.​- Be confident.​Lets Begin​
Things Needed:
- Xiaomi Mi A2​- PC(Windows recommended)​- Data Cable​​Files Needed​
File NameDownload LinkInstructionsRROS-Q-Final v8.6.5Resurrection Remix Downloads- Scroll down until you see a file: RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip
{
"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"
}
- Now click on this file name to start the download.
*Gapps included in this ROM file​twrp v3.5.0Download twrp-3.5.0_9-0-jasmine_sprout.img-Click on the blue colored text: Download twrp-3.5.0_9-0-jasmine_sprout.img
twrp-installer v3.5.0Download twrp-installer-3.5.0_9-0-jasmine_sprout.zip- Click on the blue colored text: Download twrp-installer-3.5.0_9-0-jasmine_sprout.zip
platform-tools v31.0.0SDK Platform Tools release notes | Android Developers- Scroll down a bit and under Downloads section click on blue colored text: Download SDK Platform-tools for windows
- Now click on checkbox and then click on the download button to start the download:
Mi Unlock Tool v4.5.813.51miflash_unlock-en-4.5.813.51.zip-​Dm Verity Force Encrypt Disabler v11.02.2020Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip-​
*all the above given download links are from the respective official websites. So, download them all on your PC.
Preparing Mi A2​
Enabling OEM Unlock and USB Debugging:
- Navigate to Settings > About phone.​~ Tap on Build number 7 times.​- Navigate to Settings > System > Developer options.​~ Enable the 'OEM unlocking' and 'USB debugging' switch.​- Switch off your phone.​- Press the Power button and Volume Down button simultaneously, until you see the fastboot screen.​- Connect the phone to your PC using USB data cable.​
Working on PC​
Installing drivers:
- Extract the 'miflash_unlock-en-4.5.813.51.zip' file.​- Inside this file double click on 'miflash_unlock.exe' file.​*we are not installing this tool. We are just using it for installing our device drivers.​​
​- On the top right corner click on the settings gear icon.​​
​- Now click on 'Check' button.​​
​*it will ask for Administration Access twice.​- Click on 'Yes' both the times.​*a new dialogue box appears asking you to connect your device again.​- Unplug your device and connect it again and the drivers will get installed.​​Unlocking Bootloader:
- Extract the 'platform-tools_r31.0.0-windows.zip' file.​- Inside this file will be a folder platform-tools. Open it.​- Now in the address bar type 'cmd' and hit enter.​​
​​*we did this in order to open cmd to this location. So that our future commands are accessible.​- In the cmd window type the command:​
Code:
fastboot devices
​*it will display our device, something like this:​​
​​/* In case your device is not displayed.​Try installing drivers again. */​- Enter the command:​
Code:
fastboot oem unlock
​*this unlocks the bootloader temporarily​/* A screen pops up on our phone.​Navigate using volume buttons and select using power button.​Our phone reboots.​Set up everything haphazardly.​Navigate to Settings and enable Developer options.​Enable USB debugging in Developer options.​Switch off your phone and boot into fastboot mode again. ​Enter the command fastboot devices in order to check if our device is successfully connected. */​- Enter the command:​
Code:
fastboot oem unlock_critical
​*this will unlock our bootloader permanently​/* Once again a screen pops up on our phone asking for a confirmation.​Confirm it and phone reboots.​Once again set it up haphazardly.​Enable Developer options and USB debugging subsequently.​Boot into fastboot mode again. */​- Enter the command:​
Code:
fastboot oem device-info
*this command will confirm if our device' bootloader has been unlocked or not​​
Installing twrp:
-Enter command:​
Code:
fastboot format userdata
*this command wipes Internal Storage of our phone​-Enter command:​
Code:
fastboot format cache
*this command wipes cache of our phone​-Now enter the command fastboot boot and drag and drop the 'twrp-3.5.0_9-0-jasmine_sprout.img' file into cmd and hit enter.​*we did this so that command file will know the location of our twrp img file and hence execute the command​​/* Our phone will boot into recovery mode.​Transfer 'twrp-3.5.0_9-0-jasmine_sprout.img', 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip', 'RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip' to Mi A2's Internal storage. */​
Working on Phone​​- Tap on Install > Install Image(bottom right corner) button.​- Select 'twrp-3.5.0_9-0-jasmine_sprout.img' file.​- Now in 'Select Partition to Flash Image:' scroll down and select the 'Install Recovery Ramdisk' option.​- Swipe right to flash.​- Press back once flashing is complete.​*temporary installed twrp in Slot B​​- Go to Home > Wipe > Advanced Wipe.​- Tap on every checkbox except the 'Internal Storage'.​- Swipe right to wipe.​*we wiped the stock rom from Slot B​​- Go to Home > Reboot > Slot A.​- Go to Home > Install.​- Select the file 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' and swipe right to flash.​*we temporary installed twrp in Slot A​​- Go to Home > Reboot > Recovery.​- Tap on Wipe > Advanced Wipe.​- Tap on every checkbox except the 'Internal Storage'.​*we wiped stock rom from Slot A​​- Go to Home > Install.​- Select the 'RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip' ROM file and swipe right to flash.​*this might take some time​- When flashing is finished tap on 'Wipe Cache/Dalvik' button.​*we flashed RROS rom in Slot A​​- Go to Home > Install.​- Select the 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' and swipe right to flash it again.​*we installed twrp in Slot A again as it got wiped when we flashed our rom​​- Go to Home > Reboot > Slot B.​- Go to Home > Install.​- Select the 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' file and swipe right to flash.​- Head back to Home > Wipe > Format Data.​- Type 'yes' and tap on the Tick button.​- Go to Home > Reboot > Recovery.​- Go to Mount and tap on 'Enable MTP' button in the lower right corner (Do not press it if it's showing 'Disable MTP').​- Now transfer the 'Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip' file into your phone's internal storage using your PC.​- Go to Install and select the file 'Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip' and swipe right to flash.​*we installed twrp permanently in slot B​- Select the 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' and swipe right to flash it again.​- Head to Home > Reboot > System.​​​Congratulations we have successfully installed RROS on our Mi A2​
How to boot into recovery:
Method 1: using Software
- Navigate to Settings > Resurrection tools > System > Power dialog.​- Scroll down and under the 'BUTTONS' section, enable the 'Enable advanced restart' switch.​-Now long press the power button and then select Advanced from the menu to see all the options.​Method 2: using Hardware
- Switch off the phone.​- Press Power button and Volume Up button simultaneously.​- Just as you see Android Boot Splash Screen, press the Volume Up button twice.​​Bugs & Fixes​
BugsFixesCamera isn't recording videos.- Head to Camera Settings.
- In 'Video quality' select 'FHD 1080p, 30fps' option.Phone stuck on boot splash screen when battery drains completely.
*this might occur for the very first time only​- Boot into recovery using Power + Volume Up buttons.
- On twrp home screen, go to Reboot > Power Off.
- Switch On your phone by long pressing power button.Sometimes excessive tweaking delays device wake up.- Reboot SystemUI.
- Let the phone sit for a minute.Camera sounds not turning off.- Root your device using latest Magisk app.
- Now, install the module 'Disable screenshot and camera sounds'.
- Reboot your device.​
Special Thanks to:
RROS Team for providing such a wonderful ROM.
TeamWin - TWRP for providing the twrp files.
@Zackptg5 for the Disable Dm-Verity file.
And to every person who made this possible.
Thankyou for Reading​

You can turn on developer option turn on oem unlock. You can register on miui. Provide your mobile details they will give you unlock code. You can say you are developer and you want to unlock it.
Unlock code for android smartphone simcard
How to unlock android smartphone, what is mobile locking & how to check smartphone is locked or not. How to get sim network unlock code for mobile, different kind of cellphone carrier unlock codes. Requirement of generating sim unlock code from imei.
mobile-cellphones.blogspot.com

YOU TOMUCH WRITE, HUHH....
MY DEVICE XIAOMI MI A2 RAM 6 gb ROM 128 GB, THIS MONT I DOWNLOAD AND INSTAL ALL KIND JANK AND FINALLY I WIPE ALL THEN YESTERDAY HERE I DOUNLOAD RROS 8.6.7 OFFICIAL VANILLA,
HOW I INSTALL IT ON WIPED MI A2?
I USE APP RUBBIT XIAOMI ADB/FastbootTools.exe ONLY,
I INSTALL IMAGES OF OFICIAL FIRMWARE Q AND PBRP recovery NOT TO boot BUT TO Recovery, UNBELIVABLE BUT IT HAPPEN. AFTER FEW TIMES I ACCESS TO SDcard OF MI A2 FROM MY TOSHIBA FAKE NOTEBOOK OF YEAR 2008 WITH FAKE WINDOWS7 AND I COPY FILE RROS 8.6.7 FIRMWARE TO TWRP FOLDER CREATED WITH PBRP, ALSO FOLDER Tools FROM PBRP recovery.img
I INSTALL RROS TO a AND TO b, ALSO INSTALL Magisk, Supersu, AND NOT ONES, I DID it UNTILL SUCCESS.
I WANT TO TELL THAT IS AMAZING ROM NO GAPS I LOVE IT, BUT IT CHEAT ME WITH UPDATE TO LATEST RROS 8.6.9 YOU SEE 69 POSE WITH GAPPS, HUHH..
I AGAIN DELETE WIPE ALL RROS AND REINSTALL RROS 8.6.7 VANILLA NO WITH GOOGLE 69.
PLESE SEND TO VANILLA UPDATES WITH VANILLA AND TO RROS WITH GAPPS SEND UPDATES RROS GAPPS, IT NOT THE SAME.
AND PLEASE GIVE FILE boot.img FOR RROS 8.6.7 or 8.6.0 or 8.6.5 BECOUSE MAGISK NEED FILE boot.img AND I DO NOT KNOW WHY YOU SMART DEVELOPERS NEVER SHARE FILE boot.img WITH PRASED ROMS, THANK YOU.
NOW AFTER INSTALLING YOUR TWRP CAN NOT START IT STACK ON LOGO, NOT GOOD YOUR TWRP,
NEED boot_patched.img OF THIS RROS.
OK, I TRY AGAIN INSTALL TWRP 3.5.2 TO Recovery AND AGAIN INSTALL TWRP 3.5.2 TO boot AND INSTALL MAISK AND MagiskManagerRecovery TO ANABLE ROOT AND REBOOT AND IT STILL RUN RR LOGO
* * * * *
RROS 8.6.7 THE BEST ROM IT HAVE ANYTHING WE NEED EVEN BUTTON REMAPER IN THE SETTING, ALL MY BELOVED GAMES CAN RUN WITH THIS RROS ANDROID 10, EVEN J2MeRunner AND IT GAME LIKE Heroes Lore Wind of Soltia AND SuperWaterBomber, ALSO J2MeLoader WORKING AND CAN RUN ALL Java Jar Games, RROS THE BEST BUT I NEED ROOT FOR MY FRIEND LuckyPatcher
* * * * *
SO MANY TALKING ABOUT TOOLS AND adb TO UNLOCK BOOTLOADER,
I AM SORRY I AM SMARTER OR ALL AROUND MAD, JUST GO DEVELOPER OPTION AND TURN ON UNLOCK BOOTLOADER.
AND IN Xiaomi ADB/FastbootTools CLICK UNLOCK AND IT SAY ALREADY UNLOCKED THEN FLASH ANYTHING. I DID IT USING GARBAGE JUNK NOTEBOOK TOSHIBA J70 CHINES CLONE AND THERE SMARTERS PEOPLE USING LATEST WINDOWS AND PC ADVICE TO US adb MANY JUNK ZIP FILES I USE APP SIZE 2.9 MB AND NOTHING ELSE.
* * * * *
GOOD/ GOOD TWRP 5.3.2 AND PATCH ALSO GOOD BUT I MISTAKE AND INSTALL TWRP TO a AND TO b NOW I HAVE TWRP IN a AND b,
PHONE BOOTLOOP WHEN START a, AND WORKING OK WHEN START b, I NO UNDERSTAND WHY NOT YET I GET ROOT, SUPERSU NO WORKING, MAGISK EVERY 3 OPTIONS YES BUT INSTALLED SHOW N/A, I INSTALL MAGISK FROM TWRP HUNDRED TIMES AND NOT YET ROOT, IT ASKED ME FOR boot.img
MAYBE NEED PATCH TWRP.. AND INSTAL IT IN 101 TIME..

eleven.co said:
Greetings Readers,
Today you will learn how to unlock bootloader of your Mi A2 device along with flashing latest(as per now) TWRP(v3.5.0) subsequently flashing the latest(as per now) Resurrection remix OS(v8.6.5).
Your Phone's warranty would void. So you might wanna think again before going forward.
All of your device data would be wiped so create a backup beforehand.
Your device might get stuck in bootloop.
Your device might get damaged.
I won't be responsible for any ruckus you create.​
Pre-requisites:
- Your phone's battery must be charged at least to 70%.​- Keep your PC plugged into power as well.​- Be confident.​Lets Begin​
Things Needed:
- Xiaomi Mi A2​- PC(Windows recommended)​- Data Cable​​Files Needed​
File NameDownload LinkInstructionsRROS-Q-Final v8.6.5Resurrection Remix Downloads- Scroll down until you see a file: RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip
View attachment 5226269
- Now click on this file name to start the download.
*Gapps included in this ROM file​twrp v3.5.0Download twrp-3.5.0_9-0-jasmine_sprout.img-Click on the blue colored text: Download twrp-3.5.0_9-0-jasmine_sprout.imgView attachment 5226271twrp-installer v3.5.0Download twrp-installer-3.5.0_9-0-jasmine_sprout.zip- Click on the blue colored text: Download twrp-installer-3.5.0_9-0-jasmine_sprout.zipView attachment 5226273platform-tools v31.0.0SDK Platform Tools release notes | Android Developers- Scroll down a bit and under Downloads section click on blue colored text: Download SDK Platform-tools for windows
View attachment 5226281
- Now click on checkbox and then click on the download button to start the download:
View attachment 5226285Mi Unlock Tool v4.5.813.51miflash_unlock-en-4.5.813.51.zip-​Dm Verity Force Encrypt Disabler v11.02.2020Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip-​
*all the above given download links are from the respective official websites. So, download them all on your PC.
Preparing Mi A2​
Enabling OEM Unlock and USB Debugging:
- Navigate to Settings > About phone.​~ Tap on Build number 7 times.​- Navigate to Settings > System > Developer options.​~ Enable the 'OEM unlocking' and 'USB debugging' switch.​- Switch off your phone.​- Press the Power button and Volume Down button simultaneously, until you see the fastboot screen.​- Connect the phone to your PC using USB data cable.​
Working on PC​
Installing drivers:
- Extract the 'miflash_unlock-en-4.5.813.51.zip' file.​- Inside this file double click on 'miflash_unlock.exe' file.​*we are not installing this tool. We are just using it for installing our device drivers.​​View attachment 5226331​​- On the top right corner click on the settings gear icon.​​View attachment 5226333​​- Now click on 'Check' button.​​View attachment 5226335​​*it will ask for Administration Access twice.​- Click on 'Yes' both the times.​*a new dialogue box appears asking you to connect your device again.​- Unplug your device and connect it again and the drivers will get installed.​​Unlocking Bootloader:
- Extract the 'platform-tools_r31.0.0-windows.zip' file.​- Inside this file will be a folder platform-tools. Open it.​- Now in the address bar type 'cmd' and hit enter.​​View attachment 5226371​​*we did this in order to open cmd to this location. So that our future commands are accessible.​- In the cmd window type the command:​
Code:
fastboot devices
​*it will display our device, something like this:​​View attachment 5226381​​/* In case your device is not displayed.​Try installing drivers again. */​- Enter the command:​
Code:
fastboot oem unlock
​*this unlocks the bootloader temporarily​/* A screen pops up on our phone.​Navigate using volume buttons and select using power button.​Our phone reboots.​Set up everything haphazardly.​Navigate to Settings and enable Developer options.​Enable USB debugging in Developer options.​Switch off your phone and boot into fastboot mode again. ​Enter the command fastboot devices in order to check if our device is successfully connected. */​- Enter the command:​
Code:
fastboot oem unlock_critical
​*this will unlock our bootloader permanently​/* Once again a screen pops up on our phone asking for a confirmation.​Confirm it and phone reboots.​Once again set it up haphazardly.​Enable Developer options and USB debugging subsequently.​Boot into fastboot mode again. */​- Enter the command:​
Code:
fastboot oem device-info
*this command will confirm if our device' bootloader has been unlocked or not​​View attachment 5226413​
Installing twrp:
-Enter command:​
Code:
fastboot format userdata
*this command wipes Internal Storage of our phone​-Enter command:​
Code:
fastboot format cache
*this command wipes cache of our phone​-Now enter the command fastboot boot and drag and drop the 'twrp-3.5.0_9-0-jasmine_sprout.img' file into cmd and hit enter.​*we did this so that command file will know the location of our twrp img file and hence execute the command​​/* Our phone will boot into recovery mode.​Transfer 'twrp-3.5.0_9-0-jasmine_sprout.img', 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip', 'RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip' to Mi A2's Internal storage. */​
Working on Phone​​- Tap on Install > Install Image(bottom right corner) button.​- Select 'twrp-3.5.0_9-0-jasmine_sprout.img' file.​- Now in 'Select Partition to Flash Image:' scroll down and select the 'Install Recovery Ramdisk' option.​- Swipe right to flash.​- Press back once flashing is complete.​*temporary installed twrp in Slot B​​- Go to Home > Wipe > Advanced Wipe.​- Tap on every checkbox except the 'Internal Storage'.​- Swipe right to wipe.​*we wiped the stock rom from Slot B​​- Go to Home > Reboot > Slot A.​- Go to Home > Install.​- Select the file 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' and swipe right to flash.​*we temporary installed twrp in Slot A​​- Go to Home > Reboot > Recovery.​- Tap on Wipe > Advanced Wipe.​- Tap on every checkbox except the 'Internal Storage'.​*we wiped stock rom from Slot A​​- Go to Home > Install.​- Select the 'RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip' ROM file and swipe right to flash.​*this might take some time​- When flashing is finished tap on 'Wipe Cache/Dalvik' button.​*we flashed RROS rom in Slot A​​- Go to Home > Install.​- Select the 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' and swipe right to flash it again.​*we installed twrp in Slot A again as it got wiped when we flashed our rom​​- Go to Home > Reboot > Slot B.​- Go to Home > Install.​- Select the 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' file and swipe right to flash.​- Head back to Home > Wipe > Format Data.​- Type 'yes' and tap on the Tick button.​- Go to Home > Reboot > Recovery.​- Go to Mount and tap on 'Enable MTP' button in the lower right corner (Do not press it if it's showing 'Disable MTP').​- Now transfer the 'Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip' file into your phone's internal storage using your PC.​- Go to Install and select the file 'Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip' and swipe right to flash.​*we installed twrp permanently in slot B​- Head to Home > Reboot > System.​​​Congratulations we have successfully installed RROS on our Mi A2​
How to boot into recovery:
Method 1: using Software
- Navigate to Settings > Resurrection tools > System > Power dialog.​- Scroll down and under the 'BUTTONS' section, enable the 'Enable advanced restart' switch.​-Now long press the power button and then select Advanced from the menu to see all the options.​Method 2: using Hardware
- Switch off the phone.​- Press Power button and Volume Up button simultaneously.​- Just as you see Android Boot Splash Screen, press the Volume Up button twice.​​Bugs & Fixes​
BugsFixesCamera isn't recording videos.- Head to Camera Settings.
- In 'Video quality' select 'FHD 1080p, 30fps' option.Phone stuck on boot splash screen when battery drains completely.
*this might occur for the very first time only​- Boot into recovery using Power + Volume Up buttons.
- On twrp home screen, go to Reboot > Power Off.
- Switch On your phone by long pressing power button.Sometimes excessive tweaking delays device wake up.- Reboot SystemUI.
- Let the phone sit for a minute.Camera sounds not turning off.- Root your device using latest Magisk app.
- Now, install the module 'Disable screenshot and camera sounds'.
- Reboot your device.​
Special Thanks to:
RROS Team for providing such a wonderful ROM.
TeamWin - TWRP for providing the twrp files.
@Zackptg5 for the Disable Dm-Verity file.
And to every person who made this possible.
Thankyou for Reading​
Click to expand...
Click to collapse

THE BEST ROM THANK YOU.

ALWAYS PROBLEM UNABLE CREATE CACH OR SYSTEM SOLVED BY WIPING ALL EXEPT ENTERNAL AND INSTALLING TO RAM DISC NOT TWRP 3.5.0_9 BUT TWRP 3.2.3 AND IT FLASHING CLEARLY TO CURRENT SLOT FROM a TO a, FROM b TO b WITHOUT RED LETTERS ABOUT ERROR, SO IN ORDER to FLASH RROS AND PATCH AND MAGISK NEED TWRP 3.2.3 jasmine sprout.img
И НИКАКИХ ТАНЦЕВ С БУБНОМ,
НУЖЕН ЗАЯЦ В УШАНКЕ 2.9 mb.exe И TWRP 3.2.3, ПРОШИВКА СУПЕР

LUCY YISRAEL said:
ALWAYS PROBLEM UNABLE CREATE CACH OR SYSTEM SOLVED BY WIPING ALL EXEPT ENTERNAL AND INSTALLING TO RAM DISC NOT TWRP 3.5.0_9 BUT TWRP 3.2.3 AND IT FLASHING CLEARLY TO CURRENT SLOT FROM a TO a, FROM b TO b WITHOUT RED LETTERS ABOUT ERROR, SO IN ORDER to FLASH RROS AND PATCH AND MAGISK NEED TWRP 3.2.3 jasmine sprout.img
И НИКАКИХ ТАНЦЕВ С БУБНОМ,
НУЖЕН ЗАЯЦ В УШАНКЕ 2.9 mb.exe И TWRP 3.2.3, ПРОШИВКА СУПЕР
Click to expand...
Click to collapse
Thankyou for your suggestions and corrections. I'm glad that you did it.

How To Guide Samsung Galaxy A54 5G [Root Stock ROM with Magisk]

WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel

Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
{
"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"
}
"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1.
"Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted.
"App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)
"App > Installed" shows the currently installed version of the Magisk app​

V0latyle said:
Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
View attachment 5893171​"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1.​"Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted.​"App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)​"App > Installed" shows the currently installed version of the Magisk app​
Click to expand...
Click to collapse
thank you, ive adjusted the how-to to your recommendations

Hello,
What about Knox with this method ??
Thanks

leosoftstudios said:
Hello,
What about Knox with this method ??
Thanks
Click to expand...
Click to collapse
I think this easily trips it. Cant confirm, because the usual system information in the bootloader doesnt show up for me. I tried using Samsung Pass with zygisk + shamiko (tried to activate anything samsung related in the denylist) but i just get the message that "you cannot use samsung pass on a rooted device", so iam not even getting past that.

Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.

terry_mccann said:
Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.
Click to expand...
Click to collapse
Funny how this pops up in every thread here like people get paid to go to a forum for custom roms and then leave their opinion, why a custom rom is useless...just why? how do you people even get here, arent you in the totally wrong place?
and to settle the argument: install a custom rom to get rom updates beyond the manufacturers lifetime support, simple as that. faster security updates, debloating, etc, dont get me started.

Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!

draykhar said:
Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!
Click to expand...
Click to collapse
I guess the CSC is country/provider dependend. Maybe your mobile shop got the device from another country or so? Try to check the model number (check 'SM-A546B' for the last letter), I found some roms with OYN as CSC with this model of the A54 here: https://samfrew.com/model/SM-A546V/region/VZW/ but was just a lucky find - definetly check your model number and make sure, you got the right one.

So I'm currently missing the "OEM Unlock" option w/in the "Developer Options" menu on my device. Does anyone know of any other alternative method to unlocking the bootloader for my situation?

Hi there
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.

sameog said:
Hi there
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.
Click to expand...
Click to collapse
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?

Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself

LidelnFR said:
Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself
Click to expand...
Click to collapse
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.

knighToFdemonS said:
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.
Click to expand...
Click to collapse
Thank you kindly for this! I am quite a noob so I don't want to reflash the ROM all the time either ^^
Not sure about these adb commands, but I might have a look if I have time (this is my gf's phone, I don't want to bother her all the time)
Btw, for the installation, I had to do these steps (most are identical, but some are slightly different or more specific):
### Preparation steps:
"Called" *#1234# to get CSC and other information
I used SamMobile (premium sub to get the file quickly because I was in a hurry -- this is not a promo, I have zero link with them whatsoever)
Went to this thread to get Odin 3.14.1 3B PatcheD (not sure it changed anything)
Did the steps to activate developer mode, USB debugging, OEM unlocking (it did not wipe anything for me)
Turned the phone off
Turned it on again using VOL+ and VOL- at the same time (had to try again because it didn't work the first time)
Another option is to use ADB: adb reboot recovery (first you have to list devices, and if need be authorize (from the phone) ADB to access it)
In the blue screen, written at the center, are the options you can "press" for (not easy to see at first)
So, LONG (!!) press VOL+ to ask to unlock bootloader
SHORT press VOL+ to confirm unlocking the booloader (which will wipe data)
Reboot phone
### Firmware/flashing steps:
On the PC, unzip the Samsung firmware
Put (only) the "AP" file into the phone (e.g. "Downloads" directory) (I had first to remove the trailing ".md5" from the filename to only keep ".tar", not sure it is mandatory but I didn't want to lose 12 minutes of copy for nothing)
Install Magisk on the phone (ONLY from their GitHub : topjohnwu) (you have to do it AFTER the bootloader is unlocked, if I understood things properly)
Using Magisk, click the first "install" button at the top (which will actually patch an AP file), choose the AP.tar file from your "downloads" folder (for example)
When done, copy the newly generated file (magisk_patched-26100_{UID}.tar) to the computer (I first had to unplug USB and replug, because it would not refresh the folder properly, at least on Windows 10)
The file was already in .tar extension (at least for me) so I didn't have to compress it again
Reboot the phone in recovery or "download mode" (using the same steps as earlier)
Launch Odin, plug the phone, and flash the Magisk-patched AP file (only this file) (leave the options to their default)
It should reboot the phone when it's done
### Magisk-related steps:
Install Magisk again (it should (??) be wiped iirc), it will ask you to reboot after some changes it automatically made
Reboot
Relaunch Magisk, go to options, activate Zygisk: it will install a new module
Reboot
Go to Magisk, enable systemless host file (or something like that) so that ad blockers (e.g. AdAway) can work properly
Reboot
Go to Magisk again and enable "hide magisk" from the options, choose a custom name
Reboot one last time (not sure you have to reboot for each Magisk step, it's just to be sure)
Again, most steps are identical, but other change slightly or are more precise, because honestly I was kinda lost at first
Thank you again for the tutorial!
For the carrier services, I tried to "reset network" but it didn't do anything.

urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that

urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..

bizkit_120 said:
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that
Click to expand...
Click to collapse
I would have to unlock the bootloader in order to flash a different rom which requires the OEM unlock toggle to be accessible, but it's not.

bizkit_120 said:
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..
Click to expand...
Click to collapse
Possibly so... I was waiting for them to respond to my comment to get a definitive answer, but time will tell.

Flash stock firmware doesn't require bootloader to be unlocked.. you can try flash another firmware see if OEM toggle comes up, then unlock it..