Database Info

LG AS730 (L7 Variant) Rooting / Unbricking / More

LG Optimus Select (LGAS730)
I figured since there really isn't any information on my device, I'd write up some useful information for anyone who has Revol/Alltel and wants to trick out thier phone with root goodness.
I wrote this up at 3 in the morning, so if there's any typo's I'll get to them in the morning
Before anyone roots their device, be aware that our phone has a locked bootloader + System App Checking,
which means if you remove certain system apps, you will be greeted with a "Security Error" message on system start,
resulting in a shiny new brick.
So, as of now, I don't recommend deleting any apps until:
A) We figure out how to unlock our phone and disable the checks or
B) There is a list of safe apps to remove.​
Rooting your LG Optimus Select:
I was previously using the universal ICS/JB root method found here http://forum.xda-developers.com/showthread.php?t=1886460
But it seems that an update might of broke the exploit.
I hate promoting this program because it uses stolen code/it's garbage but it works. (Unlockroot Pro Free)
Just download > Install > Uncheck the boxes to all the toolbar spam > Run > Root > Say no to the powersave crap
I would instead promote SuperOneClick which should work aswell, but it kept freezing for some reason.
Key Combinations:
Power + Vol up + Home = Recovery
Power + Vol Down + Home = Factory Reset
Vol Down + Up / Then plug in USB = Emergency Mode
Downloading the .cab for your LG phone:
1. Find your LG phone model and serial number. [You will have to take out the battery to find the serial number/]
2. TYPE in the following URL or COPY AND PASTE (do not click on link it will not work) it in the URL Line: http://csmg.lgmobile.com:9002/svc/po...eck.jsp?model=[model]&esn=[serial_number]
Now replace the [MODEL] and the [SERIAL NUMBER] with your phones model and serial number.
3. Hit enter to load the page. Now the page should be blank less a string. In order to view the information you have to view the page source code:
a) On Firefox: Tools --->Web Developer --->Page Source (Cntrl + U or Cmd + U)
b) On Safari: Right click blank area anywhere on the page, select View Source in the menu.
c) On Internet Explorer: View --->Source
d) On Chrome: Click Customize and Control at the right of URL Line --->Tools --->View Source
4. Find the number inside <ESN></ESN> line.
5. Type in the following address in the URL Line: http://csmg.lgmobile.com:9002/csmg/b...heck2.jsp?esn=[esn_number]
6. Replace the [esn_number] with the number you got from the first source code.
7. Load the page which should be blank again and just view source code using the above mentioned method.
8. You will then see all of the information about your particular phone including your firmware update link which would lay between <SW_URL></SW_URL>.
9. Copy the URL into your URL Line and hit enter. The download should start automatically.
Click to expand...
Click to collapse
@Nathan.7118391
This program can also be downloaded that does pretty much everything for you: http://forum.xda-developers.com/showpost.php?p=13682353&postcount=1
Recovering From A Bricked Device / Security Lock:
1) Download the LG Support Tool http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe
2) Once installed, open it, and click Install USB Drivers > Other Carriers > LGAS730 > Double Click and install
3) Install KDZ_FW_UPD http://www.2shared.com/file/s1ZPxEPL/KDZ_FW_UPD_EN.html (Make sure to install msxml.msi first)
4) Download the the most current .cab for your phone (Method can be found above)
5) Rename .cabs to .kdz
6) Run KDZ as an Administrator > Click the little folder > browse for the .kdz you just renamed
7) Put your phone in Emergency Mode (Vol Down + Up / Then plug in USB = Emergency Mode)
8) Click Launch Software Update
9) You're phone should be working now!

Rooting does work. I also have installed Google Now but for some reason the logcat says 400 Bad Request when attempting to login, so you get the Offline Voice Recognition, Online Voice Recognition, Google Search, but no Cards for some reason.
On another note: It does seem that it only checks that the files still exist, I replaced a number of files in /lib with their Google Now versions and it hasn't made any complaints, the same goes for replacing GoogleTTS.apk (which doesn't work for some reason, we don't get the Google Now TTS, but that doesn't matter as much)
Overall, I'd have to say that I believe the bootloader doesn't check the CRC32 checksum, rather it simply checks that the files still exist.
EDIT: I redact my previous statement about Google Now not working right, it does :3 Just needed to remove and re-add my Google account.
UPDATE:
Another trick is to enable USB Mass Storage Mode:
To do so, Install DriveDroid from the Market. (You can either use disk images to separate your data from the SD Card or use the trick below)
Enable USB Mass Storage as directed by the application (within it's settings)
Plug and Unplug your phone with DriveDroid closed (Do NOT press any of the connectivity options when they appear, they should all be unchecked)
If all goes well, the USB Mass Storage Mode application built into Android will startup and your Phone will mount on your PC. (It doesn't seem to happen 100% of the time, so just toy around, it does work.)
UPDATE 2/6/13:
Firmware Update AS73012a has been released? Anyone install it yet?

So I just got this phone (I'm moving over from a Samsung Fascinate), And so far I'm loving it. It's was smoother the GPS is way more Accurate ! But I do have one qustion. What System Apps are safe to remove ?

NomadCF said:
So I just got this phone (I'm moving over from a Samsung Fascinate), And so far I'm loving it. It's was smoother the GPS is way more Accurate ! But I do have one qustion. What System Apps are safe to remove ?
Click to expand...
Click to collapse
Okay so far I've found it's safe to remove the fallowing.
1. Facebook
2. Twitter
3. Built in Stock weather
4. Built in Stock calendar

NomadCF said:
Okay so far I've found it's safe to remove the fallowing.
1. Facebook
2. Twitter
3. Built in Stock weather
4. Built in Stock calendar
Click to expand...
Click to collapse
That's great, I just noticed in the Optimus L7 thread that their boot loader has been unlocked, was wondering if someone could test this patch with our device as its an L7 variant. According to the threads, its possible to enter emergency mode if a soft brick happens. If anyone's courageous enough to try, please report back. I'd try but I can't afford to replace my phone if something happens to the point that I can't access emergency mode.
Edit: its worth noting that if it does work, we could use the online CWM builder to build a recovery for our device then work on a custom ROM.

veris said:
4) Download the .cab firmware for our phone http://csmgdl.lgmobile.com/swdata/WEBSW/LGAS730/ABPTBK/AS73011a_01/AS73011a_01.S1a_01.cab
Click to expand...
Click to collapse
the .cab firmware does not exist

Is there any way someone can share the CAB file? or direct me to it please

Some Other info for this phone:
Service Menu Code : ##5473784236368
Service Menu Security Code : 000000

NomadCF said:
Some Other info for this phone:
Service Menu Code : ##5473784236368
Service Menu Security Code : 000000
Click to expand...
Click to collapse
Sorry for the no responses, I hadn't been able to do anything else with the phone after we got root working. Unfortunately now I no longer have the device and now have the VZW LG G2.

I also have recently moved to another service provider and a new phone.
But I still have it laying around somewhere, I might mess around with it, maybe try to get CWM working.
Also, I've gotten quite a few PM's after my long absence from XDA for the .cab
I'm assuming since a new firmware release, they've probably taken down the old link.
There was a program I had found which generated the URL based on any LG phone serial, I'll try to find it and post the application which would be 10x more beneficial along with a current .cab.
>Method added to original post, I don't have my phone at the moment to do it myself and get the URL, sorry ):
>Application for the lazy can be found here: http://forum.xda-developers.com/showpost.php?p=13682353&postcount=1

veris said:
LG Optimus Select (LGAS730)
I figured since there really isn't any information on my device, I'd write up some useful information for anyone who has Revol/Alltel and wants to trick out thier phone with root goodness.
I wrote this up at 3 in the morning, so if there's any typo's I'll get to them in the morning
Before anyone roots their device, be aware that our phone has a locked bootloader + System App Checking,
which means if you remove certain system apps, you will be greeted with a "Security Error" message on system start,
resulting in a shiny new brick.
So, as of now, I don't recommend deleting any apps until:
A) We figure out how to unlock our phone and disable the checks or
B) There is a list of safe apps to remove.​
Rooting your LG Optimus Select:
I was previously using the universal ICS/JB root method found here http://forum.xda-developers.com/showthread.php?t=1886460
But it seems that an update might of broke the exploit.
I hate promoting this program because it uses stolen code/it's garbage but it works. (Unlockroot Pro Free)
Just download > Install > Uncheck the boxes to all the toolbar spam > Run > Root > Say no to the powersave crap
I would instead promote SuperOneClick which should work aswell, but it kept freezing for some reason.
Key Combinations:
Power + Vol up + Home = Recovery
Power + Vol Down + Home = Factory Reset
Vol Down + Up / Then plug in USB = Emergency Mode
Downloading the .cab for your LG phone:
@Nathan.7118391
This program can also be downloaded that does pretty much everything for you: http://forum.xda-developers.com/showpost.php?p=13682353&postcount=1
Recovering From A Bricked Device / Security Lock:
1) Download the LG Support Tool http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe
2) Once installed, open it, and click Install USB Drivers > Other Carriers > LGAS730 > Double Click and install
3) Install KDZ_FW_UPD http://www.2shared.com/file/s1ZPxEPL/KDZ_FW_UPD_EN.html (Make sure to install msxml.msi first)
4) Download the the most current .cab for your phone (Method can be found above)
5) Rename .cabs to .kdz
6) Run KDZ as an Administrator > Click the little folder > browse for the .kdz you just renamed
7) Put your phone in Emergency Mode (Vol Down + Up / Then plug in USB = Emergency Mode)
8) Click Launch Software Update
9) You're phone should be working now!
Click to expand...
Click to collapse
Hey, I realize this thread is over three years old now, but are you still able to help? I followed all of the instructions to get the phone back to stock, but it can't extract the kdz file. I used UpTestEX_mod2_marwin.exe to convert the cab to kdz, and KDZ_FW_UPD.exe is telling me "Extract file error." Any idea why or how to fix it? Thanks!

