Related
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
@rmorris003
You said the phone won't even power on. You mean no Google? Hold the power button down for a couple of minutes and see if it will reboot. If not put it on a charger, and after fully charging try the long press power button again. If you can get it to start, try to put it in fastboot mode. (ie. power+vol dn). If you can get to bootloader you can send fastboot commands and fix it. If you can get to this point, there are instructions here.
rmorris003 said:
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
Click to expand...
Click to collapse
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
5.1 said:
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
Click to expand...
Click to collapse
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
rmorris003 said:
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
Click to expand...
Click to collapse
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
5.1 said:
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
Click to expand...
Click to collapse
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
rmorris003 said:
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
Click to expand...
Click to collapse
You disabled driver signature and rebooted your computer? Then installed Qualcomm drivers from the thread I linked you to? I think you have to reboot your computer once more...
Good luck...
I held the power and vol down and now it shows up under com ports so this is a good sign.
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
rmorris003 said:
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
Click to expand...
Click to collapse
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
5.1 said:
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
Click to expand...
Click to collapse
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
You could report your experience in the other thread. Maybe it could help other users who faced the issue you had. :good:
Cheers...
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
Falitheman said:
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Click to expand...
Click to collapse
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
5.1 said:
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
Click to expand...
Click to collapse
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Falitheman said:
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Click to expand...
Click to collapse
Hey,
What version of qpst did you install?
Good luck...
5.1 said:
Hey,
What version of qpst did you install?
Good luck...
Click to expand...
Click to collapse
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Falitheman said:
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Click to expand...
Click to collapse
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
5.1 said:
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
Click to expand...
Click to collapse
I tried with the version you suggested and i got the same error i just had. Can you send me your version so i can see if that works?
So, I side loaded build no. 13.8.26.76 to my phone, not knowing that it was meant only for the snapdragon 410 counterpart (mine is 615 one). It installed successfully until I rebooted and phone stayed dead. I think I hard bricked it
No logo, no charging, can't enter recovery or fastboot. No nothing... Connected device to PC, and windows doesn't recognize it.
Please help me....
sree27 said:
So, I side loaded build no. 13.8.26.76 to my phone, not knowing that it was meant only for the snapdragon 410 counterpart (mine is 615 one). It installed successfully until I rebooted and phone stayed dead. I think I hard bricked it
No logo, no charging, can't enter recovery or fastboot. No nothing... Connected device to PC, and windows doesn't recognize it.
Please help me....
Click to expand...
Click to collapse
Can you go to recovery mode ?? If yes please flash your device compatibility custom rom like RR rom ..if u cant go to even recovery mode..
RIP asus zenfone max Just Change your Motherboard of your phone
Thanks
Its dead u can recover i also had same issue ...mine works now ....email me [email protected]
Hello, I had a very little progress. I gave up about my asus zenfone max a year ago but glad that now looks like there's a hope in reviving my phone. I was able to download the right files to flash with QFIL. Most people here say that their PC detected QUALCOMM HS-USB QDLOADER 9008 but mine detect it as QUALCOMM HS-USB DIAGNOSTICS 9006. Due to excitement, I flashed it anyway and it created some memory partition on my hard drive whenever I plug the phone but QFIL gave me an error of :
** Download Fail: Switch To EDL Fail Failed to switch to Emergency Download Mode
I tried to google this error, some encountered it and was able to get a resolution by just removing the battery before plugging it in but our zenfone is with non removable battery. I have no luck yet. Anyone got suggestions ?
MJMarra34 said:
Hello, I had a very little progress. I gave up about my asus zenfone max a year ago but glad that now looks like there's a hope in reviving my phone. I was able to download the right files to flash with QFIL. Most people here say that their PC detected QUALCOMM HS-USB QDLOADER 9008 but mine detect it as QUALCOMM HS-USB DIAGNOSTICS 9006. Due to excitement, I flashed it anyway and it created some memory partition on my hard drive whenever I plug the phone but QFIL gave me an error of :
** Download Fail: Switch To EDL Fail Failed to switch to Emergency Download Mode
I tried to google this error, some encountered it and was able to get a resolution by just removing the battery before plugging it in but our zenfone is with non removable battery. I have no luck yet. Anyone got suggestions ?
Click to expand...
Click to collapse
Check my post for detailed instructions. And yes, I did face that issue and fixed it by reinserting the battery. It's a bit risky, but worth a try. Try watching some YouTube teardown videos
sree27 said:
Check my post for detailed instructions. And yes, I did face that issue and fixed it by reinserting the battery. It's a bit risky, but worth a try. Try watching some YouTube teardown videos
Click to expand...
Click to collapse
Oh Great! do you have a link of your instructions man? thank you! so I really have to dissassemble the phone?
MJMarra34 said:
Oh Great! do you have a link of your instructions man? thank you! so I really have to dissassemble the phone?
Click to expand...
Click to collapse
It's on my profile. I haven't mentioned the disassembly part since it was not required in general cases. Check my profile for the detailed instructions
Hey Man. I'm currently working on my phone. I already tried removing the battery but I'm still getting the error:
Download Fail: Switch to EDL Fail.
hopes are going narrow. Now I don't know what to do.
MJMarra34 said:
Hey Man. I'm currently working on my phone. I already tried removing the battery but I'm still getting the error:
Download Fail: Switch to EDL Fail.
hopes are going narrow. Now I don't know what to do.
Click to expand...
Click to collapse
Are you on fastboot mode? What is on your display?
Im still at the part with the QFIL. Im retrying it right now bruh.. hmmm
MJMarra34 said:
Im still at the part with the QFIL. Im retrying it right now bruh.. hmmm
Click to expand...
Click to collapse
If you're having trouble with QFIL, best thing to do is uninstall Qualcomm drivers, reboot, reinstall, try again. Repeat until you can flash without problem.
I had to uninstall many times. Don't lose hope. It takes a lot of effort
hey Sree. I noticed that it is being detected as Qualcomm HS-USB diagnostics 9006. So what I did is I forced driver to install Qualcomm HS-USB QDLoader 9008. I'm now having a Sahara error. I'll try reinstalling drivers but I have a quastion. Does QFIL version matter ?
MJMarra34 said:
hey Sree. I noticed that it is being detected as Qualcomm HS-USB diagnostics 9006. So what I did is I forced driver to install Qualcomm HS-USB QDLoader 9008. I'm now having a Sahara error. I'll try reinstalling drivers but I have a quastion. Does QFIL version matter ?
Click to expand...
Click to collapse
I don't know. I used the latest one. Try the version linked in my original post. Also, of you're getting sahara fail, it's ok. You're on right track. Uninstall driver, reboot and reinstall. It'll take hell a lot of tries, but will work eventually
Hi.
My Leeco le s3 x626, helio x20 is bricked with red light.
I Just work with win7, Windows 10, but don't work.
It is recognised like
Mtk usb and with mtk preloaded.
Flashtool, with download give back error or doesn't start.
I see guide for mediateck x6...
b1gb1ng said:
Hi.
My Leeco le s3 x626, helio x20 is bricked with red light.
I Just work with win7, Windows 10, but don't work.
It is recognised like
Mtk usb and with mtk preloaded.
Flashtool, with download give back error or doesn't start.
I see guide for mediateck x6...
Click to expand...
Click to collapse
Hello, if you're still looking for a way to restore, then write to me in private messages, I'll help you with this deal)
bricked my Leeco le s3 x626
AxtExpos said:
Hello, if you're still looking for a way to restore, then write to me in private messages, I'll help you with this deal)
Click to expand...
Click to collapse
Hi, i am new to this and i just bricked my Le s3 x626. please help me. the phone is just showing a red blinking light when i connect the usb cable to charger or pc. tahnks
I have the same problem...
leeco le x626 red light brick
AxtExpos said:
Hello, if you're still looking for a way to restore, then write to me in private messages, I'll help you with this deal)
Click to expand...
Click to collapse
Please what is the solution i need help mine also bricked while trying to root
Hi,
i have the same problem - stuck on red light.
Its recommended to use SP Flashtool to flash Stock.
Before, installing correct VCOM drivers. I've done that successfully.
But now...
I need the Stock ROM for this LeEco Le S3 X626 WITH the scatter file (MT6797_Android_scatter) that is needed for SP Flashtool.
None of the downloadable Stock ROMs i could get contain this scatter file. These Stock ROMs are all for devices that can still access fastboot.
This brick, stuck on red light can't access fastboot anymore..........
Any help? i need this ROM with the scatter file... please!
majo334 said:
Hi,
i have the same problem - stuck on red light.
Its recommended to use SP Flashtool to flash Stock.
Before, installing correct VCOM drivers. I've done that successfully.
But now...
I need the Stock ROM for this LeEco Le S3 X626 WITH the scatter file (MT6797_Android_scatter) that is needed for SP Flashtool.
None of the downloadable Stock ROMs i could get contain this scatter file. These Stock ROMs are all for devices that can still access fastboot.
This brick, stuck on red light can't access fastboot anymore..........
Any help? i need this ROM with the scatter file... please!
Click to expand...
Click to collapse
I have the files you need.
blueasteroid said:
I have the files you need.
Click to expand...
Click to collapse
Hey, i also recently bricked my phone, it has the red light problem and i have the flash tool installed, i am looking for a rom with the scatter files or the files themselves since i can't access fastboot, could you send them over?
Here you have some.
https://www.leakite.com/2017/09/download-letv-le-s3-x622-stock-firmware-flash-file.html
https://bbs.le.com//zt/eui/le_2.html
https://mega.nz/#F!MI9w3T6L
password: !YMutE59mUDbdOs9BoYY59Q
https://www.youtube.com/watch?v=xOKFI_eFq9o
blueasteroid said:
Here you have some.
https://www.leakite.com/2017/09/download-letv-le-s3-x622-stock-firmware-flash-file.html
https://bbs.le.com//zt/eui/le_2.html
https://mega.nz/#F!MI9w3T6L
password: !YMutE59mUDbdOs9BoYY59Q
https://www.youtube.com/watch?v=xOKFI_eFq9o
Click to expand...
Click to collapse
i am panicked
so so so panicked
i tried everything i could already but it is giving me errors and the red led persists, i followed https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937 but it doesn't work at all, just gives me a lot of errors that when i google nothing turns up, when i try to flash only the preloader alone it gets me somewhat through the process but gets stuck and there pops up the same error as always, i will try your files (as i was using the ones provided in the tutorial) tomorrow and report back, thanks for posting them so quickly.
marksklava said:
i am panicked
so so so panicked
i tried everything i could already but it is giving me errors and the red led persists, i followed https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937 but it doesn't work at all, just gives me a lot of errors that when i google nothing turns up, when i try to flash only the preloader alone it gets me somewhat through the process but gets stuck and there pops up the same error as always, i will try your files (as i was using the ones provided in the tutorial) tomorrow and report back, thanks for posting them so quickly.
Click to expand...
Click to collapse
Read the last post in that thread. 2 days ago I was like you. Read carefully.
i don't know at all, but it actually sounds like u didn't have the correct files before... i hope at least! things should work out with tutorials and instructions, i mean we're not that dumb right? but if we don't have the exact matching files..........
i will also try the same procedure with the new files thanks ALOT to blueasteroid, and write my results here.......
marksklava, are u actually on a L3 x626 aswell? cause most seem to operate with a x622
majo334 said:
i don't know at all, but it actually sounds like u didn't have the correct files before... i hope at least! things should work out with tutorials and instructions, i mean we're not that dumb right? but if we don't have the exact matching files..........
i will also try the same procedure with the new files thanks ALOT to blueasteroid, and write my results here.......
marksklava, are u actually on a L3 x626 aswell? cause most seem to operate with a x622
Click to expand...
Click to collapse
i am on an x626, it has a 21 mp camera and i bought it from china, sorry for not replying for 4 days.
---------- Post added at 02:14 PM ---------- Previous post was at 01:50 PM ----------
I get errors still, i believe it is a drivers issue but i don't really know how to fix it, i have tried uninstalling the drivers and installing the ones needed but they do not work at all. What do i do now? Am i out of options? What are the drivers supposed to look and how do i install them? i installed the ones that were provided in the inf file, those give me error 10 and my phone keeps disconnecting and connecting on a different COM port, although the driver seems to be installed, can someone help? If anyone is kind enough to screenshare with me i can do that via skype, discord and teamviewer, i also found a 5 year old camera here so i can catch any errors on video with my phone in the frame now which could be useful. Thanks for reading this, please help me any way you can, every bit helps.
marksklava said:
i am on an x626, it has a 21 mp camera and i bought it from china, sorry for not replying for 4 days.
Click to expand...
Click to collapse
Don't panic, i figured out this thing yesterday with my x626, it was successful and was not too hard in the end! don't worry much about the drivers, its completely normal that u lose connection all the time, it happens to all of us with bricked LeEco. The drivers won't keep still for the procedure, its normal...... I worked with the drivers in the Unbrick LeEco folder from blueasteroid. I installed all the stuff there was, and Windows said: Preloader VCOM 10 - it still switched but this is normal!
It is necessary to have the correct files, the correct paths in SPFlashtool and it only worked (for me) with DA_PL_HIGH and the pressing of buttons on the phone (Pow and Vol- holding it all the time). There was no BROM Error anymore and it all worked out.
All i can say don't give up, i have been at this point since beginning of December and now i finally got it unbricked! as much BROM errors u get, don't lose patience, keep on doing... u will finally find the right timing by happenstanc and it will work. The part after it is not that problematic then.
Check this thread, its very active at the moment and imo very very helpful: https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937/page5
Read the last pages...
leeco s3 x626 bricked
i also have the same problem with 4gb-32gb from the first day . Bricked after "fastboot reboot" command.
I tried to repair with flash_tools.exe but without success. I also tried various drivers.
Hello.
If anyone can help me... LeEco X625, blocked on red led, not charging, not connecting on PC, just red led when connect.
NOT seen in device manager.
jonyx87 said:
Hello.
If anyone can help me... LeEco X625, blocked on red led, not charging, not connecting on PC, just red led when connect.
NOT seen in device manager.
Click to expand...
Click to collapse
Same problem with mine. I once hard bricked mine, but whenever i connect to PC it gives sound, i was able to restore the phone @Long run. Few weeks after, i went to charge the phone and the phone went off, ever since then, not charging, no signs nor sounds when connected to PC... Took it to Engineers and all they say is dat i need to change the board... I'm so sad because i used all the money in my account to get the phone. The phone is still enjoying inside my wardrobe
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Daan_K said:
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Click to expand...
Click to collapse
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Choose an username... said:
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Click to expand...
Click to collapse
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Daan_K said:
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Click to expand...
Click to collapse
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Daan_K said:
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Click to expand...
Click to collapse
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Choose an username... said:
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Click to expand...
Click to collapse
Allright, thankyou so much my dude
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Daan_K said:
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Click to expand...
Click to collapse
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
RedWave31 said:
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
Click to expand...
Click to collapse
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Daan_K said:
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Click to expand...
Click to collapse
Sorry, I don't believe you for one second. Like litterally THOUSANDS of people here and here opening "bricked plz hlp" threads, you didn't even have the BASIC, LOWEST courtesy of writing more than 10 words of gibberish whining about your situation, without a single usefull element of context.
Proof of that in the NUMEROUS questions asked about ELEMENTARY elements about your situation. You're litterally the kind of person that would go to a car mechanic, drop the keys on the counter saying "my car is broken, fix it" and just leave without a single word added. That's RUDE and, yeah, I'm tired AF of people like you who can't READ THE DAMN XDA RULES and got NOT education whatsoever.
Nd writng frm a phone in T9 mde dsnt rlly bring nythng mre on the tble either.
Too bad you found somebody to help, as it's only encouraging that kind of behaviour.
//Rant off//
@Daan_K this EDL Tool can help https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Choose an username... said:
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Click to expand...
Click to collapse
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Daan_K said:
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Click to expand...
Click to collapse
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
IvI97 said:
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
Click to expand...
Click to collapse
Hey, a couple of things: one, i've updated the guide, it's around, much simpler to use. just saying. Two, this guy has the right driver. Don't confuse him with DFU while at least for now it is not.
Choose an username... said:
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
Click to expand...
Click to collapse
omg the triangle is gone, thankyousomuch, but what can I use now 2 fix it further?? is that in your guide maybe?
choose an username... said:
hey, a couple of things: One, i've updated the guide, it's around, much simpler to use. Just saying. Two, this guy has the right driver. Don't confuse him with dfu while at least for now it is not.
Click to expand...
Click to collapse
omygod it ****ing working, choose an username man, i can't thank you enough, seriously ur the best man lots of love for doing this
My problem is that I can't even try to do the procedure in the other threads that i've read because my pc simples dont recognize anything when i install the qualcomm drivers. Any tips? Thank you in advance. I want to try this thread [GUIDE][QFIL MODE]Unbrick your Le Pro3, tested and working. But simply the qualcomm port doesnt appear in the device manager.
Bad cable or need to reinstall drivers...
marik1 said:
Bad cable or need to reinstall drivers...
Click to expand...
Click to collapse
I tried with two different cables and reinstalled the drivers a few times now. No port in the device manager. Just the Android ADB Interface tha showed when I installed the leeco adb drivers. On the ports just appear the standard Comunication port and printer port. I tried everything, the volume bottons power, etc. The Flash One dont recognize the phone for QFIL.
Say sth more about your phone state and history...
marik1 said:
Say sth more about your phone state and history...
Click to expand...
Click to collapse
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
I've no idea how to help you... Sorry.
gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
tsongming said:
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
Click to expand...
Click to collapse
I've tried four different cables now and nothing. Thank you for minding but I think there isn't a solution for my leeco. Its dead and no one can help him.
Is yours 722?
Sent from my SM-A730F using xda premium
mchlbenner said:
Is yours 722?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
No, x720 6gb ram 64 rom.
gradim said:
No, x720 6gb ram 64 rom.
Click to expand...
Click to collapse
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
mchlbenner said:
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
Completely dead, just vibrates when I press power and yes, I sometimes have the red light, sometimes flashing, sometimes stable.
gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Your phone is probably fixable.
Based on what you stated above, it seems that you downloaded and attempted to install the wrong version of TWRP and now your phone has no recovery at all.
Here is partial instructions I posted in the unbricking forum : https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Use those instructions along with is mentioned below. I have personally helped so many people unbrick their phone that I have lost track and this is the reason why the posts are so long and extensive. Because sometimes what works for one person does not work for the next. So I have essentially have taken everyone's great advice and updated the links, made the instructions steps a little more concise and easier to read, fixed some incorrect steps or added the needed skipped steps. Plus added my own research into what I believe is now a definitive guide for unbricking the Leeco variants X720 and X727. The point of not reposting the information here is to keep everything from becoming more fragmented.
Yes, it's possible that you have a hardware issue. But, its also possible that it can be fixed!
Remember that you will not see the port unless you are in EDL mode
Just press volume △ (+) and volume ▽ (–) buttons together while powering the phone on.
It should now be EDL mode. If you cannot get into EDO mode, you cannot do anything else.
If you get an error, press and hold the power button while at the same time hold vol up + and down simultaneously plug the usb cord into the back of the computer while holding the buttons.
Yes, It's a pain and this is why the deep flash cable is handy....it's a special cable ( so your extra cables will do nothing to help you) The deep flash cable will automatically put your phone into EDL mode and allow you to use Flash on.
Install the Qualcomm QDLoader 9008 driver: https://goo.gl/9E3bKq or the from links provided in the unbrick forum.
There are multiple versions or Qfil, some have issues. I posted the correct one that works.
FOR anything else go to that forum read my and everyone else's posts. Again, I keep all of my linked files are up to date, and many are located on my own drives.
You can make one of these cables. Here's a video that shows you how:
https://www.youtube.com/watch v=kSiGsYK66gM&lc=z220yhtqvwyyct21pacdp432sh2xjecek10dae1jen5w03c010c.1524884617336803
it will not be a quick fix.
There are 4 or 5 different unbricking options and it requires persistence and patience.
The good news is that your phone has a solution that may work.
So when your where flashing a rom you got error 7 and your phone went dead.
I had gotten that same error.
Error could mean two things 1) update recovery or update firmware.
My point is sounds nice like hardware issue.
These phones are known for just dieing.
Also getting into that mode you have to push power+volume+volume- at the same time.
Sent from my SM-A730F using xda premium