Hi,
I was trying to flash Lineage OS on my Whyred, and installed non-ARB ROM over MiUi 10 and my device is now bricked.
I can see my phone in EDL mode, as I can see "Qualcomm HS-USB QDLoader 9008" in the device manager.
I have also installed all the drivers from MiForum thread-784616-1-0. (I don't have right to post complete link)
Even after restart and power cycling the phone, my device does not show in MiFlash tool, and I get "Length cannot be less than zero. Parameter name: length" error. I have tried three different versions on MiFlash tool.
I am on Win10 64 bit
I have unlocked bootloader with TWRP installed before the brick happen.
EDIT:
I tried QFIL methods but it was unsuccessful.
Qfil tool detects the phone without issue, but flashing fails with the following error:
Code:
ERROR: Only nop and sig tag can be received before authentication.
1. none of the custom rom has ARB switched on! how did you brick your phone by flashing Linage??? I cannot understand
2. you cannot JUST go in to EDL mode with RN5pro since Xiaomi has removed the pressing volumes and power button 30 seconds to get in to edl mode! you have remove BACK PANEL of rn5p and short the testpoints with metal & plug the usb in with pc in order to ender edl mode!
3. even if you enter in edl more! miflash will ONLY flash if your MI account has been authorised from china!
now what exactly is your device state? can you reboot enter in fastboot mode?
fastboot roms cannot be placed in LONGGGG paramiters! put it in C drive and rename folders to smaller.. like C:\1 and put all the unzipped Tz files here to flash!
if you cannot flash by mi then you should consider Qualcom Qfil flasher! , RN5p is snapdragon device and can be flashed with QFIL!
YasuHamed said:
1. none of the custom rom has ARB switched on! how did you brick your phone by flashing Linage??? I cannot understand
2. you cannot JUST go in to EDL mode with RN5pro since Xiaomi has removed the pressing volumes and power button 30 seconds to get in to edl mode! you have remove BACK PANEL of rn5p and short the testpoints with metal & plug the usb in with pc in order to ender edl mode!
3. even if you enter in edl more! miflash will ONLY flash if your MI account has been authorised from china!
now what exactly is your device state? can you reboot enter in fastboot mode?
fastboot roms cannot be placed in LONGGGG paramiters! put it in C drive and rename folders to smaller.. like C:\1 and put all the unzipped Tz files here to flash!
if you cannot flash by mi then you should consider Qualcom Qfil flasher! , RN5p is snapdragon device and can be flashed with QFIL!
Click to expand...
Click to collapse
I don't know how it got bricked AFTER installing Lineage OS.
Current situatiuon
1) Mi Flash tool does not list/detect my phone even though I am in EDL mode.
2) Qfil tool detects the phone without issue, but flashing fails with following error:
Code:
ERROR: Only nop and sig tag can be recevied before authentication.
Did you try this method?
[email protected] said:
Did you try this method?
Click to expand...
Click to collapse
Yes, and the above error is after trying this method.
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
I hard bricked my phone (realme 3) yesterday, by flashing boot.img and recovery.img from Android 9 firmware to my current C.14 (Android 10) firmware.
Now my phone is dead.
Problems:
Screen wont turn on
No Fastboot
No Recovery
Solution i tried:
Remove battery and put back again and Power On (No luck)
Remove Screen ribbon and put back again and Power On (No luck)
Removes Screen and Battery Ribbon and the same time and Power ON (Still no luck)
Posible Hope:
Everytime i connect the phone into computer (usb cable), and holding the Volume - + Volume + + Power button at the same time, the computer recognized the phone. In the computer device manager it shows Ports and Com > (USB Serial [COM5]). it only show for a second and suddenly it will disconnect.
AUTH-FLASH Realme DownloadTool can fix this i think but it need Flash Credit (username & password), well credit is too expensive 1 credit is = 1 flash , 1 credit is = to $15 here in my country.
Is there any Tool for (MTK Chipset) Realme Device that can flash like AUTH-FLASH Realme DownloadTool without any payment? or some other ways to repair this kind of problem? Please if there is anyone know HELP ME. Thank You So Much!
[SOLVED]
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
i recently hard bricked my realme x2 my flashing a wrong file .Now my phone dont even start or respond to charging .But only respond when i connect to my pc and i install the drivers and now it is show as qualcomm devies under ports in device manger.I cant go to the service centre beacause im in lockdown.Can any one pls provide the opp frimware that install usinf qfil tool in edl mode of my phone pls help
Hello there. So, I hard bricked my OnePlus 9 Pro probably - stuck in EDL, tried all the MSM tools (EU, Global, India etc) and no luck. It randomly turned off and never turned back on. No fastboot, no recovery. Just EDL.
What I did was:
Flashed it a bunch of times with MSM tool
Tried different cables, ports and hubs (I have intel Laptop)
Always recognized as Qualcomm HS-USB QDLoader 9008
Noticed that it only flashed the a partitions so I did this trick: launched MSM, clicked verify and then clicked on the radio buttons for SMT and Upgrade mode a couple of times until I finally selected the Upgrade mode
Flashed again, now It indeed flashed both partitions and it took almost double the time
I always choose lite firehose because my phone disconnects every few seconds so with lite firehose it has time to make the handshake and begin the flash
Still, nothing. Can't get it out of EDL. Any help? Any suggestions for service?
doomangel said:
Hello there. So, I hard bricked my OnePlus 9 Pro probably - stuck in EDL, tried all the MSM tools (EU, Global, India etc) and no luck. It randomly turned off and never turned back on. No fastboot, no recovery. Just EDL.
What I did was:
Flashed it a bunch of times with MSM tool
Tried different cables, ports and hubs (I have intel Laptop)
Always recognized as Qualcomm HS-USB QDLoader 9008
Noticed that it only flashed the a partitions so I did this trick: launched MSM, clicked verify and then clicked on the radio buttons for SMT and Upgrade mode a couple of times until I finally selected the Upgrade mode
Flashed again, now It indeed flashed both partitions and it took almost double the time
I always choose lite firehose because my phone disconnects every few seconds so with lite firehose it has time to make the handshake and begin the flash
Still, nothing. Can't get it out of EDL. Any help? Any suggestions for service?
Click to expand...
Click to collapse
Boot to fastboot mode ( vol up and vol down and power buttons) altogether then change the active slot in fastboot mode then reboot system...maybe work
Or try this MSM tool...
File on MEGA
mega.nz
TheGhost1951 said:
Boot to fastboot mode ( vol up and vol down and power buttons) altogether then change the active slot in fastboot mode then reboot system...maybe work
Click to expand...
Click to collapse
Thanks for your reply. Can't enter ADB or Fastboot, it is stuck in EDL.
TheGhost1951 said:
Or try this MSM tool...
File on MEGA
mega.nz
Click to expand...
Click to collapse
Now that specific MSM build is new to me so I'm running to test and will report back! Thanks for this
I have had this issue before on my OnePlus 9/ not a pro/ . I tried reinstalling drivers and restarted my PC and then I was able to install via MSMtool without errors and without having to use lite firehouse.
The driver you need is called qualcomm hs-usb qdloader 9008 you can find a fix on the net.
... I can only recommend trying different MSM tools until you find one that works. As some just don't seem to recognize your device that's having errors... One more thing I encountered was, plugging in the device at the right time in EDL mode works wonders you really have to get this part right for the MSMtool to detect your device correctly. Especially if you're hard bricked/ black screen.
I've also had this issue before and accidentally ran into it again yesteday. I'm currently waiting for the battery to drain. It's been a while although after the phone is able to power off I believe on reboot/(plugging it in) fastboot and the button sequences should be available to use msm. I found before that there was a particular way to do it with the timing, and needed the hs-usb qdloader 9008 driver.
xifo.0001 said:
I"ve also had this issue before and accidentally ran into it again yesteday. I"m currently waiting for the battery to drain. It"s been a while although after the phone is able to power off I believe on reboot/(plugging it in) fastboot and the button sequences should be available to use msm. I found before that there was a particular way to do it with the timing, and needed the hs-usb qdloader 9008 driver.
Click to expand...
Click to collapse
You don't need to drain battery, only need to make sure phone is booting correctly into EDL mode. Probably better to have a full battery.
Vmo x said:
You don't need to drain battery, only need to make sure phone is booting correctly into EDL mode. Probably better to have a full battery.
Click to expand...
Click to collapse
Sorry for my reply, I see now that was for a different blacksreen issue with fastboot. It's definitely better to have full battery if in EDL. However I was able to get it flashed just now leaving device manager open to see the state of the connection. I'm on IO but the global msm tool did not work so using the win 7 ver. of the India (lemonadep_22_I.07_210412.op) with firehose lite, India selected from dropdown. I am not sure all of what was necessary but with msm open I held all buttons until I see it triggered the reboot in device manager then immediately disconnected the device, let go of power button and reconnected holding just both the volume buttons and hit enum then start.
Try using indian version of MSM for the 9 (not the pro). After MSM, you'll have weird dpi issues, skip setup, download ota, all will be gucci after.
Had problems with Indian version, went back to TMO stock...just me
xifo.0001 said:
Sorry for my reply, I see now that was for a different blacksreen issue with fastboot. It's definitely better to have full battery if in EDL. However I was able to get it flashed just now leaving device manager open to see the state of the connection. I'm on IO but the global msm tool did not work so using the win 7 ver. of the India (lemonadep_22_I.07_210412.op) with firehose lite, India selected from dropdown. I am not sure all of what was necessary but with msm open I held all buttons until I see it triggered the reboot in device manager then immediately disconnected the device, let go of power button and reconnected holding just both the volume buttons and hit enum then start.
Click to expand...
Click to collapse
You should definitely update your windows,.
To enter EDL Mode
Hold
Volume UP +
volume DOWN -
At the same time wait a 7-10 seconds before
You do not have to press power button infact that ruins the process.. plug in cord at the exact time frame as given. If correct drivers installed on PC you will get a sound or a notification of connection proceed flash as soon as connection is received.
TheKnux said:
Try using indian version of MSM for the 9 (not the pro). After MSM, you'll have weird dpi issues, skip setup, download ota, all will be gucci after.
Click to expand...
Click to collapse
Oh I tried every MSM version I could find but still nothing
T
TheGhost1951 said:
Had problems with Indian version, went back to TMO stock...just me
Click to expand...
Click to collapse
Trying to use MSM tmo atm but I get device mismatch error. Strange - didn't had that error when EDL flashing from EU to India to global and vice versa
Best return to TMO stock is this MSM tool
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
If you have problems with MSM tool, it is best to uninstall Qualcomm drivers and make sure windows driver signature is disabled and then re-install Qualcomm drivers latest addition
doomangel said:
Oh I tried every MSM version I could find but still nothing
Click to expand...
Click to collapse
MSM for Indian OnePlus 9
NOT for the 9 pro.