any work on a cwm or other recovery/rom? or bootloader unlock?

darkdragone said:
any work on a cwm or other recovery/rom? or bootloader unlock?
Click to expand...
Click to collapse
Sadly, it doesn't look so. Sad since I still have this phone sitting around somewhere, would love to do other things with it. But it seems that this phone may have died.

Will the current root method used on C432e7r1p8(patch03) allow install font apps?

I'm fairly reluctant to root the phone. I have had an excellent resource on here pretty much warn me against that.
I really want to put a different font on the phone. That's really the only reason I interest in rooting. I'm not wanting it just to be more decorative...I find the bold font hard to read in whatever app may be presenting bold text.
So anyway, l'd hate to do the root (which I understand is not really a full root), and then find it doesn't allow me to install the new fonts anyway.

ewingr said:
I'm fairly reluctant to root the phone. I have had an excellent resource on here pretty much warn me against that.
I really want to put a different font on the phone. That's really the only reason I interest in rooting. I'm not wanting it just to be more decorative...I find the bold font hard to read in whatever app may be presenting bold text.
So anyway, l'd hate to do the root (which I understand is not really a full root), and then find it doesn't allow me to install the new fonts anyway.
Click to expand...
Click to collapse
Rooting is 'full', just that technology (Android 9/10) is changing.
For AdAway app you must enable Systemless hosts (option/module in Magisk Manager), for modules Magisc automatically handles symlinking to the read-only System
So, even from root explorer (sugested MiXPlorer), you see as if AdAway wrote directly to the file system/etc/hosts, or that BusyBox tools are applied directly to system/xbin
Since EMUI 8, Huawei replaced Boot with Ramdisk, and since EMUI 9.1 Ramdisk is also read-only, hence Magisk must patch to Recovery instead
Because of that, you cannot have TWRP if you go for root (don't consider an alternative solution to flash TWRP over erecovery). But formally speaking, TWRP is not part of root (on the old systems, you could have TWRP without root, vice versa, or both). Even with TWRP, TWRP could not change read-only System, and it cannot see dynamical linking active only when system is running (Magisk running). Plus, because of new encryption since EMUI 8, TWRP cannot handle Internal storage (don't consider alternative solution to completely wipe Internal storage and format it without encryption)
All together, from system, systemless works fully seemlessly (as 'full' root). Just you don't use TWRP
To root:
- Install Huawei UpdateExtractor (PC), download update.zip for your 9.1.0.252 c432 from FirmwareFinder, unzip and extract Recovery_Ramdisk.img
- Copy Recovery_Ramdisk.img to the phone, install Magisk Manager, choose Install and then Patch a file, check all three options Preserve AVB, Preserve encryption, Recovery file
- Copy patched_boot.img (rename to patched_recovery.img or so) to PC and flash from Fastboot to Recovery (similar like flashing TWRP) - of course, Bootloader must be unlocked (you have code) and OEM/FRP must be unlocked
- You must boot to system through recovery (because Magisk was patched to recovery), if Magisk Manager shows rooted, you are done
To unroot:
- In case of bootloop or anything: just flash stock Recovery_Ramdisk.img back to Recovery, and you are back to stock
- Regular unrooting: take Uninstall from Magisk (and later, optionally, flash stock recovery_ramdisk.img)
- In case of OTA: unroot (regularly, as above), accept OTA, root again
Btw, you could update your sig now (no more EMUI 5)

Thanks for all the info.
One thing I did not understand from that: will rooting then allow me to add different fonts?
Thanks for the reminder on the sig. I've been thinking of it but procrastinating...which means I would ultimately forget.

