Database Info

[LG LS620] LG Realm / LG Prism - "One Stop Shop"

i decided to put EVERYTHING for this phone under one roof.. the drivers, root, roms, tweaks, tutorials, links etc etc, all consolidated in one spot.. this way, anyone that bought or buys this phone dont have to scour the interwebs to find what theyre looking for. normally, its fair to assume if youre here, you have some degree of knowledge about everything to follow. however, im going to over simplify some or eventually most stuff for, example, family or friends that ask me to "jailbreak" their phone then have no idea what to do once i do. or, for anyone else that meets the same criteria ("budding android modders") lol. :good:
at the moment though, i dont have time to get everything up all at once, so i decided to create a placeholder and upload a rom in the meantime.. theres more to come as time permits..
ROM
deodexed
(now you can switch from "dalvik" to "art" in "developer options" without all the FCs.. the pros and cons with odex vs odexless roms goes back and fourth. having an odexed rom can make your phone a little faster, and free up more room for apps and stuff which is why most if not all phones come odexed (eventually, you can click here to see how to free up room by getting the most of your sdcard, so the free space you lose being unodexed wont really matter), but it has a few setbacks when it comes to modding your phone depending on what youll be doint to/with it now that its rooted (wil discuss more in detail later). If youre coming from another phone with a custom rom, and became spoiled by having developer options already in settings for you. or, you just wanna try art and/or have access to more features (this will later be moved when i explain how to root and setting up drivers, since debugging becomes relevant), getting the menu back is pretty simple. just open settings and go down to "about phone", then click on "software information". on the following screen click "build number" 7 times and if you did it right a popup will display welcoming you to the world of development lol. so simplified its "Settings>About phone>software info", click "Build number" 7x.. "Developer options" is now in settings again. in developer options ("settings>developer options") youll see "select runtime", where you can do just that).
added root and enabled adb root (you need to download your superuser app of choice though).
added busybox with symlinks.
fixed a few invalid permissions. (come to think, im gonna add them back jic its relevant to other carriers besides boost mobile)
and removed some useless symlinks. (come to think, im gonna add them back jic its relevant to other carriers besides boost mobile)
fixed kitkat sdcard write restriction.
this is a "rough draft", there is a few more little tweaks i wanna add (ie: once the device is activated on boost mobile, it downloads all the boost related apps, and those apps reinstall even after a fresh wipe/format/rom installation. its inconvenient if you switch carriers) but i just wanted to get a link up, this is a great phone for the price (only $40, when the HTC Vision still sells for $100 at a fraction of the performance), but it seems like there is close to zero development being done probably because of that (ie; i couldnt find 1 single rom for this device, its not exactly a well known, high demand, highly advertised device. but imho that doesnt mean the 27 or so rooted owners shouldnt have some easy options). unfortunately, even though i stumbled across the kernel source code for w5c (ironically on a LG l70 board) my laptop would probably take days to compile from source, so in the meantime ill tweak the stock image, and maybe eventually see if i can hack some cyanogenmod goodness together.. ill make this thread more professional as time progresses, as well as add an odexed version (definately the stocks version, but i might even redo odexing the right way as well, i donno yet because i dont see the benefit, its just my OCD acting up because i know LG did it half assed), and MAYBE a completly stock rom w/ no mods (which seems redundant since most people keep a "stock" recovery backed up.. but if you were like me and didnt know how easily the bootloader could be unlocked, so you just rooted and started playing with stuff, it might come in handy to have a stock rom lying around.)
Downloads
http://[email protected]/download/%75c%749%6D%6459%77%659%78sl%78/lgls620.zip
http://[email protected]/public/%42%54%44s%42%56/lgls620.zip
http://[email protected]/#!KZFkxb5K!zXW_1p_WMcR_EenrGPoLEgo_-OURR2i7tHSa6GCk5j8
MD5: cc88f51b3e483c4a8c3b974d6f87ceec
File Name: lgls620.zip
(google url shortener didnt like my link and claimed it was a TOS violation, then mediafire deleted the file claiming the same, all within only a few hours of uploading.. so i apologize for the obscured non clickable download links. i never had this problem before so i dont know what they dont like or how theyre deciding its a violation, and if i make the urls clickable xda automatically un-obscures them, so untill i figure out what they dont like or how they go about making that decision, im gonna assume its a bot. i tried an anonymous referer but then mediafire falsely claims the file was removed for violating TOS, without the referer it works fine though (completely unrelated, keep that in mind.. if you ever try downloading something on mediafire that says its been removed, and you were sent there by a referer, try reloading the mediafire link independently before giving up on the dl, i imagine they assume if your being refered anonymously its pirate related so they block you)
PLACEHOLDER

Placeholder
Placeholder

Placeholder0
Placeholder0

Placeholder1
Placeholder1

Placeholder2
Placeholder2

Placeholder3
Placeholder3

How did you unlock the boot loader?
I zeroed the laf partition and did fastboot oem unlock with fastboot oem device-info reporting:
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
but when I try flashing a modified (using Android Kitchen) boot image it comes up saying:
Code:
ERROR : boot certification verify
[750] ------------------------------------------
[760]
[760] Secure booting Error!
[760] Cause : boot certification verify
[760]
[760] ------------------------------------------
I'd like to be able to change the init scripts, and possibly the kernel (where did you find the source?), but I'm stuck getting it to boot with the new image.

Laf
Zero laf, fastboot oem unlock, flash recovery, profit

soulife said:
Zero laf, fastboot oem unlock, flash recovery, profit
Click to expand...
Click to collapse
this thread will be updated soon (for those who give af)

Recover your dead LG REALM (LS620)
First of all thanks to @soulife for the deodexed rom.
2nd to @fatherguido for the boot.img
3rd to @bcrichster for the stock recovery.img
4th to @elisam98 for the bumped twrp img
This is for you all that want to recovery your dead LS620.
This applies to all phones that have no recovery/fastboot mode enabled/download only/or just a faulty rebooting system.
1. you have to enter download mode and zero out LAF partition: to do this you have to download the LG root zip and follow some steps in this tutorial (until step 10) then run the following command:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
2. Power off the phone and enter download again, only this time it will be fastboot mode.
2a. here you will fastboot oem unlock command
2b. flash twrp from here
(the commands to flash this twrp img in fastboot are: fastboot flash recovery w5c_twrp_bumped.img)
3. Enter twrp and flash my backup which has the boot.img from fatherguido and the stock deodexed rom from soulife.
Or you can flash the stock deodexed rom in this forum by soulfie
and then reboot to fastboot again and flash manually the boot.img by fatherguido.
links to all files:
boot.img (zipped)
twrp.img (zipped and bumped)
LG ROOT (zipped)
Stock recovery (zipped)
My TWRP backup (7zipped)
GOOD LUCK!!!

Sweet! Nice job, bro.
Gratefully sent from my Rooted JollyRoger_B13

Alex_XV6700 said:
First of all thanks to @soulife for the deodexed rom.
2nd to @fatherguido for the boot.img
3rd to @bcrichster for the stock recovery.img
4th to @elisam98 for the bumped twrp img
This is for you all that want to recovery your dead LS620.
This applies to all phones that have no recovery/fastboot mode enabled/download only/or just a faulty rebooting system.
1. you have to enter download mode and zero out LAF partition: to do this you have to download the LG root zip and follow some steps in this tutorial (until step 10) then run the following command:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
2. Power off the phone and enter download again, only this time it will be fastboot mode.
2a. here you will fastboot oem unlock command
2b. flash twrp from here
(the commands to flash this twrp img in fastboot are: fastboot flash recovery w5c_twrp_bumped.img)
3. Enter twrp and flash my backup which has the boot.img from fatherguido and the stock deodexed rom from soulife.
Or you can flash the stock deodexed rom in this forum by soulfie
and then reboot to fastboot again and flash manually the boot.img by fatherguido.
links to all files:
boot.img (zipped)
twrp.img (zipped and bumped)
LG ROOT (zipped)
Stock recovery (zipped)
My TWRP backup (7zipped)
GOOD LUCK!!!
Click to expand...
Click to collapse
hey ive been doing this for a long time now, but im still a noob to some things.....
what is a boot.img?
i always read people saying to flash it this way or that, and i see it on file hosting sites along with the stock and custom roms and recovery.img, but ive never gotten it and done anything with it because i dont know what the hell it is,what it is for, and what the point of having it is
just wondering lol

mistaweeks said:
hey ive been doing this for a long time now, but im still a noob to some things.....
what is a boot.img?
i always read people saying to flash it this way or that, and i see it on file hosting sites along with the stock and custom roms and recovery.img, but ive never gotten it and done anything with it because i dont know what the hell it is,what it is for, and what the point of having it is
just wondering lol
Click to expand...
Click to collapse
If you dont need to repair or resurrect your phone or change to a custom rom then you dont need to modify the boot.img
:good::good::good::good:

I'm stuck my lg realm ls620 only enters download mode, no recovery, and won't boot. So following your instructions in step one gets me stuck on step 2 of the thread you referred to in step 1. How can I transfer the rootedsystem file into the root of my phone if it will ONLY go into download mode? Please help.

Wazza
bcrichster said:
Sweet! Nice job, bro.
Gratefully sent from my Rooted JollyRoger_B13
Click to expand...
Click to collapse
Hey wassup remember me from the other website??
You helped me root my ZTE Z730 and made a custom
ROM for it. I got this phone now, but I'm probably not
Gonna use this ROM. I'll wait for an odexed one.
Thanks anyways!!

i recently seen a web site that says 5.0 update for lg realm is this a legit rom or a fake

Hello XDA. I'm curious if anyone has any info or advice on getting working camera libraries for cm12 for the lg realm. As those from Android forums are aware, we have some cm12.1 Roms for the ls620, but they are incomplete in a few aspects.
One is cameras. Neither front or back cameras work, which I believe to be an issue with the libraries used. I don't know enough about compiling the ROM with proper Android lollipop camera libraries for this phone.
Aside from that, the Roms work pretty well. There seems to be less development for this phone which is a beast otherwise(not considering the small memory...)
Hoping someone can lend some input.
Thanks!

Hey I've bricked my lg ls620 I can get into factory reset and download mode can you instruct me on how to get it fixed or at least get twrp on it and I got it from there it's a girls phone I'm fixing for here and she has her dought that it can be done normal thing would be flash tool and kdz but the only way to get the kdz is to buy it and it may still not work I get a secure boot error
Sent from my XT1526 using XDA-Developers mobile app

hard bricked
i need to unbrick ( Qualcomm DLoader mode ) no recovery no boot. :crying:
p.d. Sorry for reviving old threats but I need it i have no phone or money to have another one :/

[H915] Root Guide + Restore Any Bricked LG V20

Just in Time for The New Year I would like to show Everyone How to root there Canadian variant LG V20!
Current Known issues
- No Service From Carrier
- Seems VERY Laggy (Can be Fixed with using a Kernel)
Other Information
- Yes you can Restore to factory Settings with this Method (So Don't worry if you screw up)
- Sorry far I Only know This works on the H915 however the Restore should work with all LG Models
- This will give you a Bootloader to have access to fastboot Commands
- Working TWRP Recovery
So After Reading the No Service Part many are mostly not going to be interested... I uploaded this Thread anyway to see if anyone could find a fix to this issue. (When one is found I will update this with the fix)
So If you still want to Root your Canadian LG V20 Let's do it!
DOWNLOAD THE ZIP FILE HERE
https://mega.nz/#!ABZV0AZZ!8LBGgpjiGT1ij6scshWTQO4tGhUb9GMUcTHtKLLhfW0
- I DO NOT TAKE ANY RESPONSIBILITY FOR YOU BREAKING YOUR DEVICE
- I HAVE NOT CREATED ANY OF THESE FILES I ONLY PUT EVERYTHING INTO ZIP FOLDER FOR YOU TO DOWNLOAD AND MAKE THINGS CONVENIENT AND SIMPLE
- PLEASE THANK THE ACTUAL DEVELOPERS WHO CREATED THESE FILES (LISTED BELOW)
FILES USED/THANK THESE PEOPLE
@me2151 Dirty Santa Files (Boot2.img, Step 1.bat, Step 2.bat and RUNMEFIRST.bat) -
HTML:
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
@jcadduono recowvery and dirtycow exploit (used with Dirty Santa)
HTML:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Stock Images for LG V20 H915 you can find those here
HTML:
http://lg-firmwares.com/lg-h915-firmwares/
(You will need to be flashed on H91510d for this to work however you could try 10e if you wanted)
@autoprime UPPERCUT for LGUP (This is what allows the LG V20 to be read and will allow you to downgrade to 10d if needed and will let you restore to stock using Download Mode at any time! This will only be used for you if you mess up with the root and need to flash back to stock or you need to upgrade or downgrade to the 10d firmware)
HTML:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
@Chainfire SuperSu v2.79 SR1
HTML:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
WHAT DO YOU NEED BEFORE YOU START
- A Copy of LGUP
- An LG V20 H915 Running the 10d Firmware (if you need help flashing this firmware read below before Step 1)
- The Zip File I Listed above to Download
- ADB and LG Drivers
- A Windows Computer
HOW TO UPGRADE/DOWNGRADE TO FIRMWARE VERSION 10d
Step 1 - Boot Your Device into Download Mode (Turn the phone off hold the Vol + Button and plug in your device to the Computer)
Step 2 - On your Computer find the Zip File (extract it) and Open Uppercut.exe (This should launch LGUP and Make sure your Phone is Connected to your Computer)
Step 3 - In LGUP Select the Upgrade button (even if you are downgrading it will still work) then find the Firmware .kdz file for 10d
Step 4 - Flash the KDZ back onto your device
ROOTING THE DEVICE!
Step 1 - Install a Terminal Emulator App to your Device
Step 2 - Verify your device is plugged in and that ADB sees the Device (adb devices)
Step 3 - On your Computer Open the RUNMEFIRST.bat (do not close this window)
Step 4 - After loading up RUNMEFIRST.bat run Step1.bat (if you see permission denied on the files Flatland and Flatland64 this is normal)
Step 5 - Once the shell prompt opens in the step 1.bat window type "run-as con" (without quotations then hit enter) then type "chmod 0777 /storage/emulated/0/*" (yet again not in quotations and then hit enter)
Step 6 - Once that has finished on your phone open the Terminal app you downloaded earlier and type in id (if untrusted_app is displayed continue if not redo the steps)
Step 7 - In the Terminal Emulator type applypatch /system/bin/atd /storage/emulated/0/dirtysanta then watch the RUNMEFIRST.bat to see when it tells u to open Step2.bat (when it tells u to open Step2.bat open it)
Step 8 - You should now Be into a Somewhat usable bootloader on your device... now we Stop using DirySanta and Start to do things manually by ourselves open up a Command Prompt and type "fastboot flash boot boot.img" this will flash the boot2.img used in the Dirty Santa Exploit
Step 9 - After that finishes type "fastboot flash recovery TWRP.img" This will put TWRP (For the H918 Variant) on your device
Step 10 - Boot into TWRP (Remove battery then put it back in hold the Vol - Button and the Power Button Once LG Powered by Android Logo Appears Release the Power Button then Hold it Again, A White screen should come up say yes to both screens then should boot into TWRP)
Step 11 - Now that you are this far I recommend you backup everything so that you can start from this point if you mess up any upcoming steps that way you do not have to reflash the stock image and start from step 1 again....
Step 12 - Select Wipe from the Main menu then go to Format Data then type yes and enter (This will remove the password lock currently enabled on the device)
Step 13 - On the Main Menu select Install browse to your SD Card where you put your SuperSU.zip File onto and flash that to the device
Step 14 - Once that is completed return to the main menu select the Wipe menu again go to Format Data then yes again
Step 15 - Go back to the Wipe Menu and go to Advanced and select Dalvik, Data and Cache then slide to wipe after this finishes reboot to the system
Step 16 - Once in the System complete the Android setup and enable USB Debugging again then type adb reboot recovery (if your device does not boot into Android this is when u go back into TWRP by doing the remove battery method and holding those buttons down as I stated before and you Restore your Backup you made in Step 11 and you try doing those Steps again)
Step 17 - Once Back into TWRP (you may make another backup here if you would like) select Install then Flash SuperSU to your device again... Go back to the Main Menu Select Wipe then Advanced and Select Dalvik and Cache then Slide to Wipe and reboot into the System
Step 18 - Once back into Android you should see SuperSU on your device and you may download a Root Checker app of the Play Store to Make sure your Device is Fully Rooted and Working!
Please inform any Issues in the Replies below and I will add them to the List for People to Know before they Attempt rooting... If anyone finds a Fix for the Modem file to get service working on the LG V20 H915 while rooted please reply and i will Add that to the guide BELOW!
I DID NOT MAKE ANY OF THESE FILES SO PLEASE THANK THE CREATORS (LISTED ABOVE) FOR THEIR HARD WORK AND EFFORTS!
I THINK I BRICKED MY DEVICE/ THE ROOT DID NOT WORK/ I WANT TO GO BACK TO STOCK
Step 1 - As Stated Above to this all we need to do is Enter Download Mode (Remove Battery reinsert battery hold Vol + and plug in the Device) and then run the UPPERCUT.exe File
Step 2 - Select Upgrade browse over to your kdz file and select it then flash it to your device! Your Device Should boot up into Android (I Have Bricked my LG V20 Many Times Removing TWRP and the Bootloader and having nothing but the LG Logo and the Download Mode and I could Still get into the Device after doing this so it should work for you! However any problems should be dealt with the developer on his forum listed here
HTML:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
)
Anyone willing to Try installing things like Kernels and ROMs I would assume you would be using H918 Supported Files For those as thats what TWRP is running in.....

Will be adding a Zip File will all the Files need in a Couple of Minutes....

There seems to be a hidden settings menu on our Devices in which we can play around with the Modem Settings among other things.... you need to open the Phone App and Type in *#546368#*915# and the menu should come up.... Maybe somebody can figure out how to get Service running.... All Credit for this goes to @KedarWolf in his post listed here https://forum.xda-developers.com/v20/how-to/access-hidden-menu-h915-t3515098

Nice little write up. Did you try this on the wind/freedom 915 or videotron 915? My guess would be that you tried it on the wind 915 and if so i bet it has something to do with their slightly differnet bands they use albeit for a change an unlocked wind device works fine on other networks. But i really have no clue if there's a connection on why there's no signal. This kind of thing is beyond my pay grade. I would be guessing someone like @autoprime would be someone to ask but chances are he has other things to worry about and likely doesn't have the device.
But keep plugging away. You may figure it out yet

markbencze said:
Nice little write up. Did you try this on the wind/freedom 915 or videotron 915? My guess would be that you tried it on the wind 915 and if so i bet it has something to do with their slightly differnet bands they use albeit for a change an unlocked wind device works fine on other networks. But i really have no clue if there's a connection on why there's no signal. This kind of thing is beyond my pay grade. I would be guessing someone like @autoprime would be someone to ask but chances are he has other things to worry about and likely doesn't have the device.
But keep plugging away. You may figure it out yet
Click to expand...
Click to collapse
Yes the Wind H915 still haven't got it figured out yet hopefully someone will soon then we will have an official working root for the Canadian Variant

I would have jumped on the Freedom Mobile (formerly Wind) deal ($30 for 6GB for the first 10 months) if the H915 had been root and has an unlocked bootloader. LG's track record of offering unlocked bootloader is looking very bleak for the H915.

@TheDantee I am sure the service issue will be resolved soon but "Seems VERY Laggy" part is worrying me more. What is the reason for that? I like the possibility to go to the default LG rom like nothing happen.

Emilius said:
@TheDantee I am sure the service issue will be resolved soon but "Seems VERY Laggy" part is worrying me more. What is the reason for that? I like the possibility to go to the default LG rom like nothing happen.
Click to expand...
Click to collapse
Sorry i should mention that a Kernel fixed this issue for me!

TheDantee said:
Sorry i should mention that a Kernel fixed this issue for me!
Click to expand...
Click to collapse
Service issue or laggy part?

Emilius said:
Service issue or laggy part?
Click to expand...
Click to collapse
Laggy Part

Noob question, is the phone fully functional after step 10 (TWRP).
The reason I ask is because I really only need to get to TWRP as I want to enable google assistant.
At this point, the root is not a big concern for me.
Thanks,

SHABBA JOTS said:
Noob question, is the phone fully functional after step 10 (TWRP).
The reason I ask is because I really only need to get to TWRP as I want to enable google assistant.
At this point, the root is not a big concern for me.
Thanks,
Click to expand...
Click to collapse
Shoulbe be but you will need to still do a format on the device or you will get locked out and it will ask for a passcode....

TheDantee said:
Shoulbe be but you will need to still do a format on the device or you will get locked out and it will ask for a passcode....
Click to expand...
Click to collapse
So SuperSU messed the service reception? Not bootloader?

Emilius said:
So SuperSU messed the service reception? Not bootloader?
Click to expand...
Click to collapse
I don't think its SuperSU Causing the problem... In the bootloader (debug) that is provided in the DirtySanta root it states the device as an unlocked US996 LG V20 I feel that this is because it has no idea which provider its with since we are Canadian.. I have tried flashing many many modem files from many different firmwares I either get modem blue screens on boot (Goes away permanently if you remove sim card) or I get no Service in the System it self... so personally I think it is the Bootloader since its a debug bootloader because the Canadian Variant does not seem to have a bootloader.... May I ask what is your reasoning for SuperSU being the issue?

TheDantee said:
I don't think its SuperSU Causing the problem... In the bootloader (debug) that is provided in the DirtySanta root it states the device as an unlocked US996 LG V20 I feel that this is because it has no idea which provider its with since we are Canadian.. I have tried flashing many many modem files from many different firmwares I either get modem blue screens on boot (Goes away permanently if you remove sim card) or I get no Service in the System it self... so personally I think it is the Bootloader since its a debug bootloader because the Canadian Variant does not seem to have a bootloader.... May I ask what is your reasoning for SuperSU being the issue?
Click to expand...
Click to collapse
Based on your answer to SHABBA JOTS I get feeling that maybe is SuperSU creating that problem if until step 10 (TWRP) is all good. So soon we do step 8 (flashing boot image) service is gone. Is that right?

Emilius said:
Based on your answer to SHABBA JOTS I get feeling that maybe is SuperSU creating that problem if until step 10 (TWRP) is all good. So soon we do step 8 (flashing boot image) service is gone. Is that right?
Click to expand...
Click to collapse
Currently I have no access to my V20 so i can not try and tell you but if you are willing to reset and try the steps again up to Step 8 then lemme know the answer... however the system is very very very unstable many crashes tons of lag massive downgrade in battery without that boot.img... what if u flash twrp once in the bootloader but not the boot.img try that.... then get back to me Curious now lol

TheDantee said:
Currently I have no access to my V20 so i can not try and tell you but if you are willing to reset and try the steps again up to Step 8 then lemme know the answer... however the system is very very very unstable many crashes tons of lag massive downgrade in battery without that boot.img... what if u flash twrp once in the bootloader but not the boot.img try that.... then get back to me Curious now lol
Click to expand...
Click to collapse
He he, I am an Nexus person. I am so afraid to mess up my V20. With Nexus it is so easy, in 2 steps you are done. I miss that part I mast say.

Ok so i gave this a quick read and from what i gather you flash the bootloader before you flash twrp and super su. So here's a question that may or may not have been tried. Is there any reason you can't follow this method to root and then flash stock recovery and then flash stock bootloader?
Since it seems bootloader is the issue with having no data or signal. You would at least have root but just not twrp. Does that make sense?

markbencze said:
Ok so i gave this a quick read and from what i gather you flash the bootloader before you flash twrp and super su. So here's a question that may or may not have been tried. Is there any reason you can't follow this method to root and then flash stock recovery and then flash stock bootloader?
Since it seems bootloader is the issue with having no data or signal. You would at least have root but just not twrp. Does that make sense?
Click to expand...
Click to collapse
It's look like H915 dues not have bootloader at all.

Emilius said:
It's look like H915 dues not have bootloader at all.
Click to expand...
Click to collapse
Well it has to have a bootloader. It's just locked right. Like if we pulled apart the stock kdz we should be able to find it and my theory is we could use flashfire to flash stock recovery and also flash thr bootloader since twrp can't to my knowledge flash bootloaders. We would be left with root but no recovery. I could be so far from being right but who knows. This could be the only way to have root and a working phone.

[CLOSED]LG Stylo 6 root development! ANY HELP APPRECIATED. DISCORD LINK AVAILABLE

Moderator Announcement:
Thread closed and content removed on request of OP.
- Oswald Boelcke

I SERIOUSLY would like to know how you get that bug report so I can get any files for the stylo 6 boost mobile
Where did you find the zip or link to the site hosting the zip in the big report? I can get that far but I really want any help on getting similar files from this specific device model/variant
I am not gonna lie your post is an oasis in a desert and I hope this does find its way into the right hands to push root dev

Me to I have the lg stylo 6 from my cable company

I'm currently browsing through the root directory to see if I can pull the boot.img.. there's a method of rooting it with magisk manager.. the bigger issue is how to reinstall the modified boot.img.. I think we will need the bootloader unlocked
Spoiler
{
"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"
}

I just checked on firmware download and the kdz for lgup is available to download.. in theory because I don't have a pc to verify.. a possible root method might be as simple as, extracting the kdz file, modifying the boot.img with magisk manager, rebuild the kdz file with a kdz tool.. then flashing the modified kdz with lgup.. then install magisk manager after 1st boot and hope we have root.. feel free to test or share any other ideas..
Spoiler

It seems like very few working on this project.. I've come across a dual mode lgup made by one of our developers capable of crossflash.. probably the best version of lgup to flash firmware with modified boot.img.. I'm also buying a laptop for experiments on this device.. I now have 2 versions of the stylo 6 to play with.. hopefully I don't go overboard and turn them to paperweight .. the only thing I need is the method or tool to rezip kdz to try achieving root myself.. if anyone find such a tool, please share ..

The boot image wouldn't work. In theory, you would use kdzTools and it will turn the KDZ into a DZ file and then you extract the DZ file. You would have to use Qfil or fastboot to flash a modified boot image, and have an unlocked bootloader. LGUP is an amazing tool to crossflash different firmware from different Stylo variants, but with AVB 2.0, this doesn't work on many of the LG devices that came out of the box with Android 10, and repacking the KDZ with a modified boot image would fail because of the boot image being signed inncorrectly. Your best bet is to see if there is an exploit like what was found on the V50, and to hope that someone makes gets Firehose working for the Stylo.

Yeedatoy said:
The boot image wouldn't work. In theory, you would use kdzTools and it will turn the KDZ into a DZ file and then you extract the DZ file. You would have to use Qfil or fastboot to flash a modified boot image, and have an unlocked bootloader. LGUP is an amazing tool to crossflash different firmware from different Stylo variants, but with AVB 2.0, this doesn't work on many of the LG devices that came out of the box with Android 10, and repacking the KDZ with a modified boot image would fail because of the boot image being signed inncorrectly. Your best bet is to see if there is an exploit like what was found on the V50, and to hope that someone makes gets Firehose working for the Stylo.
Click to expand...
Click to collapse
I just found all the information necessary to root our Stylo.. I'm not experienced enough to do the final step but I'm willing to pay our more experienced developers to do it.. we can simply use an all in one tool I'll share the link to, that will let us extract the kdz, modify the system.img and reconstruct the kdz.. in the extracted system.img we can hopefully find the boot.img and modify it for root using magisk manager.. dual mode lgup should flash the modified kdz.. I plan to try.. then on 1st boot we can manually install magisk manager and enjoy root.. the downside is with a locked bootloader all we get is root.. no custom recovery or custom rom until we unlock the bootloader.. but it's a start.. again.. bounty for dev that can use this handy tool.. Happy New Year
GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
Tools for working with KDZ files (LG's Android device upgrade format) - GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
github.com
Spoiler

lowkeyst4tus said:
I just found all the information necessary to root our Stylo.. I'm not experienced enough to do the final step but I'm willing to pay our more experienced developers to do it.. we can simply use an all in one tool I'll share the link to, that will let us extract the kdz, modify the system.img and reconstruct the kdz.. in the extracted system.img we can hopefully find the boot.img and modify it for root using magisk manager.. dual mode lgup should flash the modified kdz.. I plan to try.. then on 1st boot we can manually install magisk manager and enjoy root.. the downside is with a locked bootloader all we get is root.. no custom recovery or custom rom until we unlock the bootloader.. but it's a start.. again.. bounty for dev that can use this handy tool.. Happy New Year
GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
Tools for working with KDZ files (LG's Android device upgrade format) - GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
github.com
View attachment 5179601
Click to expand...
Click to collapse
Give it a shot, it's not as confusing as it may look at first glance. Just put everything in the same folder on you computer. Open the tool and select your KDZ file. Extract it, and it turns it from a KDZ file into DZ file. Select extract DZ in KDZ tools next, and it will fully extract the file. You'll see a bunch of bin files. You can simply rename bin, to img for boot, and then copy it to your phone and patch it with magisk. Then copy the patched boot image back to your PC and change the img extension back to bin and rezip the KDZ.

Do you have fastboot access on the Stylo 6?

Not sure yet but I don't think I'll need it.. I don't want to start by diving deep and overlook a simpler solution than accessing fastboot.. I just need a developer that can modify a kdz.. if I can simply achieve root via the new magisk method, it's a start.. I'm picking up another stylo 6 today, then a real computer cause my chromebook useless.. I'll update if I get a modified kdz and what happens when I try to flash

lowkeyst4tus said:
Not sure yet but I don't think I'll need it.. I don't want to start by diving deep and overlook a simpler solution than accessing fastboot.. I just need a developer that can modify a kdz.. if I can simply achieve root via the new magisk method, it's a start.. I'm picking up another stylo 6 today, then a real computer cause my chromebook useless.. I'll update if I get a modified kdz and what happens when I try to flash
Click to expand...
Click to collapse
I myself have just finally found this thread and am super more than willing to put in some work!
so i've gotta:
- `adb reboot recovery`
- boot into fastboot from recovery
- unlock the bootloader with `fastboot oem_unlock`
- let the phone factory reset with an unlocked bootloader
_____________________
and:
- download the .kdz firmware file for the unlocked version on pc
- locate and extract the boot.bin with kdzTools and convert it to boot.img
- send extracted file to my personal phone
- patch boot.img in magisk manager app on my phone
- send it back to pc with `adb pull /sdcard/boot.img C:/users/myname/`
_____________________
then:
- load patched boot.img into the stylo 6 through `fastboot flash boot boot.img`
- `fastboot reboot` and let it reboot hopefully with root AND with carrier unlock
- download magisk manager to verify
I guess I'll give this a shot and get back to you guys.

haise.zero said:
I myself have just finally found this thread and am super more than willing to put in some work!
so i've gotta:
- `adb reboot recovery`
- boot into fastboot from recovery
- unlock the bootloader with `fastboot oem_unlock`
- let the phone factory reset with an unlocked bootloader
_____________________
and:
- download the .kdz firmware file for the unlocked version on pc
- locate and extract the boot.bin with kdzTools and convert it to boot.img
- send extracted file to my personal phone
- patch boot.img in magisk manager app on my phone
- send it back to pc with `adb pull /sdcard/boot.img C:/users/myname/`
_____________________
then:
- load patched boot.img into the stylo 6 through `fastboot flash boot boot.img`
- `fastboot reboot` and let it reboot hopefully with root AND with carrier unlock
- download magisk manager to verify
I guess I'll give this a shot and get back to you guys.
Click to expand...
Click to collapse
If you do manage to get into fastboot, there's 2 commands to try.. the new command is " fastboot flashing unlock".. you can also try getting unlock.bin even though there's no mention of availability.. it might be required for fastboot unlock.. the unlocked firmware is what I was going to experiment with also.. if you do manage to successfully extract the boot.img from the kdz, skip fastboot flashing.. just install magisk manager on your phone and follow the instructions on other threads to modify the boot.img.. then rezip the kdz with the modified boot.img.. flash with dual mode lgup for better chance of success.. it should install and boot normal.. on the surface you should not notice any change like errors with boot.. after 1st boot, install magisk manager and it should say root is working .. good luck and I look forward to your results
Spoiler

lowkeyst4tus said:
If you do manage to get into fastboot, there's 2 commands to try.. the new command is " fastboot flashing unlock".. you can also try getting unlock.bin even though there's no mention of availability.. it might be required for fastboot unlock.. the unlocked firmware is what I was going to experiment with also.. if you do manage to successfully extract the boot.img from the kdz, skip fastboot flashing.. just install magisk manager on your phone and follow the instructions on other threads to modify the boot.img.. then rezip the kdz with the modified boot.img.. flash with dual mode lgup for better chance of success.. it should install and boot normal.. on the surface you should not notice any change like errors with boot.. after 1st boot, install magisk manager and it should say root is working .. good luck and I look forward to your results View attachment 5181357
Click to expand...
Click to collapse
Sounds good, thanks for the advice! It's super helpful.
I'll be taking a crack at it here soon, or maybe tomorrow since it's 1:30am and I'm having a drink (depends on my mood ). I'll probably go with fastboot flashing unlock_critical just to be on the safe side of things and have everything unlocked from the get go for development purposes. I did run into an issue when I ran that command already -
C:\Users\myname>fastboot flashing unlock_critical
...
FAILED (remote: Unrecognized command flashing unlock_critical)
finished. total time: 0.006s
I can get into fastbootd on the device, and need to read up on it a bit since nearly every fastboot command I send in is unrecognized (see above) or gets a response like FAILED (remote: Unable to open fastboot HAL)
I'll enable test signing mode on my windows machine and get the right drivers installed, and get fastbootd working and then try again. I'll likely run into a roadblock though, since Boost doesn't exactly want us unlocking the bootloader - nor does LG, apparently...
For now, here's a few resources that might help catch you up on things and possibly give me some more room to wiggle around:
- Android documentation on fastbootd and fastboot being moved to userspace (contains information about the HAL)
- A mildly helpful and more easy-on-the-eyes article that can help explain the above documentation
I'll try and get past this issue. There's gotta be something, somewhere... I first just need to communicate with the phone correctly and get it to do what I need it to do in fastboot mode.
I also have downloaded two different .kdz files and have indeed extracted both of them into .dz files. I didn't get past that last night, so I'll have to get in there soon or maybe tomorrow and see if I can't find the system.img and/or the boot.img contained within. If I can, I'll be sure to get it patched and try to pass it to the phone.
For anyone trying to use the kdztools, it's outdated and you'll get some error about the headers when you try to extract the Stylo 6's .kdz files. Below are links to a couple of repositories that will be helpful:
- An updated fork of the original kdztools from somebody else that I've forked for laziness (fixes the headers issue)
- A fork of KDZZ, an up-to-date-enough tool for zipping .kdz files into TWRP-able zip files (again, personally forked for laziness)
There's only one problem... Boost Mobile.
I bought this phone from a third party and it is still registered to someone else on the Boost network. Since it's gone through a factory reset and my google account has been added to it, the phone isn't activated on their network and they seem to have disabled my ability to use wifi as they constantly send me screens and notifications trying to get me to activate the device, which I don't have the money to do. So, no internet access; I'll have to adb push and pull files and apks in order to get things working. I could factory reset and not ping their networks or put the other person's SIM in, but for the sake of longevity, I'd love if anybody had a solution to carrier unlocking this thing - or even an idea of what to do for that? Could I flash stock firmware? Is there any process to read the code I need from logcat? Any ideas at all? New ideas, hypothetical ideas, or even old ideas I could shine up and make new? Even just a thought? This is a pain.
I will keep everyone posted! I'd ask you all do the same - about this, and about carrier unlocking just as a possible favor.
PS: Bounty, huh? I could really use the reward. I might just have to take you up on that if we can get this working haha, exciting!

haise.zero said:
Sounds good, thanks for the advice! It's super helpful.
I'll be taking a crack at it here soon, or maybe tomorrow since it's 1:30am and I'm having a drink (depends on my mood ). I'll probably go with fastboot flashing unlock_critical just to be on the safe side of things and have everything unlocked from the get go for development purposes. I did run into an issue when I ran that command already -
C:\Users\myname>fastboot flashing unlock_critical
...
FAILED (remote: Unrecognized command flashing unlock_critical)
finished. total time: 0.006s
I can get into fastbootd on the device, and need to read up on it a bit since nearly every fastboot command I send in is unrecognized (see above) or gets a response like FAILED (remote: Unable to open fastboot HAL)
I'll enable test signing mode on my windows machine and get the right drivers installed, and get fastbootd working and then try again. I'll likely run into a roadblock though, since Boost doesn't exactly want us unlocking the bootloader - nor does LG, apparently...
For now, here's a few resources that might help catch you up on things and possibly give me some more room to wiggle around:
- Android documentation on fastbootd and fastboot being moved to userspace (contains information about the HAL)
- A mildly helpful and more easy-on-the-eyes article that can help explain the above documentation
I'll try and get past this issue. There's gotta be something, somewhere... I first just need to communicate with the phone correctly and get it to do what I need it to do in fastboot mode.
I also have downloaded two different .kdz files and have indeed extracted both of them into .dz files. I didn't get past that last night, so I'll have to get in there soon or maybe tomorrow and see if I can't find the system.img and/or the boot.img contained within. If I can, I'll be sure to get it patched and try to pass it to the phone.
For anyone trying to use the kdztools, it's outdated and you'll get some error about the headers when you try to extract the Stylo 6's .kdz files. Below are links to a couple of repositories that will be helpful:
- An updated fork of the original kdztools from somebody else that I've forked for laziness (fixes the headers issue)
- A fork of KDZZ, an up-to-date-enough tool for zipping .kdz files into TWRP-able zip files (again, personally forked for laziness)
There's only one problem... Boost Mobile.
I bought this phone from a third party and it is still registered to someone else on the Boost network. Since it's gone through a factory reset and my google account has been added to it, the phone isn't activated on their network and they seem to have disabled my ability to use wifi as they constantly send me screens and notifications trying to get me to activate the device, which I don't have the money to do. So, no internet access; I'll have to adb push and pull files and apks in order to get things working. I could factory reset and not ping their networks or put the other person's SIM in, but for the sake of longevity, I'd love if anybody had a solution to carrier unlocking this thing - or even an idea of what to do for that? Could I flash stock firmware? Is there any process to read the code I need from logcat? Any ideas at all? New ideas, hypothetical ideas, or even old ideas I could shine up and make new? Even just a thought? This is a pain.
I will keep everyone posted! I'd ask you all do the same - about this, and about carrier unlocking just as a possible favor.
PS: Bounty, huh? I could really use the reward. I might just have to take you up on that if we can get this working haha, exciting!
Click to expand...
Click to collapse
I have the boost mobile version and I got the cricket wireless version yesterday just for gradient blue.. according to Gsmarena, all versions of the Stylo 6 are identical.. I'm going to try flashing the unlock firmware on the boost mobile version.. it should unlock the sim and no longer ask for activation .. then I'm going to sell it before I drop it .. I'll use my blue one for development

lowkeyst4tus said:
I have the boost mobile version and I got the cricket wireless version yesterday just for gradient blue.. according to Gsmarena, all versions of the Stylo 6 are identical.. I'm going to try flashing the unlock firmware on the boost mobile version.. it should unlock the sim and no longer ask for activation .. then I'm going to sell it before I drop it .. I'll use my blue one for development
Click to expand...
Click to collapse
Could you link me to the unlocked firmware? Is it the Q730M10l? Or another one?
I would love to flash the unlock firmware and factory reset this thing to get some internet and functionality back. It would greatly help with my development
Thank you!

haise.zero said:
Could you link me to the unlocked firmware? Is it the Q730M10l? Or another one?
I would love to flash the unlock firmware and factory reset this thing to get some internet and functionality back. It would greatly help with my development
Thank you!
Click to expand...
Click to collapse
The unlocked model according to Best Buy is LMQ730QM.. I can't find a download source yet but I'm still looking

Weird, my Stylo 6 says its software version is Q730TM... Q730TM10P to be specific There shouldn't be any issues if they're all identical though, right? I can safely flash a Q730QM image on a Q730TM device?
And I'm looking as well - I'll edit this post if/when I find a source
Edit:
Found this, and this, but I'm unsure if Q730QM10c or Q730QM10d is the genuinely unlocked version, (the C variant is USA and the D variant is USL) and I'm also unsure what carrier, if any, NAO stands for (Q730QM10c_00_NAO_US_OP_0908.kdz for example)
I suppose I'll download the kdz and flash it to try it out. I can always revert back to stock if something goes wrong. I'll let you know how that goes
Hmm... I'm having some trouble. kdzdownloader downloads 0kb. I tried switching my useragent but it didn't work out, either. You having any better luck? Able to attach the file?
Woohoo! I got it.
Use this to install the XDM download manager, and then paste this link into a new job (just hit the + button). It just worked for me.
We officially have the .kdz for Q730QM10C! Time to flash it as soon as it's done downloading.

haise.zero said:
Weird, my Stylo 6 says its software version is Q730TM... Q730TM10P to be specific There shouldn't be any issues if they're all identical though, right? I can safely flash a Q730QM image on a Q730TM device?
And I'm looking as well - I'll edit this post if/when I find a source
Edit:
Found this, and this, but I'm unsure if Q730QM10c or Q730QM10d is the genuinely unlocked version, (the C variant is USA and the D variant is USL) and I'm also unsure what carrier, if any, NAO stands for (Q730QM10c_00_NAO_US_OP_0908.kdz for example)
I suppose I'll download the kdz and flash it to try it out. I can always revert back to stock if something goes wrong. I'll let you know how that goes
Hmm... I'm having some trouble. kdzdownloader downloads 0kb. I tried switching my useragent but it didn't work out, either. You having any better luck? Able to attach the file?
Woohoo! I got it.
Use this to install the XDM download manager, and then paste this link into a new job (just hit the + button). It just worked for me.
We officially have the .kdz for Q730QM10C! Time to flash it as soon as it's done downloading.
Click to expand...
Click to collapse
Great job bro.. use dual mode lgup from XDA as it's designed for crossflashing and supposed to have more features than regular lgup.. let me know if you sim unlock with Q730QM firmware.. Q730TM is the Boost Mobile model.. I have that and the Q730AM in gradient blue from cricket wireless.. I want to crossflash both to Q730QM

Alrighty, well I've been halted. Before I could get to flash, I installed the LG drivers because LGUP wasn't detecting my device (or maybe I was just being dumb).
After that... the phone stopped being recognized. In device manager it says Unknown USB (Device Descriptor Failed)
I've looked online, no solutions have helped. I've installed the Google USB drivers through Android Studio, I've uninstalled the device and reconnected the phone, tried reinstalling the LG drivers, I've factory reset the phone, tried a different USB port, a different cable, and nothing. After I factory reset, it showed up for a bit, but upon a reconnection it crapped itself again and refuses to show up.
Any ideas? I can't continue development if I can't communicate with the phone.
Never mind, possibly? It works after uninstalling the device and replugging again... for the 20th time. But ADB still won't recognize the phone even as unauthorized; it just doesn't show up. Weird... I guess I'll tinker and get back to the post here in a while.
It's back to the error... so damn weird. I'll look into it. If and when I find a solution I'll let you know.
Development has been paused for the time being.

[CLOSED] Delete Thread.

Due to the disrespect of certain members I will no longer share the tutorials.

Wait does this mean you finally got my script to work?

lebigmac said:
Wait does this mean you finally got my script to work?
How about a little feedback in my project thread? Is that too much to ask for?
Did the latest fix work for you or not? Hello?
Click to expand...
Click to collapse
I said you were working on it. LOL. If it worked I'd be writing a Guide for that!

Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root

mingkee said:
Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root
Click to expand...
Click to collapse
Exactly. Definitely made a note of that in the guide since that is why the frozen touchscreen issue happens.

Articul8Madness said:
.This tutorial is for people like me than ran into problems rooting the Moto One 5G Ace XT2113 (MetroPCS Qualcomm Variant) running on stock Android 10. I got this phone literally last week brand new in the box. This is a hand holding guide for the Noobs that really are intimidated by rooting their device.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
I want to thank @mingkee and @sd_shadow for pointing me in the right direction. And for the rest of the contributors that I took bits and pieces from that helped me figure out rooting this; I did achieve root out the starting gate but initially lost touchscreen functionality. The issue was that you have to use the boot.img of your firmware to patch into Magisk; if you do this with your phone out the box you really don't know which firmware was used and that is where the bungle happens. This will clear up all those potential freakout moments.
Thanks to Android 10 being System As Root with all these new super partitions running amuck, you cannot get Write access in the actual system files. So even when you achieve root, you can't do much. @lebigmac is working on that as we speak. Drop by his thread on R/W access and beta test his script so he can get more knowledge about how our phone works.
Introduction/Preparation
First, go and prepare by READING EVERYTHING. Very important. This is the Qualcomm variant and NOT the Mediatek variant. Flashing does make a difference between the two. Last thing you want to do is brick the device because you flashed the wrong firmware to the wrong processor, or you flashed other software for the other similiar Moto One 5G and it bricked.
Second, unlock the bootloader. All T-Mobile and their subsidiary variants can be unlocked by Motorola as well as International and Motorola factory variants; go to their bootloader official unlock site and follow their instructions, it's easy peasy. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). It is HIGHLY ADVISABLE to do this in Waterfox or Chrome (I used Waterfox). And yes, you may have to request the code 3x to get it to send to your email depending on their server traffic. When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
Verizon and ATT Variants CANNOT BE BOOTLOADER UNLOADER UNLOCKED.
***NOTES SO YOU DON'T FREAK OUT***
1. I did NOT see the motorola post screen telling me it was unlocked. I had to find this in fastboot's menu.
2. The only way to restore the phone if something goes wrong is by flashing it via fastboot. The way to get to fastboot is turn the phone off and press Volume Down and Power. The Motorola tool will NOT work. That's normal.
3. You will see a cute message that you've unlocked the bootloader and that the phone software integrity is compromised when you boot the phone up every single time after the bootloader unlock. It will also say press the power button to pause. This is normal. Give it a minute, you havent broke it.
4. OEM Unlocking should already be activated and greyed out in the Developer Options once the bootloader is unlocked; you can't access it anymore.
Files
You will need an SD card for root. You will also need other apks to successfully help you pull off root ready to install. Pull ALL the necessary files you will need.
1. Get Minimal ADB and Fastboot (it's easier).
2. Download the Motorola Drivers from their site if yo don't already have them (if you run into problems you will have to uninstall and reinstall them through their utility which is found on PC here: C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
3. Cpu-Z.apk (Very important, its hard to know your hardware without this).
4. Magisk v22.0.apk (They no longer have a separate Magisk Manager)
5. Root Explorer.apk (This software helps navigation better but you can use any Explorer of your choice).
6. Root Checker.apk
7. Stock Firmware XT2113-3_KIEV_RETEU_10_QZK30.Q4-40-62_subsidy-DEFAULT_regulatory-XT2113-3-EU-SAR_CFC.xml (This is important if you mess up the boot image trying to root). You can get the firmware of your choice at Motorola Official Firmware For Kiev.
8. Patience (and a good movie keeping you going).
As of now this device as no TWRP, so you have to do this the old fashioned way to root. And just so you know, I used Windows 7 for all of this.
Pre-Rooting
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. Everytime you wipe the phone or do anything messing with the boot image the phone resets itself to factory settings, and tries to push an update. Just take the silver key thing and pop it out. You will have to push it back in and out in a second, but start with it out.
3. Make sure your wifi is OFF.
4. Make sure your SD is in and mountable and all files you need are on the card.
5. Make sure you Save boot.img to your SD Card from your firmware files. This is very important for root.
6. Make sure your developer options are activated.
7. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below).
8. Make sure to check CPU-Z for your hardware specs so you download the right files for the phone and avoid potential problems.
9. Make sure you manually set USB to Transfer files (no other option will work and by default its set to Charge this Device).
10. Make sure you have the STOCK CABLE that comes with the phone. Like most Motorolas this model is funky about using other cables.
11. Make sure you back up all your calls, texts, pics, etc. Flashing the firmware is the ultimate factory reset and you will lose all your files on the phone. SMS Restore is a good software to backup Calls and Text logs and it supports keeping MMS.
12. Make sure you have the internet. It is necessary for some steps.
Rooting
1. Make sure all the firmware files are extracted into your Minimal ADB and Fastboot folder (or whatever ADB folder you're using for this).
2. Open FlashFile.xml in Notepad. This is located among the firmware files you put in the Minimal ADB and Fastboot folder.
3. Cut, copy, and paste everything from the FlashFile that is shown and then paste it in an online Flash file Converter. I used Online Flash File Converter here.
4. Convert the text by pressing the bar below where you pasted the text. It may be in Spanish or Portuguese but is should say something like Cerar Commandos.
5. Copy the text by hitting the two pieces of paper icon in the corner after it's converted. Or just cut copy and paste manually.
6. Turn the phone completely OFF.
7. Plug your phone via USB cable into the computer.
8. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY).
9. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your firmware files are in the Minimal ADB directory or it won't work.
10. Paste the contents of the flashfile converter into Minimal ADB and Fastboot. This should start the process of the flashing.
11. When the entire flash is complete, boot the phone and disconnect phone from the computer. Ignore the bootloader unlock error.
12. Wait. Sometimes this takes up to 3-5 minutes on a new flash. You should see the boot animation of Motorola.
13. Push your Sim Card back into the phone.
14. Start setting up your device on the screen. Sim Card must be in or it will give you a message your phone is Network Locked.
15. Once you make it to the Wifi Setup screen take the Sim back OUT the phone. Do not connect to Wifi.
16. Once you are done with setup, go to Settings>About phone.
17. Go all the way down to Build Number and press it until you unlock Developer Options.
18. Go to Settings>System>Advanced>Developer Options. Advanced is a pull down tab that will reveal Developer Options.
19. Disable Automatic System Updates. I know this is hard for some people, but a forced OTA update may cause problems and prohibit root.
20. Enable USB Debugging. Disable Verify bytecode of debuggable apps. Disable Verify apps over USB if it is highlighted. Exit.
21. Put your SD/Sim card back into the phone.
22. Go to the Files folder and install Magisk first, then Root Explorer and Root Checker.
23. Open Magisk. You will see Magisk and App. Hit Install by Magisk (a fingerprint looking icon is to its left).
24. Allow Magisk to access photos, media, and files if it asks.
25. Select option "Select and Patch A File."
26. It will take you to a screen where you can select your explorer to navigate to your SD card where you saved the boot.img. Go there and select it.
27. Magisk will save it as magisk_patched.img. Once you get it patched, find where it saved, make sure it's on your SD card and then turn off the phone.
28. Plug your phone via USB cable into the computer.
29. Press Volume Down and Power to boot into fastboot mode.
30. Open up a fresh Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure you transfer the magisk_patched.img that Magisk patched off your SD card into this folder.
31. Rename your original boot.img to "boot.img original" or whatever distinct name you want to give it in your Minimal ADB and Fastboot folder.
32. Rename your magisk_patched.img to boot.img.
33. In Minimal ADB and Fastboot type "fastboot flash boot boot.img" and hit enter.
34. If all goes well it should flash to the partition before it says done and in how many seconds.
35. When it is done, reboot phone by selecting START (keep pressing volume rockers until you see it, then press the power button).
36. Wait for the bootloader cannot be trusted screen to pass (may take a minute) and wait for the Hello Moto opening.
37. Open Root Checker and confirm root. You can uninstall it after confirmation if you like.
38. Open Root Explorer. A prompt asking you to grant permission should pop up.
Congrats. You should be rooted now.
***NOTES SO YOU DON'T FREAK OUT***
1. Do NOT flash someone else's patched boot image. It WILL NOT WORK. Do the work, find your firmware, and patch the boot image yourself. You're asking for bootloop hell if you do as your boot.img that Magisk patches needs to match that particular firmware you used.
2. While it hasn't happened to me, You may have followed everything perfect and it still bootlooped. Save yourself the frustration and just flash it over. See the next section on the proper way to flash so you don't lose your baseband, IMEI, or any other important stuff.
3. While you won't lose anything just flashing boot.img, you will lose everything having to flash ALL the firmware over. Keep backups of all your important stuff.
****Notes on Flashing The Stock Firmware if you have to****
In the event you bootloop and have to start from scratch, follow my guide on restoring the firmware on the phone. And don't worry - it won't relock the bootloader. You can find my guide here: The Complete Noob Guide to Flashing via Fastboot MetroPCS Moto One 5G Ace XT2113 [Qualcomm Version]
Hope this helps my fellow TMobile and subdiary acolytes and othoers. I have flashed and reflashed my phone with different variant roms trying to force Write status and beta testing scripts for @lebigmac on our device so it's pretty straightforward now.
I will try and answer questions if I can or point you in the right direction.
Click to expand...
Click to collapse
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset

bobbyp1086 said:
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset
Click to expand...
Click to collapse
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.

Articul8Madness said:
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.
Click to expand...
Click to collapse
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.

bobbyp1086 said:
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.
Click to expand...
Click to collapse
If your bootloader is unlocked the only way you should have gotten the corruption is if you flashed an incompatible firmware. Mine came with MetroPCS but I've flashed RETUS and RETEU well. I'd stray from any VZW or ATT software just because you can't trust their firmware won't lock down the bootloader.
Or maybe the software just didn't download well. Try re-downloading it . I've had a bad download mess up a flash before.

I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch

bobbyp1086 said:
I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch
Click to expand...
Click to collapse
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.

Articul8Madness said:
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.
Click to expand...
Click to collapse
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /
{
"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"
}
and fix file permissions, it's in settings

bobbyp1086 said:
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /View attachment 5279427View attachment 5279429View attachment 5279431View attachment 5279433 and fix file permissions, it's in settings
Click to expand...
Click to collapse
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.

Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.

I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?

I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked

bobbyp1086 said:
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.
Click to expand...
Click to collapse
Android 10 is very challenging. It is easy to root but it is a trickable root with a false sense of root since Google locked all Android 10 and newer as Read Only on the System with this super partition crap trying to be Apple.

Skel40 said:
I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?
Click to expand...
Click to collapse
Check my guide. I posted link to where the repository is.

Skel40 said:
I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked
Click to expand...
Click to collapse
You will not pass safety net because you've rooted it and Android 10 will block it. It isn't necessary, especially if you delete all Google stuff and their tracking Covid crap.

Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
Hi @Articul8Madness. Thanks for mentioning me
There's a Motorola user who recently got my script to work using the troubleshooting repair script that I posted here
It turns out the lpmake arguments that are auto-generated by the original script were flawless and were not the root cause of the unidentified lpmake error that some Motorola users were experiencing at the end of the original script. According to @Xiaoleng the error was most likely caused by some kind of new Motorola security feature that prevents the terminal command from executing if the arguments are too long. Go figure.
And he was even able to fastboot flash the super_fixed.bin in one piece without having to first split it up into chunks. That's a huge surprise to me. I always thought Motorola users can only fastboot flash super sparsechunks?!
Please feel free to give it a try and report back your results. Thanks. Good luck!

[OTA / UPDATE GUIDE WHILE MAGISK ROOTED] UPDATE FIRMWARE *WITHOUT LOSING DATA* (for stock Samsung ROM users)

** PLEASE DO YOUR PART AND READ / SEARCH / RESEARCH BEFORE POSTING AND/OR ATTEMPTING ANY MODIFICATIONS TO YOUR DEVICE. THIS GUIDE ASSUMES YOU ALREADY KNOW HOW TO OR HAVE ALREADY UNLOCKED YOUR BOOTLOADER, ALREADY ROOTED YOUR DEVICE, HOW TO FIX KG STATE ISSUES, HOW TO USE ODIN, 7-ZIP, LZ4 TOOL, ETC. THIS POST IS SIMPLY MY OBSERVATIONS AND STEPS TO UPDATE THE FIRMWARE WHILE ROOTED WITH MAGISK, WITHOUT LOSING DATA / REQUIRING A WIPE. MODIFYING YOUR DEVICE COMES WITH INHERENT RISKS, AND IT'S NOT MY RESPONSIBILITY IF YOU LOSE YOUR DATA. THE STEPS I SHARE HAVE WORKED WITHOUT FAIL FOR ME, BUT THAT DOESN'T MEAN YOU MAY NOT RUN INTO PROBLEMS. BACKUP YOUR DATA.**
The reason I decided to write up this guide is because of the extremely large amount of misinformation, as well as general noob-ness (no offense to anyone, just my observations to be completely honest), that I seem to come across when it comes to the Samsung sub-forums around here. I've seen many people state that updating the firmware on this particular device (Galaxy Tab S6 LITE) will REQUIRE a data wipe, which is simply not true in my experience. However, I will admit that the procedure is extremely bass ackwards when it comes to this particular device, so maybe that's why people have been claiming this.
This guide only applies to stock Samsung firmware users.
Spoiler: Boring Backstory (click to read):
I ditched Samsung a long time ago, after the Galaxy S5 (not TAB, but the phone) days, when they really started locking up the bootloaders on the USA variants. Only T-Mobile was excluded on that particular model, but from what I understand, pretty much all Snapdragons since then have been completely locked down, across all carriers. So first of all, F*CK Samsung for being dickholes. Other than that, I recently decided I wanted to start using an Android tablet again, so at first I bought a Galaxy Tab S6 Lite several months ago. Eventually I got the Galaxy Tab S7 Plus, after hearing (and it's true) that the S7 series tablets actually kept Widevine L1 status after unlocking bootloader / rooting. Heck yeah.
Anyway, my Tab S6 Lite just gathered dust over the last few months, but now that I'm donating it to a friend of mine who's in school, I reloaded it with stock firmware, but rooted and heavily modified (he's an art student, so having all the stock Samsung / S-Pen integrations will be very useful for him). I finally decided to take some rough notes (written and mental, lol) about the process of updating the firmware WITHOUT losing data. As in updating your device as if like taking a standard OTA, but needing to do it manually because we're rooted and modified.
Unfortunately, like I said this device is freaking weird. Not sure if it's because it's Exynos (it's my first Exy device) or what, but it doesn't follow the same procedure as I've been used to back in the Galaxy phone days, other Tabs I've come across, nor with the Galaxy Tab S7 Plus I now own... Which is to literally follow the instructions as the creator of Magisk himself, @topjohnwu, published on his Github (see the Samsung section): https://topjohnwu.github.io/Magisk/install.html
But following those official Magisk instructions will result in this particular device not being able to boot, and you will need to wipe and start over. tl;dr - normally for sammy devices, you need to patch the full AP file in Magisk Manager and flash that in the AP slot in Odin because it also patches vbmeta to work around AVB. But for this device, this doesn't seem to be the case. At least in my experience.
Spoiler: Technical Rantings; Still Worth A Read IMO (click to read):
For some reason, on this particular device, you can't just patch the entire AP file. That will result in your device not booting, and eventually requiring a clean (wipe it all) Odin flash. Instead you need to flash the full, unmodified AP file (which normally would screw you over and is completely advised against), and then some extra steps... Anyway, I've outlined those steps below, as well as some preparation you'll need to do beforehand, which really just involves patching the boot image itself and placing in a .tar archive, which I would hope you already know how to do to be perfectly honest.
Not sure WTF is going on, as on other Samsung devices, you want to patch the entire AP file because Magisk will also automatically patch the vbmeta image thus working around AVB restrictions. It's really freaking weird to me because normally failing to patch vbmeta should normally result in inability to boot and subsequent SOL situation where you need to wipe... but with this device, it's ass backwards. And Magisk does indeed patch the vbmeta image when patching the full AP for this device... Why instead you need to skip patching the full AP file and flash just the patched boot image separately (thus skipping patching vbmeta) makes little sense to me. Not sure why this tablet is different, but again I'm not usually a huge fan of Samsung anyway so I really don't give AF. But they make the best Android tablets, so now that I've recently bought them (though I won't have this model S6 Lite for much longer), well I wanted to share with you guys; here are my working update instructions for the Galaxy Tab S6 Lite, without losing data. At least it works for me.
FOLLOW THIS GUIDE AT YOUR OWN RISK! AND BACKUP YOUR CRAP BEFORE ATTEMPTING, JUST IN CASE.
I'm not responsible for any problems you incur, etc. etc. blah blah.
(BTW, this is for the SM-P610 - WiFi USA version. Not tested on LTE, and if you try on LTE, you'll also have a CP file to flash, fyi. I have no experience with the LTE model either). This guide assumes you already have your bootloader unlocked, know how to use Odin, aren't a complete noob, and can at least restore back to stock if crap goes sideways.
Below are some bonus resources anyway, to hopefully clear up some silly questions before they come up.​
* Please thank the devs and OP's of these posts if you find them helpful and/or use their tools. It's the least you can do! *
[FRIJA] USE THIS TO DOWNLOAD THE LATEST FIRMWARE: https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910584/
[ODIN *PATCHED*] I RECOMMEND VERSION "Odin3 v3.14.1_3B_PatcheD": https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
[LZ4 TOOL] DECRYPTS LZ4 EXTENSION'D FILES: https://github.com/lz4/lz4/releases
[BL WARNING TEXT REMOVAL] TO REMOVE UGLY WARNING TEXT AT BOOT: https://forum.xda-developers.com/t/...tock-firmwares-modded-bl-warningtext.4195829/
* Please thank the devs and OP's of these posts if you find them helpful and/or use their tools. It's the least you can do! *
***************************** STEPS TO UPDATE FIRMWARE: *****************************​
Use Frija (download thread provided above), or download firmware from somewhere like samfw.com
Open / unzip the firmware, and then open the AP archive and pull boot.img.lz4.
Using LZ4 tool (download thread provided above), decrypt boot.img.lz4 to boot.img
* you can just simply drag and drop the boot.img.lz4 file over the lz4.exe binary in Windows explorer
Copy boot.img to your tablet. Open Magisk (Manager) and patch the file.
Copy the Magisk Patched boot file back to your PC. Rename it as boot.img
Create .tar file (tar file name doesn't matter) containing ONLY boot.img - do not use compression (if using 7-Zip, add the boot.img to archive, select archive format as "tar", and use compression level as "Store"). While the .tar file name doesn't matter, IT SHOULD ONLY CONTAIN A SINGLE FILE - boot.img
Reboot to download mode. Hook up your tablet to your PC.
**IT MAY GET SCARY HERE ON SOME STEPS, BUT CONTINUE FOLLOWING THIS EXACTLY**
(Use Odin3 v3.14.1_3B_PatcheD, link provided above)
Flash new stock firmware, using BL / AP / HOME_CSC (must use HOME_CSC to not wipe data, DO NOT USE THE REGULAR CSC FILE OR IT WILL AUTOMATICALLY WIPE). If you have LTE version, also flash the CP file in CP slot. WiFi version does not have CP file.
Using default Odin options is fine (F. Reset Time, Auto Reboot). In fact, I would recommend it for the sake of following this guide.
It'll be scary, but it will reboot a few times and eventually boot into recovery mode. Don't interrupt the process and let it eventually settle on its own into recovery mode (after a few seemingly failed boot attempts).
It'll make you think you're screwed and must factory wipe the device. DON'T FREAK OUT. Options will be:
Try again
Factory data reset
View recovery logs
While USB cable is still plugged into the tablet and computer, select Try again (tap power button, but don't hold the button down) and then immediately hold down volume up and down at the same time so that and until it goes back to download mode. As prompted, press volume up to continue.
Using Odin, flash ONLY the magisk patched boot image tar file (uncheck BL / CSC boxes if Odin is still open from before). Also you can flash the modified bootloader splash tar as well at this time, might as well kill 2 birds with 1 stone. Again, you can just leave default options enabled (F. Reset Time, Auto Reboot).
Again, this will be very scary. It won't boot to system, but rather bootloader again. Probably an error at the bottom, something like "failed to load locales from the resource files" / "failed to compare" / whatever. However, the normal recovery options should now be available.
YOU WILL ONLY WIPE CACHE PARTITION (scroll down to "Wipe cache partition", and then confirm yes. Then select "Reboot system now".
It will take a while to boot, but this time you should eventually get to the lone "SAMSUNG" boot logo (this is a great sign), and then eventually get the "Tablet is updating..." box which shows the progress as it re-optimizes all of your apps.
That's it, and once it finishes optimizing your apps, should continue to load to your lockscreen! If so, congratulations, you've now updated to the latest firmware while retaining root without losing your data!
**********************************************************​
Even with a heavily modified tablet, this has worked over several months, including the jump from A10 to A11. SafetyNet still passes (using kdrag0n's module), YouTube Vanced (my module), LSposed with Firefds kit and GravityBox R, and a bunch of other Magisk modules.
I'm very much aware you can save time by tweaking the above process, but this was the very safest exact procedure I could think of, so I recommend following it exactly as I wrote above.
Good luck, I hope it works for you, and enjoy your tablets!

just in case

and another

Damn, thanks dude. I'd just about given up clean flashing and thought I'll give your suggestion a go and it worked like a Boss! Im using the LTE version and not a single hiccup. Thank you for saving me a huge hassle. Only things i didn't follow was use frija, paid$2.99 and got the firmware. Everything else was exactly what you did. Worked man! Thank you so much again.
If anyone wants the latest. ACR firmware for SM-P615, lemme know and I'll share my drive link with you.
Cheers! Kudos. On latest may update now.

Didn't do the 2 birds one stone thing, was scared. I'm gonna do that later. Again, just to clarify, i run Magisk only for and root level file brousing, does it really matter if i don't pass the test? Everything runs as it should, just curious if there was a benefit to it.

Thanks a lot for this detailed guide!
It worked perfectly on my Galaxy tab S7, I updated it successfully with magisk already installed.

didnt work for me on the CUH2 update

sunmybun said:
didnt work for me on the CUH2 update
Click to expand...
Click to collapse
I actually just tried it and it does still work for CUH2. I am happy for this firmware as I was having a weird system reboot every time I unlock with PIN.

shattacrew said:
I actually just tried it and it does still work for CUH2. I am happy for this firmware as I was having a weird system reboot every time I unlock with PIN.
Click to expand...
Click to collapse
it mightve not worked for me because i decrypted my data partition by factory reset and disabling the system to encrypt and check the partition before booting.
one of the tablets is encrypted and is using the KOO firmware, and the updating steps doesnt work either.
Ive flashed the tablets that were originally XAR firmware to KOO firmware.
im giving my inputs with my situation.
if anyone can find a way for my situtation, let me know =)

So I haven't updated my rooted tablet since the September 2020 update. Can I still jump to the latest version and still root or do I need to do some additional steps first?

still hasnt worked for me. I even went back to the tablet being encrypted.
for people who updated to DUL9 and rooted. please tell me the steps because it doesnt work for me

Can you specify the process of creating the TAR file? I patched the boot file from AP in Magisk already.
I used WinRar to make a .zip containing boot.img, then renamed it from AP-SLOT.zip to AP-SLOT.tar. Don't know if that's acceptable. I also used the "Store" compression method.
Afterwards what slot in Odin do you upload the .tar file to? I tried the AP slot but it hangs at "File analysis.....". It seems like it want a .tar.md5 file

TheCoryGuy said:
Can you specify the process of creating the TAR file? I patched the boot file from AP in Magisk already.
I used WinRar to make a .zip containing boot.img, then renamed it from AP-SLOT.zip to AP-SLOT.tar. Don't know if that's acceptable. I also used the "Store" compression method.
Afterwards what slot in Odin do you upload the .tar file to? I tried the AP slot but it hangs at "File analysis.....". It seems like it want a .tar.md5 file
Click to expand...
Click to collapse
you cant just rename from zip to tar. you have to use a diff program like 7zip to make into .tar

Great instruction. Everything is up and running and that stupid splash screen is gone. Great job, @i5lee8bit.

Late for the party...
I've found a python utility to download Samsung firmware at full speed.
It's quite easy to use:
SamLoader
[Tool] Samloader (SamFirm / Frija replacement)
Hello, I recently wanted to download some firmware for my Samsung device, but I realized that there is no 100% open source program to do so. In fact, all the tools that claim to do so require a library that is packed by Themida (so it is...
forum.xda-developers.com

Thank you @i5lee8bit this worked like a charm.
One question though, using a patched Odin is a not a requirement, is it?
Thank you @eddiefive for samloader link.

I just completed this to upgrade to Android 13 on my Tab S6 Lite. It worked perfectly. Thanks so much. I'm always amazed at the community support here.

awtompson said:
I just completed this to upgrade to Android 13 on my Tab S6 Lite. It worked perfectly. Thanks so much. I'm always amazed at the community support here.
Click to expand...
Click to collapse
I had successfully used this method to update to Android 12 (SM-P610_2_20221024120141_tk8omuwosv_fac)
I just tried updating to Android 13 (SM-P610_3_20230118120131_f9h5nltlpa_fac) and after wiping the cache step and rebooting to system, it goes into bootloop.
I tried twice, and in fact I re-downloaded everything and did all the steps just in case there was any corruption in any step or I missed something. Same thing. bootloop.
Had to re-apply Android 12 to recover the tablet.
I used Odin3 v3.14.1_3B_PatcheD
Any ideas?

badabing2003 said:
I had successfully used this method to update to Android 12 (SM-P610_2_20221024120141_tk8omuwosv_fac)
I just tried updating to Android 13 (SM-P610_3_20230118120131_f9h5nltlpa_fac) and after wiping the cache step and rebooting to system, it goes into bootloop.
I tried twice, and in fact I re-downloaded everything and did all the steps just in case there was any corruption in any step or I missed something. Same thing. bootloop.
Had to re-apply Android 12 to recover the tablet.
I used Odin3 v3.14.1_3B_PatcheD
Any ideas?
Click to expand...
Click to collapse
Not really. I did not use the patched Odin but I don't think that'st the problem. The boot after wiping cache did take long time, but no boot loops. The trickiest part is getting it to reboot into download mode after the "Try again" step. Wish I could be more help.

awtompson said:
Not really. I did not use the patched Odin but I don't think that'st the problem. The boot after wiping cache did take long time, but no boot loops. The trickiest part is getting it to reboot into download mode after the "Try again" step. Wish I could be more help.
Click to expand...
Click to collapse
Thanks, rebooting to download was easy for me, but the damn thing almost immediately would go into bootloop after the wipe, no long wait.