Differences

This shows you the differences between two versions of the page.

--- phones:kyocera_digno_keitai_4:rooting_the_kyocera_digno_keitai_4 [2026/02/27 13:32] – phobos
+++ phones:kyocera_digno_keitai_4:rooting_the_kyocera_digno_keitai_4 [2026/06/03 18:44] (current) – typo phobos
@@ Line 1: / Line 1: @@
+====== Rooting the Kyocera DIGNO Keitai 4 ======
 <note warning>
 Unlocking the bootloader (a necessary step to root the device) wipes any data you have on the device. Rooting the device before putting any data on it prevents you from losing any time and work.
@@ Line 7: / Line 9: @@
 ^  Variant  ^  A202KC  ^  A203KC  ^  A204KC  ^  KY-42C  ^  KY-43C  ^
 ^  Confirmed working  |  1.000AL \\ 1.010AL \\ 1.031AL \\ 1.050AL \\ 1.060AL \\ 1.070AL |  1.060AN  | 1.050PO  |  1.041GC \\ 1.060GC \\ 1.080GC  |
-^  Confirmed not working  | |  1.090AN  | |  1.090GC  | |
+^  Not working via pre-1.090XX method  | |  1.090AN  | |  1.090GC  | |
-The 1.090 updates on the A202KC, A204KC, and KY-43C most likely also block rooting, but this has not yet been confirmed. A way of bypassing this has been found, but not yet documented on this wiki. Join our [[https://discord.gg/hSUkk3NYZe|Discord]] if you would like the details.
 ===== Introduction =====
@@ Line 18: / Line 18: @@
   - Having read, and understood the warning at the beginning of the page.
-The rooting process will require a tool called [[https://github.com/bkerler/mtkclient|MTKClient]], which will facilitate dumping images from the phone, unlocking the bootloader, and flashing the patched images back onto the device.
+==== Checking your build number ====
-MTKClient is unfortunately not easily usable on platforms other than Linux, and even on Linux it can be a hassle to set up. Due to this, we have created a [[wp>Live USB]] environment with the tool preinstalled and ready to use.
+<note important>At this time there is no known way to root the KY-4XC if the version number is 1.090XX or above.</note>
-The rest of this page is a step by step guide for the rooting process.
+The rooting method will differ depending on if your phone has been updated past the 1.090XX build number. This version includes a patch that blocks the originally used method.
+You may find your build number in settings under "About phone">"Build number" in the format 1.0XXXX. If your build number is higher than 1.090XX (i.e. 1.110XX), see the [[#models_after_version_1090xx|models after version 1.090XX]] section, otherwise continue to the [[#models_before_version_1090xx|models before version 1.090XX]] section.
+===== Models before version 1.090XX =====
+This rooting process will require a tool called [[https://github.com/bkerler/mtkclient|MTKClient]], which will facilitate dumping images from the phone, unlocking the bootloader, and flashing the patched images back onto the device.
+MTKClient is unfortunately not easily usable on platforms other than Linux, and even on Linux it can be a hassle to set up. Due to this, we have created a [[wp>Live USB]] environment with the tool preinstalled and ready to use.
-===== Rooting =====
+The rest of this section is a step by step guide for the rooting process.
 ==== 1: Downloading Magisk ====
@@ Line 31: / Line 41: @@
 Install from F-Droid: https://f-droid.org/en/packages/com.topjohnwu.magisk/
 Install from the Magisk GitHub: https://github.com/topjohnwu/Magisk/releases
@@ Line 45: / Line 56: @@
 The wiki does not go through the process of installing MTKClient manually at this time.
-If you would like to install MTKClient manually for any reason then feel free to reach out on our [[https://discord.gg/hSUkk3NYZe|Discord]] for assistance. You can find the install steps on the MTKClient GitHub but they are very outdated: https://github.com/bkerler/mtkclient#installation.
+If you would like to install MTKClient manually for any reason then feel free to reach out on our [[:start#community|community]] for assistance. You can find the install steps on the MTKClient GitHub but they are very outdated: https://github.com/bkerler/mtkclient#installation.
 The rest of this guide, as well as the command syntax will differ from using the manually installed version. You can use this guide as reference however while paying close attention to the differences on the MTKClient official usage guide: https://github.com/bkerler/mtkclient/blob/4ee021531144e7aadff63479bb5c4a44b721131e/README-USAGE.md
@@ Line 67: / Line 78: @@
 {{:phones:kyocera_digno_keitai_4:digno_4_rooting_example_dumped_images.png?800|}}
-==== 4: Patching the images ====
+In the terminal again, type in and run:
+''sudo mtk reset''
+This will reboot the phone and you can now unplug the device.
+==== 4: Backing up the images ====
+If something goes wrong during the rooting process these images will be instrumental to reviving the phone. The live boot is impermanent and the dumped files will be lost forever once you exit it.
+Because of this it is important to backup these files through some method. Here are some recommended options:
+=== Use a spare USB flash drive/SD card ===
+Plug in another USB capable device, and using the file explorer move the files onto the device, and safely eject the drive.
+=== Using your phone's internal storage ===
+If you do not have a USB you can use your phone to transfer the files from the live boot to your regular operating system.
+After rebooting your phone, reconnect the USB and accept the "Allow MTP" prompt (if you dismiss it just re-plug the phone again). On the PC you will find a phone icon on the desktop, navigate to "Downloads" and place the files there. Safely eject your phone.
+Now at the top right press the red power button and shut down, immediately after unplug the live boot USB. Turn your computer back on and boot into your regular operating system.
+Now plug in your phone and copy paste the files you put on the phone to somewhere safe on your computer. Specially copy paste them as you will need to keep them on your phone. Safely eject the phone.
+Now plug the live boot USB back in and repeat the steps you took to enter the live boot. Once back in the live boot plug the phone back in and copy paste the files on the phone into the Home folder shown earlier.
+==== 5: Patching the images ====
+//
+If you used your phone to backup your files in the last step ignore this next part.//
+In the live boot, plug your phone into your PC and accept the "allow MTP" prompt. On the PC you will see a phone icon on the desktop.
+Double click the phone icon and navigate to the "Downloads" folder. Now copy paste the boot.bin file into that folder.
+You may want to use [[:screen_mirroring|screen mirroring]] which can be accessed by opening a new terminal window and entering:
+''scrcpy --render-driver vulkan''
+{{:phones:kyocera_digno_keitai_4:digno_4_rooting_example_scrcpy.png?800|}}
+Now on your phone open Magisk, select "Install">"Select and Patch a file" and in the file chooser go to "Downloads" and select boot.bin.
+After completion Magisk will display the name of the patched file. Back on the PC go back to the phones downloads folder and find the patched file. Copy this file and place it in your home folder, rename it to boot.patched (.patched is the file extension).
+{{:phones:kyocera_digno_keitai_4:digno_4_rooting_example_home_boot_patched.png?800|}}
+If you need to exit the live environment before the next step, you will need to backup the boot.patched file. Otherwise you will lose the file as you will be wiping the phone. It also is good to have for our archive if you would like to contribute.
+==== 6: Unlocking the bootloader ====
+Now we will be unlocking the bootloader, which in the process will delete all data on the phone.
+Turn the phone off again and plug into your PC.
+The first command will erase metadata and userdata (and md_udc if existing). In the terminal run:
+''sudo mtk e metadata,userdata,md_udc''
+Next you will unlock the bootloader:
+''sudo mtk da seccfg unlock''
+If you had no errors congratulations, your bootloader is now unlocked!
+Now restart the phone:
+''sudo mtk reset''
+You'll see that there is an "orange state" warning on the reboot, seeing this means that the bootloader was successfully unlocked. It is relevant to mention that you may want to relock the bootloader after rooting, a sub section of the final step will go over how to do so.
+After the phone restarts, immediately turn it off again for the next steps.
+==== 7: Flashing the patched images ====
+This section assumes that you have the vbmeta.bin and boot.patched file in your home directory like so:
+{{:phones:kyocera_digno_keitai_4:digno_4_rooting_example_home_boot_patched.png?800|}}
+These two commands will flash the files onto the phone, open a terminal and run:
+''sudo mtk da vbmeta 3''
+and immediately after:
+''sudo mtk w boot boot.patched''
+And finally:
+''sudo mtk reset''
+Congratulations! Your phone should now be rooted. At this stage you can exit the live environment if you so choose, although there are a few things you may want to consider from the following first:
+=== Setting language to English ===
+After you are rebooted just press enter on all the prompts in Japanese until you get to the home screen. To change the language to English go to settings, select the bottom option ("more settings") and the 7th option down is language where you can swap it to English.
+=== Testing for root access ===
+You can immediately test if the phone has been successfully rooted by opening a terminal on your PC and running some ADB commands to the phone. You'll need to activate USB Debugging in Developer settings again: [[:setting_up_adb|ADB Setup]].
+Run:
+''adb shell''
+You will now be in the phones terminal basically. Attempt for root access by simply entering:
+''su''
+If you get a prompt on screen asking to allow root access you have successfully rooted the phone and have root access.
+=== Relocking the bootloader ===
+Keeping the bootloader unlocked introduces additional security risks, but it is not possible to keep it locked on a rooted device. If you would like to re-lock the bootloader, and you have a device running the stock boot firmware, run:
+''da seccfg lock''
+===== Models after version 1.090XX =====
+<note important>At this time there is no known way to root the KY-4XC if the version number is 1.090XX or above.</note>
-==== 5: Unlocking the bootloader ====
+At this time this section is a stub. This method has only been done once on the A203KC, the method is documented on our [[:start#community|discord server]]. Please be advised that this method has yet to be replicated, we hope to document the process when it is better understood.
-==== 6: Flashing the patched images ====