Related
hi
i hard bricked my lg 930
how ?
i followed this step
http://www.androidauthority.com/lg-nitro-hd-clockworkmod-cwm-recovery-48447/
(do not follow)
i tried install ClockworkMod (CWM) since i installed the koereean rom and (no wi-fi to install tru rom manager)
is anything i can do for my phone like i'm not able to go in download mode, i can't see anything on screen. black
while i connect the usb cable i can hear a sound like connecting to computer
thanks a lot
We would need some more information to know if your phone is truly bricked.
does your device show up via ADB?
does it show up with B2CAppSetup program?
have you followed the unbricking solution?
http://forum.xda-developers.com/showthread.php?t=1597488
an important part of getting the phone into download mode is unplugging the usb at the right time during a hard reboot with the volume up held.
hope any of this helps but hopefully we will hear back with more info.
Maverick.Marq said:
We would need some more information to know if your phone is truly bricked.
does your device show up via ADB?
does it show up with B2CAppSetup program?
have you followed the unbricking solution?
http://forum.xda-developers.com/showthread.php?t=1597488
an important part of getting the phone into download mode is unplugging the usb at the right time during a hard reboot with the volume up held.
hope any of this helps but hopefully we will hear back with more info.
Click to expand...
Click to collapse
first of all thanks for response
no, it doesn't show up in adb (use command adb devices)
i can hear only the sound from computer (exactly like you connect true usb cable) but nothing on screen
yes, i tried the steps but ask to connect the phone, no usb connecting
@Maverick.Marq,
No, we don't really need more info to know his phone is hosed. Basically he has flashed a supposed CWM image on top of one of the bootloader partitions instead of the recovery partition. Everyone should contact these guys and tell them their guide is horribly, horribly wrong. They never responded to my email...but maybe if more people contact them about it, they'll remove their stupid guide.
Sent from my LG-P930 using Tapatalk 2
Malnilion said:
@Maverick.Marq,
No, we don't really need more info to know his phone is hosed. Basically he has flashed a supposed CWM image on top of one of the bootloader partitions instead of the recovery partition. Everyone should contact these guys and tell them their guide is horribly, horribly wrong. They never responded to my email...but maybe if more people contact them about it, they'll remove their stupid guide.
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
thanks
anything i can do for my phone?
some update
some update
i have 2 computers
to the first one i never installed phone drivers other then lg drivers
1- in device manager with the phone conected (without or with battery) it's show "QHSUSB_DLOAD" with exclamation , see attachment
error 2 device manager lg p930 nitro.jpg
error device manager driver lg p930.jpg
2 - in USBVIEW20.exe when i open (phone still conected) i have this error (see attachment "error in usb view.jpg" and "usb view qualcomn.jpg")
some udate 2
in second computer i had many phone drivers like sony xperia play, htc evo 3d or htc desire
it's show zeus flash device with exclamation and now QHSUSB_DLOAD like the other computer - see " error desktop device manager zeus flash device"
i made 2 posts because i can't upload more then 4 images
i think to force to take driver for QHSUSB_DLOAD but how can i do that because i tried with propietes, update driver and don't want to take " android_winusb.inf" from lg drivers
i found in adb/adroid-sdk/extras/google a file android_winusb.inf and i have 3 choises (of course, i try to force to take the drivers,)
sorry for my english
if is some developer i can give access to my computer by remote
any ideas
thanks
update
i tried to burn the recovery image with nero and i have a error size
maybe this was the problem, the recovery image was incomplete?
nickmatine said:
i tried to burn the recovery image with nero and i have a error size
maybe this was the problem, the recovery image was incomplete?
Click to expand...
Click to collapse
LOL, I have no idea why you're trying to use Nero, but yes you are correct -- recovery images should be 16MB (16777216 bytes).
That's not the issue though. The issue is that you flashed something to the mmcblk0p6 partition, which is bad.
drumist said:
LOL, I have no idea why you're trying to use Nero, but yes you are correct -- recovery images should be 16MB (16777216 bytes).
That's not the issue though. The issue is that you flashed something to the mmcblk0p6 partition, which is bad.
Click to expand...
Click to collapse
i used nero just to see if is some error
mmcblk0p6 partition it's the bootloader partition?
Hi
Hi Nickmatine,
Could you please confirm if your phone (LG P930) got unbricked?
Regards
@allians2002,
Unless he sent it in to be hardware-flashed, it's probably pretty much hosed.
I think I have the same problem
http://forum.xda-developers.com/showthread.php?t=1569514
There is nothing you can do. I will sell mine, or if someone need a new screen or something, just so damn unlucky...
allians2002 said:
Hi Nickmatine,
Could you please confirm if your phone (LG P930) got unbricked?
Regards
Click to expand...
Click to collapse
not yet, but not abandoned the project
i think know where to solder wires to hard flash but it's a very small connector. Maybe 7-8 hours just to solder the wires. If someone know where can i buy the cable for this connector i can help you and other people
nickmatine said:
not yet, but not abandoned the project
i think know where to solder wires to hard flash but it's a very small connector. Maybe 7-8 hours just to solder the wires. If someone know where can i buy the cable for this connector i can help you and other people
Click to expand...
Click to collapse
i also have exactly the same problem. after unbricking . and coming to korean firmware i tried putting at&t firmware images and in the last step. it gave me an error "less in memory " for system.img.
the battery was at 2% when i did that. since then the screen wont light up.
i am trying to see if i can charge the battery with an external charger and then put back to phone and try if it boots.. i am pretty sad about it ..
i'll buy a jtag box next week and i'll let you know
or maybe someone know without jtag like this for optimus p930
http://forum.xda-developers.com/showthread.php?p=25501047
nickmatine said:
i'll buy a jtag box next week and i'll let you know
or maybe someone know without jtag like this for optimus p930
http://forum.xda-developers.com/showthread.php?p=25501047
Click to expand...
Click to collapse
i have given my phone for repair to nearby mobile repair shop. i have a very little hope from them .. which means its bricked
hem.acharya said:
i have given my phone for repair to nearby mobile repair shop. i have a very little hope from them .. which means its bricked
Click to expand...
Click to collapse
please tell as what happened
I'll let you next week after buy medusa box
finally, i bought the medusa box but i messed up my motherboard. Why?
In the schematic diagram for Jtag they give me the wrong pins (in mirror). Beacuse i tried many times with wrong configuration my motherboard died. After that i removed the JTAG conector and i so the wrong schematic
now,i still try to fix a lg p 930 so if anybody have a hard bricked phone for sell send a messege
Sorry for my english
SOLVED
greeting
After 6 months I'm back with feedback. I was Able to fix my LG P930 with Medusa box. Meanwhile I bought a professional microscope, Octopus Box, Z3X box and Riff box, so now i fix phones by JTAG. I managed to fix my P930 so is alive again after 6 months
So today I tried flashing android 5.0 on my T-mobile LG G3 D851. I put it into download mode, started the flash and waited. My LG flash tool then crashed and closed. My phone was %6 through the installation however and was just left frozen after it crashed. I tried every way possible to restart it and get out of the screen while keeping it plugged in, but I couldn't...so I took out the battery and put it back in. Now nothing is turning on, I can't put it in download mode and the charging LED doesn't light up, etc. It's completely bricked....what do I do? I've already tried taking out the battery and waiting and plugging in the cord and then battery. Please help! I can't afford the insurance or another phone...
EDIT: Also the battery does have charge...although I don't know how long it will last.
EDIT 2: I just realized this flash was for the 855 variant..not 851. Does this mean that I am just screwed?
It means that you got expensive brick.
You cant enter into download mode or recovery?
Probably only help is jtag. Find someone who can do that.
Sounds like someone has learned a very expensive lesson! Have you tried to factory reset it?
Yeah JTAG is all you got if no download mode
Sent from my LG-D855 using XDA Free mobile app
joshmccoyy said:
So today I tried flashing android 5.0 on my T-mobile LG G3 D851. I put it into download mode, started the flash and waited. My LG flash tool then crashed and closed. My phone was %6 through the installation however and was just left frozen after it crashed. I tried every way possible to restart it and get out of the screen while keeping it plugged in, but I couldn't...so I took out the battery and put it back in. Now nothing is turning on, I can't put it in download mode and the charging LED doesn't light up, etc. It's completely bricked....what do I do? I've already tried taking out the battery and waiting and plugging in the cord and then battery. Please help! I can't afford the insurance or another phone...
EDIT: Also the battery does have charge...although I don't know how long it will last.
EDIT 2: I just realized this flash was for the 855 variant..not 851. Does this mean that I am just screwed?
Click to expand...
Click to collapse
Did you manage to unbrick your G3?
Neurom707 said:
Yeah JTAG is all you got if no download mode
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Not necessarily. This might work in his situation
http://forum.xda-developers.com/showthread.php?t=2582142
itsbighead said:
Not necessarily. This might work in his situation
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
The linked solution works only if the device shows some signs of life - atleast a boot logo.
i have a D851 that a friend bricked. She tried upgrading to Lollipop and flashed the AT&T baseband on this TMobile version. The result is a hard bricked device which does not even seem to power on. Shows no signs of life, except when connected to a windows pc. It shows up as 'LG Androidnet USB modem' in the device manager. No boot logo, recovery, or download mode. Fortunately she has IMEI and twrp backups for this phone (boot, efs1, efs2, radio, rpm, tz). I did some research on JTag solutions. Unfortunately, none of the boxes support the D851, yet.
Any ideas on how to recover this device would be greatly appreciated.
majesticpark said:
The linked solution works only if the device shows some signs of life - atleast a boot logo.
i have a D851 that a friend bricked. She tried upgrading to Lollipop and flashed the AT&T baseband on this TMobile version. The result is a hard bricked device which does not even seem to power on. Shows no signs of life, except when connected to a windows pc. It shows up as 'LG Androidnet USB modem' in the device manager. No boot logo, recovery, or download mode. Fortunately she has IMEI and twrp backups for this phone (boot, efs1, efs2, radio, rpm, tz). I did some research on JTag solutions. Unfortunately, none of the boxes support the D851, yet.
Any ideas on how to recover this device would be greatly appreciated.
Click to expand...
Click to collapse
If OP at least get QHUSB_BULK when he plugs it in it's better that he tries it
Sent from my iPad using Tapatalk
itsbighead said:
If OP at least get QHUSB_BULK when he plugs it in it's better that he tries it
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Nope. Only LG Androidnet USB modem'
Last night, whilst trying to flash all the phones in our house with their respective Nexus factory images, I inadvertently ended up running the flash-all.bat for a Nexus 5 (hammerhead) onto a Nexus 5X (bullhead) by mistake. It got as far as flashing the radio and bootloader, and rebooted the phone.
And now the phone won't turn on at all.
Can't get into fastboot mode with key combination (I'm assuming because the bootloader for the Nexus 5 was flashed mistakenly).
When plugged into a computer, it shows up in Windows Device Manager as QHSUSB_BULK.
ADB and FASTBOOT won't see the phone at all.
Can anyone help? I've tried looking online for this but the only hits I'm getting are specifically for other phones, not the Nexus 5X. A lot of the steps to resolve seem to be extremely specific to those phones (i.e. - there's a thread here about the Nexus 5 but the restore file is only for the Nexus 5).
oscillik said:
Last night, whilst trying to flash all the phones in our house with their respective Nexus factory images, I inadvertently ended up running the flash-all.bat for a Nexus 5 (hammerhead) onto a Nexus 5X (bullhead) by mistake. It got as far as flashing the radio and bootloader, and rebooted the phone.
And now the phone won't turn on at all.
Can't get into fastboot mode with key combination (I'm assuming because the bootloader for the Nexus 5 was flashed mistakenly).
When plugged into a computer, it shows up in Windows Device Manager as QHSUSB_BULK.
ADB and FASTBOOT won't see the phone at all.
Can anyone help? I've tried looking online for this but the only hits I'm getting are specifically for other phones, not the Nexus 5X. A lot of the steps to resolve seem to be extremely specific to those phones (i.e. - there's a thread here about the Nexus 5 but the restore file is only for the Nexus 5).
Click to expand...
Click to collapse
Well, that happens when you flashed the wrong bootloader image.
I remember reading about there being multiple modes with QHSUSB_BULK? Some seems to require images signed with keys from Qualcomm...
Can you take a screenshot in Windows device manager? Also try getting the USB VID and PID if possible?
alvinhochun said:
Well, that happens when you flashed the wrong bootloader image.
I remember reading about there being multiple modes with QHSUSB_BULK? Some seems to require images signed with keys from Qualcomm...
Can you take a screenshot in Windows device manager? Also try getting the USB VID and PID if possible?
Click to expand...
Click to collapse
Yeah, this is likely going to be an expensive lesson in making sure I don't have multiple factory image folders sitting on my drive, ready for flashing onto the various Nexus phones I have to 'administer' for my family and friends!
From what I've been able to gather, I had already come to the conclusion that it may be salvageable, providing I can get access to the appropriate partition image files from Qualcomm and the appropriate tool to flash it, and instructions! I've seen as much for the Nexus 5, but nothing for the Nexus 5X.
I can try and get some screenshots later tonight, and even boot up a Linux box to get some more info.
Perhaps there is an easier way...
There should be a "backup" bootloader partition (in fact, I just checked my 5X and there is one).
Perhaps try holding all buttons to get it to use the backup bootloader? But first you need to get out of the QHSUSB_BULK mode.
Reference thread for N5: http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
And then if you managed to boot the backup bootloader you should be able to just use fastboot to flash the bootloader again.
Edit: Now that I think about it, it may be bricked on even earlier boot stages since I think the bootloader image contains them as well. Probably still worth a try but I guess your chances are pretty low...
alvinhochun said:
Perhaps there is an easier way...
There should be a "backup" bootloader partition (in fact, I just checked my 5X and there is one).
Perhaps try holding all buttons to get it to use the backup bootloader? But first you need to get out of the QHSUSB_BULK mode.
Reference thread for N5: http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
And then if you managed to boot the backup bootloader you should be able to just use fastboot to flash the bootloader again.
Edit: Now that I think about it, it may be bricked on even earlier boot stages since I think the bootloader image contains them as well. Probably still worth a try but I guess your chances are pretty low...
Click to expand...
Click to collapse
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
oscillik said:
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
Click to expand...
Click to collapse
What if you hold the power button for a few seconds? Like more than 10 seconds? I think it should reboot the phone.
alvinhochun said:
What if you hold the power button for a few seconds? Like more than 10 seconds? I think it should reboot the phone.
Click to expand...
Click to collapse
If it reboots the phone, I'm not getting any feedback from the device whatsoever of that happening. Nothing appears on the screen, no vibration, no sound. Even if I do that while it's plugged into the computer, I don't get the Windows 'disconnect / reconnect' USB device sound (if you get what I mean?) to denote that a device has been unplugged/replugged back in - which is what I would expect to happen if I power cycled the phone whilst it's connected to the computer.
Hi,
I am dealing with the EXACT same situation. Did you find any solution to this? I wanted to sell my 5X in order to purchase 6P and when the buyer came I wanted to un-root the phone and write back the original recovery image. Anyway, I ended writing the bootloader also, but from my wife's Nexus 5 (hammerhead) and not from 5X
Same problem. Tried a lot of qualcomm tools and the lg flash tool with tot file. Doesnt work.
bricked
Hey brother, I am sorry to say you are screwed. I just did the same thing to my phone two weeks ago. It seems without the bootloader the phone will not react at all and yes the flash-all script flashs bootloader first then restarts but once the nexus 5 bootlader is flashed the phone cant start the bootloader.
here is my thread i started with some responses but its all bad news
http://forum.xda-developers.com/nexus-5x/help/hard-bricked-phone-t3278033
There is a plus side for you that is not for me. I have called google and was 100% honest with them as to what happend. They told me they would not warranty me out a new phone since its my fault. However they did say because it is a software issue LG should be able to fix the issue. I already started the RMA process and my phone should be arrivng at LG on monday (two days from now) so hopefully they cover it under warranty or charge me something small to just flash the proper bootloader.
I will report back to my orignal thread and this one for others as I am betting as time passes a lot of original nexus 5 owners who upgrade and are used to flashing a lot will also make the same careless mistake.
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
That's great news! I wonder if the repairing was done by changing the motherboard or they've been able to re-write the eMMC chip. Anyway, take good care of it
P.S. Did you told them that you wrongfully wrote the firmware from another phone or they didn't asked? I wonder if this could be considered that you void your warranty or not.
anjelika said:
That's great news! I wonder if the repairing was done by changing the motherboard or they've been able to re-write the eMMC chip. Anyway, take good care of it
P.S. Did you told them that you wrongfully wrote the firmware from another phone or they didn't asked? I wonder if this could be considered that you void your warranty or not.
Click to expand...
Click to collapse
They told the truth and everything worked in their favor: http://forum.xda-developers.com/showthread.php?t=3278033
Sent from my Nexus 5X using Tapatalk
the bulk mode is the qhusb 9008 mode. With the right files a unbrick is possible. Unbricked my G3 also from 9008 last week.
But the prob is to get the right files.
I get the files for the flex2. So iam try if i could rewrite those files.
I dont want to send it to lg, its funny so solve it with my own hands -
konsolen said:
the bulk mode is the qhusb 9008 mode. With the right files a unbrick is possible. Unbricked my G3 also from 9008 last week.
But the prob is to get the right files.
I get the files for the flex2. So iam try if i could rewrite those files.
I dont want to send it to lg, its funny so solve it with my own hands -
Click to expand...
Click to collapse
pardon me , did you have solve it ? my 5x have this problem for a week , i can't find the file , what i find is boardiag (N5) and blank flash (n6)
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
konsolen said:
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
Click to expand...
Click to collapse
thanks for reply , it's so hard to find OTG with C type in indonesia and LG in here must to check it not sure they can fix it .
Did some tested if this method works for N5x?
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
konsolen said:
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
Click to expand...
Click to collapse
Hi I have this issue on my H791. I do have a USB C OTG cable. Are you saying you were able to point the LG Tool to the file on the SD card through the OTG cable/PC, then flash? Can you elaborate or point me to the thread in reference? I backed up my EFS partition before all this happened, so my IMEI is still intact on a backup. Thanks.
oscillik said:
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
Click to expand...
Click to collapse
I found a way off QHSUSB_BULK that worked for me--with rubber bands. To invoke either boot loader when stuck like this I needed to drain the battery completely, and I figured that would take a very long time without the screen even turning on.
I noticed that if I held in any of the volume keys + power while connected to my PC that the phone was in reality rebooting every 30 seconds--it would come and go from Device Manager. So I grabbed three rubber bands and wrapped them around the phone at each of the 3 buttons and pressed them in.
After a few hours the phone was completely dead and I could power it back on with a brief charge. Into the bootloader it went and I'm back in business.
Hi everyone
I having this problem with my lg g3 d855 ... My phone was at 5% then i wanted to remove kingroot because i wanted to flash super su. After uninstalling kingroot (in the app) the app crashed ant after few seconds my phone turned off... i was thinking my phones battery just died, but i was wrong. My phone wont turn on now :/... Only response i get from it then i plug it in the charger without battery (it show no battery error)... then i put battery in, screen goes blank.
And also i installed twrp using app from store (Forgot the name, but for d855 model)
*LG G3 D855 Android 6.0 official* (if needed.)
i tried:
holding power button for 15sec without battery and then charging it... Didn't work :/.
Putting another battery (Galaxy s3... Charged to 30% at least. I don't have another lg battery ), same result.
New battery also doesn't do anything...
EDIT:
i tried method in http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 but i can't find nor make .tot file :/ anyone can link mby?
and there's exclamation mark near Qualcomm HS-USB QDLoader 9008(COM13) in device manager. Maybe there's a problem with that?
Help guys
EDIT V2!!:
Thanks for nothing
i fixed my lgg3 with this tutorial http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
and flashed files in this order http://forum.xda-developers.com/spr...very-guide-t3132359/post65291398#post65291398
after that i put phone into download mode and flashed kdz file i had
at least someone responded to this post :/
It works now!..
The problem was autorec... i tried to install recovery using autorec for lollipop and that screwed everything
I have exactly the same problem.
Hamtero said:
I have exactly the same problem.
Click to expand...
Click to collapse
i fixed my lgg3 with this http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
and flashed files in this order http://forum.xda-developers.com/spr...very-guide-t3132359/post65291398#post65291398
(i installed slb1 without battery and then unpluged phone, put battery, hold volume up, putted usb back into phone and tried to put phone into download mode. IT WORKED!! )
And Thanks for replay
I was in the middle of unbrick my g3 from hard brick to soft brick. I flash firmware using lg up at 99% then the phone died as it tried to reboot. It won't boot at all. As you said when remove the battery and connect charger, i can see my motherboard working with exclamation mark. As soon as i put the battery, motherboard out and no sign of life. Is this sign of bad battery or what. I don't have spared battery
I recommend first, to users with similar problems, to try first my guide in following link and after the pins in motherboard-tot files
https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268/page116
Superuser_ said:
I recommend first, to users with similar problems, to try first my guide in following link and after the pins in motherboard-tot files
https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268/page116
Click to expand...
Click to collapse
I have D858HK hard bricked for 2 month and i use v10d to flash every partition. Then it won't boot into recovery. When i use v985 .tot, it successfully boot into recovery. Also on LG Smart Board diagnostic, my model not detected. Even if i manually select, nothing happen when it reboot. Right now, i have no idea whats wrong as i spent countless of hour on google and XDA.
anip_aniki said:
I have D858HK hard bricked for 2 month and i use v10d to flash every partition. Then it won't boot into recovery. When i use v985 .tot, it successfully boot into recovery. Also on LG Smart Board diagnostic, my model not detected. Even if i manually select, nothing happen when it reboot. Right now, i have no idea whats wrong as i spent countless of hour on google and XDA.
Click to expand...
Click to collapse
Have you try my guide?
Superuser_ said:
Have you try my guide?
Click to expand...
Click to collapse
I already follow your guide. The thing is, my device not detected on LG Smart Board Diagnostic. When i manually select my device, everything ok then it boot with blank screen with red and blue led. I can't even enter download mode. I use win 10 64bit with all driver installed and disable integrity checks and everything
Accidentally my phone droped on the floor after that it kepps the mi logo loop after some time the battery got dead and phone also not charging. While connecting to the charger cable the led blinking and looping. Buy my phone doesn't charging and while on the flash process without battery the fastboot mode opens and closes rythmically.and my computer doesn't take the time to load the drivers. Now what to do feeling dizzy....
Please help me out of this problem. I think it bricked but not hard. Because the fastboot logo comes but not more than 5 seconds it goes off. Please help
Try giving it to a local repair store.
I also had the same problem. If I used to remove and put the battery back, it used to reboot. I tried flashing using fastboot, but it used to reboot every 6 seconds. According to some friends of mine (Thanks to them) I gave it to a store, which in turn (I dunno how) hardbricked the device. I connected it to the PC, tried to go to fastboot, and it shows up as QCOM Loader 9008, which basically tells you your device is hardbricked.
Fastboot didn't work.
Using MiFlash Tool, while flashing through the QcomLoader, it showed "Did not receive hello packet"
Tried many times more, didn't work out.
So, I went and tried the trusted method: TEST POINT method.
It worked out. Now my armani is up and running!
TL : DR;
Try giving it to a local repair store (not Mi service center, they didn't help me AT ALL.)
Something might have dislodged.
Or
Try testpoint method, google for it
it *might* work. Well, that worked for me.
Not end at all
Hi, sorry for very late reply
Recently I discovered that the battery is dead not working at all. And while doing the test point method I think battery power is needed! So I ordered a spare battery after the delivery I will do the test point method agian. Currently if I plug in my phone thorough usb to my computer the qcom 9008 port shows but while flashing it gets detached then re shows up . And the flashtool error happens. I think a battery power is required so that this failure is happening.
So, what do you think is edl mode requires battery power?.
Need help because I have to fix it. It's my one and only loved phone of all time.
Currently I am using my friends phone to discuss about this matter.....please help me.....
parag2001 said:
Hi, sorry for very late reply
Recently I discovered that the battery is dead not working at all. And while doing the test point method I think battery power is needed! So I ordered a spare battery after the delivery I will do the test point method agian. Currently if I plug in my phone thorough usb to my computer the qcom 9008 port shows but while flashing it gets detached then re shows up . And the flashtool error happens. I think a battery power is required so that this failure is happening.
So, what do you think is edl mode requires battery power?.
Need help because I have to fix it. It's my one and only loved phone of all time.
Currently I am using my friends phone to discuss about this matter.....please help me.....
Click to expand...
Click to collapse
You do not need battery power for test point method.