Database Info

[Q] Looking for root basics, list etc.

As the title states, I need help with understanding the basic steps on rooting the ASUS TF300.
I am not a programmer, I do not know the lingo or terms, and searching on the site has yielded very confusing results.
Basic steps?
1. Unlock boot loader - Why? What does this do?
2. TWRP? I have no clue, but I see references all over the place
3. Custom Recovery - What does this do? Do I need it?
4. Kernel - What is this?
5. ROM - What is this?
6. Install Super SU or SuperUser (what's the difference?, what does this do?
7. Install a root check app (to check if rooted I presume)
8. Install some form of file explorer (I have Fx File Explorer) and backup/control app (I have Titanium backup)- both paid forms
9. De-bloat with caution!
Where does the OEM firmware/software fit in this scheme? Does it exist as a backup or is it over-written? Do I have a choice?
As you can guess I'm lost. Reading threads after searching for "root TF300" or even the guides or the very good index, I have more questions than answers. How does one know what to do if the acronyms used are cryptic? (example TWRP~ what does this even stand for?)
I believe that not all steps are required, but I also believe the order I do things is important, and I'm concerned about bricking my TF300 by doing something wrong. I also don't want to assume that this is the same for every device or phones. (what steps work for a phone may not be the best for a tablet)
All I want to do is root and remove bloat. After I get this, I may consider upgrading the OS (kernel? Rom?) to something better.
Any links would be greatly appreciated. Please just bear in mind I'm so noob to this I don't know a ROM from a Kernel yet. (When I search, all answers are overly complicated developer definitions.)
Thank you!

Here is a "simple Step by Step" with notes in red as to how my mind tries to grasp this:
1. Upgrade your tablet to the desired firmware: 4.1 or 4.2 I assume they mean any OTA upgrade~ my tablet is current with JB 4.2.1 and I do not believe ASUS will plan on upgrading this anytime soon)
2. Be sure the correct drivers for your tablet are installed!! Installed where? on my PC? How do I know what are the correct drivers? Where can I get them?
3. Download the updated rooting toolkit: Updated Motochopper rooting toolkit -OK, I can do this!
4. Download TWRP for your firmware version:
- 4.1: TWRP 2.5.0.0 for Jellyeban 4.1
- 4.2: TWRP 2.5.0.0 for Jellybean 4.2 -This makes sense to me, as I am jellybean 4.2.1
5. Rename the downloaded TWRP blob file to twrp.blob and copy it to the root of your sdcard -what is a blob file? Is there a size requirement for the SD card? Does the SD have to be blank?
5. Extract the rooting toolkit to a place you like. -I assume the above mentioned motochopper? Does this answer my question above about the SD card?
== Part 2 - Rooting ==
1. Open up the folder where you placed the rooting toolkit. - with what program? A simple file explorer I assume?
2. Open the run file and follow the instructions -I hope there aren't any cryptic/over my head choices to make!
After installation the tablet should reboot and you should be rooted. -Does this install all the SuperSu stuff or is this it? What about customer recovery? Can I go back? what are the limitations of doing it this way assuming it works....
And this is just PART of the process!

