Database Users

Wiley Fox Swift2+ Bootloader Unlock

It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead

I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.

Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.

Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.

thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable

I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.

SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll

Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip

"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553

Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?

got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)

Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?

bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery

Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now

bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .

I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|

When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.

My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse

bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.

After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818

New way to flash stock rom without miflash!! (easy way) will work on any mi device

I have developed this process by mistake
TRIED AND TESTED
Requirements -1)Download the miui 9 beta rom or stable rom (ie miui 8) from officical miui page.
It has to be fastboot rom
2)Download adb tools from androiddatahost
Procedure
*extract the rom file and then move the files from the image folder to Minimal ADB and Fastboot(which is located in c/program files)
*reboot ur phone into fasboot mode.
*open the command window in Minimal ADB and Fastboot folder and type the following commands
1) fastboot -w
2) fastboot flash system system.img
3) fastboot flash boot boot.img
4) fastboot flash recovery recovery.img
*after completing the above process type the command
5) fastboot oem lock ( it's optional this will lock ur bootloader)
6) fastboot reboot
THATS ALL ITS VERY EASY PROCESS:laugh:
AND WILL WORK ON ANY MI DEVICE WHEN EVER U WANT TO ROLL BACK TO STOCK ROM:good:
?If u want proof let me know in the comments

That re-locking bootloader step is 'optional', right?

lscambo13 said:
That re-locking bootloader step is 'optional', right?
Click to expand...
Click to collapse
Yes it depends upon u
Whether u want to remain in unlocked bootloader or u want to lock it?

Adi.s said:
Yes it depends upon u
Whether u want to remain in unlocked bootloader or u want to lock it
Click to expand...
Click to collapse
i guess you better add some explanation for that step just in case someone really did all the step without knowing it was optional
thank you for this thread, useful
---------- Post added at 02:17 PM ---------- Previous post was at 02:12 PM ----------
i think you have some typos on your last words too
cheers

Z17S (NX595J) Unlock Bootloader & TWRP

Hi, I'm new to this phone. Just got it 1 week ago. I tried to find any related information on the bootloader unlock and custom recovery, but it is very limited. I think maybe this phone is not well known. I would appreciate if someone can provide me the way to unlock bootloader, flash TWRP and roots. I can't live without magisk and viper4android. Thanks.

Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !

thanks

dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
Hi, I've tried numerous timed and it always won't pick up the command of unlocking bootloader. It always stay in the fastboot menu. I've toggled the 'OEM Unlock' function in the developer setting, as well as the USB debugging. Any idea why the device won't pick up that command?

Is it changing to unlock after you enter the command?
If so flash twrp then boot into recovery ...

dantonuci said:
Is it changing to unlock after you enter the command?
If so flash twrp then boot into recovery ...
Click to expand...
Click to collapse
Nope. It doesn't respond to the command in the fastboot. It just shows the fastboot menu. My adb is written 'waiting for device.... '.

Drivers , uninstall all other drivers and try please

dantonuci said:
Drivers , uninstall all other drivers and try please
Click to expand...
Click to collapse
Okay will try again

storytellerz said:
Okay will try again
Click to expand...
Click to collapse
I am also finding this message, what is its solution ???

the same recovery
dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
Hi there, when I flashed the recovery that is always the stock recovery, why?

vins84 said:
Hi there, when I flashed the recovery that is always the stock recovery, why?
Click to expand...
Click to collapse
Not sure what you're asking, did you want to flash TWRP or stock? I was just giving tutorial for how to install TWRP

dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
I'm having the problem. Unlock is not sticking to unlock. The unlock works and the flash works but as soon as you try and reboot into recovery it hangs at a blank screen no twrp. Console says waiting for device and stuck. next time I go into bootloader it says locked. The count is 3 for unlock count is there a limit? 7-6-18 Nubia Z17 NX591J WIn 10.

bmaz121 said:
I'm having the problem. Unlock is not sticking to unlock. The unlock works and the flash works but as soon as you try and reboot into recovery it hangs at a blank screen no twrp. Console says waiting for device and stuck. next time I go into bootloader it says locked. The count is 3 for unlock count is there a limit? 7-6-18 Nubia Z17 NX591J WIn 10.
Click to expand...
Click to collapse
Trouble shoot and experiment with the process it will work, even if it appears not locked after reboot

