Related
I accidentally deleted my phone OS using TWRP.
So, I fixed this and installed stock android firmware for my device and locked the bootloader.
It was all set up nicely. Then, I decided to update to the latest android version and now it showed the updating logo and everything and the screen suddenly went black and it won't show anything.
I have tried holding power and volume down for 2 minutes but have had no luck.
I have tried charging with many USB cables.
When I plug a USB cable into my phone and computer, I get the error message "USB Device Not Recognized".
Please help me fix this error and help me to get my phone working again, thank you in advance.
You broke the bootloader, this can be solved if Moto releases the blankflash files, however motorola has no idea in releasing those files. get some other mobile, no other alternatives as of now.
Jon_6 said:
I accidentally deleted my phone OS using TWRP.
So, I fixed this and installed stock android firmware for my device and locked the bootloader.
It was all set up nicely. Then, I decided to update to the latest android version and now it showed the updating logo and everything and the screen suddenly went black and it won't show anything.
I have tried holding power and volume down for 2 minutes but have had no luck.
I have tried charging with many USB cables.
When I plug a USB cable into my phone and computer, I get the error message "USB Device Not Recognized".
Please help me fix this error and help me to get my phone working again, thank you in advance.
Click to expand...
Click to collapse
Sorry Bro, you've completely bricked your phone. Even if Motorola releases blank flash files for Moto G 2 Titan, your mobile should be detected as "Qualcomm HS-USB Qdloader 9008". But as you mentioned that when you connect your phone with PC, it shows USB DEVICE NOT RECOGNISED, so there is nothing you can do now. Try giving it to service centre see if they can help
pkdon123 said:
Sorry Bro, you've completely bricked your phone. Even if Motorola releases blank flash files for Moto G 2 Titan, your mobile should be detected as "Qualcomm HS-USB Qdloader 9008". But as you mentioned that when you connect your phone with PC, it shows USB DEVICE NOT RECOGNISED, so there is nothing you can do now. Try giving it to service centre see if they can help
Click to expand...
Click to collapse
Thank you for your reply. I tried plugging my phone into my PC again after leaving it for a while and charging it for a few hours. Now, it shows as Qualcomm HS-USB Qdloader 9008 as you said. For some reason, it wasn't recognised last time I connected my phone to my computer.
Karthik_pm said:
You broke the bootloader, this can be solved if Moto releases the blankflash files, however motorola has no idea in releasing those files. get some other mobile, no other alternatives as of now.
Click to expand...
Click to collapse
Thank you for your answer, in the meantime, I'll just buy a cheap SIM-free phone that is in my Moto G.
I may as well use that and when my contract is finished, buy a new phone.
Jon_6 said:
Thank you for your reply. I tried plugging my phone into my PC again after leaving it for a while and charging it for a few hours. Now, it shows as Qualcomm HS-USB Qdloader 9008 as you said. For some reason, it wasn't recognised last time I connected my phone to my computer.
Click to expand...
Click to collapse
Well That's A Good News But I've Tried Searching Blank Flash Files on Google, Unfortunately I'm Unable To Find The Files For TITAN, The Files Available Online Are for Moto G FALCON, Which Wont Work Here..
My device is H811 running 10N version (rooted), but I'm unable to update it using because it won't be detected once it goes into fastboot or download mode. I have tried many drivers, and different PCs (running different OS, Windows 10, 8.1, 7) but still can't get it to works. Is there something I'm missing?
zenkhas said:
My device is H811 running 10N version (rooted), but I'm unable to update it using because it won't be detected once it goes into fastboot or download mode. I have tried many drivers, and different PCs (running different OS, Windows 10, 8.1, 7) but still can't get it to works. Is there something I'm missing?
Click to expand...
Click to collapse
first of all. update what.??
raptorddd said:
first of all. update what.??
Click to expand...
Click to collapse
I want to update it to Marshmalllow 20i or later.
zenkhas said:
I want to update it to Marshmalllow 20i or later.
Click to expand...
Click to collapse
have you tried lgbridge..
i doesnt detect phone at all.?
you have both of this drivers http://www.mediafire.com/file/k6ozyesitcqbkdr/driverslg.zip
usb 2.0 ? if nothing else works .. i can only think of format pc.. install drivers.. have windows update on in case it doesnt find drivers.. wait for it to install all drivers first time you connect phone.. or maybe bad usb port in phone .??
raptorddd said:
have you tried lgbridge..
i doesnt detect phone at all.?
you have both of this drivers http://www.mediafire.com/file/k6ozyesitcqbkdr/driverslg.zip
usb 2.0 ? if nothing else works .. i can only think of format pc.. install drivers.. have windows update on in case it doesnt find drivers.. wait for it to install all drivers first time you connect phone.. or maybe bad usb port in phone .??
Click to expand...
Click to collapse
No it doesn't. LG Up detects it when phone is On, but when LG Up restarts the device in fastboot, it says no devices connected, even when drivers are installed. Yes, the USB port is 2.0, and it can't be problem with port of phone since it is detected in normal mode. I will try these drivers and let you know if it works. Thank you
zenkhas said:
No it doesn't. LG Up detects it when phone is On, but when LG Up restarts the device in fastboot, it says no devices connected, even when drivers are installed. Yes, the USB port is 2.0, and it can't be problem with port of phone since it is detected in normal mode. I will try these drivers and let you know if it works. Thank you
Click to expand...
Click to collapse
LGUP and fastboot.??? what you talking about.?
turn off phone. then press vol up and plug you usb cable. it should take you to download mode and open LGUP it takes a while for connection sbut less then a minute..
raptorddd said:
LGUP and fastboot.??? what you talking about.?
turn off phone. then press vol up and plug you usb cable. it should take you to download mode and open LGUP it takes a while for connection sbut less then a minute..
Click to expand...
Click to collapse
Okay, that's the problem actually. I was confused between fastboot and download mode. When I press volume up and connect the cable it boots into fastboot mode instead of download mode. What could be the problem?
BTW here is the log from fastboot mode:
usb_error();transaction failed.txn_status = -1
usb_read(); DONE. ERROR. len 64
SECURE BOOT: DISABLED
LOCK STATE: LOCKED
zenkhas said:
Okay, that's the problem actually. I was confused between fastboot and download mode. When I press volume up and connect the cable it boots into fastboot mode instead of download mode. What could be the problem?
BTW here is the log from fastboot mode:
usb_error();transaction failed.txn_status = -1
usb_read(); DONE. ERROR. len 64
SECURE BOOT: DISABLED
LOCK STATE: LOCKED
Click to expand...
Click to collapse
am not good at readings of finding error i just suggestion why i think it might be..
can you do a factory reset.? can you try again to go into download mode.. maybe use an app that has download mode recovery mode one click on phone to take you there.?
its weird .. something not right when vol up and connect usb.. doenload mode should pop up. with screen showing usb icon.
I had the same exact problem for 6 hrs yesterday and i came across your thread and the problem is when you do adb reboot bootloader, and your phone doesn't show up on your pc under 'Computer management > devices', the driver says unsupported, follow this video starting around 4:50, you'll find all the drivers that way and it'll work right away
nkia2sg said:
I had the same exact problem for 6 hrs yesterday and i came across your thread and the problem is when you do adb reboot bootloader, and your phone doesn't show up on your pc under 'Computer management > devices', the driver says unsupported, follow this video starting around 4:50, you'll find all the drivers that way and it'll work right away
Click to expand...
Click to collapse
What video?
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!
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