I'll answer in logical order:
broderp said:
5. ROM - What is this?
Click to expand...
Click to collapse
That's the Operating System that's running on your tablet, i.e. what is called Lollipop or KitKat, or even further what makes the difference between Android and iOS.
Your ROM may come with some preinstalled apps, but with some ROMs they are separate (i.e. the Google apps).
broderp said:
1. Unlock boot loader - Why? What does this do?
2. TWRP? I have no clue, but I see references all over the place
3. Custom Recovery - What does this do? Do I need it?
Click to expand...
Click to collapse
On your ASUS tablet you can, by default, only install ASUS supplied ROMs (i.e. updates).
In order to install a new ROM you need to unlock your device. You do that by unlocking the boot loader. Once you have unlocked the boot loader, you can install a custom recovery, such as TWRP (there are many custom recoveries, but for your device TWRP is recommended).
Once you have a custom recovery, installing a new ROM, or rooting your device, becomes a lot easier. No need to type in commands, but you can now use touch.
broderp said:
4. Kernel - What is this?
Click to expand...
Click to collapse
Your kernel is the most important part of your ROM. It's the software between apps and your actual hardware, the lowest level actually. The kernel determines if you can talk to certain pieces of hardware or not. If the kernel does not support certain hardware, that's it, you can't use it.
When your tablet boots up, the first thing it loads its the kernel, the kernel loads all other programs. Another responsibility of the kernel is to allow you to run multiple programs at once.
broderp said:
6. Install Super SU or SuperUser (what's the difference?, what does this do?
Click to expand...
Click to collapse
They allow you to execute programs with root privileges (i.e. no limit to privileges, can do anything), but also give you some protection so malicious programs cannot become root: you have to give explicit permissions for every app.
broderp said:
7. Install a root check app (to check if rooted I presume)
Click to expand...
Click to collapse
Yes.
broderp said:
8. Install some form of file explorer (I have Fx File Explorer) and backup/control app (I have Titanium backup)- both paid forms
Click to expand...
Click to collapse
Optional, pick whatever you like.
broderp said:
9. De-bloat with caution!
Click to expand...
Click to collapse
No clue!
broderp said:
Where does the OEM firmware/software fit in this scheme? Does it exist as a backup or is it over-written? Do I have a choice?
Click to expand...
Click to collapse
Firmware often is part of the hardware: it gets written to special memory, and "sticks", i.e. when you reboot it stays there. If you get a T300 you should let ASUS run all the updates as it installs new firmware. Some firmware gets written when your device boots, meaning the special program, the kernel, starts, and at some point writes updated firmware to hardware.
So firmware is software that makes hardware a bit more flexible: else everything is hard-wired, if there's a problem you can't fix it, but with software you sometimes can fix a hardware issue.
Hope this helps!

First, to unlock the bootloader, you need to go the asus site and register your tablet. Then you can download the unlock app from the asus site as well. Next, move the unlock app from where ever it downloaded on your pc to your tablet. You can put it on the tablet RAM or on an SD card, it doesn't matter. On your tablet, go into the settings menu. under security(I think it is there) and enable 'unknown sources' for app installation. I haven't had the stock ROM for so long, I can't recall where that option is. Run the unlock app. It may take a couple times to unlock the tablet. WARNING! this will void your warrenty! So if your tablet is relatively new, think hard about this. Once your tablet is unlocked, then you can worry about TWRP and ROMS
TWRP is a custom recovery. It is officially Team Win Recovery Project, hence TWRP. It is a program that will allow you to back up your tablet before you make changes(very important in case you screw something up) and a host of other things including flashing custom ROMs. If you go into the LP 5.1 for the TF300 thread in the development area, it will have all the links for stuff like the current TWRP, Gapps packages and the newest LP ROM. It is great for our tablets and really wakes it up. Oh yeah, the TWRP site will have instructions for flashing TWRP on your newly unlocked tablet as well.
All this seems very intimidating for noobs, I was one about 4 months ago. I now feel sort of not-noobish. To install TWRP you will need either Fastboot or ADB on your computer. Google Fastboot or ADB and you should find plenty of answers. There are also 'lite' versions of Fastboot out there too. If you are on Windows 8 or 8.1 you will need one of those. Windows doesn't like fastboot or ADB for some reason
HTH

Kyocera DuraForce Super Thread

Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
There is a Lollipop update available for the device as of early February, 2016. I have found a way for users to update if the OTA fails (see below). I've also updated the below posts with information regarding the Lollipop update and moved the KitKat notes to another location (link for old notes is below)

Ota - lmy47v1218_2217
For those who are having trouble applying a FOTA on the DuraForce, check /cache/fota/xyz_fotalog_123.dat It's a text file that contains a lot of really good info on what is going on during a FOTA. Including errors. Keep a look out for signature mismatch errors.
I had errors with the following files. Took me a few tries to get the OTA applied as each attempt resulted in one error.
Uninstall Xposed (moar hacks)
/system/usr/keylayout/gpio-keys.kl (disable PTT/Speaker buttons)
/system/etc/permissions/platform.xml (sd card "fix")
If trying to address the issues manually does not work, follow the procedure below.
Download "vanilla" system image from HERE (link)
Extract zip file
Ensure at least 2Gb of storage is available for internal data
adb push mmcblk0p21_KVT49L_0617_0132 /storage/sdcard0/
adb shell
su
dd if=/storage/sdcard0/mmcblk0p21_KVT49L_0617_0132 of=/dev/block/mmcblk0p21
Reboot phone once it completes. It will take awhile and not report anything during the process.
After phone boots, run "adb reboot recovery"
Wipe data / factory reset
Wipe cache
Reboot
Run software update

General Notes - Lolipop
Force Reboot: Pwr + Vol Up + Vol Dn + Back + Home + App Switcher buttons for ~10-30 seconds
Root: Use KingRoot from http://king-root.net/ -- I used the android APK successfully
SD cards bigger than 32Gb still do not work correctly on stock firmware

Known Working Customizations
To be determined

KitKat Notes
All previous notes for KitKat have been moved to a document in box. The notes can be found HERE (link)

Sources / Mirror(s)
The OSS drop is available on Kyocera's developer site: http://www.kyoceramobile.com/support/developers/
Misc file mirror: https://nuskunetworks.box.com/s/p5hwq3hboctl0saze0wkcv3jzfefuw45

Do you trust Kingo?
I'm THRILLED to hear you were able to root and freeze all the AT&T crapware. I can't wait to do the same. But how do you feel about Kingo? I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
kemonine96 said:
Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
If you're looking for root, look no further than Kingo. I can confirm the Windows version of Kingo is working on the AT&T varient of the DuraForce.
Click to expand...
Click to collapse

tomzweifel said:
How do you feel about Kingo?
Click to expand...
Click to collapse
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
tomzweifel said:
I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
Click to expand...
Click to collapse
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants

Components to clean up?
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
kemonine96 said:
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Click to expand...
Click to collapse

tomzweifel said:
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
Click to expand...
Click to collapse
Unfortunately I don't have notes on what Kingo leaves around on /system... Some searching online or poking about /system should yield results.

New OTA Update
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.

tomzweifel said:
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
Click to expand...
Click to collapse
Please do. I haven't gotten any notifications yet and I'm kinda curious what the OTA will contain.

http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates

Dkesler76 said:
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Click to expand...
Click to collapse
Thanks for the heads up. Too bad it's not L.

kemonine96 said:
Thanks for the heads up. Too bad it's not L.
Click to expand...
Click to collapse
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan

Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to free up some time this weekend and I'm going to be pulling the OTA and seeing what I can do for re-packing it for those of us who are rooted and/or de-bloated.
Will post back with more info after I've had some time to poke at the OTA some.
Edit 1: Looks like this has patches for system and boot. /cache/delata looks like the directory where everything was downloaded. Hopefully binwalk and some other tools will yield useful information on what's contained within.
Edit 2: Looks like I was able to install the OTA despite being rooted. I'm waiting for 1st boot to verify root persisted and I'm also working on mirroring a number of partitions that can be used to "go back" to stock as well as images for updated partitions post-OTA.

Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device

Good news everybody! The ATT OTA doesn't remove root and can be installed as-is provided you've not de-bloated the ROM or installed Xposed. If you've de-bloated (see below) you'll need to restore the missing bloatware and if you've installed Xposed, you'll need to uninstall it prior to applying the OTA.
In one of the early OP's there's a link to the "misc file mirror" that contains partition images for boot and system partitions. These are from an ATT device and can be used to restore back to a state that'll allow the OTA to apply.
Happy hacking and OTAing everyone.

kemonine96 said:
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Click to expand...
Click to collapse
weird i tried dd and busy box and no go not showing up on device

Dkesler76 said:
weird i tried dd and busy box and no go not showing up on device
Click to expand...
Click to collapse
What isn't showing up?

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.

samsung galaxy s9 root android 10 exynos

Hello, is there a way to root the phone where everything works now (Bluetooth, Face ID, etc.)?

I would very much like to see this answered. I've seen some application-specific instructions such as this reddit thread for enabling Samsung Health, and I've read about hiding the fact that the phone is rooted from apps by using MagiskHide, but it's not clear whether this works for all apps and features or just some. There's also this recently updated guide to rooting that claims:
Magisk is a highly advanced way of rooting android systemless-ly. This means that Magisk root android without changing or modifying the system partition. Hence you can receive OTA updates, run apps that require to pass Google’s SafetyNet tests.
Click to expand...
Click to collapse
However, many hacks that sound good when you read about them in advance run into snags and gotchas once you actually get into implementing them, and I'm hesitant to just give it a try and see how it works out when tripping Knox is irreversible and if things stop working you can't get them back by flashing the stock ROM.
I'd be grateful if anyone who has actual experience on this subject could vouch for being able to re-enable all lost functionality after rooting or to not lose it in the first place, or whether even some lost functionality can be enabled (and if so, what have you been able to get working and what haven't you? I don't know about OP, but to me the most important ones are Secure Folder and Samsung Health).
Also, does anyone have experience with retaining Knox-sensitive functionality on rooted S9 Exynos with Android 11 (either rooting after upgrading to 11, or rooting first and retaining root when upgrading)?

@bis225
IMO noone needs Magisk to root a device's Android. Rooting Android means having the SU-binary present on Android - a ~100KB file - nothing else. Copying SU-binary onto Android allows you to temporariy give you root access when needed.

jwoegerbauer said:
@bis225
IMO noone needs Magisk to root a device's Android. Rooting Android means having the SU-binary present on Android - a ~100KB file - nothing else. Copying SU-binary onto Android allows you to temporariy give you root access when needed.
Click to expand...
Click to collapse
I'm not sure I understand what you're saying. Are you telling me that you can simply copy the file onto an unrooted phone, and voila, you can gain root access?? Can you point to information about what to do and how this works? It runs contrary to everything I've ever read on the subject.
To the best of my understanding, in order to install su binary unto an unrooted phone you need to install a custom recovery, and use that to flash the su binary onto the phone. I thought the idea of Magisk was to provide root access without modifying system files so that SafetyNet can't detect that the system has been modified. Unless I'm missing something there's no disadvantage to rooting with Magisk, only advantages, but regardless, I don't see how it makes a difference with respect to this topic. Installing a custom recovery is what trips Knox and prevents some features and apps from working, so it doesn't really matter what root method you use if you have to use a custom recovery to install it.
If you know of a way to root a Galaxy S9 without using a custom recovery or tripping Knox and that can't be detected by SafetyNet, please elaborate.

Rooting Android simply means to add a ( hidden ) user called root ( AKA super-user ) who has ALL rights to Android's file system.
For example from within ADB you activate this user and let run him any command what requires to have ALL rights - assumed the SU-binary is located in /sdcard
Code:
adb shell "/sdcard/su -c '<command-here>'"
AFAIK Magisk installs the SU-binary in /data/adb/magisk/busybox, but I may err.

@jwoegerbauer
But I didn't ask what rooting means. Unfortunately, this doesn't answer any of my questions.

I think I clearly expressed that neither a Custom Revovery nor Magisk itself is needed to have root, that simply copying SU-binary to Android's user-space is enough.
If you want to root via Magisk then do it.
Personally never would do it this way.

jwoegerbauer said:
I think I clearly expressed that neither a Custom Revovery nor Magisk itself is needed to have root, that simply copying SU-binary to Android's user-space is enough.
If you want to root via Magisk then do it.
Personally never would do it this way.
Click to expand...
Click to collapse
This really seems contrary to everything I've read, and this Stack Exchange thread specifically explains why that wouldn't work, but if you say you have experience with this and it works for you, I'm certainly willing to give it a try and see how far it gets me. Do you know where a copy of the su binary can be obtained? All my searches for su binary lead to the supersu APK and instructions for installing it by flashing, or something along those lines. I can't find an su executable that can just be copied to internal storage as-is anywhere.

How To Guide Root GALAXY A53 5G - Android12 OneUI4.1

Hello, This is a work in progress guide to help you with rooting your phone for whatever reason (i root it to use the Automate app as i am lazy)
I hope this is not a total mess, i will edit this if you have too much trouble reading
DISCLAIMER /!\
• Please consider that you follow this guide at your own risks, i am a random person in the internet, if you do not trust any part of this guide, dont follow it!
• I am adressing this guide to experimented users, i have probably missed a lot of steps and i will try to correct myself, (or not, it takes time sry)
• i am from Europe; not a native english speaker + a noob in the field. feel free to criticize, but be elaborate to help others
I did this on the GALAXY A53 5G phone with :
• Build ver. SP1A.210812.016.A536BXXU1AVCC
• One UI 4.1
• Android Version 12
The following is needed in order to speedrun this :
+MAGISK25.1
+LZ4
+ODIN3.14
+YOUR BOOT.IMG (FROM THE AP_ FILE OF THE FIRMWARE)
1) On your phone go to Settings -> About phone
2) Then -> Software info
3) Check at (the 6th line) ; BUILD Versionfor me it was:
SP1A.210812.016.A536BXXU1AVCC
4) You will have to download yours at sammobile or any other website you trust more : (needs an account but then is free to download)
Download Samsung Galaxy A53 5G SM-A536B firmware
Download the latest Samsung firmware for Galaxy A53 5G with model code SM-A536B. Check out our free download or super fast premium options.
www.sammobile.com
Then when you have you files , the one that matters is the one starting with AP_
5) extract the boot.img.lz4
6) download one of the versions of LZ4 from : https://github.com/lz4/lz4/releases
7) extract all files into a folder
8) drag and drop the extracted file from part 5) INTO the .exe file from part 7)
YOU HAVE YOUR BOOT.IMG
9) Now drag and drop this Boot.img INTO your phone
The version 25.1 of Magisk (or above is needed ? as i used that version of magisk to root my phone i guess)
10) Install it on your A53 you can download it from :
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
11) inside the app, click on INSTALL (written in blue on top right)
12) select the only option
13) go to the boot.img (that you dropped into your phone at part 9)
14) wait
15) when it is done, plug your phone again if you unplugged it and drop the new file generated by MAGISK into your computer and rename it boot.img.tar
Unlock the bootloader of your phone by either ;
• Watch a tutorial it helped me understand why i kept having an error while doing the next steps (i "unlocked" OEM only within dev options, that wasn't enough)
and skip to 22)
• Or follow these steps
on your A53 go developper mode by clicking 7-10 times on the VERSION in settings -> about phone -> Software
turn on the switch for OEM unlocking (wifi must be connected if the button doesnt appear)
and i am not sure if we need to but , turn on the switch for USB DEBUGGING as well (for adb)
16) stay pressed on both VOL UP + VOL DOWN
17) plug your phone to computer
18) wait
19) long press VOL UP
20) wait
21) press VOL UP
ez
So now get ODIN 3.14 on ur computer
I got the official website but cant remember where from, i will look into it, maybe you can find it on google but be carefull of malicious ones i swear !
(if you are kind enough you will share it below ♥)
22)after launching ODIN
23)The on the AP button put your boot.img.tar file that you got from part 15)
24) on your A53 go developper mode by clicking 7-10 times on the VERSION in settings -> about phone -> Software
25) check that you wave wifi connected
26) go to dev options and check if OEM unlock is grey'd out
30) turn OFF your A53 phone
wait for it to BZZZZZZZZ (viber)
31)STAY PRESSED onto the 2 buttons VOL UP + POWER
on recovery choose the 2nd option with your volume keys, "reboot to bootloader"
then if odin recognise the phone press start

