Please Help! stuck on fastboot loop, cant flash rom??? - Xiaomi Poco F1 Questions & Answers

So I've been messing around, i rooted my poco f1, i insalled twrp etc... i was add Viper4 FX module in Magisk and when i removed it then hit reboot, my phone has been in a loop going to fastboot all the time. I want to just flash a fresh copy of miui to it and start from scratch again but im getting the error on MiFlash tool "error:fastboot: error: cannot load *insert directory location here*: No such file or directory" see attached image.
I have installed all the drivers listed below:
Qualcomm_USB_Driver_v1.0
Universal ADB Driver v6.0
android_winusb.inf
Please someone help. I've tried everything i can think of, including trying command: fastboot format:ext4 userdata (this helped me once before but it is still stuck in fastboot loop.
Please ask me for anything else you may require i.e. screenshots etc...
If you wish to communicate directly and guide me through fixing the issue quicker, I am available on Discord, DM me for my username.

irnbru95 said:
So I've been messing around, i rooted my poco f1, i insalled twrp etc... i was add Viper4 FX module in Magisk and when i removed it then hit reboot, my phone has been in a loop going to fastboot all the time. I want to just flash a fresh copy of miui to it and start from scratch again but im getting the error on MiFlash tool "error:fastboot: error: cannot load *insert directory location here*: No such file or directory" see attached image.
I have installed all the drivers listed below:
Qualcomm_USB_Driver_v1.0
Universal ADB Driver v6.0
android_winusb.inf
Please someone help. I've tried everything i can think of, including trying command: fastboot format:ext4 userdata (this helped me once before but it is still stuck in fastboot loop.
Please ask me for anything else you may require i.e. screenshots etc...
If you wish to communicate directly and guide me through fixing the issue quicker, I am available on Discord, DM me for my username.
Click to expand...
Click to collapse
Rename Folders and remember don't use spaces in any of the Folder Name. Path I'm looking at screenshot you have a Folder "Poco Stuff" it has a space in it. Remove spaces in Folders and Flash it.

Related

[MOD][Custom Boot Animation]LG G Watch Custom Boot Animation

Today I am going to show you how to install a custom boot animation onto your LG G Watch device! Assuming the principles of the Android Wear file system are the same across all devices, it should *technically* work on the Moto 360 and Gear Live as well.
This is my first tutorial, so I do apologize if I don't go in depth enough in some parts, or am unclear. Please let me know and I will explain anything that does not make sense!
IMPORTANT!!!!!
The bootanimation MUST have the filename of (without quotes) "bootanimation.zip" otherwise it will not work
Getting Started
1) First you must make sure that your device is rooted with a custom recovery.
Rooting - https://www.youtube.com/watch?v=shGqwLp4teE
Custom Recovery - http://forum.xda-developers.com/g-watch/development/recovery-clockworkmod-recovery-lg-g-t2833877
2) Secondly you need to have adb installed and working, as well as the usb drivers for your device
Tutorial - http://forum.xda-developers.com/showthread.php?t=2588979
2) Once you make sure that you have all of that set up, and are comfortable with adb transfer, we can get started
Installation
1) To start with you must have the zip of whichever boot animation you desire to have on your watch, and for convenience, place it in the same folder that your adb files are in (for me it was C:\adb)
2) Having your watch connected to your computer and booted into your recovery, go ahead and open a command prompt and navigate to the folder you have your adb installation in (C:\adb)
3) From here you mist make sure that System is mounted in your recovery, then on your computer type in (without quotes) "adb push C:\adb\bootanimation.zip /system/media"
that's it!
If this helped you, please let me know! And let me know if there is anything you need help with.
(I attached a picture of my device booting up)
Credits
Google is my friend, giving me these amazing devices and awesome platforms! The adb transfer service made the mod possible.
Hours spent figuring this out and searching files and folders to make sure everything was in order, I take credit for having the first tutorial on changing the LG G Watch boot animation, although if I am wrong I will promptly change this. Thank you XDA-Developers for all of your help
More information please
what do you want to know?
How are you writing to the system, I have tried this over and over and it won't work.
So to start off simply, you need to have your watch connected to your computer, boot into the bootloader, and install a custom recovery. Then after that boot into the recovery and you can copy files over. Have you gotten all of that done before attempting this?
I have done everything like in the op , that's why I ask.
I'm not sure why it's not working for you then. What are you getting when you try to write over the files in command prompt?
It is saying it's a read only system, and I have even tried from root shell.
Okay yeah I was having an issue with that too. For some reason if I just kept trying, it eventually worked I know how it sounds, but that's my solution for now! Try going back to the bootloader and into recovery again, and you can try transferring the file while in the file manager, or on the recovery home. Different things might yield a different result! I apologize if I'm not helping
Also go to device manager and make sure that when in the bootloader and recovery it has the Google driver installed and not a yellow triangle without a driver
One more thing, when in the recovery you must check and see if System is mounted. It helped for me to make sure it was checked under Mount (TWRP).
Ok bro thanks, mounting system worked, now gotta edit all of my images.
Yeha my bad man! Didn't even think about that, I had to spend a lot of time tweaking to get it working I'll add it to the guide. Glad you got it
Also once you mount the system you can push the zip directly to the /system/media/, no need to manually move it after that. Now it's time to start pumping out custom boot animations....
Can you post the stock desc.txt for me?
cbrown245 said:
Can you post the stock desc.txt for me?
Click to expand...
Click to collapse
for the stock boot logo i did not have a backup unofrutnately.... but i did go to the thread originally outlining pulling the animation off the watch! copied this from their dump desc.txt
1080 1080 24p 1 0 part0 p 0 0 part1
and i am attaching the zip for my animation im using as well if that helps at all.
hey man I have a couple questions about this procedure. I know this thread is not current and that may be my problem. adb is not recognized in recovery for me, it returns no device found. also I was curious why you put your path in the command if the zip is in the folder with adb? tia.
also I reeaallly want that kate upton bootani, way cool!!!

