-----------------------------------------------------------------------------------------
Start up Failed:
Your device didnt't start up successfully.
Use the software repair assistant on computer
to repair your device.
connect your device to your computer to get
the software repair assistant
ap fastboot flash mode (secure)
failed to validate boot image
ERROR: Failed to pass validaton, backup to fastboot
fastboot reason: Fall-through from charger boot mode
-----------------------------------------------------------------------------------------
is there any way to backup my phone data before flashing ?
only if you installed custom recovery, boot in recovery and exctract /data in SD card/ USB OTG.
as this looks like you screwed up with bootloader unlock, or reflashing stock ROM
indestructible master said:
only if you installed custom recovery, boot in recovery and exctract /data in SD card/ USB OTG.
as this looks like you screwed up with bootloader unlock, or reflashing
Click to expand...
Click to collapse
i didn't tried to unlock bootloader or did anything. my phone was just charging & then this showed up , all other options are disabled (recovery, factory, restart bootoader etc)
adb is not detecting & i can only execute fastboot command ,
is there any way to backup my photos & files ?
niirmaaltwaatii said:
i didn't tried to unlock bootloader or did anything. my phone was just charging & then this showed up , all other options are disabled (recovery, factory, restart bootoader etc)
adb is not detecting & i can only execute fastboot command ,
is there any way to backup my photos & files ?
Click to expand...
Click to collapse
no,
remove SD card, and
at least recover it via fastboot, or via stock recovery (download official, stock ROM and flash in stock recovery, it should work)
or install that software for PC first to check if it can be restored that way, maybe it's faulty boot.img which software can fix (try this first, maybe you get lucky and save data)
Related
Hello
A newbie here ...
My new phone "Lenovo Vibe C (A2020)" does not allow me to install any kind of custom recovery on it, I tried the following methods ...
1- SP Flash Tool: doesn't detect my phone at all, even after installing all drivers (Qualcomm, MTK, Etc ,,, ).
2- Adb and fastboot: whenever I try to flash a recovery, it only shows (waiting for a device) command, even after being detected by "adb devices" command, and showing device ID.
3- flashing apps: I used flashify and thrasher, at the beginning they both show a successful flashing process, up until rebooting to recovery, then only shows "Lenovo" logo for a second right before turning the phone off.
that's what i did, any help would be appreciated.
Note: the phone isn't even indexed in the site's database ... I wonder why!
You should unlock the bootloader first after rooting your device
Hello there. I do hope that you can still boot your device normally. If you can, please do make a backup of your rom.
(a) Download and install the latest driver for your device
(b) Download the latest adb and fastboot tool (I recommend Minimal ADB and Fastboot)
(c) Download the custom recovery image. Save/copy it on the root directory of your ADB and Fastboot folder.
(d) In your device, go to settings > developer > enable oem unlocking and usb debugging (which is I guess you already did).
(e) Now open your terminal/cmd: adb reboot bootloader (this will boot your device in fastboot)
(f) In terminal/cmd: fastboot oem unlock (or fastboot oem unlock-go)
(g) Now flash the custom recovery: fastboot flash recovery "recovery.img"
***I suggest you try first if the custom recovery image works: fastboot boot recovery.img
(h) Reboot into recovery and check if it works.
Ospider said:
Hello
A newbie here ...
My new phone "Lenovo Vibe C (A2020)" does not allow me to install any kind of custom recovery on it, I tried the following methods ...
1- SP Flash Tool: doesn't detect my phone at all, even after installing all drivers (Qualcomm, MTK, Etc ,,, ).
2- Adb and fastboot: whenever I try to flash a recovery, it only shows (waiting for a device) command, even after being detected by "adb devices" command, and showing device ID.
3- flashing apps: I used flashify and thrasher, at the beginning they both show a successful flashing process, up until rebooting to recovery, then only shows "Lenovo" logo for a second right before turning the phone off.
that's what i did, any help would be appreciated.
Note: the phone isn't even indexed in the site's database ... I wonder why!
Click to expand...
Click to collapse
Check my thread for custom marshmallow rom and twrp recovery .
https://forum.xda-developers.com/android/general/bliss-rom-lenovo-vibe-c-a2020a40-t3567812
rolland.arriza said:
Hello there. I do hope that you can still boot your device normally. If you can, please do make a backup of your rom.
(a) Download and install the latest driver for your device
(b) Download the latest adb and fastboot tool (I recommend Minimal ADB and Fastboot)
(c) Download the custom recovery image. Save/copy it on the root directory of your ADB and Fastboot folder.
(d) In your device, go to settings > developer > enable oem unlocking and usb debugging (which is I guess you already did).
(e) Now open your terminal/cmd: adb reboot bootloader (this will boot your device in fastboot)
(f) In terminal/cmd: fastboot oem unlock (or fastboot oem unlock-go)
(g) Now flash the custom recovery: fastboot flash recovery "recovery.img"
***I suggest you try first if the custom recovery image works: fastboot boot recovery.img
(h) Reboot into recovery and check if it works.
Click to expand...
Click to collapse
But how about a person WITHOUT PC? Including me.
So, if I completely wipe the storage of an android device, would I still be able to enter the Fastboot?
Is fastboot the same thing like bios? Where is fastboot-programm storaged?
Can I actually break the fastboot funktion somehow?
I also would be thankful if you just give me some good links. Thanks.
@GoFurthAndDie
1.
The BIOS of an Android device is the BOOTLOADER.
2.
In Android, FASTBOOT is a special diagnostic and engineering protocol that you can boot your Android device into. While in FASTBOOT, you can modify the file system images from a computer over a USB connection (AKA ADB ).
FASTBOOT is three different things with the same name:
A protocol for communication between your phone hardware and a computer
A software that runs on the phone when in fastboot mode
The executable file on the computer you use to make them talk to each other
3.
FASTBOOT is a Windows app.
jwoegerbauer said:
@GoFurthAndDie
1.
The BIOS of an Android device is the BOOTLOADER.
2.
In Android, FASTBOOT is a special diagnostic and engineering protocol that you can boot your Android device into. While in FASTBOOT, you can modify the file system images from a computer over a USB connection (AKA ADB ).
FASTBOOT is three different things with the same name:
A software that runs on the phone when in fastboot mode
The executable file on the computer you use to make them talk to each other
3.
FASTBOOT is a Windows app.
Click to expand...
Click to collapse
First thing, thank you very much for your answers.
Now I have an other question: if I use Fastboot to boot up TWRP and then use TWRP to wipe all data and all partitions from the intern storage of my android device and reboot it without flash any new ROMs (no /boot partition and all the other partitions), then my smartphone won't funktion any and won't be able to get into the fastboot mode on my phone.
If this happens, what could I do to make this smartphone functional again?
@GoFurthAndDie
Run
Code:
fastboot boot <<twrp.img>>
where <<twrp.img>> is replaced with your TWRP image name. This will boot you back into TWRP and should allow you to use TWRP to install a stock recovery and system partition.
Alternately, run
Code:
fastboot flash recovery <<twrp.img>>
to flash TWRP back to your recovery, and boot into recovery normally.
Hello I have a xiaomi mi mix 3 5g that I never removed the bootloader on, as it had the stock EU firmware on. It has recently been updated to to MIUI12. however the battery went low and went all weird and now constantly reboots.
I can get to fastboot by holding down the power and volume down, I have also tried a wipe device by holding down the power and up. From what I have read I i cant re-install fastboot firmware without and unlocked bootloader. (can someone confirm that this is correct) as its not clear.
***I have now confirmed this I have tried to install firmware using xiaomi flash tool and fails with the following
"Error: erasing boot Failed remote erase is not allowed in locked state. so this confirms it.
Also I cant unlock the bootloader as it wont boot. Does any body have any idea of what I can do with this phone? any help would be apprciated
thanks
The error I get when trying the mi unlock tool
Couldn't Unlock
Please add your account in MIUI;s Settings > Developer options > Mi Unlock Status
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
jwoegerbauer said:
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
Click to expand...
Click to collapse
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
sivhead said:
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
Click to expand...
Click to collapse
How to flash firmware to any Xiaomi smartphone is described here.
jwoegerbauer said:
How to flash firmware to any Xiaomi smartphone is described ["]here[/url].
Click to expand...
Click to collapse
I have already tried that method When I flash using the flash tool I get the error "Error: erasing boot Failed remote erase is not allowed in locked state" My bootloader is not unlocked is this method supposed to be work with a locked bootloader. Bit of chicken and egg situation. I cant unlock the bootloader as I cant boot the device and I cant reflash software as I don't have an unlocked bootloader.
AFAIK you always are allowed to flash an original firmware image without unlocking the phone's bootloader.
If you can access the device by means of ADB try to flash the Stock ROM via ADB:
Code:
adb devices
adb reboot sideload
adb sideload <LOCATION_OF_STOCK_ROM_ZIP_FILE_HERE>
C:\adb>adb devices
List of devices attached
f625af1 sideload
C:\adb>adb sideload miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip
loading: 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip'
* cannot read 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip' *
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
jwoegerbauer said:
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
Click to expand...
Click to collapse
tried that same error cannot read rom.zip
sivhead said:
tried that same error cannot read rom.zip
Click to expand...
Click to collapse
C:\adb>adb sideload c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip
loading: 'c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip'* failed to read command: No error
I also thought its worth mentioning that I have never registered the device with mi connect
Also enable usb debugging is not enabled.
aqnd THe bootloader is locked .
Man I wish I would have unlocked the bootloader when I got it and put a custom rom on. then I wouldnt be in this situation. how ironic that I wanted to keep it stock
so I am at a loose end
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.
hi guys, i have a problem let me explain to u what heppened and all stuffs
(my phone is redmi 9)
firstly i decided to install a custom rom and i've unlock the bootloader and i suffered in this step and then i flahsed recovery with pixel experience recovery but when i enter to recovery mode the device just reboot then i flashed recovery with twrp, i try to enter to recovery but system declins and i tried many time and finally i get into twrp, i wiped cach and i wiped all thing in list (i didnt remember but i deselect only sd card and otg maybe the problem was here and im newbie btw) and the wipe process successed, i tried flash rom with adb sideload but proccess failed idk why after that i tried flash recovery with shrp from fastboot but when i enter to fastboot using volum down + power off the fastboot still active for 5secs and exit i tried to boot into this recovery but when u complete the first step (i forget the name) but the output was like this:
[xxxxxxx]: 2.001sec
[booting]: (no input device)
command error
in booting step the fastboot exit and then when i tried many times i did this command: fastboot reboot fastboot
after this the device cant get into recovert mode or fastboot mode (when i try enter to fastboot mode the phone shows redmi logo and close immediaty 1sec or less) (system now is destroyed and i try to boot into os the phone stuck on redmi logo)
there is any way to enter to fastboot mode in this situation? i need help plz and thanks
also sorry for bad english
BESHIZUMOTO said:
hi guys, i have a problem let me explain to u what heppened and all stuffs
(my phone is redmi 9)
firstly i decided to install a custom rom and i've unlock the bootloader and i suffered in this step and then i flahsed recovery with pixel experience recovery but when i enter to recovery mode the device just reboot then i flashed recovery with twrp, i try to enter to recovery but system declins and i tried many time and finally i get into twrp, i wiped cach and i wiped all thing in list (i didnt remember but i deselect only sd card and otg maybe the problem was here and im newbie btw) and the wipe process successed, i tried flash rom with adb sideload but proccess failed idk why after that i tried flash recovery with shrp from fastboot but when i enter to fastboot using volum down + power off the fastboot still active for 5secs and exit i tried to boot into this recovery but when u complete the first step (i forget the name) but the output was like this:
[xxxxxxx]: 2.001sec
[booting]: (no input device)
command error
in booting step the fastboot exit and then when i tried many times i did this command: fastboot reboot fastboot
after this the device cant get into recovert mode or fastboot mode (when i try enter to fastboot mode the phone shows redmi logo and close immediaty 1sec or less) (system now is destroyed and i try to boot into os the phone stuck on redmi logo)
there is any way to enter to fastboot mode in this situation? i need help plz and thanks
also sorry for bad english
Click to expand...
Click to collapse
Flash the device using SP Flash tool if your device has MEDIATEK G80 processor.
mvikrant97 said:
Flash the device using SP Flash tool if your device has MEDIATEK G80 processor.
Click to expand...
Click to collapse
i will try it now ty
mvikrant97 said:
Flash the device using SP Flash tool if your device has MEDIATEK G80 processor.
Click to expand...
Click to collapse
its require boot device in fastboot or no? cuz i cant access to fastboot
BESHIZUMOTO said:
its require boot device in fastboot or no? cuz i cant access to fastboot
Click to expand...
Click to collapse
Redmi 9 brick problem solution.
1.if you are above v11.0.8.0 then go and follow below link... https://forum.xda-developers.com/t/disable-authorization-and-unbrick-your-redmi-9.4228213/ ================================== 2.Else follow it...
forum.xda-developers.com