My Le Pro 3 x727, it random entered QFIL mode 9008 for couple times and I was able to get it out.
But this time after flash firmware it stucks in QFIL, then I failed trying the Flashone method it just completely dead and unresponsive, cannot enter QFIL mode and does nothing.
The battery is charging, I can feel it is warming up but I just cannot enter QFIL mode.
I am throwing in the white flag as I can't seem to get it to any mode. completely gone.
Problem solved: please see y comment here
Does anyone ever experience this type of issues?
SOLVED: Please see my comment here and follow the guide~
https://forum.xda-developers.com/showpost.php?p=78946313&postcount=56
Related
Hello, last week i kept my phone in charging and i left it there for like about 4 hours and it was not the default charger that it comes with and when i unplugged it and tried to start it, it didnt start up, it only kept a black screen with the notification led flashing every one second ish so then i tried to go into fastboot and recovery mode but it didnt go into it and kept the notification led flashing so today i tried to go into the qualcom qdbootloader 9008 mode and flashed the ufs file and it said successful but i can still not access the phone or fastboot or recovery mode and I need help.
Can you see the phone in the device manager? If not you are not in 9008 mode.
I have kept the links up to date in the unbricking forums. I debricked one of my phones a few months ago and have helped alot of people via PM ( while not all of those were successful most were debricked)
Here is an excellent link to follow after you have downloaded all of the software tools and have properly prepared your computer to unbrick your phone.
https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html
Take a look at these posts for the tools needed:
https://forum.xda-developers.com/showpost.php?p=76304443&postcount=156
https://forum.xda-developers.com/showpost.php?p=76252279&postcount=143
https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Voce resolveu o problema do leeco x727?
Hello,I recently flash a wrong file and now my device is straight up dead no logo nothing the led blinks for a mini second and turns off I tried using qfil and mi flash but it was getting detected as 900e port and wasn't even detected on mi flash I tried updating drivers and got it to 9008 but still it would get stuck forever when I hit download asap in qfil or would show some sahara port error and still no detection on mi flash even in 9008 mode I tried over 50+ times using the button combinations to get it to 9008 mode but every time it would be 900e any solution other than deep flash as I have just one type c cable and I may screw up
Press volume up key for 15 seconds, then press power button & insert usb (within a second) to pc..it will get it to edl mode..
probably your only way out is deep flashing, i've been through this
any solution for this ? i'm suffering the same
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
Hi I recently try to flash a Stock Android One to my Xiaomi Mi a2 lite (Global Version of Redmi 6 pro).
I used Mi flashtool and I download a Fastboot Image file that matches my device model but my phone is bricked
the notification light is blinking when ever I push the power button. And I cannot know when my phone is charging there are no display that my phone is charging and when I press the Volume down and Power button I cannot access the Fastboot mode so I just simply attached my phone to the Computer and I shocked when I heared of a sound that my device was read by the computer but the phone is dead that time so I use the Miflash tool and It detect my phone but when I use powershell and command fastboot devices it doesnt recognized or detecting my phone.
So I decided to flash the rom to my phone because it can detect it, but Its taking too long to flash, 1500 seconds has passed but the flashing is not finish so I decided to unplug my phone but the xiaomi flash tool is still flashing so I thought that the app is corrupted so I just exit the app and open it again and do the flashing again but 2000 seconds has passed and still its the same thing I unplug the phone and the flashing still continue so I decided to stop it.
After some time I try to plug my device again but the computer dont recognized the phone anymore, the connected device sound has not triggered and the miflash tool has not recognized my phone anymore and the blinking notification light is not present too.
Please anyone help me I need this phone to attend my Online Classes please.
Similar situation here. Tried to flash Magisk. Stuck on a boot loop. Then I tried to flash Global a2 lite ROM.
Now my phone is stuck in EDL mode with 900E Drivers I see random numbers in MiFlash. When I install 9008 drivers I see the COM10 and the same random numbers on the device info in the MiFlash tool.
Taking like 30 minutes to flash and never ends. If someone has the Auto unbrick Mi a2 Lite software
please post it here so we can try to flash with this one.
Hey everyone
My LG G4 (H815) suddenly turned off when i was using it, and it showed no life when i tried to boot it up again. Its completely stock, no custom recovery or custom firmware is installed. I cant boot into fastboot or EDL mode. I tried the button combinations as well as the test point method but i just cant get it to enter any kind of recovery mode, the screen just remains black (no backlight either). I installed the Qualcomm HS-USB drivers and when i plug my phone in my pc it gets recognized by QFIL. I tried flashing the fimware but it always gives me the Sahara unable to read packet header error. Can anyone help me?
Thanks in advance.
Have you searched the forum and tried any of these ?
https://forum.xda-developers.com/t/guide-proper-h815-unbrick-through-qfil-files-included.3709212/
https://forum.xda-developers.com/t/...-unbrick-via-external-sdcard-no-qfil.3748946/
https://forum.xda-developers.com/t/lg-g4-h818p-h815-hard-brick-recovered-working.3703565/
https://forum.xda-developers.com/t/unbrick-lg-g4-9008-qualcomm-mbn-files.3574595/