hard bricked a6000.. - Lenovo A6000/Plus Questions & Answers

Okay , i dont know what really happened but.. I was running CM12 with custom kernel.. it were fine *for2days* , then there were some annoying bugs with the video and audio playbacks and also wifi.. Before i flashed cm12 i did twrp backup, so i restored it and when i rebooted to system.. the phone didnt seem to turn on. just a black screen and vibrating every 2 seconds. PC doesnt recognize it , i cant get to the boot logo , just vibrating.. I cant go in recovery neither download nor fastboot or anything else.. just vibrating every 2 seconds or less.

edit.. it stopped vibrating when i pulled out the battery for 10mins. now its doing nothing, just black screen. ill charge it for several hours and try again

smirnofz951 said:
edit.. it stopped vibrating when i pulled out the battery for 10mins. now its doing nothing, just black screen. ill charge it for several hours and try again
Click to expand...
Click to collapse
I think its not possible to revive your Lenovo A6000.
I too had a similar experience. The Motherboard of the phone may have have fried .
So I suggest you to visit the Lenovo Service Center & say that the phone doesn't turn ON after you updated to the new update version.
Say nothing about rooting or your custom ROM.
I hope you are still under warranty & they will probably repair it for Free. Also Enquire abt the charges if any.

Qualcomm Hs USB Qdloader 9008 (or 9006) mode
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you

kartixda said:
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you
Click to expand...
Click to collapse
I tried everything. But when i connect my phone to PC its just vibrating , its not recognized by pc.. Vibrating in different intervals, sometimes stops for a 5 - 10 seconds. I dont know what really happened to that phone. I just restored my twrp backup, rebooted and thats it... It cant be hardware issue.

averagegeek said:
I think its not possible to revive your Lenovo A6000.
I too had a similar experience. The Motherboard of the phone may have have fried .
So I suggest you to visit the Lenovo Service Center & say that the phone doesn't turn ON after you updated to the new update version.
Say nothing about rooting or your custom ROM.
I hope you are still under warranty & they will probably repair it for Free. Also Enquire abt the charges if any.
Click to expand...
Click to collapse
Yea i'm under warranty , ill go tomorrow and see what they will do.

Are u able to go into fastboot mode by pressing power + volume down .If yes then it is very easy to recover!

smirnofz951 said:
Yea i'm under warranty , ill go tomorrow and see what they will do.
Click to expand...
Click to collapse
Let me know what they said
Sent from my Lenovo A6000/Plus using Tapatalk

Sourav_8434 said:
Are u able to go into fastboot mode by pressing power + volume down .If yes then it is very easy to recover!
Click to expand...
Click to collapse
Its not going into fastboot mode. Just vibrating in intervals.

averagegeek said:
Let me know what they said
Sent from my Lenovo A6000/Plus using Tapatalk
Click to expand...
Click to collapse
So , i went to Lenovo's service center and as u said i told them that it happened after an OTA update. They told me that its software issue and will fix it soon. Can they understand that it have been rooted and flashed with custom ROM ? Before it died I flashed back the stock kitkat rom but the recovery is still twrp. And if so, will they charge me for that?

smirnofz951 said:
So , i went to Lenovo's service center and as u said i told them that it happened after an OTA update. They told me that its software issue and will fix it soon. Can they understand that it have been rooted and flashed with custom ROM ? Before it died I flashed back the stock kitkat rom but the recovery is still twrp. And if so, will they charge me for that?
Click to expand...
Click to collapse
I think they dont

Sourav_8434 said:
I think they dont
Click to expand...
Click to collapse
Thanks for supporting, ill let you guys know if something happen.

smirnofz951 said:
So , i went to Lenovo's service center and as u said i told them that it happened after an OTA update. They told me that its software issue and will fix it soon. Can they understand that it have been rooted and flashed with custom ROM ? Before it died I flashed back the stock kitkat rom but the recovery is still twrp. And if so, will they charge me for that?
Click to expand...
Click to collapse
I hope they don't. Probably they will replace the Motherboard .
I also had the same issue as yours. I told the same as you did & they haven't charged for me.
I expect that even if they found out ,they will probably ignore it

its recognizd what i should donow

Okay , the phone came back. For first 3 days it was in Sofia,Bulgaria and they didn't found out why its not booting. Then, they texted me that the phone is shipped to India ( i dont really know why ). 10 days later the phone arrived here with changed motherboard. They did not charged me and my warranty is still alive. I'm fully sure that its software issue , really don't know whats the point of changing mobo. Anyway , thanks for supporting.
Lol lol lol just booted in recovery and its still twrp .. how its possible when they said its changed mobo

Help ME!! Bricked my Lenovo A6000 plus
kartixda said:
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you
Click to expand...
Click to collapse
I too have the same problem.The device is completely gone black but responds to power button.My PC detects Qualcomm Usb drivers 9008 .I tried flashing the stock rom but it is taking sooo long and does not finish flashing.{I even kept it overnight to flash}.Please help me recover my phone.

PLease Help
Hello,
I tried flashing the stock rom of a6000+ using twrp but after that my phone got bricked.
i am not able to boot in recovery mode. My device is not getting recognized in adb.
in the device manager section it show TP-Link Android Device->Android Bootloader Interface.
Please Help Me Unbrick My Phone.
the phone just restarts itself even if it is connected to computer.
email:[email protected]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kartixda said:
Qualcomm Hs USB Qdloader 9008 (or 9006) mode
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you
Click to expand...
Click to collapse
hello, I have a bricked A6000, maybe you can help...
now it is shown as qualcomm Hs USB qdloader 9008 in device manager. what should i do next?

Related

Unbricking Gionee elife e7 from total hard brick