dantonuci said:
Trouble shoot and experiment with the process it will work, even if it appears not locked after reboot
Click to expand...
Click to collapse
I don't understand? Appears not locked? It is locked. Now I remember when I flashed my Star N997 the developer said that there is a unlock bit that has to be turned on in the process of unlocking. I think this may be the case here since it unlocks until a reboot. I am deep concerned that after a unlock count of 3 the phone will not boot anymore. Do you know anything about these things? Another thought is does the USB C need different drivers and should it be plugged into a USB 3.0 outlet?

TWRP will flash only when it's unlocked so even if it's saying it's locked go by what you can do with TWRP
---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------
I did it several times and never had a problem

i was looking for camera.apk file from Nubia Z17S phone from Stock ROM, can anyone upload it here..it should be located in system / app or app-pvt folder, you can copy using Root Explorer tool.
pls. let me know...

I'm having problems unlocking the bootloader. Has anyone got the proper TWRP for this phone? I can't find it. The one I have says FAILED (remote: Requested download size is more than max allowed). Thanks

hello links no longer works. Someone could give me back the TWRP and minimalb fastboot adb

For anyone's information, TWRP will not boot in recovery while the phone is being charged. Unplug first. You will just get a black screen.

i am also experiencing the same issue.. where can i find the drivers for this phone nx595j? or how do i uninstall the drivers for it?
---------- Post added at 01:21 AM ---------- Previous post was at 01:17 AM ----------
yo can somebody help me install a custom rom on my z17s via team viewer?? im willing to pay for your time

Xiaomi noob. Want to root. Need help to avoid breaking the phone

