Related
MOD EDIT: VRoot discussions aren't currently allowed on XDA as it is under review. Be aware that Vroot is known to collect your IMEI, S/N and more information, and is able to download (any) file from their servers, which may or may not include malware. Thread closed.
I have sacrificed a lot of time trying to be administrator of my own 824 . Currently this is the ONLY WAY which works on my device. Its described on german page (link removed), but I realize its hard language ( I cant speak it too ), so I give full description of rooting sweet 824:
1. enable USB Debugging in developer settings while ur device is not connected to anything
2. switch ur connecting mode to PTP ( storage>'upper right corner options')
3. download and install application from this site link removed
4. run the program and connect ur tab in PTP mode.
5. click ROOT. After few minutes ur 824 will reboot ( not much longer than usual)
6. if u wanna check if the process is accomplished u can check it with Terminal Emulator entering su and observing # prefix
7. enjoy
U can try it with other devices u couldnt root and give feedback.
Hi guys. I was checking the forums of emui here in XDA and I saw a guy mentioning (here: https://forum.xda-developers.com/an...ing-xposed-t3338765/post66250513#post66250513 ) the HRT team from China (HUAWEI ROM TEAM) is always developing custom roms for HUAWEI devices and found this rom:
http://club.huawei.com/thread-10756653-1-1.html
I used google translate to translate the webpage and it seems to be pretty new and it includes Xposed frameword which for me is super! And also it's based in the latest firmware 130 for our HONOR 5C. If some of you know chinese or how to get proper instructions of how to install the ROM would be great.
Thanks you all! and let's try to get it together!
Hi !
It's possible we have a tutoriel for the installation in english please ?
Thanks !
DaRkLinK_35 said:
Hi !
It's possible we have a tutoriel for the installation in english please ?
Thanks !
Click to expand...
Click to collapse
Hi DarkLink, that is what I'm asking. Someone who knows chinese to have proper isntructions. Cheers
The methods is traditional...
Recovery -> Wipe All -> and flash maybe...
I tried it, its not working at all, got stuck at blank screen after boot logo, unable to reset. End up updating with stock rom using, vol- vol+ power button.
One thing to note is that the chinese huawei glory 5c model is launched with volte and there is no seprate modem update we can flash.
Woooh.. I see.
Well... I think this rom is not flashable now !
Mike_Wasawsky said:
Hi DarkLink, that is what I'm asking. Someone who knows japanese to have proper isntructions. Cheers
Click to expand...
Click to collapse
There is no need for Japanese casue it is in Chinesee.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
Features】
Based on the current B130 firmware
Perfect root privileges. .
Delete the contact list of Huawei's contact information
Integrated Busybox instruction set
As the SuperSu in the background will be EMUI kill. So, the first time when using the fantasy settings, please manually open the SuperSu once to get permission
【Dream Setting】
Adding advanced power, the normal restart to the recovery and bootloader
Protect your eyes with the Eye Care Assistant
Join the program to freeze the app and disable the unwanted app
Join the Xposed framework
Join K song effects
Join the WiFi password view feature
Add recovery brush to write tools
Increase the DPI setting
Add CPU frequency adjustment
【Brush Note】
1. Please strictly follow the following brush machine tutorial operation
2. After downloading the Brush Pack, please check the Brush package size and whether to download the full
3. System comes with root privileges, such as the use of the system do not know the blind do not delete. . Otherwise it may lead to cell phone brick
4. Any questions welcome to our private letter Sina microblogging feedback microblogging ID: dream without glory
Brush tutorial
1. Must first unlock the phone, and successfully brush into the Chinese TWRP Recovery, to ensure that the computer installed a good phone driver, download recovery after decompression, the phone open USB debugging connected to the computer, double-click xx.exe start to brush into
2. Download ZIP format brush package, copied to the memory card, can be an external card can also be built-in card, you can copy to the root directory, you can also copy to a subdirectory
3. Use the Recovery tool or press the volume + power button to enter the recovery interface
4 Go to Recovery, click to clear the data "slide clear the data" and then return to the main interface
5. Back to the main interface, select "Install Brush Pack" "Select Brush package location (TWRP internal storage called: emmc, external storage called sdcard, click the top of the UP A Level to return to a directory)" Click Brush Package "sliding brush into
6. Wait about 2 minutes to complete the end of Brush "Click to restart the device to restart the phone
7. Phone restart
ROM built several practical software to promote, if you do not like to directly use the re-file manager to uninstall ~ ~
Disclaimer: Recently discovered that someone steal my ROM to join the promotion without the test release, if found also asked machine friends to report, please respect the author of labor results, forbidden based on the ROM for the second package ~ ~
[ROM screenshot]
By GoogleTranslator
This guide is based on the original PewPewK post.
Which, in turn, was inspired by TopJohnWu's 'Samsung (System-as-root)' Magisk Installation Guide
It is an extended walk through aimed at ALL users, meant specifically for the SM-T720 (Tab S5e) BUT specifically meant to:
UNLOCK THE BOOTLOADER
INTRODUCE ROOT
RESTORE STOCK/RELOCK THE BOOTLOADER
Because of the community support, the options available to you have become numerous!
So if you're looking to squeeze EVERY inch out of your tablet, search the thread for suggestions or see the links below:
Go HERE if you are interested in custom recovery (e.g., TWRP).
Go HERE if you are interested in custom ROMs or kernels.
ROOT WARNING
Introducing root and further tampering may lead to unfavorable performance and/or shortened device lifespan.
In extreme circumstances, it may render your device OR specific hardware components unstable or non-functioning.
By following this guide, you ACKNOWLEDGE these risks and release AHE_XDA, XDA and its CONTRIBUTORS of ANY and ALL responsibility.
WARRANTY WARNING
In many states, countries, provinces and territories, introducing root voids device warranty (manufacturer's and/or third-party). Please consult your regional Samsung office, place of purchase or third-party warranty company to determine if these terms are applicable to you.
ALTERNATIVES TO ROOT
If you are looking to maintain warranty and continue access to Samsung-specific features, consider disabling or uninstalling unwanted applications via the Android Debugging Bridge (ADB).
TiTiB, a genius in his own right, has a thread dedicated to the Tab S5e and bloat removal without the cost of warranty.
Visit it HERE and click 'Thanks!' if it helped.
Known Issues (January 31, 2020)
KNOWN ISSUES (January 31, 2020)
Where's Recovery?
Explanation: TWRP (custom recovery) is NOW available. Please visit TeamWin for instructions.
Workaround: Resolved as of August 6, 2019.
Magisk shows as 'Not Installed.'
Explanation: Magisk, due to the changes to the recovery partition in Android Pie & above, will not boot automatically. It requires user intervention.
Workaround: To enable root access, be prepared to hold 'Volume Up' and the 'Power' keys on EVERY BOOT or REBOOT.
WiFi stopped working after installing 'magisk_patched.tar' with Odin.
Explanation: Cause unknown as of January 31, 2020.
Workaround: In some cases, after introducing root ('magisk_patched.tar'), WiFi may stop working. If this happens, do the following:
From the app drawer, go to Settings > Connections > Wi-Fi.
Highlight and select your WiFi network.
Long press the network name and select "Forget Network".
Wait 3 to 5 seconds.
Press and click on the network in which you asked Android to forget.
Re-enter your password.
If entered correctly, WiFi will resume connectivity.
"Your phone is locked because the payment service was uninstalled."
OR
Only official released binaries are allowed to be flashed (vbmeta).
Explanation: To protect against various threats (e.g., compromised data, theft or root), Samsung, as of December 2017, introduced a series of low-level initiatives to LOCK the device should ANY part of Knox be compromised. These initiatives are frequently referred to as 'KG' (KnoxGuard) or 'RMM' (Remote Monitoring and Management).
Further details can be found HERE.
Workaround: A workaround now exists, thanks to @ianmacd, but requires TWRP to be installed followed by the Samsung multi-disabler file.
If you do NOT intend to install TWRP, precautions MUST be taken not to freeze, disable or remove the following files:
'Payment Services' (com.samsung.android.kgclient)
'KnoxGuard' (knoxguard.apk)
In most circumstances, the issue will present itself immediately after the application(s) is frozen, disabled or removed. In rare circumstances, only after a device restart.
PRO-TIP: Do NOT reboot unless absolutely necessary; opt to power down the device.
Should you encounter EITHER error, you will need to boot into 'Download Mode', revert to original factory settings and verify your Google account to avoid an FRP LOCK.
To enter 'Download Mode' and recover from the error:
Connect a USB cable to your Laptop/PC.
With power-off on the device, hold down BOTH 'Volume Up' and 'Volume Down'.
Connect the USB cable to the device, while holding down both volume keys, and press 'Power'.
If done correctly, the device will boot to 'Download Mode'.
My Streaming Service won't log me in, no longer provides HD viewing or doesn't allow offline downloads.
Explanation: Widevine is a digital rights management platform used by major streaming companies to prevent piracy.
Low-level details can be found HERE.
Workaround:
Resolved by @ianmacd and his 'liboemcrypto disabler' via Magisk Manager and/or Custom Recovery (e.g, TWRP) as of April 4, 2018.
NOTE: If you installed TWRP and flashed the Samsung multi-disabler file, this issue is resolved of as December 13, 2019.
If you do NOT intend to install TWRP, log-out and uninstall your streaming application(s). With root introduced and magisk enabled, download 'liboemcrypto' from 'Modules' within Magisk Manager. You will be asked to restart after installing the module. Do this and re-enable Magisk on boot. Sideload your streaming application(s) from a source OUTSIDE the Playstore. Log in and resume streaming.
Items are ADDED and UPDATED as they are discovered, solved or a workaround is introduced. Please message me directly if something is missing.
Requirements & Instructions
HARDWARE & SOFTWARE REQUIREMENTS
Windows Laptop/PC with more than 25GB of available storage space
SM-T720 Tablet (Galaxy Tab S5e)
Samsung USB Type-C Cable (as found in the original packaging)
WIFI connection (and if necessary, login details)
SECTION ONE - LOG-OUT & BACK-UP YOUR DATA
Log out of your Samsung and Google account(s).
Back-up ANY and ALL data as following this guide will result in COMPLETE data loss.
SECTION TWO - DOWNLOAD THE RIGHT UTILITIES
In order to root, you require several utilities.
They are as followed:
Samsung USB Drivers - Provides connectivity between Laptop/PC and your device.
7-Zip - An open-source file archiver.
Odin 3.13.1 - Used to flash original or custom Samsung firmware.
Frija - Downloads the latest available Samsung firmware.
Magisk Manager (APK) - Helps obtain/manage and extend root options. Download the latest .APK (Application Package).
Click on the UNDERLINED NAME of the above utilities to download them to your local Laptop/PC.
PRO-TIP: Create sub-directories, like pictured below, and organize your downloads accordingly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PRO-TIP: Consider a donation to Frija, Magisk or your favorite developers as a token of goodwill and to help ensure future development efforts.
SECTION THREE - DOWNLOAD THE RIGHT FIRMWARE
In order to root or, at a later time, return to original factory settings; you MUST have a local copy of firmware.
This requires knowing our CSC; a three letter code that Samsung devices use to comply with local telecommunication standards and determine device-specific features or updates.
To locate your CSC, perform the following:
On your device, go to 'Settings'
From 'Settings', scroll down to 'About Tablet'.
Press on 'About Tablet' followed by a press on 'Software Information'
Scroll downwards until you see 'Service Provider SW Ver.'
There are three lines.
The third line will read similar to the following:
TUR//
Those three characters (e.g., TUR) represent the CSC code for your region.
PRO-TIP: Your CSC may OR may not be the same as the example; that's expected and perfectly normal.
Open Frija, which you downloaded under 'Section One', and input your model and CSC.
Make sure 'Auto' is selected and click on 'Check Update'.
If the right values are inputted, Frija will look similar to the following:
Click on 'Download' and select a location on your Laptop/PC.
When the download is complete, Frija will verify and decrypt the firmware.
Once finished, Frija will look similar to this example:
PRO-TIP: If you can't get Frija to open or download, right click and select 'Run as administrator'.
SECTION FOUR - UNLOCK THE BOOTLOADER
THIS STEP WILL REMOVE ALL DATA FROM YOUR DEVICE. PLEASE REFER TO 'SECTION ONE' FOR MORE DETAILS.
Power off the device.
Power on your Laptop/PC and login into your Windows account.
Connect the USB cable to your Laptop/PC but NOT to your device.
On the device, hold the 'Volume Up' and 'Volume Down' keys at the SAME time.
Connect the USB Cable from your Laptop/PC to the device.
You MUST hold BOTH keys during AND after inserting the USB Cable to receive the following warning:
PRO-TIP: In SOME cases, you may also need to hold 'POWER' as well.
To continue towards unlocking your bootloader, hold the 'Volume Up' key for approximately 4 to 5 seconds (or until the screen goes black).
After 4 to 5 seconds have passed (or if the screen went black), release the 'Volume Up' key and you will be presented with one last warning:
Press and click on the 'Volume Up' key to finalize your decision.
The device will factory reset and from now on, until the bootloader is re-locked, you will receive this warning:
Leave the device to reinitialize. This will take approximately three minutes. The device will erase itself and you will notice several reboots. Afterwards the only activity you'll see is a pulsing 'SAMSUNG' logo. Eventually you will be presented with the 'Let's Go!' set-up screen. Set the device aside for now.
SECTION FIVE - INSTALLING 7-ZIP
If you correctly followed the first FOUR sections, you now have the required utilities, firmware and an unlocked bootloader.
In order to proceed, you MUST install 7-Zip to extract and manipulate key files required for root.
If you have prior experience with 7-Zip or an alternate compression manager, SKIP this step and proceed to 'SECTION SIX'.
It IS enough to double-click the EXECUTABLE and install it; you need NOT configure anything.
However, for a visual reference, follow this LINK to see 7-Zip in use.
Alternately, for technical support and assistance SPECIFIC to 7-Zip, use this LINK. Search thoroughly before posting.
SECTION SIX - EXTRACTING FIRMWARE
Like the CSC code, mentioned in 'SECTION THREE', the name of your download will differ slightly but 'SM-T720' and 'AP_T720' will be in the file name:
Using 7-Zip, you must extract the following file:
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
From the following ZIP container:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
Right click on your ZIP container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
7-Zip will begin to decompress the necessary files and will result in the following output:
Delete ALL files except for the following:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
Rename the extension of 'AP_T720XX.....tar.md5' to 'AP_T720XX.....tar' and ignore the warning provided by Windows.
When finished, your folder contents will look similar to this:
The AP file is required for root.
PRO-TIP: Keep the ZIP container should you ever want to revert back to original factory settings. If not, delete it and download again later using Frija.
SECTION SEVEN - ENABLE WIFI, TRANSFER FILES & INSTALL MAGISK MANAGER
In 'SECTION FOUR', the device was left to reinitialize.
This means you have a device that requires set-up:
Do NOT log into your Samsung or Google account. The ONLY thing required is WIFI:
PRO-TIP: WIFI and Magisk work together to help achieve root access, provide updates and for module repository access.
Once you've arrived at the home screen, you need to enable 'Developer Options' to ensure the bootloader is unlocked.
To verify your bootloader is unlocked, perform the following:
On your device, go to 'Settings'.
From 'Settings', scroll down to 'About Tablet'.
Press on 'Software Information'.
Scroll downwards until you see 'Build Number'.
Tap 'Build Number' seven times to enable 'Developer Options'.
Press the back button on the navigation bar to return to 'Settings'.
Underneath 'About Tablet', you will now see 'Developer Options'.
Open this and locate 'OEM Unlocking'.
If you've followed the outlined steps, your screen should match this example:
PRO-TIP: If your screen does NOT match the example, it is possible you are NOT connected to WIFI or you did NOT successfully unlock the bootloader. If all these conditions are true, restart the device and check again. If the issue persists, create a NEW response in the thread.
Now connect the device to your Laptop/PC and, when prompted, 'Allow access to tablet data'.
Using Windows Explorer, copy the following files to the 'Download' folder of your device:
MagiskManager-v7.3.2.apk
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
Due to the size of the AP file, this may take several minutes on a low-end Laptop/PC.
Once the copy is complete, go to your device and double press on 'MagiskManager-v7.3.2.apk' to initiate the install process.
PRO-TIP: Due to changes introduced in Android Oreo, you MUST allow permission to install applications (APKs) not obtained from the PlayStore.
Click on 'Settings' to open the 'Install unknown apps' screen and toggle 'Allow from this source' on.
Press the back button on the navigation bar to allow the installation:
SECTION EIGHT - PATCH YOUR AP FILE
Open your app tray by swiping up and open Magisk Manager.
You will see a RED QUESTION MARK and the following error:
'Magisk is not installed.'
Click on 'Install' and, when prompted by Magisk, select 'Install' again:
Magisk will provide another prompt:
Choose 'Select and Patch a File' to proceed.
Magisk will now prompt for device access:
Click on 'Allow' and the internal Device File Explorer will open to the 'Recent' tab:
Click on the top app bar and select 'Downloads' to find your AP file:
And then:
Once inside the 'Downloads' folder, select your AP file to begin the flash process.
Once the flash process is complete, the status on the top title bar will change from 'Flashing' to 'Done!':
SECTION NINE - RETRIEVAL & DISSECTION
With our AP file patched by Magisk, you must now locate and transfer it back to our Laptop/PC.
If you have not already done so, reconnect the device to your Laptop/PC:
Open Windows Explorer, double-click on 'Tab S5e', double-click again on 'Tablet' and open the 'Downloads' folder:
Under 'Downloads', you will see THREE files:
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
magisk_patched.tar
magisk_install_log_2019-07-10T225845Z
PRO-TIP: 'magisk_install_log' is an output of the AP file patching process. If you encountered ANY errors, keep a copy and raise a question in the thread.
Delete 'AP_T720XX.....tar' and copy 'magisk_patched.tar' back to your Laptop/PC; preferably to the 'FIRMWARE' sub-directory suggested in 'SECTION TWO'.
Due to the size of the 'magisk_patched.tar' file, this may take several minutes on a low-end Laptop/PC.
Once the transfer is complete, let's make room in our 'FIRMWARE' folder by deleting the 'AP_T720XX.....tar' file.
This should leave you with TWO files:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
magisk_patched.tar
Move OR delete the 'SM-T720.....fac.zip' container so you can focus exclusively on 'magisk_patched.tar'.
With NO files left except for 'magisk_patched.tar', you must now use 7-Zip again to extract its contents.
PRO-TIP: Refer to 'SECTION FIVE' if you need a refresher on 7-Zip.
Right-click on the 'magisk_patched.tar' container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
Once all files are extracted, your output will look similar to, if NOT exactly like, this:
Now DELETE these files:
dtbo.img.lz4
magisk_patched.tar
modem.bin.lz4
persist.img.ext4.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vendor.img.ext4.lz4
In order to have the following:
meta-data [FOLDER]
boot.img
recovery.img
vbmeta.img
If done correctly, your folder output will look like this:
SECTION TEN - CREATE YOUR TAR
In 'SECTION NINE', you organized the following list of files/folder:
meta-data [FOLDER]
boot.img
recovery.img
vbmeta.img
Using Windows Explorer, navigate to your 'Firmware' folder (or whatever location you used).
Now, using 7-Zip, you need to compress these files into a TAR container.
This means you must select ALL files.
This can be achieved by using CRTL + A on your keyboard or simply by highlighting them all with a left-click:
Right-click on the selected files, navigate to '7-Zip' and, from the sub-menu, select 'Add to archive...':
If done correctly, the following screen will present itself:
Only THREE things MUST be done to complete our TAR:
Change the filename to 'magisk_patched' WITHOUT quotations
Change the 'Archive format' to 'TAR'
Click on 'OK' to confirm your decisions and begin compression:
PRO-TIP: If, for ANY reason, you don't want to keep these files, you can select 'Delete files after compression' before clicking on 'OK'.
With this step complete, you are left with the following output:
SECTION ELEVEN - DOWNLOAD MODE
Using the 'Power' key on your device , select 'Power off':
Disconnect the USB cable or the device will switch to 'Charging Mode':
On your device, hold 'Volume Up' and 'Power' together until the 'Android Recovery' screen appears:
'VOLUME UP' will navigate upwards, 'VOLUME DOWN' will navigate downwards, and 'POWER' will highlight and confirm your choice.
PRO-TIP: You may have to press 'POWER' twice.
Highlight and select 'Reboot to bootloader' to properly put your device into 'Download Mode':
Reconnect the device back to your Laptop/PC.
SECTION TWELVE - ODIN PREPARATION AND FLASH
Now, because recovery is unavailable, you must use Odin to flash your TAR file to introduce root.
In 'SECTION TWO', you downloaded Odin and created a folder for it.
You must now go to that folder, or whatever folder you opted to use, and decompress Odin.
Right-click on the 'Odin3_v3.13.1.zip' container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
This will create a sub-directory called 'Odin3_v3.13.1'.
Double-click and you will be presented with the following output:
Double-click on 'Odin3 v3.13.1.exe' to launch the application.
You will receive a prompt written in both English and Korean. Click 'OK' to close the warning.
With Odin open, locate and click on the second tab called 'Options' and uncheck 'Auto Reboot':
When you click on the 'AP' button, Windows File Explorer will automatically launch.
As per 'SECTION NINE', and using Windows File Explorer, navigate to the location you created and saved 'magisk_patched.tar'.
Double-click 'magisk_patched.tar' (or alternatively, highlight the file and select 'Open') to have it load into the AP slot:
With all these steps completed and your device connected, STOP and read below:
A green navigation bar on Odin, and a white bar on you device, will appear.
This indicates that key files are being written to your device.
Irregardless of how quick or slow the progress bar is, DO NOT disconnect the device.
The device, no matter if the flash was successful or not, will do NOTHING because you unchecked 'Auto Reboot'.
Wait for 'PASS!' to appear in Odin before you disconnect your device.
If everything was done correctly, Odin will look like this:
Your device, on the other hand, will have the following bar across its screen:
Now disconnect the device, STOP and read below until you feel comfortable enough to execute the instructions:
Hold 'Volume Down' and 'Power' until the screen goes black (also known as a 'Soft Reset').
The moment the screen goes black, continue to hold down 'Power' but QUICKLY switch so now only 'Volume Up' is being held.
Do this until you enter 'Android Recovery'.
As outlined in 'SECTION ELEVEN', use the 'Volume Keys' & 'Power' to navigate the menu.
First select 'Wipe Data/Factory Reset' and, upon completion, choose 'Reboot System Now'.
Your device will reboot several times. This is expected behavior.
If everything was done correctly, your device will reinitialize and require set-up again:
SECTION THIRTEEN - ROOT VERIFICATION
Like 'SECTION SEVEN', you need WIFI to complete set-up but mustn't log into ANY accounts.
Also, like 'SECTION SEVEN', you will need to install Magisk Manager again.
Once the first two steps are complete, power-off the device:
With the device powered off AND disconnected, hold down 'Volume Up' and 'Power' until you see the following warning:
WARNING: From now on, on EVERY BOOT or REBOOT, you MUST do this if you want Magisk enabled.
Release all keys and allow the device to boot.
Once Android is loaded, launch Magisk from your app drawer.
If you are prompted to update, do so but select 'Direct Install (Recommended)' and remember the key sequence on reboot:
Magisk Manager, if set-up properly AND with root enabled, will look like this:
Magisk Manager, if NOT set-up properly OR with root disabled, will look like this:
PRO-TIP: To further validate root, you can use an application like 'Root Checker' to verify:
You may now log into your accounts and finish configuring the device.
Recognition & Sharing Policy
RECOGNITION
This guide, and the required methods and software, would NOT be possible with the efforts of the following individuals:
@topjohnwu
@ianmacd
@LuK1337
@invmini
@CrazyApe
@eragon5779
@PewPewK
A sincere thank you for your time, hard work and, most importantly, determination to explore.
Praise and tribute is also extended to @TiTiB for his editorial skills, testing and much needed feedback.
SHARING POLICY
Do NOT reuse any part of this guide without first asking.
Do NOT reuse any part of this guide without giving credit to those in the 'RECOGNITION' header.
ALL photographs, not screenshots, are the property of myself (AHE_XDA). I spent considerable time capturing and editing each posted photograph. Therefore photographs may NOT be downloaded, copied, reproduced or used anyway without consent.
If there's something you like (styling/format/text/photographs) and want to use, ask.
Return To Stock Instructions
To return to stock and/or relock the bootloader, these are the best instructions available:
https://forum.xda-developers.com/showpost.php?p=79698366&postcount=44
They are originally intended for the Galaxy S10 series but work perfectly for the Tab S5e (SM-T720).
Full credit to @robbo1947.
Very nice how-to!!!
Would've made my first attempts much easier
I made it through the old way, getting all bits and pieces from through the other thread, this saves new comers hours of reading through all info available and getting it done at once.
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
Side note I never used the key combo on rebooting for magisk updates or other stuff, always had root enabled afterwards.
You've done one helluva job @AHE_XDA!! I can't even imagine how long it took to put all of this together. It leaves nothing to be desired. Honestly, I've never seen such a comprehensive guide on xda before. Here's some $$$$$$$$$$ in thanks.
BTW, I'm fully up and running with Magisk and am currently freezing away many apps.
CAUTION: Be very careful when freezing anything Samsung 'billing' related.
I got a bit carried away freezing Samsung stuff and locked it up tighter than a drum.
FYI, before rooting I was disabling every Samsung app I could (including com.sec.android.app.billing) and had no problems. Root really *is* powerful.?
Anyways, if you get in to a predicament like mine and see these screens there is still hope.
Power off> Hold both VOL> Plug in PC-connected USB cable> Press PWR
Might take a few tries, but eventually you should get to DOWNLOAD screen.
Pics are in reverse order. You would see the one on the right first.
@TiTiB
I was able to reproduce your error.
I updated the 'Known Issues' to reflect this.
It is either 'Payment Services' (com.samsung.android.kgclient)' or 'KnoxGuard' (knoxguard.apk) that caused the error.
I can disable, freeze or delete 'Samsung Billing' (com.sec.android.app.billing) without issue.
Thank you for this info! It really helps in my continuing persuit to get rid of as much Samsung stuff as possible, while still retaining OneUI functionality. It gets a bit unnerving freezing stuff when you're several days in to setting up stuff. I'm going slower this time.
@AHE_XDA first of all thanks for this manual, I had never seen more comprehensive here!
Second, I had one attempt to root t725, it was 2 months ago. I done all steps, made patched AP, glashed successfully (only ap, not other 3 files). After reboot I got exactly same messages as described in upper post! Not debloat, but straight from boot with root.
I afraid, gone to download mode and flashing stock. Got it back.
Never tried again.
Have you idea what was wrong?
I want to do again, but afraid a little...
Thanks
ivanox1972 said:
@AHE_XDA first of all thanks for this manual, I had never seen more comprehensive here!
Second, I had one attempt to root t725, it was 2 months ago. I done all steps, made patched AP, glashed successfully (only ap, not other 3 files). After reboot I got exactly same messages as described in upper post! Not debloat, but straight from boot with root.
I afraid, gone to download mode and flashing stock. Got it back.
Never tried again.
Have you idea what was wrong?
I want to do again, but afraid a little...
Thanks
Click to expand...
Click to collapse
After you flash the AP file with Magisk, you don't want to re-install the entire binary with Odin.
You need to dissect its contents, re-compress it and THEN install with Odin.
Take a look at 'Section Ten' on the first page to see what I'm talking about.
Any questions, place them on thread or PM me.
AHE_XDA said:
@TiTiB
I was able to reproduce your error.
I updated the 'Known Issues' to reflect this.
It is either 'Payment Services' (com.samsung.android.kgclient)' or 'KnoxGuard' (knoxguard.apk) that caused the error.
I can disable, freeze or delete 'Samsung Billing' (com.sec.android.app.billing) without issue.
Click to expand...
Click to collapse
Check this-wtf?
TiTiB said:
Check this-wtf?
Click to expand...
Click to collapse
Yes, there is a dependency between the two. With App Inpector, you don't see 'KnoxGuard' explicitly listed but if you use something like 'Root Explorer', you'll find it.
Until we get recovery, like the other Samsung devices on Pie, we simply can't touch these files.
AHE_XDA said:
Yes, there is a dependency between the two. With App Inpector, you don't see 'KnoxGuard' explicitly listed but if you use something like 'Root Explorer', you'll find it.
Until we get recovery, like the other Samsung devices on Pie, we simply can't touch these files.
Click to expand...
Click to collapse
I use MiXplorer and have seen those while 'xploring'. Before rooting, when I was using PackageDisabler, kgclient was one of the disabled packages....uh, so my point is WTF?
@TiTiB
So to make sure we understand each other; you could disable/uninstall it through ADB but a removal of the apk froze the device (along with the error)?
Bixby Is Coming - July Update
In the next build of software for the Tab S5e (July), Bixby will be introduced and fully integrated into the system.
This means nothing for root but means you'll have more to uninstall/disable.
If you don't want or need Bixby, stay on ANY release prior to July.
AHE_XDA said:
@TiTiB
So to make sure we understand each other; you could disable/uninstall it through ADB but a removal of the apk froze the device (along with the error)?
Click to expand...
Click to collapse
I disabled kgclient using Disabler Pro app with no ill effects (before rooting). It's in my 'disabledpackages133-OK.xml', so I assume it was disabled. Perhaps the Disabler app handled it differently or something, idk.
After I rooted, while I was freezing Samsung apps using '3C Toolbox Pro', and I'm *almost* 100% certain Payment Services/kgclient was among them, the tablet locked up. AFAIK, these two actions, using these two apps is effectively the same thing, therefore the 'wtf' statement.
I am curious enough that I'm going to prepare for disaster, then mess around with this package—first, disabling it with the 'CCSWE App Manager (SAMSUNG)' app, then manipulating the package's contents (expecting disaster), then freezing it with 3C Toolbox—I MUST HAVE THE ANSWER!! (TiTiB *does* stand for Tweak it Til it Breaks, after all) ?
It wiil be an hour or two, and, of course, I'll post my results here.
@TiTiB
Whenever you disable or remove a system app without root; the application still exists on the device.
It's never truly gone.
It's only been removed from your profile; usually referred to as user 0 (current user).
A factory reset will bring that application right back.
Introduce root and now, because you have administration access over the entire device, remove the application and it's gone for good (or at least until you flash stock firmware).
Alter them at a root level, freeze/remove/disable, it's likely you're going to see the same error as before.
TiTiB said:
I disabled kgclient using Disabler Pro app with no ill effects (before rooting). It's in my 'disabledpackages133-OK.xml', so I assume it was disabled. Perhaps the Disabler app handled it differently or something, idk.
After I rooted, while I was freezing Samsung apps using '3C Toolbox Pro', and I'm *almost* 100% certain Payment Services/kgclient was among them, the tablet locked up. AFAIK, these two actions, using these two apps is effectively the same thing, therefore the 'wtf' statement.
I am curious enough that I'm going to prepare for disaster, then mess around with this package—first, disabling it with the 'CCSWE App Manager (SAMSUNG)' app, then manipulating the package's contents (expecting disaster), then freezing it with 3C Toolbox—I MUST HAVE THE ANSWER!! (TiTiB *does* stand for Tweak it Til it Breaks, after all)
It wiil be an hour or two, and, of course, I'll post my results here.
Click to expand...
Click to collapse
Sho'nuff, stay away from Samsung Payment/kgclient if rooted.
Maybe helpful to have some basic information about this great device in one posting:
Device Specs
https://www.mobosdata.com/phone/hisense-a5/
How to reflash Firmware directly from microSD (Tfmode)
Thanks to Anghirrim !!!
https://forum.xda-developers.com/showpost.php?p=82575517&postcount=21
Edl mode (in General)
Thanks to Anghirrim !!!
https://forum.xda-developers.com/showpost.php?p=82654769&postcount=79
Rooting for Firmware Version 6.09.06.00
Thanks to joygram !!!
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
QFIL Firmware 6.03.02 for unbricking in Edl-Mode
Thanks to gowin132 !!!
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
QFIL Firmware 6.09.06 for flashing in Edl-Mode
Thanks to gowin132 !!!
https://forum.xda-developers.com/showpost.php?p=82727173&postcount=8
Rom Download Links for flashing in TF-Mode (microSD)
6.09.06.00 Thanks to giuseppemag !!!
https://forum.xda-developers.com/showpost.php?p=82583733&postcount=28
https://drive.google.com/open?id=1JBzsFrtGtIXLYTPTMA2cc9spp_dxF_WX
Debloating help and blocking IP (Updated)
https://forum.xda-developers.com/showpost.php?p=82795057&postcount=4
Do you have an unlocked Bootloader? ( Hisense always locked!)
https://forum.xda-developers.com/showpost.php?p=82634399&postcount=117
How to enter hardware Edl mode
Thanks to joygram !!!
https://forum.xda-developers.com/android/general/hisense-a5-how-to-enter-hardware-edl-t4103929
There are a lot reviews about the device and a thread at MobileRead.
Unbricking in Detail
Unbricking the Device in Detail
Before you step forward I would recommend taking out the Sim-Card
stay offline until the device is debloated
Some general information:
Bricked, but you have an unlocked Boolader
just flash Image in fastboot or if available in twrp
*** All bootloaders of Hisense devices are locked and there's no way to unlock !!! ***
Bricked & you haven't got an unlocked Boolader
TF-Mode (microSD)
https://forum.xda-developers.com/showpost.php?p=82575517&postcount=21
download latest TF-Firmware i.e.
https://forum.xda-developers.com/showpost.php?p=82583733&postcount=28
how to enter TF Mode?
https://forum.xda-developers.com/showpost.php?p=82650955&postcount=72
shutdown the device
press both volume buttons and then power button together
release power button and wait 10s until the update screen comes up
alternative1
shutdown device
holding volume +- and power buttons together
alternative2
shutdown while holding volume +-
press+- buttons and then power button
release power button but holding +-
wait 10sec
release +- buttons
Hisense powered by Android
wait 10sec
press power button just short
If this above won't work, then the bootloader is damaged you will need to flash the Firmware in Edl-Mode with Qfil. This always works if not hardbricked!!! So relax
General Info about EDL Mode (You need to get a Qfil-Firmaware-Image)
https://forum.xda-developers.com/showpost.php?p=82654769&postcount=79
https://forum.hovatek.com/thread-21791.html
Files needed:
Edl-Mode Firmware files 6.03.02 for unbricking
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
prog_emmc_firehose_8937_ddr_000bf0e1.mbn from joygram Root-package
attachement inside "RootKit R03"
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
Qualcomm drivers i.e. 64bit for Windows 10
i.e.
https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
actual Qpst software incl. Qfil
https://www.qpstflash.com/
Before installing drivers please read this
Obey these steps before installing unsigned drivers and prevent Sahara errors
https://forum.xda-developers.com/showpost.php?p=77229641
Installing Instructions details for drivers
https://forum.hovatek.com/thread-16965.html
Installing Qpst instructions details
https://forum.hovatek.com/thread-31475.html
Start Qfil from the startmenu (inside "Qpst")
check the setup Qfil before entering edl-mode
steps 1-4. from instructions here
https://forum.hovatek.com/thread-31475.html
-> then go back and tick "flat build"
-> select Programmer and browse
-> select the "prog_emmc_firehose_8937_ddr_000bf0e1.mbn"
Now it's time to enter the edl-mode with your smartphone
How to enter edl mode
a)Soft edl mode per adb
adb reboot edl
flush image with QFIL
b) )Soft edl mode per fastboot
fastboot oem edl
fastboot reboot-edl
fastboot reboot edl
(may not work for Hisense)
c)hard edl mode
https://www.oxygen-forensic.com/upl...s_based_on_Qualcomm_chipsets_via_EDL_mode.pdf
using a hardware cable (working 100% - preferred method!!!)
https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/
(working with Hisense A5)
by shortening the pins [not recommended!!!! Don't do this!!!!]
*** you need to open the device ***
https://forum.xda-developers.com/android/general/hisense-a5-how-to-enter-hardware-edl-t4103929
If you entered the edl-mode your Qfil screen should show
"Qualcomm HS-USB QDLoader 9008" (Com-Port)
like step 5 from here
https://forum.hovatek.com/thread-31475.html
Then Click Tools -> Partition Manager
step 9
https://forum.hovatek.com/thread-31475.html
confirm ok
step 10
https://forum.hovatek.com/thread-31475.html
select boot partition and right mouse click
manage Partition Data
we won't backup, we want to restore the boot-image
press Load Image and browse the boot.img from the edl-Firmware above, flash it and wait until it successful is flashed
if there's a Sahara error check again here
https://forum.xda-developers.com/showpost.php?p=77229641
Then flash recover.img and vbmeta.img
After that reboot your phone and it must boot the system.
Then Update in TF-mode to Firmware 6.09.06 (see above)
You successfully restored your bricked phone and updated the Firmware!
Thanks to joygram, Anghirrim, gowin132, giuseppemag
and all other sources of knowledge mentioned above!
Rooting your Smartphone Firmware 6.09.06
The Sim-Card still shouldn't be attached to the device
Files needed:
latest ADB-Drivers
https://forum.xda-developers.com/showthread.php?t=2588979
joygram Root-package for 6.09.06
attached files "RootKit R03"
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
Magisk Manager latest apk
https://github.com/topjohnwu/Magisk/releases
open developer mode in system settings
search settings `kernel version' and go
tab 7 or more : developer options enabled
* enable usb debugging
enter developer mode in system settings -> "other settings"
change USB computer connection to Transfer files(MTP)
Install the adb-drivers
Start Qfil-Software in Windows
Enter Edl-Mode while connectd phone to USB
->adb devices
use adb command
-> adb reboot edl
In Qfil
* flush ROOT files with QFIL : QFIL_6.09.06
-> Select Build Type : Flat Build
-Y Select Programmer : select
prog_emmc_firehose_8937_ddr_000bf0e1.mbn
->LoadXML:
rawprogram_000bf0e1_joygram
-> Download
when complete please reboot the device.
After install in system
* magisk manager
MagiskManager-v7.5.1.apk
Finally you have root!
Thanks to joygram!!!
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
Debloating the Device privacy friendly
You restored your Firmware and have the latest Chinese Firmware 6.09.06 without Google Playstore installed
The Sim-Card isn't attached to the device
You're offline, no WiFi
You're rooted with Magisk Manager(but the bootloader is locked)
General Information
There are many ways to debloat the device.
This is only a description how I did this.
It doesn't mean that it's working for you. Please be careful. I am not responsible if oyu brick your phone. If this happened you should easily unbrick it.
So read it carefully and always check if you need the programs or not.
I debloated all system programs which I don't need and install alternatives from F-Droid Store which just need user rights
i.e.
AfWall+ as a Firewall (Root)
Calculator (SimpleMobileTools)
Calendar (SimpleMobileTools)
Clock (SimpleMobileTools)
Contacts (SimpleMobileTools)
Conversations
Dialer (SimpleMobileTools)
Editor
Essential Launcher
F-Droid
FairEmail
Foss Weather
Gallery (SimpleMobileTools)
Net Monitor for checking Net-Traffic
Open Camera
OSMAnd+
PrivacyBrowser
QuickDic
beside that:
TitaniumBackup Donate (Root) Backup & Freezing System-Apps
Total Commander (Root) file manager
VocalizerEx2 TTS
https://forum.xda-developers.com/showthread.php?t=2566795
I debloated everything that the main features of a smartphone still works:
Phone using a Sim-Card (incl. LTE, depends on your region)
TextMessages (SMS)
Internet data
WiFi (2.4 MHz, no 5Ghz)
Bluetooth
GPS
Doing backups from all system files you want to debloat with Total Commander
create directories with permissions 755
i.e.
system/_keepsave/
system/_keepsave/system
system/_keepsave/system/app
system/_keepsave/system/preload
system/_keepsave/system/priv-app
system/_keepsave/system/vendor
system/_keepsave/system/vendor/app
system/_keepsave/system/vendor/overlay
Then backup all directories to the keepsave dirs
system/app
system/preload
system/priv-app
system/vendor
system/vendor/app
system/vendor/overlay
Then setup the system settings
I disabled everything I don't need (location only Gps, automatic System Updates/Accounts, App shadow,...)
setting up Afwall to your needs
disabling captive portal login with some alternative url
disabling ipv6 in Afwall if you don't need it
Then you can try freezing system apps with Titanium Backup
Or just delete all the bloat you don't need.
I deleted in TotalCommander
system/preload
system/vendor/app
system/vendor/overlay
in system/app are only:
Code:
/system/app/CertInstaller don't remove
/system/app/CtRoamingSettings don't remove / freeze & use only if roaming
/system/app/Eink_Settings don't remove / Settings Clearview per App!!!
/system/app/ExtShared don't remove
/system/app/HardwareDetection don't remove
/system/app/NetworkSelect don't remove
/system/app/QtiTelephonyService don't remove
/system/app/SimSettings don't remove
/system/app/Vision_AutoRunManager don't remove
/system/app/Vision_Bluetooth don't remove
/system/app/Vision_CalendarProvider don't remove
/system/app/Vision_WifiDetector don't remove
/system/app/WeatherWidget don't remove / just freeze / navigation bar flickering! com.hmct.clock.systemwidget
/system/app/WebViewGoogle don't remove
in system/priv-app are only:
Code:
/system/priv-app/CarrierConfig don't remove
/system/priv-app/com.qualcomm.location don't remove / GPS
/system/priv-app/DefaultContainerService don't remove
/system/priv-app/ExtServices don't remove
/system/priv-app/ExternalStorageProvider don't remove
/system/priv-app/FusedLocation don't remove /GPS
/system/priv-app/InputDevices don't remove
/system/priv-app/MmsService don't remove
/system/priv-app/MtpDocumentsProvider don't remove / MTP
/system/priv-app/ProxyHandler don't remove
/system/priv-app/QcomMediaProvider don't remove
/system/priv-app/SettingsIntelligence don't remove / settings needed
/system/priv-app/SettingsProvider don't remove
/system/priv-app/Shell don't remove
/system/priv-app/StatementService don't remove
/system/priv-app/StorageManager don't remove
/system/priv-app/TelephonyProvider don't remove
/system/priv-app/TeleService don't remove
/system/priv-app/Vision_CallSettings don't remove
/system/priv-app/Vision_ContactsProvider don't remove
/system/priv-app/Vision_DocumentsUI don't remove
/system/priv-app/Vision_DownloadProvider don't remove just freeze
/system/priv-app/Vision_DownloadProviderUi don't remove
/system/priv-app/Vision_MmsProvider don't remove
/system/priv-app/Vision_NetworkSetting don't remove
/system/priv-app/Vision_PackageInstaller don't remove
/system/priv-app/Vision_PermissionManager don't remove
/system/priv-app/Vision_RecentsService don't remove
/system/priv-app/Vision_ScreenOffGesture don't remove
/system/priv-app/Vision_Settings don't remove
/system/priv-app/Vision_SystemUI don't remove
/system/priv-app/Vision_Telecom don't remove
After successful debloating the system to your needs, test with Afwall log and Net Monitor if there are outgoing system apps calling home
if so freeze or delete them or let Afwall just block them.
This setup works 100% for my needs, but that doesn't mean it works in the same way for you. Please be careful. I am not responsible if oyu brick your phone. If this happened you should easily unbrick it (see above).
Have fun with a debloated chinese Firmware
For the A5C version, the chinese stock rom if someone wants it (first seed, so it will take a while until there are more seeders).
HLTE202N_L1657.6.01.04.B5.zip.torrent
Shared with Dropbox
www.dropbox.com
danielvelezbravo said:
For the A5C version, the chinese stock rom if someone wants it (first seed, so it will take a while until there are more seeders).
HLTE202N_L1657.6.01.04.B5.zip.torrent
Shared with Dropbox
www.dropbox.com
Click to expand...
Click to collapse
Hi, Daniel!
Do you have the chinese sotock rom for Hisense A5 Pro (not CC)? My cell model is HLTE203T and i never can't update...
carlo.z.du4rdo said:
Hi, Daniel!
Do you have the chinese sotock rom for Hisense A5 Pro (not CC)? My cell model is HLTE203T and i never can't update...
Click to expand...
Click to collapse
Ahhh... Nope. I only got my hands into the A5C stock as it is what i got.
Hi, I'm leaving a mirror link for all Hisense A5 stuff that may be helpful in the future when original links will be dead. As a bonus there are offline OTA zip files for L1657.6.10.04.00, L1657.6.11.01.00 and L1657.6.12.01.00. When Software update downloads OTA it saves in /data/media/
Remember that OTA updates need to go in order like L1657.6.09.06.00 -> L1657.6.10.04.00 -> L1657.6.11.01.00 -> L1657.6.12.01.00. DO NOT UPGRADE from L1657.6.09.06.00 to L1657.6.12.01.00 directly.
OTA manual install:
0. Prepare at least 2 GB SD card and format it as FAT32
1. Rename desired OTA file to update.zip
2. Copy update.zip to the root of the SD card and after that insert the card into the phone
3. Go into recovery mode on the phone (I used ADB for that, if you want you can use key combination) 4. Connect it to pc via ADB (I'm assuming that you enabled USB debugging in developer options after clicking on kernel version 8 times in phone info)
4. Run `adb devices` and make sure that you allowed debugging on the phone
5. Run `adb reboot recovery` to boot into recovery mode
6. You will see 2 options on the screen - Choose 1st one
7. Now you will see 3 options - Choose 3rd
8. Now there will be 2 options - Choose 1st
9. Phone should update and reboot
Mirrored content:
Rom and OTA:
Hisense_A5_L1657.6.03.02.00_Full_Backup.7z (Backup using QFIL, every partition, official with GAPPS, flash using QFIL)
Hisense_A5_HLTE202N_L1657.6.03.02.00.7z (for debricking)
Hisense_A5_LA592C(HLTE202N)_L1657.6.09.06.00_TFDownload_202004090105_user.zip
Hisense_A5_L1657.6.10.04.00_OTA.zip
Hisense_A5_L1657.6.11.01.00_OTA.zip
Hisense_A5_L1657.6.12.01.00_OTA.zip
Root tools:
Hisense_A5_customizer-R04.7z
Hisense_A5_customizer-R05-06.10.04.00.7z
Hisense_A5_L1657.6.12.01.00_Magisk22.1_Root_by_Sillage.7z
FireHose_HiSenseA5.mbn
Hisense_A5_debloat.txt
Hisense_A5_block_hisense.sh
Hisense_A5_EDL_PINS_1.jpg
Hisense_A5_EDL_PINS_2.jpg
Hisense_A5_boot_recovery_vbmeta_6.03.02.zip
LINK: https://mega.nz/folder/QkVXUDLS#LWYIHVvuiOFxxeZpWruTlg
.
@gowings23
@JLowe
Would be possible to share:
- Stock ROM 6.12 Full QFIL Backup
- EFS/QCN backup files
- TWRP recovery (if you managed to get one)
First of All, these are my knowledge which was gained through hard reading from XDA Developers Forum, GitHub, reddit, different websites & watching YouTube Videos.DISCLAIMER: Here, I will explain all the process of unlocking Bootloader, Flashing Recovery & Rooting Your Xiaomi Phone, though the general idea is the same, so you can read it from TOP TO BOTTOM because you can use this knowledge FOR ANY ANDROID PHONE GENERALLY. Here, I also explained ALL THE PROBLEMS YOU MIGHT FACE WHILE DOING THIS, AND HOW TO GET OUT OF THOSE PROBLEMS, BECAUSE XDA THREADS AND YOUTUBE VIDEOS DOES NOT ANSWER YOUR PROBLEMS IN ONE THREAD OR IN ONE VIDEO, ONLY WHILE DOING IT, WE FIND THAT, DOING THESE WEREN'T SO EASY LIKE YOUTUBE VIDEOS OR XDA THREADS
AND OF COURSE, DO THESE ON YOUR OWN RISK, IF SOMETHING HAPPENS TO YOUR DEVICE AND YOU BLAME ME, I WILL LMAO AT YOU.
REQUIREMENTS: 1. PC/LAPTOP 2. PENDRIVE WITH OTG CABLE (FOR PRECAUTION, GO TO STEP 4.3 TO LEARN WHY)
Step Number 01: Backup All Your Data:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOU HAVE BACKUP ALL YOUR DATA, INCLUDING APP DATA, GALLARY PHOTOS, ALL OF THEM BECUASE UNLOCKING BOOTLOADER WILL RESET EVERYTHING, IT WILL START FROM THE MOMENT WHEN YOU BOUGHT YOUR PHONE FIRST & SWITCHED IT ON.
STEPS:
To Backup All Your Data-
Go to settings "backup and restore" in additional setting (or in MY DEVICE - BACK UP & RESTORE) you can use either mobile or computer backup, both are same, after backing up, transfer it to computer.
Backup your contact from "contacts" (optional, because "step a" includes this)
Then connect your phone with your pc & backup all the necessary files, for example, create a backup of these folders:
DCIM
Download
Pictures
MIUI (Gallery, recorder etc.)
Shareit, vidmate folder
Whatsapp folder (you can also backup it in google, goto SETTINGS - CHATS - CHAT BACKUP)
and others as per your necessity
My process is a manual process, so no app is required.
READ IT: in internet, you will find that you can use rooted app to backup these, like TITANIUM, or take a NANDROID BACKUP (SYSTEM AND APPS) USING TWRP RECOVERY, my boy, listen well, you haven't yet unlocked your bootloader, how can you have a rooted device and twrp recovery? (well you can have a rooted device but that also requires unlocked bootloader which will reset everything on your phone)
Step Number 02: Unlock Your Bootloader
STEPS:
Enable developer option by clicking on MIUI version 7 times
from "Additional setting", go to "developer option". there, do these:
enable OEM UNLOCKING
in device unlocking, add your MI account. if shows problem or error, remove your MI account then add it again from device unlocking, (NOT FROM MY DEVICE, ADD ACCOUNT) then, it will take you to main settings, just come back and click add again, it will work in Sha Allah.
now in your pc, download MI Flash Unlock from official MI website, HERE (better to install the latest)
Unzip it, run it using "batch_unlock", add your mi account
in additional settings again, in developer option, enable "USB DEBUGGING"
now in pc, connect your phone in fastboot mood, (swithing off then holding power button and volume down will take you to fastboot mood, there is another process of going to fastboot mood, which is described in step 3)
if your device is recognized IN MIUI UNLOCK TOOL but after connecting it in miui unlock tool, fastboot mood turns of and says "PRESS ANY KEY TO SHUTDOWN" in your phone, you may try swithing to USB port 2 but it didn't work for me. Instead, I ran this bat file code "AS ADMINISTRATOR" from XDA developer forum, you can do it too. I renamed it as "a.bat" first thing to come it my mind. then disconnect USB and connect again in your fastboot mood. Click Refresh in unlock tool.
(OR, IF YOUR DEVICE IS NOT RECOGNIZED IN MIUI UNLOCK TOOL, FOLLOW THESE:
remove MI account from unlock tools and again add, if password shows error even after typing correctly, use phone number and pass to log in, in stead of email and password. Check if device if recognized or not.
If not, try these, Download MIUI Flash Tool and unzip it, run XiaoMiFlash.exe. At the top line, find DRIVER, install all DRIVERS.
IF YOU FACE LOG FILE ERROR,
SOLUTION: JUST CREATE A FOLDER NAMED "log" in the same directory. DONE, YOUR DRIVER WILL BE INSTALLED, CLICK YES EVERY TIME, THEN CONNECT YOUR PHONE WITH MIUI UNLOCK TOOL AND CLICK REFRESH.
your device will be shown in "batch_unlock" in sha Allah. Click unlock. Remember, your phone will loose all data, just full factory reset.
8. after 99% it will show "unlock sign" at the top of your phone, and your phone will reboot, just let it reboot. It will take at best 12 minutes to reboot. Don't worry, seat tight, watch a YouTube Video of Dr. Zakir Naik or Ahmed Deedat Sir <3.9. setup your phone as if it's a new device. (it is necessary, because after this, we will flash recovery and root your phone, because it is really important to take a backup of your original "PERSIST.IMG" . it is possible for rooted device only. (though it can be done through recovery, but from magisk, it's the best way and safest).10. you can restore all backup from your pc now. (not necessary, if you want to change ROM)
Step Number 03: Install ADB (PC) & TWRP RECOVERY (Android)STEPS:
download latest SDK from OFFICIAL WEBSITE.
2. name of the download will be "platform-tools_r31.0.2-windows.zip" unzip it in DESKTOP (IMPORTANT). it's name will be "platform-tools", open it. (ADB COMMAND WILL RUN ONLY IN THIS FOLDER.
ALTERNATIVE ADB: you can also do it by one click adb installer, just install the file, and cmd will work at any position. File is given in the telegram, in my .rar file. But sometimes it shows problem, adb command is not recognized by the windows. then, above platform tools folder is useful as it always works.
3. downlead latest TWRP specific for your device from HERE. website guide: >find your device name> device model> Download Links > click either "Primary (Americas)" or "Primary (Europe)" or you can download them from XDA too (XDA process: search in google "TWRP for MI 9 se (your specific device with model number, not Mi9SE) XDA" then, go to the thread, below you will find GITHUB or any other download link, go there and you can download it from there.
4. (YOU CAN IGONORE THIS STEP, LET ME KNOW IF YOU FACED ANY PROBLEM, THOUGH YOU SHOULDN'T) rename the twrp file to twrp.img (not necessary though, check if your device extension is hidden or not, if hidden, you will not see any extension after any file, in that case, you can just rename "twrp" because img extention is already there and it's hidden. How to check hidden extention: in that folder, go to view at the top of the screen of that folder, (at beginning - beside cross, minimize then click "view"> click "option" in one row down, at extreme right side of it > click "view"> in downwards, untick "hide extensions for known file type"> click "apply">click "ok" then close it.)
5. keep the "twrp.img" (the file you downloaded, no need to rename, .img will show depending on unhidden condition) in the "platform tools" folder.
6. now go to "platform tools" folder. it's better to keep the folder in "desktop". go to the folder address, it is above the "Name, Date Modified, Type, Size" row, where it is written all the folders name that you have clicked to come to this folder. Now, click on the folder address, write "cmd", hit enter.
7. now connect your phone making sure "USB DEBUGGING IS STILL ON" because after unlocking bootloader, it will automatically be set to OFF.
write these commands: (after each command hit enter)
adb devices (it will show your device number if it is connected properly, if shows unauthorized, g0 to your phones home screen, disconnect and connect the usb again, in cmd write adb devices, a permission will pop up in your phone at bottom, not in notifications, click YES, your device will be authorized)
adb reboot bootloader (it will take you to fastboot mood instantly)
fastboot devices (it will show your device number it it is connected properly, to make sure it is still connected)
fastboot flash recovery (give space after recovery, then drag the twrp.img file here)
fastboot boot (give space after boot, then drag the twrp.img file here, your phone will boot into recovery.) ALTERNATIVE TO THIS STEP: fastboot reboot (it will reboot, but stop it instanlty by holding "power and volum up button", it is a must, it will take you to twrp manu, if you don't go now, later twrp will be removed by your phone)
AND OF COURSE, YOU HAVE TO ROOT YOUR PHONE RIGHT NOW, EVEN IF YOU DON'T WANT IT, CAUSE IF YOU DON'T, YOUR PHONE WILL REMOVE TWRP AS YOUR RECOVERY.
8. you will see twrp screen, then asking you "to keep system files as read only or swipe to allow modification, tick in DON'T SHOW AGAIN AND SWIPE TO ALLOW MODIFICATION". Then it will ask for a password to decrypt your phone, give the password to decrypt your phone. (to learn about encryption decryption, go to step number 4.3).
IF YOU FACE BOOTLOOP OR ANY OTHER ISSUE LIKE TWRP RECOVERY IS NOT STARTING AS IT SUPPOSED TO:
Again, go to fastboot mood by pressing power + volume down button. Download this vbmeta file. Go to platform tools > cmd > type
fastboot --disable-verity --disable-verification flash vbmeta (space, then drag the vbmeta file and hit enter, then follow step number 3.7
(3 is step number, 7 is the point number under step number 3)
Step Number 04: Install MagiskSTEPS:
1. you should stay in TWRP manu from the last step of STEP NUMBER 3 and your phone is connected with your computer via USB.
2. In your computer, download MAGISK FROM OFFICIAL GITHUB PAGE . Copy the magisk.apk and paste it twice in the same folder, now you have three magisk apk, rename the second one removing the "copy from name and just add .zip in stead of .apk at last. Rename the third one as this: "uninstaller.zip"
3. Now listen carefully, this is very important part of this topic:
your phone has two state: a. encrypted b. decrypted
a. IF ENCRYPTED AND CAN'T BE DECRYPTED THROUGH TWRP, that is TWRP IS NOT ASKING PASSWORD AT THE BEGINNING TO DECRYPT YOUR PHONE, THEN: some china rom's security is so encrypted, LIKE MY MI9SE, THAT TWRP CAN'T DECRYPT IT, EVERYTIME I HAVE TO RESET THE PHONE TO DECRYPT, IN THIS CASE ,YOU CAN'T ACCESS YOUR PHONE'S INTERNAL STORAGE NEITHER FROM TWRP NOR FROM PC (TWRP ACTS AS MTP, MEDIA TRANSFER PROTOCOL, MEANING YOU CAN TRANSFER FILE BETWEEN PHONE AND ANDROID IN RECOVERY MOOD), SO YOU CAN'T ACCESS YOUR INTERNAL STORAGE, YOU CAN'T INSTALL MAGISK. HERE, PENDRIVE WITH OTG COMES HANDY. Disconnect your phone Keep those three files in pendrive and connect it in OTG with your phone. go to twrp > install > select storage at bottom > select pendrive > select magisk.zip > swipe to flash. CONGRATULATIONS, YOUR PHONE IS ROOTED.
b. IF YOUR PHONE IS DECRYPTED BY TWRP AFTER GIVING PASSWORD:
Copy those three magisk file from your computer and drop it in your phones internal storage. go to twrp > install > select magisk.zip > swipe to flash. CONGRATULATIONS, YOUR PHONE IS ROOTED.
4. Reboot Your Phone (If your phone is bootlooped, which never happened to anyone I know, still for safety, again go to recovery by holding POWER + VOLUME UP BUTTON. go to twrp > install > select uninstaller.zip > swipe to flash. This will uninstall magisk from your phone and then reboot to system, your phone will reboot normally)
5. A Magisk app will be shown among your apps which is not like magisk logo. Don't touch it, Goto file manager, find those three magisk files, one file is the original magisk.apk file you downloaded, install it normally like any other app.
6. CONGRATULATIONS, YOUR PHONE IS COMPLETELY ROOTED.
Step Number 05: Backing up your PERSIST.IMG (MOST IMPORTANT)STEPS:
You will know from my other threads about what is persist partition of your phone. But let's just back it up now without knowing it. Copy it to your computer, cloud so that you never loose it.
Assuming you still have your phone connected through usb to the computer.
Install TERMUX from playstore or from HERE if you don't have play store.
in termux, type su to obtain root permission. A pop up will be shown to grant root permission, if it doesn't work, leave termux app, go to magisk app, at bottom, you will be 4 options, click the second one, you will see this screen.
grant super user permission for termux from here.
4. again go to termux, type this:
su (hit enter)
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img (hit enter)
5. your persist.img is backed up in your internal storage.
6. you can transfer it to pc manually or
use this process because it is relatively safe, though I never found any difference,
go to platform tools in cmd, type this:
adb pull /sdcard/persist.img D:\
it will take around 10 seconds, you will find the file persist.img in your PC's D drive folder, whatever the name is, the next folder to C drive, okay? Copy the persist.img wherever you want to keep it. I am again saying, it's not mandatory to do it in this way, just do normal copy paste from your phone's internal storage to your PC, it will do the work.
THANK YOU GUYS FOR READING IT ATTENTIVELY, FROM TOP TO BOTTOM, AND IF YOU DIDN'T, WHAT CAN I SAY. IT TOOK MORE THAN 30 DAYS TO ACQUIRE ALL THESE KNOWLEDGE AND YOU ARE GETTING IT WITHOUT ANY EFFORT, FREE, WHAT MORE DO YOU WANT?
My Other Threads according to "how should you read them" serial:
1. MIUI 12.5 Chinese ROM Google PlayStore Stopped Working
2. MIUI Unlocking Bootloader, Flashing Recovery & Rooting Process (This Thread)
3. Android Terminology You Must Know Before Toying with Your Android
4. ROM Naming & CUSTOM ROM, AOSP ROM, TREBLE ROM, GSI ROM, PORTED ROM
shafi1885 said:
First of All, these are my knowledge which was gained through hard reading from XDA Developers Forum, GitHub, reddit, different websites & watching YouTube Videos.DISCLAIMER: Here, I will explain all the process of unlocking Bootloader, Flashing Recovery & Rooting Your Xiaomi Phone, though the general idea is the same, so you can read it from TOP TO BOTTOM because you can use this knowledge FOR ANY ANDROID PHONE GENERALLY. Here, I also explained ALL THE PROBLEMS YOU MIGHT FACE WHILE DOING THIS, AND HOW TO GET OUT OF THOSE PROBLEMS, BECAUSE XDA THREADS AND YOUTUBE VIDEOS DOES NOT ANSWER YOUR PROBLEMS IN ONE THREAD OR IN ONE VIDEO, ONLY WHILE DOING IT, WE FIND THAT, DOING THESE WEREN'T SO EASY LIKE YOUTUBE VIDEOS OR XDA THREADS
AND OF COURSE, DO THESE ON YOUR OWN RISK, IF SOMETHING HAPPENS TO YOUR DEVICE AND YOU BLAME ME, I WILL LMAO AT YOU.
REQUIREMENTS: 1. PC/LAPTOP 2. PENDRIVE WITH OTG CABLE (FOR PRECAUTION, GO TO STEP 4.3 TO LEARN WHY)
Step Number 01: Backup All Your Data:
YOU HAVE BACKUP ALL YOUR DATA, INCLUDING APP DATA, GALLARY PHOTOS, ALL OF THEM BECUASE UNLOCKING BOOTLOADER WILL RESET EVERYTHING, IT WILL START FROM THE MOMENT WHEN YOU BOUGHT YOUR PHONE FIRST & SWITCHED IT ON.
STEPS:
To Backup All Your Data-
Go to settings "backup and restore" in additional setting (or in MY DEVICE - BACK UP & RESTORE) you can use either mobile or computer backup, both are same, after backing up, transfer it to computer.
Backup your contact from "contacts" (optional, because "step a" includes this)
Then connect your phone with your pc & backup all the necessary files, for example, create a backup of these folders:
DCIM
Download
Pictures
MIUI (Gallery, recorder etc.)
Shareit, vidmate folder
Whatsapp folder (you can also backup it in google, goto SETTINGS - CHATS - CHAT BACKUP)
and others as per your necessity
My process is a manual process, so no app is required.
READ IT: in internet, you will find that you can use rooted app to backup these, like TITANIUM, or take a NANDROID BACKUP (SYSTEM AND APPS) USING TWRP RECOVERY, my boy, listen well, you haven't yet unlocked your bootloader, how can you have a rooted device and twrp recovery? (well you can have a rooted device but that also requires unlocked bootloader which will reset everything on your phone)
Step Number 02: Unlock Your Bootloader
STEPS:
Enable developer option by clicking on MIUI version 7 times
from "Additional setting", go to "developer option". there, do these:
enable OEM UNLOCKING
in device unlocking, add your MI account. if shows problem or error, remove your MI account then add it again from device unlocking, (NOT FROM MY DEVICE, ADD ACCOUNT) then, it will take you to main settings, just come back and click add again, it will work in Sha Allah.
now in your pc, download MI Flash Unlock from official MI website, HERE (better to install the latest)
Unzip it, run it using "batch_unlock", add your mi account
in additional settings again, in developer option, enable "USB DEBUGGING"
now in pc, connect your phone in fastboot mood, (swithing off then holding power button and volume down will take you to fastboot mood, there is another process of going to fastboot mood, which is described in step 3)
if your device is recognized IN MIUI UNLOCK TOOL but after connecting it in miui unlock tool, fastboot mood turns of and says "PRESS ANY KEY TO SHUTDOWN" in your phone, you may try swithing to USB port 2 but it didn't work for me. Instead, I ran this bat file code "AS ADMINISTRATOR" from XDA developer forum, you can do it too. I renamed it as "a.bat" first thing to come it my mind. then disconnect USB and connect again in your fastboot mood. Click Refresh in unlock tool.
(OR, IF YOUR DEVICE IS NOT RECOGNIZED IN MIUI UNLOCK TOOL, FOLLOW THESE:
remove MI account from unlock tools and again add, if password shows error even after typing correctly, use phone number and pass to log in, in stead of email and password. Check if device if recognized or not.
If not, try these, Download MIUI Flash Tool and unzip it, run XiaoMiFlash.exe. At the top line, find DRIVER, install all DRIVERS.
IF YOU FACE LOG FILE ERROR,
SOLUTION: JUST CREATE A FOLDER NAMED "log" in the same directory. DONE, YOUR DRIVER WILL BE INSTALLED, CLICK YES EVERY TIME, THEN CONNECT YOUR PHONE WITH MIUI UNLOCK TOOL AND CLICK REFRESH.
your device will be shown in "batch_unlock" in sha Allah. Click unlock. Remember, your phone will loose all data, just full factory reset.
8. after 99% it will show "unlock sign" at the top of your phone, and your phone will reboot, just let it reboot. It will take at best 12 minutes to reboot. Don't worry, seat tight, watch a YouTube Video of Dr. Zakir Naik or Ahmed Deedat Sir <3.9. setup your phone as if it's a new device. (it is necessary, because after this, we will flash recovery and root your phone, because it is really important to take a backup of your original "PERSIST.IMG" . it is possible for rooted device only. (though it can be done through recovery, but from magisk, it's the best way and safest).10. you can restore all backup from your pc now. (not necessary, if you want to change ROM)
Step Number 03: Install ADB (PC) & TWRP RECOVERY (Android)STEPS:
download latest SDK from OFFICIAL WEBSITE.
2. name of the download will be "platform-tools_r31.0.2-windows.zip" unzip it in DESKTOP (IMPORTANT). it's name will be "platform-tools", open it. (ADB COMMAND WILL RUN ONLY IN THIS FOLDER.
ALTERNATIVE ADB: you can also do it by one click adb installer, just install the file, and cmd will work at any position. File is given in the telegram, in my .rar file. But sometimes it shows problem, adb command is not recognized by the windows. then, above platform tools folder is useful as it always works.
3. downlead latest TWRP specific for your device from HERE. website guide: >find your device name> device model> Download Links > click either "Primary (Americas)" or "Primary (Europe)" or you can download them from XDA too (XDA process: search in google "TWRP for MI 9 se (your specific device with model number, not Mi9SE) XDA" then, go to the thread, below you will find GITHUB or any other download link, go there and you can download it from there.
4. (YOU CAN IGONORE THIS STEP, LET ME KNOW IF YOU FACED ANY PROBLEM, THOUGH YOU SHOULDN'T) rename the twrp file to twrp.img (not necessary though, check if your device extension is hidden or not, if hidden, you will not see any extension after any file, in that case, you can just rename "twrp" because img extention is already there and it's hidden. How to check hidden extention: in that folder, go to view at the top of the screen of that folder, (at beginning - beside cross, minimize then click "view"> click "option" in one row down, at extreme right side of it > click "view"> in downwards, untick "hide extensions for known file type"> click "apply">click "ok" then close it.)
5. keep the "twrp.img" (the file you downloaded, no need to rename, .img will show depending on unhidden condition) in the "platform tools" folder.
6. now go to "platform tools" folder. it's better to keep the folder in "desktop". go to the folder address, it is above the "Name, Date Modified, Type, Size" row, where it is written all the folders name that you have clicked to come to this folder. Now, click on the folder address, write "cmd", hit enter.
7. now connect your phone making sure "USB DEBUGGING IS STILL ON" because after unlocking bootloader, it will automatically be set to OFF.
write these commands: (after each command hit enter)
adb devices (it will show your device number if it is connected properly, if shows unauthorized, g0 to your phones home screen, disconnect and connect the usb again, in cmd write adb devices, a permission will pop up in your phone at bottom, not in notifications, click YES, your device will be authorized)
adb reboot bootloader (it will take you to fastboot mood instantly)
fastboot devices (it will show your device number it it is connected properly, to make sure it is still connected)
fastboot flash recovery (give space after recovery, then drag the twrp.img file here)
fastboot boot (give space after boot, then drag the twrp.img file here, your phone will boot into recovery.) ALTERNATIVE TO THIS STEP: fastboot reboot (it will reboot, but stop it instanlty by holding "power and volum up button", it is a must, it will take you to twrp manu, if you don't go now, later twrp will be removed by your phone)
AND OF COURSE, YOU HAVE TO ROOT YOUR PHONE RIGHT NOW, EVEN IF YOU DON'T WANT IT, CAUSE IF YOU DON'T, YOUR PHONE WILL REMOVE TWRP AS YOUR RECOVERY.
8. you will see twrp screen, then asking you "to keep system files as read only or swipe to allow modification, tick in DON'T SHOW AGAIN AND SWIPE TO ALLOW MODIFICATION". Then it will ask for a password to decrypt your phone, give the password to decrypt your phone. (to learn about encryption decryption, go to step number 4.3).
IF YOU FACE BOOTLOOP OR ANY OTHER ISSUE LIKE TWRP RECOVERY IS NOT STARTING AS IT SUPPOSED TO:
Again, go to fastboot mood by pressing power + volume down button. Download this vbmeta file. Go to platform tools > cmd > type
fastboot --disable-verity --disable-verification flash vbmeta (space, then drag the vbmeta file and hit enter, then follow step number 3.7
(3 is step number, 7 is the point number under step number 3)
Step Number 04: Install MagiskSTEPS:
1. you should stay in TWRP manu from the last step of STEP NUMBER 3 and your phone is connected with your computer via USB.
2. In your computer, download MAGISK FROM OFFICIAL GITHUB PAGE . Copy the magisk.apk and paste it twice in the same folder, now you have three magisk apk, rename the second one removing the "copy from name and just add .zip in stead of .apk at last. Rename the third one as this: "uninstaller.zip"
3. Now listen carefully, this is very important part of this topic:
your phone has two state: a. encrypted b. decrypted
a. IF ENCRYPTED AND CAN'T BE DECRYPTED THROUGH TWRP, that is TWRP IS NOT ASKING PASSWORD AT THE BEGINNING TO DECRYPT YOUR PHONE, THEN: some china rom's security is so encrypted, LIKE MY MI9SE, THAT TWRP CAN'T DECRYPT IT, EVERYTIME I HAVE TO RESET THE PHONE TO DECRYPT, IN THIS CASE ,YOU CAN'T ACCESS YOUR PHONE'S INTERNAL STORAGE NEITHER FROM TWRP NOR FROM PC (TWRP ACTS AS MTP, MEDIA TRANSFER PROTOCOL, MEANING YOU CAN TRANSFER FILE BETWEEN PHONE AND ANDROID IN RECOVERY MOOD), SO YOU CAN'T ACCESS YOUR INTERNAL STORAGE, YOU CAN'T INSTALL MAGISK. HERE, PENDRIVE WITH OTG COMES HANDY. Disconnect your phone Keep those three files in pendrive and connect it in OTG with your phone. go to twrp > install > select storage at bottom > select pendrive > select magisk.zip > swipe to flash. CONGRATULATIONS, YOUR PHONE IS ROOTED.
b. IF YOUR PHONE IS DECRYPTED BY TWRP AFTER GIVING PASSWORD:
Copy those three magisk file from your computer and drop it in your phones internal storage. go to twrp > install > select magisk.zip > swipe to flash. CONGRATULATIONS, YOUR PHONE IS ROOTED.
4. Reboot Your Phone (If your phone is bootlooped, which never happened to anyone I know, still for safety, again go to recovery by holding POWER + VOLUME UP BUTTON. go to twrp > install > select uninstaller.zip > swipe to flash. This will uninstall magisk from your phone and then reboot to system, your phone will reboot normally)
5. A Magisk app will be shown among your apps which is not like magisk logo. Don't touch it, Goto file manager, find those three magisk files, one file is the original magisk.apk file you downloaded, install it normally like any other app.
6. CONGRATULATIONS, YOUR PHONE IS COMPLETELY ROOTED.
Step Number 05: Backing up your PERSIST.IMG (MOST IMPORTANT)STEPS:
You will know from my other threads about what is persist partition of your phone. But let's just back it up now without knowing it. Copy it to your computer, cloud so that you never loose it.
Assuming you still have your phone connected through usb to the computer.
Install TERMUX from playstore or from HERE if you don't have play store.
in termux, type su to obtain root permission. A pop up will be shown to grant root permission, if it doesn't work, leave termux app, go to magisk app, at bottom, you will be 4 options, click the second one, you will see this screen.
grant super user permission for termux from here.
4. again go to termux, type this:
su (hit enter)
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img (hit enter)
5. your persist.img is backed up in your internal storage.
6. you can transfer it to pc manually or
use this process because it is relatively safe, though I never found any difference,
go to platform tools in cmd, type this:
adb pull /sdcard/persist.img D:\
it will take around 10 seconds, you will find the file persist.img in your PC's D drive folder, whatever the name is, the next folder to C drive, okay? Copy the persist.img wherever you want to keep it. I am again saying, it's not mandatory to do it in this way, just do normal copy paste from your phone's internal storage to your PC, it will do the work.
THANK YOU GUYS FOR READING IT ATTENTIVELY, FROM TOP TO BOTTOM, AND IF YOU DIDN'T, WHAT CAN I SAY. IT TOOK MORE THAN 30 DAYS TO ACQUIRE ALL THESE KNOWLEDGE AND YOU ARE GETTING IT WITHOUT ANY EFFORT, FREE, WHAT MORE DO YOU WANT?
My Other Threads according to "how should you read them" serial:
1. MIUI 12.5 Chinese ROM Google PlayStore Stopped Working
2. MIUI Unlocking Bootloader, Flashing Recovery & Rooting Process (This Thread)
3. Android Terminology You Must Know Before Toying with Your Android
4. ROM Naming & CUSTOM ROM, AOSP ROM, TREBLE ROM, GSI ROM, PORTED ROM
Click to expand...
Click to collapse
I have redmi k40 bootloader locked and stuck on fastboot mode and can't unlock it through mi unlock tool so any solution for that problem beside edl ? And if I go with edl which flashing tool i will use ??
Hussein Gbr said:
I have redmi k40 bootloader locked and stuck on fastboot mode and can't unlock it through mi unlock tool so any solution for that problem beside edl ? And if I go with edl which flashing tool i will use ??
Click to expand...
Click to collapse
have you flashed any rom? or flashed anything? if you haven't, just restart your phn using power button. and if you have flashed anything already, how on earth you did it without unlocking your bootloader?
shafi1885 said:
have you flashed any rom? or flashed anything? if you haven't, just restart your phn using power button. and if you have flashed anything already, how on earth you did it without unlocking your bootloader?
Click to expand...
Click to collapse
My bootloader was unlocked but when i try to use mi flash tool by mistake or by default flash and lock bootloader option with there and the flash didnt go through in last second
Is there a way to unlock the phone if it only turns on in fastboot mode and is not associated with a xiaomi account?
Hello there, I would like to contribute to this tutorial if you agree
There is a way for people that have encrypted storage and no usb otg pendrive:
Step 4.3:
a-alternative. If encrypted, but no OTG Pendrive at your disposal:
You still can use the adb push command to send your Magisk folder into a decrypted part of your phone’s root folder. You are going to use your phone “/tmp” folder.
“/tmp” folder is suitable for temporary files just as our files (We will not need these files anymore after this tutorial). There is no risk to add files into this folder while it is not encrypted but do not delete any files already present into your /tmp folder!
1.Copy your Magisk folder containing your three Magisk files into the Plateform-tool folder:
2.Then in the cmd execute: adb push [replace_brackets_by_your_Magisk_folder_address_location] /tmp
3.Your Magisk folder should be now copied into your /tmp folder
4.twrp > install > select tmp/magisk.zip > swipe to flash. CONGRATULATIONS, YOUR PHONE IS ROOTED.
4.5-alternative. (This step only for those that processed through the “a-alternative” step) After rebooting your phone, you might have no chance to access the Magisk folder you’ve pushed earlier into the /tmp folder. However, now you have booted into your MIUI usual OS, you can copy the Magisk folder again into your internal storage using the classical drag and drop thanks to MTP protocol, to continue through this tutorial.
Hope this will help