Related
My phone has banished me from using it for about 3 months now. I repeatedly apologized for upsetting it, and begged of it to allow me back in. But it's a cold machine, which feels no empathy and cares not for my well-intentioned promises of never angering it again.
I understand it's reluctance to believe my words, as this is not the first time I've committed such atrocities. You see, I bricked it doing the same thing once before. Likewise, I was never able to fix it. Instead, I pawned it off to an Android developer in the office and he was able to fix it after a few hours of struggling. I've since moved to a different office on the other side of the country, and he was unable to remember exactly what he did that finally fixed it.
On to the important things:
What happened exactly?
I was installing a ROM (I can't remember which one at this point, it's been a while). Something counterproductive happened during the install, and sent it into a bootloop.
Symptoms?
1. It starts booting as normal. HTC logo for a few seconds, goes black as if it's going to the next screen, then it reboots.
2. This time it has the HTC logo with "Entering Recovery..." in pink above it.
3. I get a very quick (a few milliseconds, tops) glimpse of the CWM loading screen, then it reboots and goes back to step 1.
4. It repeats indefinitely, and would probably do so for eternity.
What can I actually do?
I can get to the bootloader screen, and cycle through the options (Fasboot, Recovery, Factory Reset, Simlock, Image CRC, Show Barcode), and I can drill into each section and see their child options. However anything I try to do, just sends me into the bootloop.
However, it does still say it's Unlocked in the bootloader. It has the "Tampered" and "Unlocked" alerts at the top.
What have I tried?
I've tried more random things than I can possibly recite right now. I even went to the extremes of dual booting Windows 8 on my Macbook, so I could start trying some of the Windows-only suggestions, like using the All-In-One Toolkit. The biggest issue, is that nothing I use can find the device. Not ADB or Fastboot on Mac, not ADB or Fasboot on Windows, and not the All-In-On-Toolkit. The only thing I ever get is "Waiting for device" or "Device not found".
Any help would be much appreciated. Thanks in advance guys!
rvrzl said:
My phone has banished me from using it for about 3 months now. I repeatedly apologized for upsetting it, and begged of it to allow me back in. But it's a cold machine, which feels no empathy and cares not for my well-intentioned promises of never angering it again.
I understand it's reluctance to believe my words, as this is not the first time I've committed such atrocities. You see, I bricked it doing the same thing once before. Likewise, I was never able to fix it. Instead, I pawned it off to an Android developer in the office and he was able to fix it after a few hours of struggling. I've since moved to a different office on the other side of the country, and he was unable to remember exactly what he did that finally fixed it.
On to the important things:
What happened exactly?
I was installing a ROM (I can't remember which one at this point, it's been a while). Something counterproductive happened during the install, and sent it into a bootloop.
Symptoms?
1. It starts booting as normal. HTC logo for a few seconds, goes black as if it's going to the next screen, then it reboots.
2. This time it has the HTC logo with "Entering Recovery..." in pink above it.
3. I get a very quick (a few milliseconds, tops) glimpse of the CWM loading screen, then it reboots and goes back to step 1.
4. It repeats indefinitely, and would probably do so for eternity.
What can I actually do?
I can get to the bootloader screen, and cycle through the options (Fasboot, Recovery, Factory Reset, Simlock, Image CRC, Show Barcode), and I can drill into each section and see their child options. However anything I try to do, just sends me into the bootloop.
However, it does still say it's Unlocked in the bootloader. It has the "Tampered" and "Unlocked" alerts at the top.
What have I tried?
I've tried more random things than I can possibly recite right now. I even went to the extremes of dual booting Windows 8 on my Macbook, so I could start trying some of the Windows-only suggestions, like using the All-In-One Toolkit. The biggest issue, is that nothing I use can find the device. Not ADB or Fastboot on Mac, not ADB or Fasboot on Windows, and not the All-In-On-Toolkit. The only thing I ever get is "Waiting for device" or "Device not found".
Any help would be much appreciated. Thanks in advance guys!
Click to expand...
Click to collapse
Sorry I don't know how drivers work on a Mac.
the procedure from a PC would be
boot to bootloader
choose fastboot
plug in usb to phone
you now see fastboot usb in bootloader
from command prompt type "fastboot erase cache" then fastboot reboot
try to boot phone.
if it fails
reboot to bootloader
reflash recovery
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot
make sure your recovery is named like above and in the same folder as fastboot
clsA said:
Sorry I don't know how drivers work on a Mac.
the procedure from a PC would be
boot to bootloader
choose fastboot
plug in usb to phone
you now see fastboot usb in bootloader
from command prompt type "fastboot erase cache" then fastboot reboot
try to boot phone.
if it fails
reboot to bootloader
reflash recovery
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot
make sure your recovery is named like above and in the same folder as fastboot
Click to expand...
Click to collapse
Thanks for the help clsA
I gave this a try, but like I expected I'm just getting a "waiting for device" message from fastboot.
This time around (in Windows), I did notice that I'm also getting an error about the USB device not being recognized. I don't think it's initializing correctly because Windows says it's malfunctioning. Nothing has happened to the device itself (no bangs, drops, water, etc), and this wasn't a problem until after it was bricked, so I doubt it's hardware related.
Interestingly, under the Device Manager, it is listed under "Android USB Devices" as "My HTC" so it seems to know what it is. My drivers appear to be up to date. Any other suggestions? Thanks again.
rvrzl said:
Thanks for the help clsA
I gave this a try, but like I expected I'm just getting a "waiting for device" message from fastboot.
This time around (in Windows), I did notice that I'm also getting an error about the USB device not being recognized. I don't think it's initializing correctly because Windows says it's malfunctioning. Nothing has happened to the device itself (no bangs, drops, water, etc), and this wasn't a problem until after it was bricked, so I doubt it's hardware related.
Interestingly, under the Device Manager, it is listed under "Android USB Devices" as "My HTC" so it seems to know what it is. My drivers appear to be up to date. Any other suggestions? Thanks again.
Click to expand...
Click to collapse
Install the drivers included in the All in one kit or install HTC sync (not recommended)
Sent from my TouchPad using xda app-developers app
[RESOLVED!]
For anyone else who might be having this problem
1. I was finally able to resolve this by downloading the archive provided by Esau Silva, which (I'm assuming) had updated versions of adb, and fastboot for Mac/OSX: http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx
2. I booted to the bootloader (power + volume down for 10 seconds), went to the Fastboot option, then plugged my phone into my Macbook; enabling Fastboot USB.
3. I opened terminal, CD'd into the directory containing adb/fastboot, and then ran "./fastboot devices" to see if it recognized my device. Sure enough, with Fastboot USB on and the updated adb, it recognized the device.
4. Then I ran "./fastboot erase cache" which allowed me to boot back into the bootload, and then properly boot into recovery, finally seeing ClockworkMod Recovery again.
5. From CWMR I erased the cache again, erased the dalvik cache, and then did a full wipe/factory reset.
6. Then I booted back into CWMR once again, and chose sideload. Then back on my Macbook I was able to run "./adb devices" to make sure adb could see my HTC One. Once I confirmed it could see it, I ran "./adb sideload nameofrom.zip"
After the sideload was complete, I was back up and running.
Big thanks to clsA who got me Googling fastboot a bit more. Hopefully this helps someone else!
After 2-3 hours of work I finally managed to unlock my Honor5x, but my phone seems to **** up on these few steps of the xda guide:
Step 9
Boot back into the bootloader by typing the following
"adb reboot bootloader"
Step 10
Flash the recovery with the following command:
"fastboot flash recovery twrp_kiwi.img"
Step 11
Once it finishes type the following
"fastboot reboot"
My phone gets recognized by adb generally, but whenever I use the command adb reboot bootloader, immediately after my phone doesn't get recognized by fastboot, so the following steps don't work. The phone is in bootloader mode however, and it DOES say that it's unlocked.
Things I've tried:
Using different USB ports
Using different USB s
Unplugging and replugging while my phone is in fastboot
Installing TWRP from the TWRP manager app (It gives me an error with every single version that's available. The error message is "Something went wrong. Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occured. Would you like to attempt rebooting to recovery now?" Pressing the button reboot now doesn't do anything.
Re-enabled developer mode and made sure that usb debug and oem unlock are both enabled.
Computer is: Win 10 64 bit
Wtf do I do?
Araschon said:
After 2-3 hours of work I finally managed to unlock my Honor5x, but my phone seems to **** up on these few steps of the xda guide:
Step 9
Boot back into the bootloader by typing the following
"adb reboot bootloader"
Step 10
Flash the recovery with the following command:
"fastboot flash recovery twrp_kiwi.img"
Step 11
Once it finishes type the following
"fastboot reboot"
My phone gets recognized by adb generally, but whenever I use the command adb reboot bootloader, immediately after my phone doesn't get recognized by adb anymore, so the following steps don't work. The phone is in bootloader mode however, and it DOES say that it's unlocked.
Things I've tried:
Using different USB ports
Using different USB s
Unplugging and replugging while my phone is in fastboot
Installing TWRP from the TWRP manager app (It gives me an error with every single version that's available. The error message is "Something went wrong. Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occured. Would you like to attempt rebooting to recovery now?" Pressing the button reboot now doesn't do anything.
Re-enabled developer mode and made sure that usb debug and oem unlock are both enabled.
Computer is: Win 10 64 bit
Wtf do I do?
Click to expand...
Click to collapse
Install the Huawei fastboot drivers
Sent from my SM-N920T using Tapatalk
I have HiSuite, which seems to be the USB drivers for huawei, but are you talking about the ones from team android? I can't post the link because this is a new account.
I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
salmanvai said:
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
Click to expand...
Click to collapse
Edit. Okay, ignore most of what i said down there as after re-reading your post you seem to have a grasp on fastboot, the no command bit still applies though i think
"No Command" mode
If your talking about the recovery with the android image in the background, then there might still be hope, for some reason, the recovery starts up in this mode, showing the "no cammand" message, its fiddly, but you have to press the power button and either volume up or volume down repeatedly, in the end i was button spamming all the buttons and eventually the recovery menu showed up. Carefull to stop pushing buttons when the menu shows up as the buttons are how you navigate(v+,v-) and choose options(power button)
Whether that gives you any options i dont know, you could try a factory reset from the recovery menu, i suppose, or try the posted ota in the other thread if nokia has`nt released official firmware, although im not sure if you can use stock recovery to flash unofficial firmware, best bet is to try and boot into fastboot and use adb on another computer to flash the firmware that way, assuming the firmware files are available.
Most android devices have a way to boot into recovery or fastboot/bootloader using hardware keys
Quick google found this (works?)
Power off
Connect Micro USB to computer.
"In the next step hold down Volume Down + Power key for a short while"
Let go of the buttons when fastboot comes up
Using the computer with adb installed, go to a command terminal and type "fastboot devices" without quotes, you`ll know everythings working if your the device is listed in terminal after typing that command. From there look up fastboot flashing firmware or something to that extent, this is assuming you managed to find the correct firmware for your device and have it stored in your computer
I`d be real carefull here with fastboot, flashing wrong image file could make things much worse, at least it seems you can boot to recovery, so hopefully a factory reset fixes things, use fastboot as last resort i.e if its new job is a paperweight, as i dont think theres any particular guide on doing this specifically for the nokia 1, but i havent checked thouroughly so i could be wrong, take a look and see..............
And let us know if/how you managed to get it working
Goodluck
So, I recently tried to root my Redmi 5 phone and install Lineage OS into it. This is my first time doing it, so I believe I may not have understood the words I had been reading well. Due to this, I'll try to be as descriptive as possible with the actions I had taken that led to my device being stuck.
I had followed this guide, for the most part: https://www.getdroidtips.com/lineage-os-17-xiaomi-redmi-5/
As per the guide, I performed the following actions:
Enabled the developer options
Registered my device to my Mi account
Enabled USB debugging, OEM unlocking
Rebooted in fastboot mode using the ADB tools through CMD (adb reboot bootloader)
While in fastboot mode, I used the Mi Unlock tool to unlock my device.
As per my understanding, these steps would unlock the bootloader. I rebooted my device, set it up (the phone behaves as if freshly booted) and checked the settings menu after enabling developer options again. It shows the bootloader is already unlocked and that Mi Account status is also unlocked. I enabled the USB debugging options again and carried on with the guide.
I then downloaded the rosy TWRP file (version 3.5, I think).
I even downloaded GApps and Lineage 18.1 OS
I tried to copy the above files into my Redmi 5 internal storage
The Lineage and GApps file failed to copy, but I was able to copy the TWRP file
One thing to note here, I am not sure if my USB cable is faulty or if my phone's micro USB port is faulty or if my laptop's USB ports are faulty. When the phone is connected to my PC, it is extremely lousy. If I shake the cable even a bit, it disconnects and reconnects. When I try to use the file explorer to copy the files from my laptop to the android phone, it usually fails for large files or large quantities of small files. I believe this was the reason behind the failure. Nonetheless, I decided to do the TWRP part first.
The guide said to reboot in recovery mode and that would take me to TWRP recovery mode. Well, it did not! It took me to a menu that had the following options:
Reboot
Reboot to System
Back to Main Menu
Wipe Data
Wipe All Data
Back to Main Menu
Connect to MIAssistant
I assumed I had entered recovery mode incorrectly, so I followed the link in the guide on how to enter recovery mode. It suggested using the ADB tools.
I used the command: adb reboot recovery
It did the same thing that I had done. So, I assumed that that is the recovery mode, but I am unable to enter TWRP recovery mode. There was another link that would show me how to do this.
I followed that link and downloaded the files that was mentioned. However, the guide tells little to nothing on what to do with these files. The only file that was used was the rosy twrp file.
I enabled the USB debugging mode on my phone.
Opened CMD from the folder with ADB
Entered the command: adb reboot bootloader
Phone enters fastboot mode
Entered the command: fastboot devices
I can see that a device is connected
Entered the command: fastboot flash recovery rosy-3-5.img (I renamed it for convenience, I believe that was allowed because every website had different name for their file)
I then rebooted into recovery mode by first rebooting it normally: fastboot reboot
Then entering the command: adb reboot recovery
It still showed the same old recovery menu. Nothing had changed. I looked around the internet and found that I could boot with the TWRP image by entering the command: fastboot boot rosy-3-5.img
This opened the screen that I was expecting, but it did not open the chinese menu at all. It directly went to the screen that had options such as Install, Wipe, etc.,
I rebooted normally and then tried to transfer the GApps file and Lineage file into my phone. As usual, it was failing. I tried to use the adb push command and it still failed but with an error saying "permissions denied"
At this point, I looked up how to get root permissions and I learnt that I had to root my device. I looked up how to root with Magisk and SuperSU. The guides all required me to boot in TWRP recovery and then install the files from my phone. Unable to transfer the files to my phone, I uploaded the files to my google drive, and manually downloaded into my phone. I boot up rosy (TWRP recovery, or so I think) using ADB tools. Unfortunately, it does not recognize any of the files in my internal storage. Everything is empty.
Defeated by this, I decided to let it go. I had a factory reset Redmi 5 at the time. I then watched a video that showed how to root with Magisk, but wasn't specific to Redmi 5, it was a generic video for android devices.
I installed the magisk manager apk into my android phone.
Then I copied the boot.img file from the Lineage folder into my android device. Despite the OS being 600 MB large, the boot.img file was only 11 MB.
Anyway, I patched the boot.img file using magisk manager.
It created a file called magisk-patched_1pTOD.img (I'm a bit unsure of the name, but it was similar to that).
The video said that I should copy this file into my laptop and then reboot my phone into fastboot.
Once in fastboot, I had to enter the command: fastboot flash boot magisk-patched_1pTOD.img
I believed that this would root my device and grant me root access. I don't know what my actions were actually supposed to do, but my device is unusable for all intents and purposes. I rebooted the device and it shows the Mi logo for a brief moment and there's no light. An empty dark screen, it's not even a black screen. It's like the display fails to work. I can switch into recovery mode and into fastboot mode but normal reboot did the same.
Thinking that I bricked my phone, I tried to unbrick it.
I downloaded the fastboot rom for Redmi 5 rosy and then installed the Mi Flash tool along with the drivers for it.
I then selected the correct ROM folder (it kept showing up as can't find flash script until I was in the right folder for it)
Rebooted my phone into fastboot mode
Hit refresh on the Mi Flash tool
It showed my device
I chose Clean All option
I hit flash
It goes up till 97%-ish and then fails with an error saying "flash system error".
However, I noticed that now, I can see that the Mi Logo doesn't disappear now. I can still go into recovery mode and fastboot mode, but normal reboot takes me to the permanent Mi Logo Screen. I cannot even shut it down. It auto reboots to the Mi Logo Screen if I do so.
I connected my device to my laptop and then opened the ADB tools.
I entered the following command to see if it's recognized by adb:
adb devices
It did not. I then switched to fastboot mode manually by pressing the Vol Down and Power buttons.
Then entered the following to see if it is recognized in fastboot mode:
fastboot devices
It showed my device there. So I used the following command to reboot and see if it is recognized in fastboot again:
fastboot reboot
While it shows the Mi Logo screen, I typed the command:
fastboot devices
It still shows my device.
I concluded that my device is in an infinite fastboot loop. I cannot boot it up normally. I cannot flash the Redmi 5 ROM into it either. I cannot use my phone.
If anybody has actually gone through this entire mess that I made, and has figured out what went wrong or at least how to fix it, please help me.
Message me on telegram @benzoylperoxide
Hope I could help you with this situation.
If you got data, download fastboot rom based on nought and fastboot rom 9.5.30
Download latest miflash tool from miglobe website.
Install proper drivers from miunlock tool zip file.
And Hope for the best.
Ping me tommorow at anytime.
Good night Bro
incertam7 said:
So, I recently tried to root my Redmi 5 phone and install Lineage OS into it. This is my first time doing it, so I believe I may not have understood the words I had been reading well. Due to this, I'll try to be as descriptive as possible with the actions I had taken that led to my device being stuck.
I had followed this guide, for the most part: https://www.getdroidtips.com/lineage-os-17-xiaomi-redmi-5/
As per the guide, I performed the following actions:
Enabled the developer options
Registered my device to my Mi account
Enabled USB debugging, OEM unlocking
Rebooted in fastboot mode using the ADB tools through CMD (adb reboot bootloader)
While in fastboot mode, I used the Mi Unlock tool to unlock my device.
As per my understanding, these steps would unlock the bootloader. I rebooted my device, set it up (the phone behaves as if freshly booted) and checked the settings menu after enabling developer options again. It shows the bootloader is already unlocked and that Mi Account status is also unlocked. I enabled the USB debugging options again and carried on with the guide.
I then downloaded the rosy TWRP file (version 3.5, I think).
I even downloaded GApps and Lineage 18.1 OS
I tried to copy the above files into my Redmi 5 internal storage
The Lineage and GApps file failed to copy, but I was able to copy the TWRP file
One thing to note here, I am not sure if my USB cable is faulty or if my phone's micro USB port is faulty or if my laptop's USB ports are faulty. When the phone is connected to my PC, it is extremely lousy. If I shake the cable even a bit, it disconnects and reconnects. When I try to use the file explorer to copy the files from my laptop to the android phone, it usually fails for large files or large quantities of small files. I believe this was the reason behind the failure. Nonetheless, I decided to do the TWRP part first.
The guide said to reboot in recovery mode and that would take me to TWRP recovery mode. Well, it did not! It took me to a menu that had the following options:
Reboot
Reboot to System
Back to Main Menu
Wipe Data
Wipe All Data
Back to Main Menu
Connect to MIAssistant
I assumed I had entered recovery mode incorrectly, so I followed the link in the guide on how to enter recovery mode. It suggested using the ADB tools.
I used the command: adb reboot recovery
It did the same thing that I had done. So, I assumed that that is the recovery mode, but I am unable to enter TWRP recovery mode. There was another link that would show me how to do this.
I followed that link and downloaded the files that was mentioned. However, the guide tells little to nothing on what to do with these files. The only file that was used was the rosy twrp file.
I enabled the USB debugging mode on my phone.
Opened CMD from the folder with ADB
Entered the command: adb reboot bootloader
Phone enters fastboot mode
Entered the command: fastboot devices
I can see that a device is connected
Entered the command: fastboot flash recovery rosy-3-5.img (I renamed it for convenience, I believe that was allowed because every website had different name for their file)
I then rebooted into recovery mode by first rebooting it normally: fastboot reboot
Then entering the command: adb reboot recovery
It still showed the same old recovery menu. Nothing had changed. I looked around the internet and found that I could boot with the TWRP image by entering the command: fastboot boot rosy-3-5.img
This opened the screen that I was expecting, but it did not open the chinese menu at all. It directly went to the screen that had options such as Install, Wipe, etc.,
I rebooted normally and then tried to transfer the GApps file and Lineage file into my phone. As usual, it was failing. I tried to use the adb push command and it still failed but with an error saying "permissions denied"
At this point, I looked up how to get root permissions and I learnt that I had to root my device. I looked up how to root with Magisk and SuperSU. The guides all required me to boot in TWRP recovery and then install the files from my phone. Unable to transfer the files to my phone, I uploaded the files to my google drive, and manually downloaded into my phone. I boot up rosy (TWRP recovery, or so I think) using ADB tools. Unfortunately, it does not recognize any of the files in my internal storage. Everything is empty.
Defeated by this, I decided to let it go. I had a factory reset Redmi 5 at the time. I then watched a video that showed how to root with Magisk, but wasn't specific to Redmi 5, it was a generic video for android devices.
I installed the magisk manager apk into my android phone.
Then I copied the boot.img file from the Lineage folder into my android device. Despite the OS being 600 MB large, the boot.img file was only 11 MB.
Anyway, I patched the boot.img file using magisk manager.
It created a file called magisk-patched_1pTOD.img (I'm a bit unsure of the name, but it was similar to that).
The video said that I should copy this file into my laptop and then reboot my phone into fastboot.
Once in fastboot, I had to enter the command: fastboot flash boot magisk-patched_1pTOD.img
I believed that this would root my device and grant me root access. I don't know what my actions were actually supposed to do, but my device is unusable for all intents and purposes. I rebooted the device and it shows the Mi logo for a brief moment and there's no light. An empty dark screen, it's not even a black screen. It's like the display fails to work. I can switch into recovery mode and into fastboot mode but normal reboot did the same.
Thinking that I bricked my phone, I tried to unbrick it.
I downloaded the fastboot rom for Redmi 5 rosy and then installed the Mi Flash tool along with the drivers for it.
I then selected the correct ROM folder (it kept showing up as can't find flash script until I was in the right folder for it)
Rebooted my phone into fastboot mode
Hit refresh on the Mi Flash tool
It showed my device
I chose Clean All option
I hit flash
It goes up till 97%-ish and then fails with an error saying "flash system error".
However, I noticed that now, I can see that the Mi Logo doesn't disappear now. I can still go into recovery mode and fastboot mode, but normal reboot takes me to the permanent Mi Logo Screen. I cannot even shut it down. It auto reboots to the Mi Logo Screen if I do so.
I connected my device to my laptop and then opened the ADB tools.
I entered the following command to see if it's recognized by adb:
adb devices
It did not. I then switched to fastboot mode manually by pressing the Vol Down and Power buttons.
Then entered the following to see if it is recognized in fastboot mode:
fastboot devices
It showed my device there. So I used the following command to reboot and see if it is recognized in fastboot again:
fastboot reboot
While it shows the Mi Logo screen, I typed the command:
fastboot devices
It still shows my device.
I concluded that my device is in an infinite fastboot loop. I cannot boot it up normally. I cannot flash the Redmi 5 ROM into it either. I cannot use my phone.
If anybody has actually gone through this entire mess that I made, and has figured out what went wrong or at least how to fix it, please help me.
Click to expand...
Click to collapse
Flash system error in MiFlash? Probably the stock rom you downloaded and extracted is corrupted.
Please try flashing MIUI 9 for your Redmi 5.
Yeah, users have had issues with twrp being replaced by stock rom.
For TWRP,
fastboot flash revovery (recovery name.img)
Fastboot boot (recovery name .img)
After that flash your custom rom after wiping system,boot, vendor, data and cache, Internal format might be needed if it's encrypted.
Then, after custom rom is flashed, flash gapps and then twrp zip in TWRP, yeah you saw it right, flash twrp zip in TWRP. This way, twrp won't get replaced.
You can give directly flashing TWRP and flashing custom rom the way I told, Flashing Miui isn't important if your goal is to flash custom rom.