Unfortunately I was one of the users that hard bricked their Gionee elife e7(my story - i tried to activate virtual softkey then systemui stopped working and I tried to flash with KitKat firmware but got fire hose error and that began my troubles). Well I guess my loss is your gain.
Generally the problem is not the flashing but the fact that it is connected as a USB hid instead of qcom hs-usb qloader 9008/9006(mine was connected as 9006). After trying so many combos and waiting for every last battery juice to dissolve, I found a combo that 'might' (not guaranteed) get you connected as qcom hs-usb qloader 9008/9006 (as I said before I got 9006 and it worked. If you get 9008 just try and see if it works .
Note:
- no download links will be posted here. The required files are the gnqc download tool and official stock firmware which you should already have.
- this is only for guys who can't boot their elife e7 at all( if you can boot to fastboot or recovery... your phone ain't dead yet and you could still save it).
- I assume you have basic knowledge of flashing firmware with gnqc download tool.
- I assume you have already installed the required drivers, have gnqc_download tool and have an official stock firmware for gionee elife e7 specific to your phone variant(32gb/16gb, E7/E7L/E7T and India/Chinese etc) of any android version(I used KitKat stock firmware and it worked but I highly recommend the stock jb 4.2.2). For some reason gnqc download tool didn't work properly in compatibility mode on my windows 10 partition but worked on windows 7. So I highly recommend windows 7.
- I also assume you have patience because this is war against your bricked elife and there could be lots of failures!
Now unto serious business!
- if you have just hard bricked the phone and it can't boot up, connect it to your pc, if it is connected as qcom hs-usb qloader 9008/9006 skip next step. If not... follow next step of course.
- Now for the dreaded USB HID. If you drain battery and it still connects as USB HID with blinking red LED try this. Uninstall the USB HID/USB input device the phone installed as(careful not to uninstall your mouse for desktop users). While still connected to PC, hold power button till red light stops blinking. Stop holding power button and immediately detach USB chord then hold volume up and volume down simultaneously in quick succession. Hold them down for quite a while. After much trial and error, i discovered that you have to hold power button for 12 seconds before phone restarts( into the dreaded black screen obviously. Tho it might not be 12 secs but that is what worked for me). So on the 12th second detach chord and press volume up and down simultaneously for quite a while. Then connect phone to PC while still holding the volume buttons(a second pair of hands might be required for precision). If all goes well, four unknown devices will appear in device manager. Wait till windows finishes installation and if you see qcom hs-usb qloader 9008/9006, you are good to go.
- Next, open the gnqc download.exe browse to your phone's firmware location. If it shows cant find mprg8x26.mbn, select 8974 in platform and if mprg8974.mbn is not found change to 8x26.
- When all is set and you see the 'Start download' button turn green, click on it. It should start download hopefully without error messages. After that, It should reboot to red Gionee logo then the white one and then to setup.
If all went well, you have successfully unbricked your Gionee elife e7! And also saved it from all phones' nightmare - your drawer.
If this works well for you feel free to click thanks and if you have a lot of joy in your heart, donate. Good luck and happy unbricking!
Question
Which version of the flashing tool do you use? The site that I found the stock firmware from has Jelly bean stock and kitkat stock but they each have a different version of the flashing tool software. (xdafirmware).
When I connect my phone to the PC the LED light only comes on for a couple seconds and then turns off?
Also does it matter if I have a 64bit windows 7 or 32bit windows 7? Thanks for your detailed guide, I am about to try it. Really appreciate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are all the files I have for the drivers and firmware. (kitkat on the right and jellybean on the left)
Cricket5467 said:
Which version of the flashing tool do you use? The site that I found the stock firmware from has Jelly bean stock and kitkat stock but they each have a different version of the flashing tool software. (xdafirmware).
When I connect my phone to the PC the LED light only comes on for a couple seconds and then turns off?
Also does it matter if I have a 64bit windows 7 or 32bit windows 7? Thanks for your detailed guide, I am about to try it. Really appreciate it.
These are all the files I have for the drivers and firmware. (kitkat on the right and jellybean on the left)
Click to expand...
Click to collapse
I used gnqc download tool v2.1.0.1, v1.6.9.0 didn't work on my windows 7. I think windows xp is required for that version. I really don't know if it will work on 64bit as mine is 32, but its worth giving a shot. At first my phone's led wasn't blinking but then after draining battery, it installed as USB input device and started to blink. Always uninstall the usb input device when it installs as that because it is worthless to have around. Good luck.
how i know if the battery is drained?
The device doesn't starts to know this.
(sorry for my bad english)
Video Help
Can you please make a dummy video of step 1
StarLord21 said:
Unfortunately I was one of the users that hard bricked their Gionee elife e7(my story - i tried to activate virtual softkey then systemui stopped working and I tried to flash with KitKat firmware but got fire hose error and that began my troubles). Well I guess my loss is your gain.
Generally the problem is not the flashing but the fact that it is connected as a USB hid instead of qcom hs-usb qloader 9008/9006(mine was connected as 9006). After trying so many combos and waiting for every last battery juice to dissolve, I found a combo that 'might' (not guaranteed) get you connected as qcom hs-usb qloader 9008/9006 (as I said before I got 9006 and it worked. If you get 9008 just try and see if it works .
Note:
- no download links will be posted here. The required files are the gnqc download tool and official stock firmware which you should already have.
- this is only for guys who can't boot their elife e7 at all( if you can boot to fastboot or recovery... your phone ain't dead yet and you could still save it).
- I assume you have basic knowledge of flashing firmware with gnqc download tool.
- I assume you have already installed the required drivers, have gnqc_download tool and have an official stock firmware for gionee elife e7 specific to your phone variant(32gb/16gb, E7/E7L/E7T and India/Chinese etc) of any android version(I used KitKat stock firmware and it worked but I highly recommend the stock jb 4.2.2). For some reason gnqc download tool didn't work properly in compatibility mode on my windows 10 partition but worked on windows 7. So I highly recommend windows 7.
- I also assume you have patience because this is war against your bricked elife and there could be lots of failures!
Now unto serious business!
- if you have just hard bricked the phone and it can't boot up, connect it to your pc, if it is connected as qcom hs-usb qloader 9008/9006 skip next step. If not... follow next step of course.
- Now for the dreaded USB HID. If you drain battery and it still connects as USB HID with blinking red LED try this. Uninstall the USB HID/USB input device the phone installed as(careful not to uninstall your mouse for desktop users). While still connected to PC, hold power button till red light stops blinking. Stop holding power button and immediately detach USB chord then hold volume up and volume down simultaneously in quick succession. Hold them down for quite a while. After much trial and error, i discovered that you have to hold power button for 12 seconds before phone restarts( into the dreaded black screen obviously. Tho it might not be 12 secs but that is what worked for me). So on the 12th second detach chord and press volume up and down simultaneously for quite a while. Then connect phone to PC while still holding the volume buttons(a second pair of hands might be required for precision). If all goes well, four unknown devices will appear in device manager. Wait till windows finishes installation and if you see qcom hs-usb qloader 9008/9006, you are good to go.
- Next, open the gnqc download.exe browse to your phone's firmware location. If it shows cant find mprg8x26.mbn, select 8974 in platform and if mprg8974.mbn is not found change to 8x26.
- When all is set and you see the 'Start download' button turn green, click on it. It should start download hopefully without error messages. After that, It should reboot to red Gionee logo then the white one and then to setup.
If all went well, you have successfully unbricked your Gionee elife e7! And also saved it from all phones' nightmare - your drawer.
If this works well for you feel free to click thanks and if you have a lot of joy in your heart, donate. Good luck and happy unbricking!
Click to expand...
Click to collapse
Bump
Dear Starlord,
experiencing major problems in step 1
(Now for the dreaded USB HID. If you drain battery and it still connects as USB HID with blinking red LED try this. Uninstall the USB HID/USB input device the phone installed as(careful not to uninstall your mouse for desktop users). While still connected to PC, hold power button till red light stops blinking. Stop holding power button and immediately detach USB chord then hold volume up and volume down simultaneously in quick succession. Hold them down for quite a while. After much trial and error, i discovered that you have to hold power button for 12 seconds before phone restarts( into the dreaded black screen obviously. Tho it might not be 12 secs but that is what worked for me). So on the 12th second detach chord and press volume up and down simultaneously for quite a while. Then connect phone to PC while still holding the volume buttons(a second pair of hands might be required for precision). If all goes well, four unknown devices will appear in device manager. Wait till windows finishes installation and if you see qcom hs-usb qloader 9008/9006, you are good to go.)
My computer beeps when i connect my phone and refreshes the device manager but i cannot see any new device there.
Am i using the wrong drivers for my device?
Or should i been doing something wrong here.
Can you please elaborate this step of a very detailed tutorial here.
Does anybody resolved the brick using this method and willing to help?
Thanks
Deepender
The complete solution
Hey all.
Just have a look here
HTML:
http://forum.xda-developers.com/elife-e7/general/guide-unbrick-hardbricked-gionee-elife-t3254532
Success full unbrick my Gionee e 7 v5626
My ginee e7 hard brick 17/12/2015 company service center give me 8k estimate for repair but i m not fools so that time i paked my phone on cupboard ..suddenly 20/1/2016 i need simcard which i used for those phone..unpacked my e7 and remove sim card at that time luckily sit near my charger so i pinned charger pin in mobile i saw that red light flashing that so i m surprised ..now i open my pc and search about it i reached xda forums and i see many solution but no one trick help me but they help me lots right way ..i download T8143 zip firmware for my Gionee e7 32gb_0301_v5626 model from Google and use flash tool wich included firmware zip..
All time i connect device to pc my pc detect hid/usb divice ...than 21/1/2016 my device connected pc and restart my pc at after restart i saw one iobit driver booster app wich notify me i have 3 new drive update one is my nvdia display one is my internet adapter ..but last one is unknown device detected ...than i click update now phone atomatic connect port ALCTEL HS Usb QDloder 9008 (port20)..now i open flash tool select firmware and select 8974 instead of 8x26 ..start download withing 5 minutes my phone downloaded 100% successfull now after 2 minutes i remove phone to pc connect charger red light start continue and 10 minutes later i pressed power button 15 second and my phone start like new unroot ..i al to happy that night ..thanks to all who give me right direction..thanks all ..sorry for bad English..
Sunilkumar Chaudhari said:
Success full unbrick my Gionee e 7 v5626
My ginee e7 hard brick 17/12/2015 company service center give me 8k estimate for repair but i m not fools so that time i paked my phone on cupboard ..suddenly 20/1/2016 i need simcard which i used for those phone..unpacked my e7 and remove sim card at that time luckily sit near my charger so i pinned charger pin in mobile i saw that red light flashing that so i m surprised ..now i open my pc and search about it i reached xda forums and i see many solution but no one trick help me but they help me lots right way ..i download T8143 zip firmware for my Gionee e7 32gb_0301_v5626 model from Google and use flash tool wich included firmware zip..
All time i connect device to pc my pc detect hid/usb divice ...than 21/1/2016 my device connected pc and restart my pc at after restart i saw one iobit driver booster app wich notify me i have 3 new drive update one is my nvdia display one is my internet adapter ..but last one is unknown device detected ...than i click update now phone atomatic connect port ALCTEL HS Usb QDloder 9008 (port20)..now i open flash tool select firmware and select 8974 instead of 8x26 ..start download withing 5 minutes my phone downloaded 100% successfull now after 2 minutes i remove phone to pc connect charger red light start continue and 10 minutes later i pressed power button 15 second and my phone start like new unroot ..i al to happy that night ..thanks to all who give me right direction..thanks all ..sorry for bad English..
Click to expand...
Click to collapse
Dear Sunilkumar can you please share a zip file for the drivers . . . . My Elife E7 is hardbricked aswell . . . Would be very thankful for your help. when i connect to pc Red light flashes only once for 2-3 seconds and it installs as usb input device. I tried the step 1 mentioned by starlord but qloader does not appear . . . again and again it installs as usb input . . . i have also installed driver booster but it is not giving update as in your case . . . can you please share driver zip files
---------- Post added at 09:49 PM ---------- Previous post was at 08:52 PM ----------
its2kool said:
Dear Sunilkumar can you please share a zip file for the drivers . . . . My Elife E7 is hardbricked aswell . . . Would be very thankful for your help. when i connect to pc Red light flashes only once for 2-3 seconds and it installs as usb input device. I tried the step 1 mentioned by starlord but qloader does not appear . . . again and again it installs as usb input . . . i have also installed driver booster but it is not giving update as in your case . . . can you please share driver zip files
Click to expand...
Click to collapse
Just Unbricked My Elife E7 Big Thanks to Sunil Kumar and XDA community. My phone was being detected as usb input device in first attemp but letting phone connected and restarting with vol up + vol down the computer detecdted unknown device driver booster identified it as ALCTEL HS Usb QDloder 9008. Driver booster detected and installed driver automatically after that i was able to update my phone. Many thanks Sunil. You saved a Worthy hardware from worst nightmare . . . MY DRAWER . . . Thanks mate
Welcome friend.
Sunilkumar Chaudhari said:
Success full unbrick my Gionee e 7 v5626
My ginee e7 hard brick 17/12/2015 company service center give me 8k estimate for repair but i m not fools so that time i paked my phone on cupboard ..suddenly 20/1/2016 i need simcard which i used for those phone..unpacked my e7 and remove sim card at that time luckily sit near my charger so i pinned charger pin in mobile i saw that red light flashing that so i m surprised ..now i open my pc and search about it i reached xda forums and i see many solution but no one trick help me but they help me lots right way ..i download T8143 zip firmware for my Gionee e7 32gb_0301_v5626 model from Google and use flash tool wich included firmware zip..
All time i connect device to pc my pc detect hid/usb divice ...than 21/1/2016 my device connected pc and restart my pc at after restart i saw one iobit driver booster app wich notify me i have 3 new drive update one is my nvdia display one is my internet adapter ..but last one is unknown device detected ...than i click update now phone atomatic connect port ALCTEL HS Usb QDloder 9008 (port20)..now i open flash tool select firmware and select 8974 instead of 8x26 ..start download withing 5 minutes my phone downloaded 100% successfull now after 2 minutes i remove phone to pc connect charger red light start continue and 10 minutes later i pressed power button 15 second and my phone start like new unroot ..i al to happy that night ..thanks to all who give me right direction..thanks all ..sorry for bad English..
Click to expand...
Click to collapse
Hello, Sunilkumar!
What are the used files for you?
Can you upload the files used, please?
Probably, the files must be as: MPRG8626.mbn, singleimage.mbn and the flash tool program.