ewingr said:
Thanks for all the info.
One thing I did not understand from that: will rooting then allow me to add different fonts?
Thanks for the reminder on the sig. I've been thinking of it but procrastinating...which means I would ultimately forget.
Click to expand...
Click to collapse
Font size can be changed in Settings /Display
I never changed system fonts but there are Magisk modules to do so, search by Google, eg:
https://forum.xda-developers.com/apps/magisk/avfonts-march-6-t3760827
https://forum.xda-developers.com/apps/magisk/module-midnightcore-one-midnight-modules-t3762758

Maybe I just am having a mental block...I can't find the firmware in FF. I searched on each of these as criteria:
MHA-L129C432
MHA-L129C432E7R1P8
9.1.0.252
9.1.0.252 c432
MHAJ-L129C432 9.1.0.252
None of those searches found a FW for L129 for the 9.1.0.252 version. I did see a lot for MHA-LGRP2.
I used FF on the phone. I downloaded FF for the PC, and can't figure out how to use it. I put a model in on the Main Page, nothing happens. I see no way to put a model in on the Search Firmwares page.
Of course, I was updated to 9.1 via OTA, so all the work I did getting to 9.1 did not involve downloading the firmware to my PC, so I don't have it from all that work.

ewingr said:
Maybe I just am having a mental block...I can't find the firmware in FF. I searched on each of these as criteria:
MHA-L129C432
MHA-L129C432E7R1P8
9.1.0.252
9.1.0.252 c432
MHAJ-L129C432 9.1.0.252
None of those searches found a FW for L129 for the 9.1.0.252 version. I did see a lot for MHA-LGRP2.
I used FF on the phone. I downloaded FF for the PC, and can't figure out how to use it. I put a model in on the Main Page, nothing happens. I see no way to put a model in on the Search Firmwares page.
Of course, I was updated to 9.1 via OTA, so all the work I did getting to 9.1 did not involve downloading the firmware to my PC, so I don't have it from all that work.
Click to expand...
Click to collapse
Look for MHA-LGRP2-OVS - see screenshots.
You can also find through Web:
https://pro-teammt.ru/firmware-database/?firmware_model=MHA-LGRP2-OVS
Btw, there are several b252 packages there, all the same size (and probably all ok) but I was told that package number #279403
is the one that is distributed by OTA

Thanks.
I saw the MHA-LGRP2-OVS ones, but I thought I needed to find one with identical name to the one I'm on.
This stuff doesn't make much sense...at least not logical. Only experience and/or help makes it possible to get it done.
Appreciate y our help.

Well, I don't know what's going on. I downloaded the FW from the link you provided, as well as from FF on the phone.
The one from the phone, once I transferred it to the PC, wouldn't extract anything from the zip.
The one from the link extracted, but when I loaded the Update.app into Update EXtractor, I got this error:
So, I then downloaded a different version from the web site (282444), and got this in Update Extracter:
Maybe it's warning me to not root:silly:
I am going through the thread about the extracter tool now to see if I find anything helpful. First blush looks like I'd need to make a profile file that is outside the limits of my knowledge. We'll see.

I found a post saying:
Try with crc check off (in settings) for extracting
Click to expand...
Click to collapse
So I turned off the settings outlined in red:
I ended up with these two files and sizes:
Do those sizes look right?

ewingr said:
I found a post saying:
So I turned off the settings outlined in red:
I ended up with these two files and sizes:
Do those sizes look right?
Click to expand...
Click to collapse
Yeah, I also switched checksum off and it showed things as usual.
Extracted Recovery-Ramdisk (32 MB is usual size, you need only that IMG file):
https://mega.nz/#!g4lwiCIC!ikK7xJk2j1G9aSsIj1y0sQsV_s6pWTcrxCJtn56YCik
Btw, now having also service repair package for MHA-L29 9.1.0.252 c432E7R1P8 (like you used MHA-L29c432b386), i.e., suitable for DLOAD installation (if anything goes wrong):
https://www.androidfilehost.com/?fid=4349826312261725171

zgfg said:
Yeah, I also switched checksum off and it showed things as usual.
Extracted Recovery-Ramdisk (32 MB is usual size, you need only that IMG file):
https://mega.nz/#!g4lwiCIC!ikK7xJk2j1G9aSsIj1y0sQsV_s6pWTcrxCJtn56YCik
Btw, now having also service repair package for MHA-L29 9.1.0.252 c432E7R1P8 (like you used MHA-L29c432b386), i.e., suitable for DLOAD installation (if anything goes wrong):
https://www.androidfilehost.com/?fid=4349826312261725171
Click to expand...
Click to collapse
Sounds good
So, I figured I need to start by re-unlocking my phone. But at the site for DC Unlocker, the following message seems to indicate I can't unlock:
WARNING:
If your phone runs Android 8 or later with latest security patch - then this service won't work!
Click to expand...
Click to collapse
I'm on Android 9 with security patch 3.

ewingr said:
Sounds good
So, I figured I need to start by re-unlocking my phone. But at the site for DC Unlocker, the following message seems to indicate I can't unlock:
I'm on Android 9 with security patch 3.
Click to expand...
Click to collapse
OMG - I think Im writing you THIRD or FOURTH time that the same unlock code you obtained will still work!!!
Because the code is bound to the serial number of your phone and will work for unlocking/relocking for the lifetime of your phone
Huawei is just making harder and harder to obtain the code (in the old days Huawei was giving the codes immediately and for free through their own page, now with the new EMUI versions it is needed to physically open the phone and use Testpoints and code providers charge you 30 Euros or more) but once you have a code (no matter when and how you obtained) , you can use the code the same way as always (fastboot oem unlock/relock ...)

zgfg said:
OMG - I think Im writing you THIRD or FOURTH time that the same unlock code you obtained will still work!!!
Because the code is bound to the serial number of your phone and will work for unlocking/relocking for the lifetime of your phone
Huawei is just making harder and harder to obtain the code (in the old days Huawei was giving the codes immediately and for free through their own page, now with the new EMUI versions it is needed to physically open the phone and use Testpoints and code providers charge you 30 Euros or more) but once you have a code (no matter when and how you obtained) , you can use the code the same way as always (fastboot oem unlock/relock ...)
Click to expand...
Click to collapse
OMG, yes, you have. BUT the site that provided the method to do it says it won't, per the quote I put in my post. I'm inclined to believe you, you have been a very good source and patient. But, I was wondering why would they say it won't work? That is their exact words, about their tool.
That being said, I guess as that I had the code before upgrading to 9, then just following the fastboot commands with that code will work, and in fact doesn't even use their tool. . So, I'll continue with that then. The information out here can sure be confusing.
Thanks...
[EDIT]
I figured that likely it would be the ramdisk.img file, and through Google search I found a thread that verified that. So, I'm continuing on.
Thanks...

Here's an interesting thing.
After patching the file, and seeing the instructions here, I find that the file they referenced in Downloads is a different size from the one I selected to patch, which was the RECOVERY_RAMDIS.img.
Do you think that indicates a problem? I presume I should use the one I selected, which was your instructions, but wonder if maybe something went wrong with the patch.
Again, just being cautious.
Thanks for your help.

