[HELP] Bricked Redmi Note 4 - Xiaomi Redmi Note 4 Questions & Answers

Hi! I think I hard bricked my Redmi Note 4. I tried to install Lineage OS 16, unlocked bootloader and installed TWRP. However, after installing the Lineage OS it keept boot looping. I did all the procedure of wiping davilk, data, cache and system, then went to install and I added this packages: Lineage OS 16, Gapps, Lineage SU addon, unlock_bootloader ZIP, Lazyflasher and Universal DM-Verity, ForceEncrypt.
After flashing it just turned off and now I cannot turn it on. I held power button for 5 minues, nothing. Can't enter fastboot, screen doesnt turn on at all. When I plug it to charger it blinks red notification light. When I connect it to the PC I hear the Windows 10 notification sound but Windows says it cannot recognize the device.
I'm desperate, I think I've tried everything. Please HELP!

If you have the Snapdragon version, try to put it in EDL mode (entering it with the test points, you have to remove the back cover) and reflash an official rom with Mi Flasher. Then you go from the beggining in order to install your custom rom.

I tried that but I can not make it to short the circuits. I followed this inctruction https://forum.xda-developers.com/redmi-note-4/help/xrn4-sd-4-gb-64gb-black-screen-flash-t3761858 but I can't get anything other than "Qualcomm HS-USB Diagnostics 900E". Idk if I need a special kind of metal to short it or maybe the pins are shown incorrectly. I have the Snapdragon version.

UmbraOG said:
I tried that but I can not make it to short the circuits. I followed this inctruction https://forum.xda-developers.com/redmi-note-4/help/xrn4-sd-4-gb-64gb-black-screen-flash-t3761858 but I can't get anything other than "Qualcomm HS-USB Diagnostics 900E". Idk if I need a special kind of metal to short it or maybe the pins are shown incorrectly. I have the Snapdragon version.
Click to expand...
Click to collapse
The pins shown are correct. Try with sharp scissors or a tiny plier. An option is a cable with solid core.. If you get "Qualcomm HS-USB Diagnostics 900E" you are ready to go to Mi Flash, there is no problem that "9008" does not show up..

I did it, this is what I get from MiFlash
{
"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"
}

UmbraOG said:
I did it, this is what I get from MiFlash
Click to expand...
Click to collapse
you get it imidiatelly or at the end? If you get it at the end, try to ignore it and start the phone.. Otherwise try changing at the right bottom of mi flasher to "clean all" and try again. Also i found something here at the k20 threads, you uncheck the check point from the condifuration of the mi flash..

Cleaning the checkpoint thing worked and MiFlash said the flash was successful, but the phone still doesn't turn on or give any signs of being alive. I guess the only hope now is to give it to repair when the whole covid thing ends. Anyways, thanks for helping me.

Related

[SOLVED] Repair hard-brick

Hello
I think I have hard-brick my smartphone. Issues are after some flash, it won't boot anymore. No MI logo, no notification light on, ... .
Configuration :
Redmi Note 4 [Snapdragon] 4GB 64GB Global Version
Windows 10 Pro x64
MIUI ROM Flashing Tool
MIUI ROM Redmi Note 4 Qualcomm Latest Global Developer Version Fastboot File Download
I am not responsible from any damages.
Open SIM card tray with ejector tool :
{
"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"
}
Open from bottom, left, right, top with tools :
Unconnect battery :
Wait 10 sec.
Plug USB side cable into laptop.
Test point method with tool catchs circles and plug micro-usb into smartphone :
If you read Qualcomm HS-USB Diagnostics 900E, it is not ok, retry previous step.
If you read Qualcomm HS-USB QDLoader 9008, it is ok, go next step :
Launch MiFlash, select mido_global_images folder, click refresh, device appears into list, select clean all on bottom (flash_all.bat), click flash, wait until result success.
Remove micro-USB.
Mount battery cache, top, bottom, left, right side.
Insert sim tray.
Power smartphone and configure it.
Enjoy
billcat74
Sorry for refresh but in MiFlash when I press "refresh" it can't find my phone I have Qualcomm HS-USB QDLoader 9008 but I have error like
It even dont show thinking on display
When i flash it stopped with error can't receive hello packet
Please help asap
flashing problem
works as described until the middle of step 7 when I hit 'flash' it tries to "ping target via firehose" for 20s and then returns "write timeote,maybe device was disconnected" and "error"
Tried repeating with different cables and different ports with the same results.
Any tips on troubleshooting / moving forward beyond this point would be very appreciated.
Thank you for this guide and your efforts
Worked for me!
Thanks a lot man. I was able to revive my mido.

