my phone is automatically in 9008 mode because of installing and opening the chinese apk today. i have been using my rooted poco f3 since 6 months & till now there were no any issue but today suddenly i installed one chinese apk & after opening it my phone has gone to 9008 edl mode. so, i am not able to move to fastboot, recovery & any option. only, when i connect my phone to pc i see 9008 in drivers & that's all. Also, i downloaded the firmware & tried to flash it with mi tool in my pc& it is asking some authentication but when i entered my mi account it will not load anything. also i have twrp recovery official backups. what's the solution my friends, brother. has any one got the solution to boot into normal mode.
Related
hello everybody.
i got a 3/64gb mi max and tried to flash twrp and the miui 8 eu version.
For some reason the phone bricked (flashing the MI logo and then nothing).
i managed to get it on edl mode, i downloaded the official chinese and eu roms but no matter which one i try to flash i get this message and it doesnt go on after that.
any suggestions ?
the phone goes into EDL mode, and also goes into fastboot mode when i keep the vol - and power button. It's working but i can't flash the official rom cause of this message and when i try to flash TWRP, the screen flashes the MI logo and then nothing.
Same problem I had when flashing the latest EU ROM using TWRP with a locked bootloader. Here's what I did to fix it:
1. Make sure you have the latest Qualcomm USB drivers installed
2. Start up Miflash, make sure the right fastboot package is selected
3. Connect your phone to the PC. Hold down Power, Vol- and Vol+ together until you get a short vibration.
4. Check Windows Device Manager. Under Ports, you should see a Qualcomm 9008 QDLoader device. If you see a 9000 port or whatever, disconnect the phone, reconnect it and hold down all three buttons again.
5. Press Refresh in Miflash, you should see a COM10 device. Flashing should be successful.
oatcooky said:
Same problem I had when flashing the latest EU ROM using TWRP with a locked bootloader. Here's what I did to fix it:
1. Make sure you have the latest Qualcomm USB drivers installed
2. Start up Miflash, make sure the right fastboot package is selected
3. Connect your phone to the PC. Hold down Power, Vol- and Vol+ together until you get a short vibration.
4. Check Windows Device Manager. Under Ports, you should see a Qualcomm 9008 QDLoader device. If you see a 9000 port or whatever, disconnect the phone, reconnect it and hold down all three buttons again.
5. Press Refresh in Miflash, you should see a COM10 device. Flashing should be successful.
Click to expand...
Click to collapse
Just tried it. Same message shows up unfortunately
I have the same Problem, bat i use a old Version of Mi Flash. IT works better
Gesendet von meinem Mi Max mit Tapatalk
May i know what windows version you're using it..?, coz old version of MiFlash tool doesn't support running under 32bit system.
Maybe you can try using latest version of MiFlash tool..
You can download it from here..
If official link above doesn't work..just download from here..
Hope it's help..
You must also mark option "Flash all" in MiFlesh.
There is a solution. I have tried everything but mistake was to obvious to posiible really. I was using wrong ROM version to flash it. Had "can not read from port ..." or "can not received hello packet data".
Firts of all download miflash beta. Then check your processor type because this is what define your rom. I thought that my Mi Max 64GB is a hydrogen ROM. Wasted because of that about 30 hours of my precious life Then I realised that my ROM is helium. I downloaded helium_global_images_V8.1.9.0.MBDMIDI_20170103
Flashed it for a first time.
google:
Discussion Solved Bootloop, Cannot receive hello packet, Object reference not set to an
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.
I had been using realme ui 2.0 on my realme x2 but was frustrated by the bugs so decided to roll back to ui 1.0 (from official website) while the loadng was going on the screen went blank and since then my phone is just bricked as i cannot enter fastboot,recovery modes,not charging nothing just dead .But when i connect it to the pc ,it is recognised as qualcom 9008 com3 as i installed qualcom drivers on pc.(my phone was never rooted nor the bootloader was unlocked).
Hint: Add Realme X2 to this thread's title thus mainly owners of this phone get addressed.
Qualcomm EDL/ 9008 Mode is an Emergency Download mode that is present in every Qualcomm device.
This "Download mode" is enabled when the device can't properly boot (It can also be booted into , using twrp or commands) this can be because of an Improper flash (Like yours) or something on the inside being damaged (less likely).
How do we get out of this EDL mode?
1.If device isn't actually damaged/bricked and just accidentally booted into EDL pressing all three buttons will reboot the device out of EDL , you will have to press it for a long time. (Easiest)
2.Give up and by a new device. (second easiest but also the most expensive)
3Give it to Realme service , many people have done this and gotten back their phone most of the time for free! , but they can charge about $30.
4. Do-It-Yourself , as of now the Firehose file for the Realme X2 is not available which is required to be able do anything useful in EDL mode. (Think of Firehose as a secret key , it is different for other phones , Realme X2 Pro firehose won't work on the Realme X2 , sometimes just submodels of the same phone can have different keys for this.)
Hallo i did root with my op 7T EU version HD1903
After root with magisk wasn't working Wifi so i tried to find original firmware and install it with fastboot.exe file.
After this i cant run phone anymore im getting now only blackscreen and after some time i get access to fastboot/ recovery
but problem is i have in recovery restarted system setting and i think it shutted down USB debugging.
If i try find device with adb is then only possible in recovery mode but device is unauthorized .
Phone is without password.
If is there any way to repair it i will be really thankful because im already working on this about 14 hours.
Thanks for every help
Msmtool, EDL mode