Nexus 6p Hard Brick - Nexus 6P Q&A, Help & Troubleshooting

Hello, as I've written my Nexus 6P is hard bricked. I've done a terrible mistake, flashing from TWRP recovery a pixel rom for the wrong telephone (I didn't notice there was written bullhead instead of angler). After rebooting, the telephone is dead, the display doesn't go. When I connect to my PC, it says there's something wrong with the device connected. I know I did something very stupid, but if there's a chance to get back my phone restored I will strongly thank you...

Is the phone able to cold boot into recovery or the bootloader?

redduc900 said:
Is the phone able to cold boot into recovery or the bootloader?
Click to expand...
Click to collapse
Well, actually I don't know, as the display is off... I only know that when connected to PC, keeping pushed the power off button I hear the sound of a new USB device.

So when you press the power+volume down buttons to boot into the bootloader, you don't see anything on the screen?

redduc900 said:
So when you press the power+volume down buttons to boot into the bootloader, you don't see anything on the screen?
Click to expand...
Click to collapse
No, nothing at all

Does the phone show up under Ports in Device Manager?

redduc900 said:
Does the phone show up under Ports in Device Manager?
Click to expand...
Click to collapse
This is what I get-->Dispositivo USB sconosciuto
(in English is "unknown USB device)

Did you try holding the power and volume down for at least 10 seconds? Or did you just press it?
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
Did you try this? Or qsil/qfil?

emtkr said:
This is what I get-->Dispositivo USB sconosciuto
(in English is "unknown USB device)
Click to expand...
Click to collapse
Hello..
Head over this thread:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Install Qualcomm drivers. I guess your phone will likely show up as:
Qualcomm HS-USB QDLoader 9008 in device manager
If it's the case, try following the guide in the thread you found Qualcomm drivers...
Good luck...

I tried also this last method, but it didn't work. . So unfortunately I had To bring It to assistance this morning...

emtkr said:
I tried also this last method, but it didn't work. . So unfortunately I had To bring It to assistance this morning...
Click to expand...
Click to collapse
Sorry...
Hopefully you'll get it back, up and running!
I'm sure you'll be more careful flashing firmware in the future. :good:
Cheers...

DEVILOPS 007 said:
Did you try holding the power and volume down for at least 10 seconds? Or did you just press it?
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
Did you try this? Or qsil/qfil?
Click to expand...
Click to collapse
5.1 said:
Hello..
Head over this thread:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Install Qualcomm drivers. I guess your phone will likely show up as:
Qualcomm HS-USB QDLoader 9008 in device manager
If it's the case, try following the guide in the thread you found Qualcomm drivers...
Good luck...
Click to expand...
Click to collapse
Surely.. I pay my big fault.. thank you very much

Related

Help i totally bricked my lg g2 :(

Phone fixed, please delete the thread.
3S0PHAGOOS said:
I changed my ROM from stock to 4.4.2 ROM but I got so many issues so changed back to stock ROM, but my LG G2 only has now only 10gb of internal memory.. [I got 32gb lg g2] Now, i tried the instruction from the guy here
http://forum.xda-developers.com/showthread.php?t=2470207&page=3
and also this
http://forum.cyanogenmod.com/topic/...s-on-internal-storage/page__st__20#entry67870
I tried to do the steps as instructed but the result is not the same as mine and then i just exit ADB... then i restart my phone and booomm...
my phone died can't on at all even on download mode... when i try download mode it's just USB Not recognize... please help me ((((
Click to expand...
Click to collapse
Try connecting the phone to a wall charger for 15 mins,and then power up the phone.
nimrodsv said:
Try connecting the phone to a wall charger for 15 mins,and then power up the phone.
Click to expand...
Click to collapse
didn't work, as expected
3S0PHAGOOS said:
didn't work, as expected
Click to expand...
Click to collapse
At the second thread its for HTC incredible, i hope you didnt flashed anything from there right?
Honestly i have no idea what you can do, but trying to eliminate some of the cases..
EDIT: you should try the first method ( http://forum.xda-developers.com/showthread.php?t=2470207&page=3 ) when using this files: https://www.dropbox.com/sh/3pqceuaqsji0dqn/nvR20mLqMF
if that what you did and it didn't worked im guessing that flashing the firmware wont help, but there are wiser people than me to help you, just wait for their input
nimrodsv said:
At the second thread its for HTC incredible, i hope you didnt flashed anything from there right?
Honestly i have no idea what you can do, but trying to eliminate some of the cases..
EDIT: you should try the first method ( http://forum.xda-developers.com/showthread.php?t=2470207&page=3 ) when using this files: https://www.dropbox.com/sh/3pqceuaqsji0dqn/nvR20mLqMF
if that what you did and it didn't worked im guessing that flashing the firmware wont help, but there are wiser people than me to help you, just wait for their input
Click to expand...
Click to collapse
I can't flash anymore, My LG G2 is completely dead, can't get into recovery and download mode, if I tried going to download my pc just say "USB NOT RECOGNIZED"
I've used the following to completely restore my phone and untrip the root checker...
Verizon: http://forum.xda-developers.com/showthread.php?t=2448960
Others: http://forum.xda-developers.com/showthread.php?t=2432476
Xyriin said:
I've used the following to completely restore my phone and untrip the root checker...
Verizon: http://forum.xda-developers.com/showthread.php?t=2448960
Others: http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
did your phone totally bricked when you did it? or you can still go to the download mode?
cause mine is totally can't on.
Do you have the LG bootlogo coming up, if so try this:
(Something similar happened to mine, and I hope this will help.)\
Turn off phone, then when off, hold down power and volume down button until it reaches the LG logo and then release and hold it down again, if that doesn't work, when just hold it down until you see a screen that says something like: Hard reset/ factory reset. For me it took me to my recovery screen, where I just flashed a older ROM onto it, and you should be fine. I then later flashed a recovery file. I hope this helps, and if you need it any clearer, just reply :fingers-crossed:
If it's saying usb not recongized I'd recommend installing the proper drivers for your specific model. Which model do you have since you didn't specifying? Also, dead or charged your phone should boot download mode with volume up being held and plugging the phone in via usb to your computer.
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
If it's Verizon, follow that posted method above correctly. Check for correct com port numbers and make sure replacing the dll file your in the c: drive and not just in your download folder.
hiddenfive said:
Do you have the LG bootlogo coming up, if so try this:
(Something similar happened to mine, and I hope this will help.)\
Turn off phone, then when off, hold down power and volume down button until it reaches the LG logo and then release and hold it down again, if that doesn't work, when just hold it down until you see a screen that says something like: Hard reset/ factory reset. For me it took me to my recovery screen, where I just flashed a older ROM onto it, and you should be fine. I then later flashed a recovery file. I hope this helps, and if you need it any clearer, just reply :fingers-crossed:
Click to expand...
Click to collapse
My phone is completely off
ceredics said:
If it's saying usb not recongized I'd recommend installing the proper drivers for your specific model. Which model do you have since you didn't specifying? Also, dead or charged your phone should boot download mode with volume up being held and plugging the phone in via usb to your computer.
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
If it's Verizon, follow that posted method above correctly. Check for correct com port numbers and make sure replacing the dll file your in the c: drive and not just in your download folder.
Click to expand...
Click to collapse
I have the D802, I already installed the drivers.
If I'm going to go to download mode, It says USB not Recognized and my phone is completely off.
I don't have too much experience with that model so hopefully someone else spying has more information. Sorry buddy.
There is no bootlogo at all? Not even when you turn it on? Try plugging it into a wall charger and if anything happens, also try changing your COM # to 41, if it isn't its Device Manager<Ports (COM & LPT), right click< properties< port settings< advanced..< COM 41, this was from this article I will link right here: http://forum.xda-developers.com/showthread.php?t=2582142
Hope this helps :good:
@3S0PHAGOOS how you did the fix?
cpaixao said:
@3S0PHAGOOS how you did the fix?
Click to expand...
Click to collapse
yes please enlighten us....I am going through the same process and I can not turn it on at all. NOthing comes on...
Send it to me, but if I fix it I get to keep the phone. Right?
Sent from my SM-T210R using XDA Premium 4 mobile app
3S0PHAGOOS said:
Phone fixed, please delete the thread.
Click to expand...
Click to collapse
How did you fix it?
Those experiencing this problem could try this
https://www.youtube.com/watch?v=E7zbs6of_4I
Btw, you should share the solution for those who are in the same situation.

Bricked NEED HELP! xt905

After unsuccessful flashing phone (from 4.4.2 to 4.1.2) are not included in the boot is not included with the connection to the computer, the green LEDs and goes out, a visitor's computer does not see it.bootloader is unlocked
Can you access fastboot or recovery? If not, there's most probably no way to get it working.
Klen2 said:
Can you access fastboot or recovery? If not, there's most probably no way to get it working.
Click to expand...
Click to collapse
I can not get to the boot prompt. Through the factory cable, the phone tries to join, Windows making a sound device is connected and tighter turns off. And so it is constant. Help what to do?
If you can't access fastboot, there is currently no help
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
Why was the flashing unsuccessful?
Are you able to press down while powering up, to get to fastboot?
victimssun said:
Are you able to press down while powering up, to get to fastboot?
Click to expand...
Click to collapse
Most likely I boot it killed not that he does not react. And there are topics on how to restore the boot?
VladimirP200KM said:
Most likely I boot it killed not that he does not react. And there are topics on how to restore the boot?
Click to expand...
Click to collapse
I'm not following, but I think what Klen2 was trying to say is that, just get it into fastboot and reflash. Did you try this, http://forum.xda-developers.com/showthread.php?t=2786016 ?
Without the battery the phone is defined as a HID device. What could be more?
VladimirP200KM said:
Without the battery the phone is defined as a HID device. What could be more?
Click to expand...
Click to collapse
my question is, new ideas?
As I said, no help. You can look here: http://forum.xda-developers.com/showthread.php?t=2533049
[Q] Hard bricked my XT907, any way to JTAG?

Nexus 6P hardbricked, black screen

Hi, i dont know what happened before this state but now it is not booting and anything show on the screen. Device Manager shows Qualcomm HS-USB QDLoader 9008. Can this phone work normally or it is fully dead? Thanks in any case.
Optimusik said:
Hi, i dont know what happened before this state but now it is not booting and anything show on the screen. Device Manager shows Qualcomm HS-USB QDLoader 9008. Can this phone work normally or it is fully dead? Thanks in any case.
Click to expand...
Click to collapse
You can always get it up and running as long as it's only the software issue. Have you tried using the Wugfresh Toolkit/ any other toolkit and connecting your phone? Have you tried to reboot to bootloader or recovery?
If you haven't already, press and hold volume up + power button until you see the bootloader then connect your phone to your PC and install the toolkit of your preference and install the stock Rom, follow onscreen instructions on your PC. Hope this helps.
superviked said:
You can always get it up and running as long as it's only the software issue. Have you tried using the Wugfresh Toolkit/ any other toolkit and connecting your phone? Have you tried to reboot to bootloader or recovery?
If you haven't already, press and hold volume up + power button until you see the bootloader then connect your phone to your PC and install the toolkit of your preference and install the stock Rom, follow onscreen instructions on your PC. Hope this helps.
Click to expand...
Click to collapse
I would try this with pleasure but its always black screen anytime. And phone recognized by computer only in that mode that i described
It is definitely hard bricked. QDloader mode = Hard Brick. But if Google has released the blankflash files for the N6P (Idk if they have or not), then you can recover.
Optimusik said:
I would try this with pleasure but its always black screen anytime. And phone recognized by computer only in that mode that i described
Click to expand...
Click to collapse
This is the closest I found related to your issue, however this is the guide to resolve the same issue but for the Nexus 5 Hammerhead. Someone needs to confirm if the N6P images can be flashed with the same method.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
superviked said:
You can always get it up and running as long as it's only the software issue.
Click to expand...
Click to collapse
Not true.
superviked said:
This is the closest I found related to your issue, however this is the guide to resolve the same issue but for the Nexus 5 Hammerhead. Someone needs to confirm if the N6P images can be flashed with the same method.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
Click to expand...
Click to collapse
The boarddiag tool is specific to LG devices. It will be of no use here.
This is the first post I've seen for Angler that has a Qualcomm HS-USB QDLoader 9008. If it starts to happen more people will start to look into a fix. Until then I'm afraid the OP is bricked.
I'm having similar issues. For some reason I can't get passed the white Google screen. I can see the phone when I plug it in, wugfresh toolkit can even flash it back to stock. Yet, it won't go past the Google,in white, loading screen.
Sent from my SM-T800 using XDA-Developers mobile app
Have you installed TWRP, have you been able to boot into recovery/bootloader via ADB?
---------- Post added at 12:02 PM ---------- Previous post was at 11:40 AM ----------
theesotericone said:
Not true.
The boarddiag tool is specific to LG devices. It will be of no use here.
This is the first post I've seen for Angler that has a Qualcomm HS-USB QDLoader 9008. If it starts to happen more people will start to look into a fix. Until then I'm afraid the OP is bricked.
Click to expand...
Click to collapse
What I meant was the phone is not completely dead. It's in a state of coma but not dead. There's a way, it could take time but this can always come back to life, but the OP will have to wait for device and storage specific files and the boarddiag/ tool to reflash image files manually.
superviked said:
Have you installed TWRP, have you been able to boot into recovery/bootloader via ADB?
---------- Post added at 12:02 PM ---------- Previous post was at 11:40 AM ----------
What I meant was the phone is not completely dead. It's in a state of coma but not dead. There's a way, it could take time but this can always come back to life, but the OP will have to wait for device and storage specific files and the boarddiag/ tool to reflash image files manually.
Click to expand...
Click to collapse
I dont know the history of this phone. It came to me in this state. Now i know that i have to wait blankflash from Google. Thanks everybody for the answers.
Qualcomm HS-USB QDLoader 9008. Having the same issue. Hope there's a fix soon. Heart broken.
robertputt said:
Qualcomm HS-USB QDLoader 9008. Having the same issue. Hope there's a fix soon. Heart broken.
Click to expand...
Click to collapse
I would like to know what did you do to cause the phone to brick? I got the phone a week ago and I'm thinking if I should root or not. I became scared after I bricked my Moto X 2014 and there's still no blankflash files for it :crying:
seco2004 said:
I would like to know what did you do to cause the phone to brick? I got the phone a week ago and I'm thinking if I should root or not. I became scared after I bricked my Moto X 2014 and there's still no blankflash files for it :crying:
Click to expand...
Click to collapse
I did it myself, was trying to patchrom miui for the phone and must have used a wrong boot file or bootloader file, corrupted emmc.
first time i've ever hard bricked a phone and been flashing stuff for years, once you follow guides and use tested files you should be fine. found someone here in ireland to repair it for me. Only one huawei repair centre here
Recently found myself in the same predicament.
mzahiri said:
I'm having similar issues. For some reason I can't get passed the white Google screen. I can see the phone when I plug it in, wugfresh toolkit can even flash it back to stock. Yet, it won't go past the Google,in white, loading screen.
Sent from my SM-T800 using XDA-Developers mobile app
Click to expand...
Click to collapse
Same thing with my girlfriends phone, have u manage to fix it ? Thanx
letmarebrmbarove said:
Same thing with my girlfriend phone, have manage to fix it ? Thanx
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Check in here. No solution (yet, hopefully), but you're not alone with this issue.
count me in!

Z00TD ZE551KL Zenfone 2 Laser *hard bricked*

I somehow managed to lock myself out of the phone, no boot, no fastboot recovery mode, no access through adb (device not recognized), no nothing. Anyways just looking for assistance in this. I know there must be a way, but I haven't seen anything clear enough to precisely *unbrick* my beloved ASUS Zenfone 2 Laser ZE551KL Z00TD. I've resorted to a Samsung Galaxy S5 that I rebuilt from an old broken ones spare parts. I'm more of a hardware repairer so flashing ROMS and all that is rather new to me. But I was having some success early on when trying to flash CM.13 onto it using ADB and TWRP, which is when the trouble started. I flashed the wrong recovery.img I think and somehow locked myself out completely. I'm not sure exactly what I did wrong, but after many failed attempts to flash CM.13 Marshmallow, I tried to revert back to the stock ROM and then realized that I didn't make a backup recovery.img. Doh! So now I'm completely stuck with a really nice looking paper weight. Please help! :angel:
okay man, if you connect your phone without battery using usb cable to your pc? and device manager shows any newly detected device for a few seconds? try this and reply me...
crossmanx said:
okay man, if you connect your phone without battery using usb cable to your pc? and device manager shows any newly detected device for a few seconds? try this and reply me...
Click to expand...
Click to collapse
I did plug in the device, while the battery was still in it, and it came up as an unrecognized device when the balloon popped up at the bottom right of the PC screen. I unplugged it, took out the battery, and plugged back in, but nothing showed up this time. Although I didn't look in device manager though. But I will try that next. What's your thoughts on helping me solve this issue? I'd really like to learn how the actual company first loads their firmware onto the devices. Like what kinds of software and equipment they use. I'm sure it's on a major scale though and probably have machines doing most of the work, just like an automobile assembly line. LOL. But I really want to get this ASUS Zenphone unbricked. So any help would be awesome. Thanks very much!
thanks man! I think you have to download QUALCOMM drivers! from internet. and install it into your pc. after installing drivers there will be a connection into your device manager when you connect your phone with pc. it maybe QUALCOMM 9006/9008, or QDLOADER or Qualcomm mmc storage. is this shows up into your pc, you are done,, you can push firmware parts into your device using qpst or qfil softwares. I will send you the link for guide.
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
---------- Post added at 10:54 AM ---------- Previous post was at 10:49 AM ----------
try to search"unbrick all qualcomm snapdragon devices" into google and you will find out how to unbrick using qfil/qpst. you have to download stock firmware for your phone.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
give results.
Thanks Man!!! I really appreciate the help. I'll try all this and report back. Thanks Again!
Well I realize it's been awhile, got pretty busy at work, I run a computer and smartphone repair shop.
But I've managed to get as far as getting the right drivers installed under COM PORTS, because it was showing up as RELINK HS-USB QDLoader 9008.
So after uninstalling those com ports drivers by uninstalling the device (you need to click the check box to uninstall drivers).
Then by holding down simultaneously the power + volume up + volume down buttons, while then connecting the usb cable back to the computer.
The device now showed up under other devices in device manager as QHSUSB_BULK. I searched and downloaded the Qualcomm HS-USB QDLoader 9008 drivers and installed them (The download was simply named Qualcomm_USB_Drivers.)
I installed the drivers to the QHSUSB_BULK device by clicking update driver software and then selecting them by browsing to where I saved them, in this case to my desktop. Note: I first had to download the .zip file, then extract that into my desktop folder I just called Firmware and Drivers. The name of the Driver pack I downloaded was called "Qualcomm_Drivers_QDLoader"
Now the device shows up as Qualcomm HS-USB QDLoader 9008 (COM10). I reconnected the device using the same method of holding down the volume up+volume down+power all at the same time with one hand and the other to plug in the micro USB cable that was linked to the PC. But I did this after which I took out the battery for about 20 seconds and placed it back in. This way I could check to see if the device was truly connected at that com port.
I have a plethora of software installed already to include, android debugging tools aka ADB+Fastboot+Tools unzipped using WINRAR to the desktop folder "adb", I also for some reason have AndroidSDKSlim.zip extracted to the desktop which just has the adb and fastboot tools in them. I also have QPST which has QFIL and a lot of other developer tools, and eMMC_DL_Tool_for_customer_ENG_V5.2.0R. I'm thinking I'll be needing these soon, so that's why when searching I just downloaded and installed all of these programs.
I'm at the point now where the phone is plugged in and the COM PORT appears to be open as far as I can tell.
Now I just have to figure out how to get the partitions, stock firmware, and all that back onto the phone so that I can unlock it, root it, load TWRP recovery, and then get it all back to life.
Any suggestions? Anyone? @crossmanx thanks for helping to get me started. Do you know where to go from here? I'm not even sure I have the right ASUS drivers installed, but I think that I do. This should be all I need correct?
Thank you. I'll continue to be as detailed as possible in my steps to recover my *hard bricked "ZE551KL Z00TD". Oh but on another note, I have heard that the stock rom or image recovery for the Asus Zenphone Selfie Z00T may work as well, but I'm afraid to try that. I just want to get this device back up and running with either the stock rom or and update MM rom like CM.13. Cheers!
WormholeMatt said:
Well I realize it's been awhile, got pretty busy at work, I run a computer and smartphone repair shop.
But I've managed to get as far as getting the right drivers installed under COM PORTS, because it was showing up as RELINK HS-USB QDLoader 9008.
So after uninstalling those com ports drivers by uninstalling the device (you need to click the check box to uninstall drivers).
Then by holding down simultaneously the power + volume up + volume down buttons, while then connecting the usb cable back to the computer.
The device now showed up under other devices in device manager as QHSUSB_BULK. I searched and downloaded the Qualcomm HS-USB QDLoader 9008 drivers and installed them (The download was simply named Qualcomm_USB_Drivers.)
I installed the drivers to the QHSUSB_BULK device by clicking update driver software and then selecting them by browsing to where I saved them, in this case to my desktop. Note: I first had to download the .zip file, then extract that into my desktop folder I just called Firmware and Drivers. The name of the Driver pack I downloaded was called "Qualcomm_Drivers_QDLoader"
Now the device shows up as Qualcomm HS-USB QDLoader 9008 (COM10). I reconnected the device using the same method of holding down the volume up+volume down+power all at the same time with one hand and the other to plug in the micro USB cable that was linked to the PC. But I did this after which I took out the battery for about 20 seconds and placed it back in. This way I could check to see if the device was truly connected at that com port.
I have a plethora of software installed already to include, android debugging tools aka ADB+Fastboot+Tools unzipped using WINRAR to the desktop folder "adb", I also for some reason have AndroidSDKSlim.zip extracted to the desktop which just has the adb and fastboot tools in them. I also have QPST which has QFIL and a lot of other developer tools, and eMMC_DL_Tool_for_customer_ENG_V5.2.0R. I'm thinking I'll be needing these soon, so that's why when searching I just downloaded and installed all of these programs.
I'm at the point now where the phone is plugged in and the COM PORT appears to be open as far as I can tell.
Now I just have to figure out how to get the partitions, stock firmware, and all that back onto the phone so that I can unlock it, root it, load TWRP recovery, and then get it all back to life.
Any suggestions? Anyone? @crossmanx thanks for helping to get me started. Do you know where to go from here? I'm not even sure I have the right ASUS drivers installed, but I think that I do. This should be all I need correct?
Thank you. I'll continue to be as detailed as possible in my steps to recover my *hard bricked "ZE551KL Z00TD". Oh but on another note, I have heard that the stock rom or image recovery for the Asus Zenphone Selfie Z00T may work as well, but I'm afraid to try that. I just want to get this device back up and running with either the stock rom or and update MM rom like CM.13. Cheers!
Click to expand...
Click to collapse
asus firmware for your device model is available on asus web site, download that and open that zip file, in that you will find boot.img, aboot or amass or droidboot.img, and also system.img files, and you have to push that into your device using qfil/qpst. i thibk you can do it also by emmc_dl is qualcomm drivers are installed properly and shows up as com_port, u just have to enter comport number and it wish push your files into device..
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
if you only push droidboot img then you will be able to get into the volume+ + power combo mode, so you can get access to fastboot, and after that you know all the procedures....
---------- Post added at 06:14 PM ---------- Previous post was at 06:04 PM ----------
well actually all the qualcomm based devices are unbrickable so sont worry your phone will be live again... you have to just experimenting it on...
well actually i dont have this phone...i am thinking about buying asus ze601kl? is this a good phone? how'z the performance and stability of cm13 snapshot version on your device? is dual sim and all the other things works without any bug? or it has any bug?
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
asus has such funky things in stock boot image as it verifies everytime on boot for valid image, if you have unlocked its bootloader before and try to update its firmware or install stock rom it creates problem. so cm13 is better choice.
crossmanx said:
asus firmware for your device model is available on asus web site, download that and open that zip file, in that you will find boot.img, aboot or amass or droidboot.img, and also system.img files, and you have to push that into your device using qfil/qpst. i thibk you can do it also by emmc_dl is qualcomm drivers are installed properly and shows up as com_port, u just have to enter comport number and it wish push your files into device..
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
if you only push droidboot img then you will be able to get into the volume+ + power combo mode, so you can get access to fastboot, and after that you know all the procedures....
---------- Post added at 06:14 PM ---------- Previous post was at 06:04 PM ----------
well actually all the qualcomm based devices are unbrickable so sont worry your phone will be live again... you have to just experimenting it on...
well actually i dont have this phone...i am thinking about buying asus ze601kl? is this a good phone? how'z the performance and stability of cm13 snapshot version on your device? is dual sim and all the other things works without any bug? or it has any bug?
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
asus has such funky things in stock boot image as it verifies everytime on boot for valid image, if you have unlocked its bootloader before and try to update its firmware or install stock rom it creates problem. so cm13 is better choice.
Click to expand...
Click to collapse
Well, here I am ready to upload the ROM to the phone using QFIL. The phone is identified by the port. The only thing I'm having trouble with now is finding the "RAWPROGRAMMER" file to load from the firmware.
I'm not sure what else to do, I can't find the file anywhere.
Maybe this is when they say I need to get ahold of someone else exact same phone, root it, load twrp, and backup their original stock rom? I'm not sure. I just feel soo close to getting this done, but I keep missing files. I'm trying to load CM.13 but inside the folders for the firmware, there isn't any file in there. I've already found the patch file and the .mbn file that I need. Just missing the rawprogrammer file.
This is giving me a headache. LOL
Actually the only file I need is the .xml file that it asks for in QFIL. Which I guess is supposed to be in the stock rom somewhere. But in order to get that, I'm guessing I'll have to use my wifes phone (she has the exact same model as I do). I'll just have to make sure to not delete anything or mess up her phone. lol
And I'm also thinking that I will have to install stock ROM first before flashing the CM.13. So I'll have to get that stock ROM from her phone, since I deleted mine on accident.
that xml file is basically a partition structure file for your phone emmc. i think it might be there in your firmware.zip
you just have to find rawprogrammer file, i think it is there where you find unbrick guide for all qualcomm devices.....you just try that file it might work for your phone too..and after adding rawprogrammer you can add firmware parts from firmware.zip file or you also can clone your wife's phone emmc, using emmc dump to raw extension.
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
you dont need to install stock rom first, only you need to send droidboot,recovery or maybe boot partitions, if you have deleted modem and other partitions, then those will also. if you get fastboot then you can flash twrp and can flash cm13.
---------- Post added at 03:09 PM ---------- Previous post was at 03:00 PM ----------
there will be different named xml file in firmware.zip for you phone's firmware you just try try yourself available xml files in firmware. if it will be wrong xml then it will auto terminate no need to worry.
What happened man! there is no response from you, since very long time!! I think you have solved the problem and been very happy with the phone live again.
flash stock firmware using this tool: maybe it works
https://androiddatahost.com/326a2
crossmanx said:
What happened man! there is no response from you, since very long time!! I think you have solved the problem and been very happy with the phone live again.
Click to expand...
Click to collapse
Nope, I still haven't unbricked it just yet. I had to put it on hold for a bit while I got much work done. But I will try again soon. I miss my phone. :'( lol
Same problem ZE601Kl
WormholeMatt said:
Nope, I still haven't unbricked it just yet. I had to put it on hold for a bit while I got much work done. But I will try again soon. I miss my phone. :'( lol
Click to expand...
Click to collapse
Hi Guys ,
Same problem happened for me with my Asus Zenfone 2 laser Ze601Kl.
I have tried QFIL , QPST all the qualcomm related softwares to make it work , but everytime i am getting same error " SAHARA FAIL "
I have tried with COLOR OS for One Plus One and which was having one chinese flasher and sadly that also showing the same error ,
AS far as i know i have installed the qualcomm drivers successfully and it is showing in device manager also . I have tried with Windows 7 X64 , Windows XP SP 2 . Still no luck
My phone has been dead since 1 month Somebody please help me
ZB500KL in Qualcomm HS-USB QDLoader 9008 no fastboot
Please help
I in Russia
Asus ZenFone Go ZB500KL in Qualcomm Snapdragon 410 MSM8916 detected pc only Qualcomm HS-USB QDLoader 9008. Please help
Try this https://forum.xda-developers.com/zenfone-3/help/hard-brick-asus-zenfone-3-ze520kl-t3483874/page3
Follow last post, technically you only need adb connectivity to flash all at once with one click. Hope this will help you.
Of course, now you need the rom for your device.
Sent from my ZenFone 3 using XDA Labs
crossmanx said:
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
Click to expand...
Click to collapse
Good to see anyone talking about LINUX here! I have my ZE550KL briked and the only thing I've been able to do till now are booting in fastboot and Android Recovery modes.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
Click to expand...
Click to collapse
Wow, this helped me a lot! My Linux system was not able to recognize the device but reinserting the battery and trying volumeUP+PowerButton did the trick! Now running 'fastbood devices' lists it and of course that made it visible through Virtualbox too [Windows 7 guest OS].
Now, considering that I would really like to resuscitate my phone by using LINUX, what else should I do in order to succeed?
Thanks a lot and best regards.
crossmanx said:
thanks man! I think you have to download QUALCOMM drivers! from internet. and install it into your pc. after installing drivers there will be a connection into your device manager when you connect your phone with pc. it maybe QUALCOMM 9006/9008, or QDLOADER or Qualcomm mmc storage. is this shows up into your pc, you are done,, you can push firmware parts into your device using qpst or qfil softwares. I will send you the link for guide.
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
---------- Post added at 10:54 AM ---------- Previous post was at 10:49 AM ----------
try to search"unbrick all qualcomm snapdragon devices" into google and you will find out how to unbrick using qfil/qpst. you have to download stock firmware for your phone.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
give results.
Click to expand...
Click to collapse
can you help me
same mode, manage to flash and download finish success.
Finish Download
Start Download
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
Finish Download
sorry dude, i have no more info about asus devices. so can't help. remember only buy phones which have flashtools available like lenovo, mi, oppo, zuk etc.

XZ Premium Dead

Hey guys,
My XZ Premium updated to 9.0. Since then I started to have many problems.
Yesterday a messagage appeared: Your phone is corrupt, it may not work properly. It can't be trusted.
Hours later it frozed and turned off. Now it's not responding to anything. The led isn't working and the device manager shows it as SOMC Flash Device.
The comands pressing volume buttons while I connect the USB cable are not working either.
Can I save it? I bought it three months ago :crying:
First, try to repair it with Sony Companion and Newflasher. if those not work return it to your dealer or ask for a repair under warranty.
Styler911 said:
First, try to repair it with Sony Companion and Newflasher. if those not work return it to your dealer or ask for a repair under warranty.
Click to expand...
Click to collapse
I alredy tried. It's not working. I bought in a different country that I live now. I can't use the local warranty.
first of all try a factory reset if the phone not modified.
If you have TWRP installed, wipe the phone out of TWRP.
Probably water in usb port then charging caused it
it cant hurt to try have you tried pressing volume up and power together until you get 3 vibrations?
mad0701 said:
first of all try a factory reset if the phone not modified.
If you have TWRP installed, wipe the phone out of TWRP.
Click to expand...
Click to collapse
I don't have the TWRP installed. The device is not responing via PC.:crying:
stipi69 said:
it cant hurt to try have you tried pressing volume up and power together until you get 3 vibrations?
Click to expand...
Click to collapse
The device is not responding to any command that I try...
amakuramio said:
Probably water in usb port then charging caused it
Click to expand...
Click to collapse
It never get wet, and when it does I make sure that no water remains....
Can you see your phone in the Systemcontrol? If yes: does the device is valid or does the device has an Akklamation Mark "!" beside? Maybe you must install the fastboot driver?
---------- Post added at 08:42 AM ---------- Previous post was at 08:37 AM ----------
on other hand:
try the Flash tool (Version 0.9.2.5.0) with a ftf file.
With this you can also change the version of country, remove a branding or viversa....
You will find links to the tool and ftf here in the forum
mad0701 said:
Can you see your phone in the Systemcontrol? If yes: does the device is valid or does the device has an Akklamation Mark "!" beside? Maybe you must install the fastboot driver?
---------- Post added at 08:42 AM ---------- Previous post was at 08:37 AM ----------
on other hand:
try the Flash tool (Version 0.9.2.5.0) with a ftf file.
With this you can also change the version of country, remove a branding or viversa....
You will find links to the tool and ftf here in the forum
Click to expand...
Click to collapse
It only appears as SOMC Flash Device. The ADB or Flash Tools can't get access to the internal memory. I know there's a way to access the internal memory. Just don't know which one yet.
It looks like a coincidence. Hardware not be working may be the real issue.
If you find a knowledgeable repair shop, they can clear your flash and install the original Sony shipped OS for a little money. Most of the time this is done from the USB after a factory reset explained by others here. However, if the USB port is not working then accessing the flash needs opening the unit which will cost you.
And then if the hardware has failed, none of this would help anyway.
What's happen, if you press for 6 Sec or longer Power and Volume up together?

Categories

Resources