I need help :( - Xiaomi Mi A2 Lite Questions & Answers

Hi guys, my friend gave me his girlfriend's Mi A2 Lite because it does not work. I need your help.
The phone does not turn on, no fastboot mode, no recovery mode. It is stock, without customization (no custom rom, no custom recovery, locked bootloader). The only think it does, when i plug it to a pc through usb, the light starts blinking. The pc recognize it like "Qualcomm hs-usb qdloader 9008", that mean (i think) it is in edl mode, but if i try to flash a rom with miflash, it give me an error "cannot receive hello packet..."
Sorry for the long message, i hope you guys can help me. Thank you

Albatros-ita said:
Hi guys, my friend gave me his girlfriend's Mi A2 Lite because it does not work. I need your help.
The phone does not turn on, no fastboot mode, no recovery mode. It is stock, without customization (no custom rom, no custom recovery, locked bootloader). The only think it does, when i plug it to a pc through usb, the light starts blinking. The pc recognize it like "Qualcomm hs-usb qdloader 9008", that mean (i think) it is in edl mode, but if i try to flash a rom with miflash, it give me an error "cannot receive hello packet..."
Sorry for the long message, i hope you guys can help me. Thank you
Click to expand...
Click to collapse
It is probably problem with the rom you download (it needs to be tgz.file ) or you put wrong address of the file in mi flash program. Make sure to download rom from this link:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871 ( you need to extract this)
and just in case watch this video for beter understanding (2 and half minutes long) : https://www.youtube.com/watch?v=TdvAlb7cXvQ&t=55s
let me know if this works. Good luck.

hrvoje007 said:
It is probably problem with the rom you download (it needs to be tgz.file ) or you put wrong address of the file in mi flash program. Make sure to download rom from this link:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871 ( you need to extract this)
and just in case watch this video for beter understanding (2 and half minutes long) :
&t=55s
let me know if this works. Good luck.
Click to expand...
Click to collapse
I give it a try and let you know. Thank you

hrvoje007 said:
It is probably problem with the rom you download (it needs to be tgz.file ) or you put wrong address of the file in mi flash program. Make sure to download rom from this link:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871 ( you need to extract this)
and just in case watch this video for beter understanding (2 and half minutes long) :
&t=55s
let me know if this works. Good luck.
Click to expand...
Click to collapse
I tried rom you linked me:
1st attempt: for few seconds status says "flashing", after that it changes in "ping target via firehose"; after about 80 seconds it gaves error.
2nd attempt: status says "can't receive hello packet" and give me error.
After these 2 attempts, pc does not recognize the phone at all. On device manager it says "unknown usb device" instead of Qualcomm HS-USB QDLoader 9008.
What can i try now?
Thank you

You didn't say why the phone is not working, maybe is hardware problem not software, anyways try to download drivers on pc to recognize phone, if that is not helping you probably need to buy new motherboard and replace it
---------- Post added at 02:33 PM ---------- Previous post was at 02:30 PM ----------
If screen is not turning on maybe you need new screen

hrvoje007 said:
You didn't say why the phone is not working, maybe is hardware problem not software, anyways try to download drivers on pc to recognize phone, if that is not helping you probably need to buy new motherboard and replace it
---------- Post added at 02:33 PM ---------- Previous post was at 02:30 PM ----------
If screen is not turning on maybe you need new screen
Click to expand...
Click to collapse
The phone turn off by itself and stop working. I've updated driver on pc. I've to solve "ping target via firehose" problem on miflash.
There is any method to discharge battery even if the phone won't boot?

Related

HELP! Fully Bricked LG G3 D855 Blank Screen

Hi,
I think I mistakenly flashing the Fastboot partition with all wrong version of Boot, Recovey and the rest of other partition.
Now phone is only turn with BLANK BLACK SCREEN, but USB Connection still active with COM assigned at port 41 (saw under device manager).
Anyone have idea how to flash it back to work, please .....
mKHMER
mkhmer said:
Hi,
I think I mistakenly flashing the Fastboot partition with all wrong version of Boot, Recovey and the rest of other partition.
Now phone is only turn with BLANK BLACK SCREEN, but USB Connection still active with COM assigned at port 41 (saw under device manager).
Anyone have idea how to flash it back to work, please .....
mKHMER
Click to expand...
Click to collapse
Search for latest stock rom 29 at the end of version number download an unzip to desktop.
Flash in Flashtool,at first take battery out and and flash only the bootloader uncheck everithing else !!!,when finisht disconect phone ,put battery in ,now in flashtool flash whole rom
Does your PC recognize your phone as Qualcomm HS-USB QDLoader 9008 or something else?
ludoke said:
Search for latest stock rom 29 at the end of version number download an unzip to desktop.
Flash in Flashtool,at first take battery out and and flash only the bootloader uncheck everithing else !!!,when finisht disconect phone ,put battery in ,now in flashtool flash whole rom
Click to expand...
Click to collapse
It dosn't recognize my USB driver, is there any driver needed to manually install? but if we put the battery it does [LGE AndroidNET COMx]
mkhmer said:
It dosn't recognize my USB driver, is there any driver needed to manually install? but if we put the battery it does [LGE AndroidNET COMx]
Click to expand...
Click to collapse
If PC doesn't recognize your device as Qualcomm HS-USB QDLoader 9008, you need to JTAG your device, or short pin.
Information about short pin;
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
That look like we need to work direct on mainboard of the phone? anyway withou touching inside the phone?
mkhmer said:
That look like we need to work direct on mainboard of the phone? anyway withou touching inside the phone?
Click to expand...
Click to collapse
You have to disassembly your device.
My LG G3 is not recognised as stated above but as Android device LGE MOBILE ADB INTERFACE and i have no issues on Win 10.
The phone is also imidiatly detected by LG Pc Suite
ludoke said:
My LG G3 is not recognised as stated above but as Android device LGE MOBILE ADB INTERFACE and i have no issues on Win 10.
The phone is also imidiatly detected by LG Pc Suite
Click to expand...
Click to collapse
But when I remove the back cover, I see another stainless steel cover on those chip/board, how to remove it? Too risky!
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359/page8#post63750296
Here is a brioef guide i am also facing that issue from alst five days.. hope some master help to solve that situation
HELP!
Soooo... I have LG G3 D855 32GB, i think i installed wrong version of TWRP recovery (for another phone). Phone is not charging, so battery is dead. NO boot, NO recovery and NO download mode. PC does not recognize phone with LG drivers and QDLoader USB driver installed. I already do a "short pin" and nothing changes at all. I am out of solutions, please help me.
I already tried:
https://www.reddit.com/r/LGG3/comments/41wbo3/how_to_unhardbrick_your_lg_g3_jtag/
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
http://forum.xda-developers.com/sprint-lg-g3/general/guide-how-to-restore-sprint-lg-g3-ls990-t2852042
ExtremeD722 said:
Soooo... I have LG G3 D855 32GB, i think i installed wrong version of TWRP recovery (for another phone). Phone is not charging, so battery is dead. NO boot, NO recovery and NO download mode. PC does not recognize phone with LG drivers and QDLoader USB driver installed. I already do a "short pin" and nothing changes at all. I am out of solutions, please help me.
I already tried:
https://www.reddit.com/r/LGG3/comments/41wbo3/how_to_unhardbrick_your_lg_g3_jtag/
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Click to expand...
Click to collapse
Your computer recognize any serial port when you connect g3
[email protected] said:
Your computer recognize any serial port when you connect g3
Click to expand...
Click to collapse
Computer doesn't recognize anything... I tried all 4 ports (2 ports 3.0, 2 ports 2.0), with original cable and non-original(Sony) cable.
ExtremeD722 said:
I tried all 4 ports (2 ports 3.0, 2 ports 2.0), with original cable and non-original(Sony) cable.
Click to expand...
Click to collapse
I mean any responce in pc device manager when u connect ur mbl
[email protected] said:
I mean any responce in pc device manager when u connect ur mbl
Click to expand...
Click to collapse
No, device manager detects nothing. I have windows 10 (i tried in normal mode and test mode). And if I connect my G3 Beat computer crashes because of LG driver.( I tried different versions of LG drivers and always the same crash(error)).
ExtremeD722 said:
No, device manager detects nothing. I have windows 10 (i tried in normal mode and test mode). And if I connect my G3 Beat computer crashes because of LG driver.( I tried different versions of LG drivers and always the same crash(error)).
Click to expand...
Click to collapse
I think crashing driver due to window .Try to connect ur device at window 7 .Hope device manager show serial port or qhbulk.I was have same problem my g3 but i resolve by short wire method.Good luck
---------- Post added at 03:01 PM ---------- Previous post was at 02:53 PM ----------
ExtremeD722 said:
Soooo... I have LG G3 D855 32GB, i think i installed wrong version of TWRP recovery (for another phone). Phone is not charging, so battery is dead. NO boot, NO recovery and NO download mode. PC does not recognize phone with LG drivers and QDLoader USB driver installed. I already do a "short pin" and nothing changes at all. I am out of solutions, please help me.
I already tried:
https://www.reddit.com/r/LGG3/comments/41wbo3/how_to_unhardbrick_your_lg_g3_jtag/
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
http://forum.xda-developers.com/sprint-lg-g3/general/guide-how-to-restore-sprint-lg-g3-ls990-t2852042
Click to expand...
Click to collapse
Bro firt change ur window then install ur variant driver and qhbulk driver.After that if device manager show qhsub bulk port or something like then all problem will solve.If ur device manager show only lge serial port then use short wire method.:good:
[email protected] said:
I think crashing driver due to window .Try to connect ur device at window 7 .Hope device manager show serial port or qhbulk.I was have same problem my g3 but i resolve by short wire method.Good luck
Click to expand...
Click to collapse
I will try with other computers, but i have on all 3 computers win10...
Thx for respond !
ExtremeD722 said:
I will try with other computers, but i have on all 3 computers win10...
Thx for respond !
Click to expand...
Click to collapse
Then u should install window 7 because qhsub bulk will not dect on window 10.
---------- Post added at 04:11 PM ---------- Previous post was at 04:07 PM ----------
Bro when u install window 7 reply me if u get any issue.Be careful when u use short wire method because due to this method my g3 baseband and imei are unknow
[email protected] said:
Then u should install window 7 because qhsub bulk will not dect on window 10.
---------- Post added at 04:11 PM ---------- Previous post was at 04:07 PM ----------
Bro when u install window 7 reply me if u get any issue.Be careful when u use short wire method because due to this method my g3 baseband and imei are unknow
Click to expand...
Click to collapse
I will reply u soon. Why do u even need baseband and imei ?
Because my baseband. Unknown and imei is null

Device will not turn on LG G3 D855 32GB

Hello everyone.
I need your help.
My Device: LG G3 D855 32GB
The device does not turn on, the only thing that appears is because when I connect the device to a PC, I see a driver installed:
RELINK HS-USB QDLoader 9008
I read guides on site here, and I'm trying to order
I downloaded the software BoardDiag 2.9
I downloaded the files to the appropriate TOT
I extracted the files by instructors on site.
I opened the program and I followed the guide and it seems to me an error
Download mode is enabled Mode,
I quickly disconnects from the computer and reconnect the computer and then the moment I am unable to do a test and the results are:
AP CHECK START = PASS
EMMC TEST START
FAILED TO OPEN PARTITION FROM EMMC
TEST ABORTED !!
I tried a lot of tutorials but I can not, it always seems the device is in Download Mode
What can I do more?
Please your help,
Eliran
If you go that way, you will need bunch of other stuff. Here is the link
http://open-freax.fr/guide-unbrick-your-lg-g3/
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
The phone fell
Navuhodonosor said:
If you go that way, you will need bunch of other stuff. Here is the link
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
Click to expand...
Click to collapse
Thanks for the comment
The phone fell into the vehicle.
I know the phone is always in Download Mode
The software does not let me do anything and making phone download mode
I did not try to install KDZ.
And I can not open a setup KDZ because the device does not rise and there is no open port.
I only have the port I did above.
Thanks for the help, I worked in the guide and I could not ...
Navuhodonosor said:
If you go that way, you will need bunch of other stuff. Here is the link
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
Click to expand...
Click to collapse
Thanks for the help, I worked in the guide and I could not ...
I went through all the steps I found at:
Now, let’s get the party started
I set up the software the guide and I got an error:
FAIL on the EMMC test
I changed the parameter Read / Write »to« Erase
And again I got the error:
FAIL on the EMMC test
Then I try again, click Start, open a window and write in English and Chinese
Device DLOAD mode
device was not found in dload trying flash peogrammer
I click OK, the window closes and then when I press Start again, the window reappears.
Only when I disconnect the USB cable from the computer and the author briefly again then I’m able to do the test, but he failed.
FAIL on the EMMC test
The device always is in Download Mode and appears port:
RELINK HS-USB QDLoader 9008
My component can not be right at all and it always is in Download Mode?
I did not do short the guide, because the computer also detected me.
It has always seemed stuck in a download mode.
There is another option? Short elsewhere as will enable progress?
Thank you very much for your help,
Eliran
I need help please. What can i do
zarfati66 said:
Thanks for the help, I worked in the guide and I could not ...
I went through all the steps I found at:
Now, let’s get the party started
I set up the software the guide and I got an error:
FAIL on the EMMC test
I changed the parameter Read / Write »to« Erase
And again I got the error:
FAIL on the EMMC test
Then I try again, click Start, open a window and write in English and Chinese
Device DLOAD mode
device was not found in dload trying flash peogrammer
I click OK, the window closes and then when I press Start again, the window reappears.
Only when I disconnect the USB cable from the computer and the author briefly again then I’m able to do the test, but he failed.
FAIL on the EMMC test
The device always is in Download Mode and appears port:
RELINK HS-USB QDLoader 9008
My component can not be right at all and it always is in Download Mode?
I did not do short the guide, because the computer also detected me.
It has always seemed stuck in a download mode.
There is another option? Short elsewhere as will enable progress?
Thank you very much for your help,
Eliran
Click to expand...
Click to collapse
I need help please. What can i do
The phone woke for a moment ...
zarfati66 said:
I need help please. What can i do
Click to expand...
Click to collapse
Hello everyone
Today I tried again to connect the device to your computer, the screen comes on suddenly.
And see the state of battery with a question mark inside a yellow triangle.
I did not realize also saw installed driver
LGE AndroidNet USB Serial Port
I tried to re-install.
Now again became a black screen and the next thing happens:
When the device without a battery connected to a computer costing me
RELINK HS-USB QDLoader 9008
When I'm with a battery, it registers an unknown device.
When the device without a battery test again tried to do this EMMC component fails.
help please
Eliran
relink hs-USB Qdloader 9008
ZARFATI6 said:
Hello everyone
Today I tried again to connect the device to your computer, the screen comes on suddenly.
And see the state of battery with a question mark inside a yellow triangle.
I did not realize also saw installed driver
LGE AndroidNet USB Serial Port
I tried to re-install.
Now again became a black screen and the next thing happens:
When the device without a battery connected to a computer costing me
RELINK HS-USB QDLoader 9008
When I'm with a battery, it registers an unknown device.
When the device without a battery test again tried to do this EMMC component fails.
help please
Eliran
Click to expand...
Click to collapse
I am exactly in the same situation. Have you found any solution so far???? My phone suddenly stopped working and didn't boot up at all first and then I used the LG Flashtool to install original TOT file and all went well. I forgot to close LG Flashtool and it started flashing again. LG Flash tool restarts the phone at about 80% and then it failed at that point and since then I am having this issue.................
Any solution???????
apur32 said:
I am exactly in the same situation. Have you found any solution so far???? My phone suddenly stopped working and didn't boot up at all first and then I used the LG Flashtool to install original TOT file and all went well. I forgot to close LG Flashtool and it started flashing again. LG Flash tool restarts the phone at about 80% and then it failed at that point and since then I am having this issue.................
Any solution???????
Click to expand...
Click to collapse
Same situation too, solutions yet?
Hey I have the same problem .
If any of you found the solution please post it here or pm me, I am stuck

Overwritten aboot.img -> G3 bricked?

Hi guys,
I made a stupid mistake:
I was overwriting aboot.img from terminal to solve "secure boot failed" error. I didn't have backcase installed and battery fell out.
Now, the phone is bricked or at least the screen remains black, no vibrating, no flashing LED.
Is there anything I can do to revive the phone?
Can you enter anything ? Download mode ?
IF nothing you have to force to qualcomm 9008 mode and use boarddiag to fix the phone
Download-mode (Vol-up while plugging in USB) does not work.
Do you think, I can unbrick it by using willcracker's method?
Is there anything I need to keep in mind? Can you give an estimation whether this approach will solve the issue?
Yes, both willcrackers and the link will fix it
If you somehow fail write here
uhm, it seems as if the archive is protected by password? Any adive on how to get hold of it or any alternative solution?
What's also a little strange: the file "androidbrick_G3_fix.7z" is above 100MB while the download of "BoardDiag v2.99a.zip" is around 7MB...
Do I need to dis-assemble the G3 to short the pins stated here?
I did the EXACT SAME THING. I guess we can be idiots together, right?
Unfortunately, boarddiag refuses to flash with some error about the AP and android_g3_fix fails for me (looks like it's working but does nothing).
If you want to try anroidbrick_g3_fix you can email the author for the password.
I'm at a loss as to what to do, I'm already in qualcomm 9008 mode with drivers...
Follow the steps on this post: http://forum.xda-developers.com/lg-g3/help/fix-marshmallow-autorec-hard-brick-t3284608
After i killed my G3 with TWRP (Autorec for LP) on MM i bring my G3 back to life.
Tip: Use a thin massive copper caple, 0,5mm, and put the other end on the top of the sim-slot for ground.
It´s easier.
Haribo68 said:
Follow the steps on this post: http://forum.xda-developers.com/lg-g3/help/fix-marshmallow-autorec-hard-brick-t3284608
After i killed my G3 with TWRP (Autorec for LP) on MM i bring my G3 back to life.
Tip: Use a thin massive copper caple, 0,5mm, and put the other end on the top of the sim-slot for ground.
It´s easier.
Click to expand...
Click to collapse
I don't have TWRP though, will it work?
Didn't seem to. I've had horrid luck with BoardDiag though...
I'm not sure if it makes any difference, but my phone is a Verizon 32GB LG G3 w/MSM8975AC that came preflashed with 35b 5.1.1 (thanks, ,verizon) and has never seemed to respond to any of the downgrade methods. Hence me playing with partitions, flashing aboot to an earleir version, and getting into this mess by failing to flash sb1.
I'm willing to pay to get this fixed, but unsure where to go or who is reputable.
I have managed to shortcircuit the pins and get my G3 to be listed as "Qualcomm HS-USB QDLoader 9008" and a corresponding COM port.
When I start the "androidbrick_G3_fix" as administrator, the tool shows that "USB Status" is "not ready". In the guide it says:
if your driver is installed you will see your port, if not, youll see “Not ready” in little green window.
Click to expand...
Click to collapse
EDIT:
I've used BoardDiag 2.99a to flash different partions according to this source extracted from *.tot file.
Now the phone (obviously) does not boot and shows "Security Error".
Trying to enter download mode seems to work though as it shows "Download Mode" followed by "Firmware Update".
MacWarrior said:
I have managed to shortcircuit the pins and get my G3 to be listed as "Qualcomm HS-USB QDLoader 9008" and a corresponding COM port.
When I start the "androidbrick_G3_fix" as administrator, the tool shows that "USB Status" is "not ready". In the guide it says:
As I've successfully installed the driver (at least the device is listed in device manager) I don't know how to proceed.
Anyone got an idea how to fix this?
Click to expand...
Click to collapse
You need to do the short and connect the cable with the tool open first. Otherwise for some weird reason it doesn't detect the phone.
It appeared to work for me but did nothing. I hope you have better luck.
---------- Post added at 11:55 AM ---------- Previous post was at 11:12 AM ----------
Just saw your edit.
If you can enter download mode, you can now flash a tot using any online guide for such, and in theory unbrick your phone.
As for me, still no luck.
Willing to paypal gift $30.00 to anyone who can help. I've recieved some help invitations but they all insist I install whatsapp, and I can't do that without a phone...
Currently, I am flashing a kitkat kdz (D85510f_00.kdz) to the phone using LG Flash Tool 2014.
It seems to takes ages but is progressing nevertheless. After 30 minutes the tool says 14% whereas the phone says 5% on the screen. I hope the process speeds up a little...
Wish me luck
----
@ R-T-B:
Are you able to get the phone to 9008 mode? Have you tried using the plain BoardDiag 2.99a to extract from *.tot file and flash those afterwards?
MacWarrior said:
Currently, I am flashing a kitkat kdz (D85510f_00.kdz) to the phone using LG Flash Tool 2014.
It seems to takes ages but is progressing nevertheless. After 30 minutes the tool says 14% whereas the phone says 5% on the screen. I hope the process speeds up a little...
Wish me luck
Click to expand...
Click to collapse
I wish you enough luck for both of us!
But seriously, good luck. Sounds like you are in the home stretch.
EDIT: Yes, I am in 9008. Unfortunately BoardDiag seems to refuse to flash it with AP errors. I think it's an issue with the updated chipset Verizon uses on the 32gb model.

Zenfone 2 ZE551ML just bricked or faulty parts?

Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Dulu93 said:
Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Click to expand...
Click to collapse
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
k0rax said:
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
Click to expand...
Click to collapse
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
i dont think so.. tried a few different cables
Dulu93 said:
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Click to expand...
Click to collapse
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
k0rax said:
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
Click to expand...
Click to collapse
i can only find die x.15 version but i think it should be enough. the problem is that ze2 is not reacting to pc commands when in bootloader.. so i can not operate in with fastboot commands and asus flash tool requires fastboot mode
maybe my last option is to flash my phone via intel phone flash tool which operates via the soc. but i dont have the necessary files. as i remember i would need some flash.xml and image
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Dulu93 said:
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Click to expand...
Click to collapse
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
---------- Post added at 06:29 AM ---------- Previous post was at 06:21 AM ----------
k0rax said:
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
Click to expand...
Click to collapse
This did:
Make sure you go to settings-->apps-->default apps and select the dialer as your default application to make calls.
k0rax said:
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Click to expand...
Click to collapse
thank you very much for your help.
the first point chaning it to 4 zeros did the trick. i was able to reinstall the bootloader.
but i still dont have connectivity via fastboot. im sure all drivers are installed and even on linux i cant see my phone. what is that special google driver?
k0rax said:
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Click to expand...
Click to collapse
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Dulu93 said:
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Click to expand...
Click to collapse
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
k0rax said:
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
Click to expand...
Click to collapse
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
k0rax said:
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
Click to expand...
Click to collapse
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
You can leave flash tool and xfstk open same time. I flashed with xfstk, waited some time and moves between the bootloader options. Make sure no residual adb or fastboot exes are running. Then unplug the phone and plug it back in. Then it will show up. Select the option you have and click start. See if the bootloader shows any life or incoming partitioning happening . If that doesn't work reboot to bootloader scroll around in it to make sure it's loaded , it brings in the correct serial intermittently. But I don't think it's necessary.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
So xfstk reboots
Xfstk round two no reboot scroll around
AFT
Unplug USB from phone and reconnect
Should show up .
Then click start. Did it give an error with that X?
Look at processes and see if it's launched adb or fastboot
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
I think you're close - it's flashing what's needed, and recognized the phone, although it did for me also but fastboot didn't work until the drivers with adb and fastboot. The last things I would think is reinstall the Google adb fastboot drivers with the phone connected to the USB port that got you this far, and if there is some serial no verification, look for .14 version of AFT.

htc desire d820n hard bricked

Hey guys i how are you doing?!!!
I have a htc desire d820n that was soft bricked and can boot only to fastboot when I tried to install a stock rom via sdcard it said that the zip file is to big and didnt install the rom then my phone was hard bricked and didn't turn on at all (not even to htc logo) and I downloaded 2 stock roms which were in a zip file and when i try to open them on my computer it says that the archive is corrupted (an unexpected end of archive) the good thing is that when i connect it to the pc it install a qualcomm driver (Qualcomm HS-USB QDLoader 9008 (COM5)) please help me.
thanks in advance.
George_Samy said:
Hey guys i how are you doing?!!!
I have a htc desire d820n that was soft bricked and can boot only to fastboot when I tried to install a stock rom via sdcard it said that the zip file is to big and didnt install the rom then my phone was hard bricked and didn't turn on at all (not even to htc logo) and I downloaded 2 stock roms which were in a zip file and when i try to open them on my computer it says that the archive is corrupted (an unexpected end of archive) the good thing is that when i connect it to the pc it install a qualcomm driver (Qualcomm HS-USB QDLoader 9008 (COM5)) please help me.
thanks in advance.
Click to expand...
Click to collapse
Carefully read it can help you with https://forum.xda-developers.com/de...n-restarts-continuously-t3548182#post71073715
My case is almost the same, but mine isn't detected for Windows (neither adb nor loader).
I had disconnected the battery, but without any results.
Any idea?
Clamp all 3 buttons and hold 1 minute. What happens?
vuk1963 said:
Clamp all 3 buttons and hold 1 minute. What happens?
Click to expand...
Click to collapse
n
Unfortunately, nothing
How did it all start? how did it all turn out? Read more.Are the drivers of the НTС installed?
---------- Post added at 07:11 PM ---------- Previous post was at 06:58 PM ----------
Android ADB driver https://yadi.sk/d/TVkbNcXv3KP7mQ Connect the phone to the computer in the task manager on the computer to choose the interface adb to install the driver, specify in the manual on the desktop. 2.Also install USB_driver_QCOM https://yadi.sk/d/mrmvZKrk3MSggY
vuk1963 said:
How did it all start? how did it all turn out? Read more.Are the drivers of the НTС installed?
---------- Post added at 07:11 PM ---------- Previous post was at 06:58 PM ----------
All started when the phone isn't capable to install the official update to 6.0.
I decided to try other ROM's, opening the boot loader and installing the TWRP recovery. All goes well, but the ROM that are working better (Tomal - Discovery 2.00) had problems with my LTE networks.
Reading one of your post, I started to try to install the official 6.0, but I forgot to wipe the system before relock the bootloader.
After trying flash different RUU files through fastboot I used one from easy firmware: (0PFJIMG_A51_UL_K44_DESIRE_SENSE60_Orange_ES_1.28.75.5_Radio_01.01.010_U10305041_08.01.41222_2__combined_signed.zip) that belong to my CID (Orange Spain)
Then the phone don't respond to anything...
I will uninstall all drivers and programs and restart according your instructions...
Click to expand...
Click to collapse
vuk1963 said:
lcarrasc said:
Yes, sadly, you need to restore the bootloader,and it's very difficult to do it yourself http://4pda.ru/forum/index.php?showtopic=643084&st=7060
Click to expand...
Click to collapse
Thanks. I understand that my phone is lost
I tried to use QFIL (romkingz.net/2016/07/how-to-use-qualcomm-flash-image-loader) but the computer hasn't recognised the phone...
Click to expand...
Click to collapse
Solution: I will buy a used 820 with broken screen and then change the bricked motherboard myself. The price here is around 40 eur.
lcarrasc said:
Solution: I will buy a used 820 with broken screen and then change the bricked motherboard myself. The price here is around 40 eur.
Click to expand...
Click to collapse
Did you do this ?: 1.Android ADB driver https://yadi.sk/d/TVkbNcXv3KP7mQ Connect the phone to the computer in the Device Manager on the computer to choose the interface adb to install the driver specify in the manual on the desktop. 2.Also install USB_driver_QCOM https://yadi.sk/d/mrmvZKrk3MSggY 3.Connect your phone to your computer,оn the computer in Device Manager, click the tab ports (СОМ and LPT).What is written there?
vuk1963 said:
Did you do this ?: 1.Android ADB driver https://yadi.sk/d/TVkbNcXv3KP7mQ Connect the phone to the computer in the Device Manager on the computer to choose the interface adb to install the driver specify in the manual on the desktop. 2.Also install USB_driver_QCOM https://yadi.sk/d/mrmvZKrk3MSggY 3.Connect your phone to your computer,оn the computer in Device Manager, click the tab ports (СОМ and LPT).What is written there?
Click to expand...
Click to collapse
Yes. I did it.
I'm running Windows 10. As you know this OS not showing Ports (COM and LTE) in Device Manager. I added manually a COM port, (COM3 in this case), but appears only the yellow signal (!) related to errors.
lcarrasc said:
Yes. I did it.
I'm running Windows 10. As you know this OS not showing Ports (COM and LTE) in Device Manager. I added manually a COM port, (COM3 in this case), but appears only the yellow signal (!) related to errors.
Click to expand...
Click to collapse
I also run Windows 10 х86 and in Device Manager has a ports (COM and LРТ)
What it's expected to find in the com ports?
lcarrasc said:
What it's expected to find in the com ports?
Click to expand...
Click to collapse
Something like: Qualcomm HS-USB QDLoader 9008 port com
The phone seems fully dead...
Only a red led blinking when the usb cable is connected to PC or a charger.
lcarrasc said:
The phone seems fully dead...
Only a red led blinking when the usb cable is connected to PC or a charger.
Click to expand...
Click to collapse
Clamp all 3 buttons and hold 1 minute,and try different variants combinations with holding the volume buttons + and - and the power button,with the connection of the phone to the computer and to the power unit
I tried all possible combinations of buttons, and nothing...
Any idea?

Categories

Resources