Hello everyone
I got my Mi 9T three weeks ago and I basically haven't used it because I couldn't transfer my backups so Im merely looking to root and install Titanium. The binding period for unlocking the bootloader should end tomorrow and I have a few question to avoid getting stuck on bootloop or break the phone
My device is Global 64gb MIUI 10.3.7.0 and update 10.3.12 is available
1. Which recovery do you recommend to flash on my device/version/MIUI release? Xiaomi-Miui.gr or 4PDA
2. Can I update MIUI and Flash recovery with no issues or are there any issues regarding MIUI version?
3. Do I flash using basic ADB method (phone on fastboot mode, "fastboot flash recovery ***" command") or is there anything I'm missing?
PS/ I did my research so Im aware of basic info
Thanks in advance

You should be fine doing that. I installed the Greek TWRP as well on my Mi 9T with MIUI Global version 10.3.12. Use the latest version available as it has more fixes and support for data encryption/decryption (latest version 3.3.1_12-08-19 as of today: http://www.mediafire.com/file/yuhi6pl5qtjr1nu/twrp_davinci_3.3.1_12-08-19_blue_Ss_new.img/file ).
After flashing TWRP you should format 'Data' first and flash Magisk to prevent the MIUI Global ROM from re-flashing the stock recovery. If you install the MIUI EU ROM or any other custom ROM this is not necessary though.
The bootloop issue is mostly related to the 'Anti-rollback' feature in the MIUI official ROMs. You can check the status by executing 'fastboot getvar anti'. If the result is empty or 1 you can flash whatever you want, but if it's more than 1 you should stick to flashing a MIUI ROM that is the same or higher version than it is now unless you can verify the 'anti' version in that particular ROM is equal or lower than the value in your phone.

You can follow the below video to root the device
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
And if any way you brick the device it can be recovered easily. Follow the below Video for unbricking

rocky29b4u said:
You can follow the below video to root the device
://youtu.be/dIWZGv-jCOA
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
And if any way you brick the device it can be recovered easily. Follow the below Video for unbricking
://youtu.be/JDrH8_yEO28
Click to expand...
Click to collapse
Video is not working. I'm interested since I both mine yesterday.

Sir_gpm said:
Video is not working. I'm interested since I both mine yesterday.
Click to expand...
Click to collapse
Try to open this link separately
https://youtu.be/JDrH8_yEO28

Please don't type english titles if your video will not be in english. This is straight up misleading and bad for everyone.
rocky29b4u said:
You can follow the below video to root the device
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
And if any way you brick the device it can be recovered easily. Follow the below Video for unbricking
Click to expand...
Click to collapse

sanchaz12 said:
You should be fine doing that. I installed the Greek TWRP as well on my Mi 9T with MIUI Global version 10.3.12.....
Click to expand...
Click to collapse
Thank you so much. Your answer clarified a lot of Xiaomi things I was wondering about.
I successfully flashed TWRP. I intended to install MIUI 10.3.12 after unlocking bootloader (im on 10.3.7) but I forgot and flashed TWRP directly. I remembered before flashing Magisk tho. Is the window for updating to 10.3.12 is closed by flashing TWRP?
Also, have you tested EU rom? Should I flash it or stick with stock?
Oh. I got value of 1 after executing "fastboot getvar anti" command

boot.img = ROM
rocky29b4u said:
You can follow the below video to root the device
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
In this video at 5:46 the guy is flashing boot.img as well not just recovery.
In other post I did not see that people were flashing boot.img, is this the firmware? And if its the ROM, is it necessary if I want just root the device or I can stay at stock ROM?
Click to expand...
Click to collapse

We need subs on the video or an english version of it. Don't just paste the video in every step, help us here..

SomniusX said:
We need subs on the video or an english version of it. Don't just paste the video in every step, help us here..
Click to expand...
Click to collapse
Hi,
See I will explain this in very simple steps
1. Download the TWRP image from description in the Video
2. Unlock your phone using MI Unlock Tool
3. Reboot your pone to FastBoot mode again
4. Wherever MiUnlock Folder is present on your computer go to that Folder
5. Right click anywhere on the folder keeping Shift pressed. You will see 'Command Prompt Here' option
6. Select that and Command Prompt will open
7. In command prompt type FASTBOOT DEVICES (This will show connected devices)
8. If device is detected type FASTBOOT FLASH RECOVERY <FULL PATH OF THE RECOVERY IMAGE FILE> (Example if TWRP is in C:\temp then command will be FASTBOOT FLASH RECOVERY C:\TEMP\TWRP.IMG)
9. This time type FASTBOOT BOOT <TWRP.IMG FILE> (This will boot phone to TWRP Forcefully)
10. If 9 doesn't work. Repeat 8 and Skip 9
11. After Step 8 type FASTBOOT REBOOT (Press Volume UP while phone is rebooting)
Phone will boot into TWRP this time.
Hope I was able to explain. If not let me know

rocky29b4u said:
Hi,
See I will explain this in very simple steps
1. Download the TWRP image from description in the Video
2. Unlock your phone using MI Unlock Tool
3. Reboot your pone to FastBoot mode again
4. Wherever MiUnlock Folder is present on your computer go to that Folder
5. Right click anywhere on the folder keeping Shift pressed. You will see 'Command Prompt Here' option
6. Select that and Command Prompt will open
7. In command prompt type FASTBOOT DEVICES (This will show connected devices)
8. If device is detected type FASTBOOT FLASH RECOVERY <FULL PATH OF THE RECOVERY IMAGE FILE> (Example if TWRP is in C:\temp then command will be FASTBOOT FLASH RECOVERY C:\TEMP\TWRP.IMG)
9. This time type FASTBOOT BOOT <TWRP.IMG FILE> (This will boot phone to TWRP Forcefully)
10. If 9 doesn't work. Repeat 8 and Skip 9
11. After Step 8 type FASTBOOT REBOOT (Press Volume UP while phone is rebooting)
Phone will boot into TWRP this time.
Hope I was able to explain. If not let me know
Click to expand...
Click to collapse
In the step 9 you type the name of the file or the whole path of the PC to the file?

rastip said:
In the step 9 you type the name of the file or the whole path of the PC to the file?
Click to expand...
Click to collapse
Its the file name with full path in PC for the Recovery File

rocky29b4u said:
Hi,
See I will explain this in very simple steps
1. Download the TWRP image from description in the Video
2. Unlock your phone using MI Unlock Tool
3. Reboot your pone to FastBoot mode again
4. Wherever MiUnlock Folder is present on your computer go to that Folder
5. Right click anywhere on the folder keeping Shift pressed. You will see 'Command Prompt Here' option
6. Select that and Command Prompt will open
7. In command prompt type FASTBOOT DEVICES (This will show connected devices)
8. If device is detected type FASTBOOT FLASH RECOVERY <FULL PATH OF THE RECOVERY IMAGE FILE> (Example if TWRP is in C:\temp then command will be FASTBOOT FLASH RECOVERY C:\TEMP\TWRP.IMG)
9. This time type FASTBOOT BOOT <TWRP.IMG FILE> (This will boot phone to TWRP Forcefully)
10. If 9 doesn't work. Repeat 8 and Skip 9
11. After Step 8 type FASTBOOT REBOOT (Press Volume UP while phone is rebooting)
Phone will boot into TWRP this time.
Hope I was able to explain. If not let me know
Click to expand...
Click to collapse
Thank you for the reply, and trust me, this text guide is much simpler and useful than trying to decode what you are saying in the video.

SomniusX said:
Thank you for the reply, and trust me, this text guide is much simpler and useful than trying to decode what you are saying in the video.
Click to expand...
Click to collapse
No Problem. Thanks...

Greetings everyone,im facing this error showing on tool,saying number not associated with your phone(already added mi account and was login from the day i got k20)..
please help.

Any help will do.

Hello Everyone,
I really need help regarding this matter. I came from Evolution X 3.0 custom rom, now when I flash to stock rom, I flashed the Nougat version instead of Pie.
Now my dilemmas are the following:
1. Stuck in bootloop
2. Unable to unlock bootloader since I'm unable to boot it to the system
3. Tried all the other guide including this post except for number 2, since I don't know how to do that, and number 6, since I'm unable to open it for now: https://forum.xda-developers.com/showpost.php?p=78219944&postcount=224
Since this is the case, should I need to proceed with number 6 or is there any other methods I can use?

kevinzareno said:
Hello Everyone,
I really need help regarding this matter. I came from Evolution X 3.0 custom rom, now when I flash to stock rom, I flashed the Nougat version instead of Pie.
Now my dilemmas are the following:
1. Stuck in bootloop
2. Unable to unlock bootloader since I'm unable to boot it to the system
3. Tried all the other guide including this post except for number 2, since I don't know how to do that, and number 6, since I'm unable to open it for now: https://forum.xda-developers.com/showpost.php?p=78219944&postcount=224
Since this is the case, should I need to proceed with number 6 or is there any other methods I can use?
Click to expand...
Click to collapse
For step 2 you need to install Mi A1 device's drivers first, so you'll be allowed to use fastboot and adb commands from PC to your device.
The command shown on that step is just what you have to type when you open cmd at file's and adb-fastboot folder. Just paste the name of the file you've to load and install "adb sideload thisiswhatiwanttoinstall.zip".
You can find a better way to understand this procedure, by reading those rooting methods with TWRP... obviously not those with 1-click-root ones... look for those that make use of "adb-fastboot", since there, after TWRP custom Recovery is flashed, you're able to sideload Magisk to it to it in order to be also flashed on your device.
It's a pretty easy task once you have managed to install device's drivers well and have "adb-fastboot" tools, to open cmd from it's folder and start to run adb or fastboot commands to your device.

KaaMyA said:
For step 2 you need to install Mi A1 device's drivers first, so you'll be allowed to use fastboot and adb commands from PC to your device.
The command shown on that step is just what you have to type when you open cmd at file's and adb-fastboot folder. Just paste the name of the file you've to load and install "adb sideload thisiswhatiwanttoinstall.zip".
You can find a better way to understand this procedure, by reading those rooting methods with TWRP... obviously not those with 1-click-root ones... look for those that make use of "adb-fastboot", since there, after TWRP custom Recovery is flashed, you're able to sideload Magisk to it to it in order to be also flashed on your device.
It's a pretty easy task once you have managed to install device's drivers well and have "adb-fastboot" tools, to open cmd from it's folder and start to run adb or fastboot commands to your device.
Click to expand...
Click to collapse
I see. We'll will this work even if the bootloader is locked? I can't really unlock it

kevinzareno said:
I see. We'll will this work even if the bootloader is locked? I can't really unlock it
Click to expand...
Click to collapse
First of all be sure you could complete that tutorial you're following.
You're flashing device's firmware, that will put all on its place.
It's not like flashing a ROM, you're trying to unbrick device's software.

if you have enabled oem unlock in Development Settings then you can unlock bootloader by fastboot cmd "fastboot oem unlock" or if it not works try flashing stock pie rom with Miflash tool and if Miflash tool not works try QFIL
just a tip: when you flash stock rom with miflash tool and don't want to relock bootloader just remove the lines with "fastboot flash userdata" and "fastboot oem lock" in flash script "flash_all.bat" or "flash_all_except_storage.bat"
---------- Post added at 05:47 AM ---------- Previous post was at 05:43 AM ----------
just boot into EDL mode and try flashing with MiFlash tool.
i was revive my device with QFIL. QFIL automatically reboot device into EDL mode