56_kruiser said:
Here's an interesting thing.
After patching the file, and seeing the instructions here, I find that the file they referenced in Downloads is a different size from the one I selected to patch, which was the RECOVERY_RAMDIS.img.
Do you think that indicates a problem? I presume I should use the one I selected, which was your instructions, but wonder if maybe something went wrong with the patch.
Again, just being cautious.
Thanks for your help.
Click to expand...
Click to collapse
So, are you the same as previously, @ewingr?
If so, have you successfully unlocked Bootloader with that old code
OpenKirin instruct to patch Ramdisk and that was correct for EMUI 8.
(If) yu are on EMUI 9.1, hence you need to patch and flash Recovery Ramdisk
When patching from Magisk Manager (MM), you have to check all three options: Preserve AVB 2.0 DM-Verity, Preserve Force Encryption and Recovery Mode.
Does MM report any error while flashing or success/ok?
You can rename patched_boot.img to like patched_recovery.img, doesn't matter, but you must flash it to Recovery (like flashing TWRP to Recovery).
Right after flashing, boot by key combo to that patched Recovery (like booting to TWRP by key combo, after flashing TWRP).
Of course, you will not flash/use TWRP here

I don't imagine you'll find this hard to believe, but I got an error on the flash attempt
I renamed the patched file to: Patched_RECOVERY_RAMDIS.img
I entered this command:
fastboot flash ramdisk Patched_RECOVERY_RAMDIS.img
Click to expand...
Click to collapse
I got this response:
target reported max download size of 471859200 bytes
sending 'ramdisk' (32768 KB)...
OKAY [ 0.721s]
writing 'ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.757s
Click to expand...
Click to collapse

56_kruiser said:
I don't imagine you'll find this hard to believe, but I got an error on the flash attempt
I renamed the patched file to: Patched_RECOVERY_RAMDIS.img
I entered this command:
I got this response:
Click to expand...
Click to collapse
Again, if you are on EMUI 9.1, forget Open Kirin instructions (for EMUI 8).
You must patch Recovery Ramdisk and flash to Recovery Ramdisk, so:
fastboot flash recovery_ramdisk Patched_RECOVERY_RAMDIS.img

I did in fact not use anything from the OpenKirin. But I apparently used wrong syntax for the command. But you providing that will help.
.......
It didn't work at first pass. I think this is why.
You will recall that in the discussion I had about the OpenKirin instructions that I mentioned they referenced a patched file in Downloads. Well, stepping through it again, and reading the small print, it says "Patched file is in downloads". So, it did not update the file I had put there, it used that to create a new patched file that was saved in downloads.
So, I will not go ahead and download that one and continue with the instructions. I bet it works this time.
---------- Post added at 10:04 PM ---------- Previous post was at 09:41 PM ----------
I think I have success. But of course, a couple interesting things:
So, you indicated I need to "boot through recovery". So I expected to hold power, and vol-up to boot into recover. But it booted to the phone.
I got a request to grant Superuser to Tasker, which I did.
I loaded Magisk, and it says it is installed, but doesn't have any indication if it is rooted. I presume it is, given the request for Superuser for Tasker.
Just now had it pop up with a notice that there is an important system update patch. I don't know if I can stop it, or if I should care about it. I did say "later" so for now, it is not installing.
One other question: Is the method to have root accomplished in the future by booting with Power+Vol-UP? If not done that way, it boots non-rooted? (I ask because it did get booted up w/o holding pwer+vol-up, and it did not show Magisk installed. After that was when I booted with the key sequence.

56_kruiser said:
I did in fact not use anything from the OpenKirin. But I apparently used wrong syntax for the command. But you providing that will help.
.......
It didn't work at first pass. I think this is why.
You will recall that in the discussion I had about the OpenKirin instructions that I mentioned they referenced a patched file in Downloads. Well, stepping through it again, and reading the small print, it says "Patched file is in downloads". So, it did not update the file I had put there, it used that to create a new patched file that was saved in downloads.
So, I will not go ahead and download that one and continue with the instructions. I bet it works this time.
---------- Post added at 10:04 PM ---------- Previous post was at 09:41 PM ----------
I think I have success. But of course, a couple interesting things:
So, you indicated I need to "boot through recovery". So I expected to hold power, and vol-up to boot into recover. But it booted to the phone.
I got a request to grant Superuser to Tasker, which I did.
I loaded Magisk, and it says it is installed, but doesn't have any indication if it is rooted. I presume it is, given the request for Superuser for Tasker.
Just now had it pop up with a notice that there is an important system update patch. I don't know if I can stop it, or if I should care about it. I did say "later" so for now, it is not installing.
One other question: Is the method to have root accomplished in the future by booting with Power+Vol-UP? If not done that way, it boots non-rooted? (I ask because it did get booted up w/o holding pwer+vol-up, and it did not show Magisk installed. After that was when I booted with the key sequence.
Click to expand...
Click to collapse
Magisk by default means you have root. You can install and disable modules in Magisk Manager, but you cannot disable root - for that you must Unistall Magisk (an option in Magisk Manager).
In MM you have a tab/menu showing all apps that were granted root - you can suspend or even revoke to some
Check in Settings/About, does it show you have b252 or b252 Patch03. I think that it thinks you are on b252 without Patch03, and it wants to install that patch.
But I don't know would you loose Magisk if you accept (or even get bootloop), so better disable authomatic OTA updates for now.
Believe me, similar 'Important' patches were receiving users (starting at the same time) with various Huawei phones running EMUI 9.1, discussing on XDA what it was, but there was never an answer, nobody detected any change for something better or worse.
So you don't loose anything if About showing b252 without Patch03
To boot to Magisk you must boot with Vol+ pressed - with USB discinnected.
If connected by USB to charger or PC, booting with Vol+ pressed will boot to eRecovery.
Normal booting (without Vol+ pressed) boots to the system (Android), but with Magisk disabled (MM will say that Magisk is not installed), so no root.
Reboot again with Vol+ and you are again rooted
If it ever comes an OTA for higher than b252, you will have to Uninstall Magisk from Magisk Manager and then accept OTA (and root by yhe same procedure one more time, with recovery_ramdisk.img from the new firmware).

Anomoly with root...
Root is working, albeit with anomalies.
If I boot w/o going through the recovery/Magisk, the phone boots up w/o root, and all works fine. When I go through recovery/Magisk, it comes up rooted, but with the following untenable anomalies: Dialer/Phone does not load; Contacts are not available; As result calls I receive do not show who is calling, and I cannot make calls out.
Given that changing fonts do not give me the fix I was chasing (see this thread), I may, unroot. But given that I can boot up w/o root and it works fine, I'll hold off un-rooting for a bit.

[GUIDE] Enabling LTE on China Telecom (and others) on Pixel 3 XL (Android 10)

Being a huge fan of the Pixel series and living in China is not easy. Just upgraded my XL to 3 XL and naturally I had to enable the LTE to work in China. Regardless what you may see on the Chinese forums (gfan), all the files you need are already present on the phone.
Files you need:
1) The ADB bridge for Windows
2) The most recent factory image
3) Magisk Manager
4) Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (Magisk Manager module) - Github direct: https://github.com/wangdaning/Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (big thank you to wangdaning for allowing me to publish it.) Also attached as a zip file to this post.
If you don't understand what these files are for or where to find them, perhaps you should ask a friend to help you. Flashing anything wrong could result in an expensive brick. Always backup your data, never blindly trust a post, and do your research. This post is in good faith and I am not liable for your actions.
Now, I don't have any of the variants of 3 (Pixel 3, 3a, 3a XL) but I would assume it would work in a similar fashion; however, see above and do your research. Check file structures, read some posts, backup data, etc. If someone does try it, please report both success and failure to build the knowledge.
1) We need to ensure our phone has an unlocked bootloader. If your bootloader is locked, you WILL lose all your data. Ensure you backup everything you want to keep. There is no getting around this step. We need to be a developer first. Go to Setting->About Phone->Build number (tap it until it says you are a developer). Then go to System-> Developer options -> OEM unlocking: turn it on. Next we need to reboot to the bootloader by resetting the phone and hold the down volume key as it reboots. In the bootloader, first use the volume keys to find and select the unlock the bootloader command with the power key. Then, we need to send the following command:
Code:
fastboot flashing unlock
You will receive a wipe and security warning. Accept and reboot the phone. It will wipe and reset your phone to factory.
2) I started from a stock image (May update; QQ2A.200501.001.B2). I suggest you start from there.
3) While we have the May update in front of us, we need to extract the boot.img so it can be patched to root the phone. TWRP doesn't support us at the time of writing on Android 10. (Hope that new baby is healthy!) The boot image can be found in the zip image-crosshatch-*release code*.zip/boot.img. Transfer this boot.img to the phone to be modded to enable root.
4) Next the phone needs to be rooted. You need to download the most recent version of Magisk Manager. Once installed, open up Magisk Manager. It will report no Magisk and that's ok, we are installing it now.
5) Tap install on Magisk and it will ask if you want to install, so install. Then you need to select the method. We will choose "Select and patch a file." Tell it where you saved your boot.img and it will patch it to allow us to root the phone. The output file we need is called magisk_patched.img is on the phone. Move it back to your directory with your ADB bridge.
6) Next we need to flash this patched boot file to our phone to complete the rooting process. Reboot to the bootloader and send the two commands:
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Reboot the phone and congrats, you are rooted with an unlocked bootloader.
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
8) Download the LTE_enabler from Github or the zip file here. Open Magisk Manager and open the menu -> Modules -> "Yellow Plus" to add. Point it to the zip file.
9) Reboot and enjoy using your phone as intended.
I tried to be as detailed as I could but not be over verbose either. If any step is unclear, there are more detailed guides on this forum concerning bootloader unlocking and Magisk rooting on Android 10. As a bonus tip, does the "x" showing no data bother you and stop some services from working? If so, this can be fixed by re-pointing your captive portal to something inside the firewall. This can be accomplished with one line of code:
Code:
adb shell "settings put global captive_portal_https_url https://developers.google.cn/generate_204"
Enjoy and if you have questions about Pixel and China, feel free to post them. Support right to repair!