This looks like a great guide. Too bad OEM Unlocking doesn't appear on US carrier phones, or else I'd totally do this :/

sorry if i sound stupid but how do i get the boot.img.lz4 file?

This does NOT work on VD7 or most likely later with Magisk 25.1/25.2 (the BL is unlocked on this SM-A536B as I get the warning on reboot and the OEM unlocked is on and greyed out in developer options).

I used the patch the entire AP file method in Magisk and flashing the patched AP file (you can google T505N XDA root Samsung; I will find the forum link later and remember to post it here (this method works on VD7 and probably higher)

I am now rooted with TWRP, thanks to this site, https://www.droidwin.com/install-twrp-recovery-and-root-samsung-galaxy-a53-5g/
Still cannot delete system/app, system/priv-app (not even in twrp) but am able to access data/app (and remove .digest and .dm files)

crazyut said:
I used the patch the entire AP file method in Magisk and flashing the patched AP file (you can google T505N XDA root Samsung; I will find the forum link later and remember to post it here (this method works on VD7 and probably higher)
Click to expand...
Click to collapse
Confirmed, works with VG1 and latest VGA. I used patched AP along with BL, CP and (Home) CSC. Please note that you have to do a factory reset after this, so remember to backup your data properly.

Hlo I rooted my a53 5g thanks to you but cannot remount system partition as read write
I get this output after running
Code:
mount -o remount,rw / <
'/dev/block/dm-0' is read-only
Please help me with it
And also cannot disable dm-verity flashed disable-dm-verity.zip but after formatting data device stuck in bootloop...

Hello. I am new to programming. I have a rudimentary knowledge of android, i.e. whatever I figured out while jailbreaking JP5 and JP6 Securus tablets, and I await academic coursework for formal education in computer hardware and software engineering.
Clarity and redundancy is greatly APPRECIATED regarding any replies to my post.
The question(s) are, what benefits would I obtain from rooting my A53, what about the Cons? I Can I improve the performance of my phone, processing data, etc.
Afterwards in the future, can I still flash the Android 13 firmware? Does Samsung find out?
I know I have to read up, I am being lazy.
THANK YOU.

JoseAndDiezel104 said:
Hello. I am new to programming. I have a rudimentary knowledge of android, i.e. whatever I figured out while jailbreaking JP5 and JP6 Securus tablets, and I await academic coursework for formal education in computer hardware and software engineering.
Clarity and redundancy is greatly APPRECIATED regarding any replies to my post.
The question(s) are, what benefits would I obtain from rooting my A53, what about the Cons? I Can I improve the performance of my phone, processing data, etc.
Afterwards in the future, can I still flash the Android 13 firmware? Does Samsung find out?
I know I have to read up, I am being lazy.
THANK YOU.
Click to expand...
Click to collapse
While I don't have a Galaxy A53, I can speak from experience that almost all Samsung phones suffer from the same pros and cons to rooting
Let's start with the pros:
Using a system-wide adblocker like Adaway is much more battery friendly and more effective using it on root mode than any non-root alternative. This one is the main reason a lot of people root and I think it merits it, it's a really amazing ad blocker.
You'd be able to activate some features that Samsung likes to disable on A-series, like full edge lighting and the camera privacy toggle (I don't know if it's disabled on A53 by default but I'm leaning towards yes)
You get to experiment with GSI and maybe some custom ROMs in the future
You can install some neat Magisk modules like the Pixelify module for example, that tricks Google Photos and lets you have unlimited space like the Pixels have.
With root, you have almost unlimited possibilities of modding your phone, it's just a matter of knowing what you want to modify and finding the right mods to it.
Now, the cons:
Samsung phones have an e-fuse. Flashing custom firmware automatically trips this fuse and it is impossible to recover from unless you change the motherboard. When this fuse is blown, you will never be able to use Samsung's security features like Samsung Pass, Pay, Secure Folder, Secure Wifi, etc...
Even if you flash your stock firmware and even if you re-lock your bootloader, the fuse will still be blown.
There are some regions which even deny any warranty claims if they find out that this fuse is blown, but some places in Europe still accept the phone in this condition.
Another con is that sometimes some apps refuse to work if they detect you are rooted like Google Pay and I believe Netflix and others too (like banking apps). Some are easy to fool/bypass root detection and some are more complicated. It all depends on the app.
And to answer your final question. Fortunately for you, you still should be able to flash the latest stock firmware and if you re-lock your bootloader, you should still be able to receive updates via OTA, just keep in mind of the services that will never work again I mentioned above

Hello. I am following up with my previous post.
I found the exact zip and Odin file at Sammobile. Would this be a good start? My understanding is that the bootloader option is not available yet
...
I am learning as I go and before I move forward (big IF) I want as many redundancies as I can.

JoseAndDiezel104 said:
Hello. I am following up with my previous post.
I found the exact zip and Odin file at Sammobile. Would this be a good start? My understanding is that the bootloader option is not available yet
...
I am learning as I go and before I move forward (big IF) I want as many redundancies as I can.
Click to expand...
Click to collapse
I din't have unlocking bootloader option. But I did:-
1)factory reset phone
2)insert sim
3)restart phone
4)enable developer mode
5)And you will get a message "Welcome to Samsung your device is registered"
6)that's it OEM unlocking option will be avilable
7)power off phone
8)holding vol +&- keys connect usb to pc
9) leave both keys after you see waring messages
10)press and hold volume + key , bootloader will be unlocked and phone will be factory resetted.

