Hello Team,
I was flashing stock rom (fastboot) via mi tool and then i got some error, i opened CMD and pushed reboot (to recovery) command.
This was the very moment i lost all the control, the device was not responding to anything.
Cannot see startup screen, recovery or bootloader
1} Plugged into computer no luck (tried everything)
2} Tried removing and re installing the battery no luck
3} Last try left was EDL but that is also not working
There is one more technique i want to try which is ** grounding isp pin** but i do not have more information about the motherboard.
Can anyone help ?
Thank you
Related
Dear All,
I bought a Mi max 2 months ago, after using it some,i decided to change my rom.
What i did:
1)Unlock phone via mi
2)Usb debugger
3)TWRP
4)Supersu rooted
Everything was fine.
I downloaded a rom and flash it in fastboot mode and BUM! total darkness.
After some research , I managed to reach my phone via MiFlash.
Mi Flash now sees my phone as a port device Qualcomm....
I downloaded a correct rom.
So what is my problem !
In EDL mode,I start flashing, 2-3 seconds it flashes than it says `can not see port`(I downloaded all drivers,disable/able driver enfor...sth)
And phone turns in NULL mode, no connection any more from pc to phone.
If i disattached/attached battery and connect again to PC in EDL mode, i can reach it for a few seconds and than again losing connection.
I need my phone to keep connected to my pc untill i will finish flashing.
It is complicated, i am not even sure if it is possible or i damaged my motherboard.
What can i do???
Thanks in advance
Hi there,
as you all can read on the tittle, my device is softbricked (because my bad with backups and flash, sorry first time). I tried everything but open phisically the phone (that was my last option) and none of them worked. So I ask you for some ideas.
Here I´ll tell what still works on my devices, and what I´ve tried:
-When I power on the device, it appears the MI logo, then "The system has been destroyed" and at the end is shuts down again or reboot.
-I can access the recovery mode that was by default (MI Recovery 3), and I can Wipe Data (it starts, and when it´s almost 3% it shows as complete).
-I can access too fastboot, and ADB recognises it.
-I can flash TWRP (with Anti-rollback warning), but not boot it (it makes the devices to reboot, and after ~10s shows failed too many links).
-MIAssistant does not recognise my device (but the phone knows if I connect it to the computer).
-I am not able to unblock my device. It recognises my device, but at 99% makes me add my device in MIUI´s Setting > Developer options > Mi Unlock Status (I didn´t do it when my device worked, my bad).
-Tried to flash with MIFlash, but it keeps me with "flash xbl error". It recognises my devices though.
Any help would be very appreciate, and if you need any additional info, ask for it. If nothing works, I will go to a phone store to mae them open my device, so I can try one more thing.
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
devcon69 said:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
Click to expand...
Click to collapse
I really apreciate your help, but none of your options did something.
The MIFlash, as the previous time, showed "flash xbl error". The QPST, didn´t recogniced my port, so I couldn´t click "Download".
And yeah, my last option is to do a testpoint, but I would like to try every other option, rather than open my device.
Anyway, thanks for using your time on me.
I did not notice that you have a locked bootloader. Try MiAssistant or MiflashPro. Try flashing latest recovery rom.
https://forum.xda-developers.com/redmi-note-5-pro/how-to/tut-flashing-official-recovery-rom-t3798165
EDL is the last choice.
devcon69 said:
I did not notice that you have a locked bootloader. Try MiAssistant or MiflashPro. Try flashing latest recovery rom.
https://forum.xda-developers.com/redmi-note-5-pro/how-to/tut-flashing-official-recovery-rom-t3798165
EDL is the last choice.
Click to expand...
Click to collapse
Tanks for taking your time, but the solution propossed did not work. Every download link gave me an invalid rom (it asked for a 10.0.6.0), so I got the newest one on xiaomi website. It looked to work, but when the PC screen was at 99% and the device screen at ~50%, it suddenly finish. The device reboots, it shows the android logo too, even makes the sound where you have to enter your pincode (the device has not a SIM inserted), and eventually reboots to the recovery menu, showing on the bottom "This MIUI version can´t be installed on this device". Tried the slow mode (more pair the load, but still don´t work), tried other roms. Nothing.
At least it boots now to the revocery menu with "MIUI version..."
So I tried the testpoint to try EDL mode, and all correct but when I tried to flash the rom, everytime but the first one (with a strange log as ERROR) showed "Cannot receive hello packet". Every single rom.
So here I am, trying not to cry on my bed. I feel like **** for breaking my device in a week.
Hello everyone, a couple of months now are also thanks to you in the world of modding. Yesterday (i have a Xiaomi Mi A2 Lite) during the installation of a custom ROM using ADB, typing in the fastboot command "erase system", I wrote erase a_boot for error because before I was reading a post about it and I wrote it. Yes I know, I was too stupid. Result? The phone does not start up either in recovery or in fastboot mode, and from the PC it is recognized as COM port. I have already documented about it and tried to flash everything with the Qualcomm tool after installing the drivers but nothing. I tried the EDL by activating it manually to unlock port 9008, but still during the flash gives me error. I tried everything, do it all over again in a newly formatted and clean PC from any other driver, but nothing. During the flash, even if I put the firmware in the same directory, it still gives me error. Guys I'm desperate please. I do not know what else to do. I hope to receive your answers
YouKnowAirborne said:
Hello everyone, a couple of months now are also thanks to you in the world of modding. Yesterday (i have a Xiaomi Mi A2 Lite) during the installation of a custom ROM using ADB, typing in the fastboot command "erase system", I wrote erase a_boot for error because before I was reading a post about it and I wrote it. Yes I know, I was too stupid. Result? The phone does not start up either in recovery or in fastboot mode, and from the PC it is recognized as COM port. I have already documented about it and tried to flash everything with the Qualcomm tool after installing the drivers but nothing. I tried the EDL by activating it manually to unlock port 9008, but still during the flash gives me error. I tried everything, do it all over again in a newly formatted and clean PC from any other driver, but nothing. During the flash, even if I put the firmware in the same directory, it still gives me error. Guys I'm desperate please. I do not know what else to do. I hope to receive your answers
Click to expand...
Click to collapse
Try to flash stock rom with Mi Flash "64-bit"
Here is a link for 64 bit version: https://yadi.sk/d/cel5Nm2sE1OpMg
In EDL mode
YouKnowAirborne said:
Hello everyone, a couple of months now are also thanks to you in the world of modding. Yesterday (i have a Xiaomi Mi A2 Lite) during the installation of a custom ROM using ADB, typing in the fastboot command "erase system", I wrote erase a_boot for error because before I was reading a post about it and I wrote it. Yes I know, I was too stupid. Result? The phone does not start up either in recovery or in fastboot mode, and from the PC it is recognized as COM port. I have already documented about it and tried to flash everything with the Qualcomm tool after installing the drivers but nothing. I tried the EDL by activating it manually to unlock port 9008, but still during the flash gives me error. I tried everything, do it all over again in a newly formatted and clean PC from any other driver, but nothing. During the flash, even if I put the firmware in the same directory, it still gives me error. Guys I'm desperate please. I do not know what else to do. I hope to receive your answers
Click to expand...
Click to collapse
Hello,
If you use Windows write it in CMD in Adminastrator,
Code:
bcdedit /set testsigning off
After that try flash via MiFlash a stock rom. IMPORTANT, Select clean all only.
If this not work use a Deep Flash Cable,
- Shutdown your phone
- Connect the usb cable to your computer
- Start pressing the button
- Wait 10 seconds
- Connect the cable to your phone
- Wait 5 seconds
- Stop pressing the button
Normaly the led flash, You are in EDL mode
Flash a stock rom via MiFlash with clean all option.
To leave EDL mode you need to press on power button 20 seconds.
PS: Soory for my very bad English
Pierre
A BIG SORRY for a long post. But I am sure its worth reading step by step. Because many peoples are stucked in same situation, no straight forward solution for this issue is available till now. All solutions are based on 50/50 success ratio.
I think if my issue is resolved then it can become WORLD's FIRST SOLUTION to UNBRICK NOTE 5 PRO with 100/100 success ratio.
About Me: I am an ordinary Android user since years. I know how to root and install TWRP and Custom ROMs on any Android Phone. I am not a Developer, every thing discussed here is purely gained by experiments by playing with my phone.
After playing with my bricked phone I reach at a point where I am hopeless and I think at this stage a Developer can help me only, who have deep knowledge of android OS. That's why I called Devs to help me.
About Phone I have Note 5 Pro Global (whyred)M1803E7SG. Phone is under warranty but unfortunately Front Glass of my phone is broken few months ago but still working, so Mi Service Center refused to accept my phone under warranty due to broken Front Glass. Tried to repair my phone by a local Phone Service Shop, thay have all professional tools like UMT, Avangers, MedusaPro etc. but they were also unable to repair my phone. Now I have no option left other than I should repair it by myself.
Phone was on ARB4, was working fine. Bootloader Unlocked and I have rooted it long time ago and was playing with it since it is rooted by flashing different Custom ROMs on daily basis.
Currently phone was working fine on Masik X 4.1 ROM. Some days ago I flashed Masik X 5.0 ROM via TWRP on my phone and after reboot phone became dead and went to EDL 9008 mode. I noticed that I flashed Masik X 5.0 for Note 6 Pro (tulip) ROM on it mistakenly.
Journey Stats Here:
1 - After bricking my phone I tried to flash fastboot ROM for whyred in EDL mode, phone flashed successfully but still stucked in EDL mode. Tried all fastboot ROMs from ARB2 to ARB4 but still no sign of life, phone was not coming out of EDL mode. Also tried "test anti4.zip" files as well but phone is still in EDL mode after a successful flashing.
2 -After that I tried to flash fastboot ROM of Note 6 Pro (tulip) in EDL mode, after flashing complete when I tried to turn ON my phone, I noticed that phone try to start with vibrate and charging light blinks for a while but nothing on Screen and phone dead again. I checked with USB cable attached to laptop, nothing appear in Device Manager. Here I opened my phone and bring it to EDL mode via Test Point method.
3 - Then after searching on internet I saw on a forum where another person was in same situation. He mentioned his phone display was turning ON on a Mi 6X (wayne) ROM but with "Press any key to shutdown" message on screen. So tried same with Mi 6X (wayne) ROM. Phone is turning ON with "Press any key to shutdown". So I started playing with Mi 6X ROM. I started replacing Mi 6X ROM file with Note 5 Pro files one by one and flashing my phone again and again with every one new file (took so many hours in playing with my phone:crying. Initially had many issues like: missing keymaster64.mbn file as Mi 6X uses keymaster64.mbn but Note 5 Pro is using keymaster.mbn file (so corrected .xml and .bat files according to need), Unable to mount Persist partition in TWRP (corrected it by terminal method in TWRP by using command "make_ext4fs /dev/block/bootdevice/by-name/persist", phone was going to Fastboot for a while, Not going to recovery mode, No USB detection on laptop in Device Manager. Fastboot lasts for a half second and then phone goes off.
In short at the end finally I noticed only three files "abl.elf, pmic.elf, xbl.elf" from Mi 6X ROM are responsible for turning my phone ON.
4 - So I replaced "abl.elf, pmic.elf, xbl.elf" files from Mi 6X ROM with Note 5 Pro ROM files and flashed my phone with this new modified ROM in EDL mode. Phone turned on without any "Press any key to shutdown" message on screen. Now phone can go to fastboot mode and detected on USB on my laptop. But not going to Recovery mode, after pressing Vol UP + Power Button, only a black screen and nothing happening on my laptop Device Manager (no driver at all). In fastboot mode I flashed "PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL" recovery (initially I tried TWRP Recovery for whyred but in TWRP phone was not detected as MTP device on my laptop, so I used Pitchblack Recovery) and after issuing boot command to recovery.img I can go to Pitchblack recovery mode, phone detected on USB port as "Note 5 Pro", MTP drive appear in My Computer, I can copy/paste files in phone Storage. In Recovery mode I flashed Official "miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0" ROM. Phone flashed successfully but after reboot phone went to EDL mode again. So I revived it again with modified ROM.
5 - After revival I tried to boot phone in normal way, I noticed that MI Splash screen is blinking with behavior: Splash screen appears fine for a while and on second blink Screen is inverted then 3rd blink Screen fine and 4th blink screen inverted and so on till I reach to MIUI10 welcome screen. On welcome screen the behavior is same like once fine then inverted. But here my touch screen is not working, I can't go after this screen. Phone is not allowing to touch Next button. I can charge my phone with charger connected. Phone detected as "Note 5 Pro" on my laptop.
6 - I rebooted phone to fastboot mode, tried to flash "whyred_global_images_V10.3.1.0.PEIMIXM_20190522.0000.00_9.0_global_8201319a7e" with MiFlash but can't flash due to "Product Mismatch" warning by MiFlash. Tried Mi 6X ROM and MiFlash started flashing fine.
7 - Then I flashed "boot.img, recovery.img, cust.img, system.img" files by using fastboot flash xx xxx.img commands for Note 5 Pro. Fastboot flashed all files successfully. But after rebooting phone behavior is same like blinking inverted screen and touch not working.
8 - Now I am helpless at this stage. Tried all ways to revive my phone. Nothing else is remaining as I think. No other file is remaining which I can try.
HELP REQUIRED FROM A Developer
I reached on a stage where my phone is now "Semi Unbricked" but is still useless for me. But I hope some Developer can help me to revive my phone.
My Note 5 Pro is converted to Mi 6X but touch screen is not working. Screen is working fine in Pitchblack Recovery mode, phone is responding in Fastboot mode but as it is the fastboot mode of Mi 6X on a Note 5 Pro so it is useless for my phone.
Kindly assist me further so I can replace Mi 6X fastboot with original Note 5 Pro fastboot so that I can flash Note 5 Pro ROM on it.
Waiting for a very positive and prompt reply.
Regards!
Any body knows about display/touch driver files inside Android OS???
My touch screen is not working at all on MIUI Welcome screen. I want to embed Display Driver files in ROM so I can go forward ahead of this Welcome Screen.
I have tried so many ROMs from different Xiaomi models, replaced so many files one by one, spent too much time on doing this all. But the only combination of files works mentioned below:
abl.elf (must be from wayne ROM)
pmic.elf (must be from wayne or tulip ROMs, both working)
xbl.elf (must be from wayne ROM)
All other files from whyred ROM are OK to flash to bring my phone alive.
ROMs Used:
whyred_global_images_V10.3.1.0.PEIMIXM_20190522.0000.00_9.0_global_8201319a7e
wayne_images_V10.3.3.0.PDCCNXM_20190514.0000.00_9.0_cn_1d4725ac4d
tulip_global_images_V10.3.2.0.PEKMIXM_20190426.0000.00_9.0_global_2264f9bd86
Now I concluded all this mess as: I can never go back to whyred original ROM. The only way left is to use my phone as a Mi 6X by name if touch screen of my mobile gets start working.
Some body please help me in replacing Display Driver files of whyred with wayne files.
Kindly assist me to pass through this step. I want to see what's working and what's not after MIUI Welcome Screen. e.g. IMEI, BT, WIFI, SOUND, CALL etc......
Please help
How can I fix it without losing my data or at least make a backup
I have a question. I downloaded an update yesterday for Mi Max 3. The screen stayed black with the MI logo for hours. I tried the following but didn't work:
- Connecting to Mi PC suite, but it isn't recognizing the device.
- Downloaded many drives for the USB, but still the device is not being recognized.
- MiFlash recognize the device, but when I downloaded the Rom (both recovery and nitrogen) it is mentioned can't find file flash all.
- I tried to put some commands such as adb back up, but it informs me no device found.
- I tried to work whether on fastbot mode or without fastbot, without success.
I want to know what should I do, I don't want to lose the data on the phone.