Hard Bricked brand new Xiaomi Mi Pad 3. Please help!!

So, I've bought a Xiaomi Mi Pad 3 with a Chinese Rom, and I was following a tutorial to flash a new rom into it.
I basically did the following:
Installed MediaTek Drivers on PC
Opened "Smart Phone Flash Tool"
Specified Download-Agent as DA_SWSEC.bin and Scatter-loading File as the ROM
Unchecked preloader and clicked on "Download"
Connected the Xiaomi Mi Pad 3 to the computer while pressing Volume Down
Then, at this point, the computer crashed with a blue screen of death with the error "BUGCODE_USB_DRIVER". Here is the diagnosis of the error:
{
"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"
}
After that, the Mi Pad won't turn on, won't respond to any button and is not recognized by the computer.... I think I might have hard-bricked it.
I've found a tutorial about recovering a Mi Pad 1, but one of the steps is to make a bridge in the SD Card slot, which Mi Pad 3 don't seem to have.
I'm a developer myself, I know my way on things, I have a VM Linux, I'm willing to open the tablet and do whathever it costs to recover it.
Please, what can I do??
Please, anyone?
I FUC*ING RECOVERED MY FUC*ING TABLET. FUC* YEAH!!!!!!!!!!!!!!
I don't know exactly what it was, but I kinda did the following:
- Installed the latest SP Flash tool from spflashtool.com on my PC
- Installed Mi PC Suite for drivers and such
- To help debug, I had a freeware called "Free Device Monitoring Studio", to better understand what's going on on my USB ports
- I was playing a little with the connection/desconnection of the device on my computer, trying to understand how it was. I saw that Kali Linux running under Oracle VM kinda recognized it as a Mediatek device, but couldn't do anything else than that. With that info, my hopes went a little higher, because it wasn't completely dead after all.
- I opened Flash tool, configured it to used the same ROM and files I was using when I bricked it, because I'm pretty sure they weren't the cause of the brick and clicked "Download"
- Then I began messing with the tablet trying to make it be recognized by SP Flash Tool, upon turning it on and off and switching USB ports and connecting them directly to the motherboard USB ports instead of the frontal USB ports
- Then at one point it suddenly recognized and started downloading and flashing the new ROM. I faced some errors but with Format all + Download and having to disconnect/reconnect the batery to make it recognizable again and some little tweaks here and there, it ended up working.
My tablet is working fine now

[SOLVED ]I bricked my phone, help me :'(

I was installing root to my cell phone, the installation everything fine, but when I was installing the original recovery, I accidentally moved the USB cable and it was disconnected, it stayed in the red bar of the flash tool, I gave it in "stop" and try to do it again, now the sp flash tool does not recognize it, but windows recognize the device as "Mediatek DA USB VCOM (Android) (COMX)" where X is a number.
I've read through other topics that keep the Vol+ works, but it does not work with me, or I do not know if I'm doing it right.
I have not removed the battery because I do not know how to open the cell phone.
In the sh flash tool, I use: "Download Only"
Sorry for my english.
EDIT:
I open the phone, quit battery, put again, and sp flash tool detect the device again
leo318x said:
I was installing root to my cell phone, the installation everything fine, but when I was installing the original recovery, I accidentally moved the USB cable and it was disconnected, it stayed in the red bar of the flash tool, I gave it in "stop" and try to do it again, now the sp flash tool does not recognize it, but windows recognize the device as "Mediatek DA USB VCOM (Android) (COMX)" where X is a number.
I've read through other topics that keep the Vol+ works, but it does not work with me, or I do not know if I'm doing it right.
I have not removed the battery because I do not know how to open the cell phone.
In the sh flash tool, I use: "Download Only"
Sorry for my english.
EDIT:
I open the phone, quit battery, put again, and sp flash tool detect the device again
Click to expand...
Click to collapse
How did you manage to open the phone? When I tried it it felt like something was going to break.
MrGoatsy said:
How did you manage to open the phone? When I tried it it felt like something was going to break.
Click to expand...
Click to collapse
I watch the next videos:
To open cellphone: (flat screwdriver and a pair of tweezers, look for a screwdriver as flat as possible, see the images)
https://youtu.be/l-KxuFfv7rk?t=2m26s
{
"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"
}
Quit Battery:
https://www.youtube.com/watch?v=4ehYF-zFDAo

Unbrick Meizu M6 Note M721H