aryanrh said:
I din't have unlocking bootloader option. But I did:-
1)factory reset phone
2)insert sim
3)restart phone
4)enable developer mode
5)And you will get a message "Welcome to Samsung your device is registered"
6)that's it OEM unlocking option will be avilable
7)power off phone
8)holding vol +&- keys connect usb to pc
9) leave both keys after you see waring messages
10)press and hold volume + key , bootloader will be unlocked and phone will be factory resetted.
Click to expand...
Click to collapse
Would this work for US phones?

nsfxpython said:
Would this work for US phones?
Click to expand...
Click to collapse
Unless you find a a hack, any U/U1 (USA/United States/The States/States/American/America) and W series (Canada) phones have not been bootloader unlock or root for the last 5+ years or more. If you want root options, get a B (EU/UK) or E series phone.

crazyut said:
Unless you find a a hack, any U/U1 (USA/United States/The States/States/American/America) and W series (Canada) phones have not been bootloader unlock or root for the last 5+ years or more. If you want root options, get a B (EU/UK) or E series phone.
Click to expand...
Click to collapse
Is there any way to recover deleted pictures in the Samsung A53 5G (USA version) if it is impossible to root this version of the phone?
I accidentially manually deleted some photos in my phone today with my computer (so it doesn't appear in the photo's trash bin), and every single recovery program I encountered says I need to root my phone in order to use a deep scan to look for the deleted files.

