Related
Hey guys
Please may your help me. I recently bought a Wileyfox Swift and decided to install CyanogenMod 12.1 for my phone. I installed CM12.1 successfully and used it for a week. 2 days ago I tried to restore stock by fastbooting the ROM found on NeedROM. After it installed my Swift just turned off and couldn't turn back on. My PC sees it as Relink HS-USB QDLoader 9008. May someone please provide me with a way to unbrick this device?
Thanks
Regards
Y Lutch
yasteellutch said:
Hey guys
Please may your help me. I recently bought a Wileyfox Swift and decided to install CyanogenMod 12.1 for my phone. I installed CM12.1 successfully and used it for a week. 2 days ago I tried to restore stock by fastbooting the ROM found on NeedROM. After it installed my Swift just turned off and couldn't turn back on. My PC sees it as Relink HS-USB QDLoader 9008. May someone please provide me with a way to unbrick this device?
Thanks
Regards
Y Lutch
Click to expand...
Click to collapse
Connect phone to computer.
Take off battery. And wait.
Is your pc can detect your device on bootloader mode?
yasteellutch said:
Hey guys
Please may your help me. I recently bought a Wileyfox Swift and decided to install CyanogenMod 12.1 for my phone. I installed CM12.1 successfully and used it for a week. 2 days ago I tried to restore stock by fastbooting the ROM found on NeedROM. After it installed my Swift just turned off and couldn't turn back on. My PC sees it as Relink HS-USB QDLoader 9008. May someone please provide me with a way to unbrick this device?
Thanks
Regards
Y Lutch
Click to expand...
Click to collapse
Or google "Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 (if you have the right kind of rom)"
And use that method.
Yes
nhmanas said:
Is your pc can detect your device on bootloader mode?
Click to expand...
Click to collapse
My pc sees the phone in QDLoader 9008 mode
yasteellutch said:
My pc sees the phone in QDLoader 9008 mode
Click to expand...
Click to collapse
I don't know what that is but flash stock rom again via fastboot
General Mobile 4G Dual cihazımdan Tapatalk kullanılarak gönderildi
yasteellutch said:
My pc sees the phone in QDLoader 9008 mode
Click to expand...
Click to collapse
Open this link
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction here
FindYanot said:
Open this link
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction here
Click to expand...
Click to collapse
I shall try but I pray it works. I am literally stuck in Android Development without my phone, Emulators aren't good enough
My dear sir you are a freaking genius
You my friend are a genius. I dont know where you acquired these files. It works like brand new. Thank you sir. Thank you thank you thank you!!!!!!!!!!!!!!!!
One Problem.
FindYanot said:
Open this link
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction here
Click to expand...
Click to collapse
The phone wont turn on with battery in. It only turns on when I use usb without battery
yasteellutch said:
The phone wont turn on with battery in. It only turns on when I use usb without battery
Click to expand...
Click to collapse
Try flash stock rom via fastboot from here
http://builds.cyngn.com/factory/crackling/cm-12.1-YOG4PAS33J-crackling-signed-fastboot.zip
FindYanot said:
Open https://cloud.mail.ru/public/NExC/qxFwsmmmV/Wileyfox Swift/Recover SW/
"Драйвера" = Drivers. Dowload drivers for your system (86/64)
Download any Recover SW zip with ROM
Then download Tool + instruction https://mega.nz/#!YUFiXRwI!PlPCplXY31Rje57IfmWucTbRY6d56nSU6de46cQxIqU
Click to expand...
Click to collapse
Hi @FindYanot , are you able to upload WileyfoxTool1.0 exe on your website and also MEGA? I can't register at 4pda.ru as I always fail the CAPTCHA, even when I use the Russian Keyboard Viewer on Mac.
I have obtained the Android One (General Mobile 4G LUZ17E Retail build) prog_emmc_firehose_8916.mbn , emmc_appsboot.mbn , patch0.xml , rawprogram_upgrade.xml , system.img , NON-HLOS.bin etc. files from Longcheer but I can't get into Emergency Download Mode from my hardbricked Swift, even when pressing Volume Up or Volume Down + Power when inserting USB cable. 'fastboot devices' doesn't list the phone when connected via USB cable, and QFIL 2.0.0.3 within QPST 2.7.429 Qualcomm 9008 2.1.0.5 on Windows 10 x86 gives me a Sahara error and RELINK / Woowellstrong Electronic co., ltd 9008 2.0.0.0 on Windows 8.1 x64 gives me an EDL error.
Thank you.
dabotsonline said:
Hi @FindYanot , are you able to upload WileyfoxTool1.0 exe on your website and also MEGA? I can't register at 4pda.ru as I always fail the CAPTCHA, even when I use the Russian Keyboard Viewer on Mac.
I have obtained the Android One (General Mobile 4G LUZ17E Retail build) prog_emmc_firehose_8916.mbn , emmc_appsboot.mbn , patch0.xml , rawprogram_upgrade.xml , system.img , NON-HLOS.bin etc. files from Longcheer but I can't get into Emergency Download Mode from my hardbricked Swift, even when pressing Volume Up or Volume Down + Power when inserting USB cable. 'fastboot devices' doesn't list the phone when connected via USB cable, and QFIL 2.0.0.3 within QPST 2.7.429 Qualcomm 9008 2.1.0.5 on Windows 10 x86 gives me a Sahara error and RELINK / Woowellstrong Electronic co., ltd 9008 2.0.0.0 on Windows 8.1 x64 gives me an EDL error.
Thank you.
Click to expand...
Click to collapse
Would you mind posting those files, why aren't you using the Swift recover files as findyanot posted it fixed my one, it w was seen as 9008 after I installed driver, I also removed battery before plugging to PC.
Sent from my SM-N920I using Tapatalk
hmsq said:
... why aren't you using the Swift recover files as findyanot posted it fixed my one, it w was seen as 9008 after I installed driver, I also removed battery before plugging to PC.
Click to expand...
Click to collapse
I have those files as well, and get the same problem even when removing the battery.
hmsq said:
Would you mind posting those files...
Click to expand...
Click to collapse
Will do when I have a chance!
Hi,
I have a following problem with my Redmi 4X. I tried to flash new rom and reboot my phone on twrp. When the phone shut down nothing happens anymore just black screen. No fastboot or recovery mode. When I contact the phone to Windows pc it shows in device manager: Qualcomm HS-USB Diagnostics 900E (COM20). I have tried to flash new rom with QFIL and Miflash (tried to change the driver to Qualcomm HS-USB QDLoader 9008).
With QFIL the error is: Download Fail: Switch to EDL FailFailed to switch to Emergency Download mode.
With Miflash the error is: Cannot receive hello packet. MiFlash is trying to reset status!
Any suggestions?
https://www.youtube.com/watch?v=uxrhJkSZc6E
Already tried that. Doesn't seem to change a thing.
Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
C:\Windows\system32>
k4rpp4 said:
Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
Click to expand...
Click to collapse
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!
The test points seems to change nothing. I think that after the " adb devices" command I should see my device listed but that is not the case and therefore impossible to flash rom. Somehow I should be able to change the "900E mode" to "9008 mode" without changing the driver manually and I think the test point method should do just that.
Here is video of what I have tried to do. If someone could point out what to do differently to get the flash work I would be very grateful.
https://drive.google.com/open?id=1aOkb3FCBzanMUW3WSdyuxyQO-33rdsBv
Windows 10 will not accept the 9008 driver because the driversignature ist not signed from Microsoft.
If you will unbrick it with Windows 10 64bit look here: https://www.youtube.com/watch?v=2d8KEruHWPg
and here: https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Had allready done that also. Gave it another try without success
k4rpp4 said:
Had allready done that also. Gave it another try without success
Click to expand...
Click to collapse
Is the Qualcomm 9008 driver now installed?
Did you start the mi-flash tool with administrator privileges?
I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.
k4rpp4 said:
I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.
Click to expand...
Click to collapse
Perfect :good:
Bro please help my device in bricked
k23m said:
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!
Click to expand...
Click to collapse
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..
sayan990 said:
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..
Click to expand...
Click to collapse
I do had same issue with my mobile but even when I tried to flash MIUI I got "ACK count don't match" attached img
Hello everyone,
I recently stopped using my Nokia 8 in favor of my new iPhone 11. However, I wanted to keep it just so I have an emergency Android phone. I found an article that says that there is a possible way to update Nokia 8 via TWRP. Of course, I didn’t trust it, so I backed up my phone via TWRP. Here are the steps I took after back up:
- I deleted everything from the device including the OS, excluding SD
- I tried installing the image but it failed
- I then restored my backup
However, phone won’t boot even after I restored my backup. I followed these instructions (forum.xda-developers.com/nokia-8/how-to/guide-restore-nokia-to-stock-t3867646/) to flash the stock firmware, but the OST LA program keeps giving me 0xc3b9 something like tool func not ready. Can anyone help me? Thanks in advance!
- I have my bootloader unlocked, if anyone’s wondering.
EDIT: I have followed the steps with more care, and I managed to advance to the flashing process, but it gets a new error; 0xc6DA
EDIT 2: I realized I don't have critical unlocked. I can't access my unlock.key since download link expired long ago. Is there any way I can unlock the critical at this moment?
Does your computer recognize your device in 9008 mode?
dongvatm said:
Does your computer recognize your device in 9008 mode?
Click to expand...
Click to collapse
How do I enter 9008 mode?
dongvatm said:
Does your computer recognize your device in 9008 mode?
Click to expand...
Click to collapse
UPDATE: It's recognized as HS-USB Diagnostics 9008
You must use OST LA 6.2.8 and firmware NB1-488 android 8.1. then update via emegency download. It works on EDL mode.
dongvatm said:
You must use OST LA 6.2.8 and firmware NB1-488 android 8.1. then update via emegency download. It works on EDL mode.
Click to expand...
Click to collapse
Do you have a link for OST LA 6.2.8 and its patch?
Link: https://fih-firmware.hikaricalyx.com/hmd_en.html
You can download ost LA and firmware at this link.
dongvatm said:
Link: https://fih-firmware.hikaricalyx.com/hmd_en.html
You can download ost LA and firmware at this link.
Click to expand...
Click to collapse
I get another error message that image upload with Sahara protocol failed - even though I have Qualcomm drivers
RaleBurazer said:
I get another error message that image upload with Sahara protocol failed - even though I have Qualcomm drivers
Click to expand...
Click to collapse
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
dongvatm said:
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
Click to expand...
Click to collapse
Yes, I do have that driver, and my phone is shown as 9008 device in device manager while I’m in EDL, however I get an error which said that image upload using Sahara protocol failed. Is there any fix for that?
QDloader 9008 not HS USB diagnostic 9008
dongvatm said:
QDloader 9008 not HS USB diagnostic 9008
Click to expand...
Click to collapse
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
RaleBurazer said:
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
Click to expand...
Click to collapse
You must download Qualcomm Usb driver. Use google to find it. Good luck
RaleBurazer said:
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
Click to expand...
Click to collapse
Does it work?
dongvatm said:
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
Click to expand...
Click to collapse
dongvatm said:
Does it work?
Click to expand...
Click to collapse
I managed to get Qualcomm QDLoader 9008, but I still get the “Image upload with Sahara protocol failed” error
RaleBurazer said:
I managed to get Qualcomm QDLoader 9008, but I still get the “Image upload with Sahara protocol failed” error
Click to expand...
Click to collapse
It's a good new if your computer recognize 9008 mode. Your phone's main is alive. Sahara failed because your phone is in EDL mode too long time. I don't know exactly how to fix it. The last hint: let take out your battery and insert again. Or Press and hold vol - + power 15-20s. Good luck
dongvatm said:
It's a good new if your computer recognize 9008 mode. Your phone's main is alive. Sahara failed because your phone is in EDL mode too long time. I don't know exactly how to fix it. The last hint: let take out your battery and insert again. Or Press and hold vol - + power 15-20s. Good luck
Click to expand...
Click to collapse
Now I managed to get rid of Sahara upload error, but I again got 0xc6DA error
Have you tried the instructions here: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Optimus_Toaster said:
Have you tried the instructions here: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Click to expand...
Click to collapse
Update on the whole situation:
I managed to get to the download mode, and flash OREO NOVEMBER boot image on it. It successfully booted into Pie that I previously had installed. When I tried to follow the instructions given in the quoted post, I install November OTA successfully, but when I try to install December update, it says that I should use the 488K package. After I do that, it aborts the installation because there is no driver directory found. I think “Okay, November is fine” but when I try to reboot it goes into EDL. I again managed to flash the OREO boot image, and boot again into PIE (how is this possible?)
Also sidenote: WiFi doesn’t work. It didn’t work even after the first time I flashed Oreo boot. Can anyone perhaps provide me with a stock Pie boot image? Or does anyone know any other solution?
Back to stock - the aftermath
Hi all,
https://forum.xda-developers.com/showthread.php?t=4081895
(please read first and last post)
In short: I found some sketchy Android 10 update for Nokia 8, tried it out, did not work. Tried to restore my TWRP backup, did not work. Tried to bring back stock firmware via OST LA, did not work. I then flashed stock Oreo November 2018 boot image, and got into my Pie, but WiFi wasn't working. I then flashed pre-Magisk-rooted pre-TWRP-installed boot image, and WiFi works. However...
When my phone boots, it boots with Android logo instead of Nokia's
My phone is detected as Dual SIM, even tho it is not.
When I try to flash OTAs via TWRP, it doesn't work
I am looking for a solution on how to remove the Dual SIM problem and how to make my phone again boot with a classic Nokia logo. Any help? Thanks in advance!
Hi everyone,
I was wondering does anyone know the Nokia TA-1004 JTAG points by any chance?
I tried looking around and I can't seem to find anything.
Because of my bricked device, I am thinking of going down the JTAG route to extract my data.
This is the absolute last resort as I REALLY don't want to loose any of my data, primarily Contacts and Messages
Hope to hear back from you wonderful lot ?
Nokia_8_fan said:
Hi everyone,
I was wondering does anyone know the Nokia TA-1004 JTAG points by any chance?
I tried looking around and I can't seem to find anything.
Because of my bricked device, I am thinking of going down the JTAG route to extract my data.
This is the absolute last resort as I REALLY don't want to loose any of my data, primarily Contacts and Messages
Hope to hear back from you wonderful lot
Click to expand...
Click to collapse
I don't know what JTAG is. Please give some more info about your bricked device, how you bricked it etc. It might be possible to recover it without hardware intervention. Looking at your current post I am guessing you have a hard brick. In that case you have 2 options:
1.) Press and hold power button for about 2-4 minutes and wait for the device to shut down. When the device shuts down, boot to fastboot mode and fix any broken partitions.
2.) If that doesn't work you need hardware based methods. You need to open your device and short some pins to enter Qualcomm EDL (Emergency Download) mode. From there you can recover your device.
emufan4568 said:
I don't know what JTAG is. Please give some more info about your bricked device, how you bricked it etc. It might be possible to recover it without hardware intervention. Looking at your current post I am guessing you have a hard brick. In that case you have 2 options:
1.) Press and hold power button for about 2-4 minutes and wait for the device to shut down. When the device shuts down, boot to fastboot mode and fix any broken partitions.
2.) If that doesn't work you need hardware based methods. You need to open your device and short some pins to enter Qualcomm EDL (Emergency Download) mode. From there you can recover your device.
Click to expand...
Click to collapse
Thanks for getting back to me.
I have done both suggestions and they don't work.
It is probably a hard bricked device, the only thing I can get is a 9008 recognition in Device Manager.
QFIL, OST and NOST doesn't seem or want to communicate with the device either
Did you open your device and short the pins required? EDL mode is different than Download mode. OST and NOST work in Download Mode not EDL. QFIL does support EDL mode. If you look at this article (https://xiaomitools.com/how-to-use-qualcomm-flash-image-loader-tool-qfil/) at Step 5 it mentions that the device should be recognised as 9008 which you mention it does. Have you installed the Qualcomm drivers? Please provide some screenshots too, it is difficult to help you without specific info about your problem
emufan4568 said:
Did you open your device and short the pins required? EDL mode is different than Download mode. OST and NOST work in Download Mode not EDL. QFIL does support EDL mode. If you look at this article (https://xiaomitools.com/how-to-use-qualcomm-flash-image-loader-tool-qfil/) at Step 5 it mentions that the device should be recognised as 9008 which you mention it does. Have you installed the Qualcomm drivers? Please provide some screenshots too, it is difficult to help you without specific info about your problem
Click to expand...
Click to collapse
@emufan4568
Sorry for my late reply, but I thought Download Mode is the same as EDL mode???
And yes, I have the Qualcomm drivers installed.
I have also shorted the EDL pins on the board, this did not do anything at all.
I have tried QFIL many times and it keeps giving me error messages.
I have done so many things and posted screenshots across the forums that I am at a complete lost!
Nokia_8_fan said:
@emufan4568
Sorry for my late reply, but I thought Download Mode is the same as EDL mode???
And yes, I have the Qualcomm drivers installed.
I have also shorted the EDL pins on the board, this did not do anything at all.
I have tried QFIL many times and it keeps giving me error messages.
I have done so many things and posted screenshots across the forums that I am at a complete lost!
Click to expand...
Click to collapse
EDL mode is Emergency Download Mode in Qualcomm devices for recovering the device at a low level. QFIL calls it download mode but it really is not. Download mode in Nokia phones is really fastboot mode or bootloader mode where you basically communicate with the bootloader and flash/erase images from the device. From what I have seen though NOST supports EDL mode too (with the Emergency Download option) but it does not really work well.
Hey everyone,
yesterday my zenfone 8 just shutdown without any sign of a problem before . i thought its nothing but since then it dosnt turn on !!!
my only hope is when i connected it to my pc i got qualcomm 900e , i managed to change it to Qualcomm HS-USB QDLoader 9008 with driver update.
but still no fastboot no nothing.
i understand there is a way with qfil tool but i dont know how to get the files for it. any help please???
i see that qfil can fix it with rawdata and patch0 but i dont have this files. can some one please help???
You can get it on ROMdevelopers
QFIL / UnBrick - QMSCT_ForCSC_DefaultFuseLock_Sake_30.02.46.108_repkg.zip
AzimBahar said:
You can get it on ROMdevelopers
QFIL / UnBrick - QMSCT_ForCSC_DefaultFuseLock_Sake_30.02.46.108_repkg.zip
Click to expand...
Click to collapse
Hey azim , i downloaded the files but it seems it knows that i am on 900e even when i tries to use other drivers to be 9008. can you please assits how to get out of 900e?? btw i managed to get the files out of my device but sahara server failed because of 900e :/
Connect phone to pC using test point and follow guides
Trigger device to 9008 mode-
1. Remove USB cable and battery (Change a new chipset, UFS
should be empty)
2. Connect the battery
3. Device will boot into the emergency download mode
4. Confirm that the device manager has detected “Qualcomm HS-
USB QDLoader 9008 (COM x)”.
& Its may help too
ZS590KS_Keybox_Keymaster_HDCP_Online_Tool_M1220.zip
AzimBahar said:
Trigger device to 9008 mode-
1. Remove USB cable and battery (Change a new chipset, UFS
should be empty)
2. Connect the battery
3. Device will boot into the emergency download mode
4. Confirm that the device manager has detected “Qualcomm HS-
USB QDLoader 9008 (COM x)”.
& Its may help too
ZS590KS_Keybox_Keymaster_HDCP_Online_Tool_M1220.zip
Click to expand...
Click to collapse
I dont understand what i need to do . I even tried with edl cable but still stuck on 900e
Once try to uninstall USB Driver & install ASUS QCOM Driver.
As you said , i managed to change it to Qualcomm HS-USB QDLoader 9008 with driver update
Click to expand...
Click to collapse
After try again !
Note - You May use EDL Cable for EDL mode !
AzimBahar said:
Once try to uninstall USB Driver & install ASUS QCOM Driver.
After try again !
Note - You May use EDL Cable for EDL mode !
Click to expand...
Click to collapse
I tried with edl cable... Only test point left to find
duduhayo said:
I tried with edl cable... Only test point left to find
Click to expand...
Click to collapse
sir i have the same issues, are you know the test point right now?
Kiyori said:
sir i have the same issues, are you know the test point right now?
Click to expand...
Click to collapse
Hey, i wish. No one found it, I am still waiting for the one