I downloaded the zip file but it tells me it's not a module.

jifengSherry said:
I downloaded the zip file but it tells me it's not a module.
Click to expand...
Click to collapse
Could use more details, otherwise it is hard to help. It definitely is a module and installs fine. Something else is going on.

is this for china only? I have a Canadian 3 XL and moved to Bucharest, need to enable VOLTE on Orange Romania. I'm also on Android 11

It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?

wangdaning said:
It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?
Click to expand...
Click to collapse
I contacted Orange and they say VOLTE should be working, that the issue is my device not being compatible with their network. I also bought a Samsung watch 3 with LTE and can't activate LTE through my phone, i assume it's due to the same issue.
I'll follow your guide and report back.
Should be no issue if i am using Android 11 instead of 10 right?

Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
Click to expand...
Click to collapse
If that does not work then you need to modify the module to include the romania mbn.

wangdaning said:
Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
If that does not work then you need to modify the module to include the romania mbn.
Click to expand...
Click to collapse
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!

angeluszero said:
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!
Click to expand...
Click to collapse
ok i spoke too fast, while VOLTE is enabled now in the settings, when i make a call, it switches to H+ which means its not using VOLTE. any idea? I modified the .txt file to include the location of the romania .mbn file, i modified the file directly on the phone though, after installing the module with magisk manager

Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.

wangdaning said:
Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.
Click to expand...
Click to collapse
I did that, both VOLTE and Wifi calling say provisioned. I guess it might be something on Orange's end.
I saw a reddit post for a Pixel 3 having the same issue and the carrier ended up doing something on their side.

Confirmed working on Pixel 3 w/ Android 11!

Can this patch work on Pixel 4 as well? Thank you

duffercn said:
Can this patch work on Pixel 4 as well? Thank you
Click to expand...
Click to collapse
You would have to find the location of the files on the Pixel 4 as I am not sure where they are. Then modify the module to point to the correct location.

[2021 noob guide] Unlock and root (with working SafetyNet, Netflix & etc., Lock/Unlock in dev settings)