I have litte hope that there is anything to recover. Despite the fact that us versions can't be unlocked what would be necessary for rooting, flash storage management (also garbage collection, trim etc.) tends to shift data all the time to other/new cells making it unlikely for you to recover lost data on an active device. Better backup from time to time, always your best bet.

Hello! Im having an issue, maybe im doing somthing wrong. I'm at 13) After giving the img.boot.lz4 i wait and wait and the memory of the phone fills completly (Around 120+Gb) and the patched img do not comes out, any thougths?

This is a deprecated method. You have to patch the whole AP file with magisk and flash it along with BP, CP and (Home) CSC after you've unlocked the bootloader.

Andoreid said:
This is a deprecated method. You have to patch the whole AP file with magisk and flash it along with BP, CP and (Home) CSC after you've unlocked the bootloader.
Click to expand...
Click to collapse
That's right, but for folks with no experience rooting new Samsung devices, please:
- DO read OP's "Unlock bootloader" section. Visitors to this page who skip to the end and have never rooted non-Samsung or older devices might think "adb reboot fastboot" followed by "fastboot flashing unlock" or "fastboot oem unlock" will do the trick. It won't. To clarify: fastboot will NOT recognize this phone, which is normal because it doesn't have a standard fastboot mode, and simply enabling "Allow OEM unlock" in developer settings is necessary but not enough.
Do follow OP's steps for unlocking.
- For rooting, I followed the instructions here https://samsungusbdriver.me/root-samsung-galaxy-a53-5g/ (second method).
But the instructions on that page for getting the actual model number and CSC for Frija are unclear. Finding that information was not straightforward. Depending on the method I used, the model number would be SEPF_SM-A536B_12_0001, SM-A536B/DS, A536B... and you need to know CSC stands for "country-specific code" and it's a 3-character code. I eventually figured out my model was SM-A536B and CSC was EUX. But it took quite a bit of research.
-If you're not familiar with Magisk's DenyList, google it. You might have to use it some apps, particularly banking apps. I think you need it for Netflix, too. Speaking of Netflix, the version that comes preinstalled won't work after rooting. The way I got it to work was uninstalling that version and sideloading the Netflix APK from Apkpure. And adding it to Magisk's DenyList.

Hello,
I have a rooted (Magisk) A53 with TWRP. For a week, I get a notification asking me to update to security patch level of May 1st, 2023. I thought that with unlocked bootloaders, OTA wasn't possible, but whatever. My question is if it's possible to perform the update without losing TWRP and Magisk, and also if it's possible to keep all user data and installed apps. I have little time to spare after work and really don't want to go again through the process of resetting my phone.
Thanks.