So I last time when I flash XiaoMi Mi4i I do not know why the phone seems to to bricked.
What I mean brick is :
No respond when pressing power button.
When charging no LED light.
No Recovery (Volume + and Power)
No Fastboot (Volume - and Power)
Today I manage to read a thread tha use the following instruction to save the XiaoMi Mi4i.
1. Download the Fastboot ROM.
2. Install XiaoMi Mi Flash.
3. Restart computer and disable driver signature verify.
4. Flash like normal.
The flashing process take about 720 second, The result is successful but the phone wont turn on itself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I try to unplug it and press the power button. No response at all then I plug into a wall powered charger the phone show me the Mi logo then turn off the screen with a red LED blinking again and again until I unplug the phone from the power sources. This happen also when I plug the phone into the computer via USB.
The good news is that I can now enter Fastboot mode. ( I assume that my device came back from brick) but no recovery menu. I then connect the phone in Fastboot mode to the computer via USB then flash the ROM again just like normal. The result success but the phone won't power on itself so I press the power button and nothing happen.
Then
I plug into a wall powered charger the phone show me the Mi logo then turn off the screen with a red LED blinking again and again until I unplug the phone from the power sources. This happen also when I plug the phone into the computer via USB.
Click to expand...
Click to collapse
just like a moment ago.
Anyone that can help me ?
Did you try with the other fastboot version?
faizauthar12 said:
Did you try with the other fastboot version?
Click to expand...
Click to collapse
Nope but in MIUI forum there is no one complaining about the version.
ic3tea said:
Nope but in MIUI forum there is no one complaining about the version.
Click to expand...
Click to collapse
I would suggest using a MIUI 7 fastboot ROM. And a global stable one over a developer build. I ran into problems like no wifi / mobile network once, always I tried to flash the developer fastboot ROM. But once I flash a stable ROM everything was okay. Then I could easily go back to the developer ROM.
Try this,
Version: V7.2.3.0.LXIMIDA
sharan.nyn said:
I would suggest using a MIUI 7 fastboot ROM. And a global stable one over a developer build. I ran into problems like no wifi / mobile network once, always I tried to flash the developer fastboot ROM. But once I flash a stable ROM everything was okay. Then I could easily go back to the developer ROM.
Try this,
Version: V7.2.3.0.LXIMIDA
Click to expand...
Click to collapse
Will try and update you back .
Related
Yesterday I run out of battery for 2 hours, when I put some i got stuck on the LG logo, and the touchable keys start to blink.
As normal I tried to log in in Recovery via AmonRa 2.2.1 but it makes me log on Emergency Mode. I tried KDZ Update but when it reebot after flash the new rom I get stuck on the same problem. What can I do?
That's the error that appear to me when I try to update bu KDZ:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some additional information:
I tried to use the fastboot too, but it dont work as well...
Do not appear the message that makes me able to install a recovery for exemple. I looked on my ADB Interface driver and it says that it didn't reconize my device.
So... I can't fastboot too..
Is this a hardware problem?
GabrielJMC said:
Some additional information:
I tried to use the fastboot too, but it dont work as well...
Do not appear the message that makes me able to install a recovery for exemple. I looked on my ADB Interface driver and it says that it didn't reconize my device.
So... I can't fastboot too..
Is this a hardware problem?
Click to expand...
Click to collapse
shutdown and press the button combo you use to get into custom recovery for P350 (like in my P500 case, its POWER + VOL DOWN + HOME)
This will hard reset your phone, as after every KDZ flashing, you must hard reset your phone or it will bootloop, as in your case it is
I hope you get it.
DJoptimus-One said:
shutdown and press the button combo you use to get into custom recovery for P350 (like in my P500 case, its POWER + VOL DOWN + HOME)
This will hard reset your phone, as after every KDZ flashing, you must hard reset your phone or it will bootloop, as in your case it is
I hope you get it.
Click to expand...
Click to collapse
When i try to go on Recovery Mod by pressing (VOL DOWN+PHONE+ENDCALL) the Custon Recovery do not appear, i get stuck on the LG Logo and start blinking...
Ohh, I forgot to thank you for your awnser.
GabrielJMC said:
Yesterday I run out of battery for 2 hours, when I put some i got stuck on the LG logo, and the touchable keys start to blink.
As normal I tried to log in in Recovery via AmonRa 2.2.1 but it makes me log on Emergency Mode. I tried KDZ Update but when it reebot after flash the new rom I get stuck on the same problem. What can I do?
That's the error that appear to me when I try to update bu KDZ:
Click to expand...
Click to collapse
facing the same problem!!!!
Hi All
I am also facing the same issue
Is this a hardware issue ?
Thanks in Advance
I did flash the lollipop alpha. Realizing that there's nothing much I can do I decided to go back for CM11S. During the process I re root the phone try to flash the CM11S. And after finished flashing the phone won't boot up (even with any combination of buttons). My computer didn't pick up the phone as well. Does this mean that my One+ is bricked? Is there any solution?
Please help
My OnePlus screen never turn on after this happen to me. All the response from the phone was vibrates. Vol up/ down + power, I tried everything, but only vibrate and nothing happen after that.
If there's any help I would appreciate!!!!
Have you tried this? https://forums.oneplus.net/threads/...-solution-to-all-kinds-of-soft-bricks.142870/
Also, when you try to boot into fastboot, it does vibrate, right? Your computer should acknowledge the device is connected if that's the case.
TigerDNA said:
Also, when you try to boot into fastboot, it does vibrate, right? Your computer should acknowledge the device is connected if that's the case.
Click to expand...
Click to collapse
I have the same exact problem. My computer is acknowledged that the phone is being connected, it makes a classic windows sound of connected device into USB. But visual notification is not there as well as there is no new device displayed in the system. This just happens when I try to fastboot (power on + up button).
poisongas said:
I did flash the lollipop alpha. Realizing that there's nothing much I can do I decided to go back for CM11S. During the process I re root the phone try to flash the CM11S. And after finished flashing the phone won't boot up (even with any combination of buttons). My computer didn't pick up the phone as well. Does this mean that my One+ is bricked? Is there any solution?
Please help
My OnePlus screen never turn on after this happen to me. All the response from the phone was vibrates. Vol up/ down + power, I tried everything, but only vibrate and nothing happen after that.
If there's any help I would appreciate!!!!
Click to expand...
Click to collapse
Same here and my computer wont pick it up as a device. Ill keep tinkering/searching but if anyone has any ideas I would love to be a guinea pig.
Tidy_wave said:
I have the same exact problem. My computer is acknowledged that the phone is being connected, it makes a classic windows sound of connected device into USB. But visual notification is not there as well as there is no new device displayed in the system. This just happens when I try to fastboot (power on + up button).
Click to expand...
Click to collapse
You should still be able to push to the phone even if nothing is on the screen.
Even if it doesnt pick up the device on the computer or in cmd?
Check this post for a solution :
https://forums.oneplus.net/threads/s...us-one.104943/
start from "HERE IS THE SOLUTION"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
shadsilvs said:
Even if it doesnt pick up the device on the computer or in cmd?
Click to expand...
Click to collapse
It did pick up as this one
TheManDroid said:
Check this post for a solution :
start from "HERE IS THE SOLUTION"
Click to expand...
Click to collapse
Will give you the resolve asap. I'm following step by step finger cross!!!!!!
You need to install the right drivers so that you can use the Msm8974DownloadTool
Hi guys,
Today I pull out my mix 2s from the charger and I had a black screen. When I press the power button the screen flickers, but goes black.
I have the bootloader locked and no USB debugging active.
I'm able to boot in fastboot (always with black screen)
And somehow I think I've managed to reset the phone (key combination withing the xiaomi recovery)
For a second I was able to see the xiaomi boot logo while connecting the phone to the pc, but it went black again..
I've tried the xiaomitool (but no USB debugging)
Xiaomi PC suite does not detect the phone
MI flash tool says it cannot flash with locked phone...
Do you have any other idea?
Sent from my MI 6 using Tapatalk
you could try to use fastboot image to flash?!
http://update.miui.com/updates/v1/fullromdownload.php?d=polaris&b=F&r=cn&n=
futureshock said:
you could try to use fastboot image to flash?!
http://update.miui.com/updates/v1/fullromdownload.php?d=polaris&b=F&r=cn&n=
Click to expand...
Click to collapse
Unfortunately when I try, it says that I don't have permission to do so...
Also I've figured out that if I leave the phone alone for like 8h when I turn it on I get to see the xiaomi logo followed by a blank screen...
What could this be?
Sent from my MI 6 using Tapatalk
i would guess something is messed up with the system… doesn't look like the screen is bricked or something… do you get into the fastboot loader mode? press and hold power and volume down.... normaly you should see the fastboot "logo" then..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
eventually you can use minimal adb and clean/format everything and reflash ah new rom
http://forum.xda-developers.com/showthread.php?t=2317790
Im able to boot in fastboot and sideload, but always with a black screen
i dont have unlocked bootloader neither usb debugging active
After all it is a screen issue...
In order to empty the battery (i wanted to try to circle the battery, maybe it would help with issue) I pressed the power button straight and the phone kept rebooting (vibrating each time it reboots)
At the 5th reboot.. The screen went on. (it's like the hardware is forced to work somehow)
However the touch was not working..
After a few minutes the screen started to flicker and it completely distorted the screen image.
Now, after the 5 reboots the screen comes on but with a distorted image.
I'll send it back and ask for a refund.
Thanks.
Sent from my MI 6 using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was figuratively about to load lineage os in twrp when my gf asked me to give her mate a lift. so i left phone on thinking nothing of it then came home to this... there was almost some domestic abuse...lol
you cannot boot into download mode anymore?
I'm bricked too but it's very much worse than that I have completely black screen. But phone still responds to the Computer in device manager. Comes up with MediaTek driver. I have libusb installed. Not sure what to do. I have the A125U model.
LR7875 said:
you cannot boot into download mode anymore?
Click to expand...
Click to collapse
no doesnt respond to buttons at all, boots up then samsung then that screen. i might have to take it apart, i have the tools.
YerBallix said:
no doesnt respond to buttons at all, boots up then samsung then that screen. i might have to take it apart, i have the tools.
Click to expand...
Click to collapse
usb bugging isnt on so cant flash stock rom or anything
YerBallix said:
usb bugging isnt on so cant flash stock rom or anything
Click to expand...
Click to collapse
FIXED GOT INTO DL MODE, loading stock rom, phone in prenormal state now though better than brick
YerBallix said:
no doesnt respond to buttons at all, boots up then samsung then that screen. i might have to take it apart, i have the tools.
Click to expand...
Click to collapse
was trying to enter dl mode with power on, don't laugh im new to this
YerBallix said:
FIXED GOT INTO DL MODE, loading stock rom, phone in prenormal state now though better than brick
Click to expand...
Click to collapse
so you can now boot into android? you can do not turn off device and connect to internet for 7 days for the rmm to turn normal
I still haven't figured out how to get mine out of bprom mode
LR7875 said:
so you can now boot into android? you can do not turn off device and connect to internet for 7 days for the rmm to turn normal
Click to expand...
Click to collapse
I was able to get out of prenormal instantly, but I have a google
YerBallix said:
I was able to get out of prenormal instantly, but I have a secure google
Click to expand...
Click to collapse
You bought it 2nd hand? Can you delete your Google account from your phone?
Yr phone should (always) be able to enter download mode.
Just press power + vol down with USB (connected to PC) and turn of, then power + vol up untill download mode starts.
As said, it'll always start download mode.
There you can just flash repair Firmware in ODIN and get it back to "pre"normal working state.
edward0181 said:
Yr phone should (always) be able to enter download mode.
Just press power + vol down with USB (connected to PC) and turn of, then power + vol up untill download mode starts.
As said, it'll always start download mode.
There you can just flash repair Firmware in ODIN and get it back to "pre"normal working state.
Click to expand...
Click to collapse
No download mode. It's currupt or something. Stays in vcom no matter what I flash successfully. Verified boot is enabled. I'm not sure what I'm doing wrong. I've always flashed my mediatek devices successfully eventually but they never actually flash if you know what I mean. Flashing the preloader doesn't give me download mode back.
Hello guys,
I need your help.
Yesterday, my phone hangged and got stuck at Qualcomm Crash Dump mode.
I was just able to enter Fastboot (Power + Volume down button) but it won't wipe date, reset to factory or enter any other mode, it would just get black and do nothing, without possibility to launch the OS.
So, I used MsmDownloadTool to reformat it with the enchilada_22_H.07_180513 ROM.
The tool succeded to download the firmware to the phone but now, when I power it on, it just go directly to fastboot and whatever I do (Start, Recovery mode, Restart bootloader), it restarts directly in fastboot mode.
The problem is my device is not unlocked (I never rooted it) so I can't use the command "fastboot oem unlock"...
Due to the use of MsmDownloadTool, I know that I won't be able to recover the data but I would like to know if there is any possibility to make the phone usable again.
Try using different versions of MSM, I used the one which had OOS 5.1.5 and it successfully booted after it showed success in MSM
Thanks for your answer.
Problem is I can't use MSM as my phone is not detected anymore. It automatically boots on fastbood mode when I plug it on my computer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I only see the "OnePlus Android Bootloader Interface" now.
I don't see the COM port "Qualcomm device" as before using MSM.
kimery52 said:
Thanks for your answer.
Problem is I can't use MSM as my phone is not detected anymore. It automatically boots on fastbood mode when I plug it on my computer.
View attachment 5665639
I only see the "OnePlus Android Bootloader Interface" now.
I don't see the COM port "Qualcomm device" as before using MSM.
Click to expand...
Click to collapse
Try this:
when in fastboot mode power off the device from there and wait for 10-15 seconds once powered off then, hold the volume up button for 5-10 seconds and as you are holding it, connect your device to USB, let me know if this works or not
Ok, I will try it sunday and 'll tell you.
shank1524 said:
Try this:
when in fastboot mode power off the device from there and wait for 10-15 seconds once powered off then, hold the volume up button for 5-10 seconds and as you are holding it, connect your device to USB, let me know if this works or not
Click to expand...
Click to collapse
That manipulation works as you expected.
I'm gonna try with OOS 5.1.5 and will tell you.
kimery52 said:
That manipulation works as you expected.
I'm gonna try with OOS 5.1.5 and will tell you.
Click to expand...
Click to collapse
that's cool! I hope it works.
Hum.. doesn't seem to work...
Tried with enchilada_22_O.09_180517 ROM but when it completes the download, it just boots with the OnePlus logo (photo) then keeps black with the cyan LED light.
Is there a way for me to diagnose what's wrong ?
kimery52 said:
Hum.. doesn't seem to work...
Tried with enchilada_22_O.09_180517 ROM but when it completes the download, it just boots with the OnePlus logo (photo) then keeps black with the cyan LED light.
View attachment 5667693
Is there a way for me to diagnose what's wrong ?
Click to expand...
Click to collapse
you know, this usually happens with me but not on this screen, you know the screen where it says "bootloader unlocked"(if it's unlocked), there's one glitchy line on the screen and when that line appears that means something's wrong and then the phone crashes to crashdump mode but usually I get out of it by simply pressing power button but it seems like the crashdump problem is different for everyone, so coming back to your problem either the flashing is going wrong or something is off, seems like even the only solution is not working for you, I can only suggest you to try it again but if even that doesn't work then I don't think there's any solution left.
PS. I hope that you are putting your PC/Laptop in test mode before performing MSM operations.