Gapps/TWRP/CWM on china tablet

Hello,
I recently got a hand on Yuntab K107, ARM MT8752, Android 5.12 Bootloader unlocked. Everything worked fine until factory reset, after that Google play store and other gapps stopped working (play store checking info, then goes black and freezes for a while).
Tablet is rooted from factory by kingroot, I tried finding TWRP/CWM for this tablet to reflash gapps but I failed. I also tried Magic TWRP installer and MTK droid tools. Magic TWRP installer acts like it's working but no results. MTK droid tools refuses to find my device even if i tried every driver possible and cleared wrong drivers with USBDeview.
I also tried flashing gapps manually thru root explorer by unpacking gapps files and matching system file structure also no luck.
Then I backed up the stock recovery and tried flashing few custom TWRP's that some post suggested may work (you guessed it - it didn't work) It just hangs on the first booting screen then it surrenders after a while and reboots back into android.
Do you know about any TWRP/CWM that might work on this tablet or any other way to repair gapps if recovery is not necessary?
Thanks
I also rooted it with kingroot but havnt any custom recovery but i doing some experiment. Let se what it will result
I should be able to compile TWRP for you
I have one of these K107 tablets but it is running Android 7 and so far I have been unable to root it. Because you guys have root you should be able to download adbd Insecure by chainfire and follow this guide to Fetch the boot.img file by Extracting the boot.img directly from the device:
you will first have to determine the (sadly device-specific) path to the storage device where boot.img's content can be retrieved. I know two methods for this:
ls /dev/block/platform/*/by-name/ (where * covers yet another device-specific folder name, chances are it is the only directory below platform/), the exact name to search is also platform dependent but makes usual sense (some examples: boot, LNX (acronym for "Linux")). The files in this directory are actually symbolic links and some people bother to manually go to the target, but I recommend sticking with the higher level name based path which, while longer, remains less error prone. So you will end-up with a path like /dev/block/platform/sdhci-tegra.3/by-name/LNX.
On some (older?) devices, the right device could be found by investigating the output of cat /proc/mtd. If you see the device mtd2 associated to the "boot" label, then you will use the path /dev/mtd2.
Now:
From the phone's developer menu:
Enable debugging on your phone,
Allow root access to ADB (this step applies to phones running CynogenMod, other devices may require some potentially more complex procedure),
Connect it to your computer (and from there to the VM guest if you are running Android tools from within a virtual machine).
If this is not already done, I recommend to manually start the ADB server on the computer's side, this will allow you to directly validate the RSA key on device's side without affecting the behavior of the following ADB commands:
adb start-server
Then switch ADB in root mode:
adb root
Finally, you should be able to directly extract the boot.img file from the device using such command (the source and destination path and names are given as examples, adapt them to your needs and preferences):
adb pull /dev/block/platform/sdhci-tegra.3/by-name/LNX ./boot.img
The command will copy the whole partition, both used and free space, so don't be surprised that the resulting boot.img file will be larger than the original boot.img file coming with the stock ROM .zip file, the content itself remains similar.
Once the transfer is finished, disconnect the phone and don't forget to disable both debugging and root access from the developer menu.
Then upload the boot.img and I will build TWRP and test it on my tablet for you

[ROM] AmazeROM WOS2 for Pace v1.2_20180627 - firmware 2.6.2.0

- Simple and safe installer;
- Installs stock and offers to install Customization Package (optional);
- Can be used to flash other ROMs that use "flash_rom.sh";
- Can be used to fix bricked devices with unlocked bootloader.
DISCLAIMER: You are using the provided files by your own risk, although I have tested the installation I am not responsible for any damage or data lost if you decide to use them.
Click to expand...
Click to collapse
Compatible with macOS/Linux (tested on High Sierra and Ubuntu 16.04) or Windows. Requires unlocked bootloader!
The script will check for requirements, and will only continue if everything is fine. If you are on Windows, make sure the drivers are working correctly before starting: open Device Manager and put watch in fastboot mode then check if it is detected correctly, or you can use the provided "checkdrivers_win.cmd" to do this and check if watch's bootloader is unlocked. If you get any errors then probably drivers aren't installed properly, and you should fix this before starting.
PS: If you are on Windows, make sure fastboot driver is working properly using the directions above. If the driver seems to be installed correctly (no question mark on the device) then try disabling or uninstalling your antivirus temporary. Avast is known to cause problems with USB drivers.
Current version installs firmware 2.6.2.0 (WOS2 = Watch OS 2.0) on Pace, and can be used to fix a bricked watch, simply put it in fastboot mode manually *before* starting the script. Make sure you try to do this with a Pace watch or provide the correct ROM in the "rom" folder, otherwise it will brick your device.
PS: During the ROM installation, when watch is in Recovery Mode, it will display a triangle with an exclamation mark and the text "no command", it's expected! Simply follow the instructions provided by the script.
- How to run on Linux
Go to the folder with the uncompressed files in terminal and run "sudo bash amazeflash.command" (Linux requires root access to fastboot), then follow instructions.
- How to run on macOS
Go to the folder with the uncompressed files in Terminal and run "bash amazeflash.command", or simply double-click "amazeflash.command" then follow instructions. PS: Decompress the 7z file with Keka or TheUnarchiver to preserve file permissions.
- How to run on Windows
Go to the folder with the uncompressed files in command prompt and run "amazeflash_win.cmd" or simply double-click "amazeflash_win.cmd" (you may not see the file extension in some cases), then follow instructions.
Use the same procedure if you want to run the custom package installation script after you successfully flashed the ROM, it will prompt to install modded files or revert to stock versions. Be aware the reverting to stock version may not work if you want to apply OTA to update later, it's recommended that you flash stock version again and don't apply the Customization Package.
For more info, please refer to the included "readme.txt" file.
Some remarks:
- Customization Package includes WearSettings, NewWearSport and HuamiWatchFaces with improved support and voice prompts in English.
- If watch is *not* on firmware 2.x yet (it means *any* 1.x firmware) then probably you want to do a factory reset first and then use the installer (it works even if watch shows QR code).
- If watch already have firmware 2.x, then no need to factory reset first a priori...
- On stock ROM in English, the "About" section in Settings causes it to crash, it works in Chinese and if the Customization Package is installed.
- After a Factory Reset, language will revert to Chinese, you can set it back to English with these adb commands (you can use copy and paste, a Windows batch script is provided too):
Code:
adb wait-for-device
adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country US
adb reboot
You can buy me a coffee or cheesecake (please, no beers ), Paypal address for donations: lfomartins[at]aim.com
Or most common cryptocoins here: https://freewallet.org/id/87331be5
PS: there is no fee free option to transfer money to my country, you must use "pay for goods and services". But don't worry, you will only be charged for the amount you send. Thanks!
This was only possible because of the modded recovery image provided by @Neuer_User:
https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
In the above post you can find details on how to put Pace or Stratos manually in fastboot mode. It's tricky and very hard to do, but it works.
*************************
Latest Version v1.2 - firmware 2.6.2.0
- Installer will NOT run anymore if root is detected (this can happen if watch has other custom ROMs) and only install via fastboot/recovery (safer).
- amazefls.log now won't be erased every time you run the installer script, but store all flash history for debugging.
Download link:
https://mega.nz/#!9OJ0mIqA!QgnX9f675VbZI9ECx__ScnHtgHTAdRa1fldWtZdVR9U
SHA1SUM: E941FD472C626872707C06065177DC728BA64FB6
*************************
Old versions
v1.1 - * Link removed, please use v1.2 *
SHA1SUM: 0CB3FB554A397B53C1E739586E98C2FF8C1FCE0C
- Updated to firmware 2.6.2.0
- Updated support for EN
Firmware Changelog (translated using Google Translator)
- Added World Cup event reminder function, need to upgrade to the latest mobile phone App, and set a reminder in the live World Cup page
- Added virtual rabbit mode to support running, indoor running, outdoor riding, cross-country running, open in Sports Settings > Motion Control
- Added Heart Rate Interval to Reserve Heart Rate Mode, App> My> My Info> Heart Rate Interval Settings
- Added data items such as sectioning speed and section speed to support running, trail running, walking, outdoor cycling and other sports
- Occurrence of abnormal heart rate output after optimising Bluetooth heartbeat disconnection
- Repair the lock screen second hand display of the third party dial
- Fixed several bugs
Thanks to @Saratoga79 for sharing the system dump! You rock, dude!
v1.01 - * Link removed, please use v1.2 *
SHA1SUM: 47D0777F599586A63D293E592B6770D7FE77982A
- Fixed AmazeCustom installer for both Win and Mac when run separately;
- Moved all scripts to main folder for easier access and simplified maintenance;
- Moved all Windows binaries to pgm folder to simplify future updates;
- Added Windows script to set language to EN (needed after a factory reset/unpair).
v1.0 - * Link removed, please use v1.2 *
SHA1SUM: 64205E4D683B388E8C087FCF49B20FE6FDEA8235
- Initial Release
Thanks to @ingraynieris and @chincheang for testing and @1immortal for support.
Manual Installation
Requirements
- Pace watch (A1602 or A1612);
- Unlocked booloader (unlockamazfit.com - read carefully the warning, doing this will void watch's warranty!);
- adb, fastboot and drivers installed correctly;
- 40% battery or more, read English and pay attention!
******************************************
DISCLAIMER: You are using the provided guide by your own risk, although I have tested the commands I am not responsible for any damage or data lost if you decide to use it.
******************************************
This is an installation guide, if you have never used adb or fastboot, then please don't try to do this. Commands should be typed in terminal/prompt/whatever you use to do adb commands.
In the end of this guide, you should have a watch with stock WOS2, so OTAs should work. Do not modify any system files if you want to apply future OTA updates, not even get root access, it may break stock updates.
Unpack the compressed 7zip file from the link at some place you have at least 1GB of free space and adb/fastboot access, then change to this directory to begin. Commands below are for Windows, macOS and Linux users should change the backslash ('\') to normal slash ('/'), hit ENTER/RETURN after each line (duh!).
If you are trying to fix a bricked devices, make sure it's in fastboot mode and that the computer detects the device, then start from step #3.
1. Connect the watch to computer using USB cable, then:
Code:
adb devices
2. If you see your device listed, type:
Code:
adb shell reboot bootloader
3. Check if device is recognized correctly (on Windows, open Device Manager and check if you see a device in fastboot mode or similar), then type:
Code:
fastboot getvar all
4. If you see "unlocked: yes", you can continue. Reboot into temporary root/Recovery:
Code:
fastboot boot Amazfit-mod-recovery.img
5. Watch should show a triangle with an exclamation mark, it's in Recovey mode and it's normal, do not panic! Then make sure you have root now:
Code:
adb root
6. Then push files to watch:
Code:
adb push rom\boot.img /data/media/0/
adb push rom\md5s.txt /data/media/0/
adb push rom\system.img /data/media/0/
adb push rom\flash_rom.sh /data/media/0/
If it fails, try:
Code:
adb push rom\boot.img /sdcard/
adb push rom\md5s.txt /sdcard/
adb push rom\system.img /sdcard/
adb push rom\flash_rom.sh /sdcard/
7. Take a deep breath and then (after the first command, you should see a "#" only, indicating root prompt):
Code:
adb shell
cd /data/media/0
sh flash_rom.sh
or use "cd /sdcard" if you have copied the files to this directory instead.
8. Wait until it says "Finished", then type:
Code:
reboot
9. To set English language after booting (stock CN WOS2 has some bugs, i.e. About in settings crash, some watchfaces show Chinese names when screen is locked, etc):
Code:
adb wait-for-device
adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country US
adb reboot
Thanks for your rom, have seen it on fb to great work!
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
Thank you for your great work!
Is it possible to install custom GPS.conf files? Will it break OTA updates?
xaametz said:
Thank you for your great work!
Is it possible to install custom GPS.conf files? Will it break OTA updates?
Click to expand...
Click to collapse
You're welcome. I am glad you like it.
Yes, you can install a custom gps.conf the same way you do with any other ROM (root, remount, push, fix permissions, reboot), but my personal experience is that GPS is much better on 2.6.1.0, no need to change anything. I cannot guarantee it will not break OTA, may or may not work as it's not a file that is used in stock firmware, but any modification to /system can cause problems. Anyway, with AmazeROM you can always flash stock later if you need it for future updates.
lfom said:
You're welcome. I am glad you like it.
Yes, you can install a custom gps.conf the same way you do with any other ROM (root, remount, push, fix permissions, reboot), but my personal experience is that GPS is much better on 2.6.1.0, no need to change anything. I cannot guarantee it will not break OTA, may or may not work as it's not a file that is used in stock firmware, but any modification to /system can cause problems. Anyway, with AmazeROM you can always flash stock later if you need it for future updates.
Click to expand...
Click to collapse
Thank you. I'll try it without custom config.
Enviado desde mi STF-L09 mediante Tapatalk
Hi,
Minor problem with the script that installs the customised apk's: You seem to have forgotten to replace "adb" with "$adbcmd" and "fastboot" with "$fbcmd".
Thanks for all the effort you have put into the scripts!
R.
Eeg.
superbert1969 said:
Hi,
Minor problem with the script that installs the customised apk's: You seem to have forgotten to replace "adb" with "$adbcmd" and "fastboot" with "$fbcmd".
Thanks for all the effort you have put into the scripts!
R.
Eeg.
Click to expand...
Click to collapse
True, thanks for reporting. There is a problem in the Windows installer as well, it doesn't work if you run it without command line arguments, it will be fixed in the next release.
I just made some quick an dirty adaptations in order to get the custom script running. Unfortunately, I'm now stuck with an unwilling fastboot (maybe it's because I'm still on "El Capitan" --> I'm considering upgrading, but first have to make a recent backup).
Though-luck for now, I'm stuck with a watch that has some Chinese notifications (at least for the time being).
superbert1969 said:
I just made some quick an dirty adaptations in order to get the custom script running. Unfortunately, I'm now stuck with an unwilling fastboot (maybe it's because I'm still on "El Capitan" --> I'm considering upgrading, but first have to make a recent backup).
Though-luck for now, I'm stuck with a watch that has some Chinese notifications (at least for the time being).
Click to expand...
Click to collapse
I have updated the installers, please check them. I am sorry for the trouble.
Hi,
You don't have to excuse yourself at all...
I just tried the new version, and it works perfectly fine now (even on my Mac).
I really appreciate the effort you're putting into AmazeROM
@lfom: HELP!
Unfortunately this installer crashs my Pace.
In the past I have used PACEfied and PACEficator custom ROM and the installers works always perfect.
But this one fails in some steps but continues and ends with an "ok" and now I see only the "A" logo before the boot animation.
Attached the whole CMD output.
I hope the Pace is not bricked. ADB devices shows the Pace, but no other commands (e.g. "fastboot reboot bootloader") are working.
Got the same problem, it crashed my PACE too, was running PACEficator Project before, now it keep having luncher has stopped error.
Installer stopped on fastboot and unable to boot to recovery anymore
fastboot boot Amazfit-mod-recovery.img
downloading 'boot.img'...
FAILED (remote: ED: The command is not allowed.)
finished. total time: 0.012s
Edit: after search the forums, I unpair and re-pair my PACE and the watch is working now. however, I am not sure should I still install this ROM on my watch anymore.
@Diginix @thomsontam Did you check you have an unlocked bootloader? If yes, you should be able to put watch in fastboot mode and flash the ROM again. It seems that the installer detected root and went ahead with the installation, but the watch crashed and it did not finish. If it's locked and you have a valid serial number, you should be able to unlock it using the same code as before. If not, please contact me via Telegram: http://t.me/lfomartins
@lfom
I had an unlocked bootloader until PACEficator 2.6.0.12. I didn't checked it after update to PACEficator 2.6.1.0
Root was definitely existing and working.
I have my serial nr. and the unlock code.
But what commands should I try now?
This doesn't work:
adb shell reboot bootloader
- exec '/system/bin/sh' failed: No such file or directory (2) -
using port=5555
Click to expand...
Click to collapse
My backlight is always on and shows the Amazfit "A". I hope the battery is charging.
@Diginix You have broken file system. You should be able to put the watch in fastboot manually. It is very hard to achieve but it works. Then check if bootloader is unlocked and try to flash it again. If you have problems, contact me on Telegram.
I have no Telegram and need ready for use commands please.
Your checkdrivers_win.cmd doesn't provide any hope.
btw: adb+fastboot was proper installed and works in the past perfect with the installer of other custom roms.
Edit: I will try this steps.
Edit2: My Pace can't be turn off as in the youtube video is shown. It always shows the "A" and backlight is on.
As it seems fastboot isn't reachable. But I will try some different delays at pressing the button and plugin it on PC.
@Diginix checkdrivers_win.cmd is useless now with a bricked device. You can turn the watch off by pressing and holding the button. Keep the watch connected to the computer and then press button again to turn it on, then count up to 4 (more or less) after the screen goes on again and release the button. If you see the battery icon you have released the button too early, if you see the A logo then you released too late. You have to release at the exact time to show the screen with Fastboot and ForceErase, then press button briefly once to enter fastboot. Keep the watch connected to the computer all the time, it's easier this way.
Now I'm in fastboot!
But "fastboot devices" doesn't prompt any device.
What to do with your ROM files?
Hi!
I installed and I'm using adb and fastboot on Mac, it works perfectly adb, but with fastboot it does not detect the clock. But if I try on my OnePlus 6, I detect both adb and fastboot the Mac. How can I do? Thank you

Doogee N20 TWRP

How I can install twrp and flash gsi rom on Doogee N20?
I found this but I'm doesnt know Russian: pda.ru/forum/index.php?showtopic=955032&st=1220#entry89836105 (I cant post URL because I'm new user, so I delete the "4" from "4pda")
Sorry for my bad English.
צבי זלצברג said:
How I can install twrp and flash gsi rom on Doogee N20?
I found this but I'm doesnt know Russian: pda.ru/forum/index.php?showtopic=955032&st=1220#entry89836105 (I cant post URL because I'm new user, so I delete the "4" from "4pda")
Click to expand...
Click to collapse
That's the Google translation:
A little instruction on how to get RooT. And so, everything that you do, as always, is at your own peril and risk! All data is erased when unlocked! Make BACKUP !!! Is always!!!! I. Unlocking Boorloder-a (required for flashing the phone and everything connected with it): 1. Go to settings -> system -> About phone -> Build number (7 clicks) (Congratulations !!!! You are a developer!) < - About phone -> For developers: Enable USB debugging and OEM unlocking. 2. We connect the phone to the computer and install the ADB usb driver (on the Internet), a connection request should appear on the phone, you need to allow it. 3. Extract files from the N20_utils.rar archive (10.87 MB) (preferably not very far, the root of the disk or the created folder N20 will be there). Go to the Unlocked Bootloader folder and run the bat file, the phone will reboot and display the request "unlock? Yes / no" rocker up - yes / rocker down - no. Naturally, you need to press the volume up, otherwise there were so many actions)) 4. Congratulations! Now, with each reboot, you will have an Orange state (5-second inscription), and the ability to do whatever you want with your phone. II. We sew! 1. For the lazy (who value their time). Download the SP Flash tool (Internet), from the N20_utils.rar archive (10.87 MB) select MT6763_Android_scatter and boot_magisk_20 files for the boot partition, lk_pached for lk, etc. you can even twrp instead of native recovery. Turn off the phone, connect it to the computer and click Download in the SP Flash programs. After the OK circle appears, disconnect and reconnect the cable (easier than a forced reboot). We turn on the phone and put the magisk manager (internet). Congratulations!!! You have a root and no Orange State label! 2. Who wants more and himself: phone to computer -> go to the Unlocked Bootloader folder -> run CMD -> write "fastboot flash recovery" put a space and move the TWRP file with the mouse to the window (fast path to the file) and press ENTER -> reboot the phone to fastboot. Congratulations!!! you have TWRP. Boot into TWRP, skip the encrypted DATE message, go to formatting and format the DATE. Go to mount and connect MTP. A phone will appear on my computer, we drop the files DisableForceEncryption_Treble (disable date encryption), orange_state_disabler_v0.3 (remove orange_state) and magisk.zip (internet) into the memory section. In TWRP, click install all this and rejoice! 3. Who has nothing to do at all: go to the forum thread Development and porting of GSI firmware (Post bullik01 # 71222655) and try what catches your eye. Not all are loaded, but .... (although we do not seem to have an A / B structure, but only "arm64 A / B" were launched) PS: look for additional information here on the forum and for brotherly devices UMiDIGI A5 Pro - Firmware ( Post Xakep1993 # 86772223) Attached files recovery-TWRP_3.3-20191015-1714.img (22.81 MB) DisableForceEncryption_Treble.zip (4.24 MB)
jwoegerbauer said:
That's the Google translation:
A little instruction on how to get RooT. And so, everything that you do, as always, is at your own peril and risk! All data is erased when unlocked! Make BACKUP !!! Is always!!!! I. Unlocking Boorloder-a (required for flashing the phone and everything connected with it): 1. Go to settings -> system -> About phone -> Build number (7 clicks) (Congratulations !!!! You are a developer!) < - About phone -> For developers: Enable USB debugging and OEM unlocking. 2. We connect the phone to the computer and install the ADB usb driver (on the Internet), a connection request should appear on the phone, you need to allow it. 3. Extract files from the N20_utils.rar archive (10.87 MB) (preferably not very far, the root of the disk or the created folder N20 will be there). Go to the Unlocked Bootloader folder and run the bat file, the phone will reboot and display the request "unlock? Yes / no" rocker up - yes / rocker down - no. Naturally, you need to press the volume up, otherwise there were so many actions)) 4. Congratulations! Now, with each reboot, you will have an Orange state (5-second inscription), and the ability to do whatever you want with your phone. II. We sew! 1. For the lazy (who value their time). Download the SP Flash tool (Internet), from the N20_utils.rar archive (10.87 MB) select MT6763_Android_scatter and boot_magisk_20 files for the boot partition, lk_pached for lk, etc. you can even twrp instead of native recovery. Turn off the phone, connect it to the computer and click Download in the SP Flash programs. After the OK circle appears, disconnect and reconnect the cable (easier than a forced reboot). We turn on the phone and put the magisk manager (internet). Congratulations!!! You have a root and no Orange State label! 2. Who wants more and himself: phone to computer -> go to the Unlocked Bootloader folder -> run CMD -> write "fastboot flash recovery" put a space and move the TWRP file with the mouse to the window (fast path to the file) and press ENTER -> reboot the phone to fastboot. Congratulations!!! you have TWRP. Boot into TWRP, skip the encrypted DATE message, go to formatting and format the DATE. Go to mount and connect MTP. A phone will appear on my computer, we drop the files DisableForceEncryption_Treble (disable date encryption), orange_state_disabler_v0.3 (remove orange_state) and magisk.zip (internet) into the memory section. In TWRP, click install all this and rejoice! 3. Who has nothing to do at all: go to the forum thread Development and porting of GSI firmware (Post bullik01 # 71222655) and try what catches your eye. Not all are loaded, but .... (although we do not seem to have an A / B structure, but only "arm64 A / B" were launched) PS: look for additional information here on the forum and for brotherly devices UMiDIGI A5 Pro - Firmware ( Post Xakep1993 # 86772223) Attached files recovery-TWRP_3.3-20191015-1714.img (22.81 MB) DisableForceEncryption_Treble.zip (4.24 MB)
Click to expand...
Click to collapse
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Good day
Had the same problem, (English not so good but I know you'll understand). What I did was just installing Corvus OS rom, the 11th version. It's been quite a while since i installed it.
Tried Lineage 18.1 and adding the smallest gapps available, but everytime i get code error 1. I guess it was the twrp 3.3 version i used cause some roms requer the latest TWRP versions. The lineage is installing just right nd can reboot to system with no hiccups.
None of Android 12 gsi versions has ever been able to installed. Cause when i try to install, i get the error of "file too large for the target partition. Tried everything from the net to increase the system partition to at-least 3gig. No success.....
Is anyone who can help to install android 12 even beta version will be ok for my N20 Doogee??
Thanx
flairepathos.info said:
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Click to expand...
Click to collapse
The file is in the forum. But to make your life easier here are the link.
https://drive.google.com/drive/folders/18B-srDVia_H4aDt7uvCDUxg2e4R5kVVY?usp=sharing The file is of type .exe and that extracts when you run on the pc, the problem is that I was suspicious about the virus so I threw the file in the total virus (if you don't know what it is, just search) and 6 programs pointed it out as malware but many others didn't find anything including karpersky and bit defender, there to make sure the files were there i renown they from .exe to .zip and I looked and the files really were there but as I don't want to take the risk I didn't extract and I didn't even try anything. The file that fix the encryption are inside doogee n20.exe, the guy said it will be in .exe and when you run it extracts the file in the C folder of the computer I recommend you to rename it from .exe to .zip because if the file have a virus you can screw your pc when running
Da-Judges said:
Good day
Had the same problem, (English not so good but I know you'll understand). What I did was just installing Corvus OS rom, the 11th version. It's been quite a while since i installed it.
Tried Lineage 18.1 and adding the smallest gapps available, but everytime i get code error 1. I guess it was the twrp 3.3 version i used cause some roms requer the latest TWRP versions. The lineage is installing just right nd can reboot to system with no hiccups.
None of Android 12 gsi versions has ever been able to installed. Cause when i try to install, i get the error of "file too large for the target partition. Tried everything from the net to increase the system partition to at-least 3gig. No success.....
Is anyone who can help to install android 12 even beta version will be ok for my N20 Doogee??
Thanx
Click to expand...
Click to collapse
you can use the pixel experience lite https://github.com/ponces/treble_build_pe/releases ( remenber the lite version, because is 2,5 gig) i try and instal in my phone and worked but i cant access my storage so i search and here are the solution https://forum.xda-developers.com/t/...loop-after-any-custom-rom-doogee-n20.4357313/ i dont try it but if you want here are the solution
flairepathos.info said:
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Click to expand...
Click to collapse
Hi, did you find N20_utils?

MIUI Unlocking Bootloader, Flashing Recovery & Rooting Process

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 Magisk​STEPS:
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 Magisk​STEPS:
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

Categories

Resources