Hi,
I am unable to boot into Recovery mode on my Redmi 1s.
Probably the recovery is corrupted and hence it is creating issues.
I tried using fastboot with MI Flash too, but the operation terminates with an error.
Brain storming since last 1 week on this.
please help me out on this.
Thanks in Advance.
you can try flashing another recovery with fastboot here's a tutorial
https://www.youtube.com/watch?v=z5ZyDsPfU1g
beginning of the vid is low quality but just skip till the screen recording part.
Sagar Dubey said:
Hi,
I am unable to boot into Recovery mode on my Redmi 1s.
Probably the recovery is corrupted and hence it is creating issues.
I tried using fastboot with MI Flash too, but the operation terminates with an error.
Brain storming since last 1 week on this.
please help me out on this.
Thanks in Advance.
Click to expand...
Click to collapse
Following is the TWRP recovery link:
https://twrp.me/devices/xiaomiredmi1s.html
If recovery is corrupted then reflash a new recovery using the bootloader(fastboot method).
If you are unable to eneter into bootloader or unable to flash the recovery via bootloader then yes it should be a matter of concern coz it is most likely your bootloader is corrupted.
Which is very rare.
Try flashing thru fastboot and let me know how did this endup.
my redmi 1s lcd display become half from right after boot logo..fastboot logo is full showing an boot animation also full showing. but after boot it become half ...
MI HM 1s
MIUI8
is there problem in hardware or in other pls help
hello, my mi6 suddenly dead, hard brick, can't enter to fastboot mode. Mi6 6/128 ceramic edition.
so i decided to open back covers and shortlink 2 pins it detect as qualcomm loader in mi flash, but when flashing fastboot rom it always show error " set boot partition 1 failed "
i tried many version of mi flash and use global stable, global dev, china stable, china dev fastboot rom but always ended in set boot partition failed..
i've searching lots of forum but can't found an answer for set boot partition failed error.
i also tried QPST for flashing with fastboot rom but also give error,
please help anyone have same problem with me? or any xiaomi engineer here? i just need how to solve flashing in mi flash with error set boot partition failed.
i hope no need to change/replace the hardware...
You can try to use XiaomiTool and flash your phone with instead.
https://www.xiaomitool.com/V2/
Also, have you tried fastboot boot recovery.img
To see if you can boot TWRP or something?
(fastboot boot might work better than flashing)
I don't have any experience with Miflash, so can't offer any advice on that.
Personally I would try fastboot boot first, since XiaomiTool is in alfa-version.
-Zteam- said:
You can try to use XiaomiTool and flash your phone with instead.
https://www.xiaomitool.com/V2/
Also, have you tried fastboot boot recovery.img
To see if you can boot TWRP or something?
(fastboot boot might work better than flashing)
I don't have any experience with Miflash, so can't offer any advice on that.
Personally I would try fastboot boot first, since XiaomiTool is in alfa-version.
Click to expand...
Click to collapse
thanks for replying.. my phone is dead can't boot to fastboot. only detect in edl mode. i think its problem with my partition being messed up (look from mi flash logs)
anyway i have tried to install xiaomitool v2 but i think it's not compatible yet with unbrick device it show error like this:
zilan said:
thanks for replying.. my phone is dead can't boot to fastboot. only detect in edl mode. i think its problem with my partition being messed up (look from mi flash logs)
anyway i have tried to install xiaomitool v2 but i think it's not compatible yet with unbrick device it show error like this:
Click to expand...
Click to collapse
it seems your Mi6 is alive again how was the solution?
DJ Regino said:
it seems your Mi6 is alive again how was the solution?
Click to expand...
Click to collapse
no , still dead.. :crying:
look into https://stackoverflow.com/questions/39906951/android-edl-mode-commands
zilan said:
thanks for replying.. my phone is dead can't boot to fastboot. only detect in edl mode. i think its problem with my partition being messed up (look from mi flash logs)
anyway i have tried to install xiaomitool v2 but i think it's not compatible yet with unbrick device it show error like this:
Click to expand...
Click to collapse
Sorry for my late reply, I had forgotten to answer this earlier, did you try to perform a regular flash (not bricked option) from XiaomiTool. if that doesn't work either, maybe you should ask the developer of XiaomiTool2 for hints.
Try mipcsuite chiese version, i saved my Mi6 when it showed penguin in the middle of screen, no fastboot nor recovery etc
HTCDevil said:
Try mipcsuite chiese version, i saved my Mi6 when it showed penguin in the middle of screen, no fastboot nor recovery etc
Click to expand...
Click to collapse
do you have a link? and what rom to use?
zilan said:
do you have a link? and what rom to use?
Click to expand...
Click to collapse
Is there any update? Did your phone recovered from that situation?
I am in the same situation with my Asus Rog 2. It has life sign only in edl mode and when I try to recover I ve got that error too "set boot partition failed" still dead.
zenhex said:
I am in the same situation with my Asus Rog 2. It has life sign only in edl mode and when I try to recover I ve got that error too "set boot partition failed" still dead.
Click to expand...
Click to collapse
u fix it?
zilan said:
hello, my mi6 suddenly dead, hard brick, can't enter to fastboot mode. Mi6 6/128 ceramic edition.
so i decided to open back covers and shortlink 2 pins it detect as qualcomm loader in mi flash, but when flashing fastboot rom it always show error " set boot partition 1 failed "
i tried many version of mi flash and use global stable, global dev, china stable, china dev fastboot rom but always ended in set boot partition failed..
i've searching lots of forum but can't found an answer for set boot partition failed error.
i also tried QPST for flashing with fastboot rom but also give error,
please help anyone have same problem with me? or any xiaomi engineer here? i just need how to solve flashing in mi flash with error set boot partition failed.
i hope no need to change/replace the hardware...
Click to expand...
Click to collapse
if you're still there, i resolve this issue.
you need to jump charge your battery using external charger ( external charger jumped wire direct on your battery). maybe for 30mins.
then try again to charge your phone, if it reapond and have display 0% battery, let it charge for atleast 50% then power ON.
If it stucks on logo.. do reflash.
I have a redmi note 5 pro/ai, and its now stuck in mi logo. I tried all tutorial in youtube, but it failed. When i flash it in fastboot, it say error and when it i flash in edl mode, cant read hello packet. What is the problem of my note 5???? No recovery, only fastboot... i tried all miflash version. please help me...
I can help you if you are indian, pm me
Soo, i was just trying to install TWRP on my Redmi 7 but my phone was freezed at "Redmi" screen, after many tried of flashing a fresh official rom into it, now im stuck with the phone at a black screen, i can't see anything but it is connected to my PC and i can see it at "MiFlash" Can someone please help me solve this problem? Ty!
Nuubsou said:
Soo, i was just trying to install TWRP on my Redmi 7 but my phone was freezed at "Redmi" screen, after many tried of flashing a fresh official rom into it, now im stuck with the phone at a black screen, i can't see anything but it is connected to my PC and i can see it at "MiFlash" Can someone please help me solve this problem? Ty!
Click to expand...
Click to collapse
Go to fastboot mode and flash twrp, after download the ROM stock in site (.zip) and flash.
Hello, as you can see from the title I accidentally hardbricked my phone and I got it to EDL mode through shorting the test points, but everytime I try to flash mi a2 lite firmware MiFlash gives a "Can't receive hello packet" error and then says "Object reference not set to an instance of an object". Perhaps I have the wrong firmware ? I don't know what to do after this point, I would really appreciate if somebody could help me solve this problem, thanks!