LG G2 Stuck with grey lines after using auto rec. please for god sake help me.

ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device; LG G2 D802 32GB
Some one please?
DroidsRugly said:
ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
Device; LG G2 D802 32GB
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.
This is why I worry messing around with my G2
Have you tried long holding the power button?
Sent from my Nexus 6 using Tapatalk
Same thing here. Any answers? I can hold the power button and it turns off for a second then turns itself on and these lines show up again. Same setup after using AutoRec on 4.4.2 rom.
This is a known problem. Have LG send you a new one
blastagator said:
This is a known problem. Have LG send you a new one
Click to expand...
Click to collapse
Sadly way outside the warranty. So it's pretty much toast?
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
Make sure you're phone is fully charged. I had a problem entering download mode with low battery. I also had to try different usb ports on my laptop for whatever reason.
Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.
walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
And sadly this was my phone. I switched for a while and was coming back and wanted an upgrade to the software. I hadn't updated from 4.4.2 as it had sat in a drawer, then did AutoRec (which I thought I had done before) and boom phone is completely unusable.
---------- Post added 27th December 2015 at 12:07 AM ---------- Previous post was 26th December 2015 at 11:55 PM ----------
dark_prince said:
Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.
Click to expand...
Click to collapse
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.
walkingagh said:
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.
Click to expand...
Click to collapse
Expand under "Ports Com Ports & LPT"
And you will see LGE Com Port Device.
Just flash the kdz away if u see so. otherwise go through the tot method if u see the com port devices to change the com port address to com41 and then flash tot.
I tried this on Windows 10, Windows 8.1, Windows 8 and Windows 7 (all 64-bit versions) and it worked on all of those. Even with USB 3.0 supported laptop.
Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files
wzedlare said:
Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files
Click to expand...
Click to collapse
Any good tutorials on fastboot? And those files come from a bootstack correct?
stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Same problem with me tried Kdz Method. But no luck any idea? It's been 3 months em using it like this. Any help?
Sent from my LG-D800 using Tapatalk
So pretty stuck at this point as well. KDZ method stalls at 60%.
UPDATE FASTBOOT WORKING! Took forever to figure out the drivers, but it's working. I have no clue what to do now.
Fastboot won't recognize the device though I have the fastboot driver installed and running. Any ideas?
TOT is just kinda giving up on me. Still chasing down any leads, but the phone feels pretty borked at this point.
Update: Now in download mode! Man this has been crazy. TOT working! Okay so here is how I did it.
First, I downloaded google's ADB drivers and installed the LG drivers as well. I am not sure which one did it. Then I plugged my phone in and went to device manager. For me, it had an unrecognized device and fastboot wasn't working. So I had to manually assign the driver.
Right click on the device and update driver > Let me choose > all devices > Google > LGE mobile ADB interface.
Now fastboot should be working.
Then I used the srktool_2.1. Option 4 then option 4 again, select model number. It reboots to black screen. From there I was able to completely power off (10 second hold on power button). And when it booted back up all the drivers installed. I was able to TOT back to stock using this guide. http://forum.xda-developers.com/showthread.php?t=2432476. KDZ might work as well.
Unfortunately the screen damage looks to be permanent. But I think this is worth more now than it was 30 minutes ago!