### Disclaimer ###
I am not responsible for damages of any kind. This will probably destroy your device without any warranty help or replacement.
If you follow this guide, your warranty will be lost forever.
Probably i described something wrong or it's not working for you.
### READ THIS ###
READ EVERYthing at least once before doing anything!
Current release of guide: 29/04/2021
Tested on:
Galaxy Tab S6 Lite (WiFi)
P610XXU2BTK2 (Nov2020, Android10, OneUI 2.5)
What's working: KG State, OEM Lock/Unlock in dev settings, SafetyNet, Netflix & etc. (NOT in HD with liboemcryptodisabler)
-> I have done this on latest the Android 10 (OneUI 2.5) because it seems the fastest OS for this tablet to me at this time of point. I don't know if this works the same way on Android 11.
Instructions
0. Make sure you have enough battery. Like 80%+
1. Create yourself an account on SamMobile https://www.sammobile.com/ and download your desired firmware for your country https://www.sammobile.com/samsung/galaxy-tab-s6-lite/firmware/SM-P610/DBT/#SM-P610
2. Extract firmware (WinRar is the fastest for that) and open the AP_[...] with WinRar or 7-Zip. Extract boot.img.lz4
3. Decode boot.img.lz4 with https://github.com/lz4/lz4/releases using lz4 boot.img.lz4 boot.img
4. Using 7-Zip add the boot.img to an tar archive and move it onto your tablet
5. Install Magisk APK from https://github.com/topjohnwu/Magisk/releases on your tablet, make sure there is no update available and press install. Choose the file patch and open the boot.tar (May need to enable show internal storage)
6. Move the patched boot.tar (named differently) onto your pc.
7. Make sure your downloaded firmware is the same as onto the device. If not flash it with https://odindownload.com/
- (Sync cloud apps and backup local data), turn off tablet, press Volume Up+Down and connect usb to pc while holding. When screen turns on the Download mode appears. Leave off the keys now and continue by pressing volume up
- Choose in Odin the following: BL: BL_[...], AP: AP_[...], dismiss CP, CSC: CSC_[...], Dismiss the Home_CSC_[...] from download
- Start and now wait until the tablet welcome screen appears. Skip it, we will reset it later again
8. Enable dev settings (tap 5 time onto build number for that), enable OEM-Unlock
9. Boot to download mode described above and unlock the Bootloader by following the instructions which show now up on the first screen in download mode (not the flash screen, before)
10. On welcome screen, skip setup because we will reset it later
11. Now we have to bypass KG State prenormal (or wait 7 days). Goto system update section, deactivate automatic download, then check for update. Your lasted checked date should be the current.
12. Then goto to general administration setting -> Date and Time -> Deactivate Auto time and timezone. Set the date manual to like 2 weeks earlier. Then check for updates again and the lasted checked date should be the current set manual.
13. Restart the device, activate auto time and timezone again and check for updates. The last checked data should be the current.
14. Boot to download mode flash screen like described earlier. The KG State should be checking (is for me), but not prenormal. If not then you have to wait 7 days for "natural" KG State reset i think but this never happened to me.
15. In Odin select in the AP section your patched tar created by Magisk from step 6, untick Auto reboot and F. Reset Time in options of Odin, then start
16. Once passed, turn off with Power + Volume Down for 7s, then after screen off unpress the keys and press Power + Volume Up immediately. This will boot recovery.
17. Wipe cache and data (factory reset) and reboot to system
18. Now you can setup the device properly. Download Magisk APK manual from https://github.com/topjohnwu/Magisk/releases, install it
19. Don't make the additional setup, cancel it. Make sure the manager has the latest version and no update is available. Then make the additional setup.
20. FOR BEAUTY ONLY (Optional): After the auto reboot, bypass KG State like above. We will now unblock the OEM-Unlock button in dev settings. For this we have to crash the tablet. Not force off, power off, ... but crash ;D Open Magisk, check for SafetyNet, Move home immediately and open PlayStore. Then open Magisk again and continue the cycle. When doing this fast, my tablet apps get unresponsive and after like 30-60s the Samsung logo appears. After the tablet is back there, my OEM unlock is always usable again. Probably there is a faster way to crash it ;D
21. Now we will fix SafetyNet and Netflix, etc.. Install https://github.com/kdrag0n/safetynet-fix Magisk module and liboemcryptodisabler from Magisk Modules. Then activate Magisk hide.
22. Now we will fix the PlayStore. Force close it, deactivate it and clean cache (I know data clean is not available)
23. Reboot your tablet. Then download PlayStore universal APK from https://www.apkmirror.com/apk/google-inc/google-play-store/#variants
24 Install the PlayStore APK. This will reactivate it. My device was certified at this point and Netflix was available on PlayStore and playing videos ;D
Note 1: Some flash process failed? Then you did very likely do something wrong. Try to make a clean flash. Fails too? Well this is bad. Probably resolvable by using another Odin version or some specific flash combination.
Note 2: I created a custom lcd calibration with Color Changer. Maybe interesting for more people ;D
The color seems for me less yellowish with white, more punchy but also less detailed. I prefer this look.
Note 3:
- Netflix is not available in HD. Stated that earlier already. It does work in HD with unlocked Bootloader but not with Magisk installed ;( Seems like the boot image is the problem here, which we cannot fix. Modded older Netflix APK's are not working either and removing Netflix system app makes the device unbootable the next boot. So if you want Netflix in HD then this is nothing for you at this time. Probably someone found a solution.
- However i did not try to use Netflix with the HiddenCore core method. I did also read in the other root guide for this device that people used MagiskHide Props. Maybe a kernel mod is required. Some research needs to be done here.
Note 4: Widevine L1 worked with unlocked bootloader and even stayed with root. However Netflix playback did not work after root... There exists a LuckyPatch for a version of Netflix newer than the one already installed in the firmware... I did not try but maybe this patch could also solve the problem
Hope my instructions are clearer then the bull**** flying around this forum for this device ;D;D

Hello , i have the s6 lite wifi with magisk on it... My problem is when I install a update every times I need to do a factory reset and start over again when I want to install the root ( the boot.img patched in Odin. ) For updating I download my complete firmware and install it with Odin... I have trying to patch the AP file from the firmware in magisk but never work when you want to install it, magisk do something wrong with this device I know this method work with the S21 and you can keep the data.. So who you can keep the data when you update the device with magisk??

I want to ask if colour changer drains battery or not bcz i use it too and i dont found any article on net about it pls tell if it drains battery or not (i am using custom with all colours on full) screen colours look like amoled

Max128 said:
Hello , i have the s6 lite wifi with magisk on it... My problem is when I install a update every times I need to do a factory reset and start over again when I want to install the root ( the boot.img patched in Odin. ) For updating I download my complete firmware and install it with Odin... I have trying to patch the AP file from the firmware in magisk but never work when you want to install it, magisk do something wrong with this device I know this method work with the S21 and you can keep the data.. So who you can keep the data when you update the device with magisk??
Click to expand...
Click to collapse
I've not tried that... but when using Odin there is a HOME_CSC and HOME image... The HOME_CSC does not reset the tablet. Also it is probably not necessary to wipe the tablet after the boot.img flash. On my phone this was not necessary but with this tablet users reported that otherwise it would boot loop. So i would try to update with Odin like that and reboot directly to download again, flash the updated boot.img and reboot.

Uniqueshiva said:
I want to ask if colour changer drains battery or not bcz i use it too and i dont found any article on net about it pls tell if it drains battery or not (i am using custom with all colours on full) screen colours look like amoled
Click to expand...
Click to collapse
Here is a quote from Color Changer: "This is NOT an overlay: it completely remaps your colors in all apps". I did not try for long because i needed Netflix in HD but i does not seem so. Tell us if you experience something like that if you try...

"1. Create yourself an account on SamMobile https://www.sammobile.com/ and download your desired firmware for your country https://www.sammobile.com/samsung/galaxy-tab-s6-lite/firmware/SM-P610/DBT/#SM-P610"
I can't. I have an Account and I can log in to that account. But when downloading the site tells me to "join". (Not Login or sth.) If I login and then click on "Edit Account", then it tells me to login first. If I login on that new site, then it tells me that my password (which I just succesfully used to login) is false. If I click reset password, then it tells me
"Invalid Redirect URL (https://www.google.com/)" If I try to "join" with new account, then it tells me that nickname and email are alreday taken.
If I register a new account with new nickname and new email, then I can't proceed either, the site will still tell me to join and if I click join, then it tells me that "Our records show that you have already registered under the name of andy02q. If you have lost your password, click here. If you would like to modify your profile, click here." I didn't even input "andy02q", it's just the account which I just created and confirmed.

andy01q said:
"1. Create yourself an account on SamMobile https://www.sammobile.com/ and download your desired firmware for your country https://www.sammobile.com/samsung/galaxy-tab-s6-lite/firmware/SM-P610/DBT/#SM-P610"
I can't. I have an Account and I can log in to that account. But when downloading the site tells me to "join". (Not Login or sth.) If I login and then click on "Edit Account", then it tells me to login first. If I login on that new site, then it tells me that my password (which I just succesfully used to login) is false. If I click reset password, then it tells me
"Invalid Redirect URL (https://www.google.com/)" If I try to "join" with new account, then it tells me that nickname and email are alreday taken.
If I register a new account with new nickname and new email, then I can't proceed either, the site will still tell me to join and if I click join, then it tells me that "Our records show that you have already registered under the name of andy02q. If you have lost your password, click here. If you would like to modify your profile, click here." I didn't even input "andy02q", it's just the account which I just created and confirmed.
Click to expand...
Click to collapse
You need to go to sammobile.com/login instead of just sammobile.com

I did go to sammobile.com/login. That's how I could login, how else? Although... now after trying the same thing again the login does carry over to https://www.sammobile.com/samsung/galaxy-tab-s6-lite/firmware/SM-P610/DBT/#SM-P610 and I can download the firmware from there, so thank you for the help. I guess Strg+F5 and closing and reopening the tab wasn't enough and I had to delete cookies or sth

Samsung Galaxy M21 2021 Edition (SM-M215G/DS)

I own some old samsung Galaxy models like J7 Prime and had tried good Custom ROMs on them but up recent I purchased this Samsung Galaxy M21 2021 Edition (SM-M215G/DS) a few days ago thinking that it's going to be same as Galaxy M21 2019 (SM-M215F) model, to my horor its bootloader & recovery seems to work differently from J7 prime (with bar codes in download mode) . So it's a differrent model. The bootloader unlock process on this Galaxy M21 2021 Edition is same as mentioned in Galaxy M21 2019 thread ( https://forum.xda-developers.com/t/rom-full-oneui-10-totsukaos-q-for-galaxy-m21.4219975/ ) but none of the unofficial TWRP recoveries work nor does Magisk boot.img patch method work for rooting this model. Samsung does not support Fastboot as I understand & everything ends with Error : Signature verification failed. The only option left to me is sell off this phone but its so new.
If any developer can help me with some Custom Recovery that could install itself for rooting and perhaps custom ROM (I know I'm asking for too much ) for this device (SM-M215/DS), I will gladly donate $20.00/month for a year (Pls consider the bad times of pandemic we all are in). As right now I've put up this device (SM-M215G/DS) for sale. I've attached a few screenshots of the device maybe it could help any Dev who's interested (Hopefully ).

To root Android a Custom Recovery isn't required at all.

jwoegerbauer said:
To root Android a Custom Recovery isn't required at all.
Click to expand...
Click to collapse
jwoegerbauer said:
Firstly, I THANK YOU for replying to my desperate post. I'm delighted that Dev (jwoegerbauer) wanted to help.
Coming to the topic, Yes I was aware that rooting didnt require Custom Recovery.
1> I had tried to install Magisk_V23.zip via command [adb sideload magisk.zip] but the
response I had got was [Error: Signature verification failed, Error: Aborted.] on this device
(SM-M215G/DS).
2> When I flashed couple of TWRPs (one official for Galaxy M20 from www.twrp.me & few
unofficial TWRP builds from the net) via latest ODINv14.3 , ODIN displayed PASS! and
rebooted as I had kept Auto Reboot & F.Reset Time ON. But Native Android revovery came
on with Custom Binary Error. Again, I did the same with F.Reset Time & Auto Reboot OFF this
time and when I manually rebooted to recovery (Vol UP + Power) it was back to native
android recovery. I had to factrory reset to get the samsung logo then booted into welcome
screen.
3> I have checked the link ( https://forum.xda-developers.com/t/...al-adb-fastboot-
drivers.4185535/post-83851013 ) you provided. Awesome work! My questions are will it
enable FASTBOOT on SAMSUNG? Because when I select Reboot to Bootloader option in Anroid Recovery the phone does go into Fastboot Mode but apparently Fastboot seems
disabled by Samsung because from the PC it does not recognise the Fastboot Devices. So,
as a noob if I've understood whats mentioned in the link you provided is that Samsung didnt
provide the Native Samsung Fastboot Drivers for the Galaxy M21 2021 DELIBERATELY? So,
the link you provided will help me install the required Fastboot Drivers? & then I can flash
TWRP.img or Magisk.img?
Thanks in advance
Click to expand...
Click to collapse

jwoegerbauer said:
To root Android a Custom Recovery isn't required at all.
Click to expand...
Click to collapse
Followup 1:
Hi, I tried your ADB-FASTBOOT-Installer but it doesnt seem to go beyond "Waiting for devices" screen.
1> I tried installing magisk v.19.3.zip (renamed to just "OTA") using command (adb sideload OTA)
first error i got was (adb: failed to read command: No error)
2> second time i tried installing from another folder belonging to 15-seconds-adb and it showed [ (0.01x) success ] something like that
3> I installed magisk manager 2021.4.9 Magisk v22.1 by Package Installer method not sideload method. When i rebooted & checked magisk manager it wasnt rooted so I tried boot.img patch method and got error: unable to unpack boot.img
I have attched some screenshots of the errors but what I understand from this is that the new Samsung devices might have img files written in some new format i guess because why else would magisk manager fail to unpack and patch a boot.img file, ususally it does fine.
I have also attached a copy of the device stock boot image file (hope i'm not breaking some xda rules here about posting img files , i just joined yesterday so )
Maybe its of some help to some Dev who might need these to find a workable solution.
The stock firmware I downloaded is flashing well on the device (SM-M215G/DS), the link is here- https://samfrew.com/download/Galaxy__M21__2021__Edition__/lOg2/INS/M215GDDU1AUG2/M215GODM1AUF3/

Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .

jwoegerbauer said:
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
Click to expand...
Click to collapse
Well what necessarily needed for rooting an android phone is just modifying some files in /system? I have seen the phrase 'toybox 0.8.5' a multiple times in your posts, not sure what is that.

LR7875 said:
Well what necessarily needed for rooting an android phone is just modifying some files in /system? I have seen the phrase 'toybox 0.8.5' a multiple times in your posts, not sure what is that.
Click to expand...
Click to collapse
Toybox is a replacement for many Linux command-line utilities that is targeted at embedded systems - similar to BusyBox. It was created by Rob Landley, who is also a former BusyBox maintainer. Toybox is merged into any Android starting with version 6.

jwoegerbauer said:
Toybox is a replacement for many Linux command-line utilities that is targeted at embedded systems - similar to BusyBox. It was created by Rob Landley, who is also a former BusyBox maintainer. Toybox is merged into any Android starting with version 6.
Click to expand...
Click to collapse
Oh learned something more.
Well what is the definition of root then?

LR7875 said:
Oh learned something more.
Well what is the definition of root then?
Click to expand...
Click to collapse
Sorry to barge in LR7875, to my knowledge (I have rooted & installed Roms on some older Samsung/Redmi/Laptops etc.) rooting is the process through which we gain Admin Rights / Super User on Linux devices. Correct me if I'm wrong. Im not a programmer by any means so.

jwoegerbauer said:
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
Click to expand...
Click to collapse
Hi there jwoegerbauer, thanks for responding. If im not being bothersome , I'll need to stalk you on XDA for some help on this issue of rooting this device, if it s okay with you . Pray tell me what else other than magisk could root this stubborn Samsung model ? Im getting some good offers for this device on the local online market but i really didnt want to sell it off just wanted to root & install roms like before.. Other than magisk I just know of SuperSU by chainfire which I think stopped working well post android 8 oreo but will it work for Android 11? No way any changes to /system/Priv-app and the phones factory reset themselves. One-Click Root only takes calls & they charge $50 for rooting, but whats the guarantee if we pay up that theyll root it properly & taht too it would be just root not Recovery or ROMs. I'm lost.

Installing Magisk DOESN'T ROOT Android. Installing SuperSU DOESN'T ROOT Android. POV.
To have said it:
Magisk is successor to XPosed, means a software framework what once get added to Android allows you to systemless apply modules, means some functionalities modders are missing on standard Android. The crux with Magisk is it patches device's bootloader.
SuperSU simply is a per-app root-access management tool, nothing else: it requires Android got rooted.

OldNoobOne said:
...
The stock firmware I downloaded is flashing well on the device (SM-M215G/DS), the link is here- https://samfrew.com/download/Galaxy__M21__2021__Edition__/lOg2/INS/M215GDDU1AUG2/M215GODM1AUF3/
Click to expand...
Click to collapse
How are you "flashing"?
Why do you say it "is flashing well"?
As far as I know, you need to use Odin (on a PC) to "flash" a Samsung device. Samsung does not support fastboot -- no amount of updating drivers on your PC will make a Samsung device start supporting fastboot.
Magisk is much more than just a way to root, but a side effect of installing Magisk is that you will be rooted.
If you have installed the Magisk Manager app and tried to patch the AP.tar of the stock firmware, and you are getting an error, you should look through the main Magisk thread, and maybe ask there.

J.Michael said:
Magisk is much more than just a way to root, but a side effect of installing Magisk is that you will be rooted.
Click to expand...
Click to collapse
IMO you're WRONG: Magisk DOESN'T ROOT Android, but you additionally can install MagiskSU app what grants elevated rights ( AKA SU ) to Magisk.

jwoegerbauer said:
Magisk is successor to XPosed, means a software framework what once get added to Android allows you to systemless apply modules, means some functionalities modders are missing on standard Android. The crux with Magisk is it patches device's bootloader.
Click to expand...
Click to collapse
I need to hop on and correct a few details here...
Magisk is not a successor to Xposed. That's like comparing apples and oranges. If you want to know how Magisk came to be John has written about that in a couple of places, here for example:
Spoiler
https://www.reddit.com/r/Android/comments/7oem7o
And Magisk does not patch the bootloader, but the ramdisk which can be found in either the boot or recovery image depending on your device. Details about that here:
https://topjohnwu.github.io/Magisk/boot.html

OldNoobOne said:
Sorry to barge in LR7875, to my knowledge (I have rooted & installed Roms on some older Samsung/Redmi/Laptops etc.) rooting is the process through which we gain Admin Rights / Super User on Linux devices. Correct me if I'm wrong. Im not a programmer by any means so.
Click to expand...
Click to collapse
Oh I see, it is used to do something that are restricted originally, e.g. access system files, delete system apps, etc.

Didgeridoohan said:
I need to hop on and correct a few details here...
And Magisk does not patch the bootloader, but the ramdisk which can be found in either the boot or recovery image depending on your device.
Click to expand...
Click to collapse
Correct: it should also have been called boot.img instead of bootloader. Sorry for this.

LR7875 said:
Oh I see, it is used to do something that are restricted originally, e.g. access system files, delete system apps, etc.
Click to expand...
Click to collapse
True . Don't quote me, (In a nut shell ) up from Andoid 9 (Pie) modification to /system /app etc. is difficult per my knowledge, thats why probably magisk sits in the boot partition, no one dare touches the system partition anymore while the gadget is ON. Only Gugle stays in the system partition im sure. The Custom Recoveries do wipe the device but are unable to erase the core andoid OS inside . Even 'Fastboot Erase' command cant get andoid out completely (exception Linux-phones i think). So practically Andoid devices are just gadgets that are 'leased' to the so-called 'owner' of the device (without explicitly mentioning the term 'leased' by gugle). The cost of the smart-gadget is practically the 'Down Payment' we pay to Gugle & OEMs then the rest of the revenue they make from Ads etc. which goes as 'Rent/lease payment' to them ultimaately & we never get to own the devices we purchase EVER! .
My sixth-sense says The chinese OEMs allowing Fastboot Mode only for now but only to make inroads into the smart-gadget market, once they have made everyones profile Gugle & pentgon might just make the softwares on these smart-gadgets wholly tamper-proof & focus more on 'managing' or keeping an eye on their 'subjects' [given that the whole gugle business,- 'search-engine', 'smart-device' etc. started officially in 2004 which was POST the 9.11 ATTACK].
So they're probably maintaining the Big-Data on everyone who uses their devices & 2014 is when data-warehousing became the need if i remember correctly; so, it was all about compressing the Big-data gathered & then Analytecs took the spotlight by 2016-17 coz they needed to analyize all the data collected & remove the junk from it then home in on pentgons targets. It's Obvious . No wonder they're pushing PX-Xperience ROMs through the ROM channels to cover the gap created by chinese OEMs eating into their market share. Why else do they charge other OEMs $2 for OTG-support while Shamshung (and now MYUI) already had native OTG-support on their devices shipped? so that's what Sekure-folder all about, YOUR DATA LOADED & LOCKED real-time then SHIPPED back to Gugle-Analytecs. Obvious.

Well so root is basically... Removing those ads and trackware up to the bare bones of the phone, to ensure all your data isn't used to make the spammy advertisements?

Android is nothing else then a derivated Linux. In the world of Linux the Root User is the user that has all rights esp. accessing / modifying system files, it's comparable to the Administrator in the world of Windows.
In the world of Linux this Root User typically is called superuser ( commonly abbreviated: SU ). In the world of Android such a superuser isn't in general implemented by default: it must get added to Android by modding it, means adding a SU ( read: Switch User ) binary - in whatever form - to Android what is systemwide accessible. In the world of Android an user root exists what is the user with user ID 0.

[ deleted ]