HI everybody, I have a very big problem with my zuk. Trying to solve a problem about network, I thought to come back to stock via fastboot. But given that I was tired doing so many tries, I wrongly flash a zip file via fastboot instead of use adb, so the phone didn't turn on anymore. I must say first of all that it isn't my first phone, so I'm not a newbie. The real problem is: When I plug Zuk into my Pc( Windows 10) it isn't recognized as qhsusb_bulk ( It could be easy to solve the problem) but as "unknown usb device (Device Descriptor Request Failed)". I try to plug the phone pressing every button like Vol+ and power, Vol- and power but nothing to do. I' m already in Test Mode on Windows 10 and I deleted every Zuk or Qualcomm Drivers. Anyone can help me?
Thank you
Ps: Even If the screen is always off, Is there a way to boot into fastboot mode with hardware keys?
Xluk3 said:
HI everybody, I have a very big problem with my zuk. Trying to solve a problem about network, I thought to come back to stock via fastboot. But given that I was tired doing so many tries, I wrongly flash a zip file via fastboot instead of use adb, so the phone didn't turn on anymore. I must say first of all that it isn't my first phone, so I'm not a newbie. The real problem is: When I plug Zuk into my Pc( Windows 10) it isn't recognized as qhsusb_bulk ( It could be easy to solve the problem) but as "unknown usb device (Device Descriptor Request Failed)". I try to plug the phone pressing every button like Vol+ and power, Vol- and power but nothing to do. I' m already in Test Mode on Windows 10 and I deleted every Zuk or Qualcomm Drivers. Anyone can help me?
Thank you
Ps: Even If the screen is always off, Is there a way to boot into fastboot mode with hardware keys?
Click to expand...
Click to collapse
Not that I know,do you have the stock recovery or twrp?
I have the exact problem with my new zuk z1. Any idea is appreciated. The nice phone seems lost now.
Seems like you'll have to restore your zuk to the zui version again. Do you have qrst and zui version downloaded??
The service port never pops up
I do have the qpst and the zui rom. The main obstacle is that qualcomm service port never pop up.
Setup.zuk said:
I do have the qpst and the zui rom. The main obstacle is that qualcomm service port never pop up.
Click to expand...
Click to collapse
try this:
start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Nikosstamatiou said:
try this:
start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Click to expand...
Click to collapse
So i am having the same problem. The phone is not being recognized by the software. That is the whole problem. Any ideas?
Tarsa said:
So i am having the same problem. The phone is not being recognized by the software. That is the whole problem. Any ideas?
Click to expand...
Click to collapse
Actually, I think the problem is, that it will not reach the fastboot mode, due to the non-stop process of system-updating and boot-loop. I can observe for a very short time the message 'systemupdate will be installed' and then the screen becomes black again. This procedure is repeating every time. I will wait till the battery is empty and see, whether the boot with Volume-+--USB-cable will work.
mikarbach said:
Actually, I think the problem is, that it will not reach the fastboot mode, due to the non-stop process of system-updating and boot-loop. I can observe for a very short time the message 'systemupdate will be installed' and then the screen becomes black again. This procedure is repeating every time. I will wait till the battery is empty and see, whether the boot with Volume-+--USB-cable will work.
Click to expand...
Click to collapse
PLease do update me if you manage to fix it. This is getting very frustrating
I have the same problem, caused after a cyanogenmod update... Did someone fix this??
Another hard bricked Z1 here.
QFIL recognizes the phone (as Qualcomm 9008 etc.). So I am able to click Download, but after a few seconds, it fails with these errors:
Code:
[...]
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
in QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
in QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
I've tried many many times, and many different things. Still no luck .
I'd appreciate if anyone could input some new ideas of other stuff to try. Thanks
CarlosAir said:
Another hard bricked Z1 here.
QFIL recognizes the phone (as Qualcomm 9008 etc.). So I am able to click Download, but after a few seconds, it fails with these errors:
Code:
[...]
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
in QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
in QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
If tried many many times, and many different things. Still no luck .
I'd appreciate if anyone could input some new ideas of other stuff to try. Thanks
Click to expand...
Click to collapse
No idea, my device is actually dead.
mikarbach said:
No idea, my device is actually dead.
Click to expand...
Click to collapse
Aw .
I don't want to lose hope, but everything I've tried so far has failed. :| , and I don't know what else to try.
CarlosAir said:
Aw .
I don't want to lose hope, but everything I've tried so far has failed. :| , and I don't know what else to try.
Click to expand...
Click to collapse
Try another cable, another USB slot, another pc/laptop
mikarbach said:
No idea, my device is actually dead.
Click to expand...
Click to collapse
try to flash cos 12.1 with qfil.
its there somwhere on 4pda forum(search there).
Sent from my Z1 using XDA-Developers mobile app
So guys if I try to flash unofficial CM 13 do I risk bricking the device for good???
t.h.i said:
try to flash cos 12.1 with qfil.
its there somwhere on 4pda forum(search there).
Sent from my Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Of course I have tried this, with two different computers and two different USB cable, both actually working on my N5X. But the point is, that I do not reach the point, that qfil recognizes the phone. Also not with the trick of starting with power-button/USB-cable. It constantly tries to reboot and with adb I get a message 'not authorized' .
---------- Post added at 11:17 AM ---------- Previous post was at 11:05 AM ----------
carlese said:
So guys if I try to flash unofficial CM 13 do I risk bricking the device for good???
Click to expand...
Click to collapse
I think in my case the after the first successful CM13-snapshot-installation was two fold:
1. I have not enabled USB-debugging and do not have had connected it to my computer after the first CM13-installation.
2. Due to some unknown reason the automatically update via CM itself has boot looped.
The second point is not a real problem, I think. I have had a bootloop many times before with other phones, as well as with the Zuk, but I was always able to resolve the problem with adb. I think the first point was the problem, so adb wasn't possible, due to authorization problems. The reason why qfil does not work, I really do not know exactly, but qfil in fact was not able to recognize the phone.
I have the same problem. Totally bricked.
No charge, no PC recognise, nothing.
I tried with QFIL but the PC does not recognise the port.
I don't know what else I can do. Any ideas?
Thanks!
alexisdance said:
I have the same problem. Totally bricked.
No charge, no PC recognise, nothing.
I tried with QFIL but the PC does not recognise the port.
I don't know what else I can do. Any ideas?
Thanks!
Click to expand...
Click to collapse
Sry, no I do not have
Hello!
I have dealt with this sort of problem before and have successfully un-bricked my friend's device. I will be posting a guide to solve this problem soon.
Hang-on!
Related
Hi all,
I have a serious problem with my G2 which I could not solve: I used the new LG Flash Tool 2014 with stock KDZ file, everything was going just fine till I received an error message that LG server is not available, I disconnected the USB cable by mistake from my G2 and afterward I saw that it was in the middle of flashing process (12% was completed). I turned it off and tried to reach download mode again and nothing!, I'm receiving the "LG" logo and nothing- the screen goes black (it is still on).
I tried also to connect my phone to the computer- I received a list of 13 "new" local disks "H" to "T", only "H" disk is available and it's showing "image" folder with list of files.
I cannot reach "download mode", nothing is working!
I hope this is not the end for my G2..
please help me
Thank you so much!
If you could receive all those hard disks then you could maybe fix it with linux/ubuntu if you have it. Search for guides to cOpy the neccesary stuff bacK like the bootloader. I can't really help you atm as i am too sleepy.
wulsic said:
If you could receive all those hard disks then you could maybe fix it with linux/ubuntu if you have it. Search for guides to cOpy the neccesary stuff bacK like the bootloader. I can't really help you atm as i am too sleepy.
Click to expand...
Click to collapse
Thank you for your reply. I found this on the sticky threads: "[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2".
I installed ubuntu and followed the instructions. when I type the following: "gdisk -l /dev/sde" I receive an error message:
"GPT fdisk (gdisk) version 0.5.1
NOTE: Write test failed with error number 13. It will be impossible to save
changes to this disk's partition table!
Problem opening /dev/sde for reading! Error is 13
You must run this program as root or use sudo!"
My device is not rooted, is this the problem?
Please help me!!
Thanks
@NNCa It says you need to run the program as root on ubuntu.
Just use sudo in front of the commands.
You need to type once your password to use sudo, you can't see the password if you enter it for safety I guess but just click enter after you typed ykur password.
wulsic said:
@NNCa It says you need to run the program as root on ubuntu.
Just use sudo in front of the commands.
You need to type once your password to use sudo, you can't see the password if you enter it for safety I guess but just click enter after you typed ykur password.
Click to expand...
Click to collapse
Thank you so much!!
I succeeded to push all the files according to this thread, however I do not see the TWRP menu. I have just constant "LG" logo on screen.
Do I miss something?
Thanks!
NNCa said:
Thank you so much!!
I succeeded to push all the files according to this thread, however I do not see the TWRP menu. I have just constant "LG" logo on screen.
Do I miss something?
Thanks!
Click to expand...
Click to collapse
Well its good you're an step further, try to reboot to recovery using power+volume down i believe or its up idk try both it should say something about wipe data factory reset, press the power button and you are in recovery.
wulsic said:
Well its good you're an step further, try to reboot to recovery using power+volume down i believe or its up idk try both it should say something about wipe data factory reset, press the power button and you are in recovery.
Click to expand...
Click to collapse
Hi,
I powered off my phone by pressing volume down + power for a while ("LG" logo blinked once and phone was fully powered off).
I pushed volume down + power till I saw the LG logo, released it, and pushed again- and finally I reached the Factory Hard Reset screen. I have pushed 3 times the power, and I have got "Factory reset processing..." and nothing is appeared, even when I'm pushing several times on power again.
I guess this is the end of my G2 :crying:
Thank you all for your support, this is an excellent forum!:good::good:
NNCa said:
Hi,
I powered off my phone by pressing volume down + power for a while ("LG" logo blinked once and phone was fully powered off).
I pushed volume down + power till I saw the LG logo, released it, and pushed again- and finally I reached the Factory Hard Reset screen. I have pushed 3 times the power, and I have got "Factory reset processing..." and nothing is appeared, even when I'm pushing several times on power again.
I guess this is the end of my G2 :crying:
Thank you all for your support, this is an excellent forum!:good::good:
Click to expand...
Click to collapse
Nope it isn't the end try to install the recovery again or try to push the custom twrp recovery again to the right partition! Dont give up that fast when i hear your things then its still fixable! you already got the factory reset processing so try to Push the Recovery again and search for an guide about recovery maybe Then you would probably get your device fixed.
Just read my things about simplicity so think easy and you can fix it. AND STAY POSITIVE You will repair your phone today :good:
wulsic said:
Nope it isn't the end try to install the recovery again or try to push the custom twrp recovery again to the right partition! Dont give up that fast when i hear your things then its still fixable! you already got the factory reset processing so try to Push the Recovery again and search for an guide about recovery maybe Then you would probably get your device fixed.
Just read my things about simplicity so think easy and you can fix it. AND STAY POSITIVE You will repair your phone today :good:
Click to expand...
Click to collapse
Thanks, but after connecting the device to linux/windows, it seems that it is not recongized, I do not see the partitions anymore even when typing "ls /dev/sd*" through linux terminal..
NNCa said:
Thanks, but after connecting the device to linux/windows, it seems that it is not recongized, I do not see the partitions anymore even when typing "ls /dev/sd*" through linux terminal..
Click to expand...
Click to collapse
Yeah because the phone has bootloader etc again so maybe you can try this:
http://forum.xda-developers.com/showthread.php?t=2432476
wulsic said:
Yeah because the phone has bootloader etc again so maybe you can try this:
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
Hi there,
I tried to flash my phone using the lg flash tool, unfortunately it cannot recognized any connected device through USB.. I don't know what else will work for my device
NNCa said:
Hi there,
I tried to flash my phone using the lg flash tool, unfortunately it cannot recognized any connected device through USB.. I don't know what else will work for my device
Click to expand...
Click to collapse
Did you already installed the LG drivers? and checked in device manager or there is like any change when you connect and disconnect your phone?
wulsic said:
Did you already installed the LG drivers? and checked in device manager or there is like any change when you connect and disconnect your phone?
Click to expand...
Click to collapse
Yes, I checked it- no response during connecting/disconnecting the device..
Maybe I did a mistake when trying to push those image files.. I guess there is nothing I can do to fix my phone..
Do you have any other suggestions?
Can someone please help me. How can I get to the LG device- Is there another software I can use to flash files into this device?
Thanks
NNCa said:
Can someone please help me. How can I get to the LG device- Is there another software I can use to flash files into this device?
Thanks
Click to expand...
Click to collapse
Sorry for late reaction but i needed to think of something. Did you tryed to use another cable? Did you tryed to do it on another pc? Did you tryed to maybe install LG PC suite and see if it gets recognized? If you have the PC Suite you may need to turn it off in the LG flashtool idk. Can you tell us more like which windows you have?
wulsic said:
Sorry for late reaction but i needed to think of something. Did you tryed to use another cable? Did you tryed to do it on another pc? Did you tryed to maybe install LG PC suite and see if it gets recognized? If you have the PC Suite you may need to turn it off in the LG flashtool idk. Can you tell us more like which windows you have?
Click to expand...
Click to collapse
Hi,
I tried all you suggested, however my devide is not recognized. I tried to use the LG PC Suite and to flash by IMEI, however it is still saying that no device was connected.. I checked windows device manager, and nothing changed there.
There is any chnage I can see my connected device? use some tool or another software?
Thank you again for your patience and help!
NNCa said:
Hi,
I tried all you suggested, however my devide is not recognized. I tried to use the LG PC Suite and to flash by IMEI, however it is still saying that no device was connected.. I checked windows device manager, and nothing changed there.
There is any chnage I can see my connected device? use some tool or another software?
Thank you again for your patience and help!
Click to expand...
Click to collapse
Hi, sorry to say but you have unfortunately completely hardbricked your device. It happened to me too however I was able to get it replaced under warranty at no extra cost.
What happened was that when your phone was still detected by linux, you had a chance to recover by flashing the correct partitions to gain access to download mode and from there, flash a KDZ to go back to complete stock. However, the files you used were probably incompatible with your variant which has now corrupted your bootloader sequence. I suggest you read this reply by fizzy177 as well as the rest of the thread: http://forum.xda-developers.com/showpost.php?p=51522304&postcount=118
So right now, you cannot do anything as you have already found out, no computer will recognise that your phone is plugged in. Your phone fails to boot when you try enter the download mode and it just freezes on the splash screen which looks like this: http://www.lg-phones.org/wp-content/uploads/2014/03/image2.png
What's meant to happen is your phone should load past that initial splash screen into this http://www.androiddunya.com/wp-content/uploads/2014/01/LG-G2-DownloadMode.jpg which accepts KDZ flashing and warns the device has been rooted.
So it's a blessing that your phone cannot boot as LG cannot find out you have voided warranty and you will be able to get a replacement free of charge.
Issue was solved- device was fixed under warranty
Hi,
I just want to update you all that my device was fixed under warranty! (motherboard replacement)
Thank you all for help and great support, this is a great forum with great community :good::good:
Hello
From past 2 weeks i am wondering on internet for a solution . Hours and hours of surfing and articles but still
Hope some one solve this issue.
Okay. First i m using LG G2 F320 K update to lollipop . Non rooted. It was working fine . I can transfer files in MTP .
But about a month ago i get an update for my phone . And after some days i need to transfer some files to my phone , i wonder when i connected my phone to computer nothing happened . No notification on mobile for changing PTP MTP option . Also nothing happened in Computer device manager..
From that day i am unable to connect my phone with windows 10. It always charging mobile.
I uninstalled all drivers in device manager and installed from LG website. I updates windows N and NK MTP update from windows for windows 10.
I changed different data cables and different computers and different ports . All stuff i can do. Still no luck.
When ever i plug USB data cable it always put my Mobile on Charging . No notification on Mobile. Also i go in setting > storage> and there is no option in upper right corner to select USB PC connection .
I am in developer mode and debugging mode is on also. Also USB tethering option is Disabled .
Kindly some one help me regarding this.
LG G2 F320K updated to stock Koren lollipop 5.0.1 . Non root.( i updated lollipop in April 2015)
Issue i am facing is no notification for Charging/ MTP/PTP Usb Debugging on mobile notice bar when i attach my phone using USB cord with computer. Also in computer device manager nothing happen. Even i checked on windows 10 , 8.1, 8, 7 .
I remember it was working like charm 4 weeks before I can change MTP PTP or Charge only mode by selecting notification when i attach it to my laptop. I can transfer files can use LG PC suit .
Then i received an software update like 40 mb and i updated my mobile. That i remembered.
After that 2 weeks before i need to transfer some books from laptop to my mobile. When i plugged my device there no notification to select MTP mode . Also there is nothing happened in my windows 10. I looked in task manager. No yellow icon in computer task manager for driver thing.
Laptop is just silent and mobile is just on charging .
Then i go to setting in LG and looked for USB PC connection settings. I wonder there is nothing . Settings > storage > 3 dot in upper right corner.. it suppose to be there . But here is no 3 dot in storage. Then i looked into share and networks in android setting and i found that USB tethering. But its faded mean it is disabled and i am unable to use this feature also.
I tried on different computers different cables , original, but nothing. Always when i plug usb mobile went on charging and in all computers nothing happen in device manager.
USB debugging is on.. I factory reset device 2 times. but useless. Also i uninstall all drivers from my laptop and then reinstall drivers from LG website also i tried google drivers , ABD, different ports. Nothing nothing happen.
Also now if i try put mobile on download mode by turning device off and then push + vol button and then put cord in mobile . No download mode also it went on charging. Well charging from laptop or from charger is okay.
Hope i explain all.
So I intstalled the WP10 preview which includes support for the 520, but the settings app didn't work and I couldn't reset the device so I used the Windows Phone Recovery Tool to revert to 8.1. However, as the firmware was about to install, the device went into flash mode (as it does while installing a firmware) and an error dialgue opened on my laptop saying that there was an error. After that my phone's screen went black and its not vibrating or powering on even when connected to a power source. I doubt that it is restorable, but any help would be much appreciated
Thank you guys for letting me know about the link I'm posting it in the OP so that everyone having this issue can upvote on that thread.
Link: https://social.technet.microsoft.co...e-recovery-possible?forum=WinPreview2015Phone
theevilpotato said:
So I intstalled the WP10 preview which includes support for the 520, but the settings app didn't work and I couldn't reset the device so I used the Windows Phone Recovery Tool to revert to 8.1. However, as the firmware was about to install, the device went into flash mode (as it does while installing a firmware) and an error dialgue opened on my laptop saying that there was an error. After that my phone's screen went black and its not vibrating or powering on even when connected to a power source. I doubt that it is restorable, but any help would be much appreciated.
Click to expand...
Click to collapse
I've just got the exact same error and I've spent the last hours trying everything possible and every tutorial to make it work. I'm afraid it's completely bricked. It's not responding to anything, when plugged into the pc it shows up as "QHSUSB_DLOAD" which is usually a very bad sign, and every software recovery or phone recovery tool I've tried from MS and Nokia either don't detect it or say it's not supported.
It's dead.
520? :/ Same here. Time to get a new phone for school, I guess.
Yes, a 520 as well.
Just a heads up, if you give the windows phone subreddit a quick read you'll notice we are not the only people to have this issue. Apparently several other people trying to roll back their phone have it completely bricked and in the QHSUSB_DLOAD situation.
I don't think MS can do anything about it, since the boot crapped out you either need to buy the tools or get it repaired by someone having them, but at least it proves there is some kind of problem with rolling back from the preview.
angstdasein said:
I've just got the exact same error and I've spent the last hours trying everything possible and every tutorial to make it work. I'm afraid it's completely bricked. It's not responding to anything, when plugged into the pc it shows up as "QHSUSB_DLOAD" which is usually a very bad sign, and every software recovery or phone recovery tool I've tried from MS and Nokia either don't detect it or say it's not supported.
It's dead.
Click to expand...
Click to collapse
same here
After a bit of reading more and more people are reporting this, so please put your own experience on this technet thread, it's a good idea to centralize reports where Microsoft can see it.
I can't link it here (don't have the permission to post links yet) but it's the first result by typing "Lumia 620 bricked during rollback procedure: recovery possible?" in google.
NL525 w/ red screen here.
feherneoh, pls make tutor!
feherneoh said:
Here it is:
...
Click to expand...
Click to collapse
Praise the Lord feherneoh!
Greatest thanx to ya!
Same error here, black screen and phone do nothing.
Tried with Thor2 but didn't work.
azogh said:
Same error here, black screen and phone do nothing.
Tried with Thor2 but didn't work.
Click to expand...
Click to collapse
Be sure using good cable. Try few times (i did 3)
[QRCODE][/QRCODE]The same problem with L520. There is already post on Technet regarding this problem
You can search Google by typing in: QHSUSB_DLOAD technet
Please upvote, then we would have some respond from Microsoft, maybe alternative driver, tool or something...
My Nokia does not turn on
The same problem! My Nokia does not turn on. I've tried everything! Any solution?
rickmaran said:
The same problem! My Nokia does not turn on. I've tried everything! Any solution?
Click to expand...
Click to collapse
I don't think there is a solution yet. Just keep and eye on this and hope for the best: https://social.technet.microsoft.co...e-recovery-possible?forum=WinPreview2015Phone
Have you anyone has try using Lumia Recovery Tool ?
1. Download ffu saperatly. (8.1 GDR1)
2. Install Lumia Software Recovery Tool.
3. Launch recovery tool.
4. Remove battery, usb, device.
5. Select my phone doesn't respond in recovery tool.
6. Insert battery, usb, plug it to pc.
7. A- Press and hold volume down.
B- Press and hold Power + volume down
8. Flash it.
Hope this will work.
feherneoh said:
Here it is:
1: Find your Recovery Tool folder on your harddisk. Mine is "C:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recovery Tool"
There should be a file called thor2.exe there.
2: Open an administrator command prompt here
3: Find the ROM Recovery Tool downloaded. Should be in "C:\ProgramData\Microsoft\Packages\Products"
You will need the FFU file for your device.
Mine is "C:\ProgramData\Microsoft\Packages\Products\rm-914\RM914_3058.50000.1425.0005_RETAIL_eu_hungary_429_05_443088_prd_signed.ffu"
4: To flash your device with THOR2, enter this to commandline:
Code:
thor2 -mode uefiflash -ffufile "C:\ProgramData\Microsoft\Packages\Products\rm-914\RM914_3058.50000.1425.0005_RETAIL_eu_hungary_429_05_443088_prd_signed.ffu"
Replace filename with your own
5: After flashing completes, reboot your phone by entering this:
Code:
thor2 -mode rnd -bootnormalmode
Click to expand...
Click to collapse
It says this error:
THOR2 1.8.2.14 exited with error code 393220 <0x60004>
Click to expand...
Click to collapse
zuchit said:
It says this error:
Click to expand...
Click to collapse
Same case
Same problem with DLOAD
The solution seems to do a JTAG... Bad news for normal people ::crying:
Bricked Nokia Lumia
Actually, the red screen means that the phone went into its UEFI MODE.
In UEFI MODE your phone could be restored as normal by a HARD RESET (see key combo).
If you have a hard luck, your phone will automatically start in Flashing Mode (IMO(0x0000001)) which only works on the downloading procedure when on Rolling back.
The RollBack program has to put your phone in Flashing Mode in order to gain access to it's microchip.
Well the app itself knows what to do, but something failed.
In this point, you disconnected the phone and tried all you've known to power it on. Meanwhile the app deleted it's cache file, it no longer knows why your phone is in that state and your PC will get it as QHSUSB_DLOAD which is a Side_Load driver for Qualcomm Enabled Phones.
At this point, RIFF JTAG is the only solution as your BOOTLOADER is dead.
Good thing? It could be fixed by any GSM Service and the price could be small.
DO NOT try any Nokia Care / Refurbish / Restore app. All of them are created to work with a phone that has it's bootloader working.
None of them will cooperate to reflash it.
Even if you manage to reflash the OS, you don't have a BIOS / BootLoader....
Hopefully, Microsoft will create a tool to fix this as it only occurs when Rolling Back from Windows 10 Tech. Prev. and 8.1 to 8.
But until that, your phone is dead.
Source of info: I'm working as an G.S.M. RepairMan.
feherneoh said:
Maybe some error message before this?
Click to expand...
Click to collapse
at the moment, i get this error when i cmd thor right after connecting phone to usb. (screenshot 1)
i58.tinypic. com/2qnz51d.jpg
Click to expand...
Click to collapse
these is what it says when i try cmd thor after red screen with Nokia logo appers.. (screenhot 2)
i61.tinypic. com/jkftq8.jpg
Click to expand...
Click to collapse
I will try to explain everything from the beginning. I was about to install a custom rom install (it was in 7.1.1 stock, unlocked bootloader) so when I was going to do full wipe with lastest TWRP there was an error. Wait for about 15 minutes just in case, but nothing happened so I decided to restart it to try again. But the phone stuck in the ZTE logo and if it tried to enter TWRP was stuck in the logo too, I tried with all versions of TWRP and no one works. Find a post that said I could use TWRP tenfars tool to recover my phone and had to enter the EDL mode. I managed to put the phone in edl mode but now I can not get out of it. I press and hold the power button for a minute and nothing happens (no vibration, no led, no ZTE logo) my pc just does the unplug windows sound. My pc recognizes the phone as QUSB_BULK. When I try to use the tenfars tool I get this message:
C:\Users\Alejandro Saavedra\Downloads\minimal_adb_fastboot_1.4.1_portable>axon7tool -w recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Also try using the xiaomi MiFlash tool (even change the drivers from QUSB_BULK to COM COM 5) but something similar happens, also tells me can not recive hello package.
I'm a little new to this so I beg you a little patience
Please work very hard to buy this phone, there has to be some way to unbrick it. :crying:
If you need any additional information just tell me
If you use axon7tool :
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
If you use MiFlash :
get latest version : https://www.androidfilehost.com/?fid=673368273298954241
check in Devices Manager if is called Qualcomm 8004.
CelesteBlue said:
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
Click to expand...
Click to collapse
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund
Smedslund said:
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund
Click to expand...
Click to collapse
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.
CelesteBlue said:
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.
Click to expand...
Click to collapse
You will find tenfar 3.0.2-2 TWRP at download center:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Once unzipped, copy it to recovery.bin:
copy twrp_rec_tenfar.img recovery.bin
Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something
ale0796 said:
Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something
Click to expand...
Click to collapse
That's because you reset the EDL that way. the method is weird but seemed to work...
If you hold the 3 buttons for ~10 secs while the device is in EDL it will reset it
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
Actually, it is a nice feature for the few seconds it lasts, but read HERE if you must. Be careful!
Good luck
CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
I'd advice against doing it... I had no trouble with it but a bunch of people now have paperweights. But yeah, the link is the one provided by the other guy above me
Thank you so much @Choose an username... and @amphi66 : that worked !
Anyway I am on G B04 (Nougat).
Do you know some cool mods I should do ?
Like debloat, remove the boot message (done), etc...
My Asus Zenfone Max Pro M1 is stuck on the screen," Powered by Android". I have neither rooted nor unlocked the bootloader. I had received the error of "Your device is corrupted" and had followed the guide to remove that. For a month, my phone lagged and had a drop in battery. Restarting it has caused it to not work.Now, it's showing no signs of starting. Any help will be sincerely appreciated!
manav113 said:
My Asus Zenfone Max Pro M1 is stuck on the screen," Powered by Android". I have neither rooted nor unlocked the bootloader. I had received the error of "Your device is corrupted" and had followed the guide to remove that. For a month, my phone lagged and had a drop in battery. Restarting it has caused it to not work.Now, it's showing no signs of starting. Any help will be sincerely appreciated!
Click to expand...
Click to collapse
download 059 fastboot rom[search in forum you will find 059 fastboot rom. it is in-(how to use flashtool thread)]
unzip it.
connect your phone with pc as in fastboot mode.
double click on flashallAFT.bat or .cmd file from fastboot rom folder.
059 fresh installtion will be donw by this although you will lose all your data so please backup if possible.
after that if u still have that 'your device is corrupt' error follow my thread . corrupt state fix command dosnt mess with your system whatsoever. so either u deleted some files accidently or it got deleted during update. dont blame any buddy regarding that.
P53mutant said:
download 059 fastboot rom[search in forum you will find 059 fastboot rom. it is in-(how to use flashtool thread)]
unzip it.
connect your phone with pc as in fastboot mode.
double click on flashallAFT.bat or .cmd file from fastboot rom folder.
059 fresh installtion will be donw by this although you will lose all your data so please backup if possible.
after that if u still have that 'your device is corrupt' error follow my thread . corrupt state fix command dosnt mess with your system whatsoever. so either u deleted some files accidently or it got deleted during update. dont blame any buddy regarding that.
Click to expand...
Click to collapse
Thanks for Replying bro. TMy phone is not going to any mode ie neither fastboot nor recovery. Its only showing Powered by Android whatever combinations I go with.I am thinking to try the QFIL s/w.
manav113 said:
Thanks for Replying bro. TMy phone is not going to any mode ie neither fastboot nor recovery. Its only showing Powered by Android whatever combinations I go with.I am thinking to try the QFIL s/w.
Click to expand...
Click to collapse
go for qfil then but use 059 qfil otherwise 130 qfill u will lose your persist,factory,fsg partition. doownload 059 fastboot rom . it is combined fastboot qfill rom. use it same as other qfill rom but choose here ww_no-nfc_no-fsg raw program.
btw your device showing powered by android that means u can go into fastboot mode and recovery mode both. just press and hold power button untill u see restart of ur screen. as soon as u see that press violume up along with power key. u will def get acess to fastboot mode.
P53mutant said:
go for qfil then but use 059 qfil otherwise 130 qfill u will lose your persist,factory,fsg partition. doownload 059 fastboot rom . it is combined fastboot qfill rom. use it same as other qfill rom but choose here ww_no-nfc_no-fsg raw program.
btw your device showing powered by android that means u can go into fastboot mode and recovery mode both. just press and hold power button untill u see restart of ur screen. as soon as u see that press violume up along with power key. u will def get acess to fastboot mode.
Click to expand...
Click to collapse
Didn't worked.. QFIL s/w was not able to detect the port even after connecting the mobile.. Tried to completely discharge and recharge hoping it would work.. Now, its not even recharging.. Nothing works now..Feels like a motherboard problem now..Should I rebuy the 4GB version or look for another mobile?
Try asus service center
manav113 said:
Didn't worked.. QFIL s/w was not able to detect the port even after connecting the mobile.. Tried to completely discharge and recharge hoping it would work.. Now, its not even recharging.. Nothing works now..Feels like a motherboard problem now..Should I rebuy the 4GB version or look for another mobile?
Click to expand...
Click to collapse
motherboard issue not lead to sudden death of phone. did u encounter random reboot before every 10-20 mins if not no worry.
for qfill u have to turn off your phone and press vol + and vol - together and have to connect your hpone with pc. check device manager of pc it will show port and comt device 2-3 mins after successfull qualcomm diag port driver installation.
98har**** said:
Try asus service center
Click to expand...
Click to collapse
No response. They said they aren't able to fix it. Can give 1k for the lcd screen.. :crying:
P53mutant said:
motherboard issue not lead to sudden death of phone. did u encounter random reboot before every 10-20 mins if not no worry.
for qfill u have to turn off your phone and press vol + and vol - together and have to connect your hpone with pc. check device manager of pc it will show port and comt device 2-3 mins after successfull qualcomm diag port driver installation.
Click to expand...
Click to collapse
Didn't had any random reboot stuff. I thought voltage fluctuations might have affected it. I had charged it at the Airport the same day the phone gave up. The QFIL software was not able to detect port even while pressing vol+ and vol- .Service Centre tells me its a PCB problem and are asking 3k for repair. Looks like a new phone is somewhere in the line for future.
manav113 said:
Didn't had any random reboot stuff. I thought voltage fluctuations might have affected it. I had charged it at the Airport the same day the phone gave up. The QFIL software was not able to detect port even while pressing vol+ and vol- .Service Centre tells me its a PCB problem and are asking 3k for repair. Looks like a new phone is somewhere in the line for future.
Click to expand...
Click to collapse
well good riddance
Really hoping someone can help me out here. I have a Nexus 6P, Non-BLOD. Yesterday, after clean flashing the latest version of EvoX, while setting some things up, device randomly crashed. No Shut down animation or anything. Just black screen. Tried turning it on via Power Button and then Power And Volume Buttons but nothing works. Connected it to PC and see it's Detected as Qualcomm USB Bulk (9008) in Coms and Ports. Did some research and found out I have to flash via QFIL. And this is where I am stuck. I tried several versions, but it doesn't flash/gives Shara error. I tried reinstalling driver. I also read a guide here. But the Firmware link is dead and it says to flash via MiFlash, something I can't even try since the Link in the OP is dead. I tried some different versions of QFIL but all of them give a Sahara Communication error. Now I'm pretty much at a loss on what to do. I'd really like to fix my 6P. And I would appreciate anyone taking the time to point me in the right direction, or help me fix it. Thanks in Advance.
DarthVader said:
Really hoping someone can help me out here. I have a Nexus 6P, Non-BLOD. Yesterday, after clean flashing the latest version of EvoX, while setting some things up, device randomly crashed. No Shut down animation or anything. Just black screen. Tried turning it on via Power Button and then Power And Volume Buttons but nothing works. Connected it to PC and see it's Detected as Qualcomm USB Bulk (9008) in Coms and Ports. Did some research and found out I have to flash via QFIL. And this is where I am stuck. I tried several versions, but it doesn't flash/gives Shara error. I tried reinstalling driver. I also read a guide here. But the Firmware link is dead and it says to flash via MiFlash, something I can't even try since the Link in the OP is dead. I tried some different versions of QFIL but all of them give a Sahara Communication error. Now I'm pretty much at a loss on what to do. I'd really like to fix my 6P. And I would appreciate anyone taking the time to point me in the right direction, or help me fix it. Thanks in Advance.
Click to expand...
Click to collapse
Same thing happened to me in the same ROM (Weird) .. but i managed to flash the qfil successfully .. but still phone doesnt boot up .. here's what you should do ... try to hard reset the phone until you hear the disconnecting sound from pc . Ready all the necessary flash in the qfil and as soon as u hear the device connected hit the download button .. it will flash without the sahara protocol error . Be quick ! tell me if that fixed ur problem . Peace
hk1271 said:
Same thing happened to me in the same ROM (Weird) .. but i managed to flash the qfil successfully .. but still phone doesnt boot up .. here's what you should do ... try to hard reset the phone until you hear the disconnecting sound from pc . Ready all the necessary flash in the qfil and as soon as u hear the device connected hit the download button .. it will flash without the sahara protocol error . Be quick ! tell me if that fixed ur problem . Peace
Click to expand...
Click to collapse
Thanks. Can you share the files you used please? I can't for the life of me, find the correct download files. There was a Nexus6P_Unbrick by TenFar but all the links are down.
DarthVader said:
Thanks. Can you share the files you used please? I can't for the life of me, find the correct download files. There was a Nexus6P_Unbrick by TenFar but all the links are down.
Click to expand...
Click to collapse
I used another qfil firmware
https://drive.google.com/file/d/1PixuumVVzxBKUsQ88X3AJ21Hsi2mV3Zq/view
Here is the link .. you can find the firehose and all files in the firmare folder . Best of Luck
I have a similar situation where I am unable to power on the phone in any way, and I am only able to communicate with the qualcom USB 9008 driver.
I am following your instructions using the firmware files you provided (thank you!) and I can see an attempt is being made to download the files before sahara error occurs.
I don't think I enabled developer options when my Nexus 6P was working and wondered if sahara error is due to that.
I was wondering if you had previously enabled developer options by tapping on the build number several times, once the operating system booted and if that is a critical step in being able to recover the Nexus 6p from this hard bricked state where I am stuck in EDL 9008 mode, and unable to access bootloader, and volume+power keys do not do anything...I feel like I'm screwed (and already moved on) but using time these days to learn about android devices!
thanks!