Hello,
i'm new in the forum, i have problem with Meizu M6 Note M721H because i have installed twrp recovery with app crack (3.2.1) and next i have deleted SO (flyme firmware) and i have cleaned the phone, after i have updated twrp to 3.2.2-0 version and after reboot, after 1-2 seconds of meizu logo the screen becomes black and the twrp doesn't start....and i haven't firmware installed...fastboot mode working but i haven't permissions because bootloader is locked and secured. I can't use well QFIL.exe and after after I Have entered the files in the program and start download, i have the issue: "Download Fail: Switch to EDL FailFailed to Switch to Emergency Download mode". I tried everything, could you help me?
{
"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"
}
Maybe this can help you to fix that error.
https://geekofia.wordpress.com/2017/10/12/download-failswitch-to-edl-failfirehose-fail-fixed/
MatteoGhost07 said:
Hello,
i'm new in the forum, i have problem with Meizu M6 Note M721H because i have installed twrp recovery with app crack (3.2.1) and next i have deleted SO (flyme firmware) and i have cleaned the phone, after i have updated twrp to 3.2.2-0 version and after reboot, after 1-2 seconds of meizu logo the screen becomes black and the twrp doesn't start....and i haven't firmware installed...fastboot mode working but i haven't permissions because bootloader is locked and secured. I can't use well QFIL.exe and after after I Have entered the files in the program and start download, i have the issue: "Download Fail: Switch to EDL FailFailed to Switch to Emergency Download mode". I tried everything, could you help me?
Click to expand...
Click to collapse
what do you mean you deleted "SO"?
if i understand correctly you replaced stock recovery with twrp but it can not load because your bootloader is locked.
i am not very well familiar with qfill but you are having wrong port open "900E" . you need to enable "9008".
try if this trick works https://www.youtube.com/watch?v=fOpZsUQwOrY
fortunately i have the same problem, same phone, unfortunately you need to open it up, as i understand there are some circuits you need to shortcircuit to load the fastboot, looking into this now, will post updates
And how did someone solve a black screen problem after TWRP botting? I have the same problem and I can not deal with it; /
master2007 said:
And how did someone solve a black screen problem after TWRP botting? I have the same problem and I can not deal with it; /
Click to expand...
Click to collapse
hold down the power button for 20 seconds?
Assuming you still have an the Android OS installed.
Unbrick Meizu M6 note
Hello, why don't you try to flash it with qfil rom?

Question Fastboot is not detected in device manager

Hi, I decided to unlock bootloader on my Xiaomi Mi 11 Lite 5G NE. I downloaded Mi Unlocker, and did everything as it was described on the internet: enabling debugging functions, unlocking OEM, logging to Mi Account etc, installing all required drivers etc. The problem is that after entering fastboot mode there's literally no device in Device Manager associated with my phone, so neither Mi Unlocker, nor fastboot can detect my phone. I tried reinstalling drivers, restarting PC, changing cables, ports, different version of adb, fastboot, and MI Unlocker with no result.
One thing that helped (but only for a minute) was doing factory reset, and then fastboot mode image changed to some older one, and then it appeared in device list, and Mi Unlocker detected it, but sadly there was an error saying "Couldn't verify device", and then fastboot exited, and after rebooting previous (newer) image appeared, and problem was back. Then I thought: hey, maybe I have too old system? So I upgraded it to MIUI 13, and now the problem is still there, but fastboot image has been reduced to only barely visible label.
Maybe I'm using obsolete drivers? Maybe you have some recent drivers, or maybe I should try another PC/linux booted from pen?
install mi pc suite 3.2.1.3111 for the drivers and check in windows/peripherals if drivers are corrected installed
Nope, it didn't help. I forgot also to mention, that phone is discoverable by adb, and I can execute adb reboot bootloader without any problems
Try (with minus - there are two diff modes):
adb reboot-bootloader
The same thing happens FASTBOOT label, and no device is detected.
Any other advices? I tried with Linux, but with the same results
Okay it's strange, but now I tried logging in to my Google account and switching most of debugging options in developer settings to on, and now it appeared as fastboot device after reboot, and I was able to unlock it
But now, unfortunately, when I wanted to flash something to phone, then fastboot disappeared again - wtf is going on?
Have you tried a different USB cable?
fibur said:
But now, unfortunately, when I wanted to flash something to phone, then fastboot disappeared again - wtf is going on?
fibur said:
But now, unfortunately, when I wanted to flash something to phone, then fastboot disappeared again - wtf is going on?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I can help you! Please check PM.
mvikrant97 said:
I can help you! Please check PM.
Click to expand...
Click to collapse
{
"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"
}
Okay, the issue was broken USB port, now it works perfectly

Categories

Resources