Lg g3 auto-rec "hard brick" fix

Hello everyone, first let me give major props to my man @bender_007 for creating the amazing LG G Series Autorec Apps which make installing TWRP on LG G Devices a simple process and for also helping me and others who ignorantly misused his app, thanks B!
Anyway recently I bought a LG G3 on Verizon that was on 35b 5.1.1 Lollipop and I rooted. Boy was I eager to get some TWRP poppin on this beast, however flashing TWRP thru Flashify and TWRP Manager left me unsuccessful giving me Secure Booting Error. So desperate I seen Autorec on the Play Store, installed immediately. From there I went through the app's proccesses and from there attempted to boot into recovery hoping for some success.... I did not realize this was went for 24b 5.0.1 until it was late, I mean hey he says it in the description. The phone was dead it wouldn't show anything on the display when I held the power button and it only vibrated, I was f***ed.... At least that is what I thought. I used the method below that me and @bender_007 were collaborating upon as he tried to help me. So please give him credit. I cannot guarantee this will work for you but it worked for me and you don't have to worry about opening up your phone and shorting pins, that nonsense if this works for you.
MATERIALS
A FUNCTIONAL COMPUTER (PREFERABLY WINDOWS, I USED WINDOWS 7)
LG FLASH TOOL 2014: http://www.mediafire.com/?fwrcd3pdj0svjtb
LG DRIVERS-
UNIVERSAL: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
VERIZON:
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427
THE LATEST KDZ FOR YOUR PHONE MODEL (GOOGLE IT)
Your Dead but Still Amazing LG G3 and a USB Cable
Note: IF DONE PROPERLY YOU WILL STILL HAVE ALL YOUR EXSISTING DATA PRE-BRICK
PROCEDURE
1. Gather all materials, and know the locations of all your downloaded files.
2. Install the drivers for your phone.
3. Unzip LGFlashTool_2014.zip
4. Move the .KDZ you should've downloaded to the LGFLASHTOOL_2014 folder.
5. Open Device Manager (press start, type in Device Manager into search bar, hit enter)
6. Click View, "Show Hidden Devices"
7. PLUG in USB CABLE TO COMPUTER ONLY!
8. THIS STEP IS VERY VERY VERY IMPORTANT! TAKE THE BATTERY OUT OF YOUR LG G3. PUT IT BACK IN. CLOSE THE BACK. HOLD VOLUME UP ONLY, WHILE HOLDING POWER UP DO NOT LET GO PLUG IN OTHER HALF OF USB CABLE INTO PHONE. KEEP HOLDING VOLUME UP FOR 20 SECONDS. YOURE PHONES SCREEN WILL STILL BE BLACK AND IT SHOULDVE VIBRATED ABOUT 2 SECONDS AFTER YOU PLUGGED IN WIRE (You'll know when you do it right when COMPUTER says installing drivers in bottom right corner.)
9. In Device Manager under Modems there should be something like LGandroidNET I DONT REMEMBER EXACTLY THIS IS ALL OFF THE TOP OF MY HEAD. Anyway, if it says that then you are good, believe it or not your in download mode. (IF YOU DO NOT SEE THIS REPEAT STEP 8)
10. Go to LGFlashTool_2014 folder and run the LGFlashTool2014.exe application.
11. Change PhoneMode to Emergency
12. For "SELECT KDZ FILE" open the folder of the the FlashTool, it should be on it by default and pick the KDZ file.
13. Click "Normal Flash"
14. On the next SCREEN click "START" at the bottom
15. Now there should be a pop-up that says "Select Country & Language" Do not mess with this, just click "OK"
16. There should be a SCREEN now that has a % or whatever... From HERE TO THE END OF IT DO NOT UNPLUG YOUR PHONE!!!
17. When you hit like 85% your phone will boot up do not UNPLUG still and once it hits 100% your done! Safe to UNPLUG and YOU FIXED YOUR PHONE!!!!!!
If you have any questions please ask I have pure empathy for anyone who goes through this hell.
The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?
wombatthing said:
The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?
Click to expand...
Click to collapse
Okay I'm here to provide my best assistance and for that you'll have to answer a few questions?
1. What is your device model? ex. VS985 Verizon
2. What KDZ did you attempt to flash? ex. VS98547a_01.kdz
Looking forward to your reply.
Sent from my VS985 4G using Tapatalk
@wombatthing I would go to device manager go to view "Show Hidden devices" then disconnect your phone take out battery put it back in close back then hold volume up for 20 SECONDS while doing that connect to computer. It probably won't say installing drivers because you said it worked the First time, from there see if it's under Modems. Good luck my friend in here for any questions
Sent from my VS985 4G using Tapatalk
Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks
Ray1000 said:
Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks
Click to expand...
Click to collapse
My friend all is good. First of all as long as it says LGandroidnet you are good you should be in download mode, in lg flash took for mode click emergency and not diag then click normal flash THIS WILL KEEP YOURE DATA IF YOU SEE CRS FLASH OR SOMETHING LIKE THAT THEN ITLL RESET YOURE PHONE just do Emergency and Normal Flash and it should work. Hope I help if you have questions please ask.
@Ray1000 "Emergency" Mode is just Download Mode flashing. Diag is not that's why you were unsuccessful.
Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00
For all people with Windows 10 an problems with drivers (device is detected by Windows but app is not connecting). Decompress de correct cab for your Windows version, and update the driver "Qualcomm HS-USB QDloader 9008" with the path you used to extract. Now this driver isn't advertising that isn't signed anymore, and all apps will connect with your LG G3
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x86
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64
mackleroar said:
Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00
Click to expand...
Click to collapse
Sorry for the late response. First of all you are welcome. I don't know if you fixed the problem yet but I'll help anyway. First remove youre battery for at least 10 seconds then put battery in, hold up and connect charger for 20 seconds. Of you are unsuccessful try reinstalling drivers. Best of luck my friend.
Sent from my VS985 4G using Tapatalk
Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!
Perezvon said:
Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Im having the same problem!!!!!! I've tried everything. I will let you know if I fix it and please let me know if you get your's running?
Does anyone know if this method will work for the Sprint LS990 variant? I too had my phone broke by autorec and I lost download bit have access to TWRP and can flash roms but can't do a factory reset with the LG Flash Tool.
Sent from my LG-ls990 using Tapatalk
Failed to flash
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!
i also cannot find the Qualcomm's driver on windows 10 & phone looses communication with flash tool..
vajee555 said:
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!
Click to expand...
Click to collapse
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me
ayarihime said:
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me
Click to expand...
Click to collapse
Hello. I managed to get my device to work. Flashed a stock MM rom and now stucked with damn Mcfee kill switch. Can not go to download mode either . Any idea how to fix this? Thanks!
Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC
mjmaxint said:
Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC
Click to expand...
Click to collapse
Hello, I had to short some other two pins to get it identified by my PC. The pins mentioned it this post did not work for me. Follow the link given below and it will work for you. Thank me later.
http://forum.gsmhosting.com/vbb/f494/how-hard-unbricked-lg-g3-all-variants-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/
He guys thank you very much. My LG3 was already down for months after many failed attempts and I was about to bin it. Decided to give it one last try, found your instructions and it works, I now have Marshmallow!! (However I downloaded the KDZ file from "downloadmirror.de" and I am not sure if that was a good idea.

Completely dead after updating

So I downloaded the Android 7.1.1 and installed it via the update tool on the phone. I have not rooted, nor was I running a custom rom.
Everything went fine, until I looked over and noticed the phone was turned off. I figured it was part of the process, but after leaving it, nothing happened. I now can not power the phone on(It won't even vibrate to indicate it is trying)
The LED is also not turning on when I plug it in.
Any ideas?
viper98 said:
So I downloaded the Android 7.1.1 and installed it via the update tool on the phone. I have not rooted, nor was I running a custom rom.
Everything went fine, until I looked over and noticed the phone was turned off. I figured it was part of the process, but after leaving it, nothing happened. I now can not power the phone on(It won't even vibrate to indicate it is trying)
The LED is also not turning on when I plug it in.
Any ideas?
Click to expand...
Click to collapse
Couple of questions:
1. Where did you download Nougat 7.1.1 from?
2. Did you get any message when you unzip the file?
3. Did you notice anything unusual during update before you realised the phone didn't turn on?
Try if you can get into recovery by holding Power and Volume Up. If you can, try updating from there. That is, copy the update zip to the external sdcard, find Apply update from external sdcard, press the Power button. Let it finish then Reboot.
Good luck
priority1 said:
Couple of questions:
1. Where did you download Nougat 7.1.1 from?
2. Did you get any message when you unzip the file?
3. Did you notice anything unusual during update before you realised the phone didn't turn on?
Try if you can get into recovery by holding Power and Volume Up. If you can, try updating from there. That is, copy the update zip to the external sdcard, find Apply update from external sdcard, press the Power button. Let it finish then Reboot.
Good luck
Click to expand...
Click to collapse
I found it online, based on the link it looks like it is from ZTE's russia page.
This could be why it happened?
I got no messages at all. I just selected to install from an SD card in the settings menu, and it started everything.
As best as I can tell, it went out while the little android guy was on screen.
Can't get to recover, phone won't power on at all. Tried holding the power button for 45 seconds and that also did nothing.
viper98 said:
I found it online, based on the link it looks like it is from ZTE's russia page.
This could be why it happened?
I got no messages at all. I just selected to install from an SD card in the settings menu, and it started everything.
As best as I can tell, it went out while the little android guy was on screen.
Can't get to recover, phone won't power on at all. Tried holding the power button for 45 seconds and that also did nothing.
Click to expand...
Click to collapse
I downloaded from ZTE Russian site as well and updated fine. Nothing wrong with the software.
As you can't even boot into recovery, I'm afraid your phone is permanently bricked. I'm at my wits end. Maybe someone else has a better idea.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also have a bricked Axon 7 mini, what we need is to figure out where the Test-Point is located. I have tried to find it without success.
@ viper98,,
In you case, you can send your phone to repair center. This issue might not be fixed by flash or TWRP.
Thanks!
http://4pda.ru/pages/go/?u=https://...ye9SnceAq6QQRTGdMO9DSeNx6dN4/view?usp=sharing
nten2 said:
http://4pda.ru/pages/go/?u=https://...ye9SnceAq6QQRTGdMO9DSeNx6dN4/view?usp=sharing
Click to expand...
Click to collapse
Thank you! Axon 7 Mini is back from the dead!
reticuli said:
Thank you! Axon 7 Mini is back from the dead!
Click to expand...
Click to collapse
hi. could you please let me know exactly how you did this?
mine is totally dead, no buttons work, not detected by pc in any way.
made a deepflash cable....nothing
only a tiny dash at the corner of the screen, blinking when connected to pc.
if I open the phone and shortcircuit the test point would I get the COM port detected?
this is all I need, but I thought what you did was the same as the deepflash cable does?
PLEASE!!!! I killed it trying to roll back to android 6 after upgrading to 7 loosing my imei,.
now I don't care about imei, just bring it back to life. but to be honest I think mine is gone forever.....
did you remove the battery to make sure the phone was not in charging mode? please....how did you do it?
Thanks in advance
EDL-MODE Test-Point method
1. Open up your phone and disconnect the battery
2. Circuit test-point
3. Use deepflash cable and push button
4. Connect the battery
5. Push button on deepflash cable or change to regular usb cable when you see HS-USB Diagnostics 9008 in device manager. Flash edl recovery image with miflash.
Only Deepflash Cable method without opening phone
1. Use deepflash cable and push button
2. Press power key
3. Look for HS-USB Diagnostics 9008 in device manager.
With the right deepflash it's the same as using test-point. It was not that easy to open the phone. This one from ebay is the only deepflash cable that worked for me, tried my own homemade without success. https://www.ebay.com/itm/2-in1-Deep...140594?hash=item3af2795332:g:8kgAAOSw-QZZyfgH
reticuli said:
EDL-MODE Test-Point method
1. Open up your phone and disconnect the battery
2. Circuit test-point
3. Use deepflash cable and push button
4. Connect the battery
5. Push button on deepflash cable or change to regular usb cable when you see HS-USB Diagnostics 9008 in device manager. Flash edl recovery image with miflash.
Only Deepflash Cable method without opening phone
1. Use deepflash cable and push button
2. Press power key
3. Look for HS-USB Diagnostics 9008 in device manager.
With the right deepflash it's the same as using test-point. It was not that easy to open the phone. This one from ebay is the only deepflash cable that worked for me, tried my own homemade without success. https://www.ebay.com/itm/2-in1-Deep...140594?hash=item3af2795332:g:8kgAAOSw-QZZyfgH
Click to expand...
Click to collapse
cool. thanks mate, I'll be ordering the cable tonight will post you back in a couple of days........
you help was truly appreciated....
reticuli said:
EDL-MODE Test-Point method
1. Open up your phone and disconnect the battery
2. Circuit test-point
3. Use deepflash cable and push button
4. Connect the battery
5. Push button on deepflash cable or change to regular usb cable when you see HS-USB Diagnostics 9008 in device manager. Flash edl recovery image with miflash.
Only Deepflash Cable method without opening phone
1. Use deepflash cable and push button
2. Press power key
3. Look for HS-USB Diagnostics 9008 in device manager.
With the right deepflash it's the same as using test-point. It was not that easy to open the phone. This one from ebay is the only deepflash cable that worked for me, tried my own homemade without success. https://www.ebay.com/itm/2-in1-Deep...140594?hash=item3af2795332:g:8kgAAOSw-QZZyfgH
Click to expand...
Click to collapse
After 2 months I also recovered mine from its "deep afterlife".
The above procedure was quite straightforward, actually all you need is patience, skills to open the phone to begin with, perseverance, but most of all...... faith!
To be honest I'm not sure how, but after the test point nothing happened, and I left my phone plugged in, battery disconnected, and left it alone for a while to finally hear the windows driver sound.......at the end it worked. Thanks a lot.
demenicis said:
After 2 months I also recovered mine from its "deep afterlife".
The above procedure was quite straightforward, actually all you need is patience, skills to open the phone to begin with, perseverance, but most of all...... faith!
To be honest I'm not sure how, but after the test point nothing happened, and I left my phone plugged in, battery disconnected, and left it alone for a while to finally hear the windows driver sound.......at the end it worked. Thanks a lot.
Click to expand...
Click to collapse
Yeah it is no fun to open up the phone. Happy to hear that you revived the phone from the dead.

Xiaomi Redmi 7A EDL mode don't turn off

Hi,
what to do Xiaomi phone (Snapdragon) does not show anything, the LED is on (when it is discharged and then it does not turn on) and "Qualcomm HS-USB Diagnostics 900E" is displayed in the device manager, the phone was discharged to 0% and the bootloader was unlocked. SparkOS is installed and I don't know what now.
SEBILOWSKI said:
Hi,
what to do Xiaomi phone (Snapdragon) does not show anything, the LED is on (when it is discharged and then it does not turn on) and "Qualcomm HS-USB Diagnostics 900E" is displayed in the device manager, the phone was discharged to 0% and the bootloader was unlocked. SparkOS is installed and I don't know what now.
Click to expand...
Click to collapse
Device auto sent to Qualcomm HS-USB Diagnostics 900E mode is not a good signal, what do you think you did, so device may turn bricked?
If you think, nothing bad was done, try charging the battery, with a 20% it's enough, and try to reboot it, by pressing the three buttons at the same time, for about 8 or 9 seconds,
I don't think this may be the case, anyway, some custom ROMs don't support the device to stay on at a minimum battery level.
SubwayChamp said:
Device auto sent to Qualcomm HS-USB Diagnostics 900E mode is not a good signal, what do you think you did, so device may turn bricked?
If you think, nothing bad was done, try charging the battery, with a 20% it's enough, and try to reboot it, by pressing the three buttons at the same time, for about 8 or 9 seconds,
I don't think this may be the case, anyway, some custom ROMs don't support the device to stay on at a minimum battery level.
Click to expand...
Click to collapse
I can't see anything on the screen at all. A million percent I installed the correct ROM because I've installed it before and never had problems. I will try to do as you wrote and let you know.
SEBILOWSKI said:
I can't see anything on the screen at all. A million percent I installed the correct ROM because I've installed it before and never had problems. I will try to do as you wrote and let you know.
Click to expand...
Click to collapse
If you press the three buttons for about 9 seconds, and nothing, or your device got again to that mode, then it turned out bricked, maybe some bad file in the zip, double check if the md5sum gets something wrong.
If this is the case, you have to start the EDL mode recovering method.
After those 9 seconds, nothing happens. The diode is lit as if it was still discharged and it is not because I had it in electricity for 3 hours. I checked and md5sum is correct. So what about this EDL now? How to do this method?
SEBILOWSKI said:
After those 9 seconds, nothing happens. The diode is lit as if it was still discharged and it is not because I had it in electricity for 3 hours. I checked and md5sum is correct. So what about this EDL now? How to do this method?
Click to expand...
Click to collapse
SubwayChamp said:
If you press the three buttons for about 9 seconds, and nothing, or your device got again to that mode, then it turned out bricked, maybe some bad file in the zip, double check if the md5sum gets something wrong.
If this is the case, you have to start the EDL mode recovering method.
Click to expand...
Click to collapse
.
SEBILOWSKI said:
.
Click to expand...
Click to collapse
Now that your device is booting to Qualcomm HS-USB Diagnostics 900E, then you have to update the drivers to Qualcomm QDloader 9008, this is one of the guides out there about update drivers from https://www.thecustomdroid.com/qualcomm-hs-usb-qdloader-9008-drivers/
Once you get it, the process is to flash the device as if it was in fastboot mode, using MiFlash tool. And just ignore, the threads claiming to open the motherboard or short-circuiting pins (test point), because your device is effectively booting to EDL mode, so not required.
In that process, if you are lucky and the damage was not serious, then you will be able to do it, in few seconds, but if somewhat the motherboard get "damaged" then it would require more effort to get it work, specially, a technician may be required.
SubwayChamp said:
Now that your device is booting to Qualcomm HS-USB Diagnostics 900E, then you have to update the drivers to Qualcomm QDloader 9008, this is one of the guides out there about update drivers from https://www.thecustomdroid.com/qualcomm-hs-usb-qdloader-9008-drivers/
Once you get it, the process is to flash the device as if it was in fastboot mode, using MiFlash tool. And just ignore, the threads claiming to open the motherboard or short-circuiting pins (test point), because your device is effectively booting to EDL mode, so not required.
In that process, if you are lucky and the damage was not serious, then you will be able to do it, in few seconds, but if somewhat the motherboard get "damaged" then it would require more effort to get it work, specially, a technician may be required.
Click to expand...
Click to collapse
I did everything as in this tutorial but still device manager detects this earlier name. I opened MiFlash but it does not detect the phone.
SEBILOWSKI said:
I did everything as in this tutorial but still device manager detects this earlier name. I opened MiFlash but it does not detect the phone.
Click to expand...
Click to collapse
I just pointed out one of the lot of guides that exist around the theme, but the guide seems to be not complete.
Qualcomm USB drivers (tab at your right side) contains all the modes listed under device manager Qualcomm tab (at your left) once you tap on it, the important part is unchecking where it says, "Show only compatible drivers" or something similar.
I'll show you, from my PC, the part that the guide lacks of. Sorry, it's in Spanish, but I guess it's self-explanatory.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If this box is checked, only these items are listed...
And when you uncheck this box, you'll see other options
So, don't worry, you don't need to find more drivers, nor do anything more, JUST update correctly the drivers, in this specific item where is listed under a Port COM.
SubwayChamp said:
I just pointed out one of the lot of guides that exist around the theme, but the guide seems to be not complete.
Qualcomm USB drivers (tab at your right side) contains all the modes listed under device manager Qualcomm tab (at your left) once you tap on it, the important part is unchecking where it says, "Show only compatible drivers" or something similar.
I'll show you, from my PC, the part that the guide lacks of. Sorry, it's in Spanish, but I guess it's self-explanatory.
View attachment 5825601
View attachment 5825603
View attachment 5825605
If this box is checked, only these items are listed...
View attachment 5825607
And when you uncheck this box, you'll see other options
View attachment 5825609
View attachment 5825611
View attachment 5825613
View attachment 5825615
View attachment 5825617
Więc nie martw się, nie musisz znajdować więcej sterowników, ani robić nic więcej, PO PROSTU zaktualizuj poprawnie sterowniki, w tym konkretnym elemencie, gdzie jest wymieniony pod Port COM.
Click to expand...
Click to collapse
SubwayChamp said:
I just pointed out one of the lot of guides that exist around the theme, but the guide seems to be not complete.
Qualcomm USB drivers (tab at your right side) contains all the modes listed under device manager Qualcomm tab (at your left) once you tap on it, the important part is unchecking where it says, "Show only compatible drivers" or something similar.
I'll show you, from my PC, the part that the guide lacks of. Sorry, it's in Spanish, but I guess it's self-explanatory.
View attachment 5825601
View attachment 5825603
View attachment 5825605
If this box is checked, only these items are listed...
View attachment 5825607
And when you uncheck this box, you'll see other options
View attachment 5825609
View attachment 5825611
View attachment 5825613
View attachment 5825615
View attachment 5825617
So, don't worry, you don't need to find more drivers, nor do anything more, JUST update correctly the drivers, in this specific item where is listed under a Port COM.
Click to expand...
Click to collapse
However, I had to manually enter the EDL, but I get these problems:
1. Cannot accept hello packet
2. Write time out, maybe device was disconnected
3. Only nop and sig tag can be recived before authentication
SEBILOWSKI said:
However, I had to manually enter the EDL, but I get these problems:
1. Cannot accept hello packet
2. Write time out, maybe device was disconnected
3. Only nop and sig tag can be recived before authentication
Click to expand...
Click to collapse
A device bricked it's easy to send to EDL mode, anyway, the drivers need to be updated, as seems you now got it.
MiFlash tool needs an authorized account, to start the flashing, so a lot of errors you may encounter in the process, specially the 3rd it's directly related to that. BUT, keep in mind, that also the motherboard, depending on what exactly you did flash may get corrupted, so a replacement may be required.
SubwayChamp said:
A device bricked it's easy to send to EDL mode, anyway, the drivers need to be updated, as seems you now got it.
MiFlash tool needs an authorized account, to start the flashing, so a lot of errors you may encounter in the process, specially the 3rd it's directly related to that. BUT, keep in mind, that also the motherboard, depending on what exactly you did flash may get corrupted, so a replacement may be required.
Click to expand...
Click to collapse
I still don't know how to solve this, can I contact you through something other than XDA and help me?
SEBILOWSKI said:
I still don't know how to solve this, can I contact you through something other than XDA and help me?
Click to expand...
Click to collapse
What is actually the status of your device?, you just keep getting errors from Mi Flash tool?. Upload some screenshot.
SubwayChamp said:
What is actually the status of your device?, you just keep getting errors from Mi Flash tool?. Upload some screenshot.
Click to expand...
Click to collapse
I keep getting it, don't know what to do with it anymore
SEBILOWSKI said:
View attachment 5846575
I keep getting it, don't know what to do with it anymore
Click to expand...
Click to collapse
I´m pretty sure, unfortunately, that the motherboard got damaged, and needs a replacement.
I had the exact situation, with a device in the past, no matter what I did, I couldn´t get it to work, but then, replaced the motherboard, and need to flash something through EDL mode, at the first attempt it worked fine,
There are another repairing method. that is anyway, up to the service center, the motherboard can be repaired, but, most of times, they consider, that the effort don´t worth it, and they ask just for a replacement, the procedure is called reballing, but again, like most of times, they don´t want to do it, not even, will mention that.

Categories

Resources