Hey guys,
Not having much fun with the Axon 7's, got one a while ago and was running Linage OS and dropped it in water and it's fully dead.
Decided that I'd grab a deal on one, and got sick of the stock ROM real quick so went to Flash Linage OS 14.1 as before with the Axon 7 Toolkit.
However when flashing the bootloader, I accidentally left the Android version set to 7.0 instead of 6.0. Which appears to have bricked my Axon 7.. Not sure if this is what bricked it or something else, regardless that's the last thing I did.
I can see it in Windows appearing as "ZTE Handset Diagnostic Interface (DFU)" - With a COM port listed.
The Axon 7 Toolkit now does not detect the phone no matter what I do, nor does Xiaomi Miflash or whatever it's called.
The phone boots to a black screen, with a red LED notification icon that stays solid red. Force restarting it boots it back into the same state as it has no bootloader or is corrupt at a guess.
Starting to get desperate here..
Windows 10 x64 Based PC and the original USB cable.
Any help or assistance is greatly appreciated.
Mattie86 said:
Hey guys,
Not having much fun with the Axon 7's, got one a while ago and was running Linage OS and dropped it in water and it's fully dead.
Decided that I'd grab a deal on one, and got sick of the stock ROM real quick so went to Flash Linage OS 14.1 as before with the Axon 7 Toolkit.
However when flashing the bootloader, I accidentally left the Android version set to 7.0 instead of 6.0. Which appears to have bricked my Axon 7.. Not sure if this is what bricked it or something else, regardless that's the last thing I did.
I can see it in Windows appearing as "ZTE Handset Diagnostic Interface (DFU)" - With a COM port listed.
The Axon 7 Toolkit now does not detect the phone no matter what I do, nor does Xiaomi Miflash or whatever it's called.
The phone boots to a black screen, with a red LED notification icon that stays solid red. Force restarting it boots it back into the same state as it has no bootloader or is corrupt at a guess.
Starting to get desperate here..
Windows 10 x64 Based PC and the original USB cable.
Any help or assistance is greatly appreciated.
Click to expand...
Click to collapse
I'm not sure about this, but based on the description you gave, it looks like you have a 4th category DFU brick.
Try zadig, maybe you will be able to get the drivers to work and get recognized as QUSB BULK but if not, then 4th category brick guide will be the only way to fix it.
troy5890 said:
I'm not sure about this, but based on the description you gave, it looks like you have a 4th category DFU brick.
Click to expand...
Click to collapse
Kantastisch said:
Try zadig, maybe you will be able to get the drivers to work and get recognized as QUSB BULK but if not, then 4th category brick guide will be the only way to fix it.
Click to expand...
Click to collapse
Yep, did have a fiddle around more. Seems like it's a 4th category brick.
I'm waiting for it to go flat,as some people have suggested that might work. I have tried zadig and no luck thus far.
If that fails I'm going to contact ZTE and see what they can offer..
If that fails I'll open it up, and I have my water damaged phone for reference purposes.
Thanks for the heads up and advice guys.
Mattie86 said:
Yep, did have a fiddle around more. Seems like it's a 4th category brick.
I'm waiting for it to go flat,as some people have suggested that might work. I have tried zadig and no luck thus far.
If that fails I'm going to contact ZTE and see what they can offer..
If that fails I'll open it up, and I have my water damaged phone for reference purposes.
Thanks for the heads up and advice guys.
Click to expand...
Click to collapse
Yeah I'd contact ZTE if it doesn't work out. I'm glad I helped you out man
troy5890 said:
Yeah I'd contact ZTE if it doesn't work out. I'm glad I helped you out man
Click to expand...
Click to collapse
Couldn't get anywhere, contacted ZTE but the level 1 person got mad at me when I said it wasn't entering recovery and told me to call senior support..
I said that it froze during updating and so I had to turn it off as it was stuck there for an hour or more.. I mean I'm not lying just didn't specify what update I was doing.
Tried to call the senior advisor line? (It's really weird that they have a separate line?) I'm Senior support for another company and we just transfer calls directly.
Their hours suck, 10-4PM... Ergh, don't know how far I'll be getting. I could always take it back to where I got it, but that's an hour away and they won't have any stock (so it'd be a refund)
Mattie86 said:
Couldn't get anywhere, contacted ZTE but the level 1 person got mad at me when I said it wasn't entering recovery and told me to call senior support..
I said that it froze during updating and so I had to turn it off as it was stuck there for an hour or more.. I mean I'm not lying just didn't specify what update I was doing.
Tried to call the senior advisor line? (It's really weird that they have a separate line?) I'm Senior support for another company and we just transfer calls directly.
Their hours suck, 10-4PM... Ergh, don't know how far I'll be getting. I could always take it back to where I got it, but that's an hour away and they won't have any stock (so it'd be a refund)
Click to expand...
Click to collapse
So you break your phone and now expect someone else to take care of it for you? Just follow the guide and fix it yourself. Pretty sure using miflash is not covered under warranty.
lafester said:
So you break your phone and now expect someone else to take care of it for you? Just follow the guide and fix it yourself. Pretty sure using miflash is not covered under warranty.
Click to expand...
Click to collapse
I have heard and seen others do it however, which is why I'm trying. If it was a flat out "no" I'd be fine with it.
Mattie86 said:
I have heard and seen others do it however, which is why I'm trying. If it was a flat out "no" I'd be fine with it.
Click to expand...
Click to collapse
On windows 10 there could be some issues with drivers, I had huge problems installig the QUSB Bulk driver but I wasn't Zte H... Interface but Qdloader 9008 but maybe it'll still work for you. I disconnected my pc completwly from the internet (becauss windows updated my drivers automaticcly, no matter what I did) and uninstalled the QDloader driver and installed the zadig driver a few times, it was a really tricky process but eventually it worked out. But as stated I was recognized as QDLOADER and ZTE Handset user interface or whatever is way worse, so I think it won't work but you could give it a try.
Kantastisch said:
Try zadig, maybe you will be able to get the drivers to work and get recognized as QUSB BULK but if not, then 4th category brick guide will be the only way to fix it.
Click to expand...
Click to collapse
Never works...
---------- Post added at 05:19 PM ---------- Previous post was at 05:14 PM ----------
Mattie86 said:
I have heard and seen others do it however, which is why I'm trying. If it was a flat out "no" I'd be fine with it.
Click to expand...
Click to collapse
Look, the FTM method only works with much more mild bricks. You flashed the wrong bootstack there probably. It's fried.
Use my DFU unbrick guide, the 4th categ guide is less detailed.
If you don't wanna do it you can risk it and try the failed update thing again, some people here convinced them. But you might face the $80 fee if they find out
Choose an username... said:
Never works...
---------- Post added at 05:19 PM ---------- Previous post was at 05:14 PM ----------
Look, the FTM method only works with much more mild bricks. You flashed the wrong bootstack there probably. It's fried.
Use my DFU unbrick guide, the 4th categ guide is less detailed.
If you don't wanna do it you can risk it and try the failed update thing again, some people here convinced them. But you might face the $80 fee if they find out
Click to expand...
Click to collapse
It worked for me, but I wasn't ZTE Handset ... device though
Kantastisch said:
It worked for me, but I wasn't ZTE Handset ... device though
Click to expand...
Click to collapse
That's the point, you are ignoring the circumstances. He made a disaster with the software; maybe he flashed a Nougat bootstack on Marshmallow. Do you think that would have changed the driver, and that magically it would still be EDL in disguise?
It worked for you because it was Qualcomm HS-USB QDLoader 9008. Or QUSB_BULK but on the unknown devices list. That has nothing to do with a 4th category brick
troy5890 said:
Yeah I'd contact ZTE if it doesn't work out. I'm glad I helped you out man
Click to expand...
Click to collapse
lafester said:
So you break your phone and now expect someone else to take care of it for you? Just follow the guide and fix it yourself. Pretty sure using miflash is not covered under warranty.
Click to expand...
Click to collapse
Choose an username... said:
Never works...
---------- Post added at 05:19 PM ---------- Previous post was at 05:14 PM ----------
Look, the FTM method only works with much more mild bricks. You flashed the wrong bootstack there probably. It's fried.
Use my DFU unbrick guide, the 4th categ guide is less detailed.
If you don't wanna do it you can risk it and try the failed update thing again, some people here convinced them. But you might face the $80 fee if they find out
Click to expand...
Click to collapse
If it's $80 I'd be happy to pay it honestly. I will double check everything I do next time before doing it too..
Choose an username... said:
That's the point, you are ignoring the circumstances. He made a disaster with the software; maybe he flashed a Nougat bootstack on Marshmallow. Do you think that would have changed the driver, and that magically it would still be EDL in disguise?
It worked for you because it was Qualcomm HS-USB QDLoader 9008. Or QUSB_BULK but on the unknown devices list. That has nothing to do with a 4th category brick
Click to expand...
Click to collapse
I also installed a nougat bootstack on 6.0 and nothing happened.
Kantastisch said:
I also installed a nougat bootstack on 6.0 and nothing happened.
Click to expand...
Click to collapse
Well he clearly did something that provoked that brick, and it wasn't just forgetting to flash something, y'kno
Related
Bricked OP2 ...
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
If you flashed a ROM that's not for you're phone you're more than likely screwed
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Bhups said:
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Click to expand...
Click to collapse
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Heisenberg said:
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Click to expand...
Click to collapse
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
mG!X said:
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
Click to expand...
Click to collapse
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Heisenberg said:
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Click to expand...
Click to collapse
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
mG!X said:
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
Click to expand...
Click to collapse
I just can say, your device is not hard bricked and will be recoverable.
You just need to be a bit patient. For the OPO, there was the ColorOs emergency recovery available (which helped me already 2x unbricking my OPO after I compiled a faulty kernel).
I just have not yet seen something similar for the OP2. But as you get the bulk_device still recognized via USB, this means the Qualcomm emergency boot loader is still intact and once the recovery stuff leaks somewhere, you will be able to fully recover your OP2.
Don't ask me when this will be available, think it also took weeks for the OPO before it was posted somewhere.
All the best!
Andi
mG!X said:
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
Click to expand...
Click to collapse
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
yanick76 said:
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
Click to expand...
Click to collapse
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Heisenberg said:
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Click to expand...
Click to collapse
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
yanick76 said:
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
Click to expand...
Click to collapse
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Heisenberg said:
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Click to expand...
Click to collapse
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Just to assure you that the hard brick issue on OPT is completely curable since I've revived two OPTs. No panic needed. I will update the complete procedure as well as the necessary files later today.
yanick76 said:
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Click to expand...
Click to collapse
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Heisenberg said:
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Click to expand...
Click to collapse
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
yanick76 said:
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
Click to expand...
Click to collapse
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Tutorial posted here http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Heisenberg said:
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
Click to expand...
Click to collapse
From this point I agree it was wrong advice.
I hope I never will be in situation like this But if, I will try to fix it based on what I suggest him + hours of google for correct files, correct drivers and correct download tool. I think this "misunderstood" was based on my advice like "here is direction and google for more", this is forum if he can find answer himself (google) he need not to ask for help here
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Irwan Fauzi said:
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Click to expand...
Click to collapse
Plz any developers help him
Sent from my Lenovo A6000 using Tapatalk
Find how to flash device with qfil in google
Irwan Fauzi said:
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Click to expand...
Click to collapse
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
sasukay said:
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
Click to expand...
Click to collapse
Im on rr 5.7.3
- first i wipe data,dalvik,cache and system in twrp
- flash L2KK.zip
- reboot recovery and stuck at boot (lenovo powered by android)
i know i have to flash twrp for kitkat right? but i end up flashing something about partition because i wasnt giving attention. not my phone cannot go into recovery or fastboot. just a red notification light. i know this is my fault.
@Irwan Fauzi, You've told these steps earlier. I want to know if you can boot into recovery or fastboot.
sasukay said:
@Irwan Fauzi, You've told these steps earlier. I want to know if you can boot into recovery or fastboot.
Click to expand...
Click to collapse
nope
Irwan Fauzi said:
nope
Click to expand...
Click to collapse
Then the only method is qfil method
Btw, did you tried the methods i advised to boot into recovery and fadtboot. Because in 90% cases, people were not doing it the right way to boot into recovery, and were stating that it's a hard brick.
sasukay said:
Then the only method is qfil method
Btw, did you tried the methods i advised to boot into recovery and fadtboot. Because in 90% cases, people were not doing it the right way to boot into recovery, and were stating that it's a hard brick.
Click to expand...
Click to collapse
maybe i have to send my phone to service center because qualcomm doesnt detect my device.
sasukay said:
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
Click to expand...
Click to collapse
You are the best developer here I've ever seen helping other developers and thanks a lot really....while others don't even open their mouth except for saying don't post this here don't ask this question here......They think they are gods but I hope they realize soon that they are nothing to anyone of us here . Making some **** modifications to an existing software and creating WhatsApp grps and feeling as legends themselves.Everybody knows they don't even know how to make a small toast in any android app.......
Sloved
i have sent my device to service center.. thanks to everyone who trying to help me..
Irwan Fauzi said:
maybe i have to send my phone to service center because qualcomm doesnt detect my device.
Click to expand...
Click to collapse
For QFIL to work you have to use the diagnostic mode on your device. First DOWNLOAD THESE USB DIAGNOSTIC DRIVERS and install them. Then press VOL UP + POWER on the device. A menu will open where you have to choose "Download". Then the screen will turn black and then connect your phone to pc. The device manager should show USB diagnostic on 9008 on com5 or something in the PORTS. Update the driver, using the drivers I provided; if the drivers didn't get installed automatically for the phone. Then, if everything is fine, you should see your phone on QFIL. Then click on choose build and flash the row firmware for your phone, which you can DOWNLOAD FROM HERE.
bvsbrk said:
You are the best developer here I've ever seen helping other developers and thanks a lot really....while others don't even open their mouth except for saying don't post this here don't ask this question here......They think they are gods but I hope they realize soon that they are nothing to anyone of us here . Making some **** modifications to an existing software and creating WhatsApp grps and feeling as legends themselves.Everybody knows they don't even know how to make a small toast in any android app.......
Click to expand...
Click to collapse
Bro, its nothing like that. I'm just another guy, like you, who has done things and hence know how to do them. I'm not a dev. I have no idea how a ROM, or kernel, or for that matter how a bug is fixed or how a patch is made or even how to ise Git. So, basically I just test things, that's what I do. You can't even me with the repected devs.
And, you should not crirticise them, in any way. They cook up the roms and kernels for us for whatever time they could manage. And, note this, They do not do it for themselves. They are not making any money out of this. They are doing all this hardwork for us. So, the least you could do is to be respectful to them, for what they are doing.
And, moreover, they don't reply much at such threads because, firstly they don't have thay much time. All the spare time they have, they use it to bring something good for us. Guys like me, who have some time, are the ones who can (and should) reply and help others. Secondly, the bricking issue has been reported hundreds, or even thousands, of times now. So, instead of asking the same question again and again, which kind of is spamming the forums, one should first check google and xda if the same question has been answered earliet. I, myself, has answered the same things to folks hundreds of time now. That, even makes me angry sometimes. I'm like, Due Seriously. You could get the answer a few posts below. And even a blind person could see that. But, alas, it is what it is.
So, in all, Respect Devs, for what they are doing for us. They are not obliged to do it for us and are not even paid for it. They do it just so that guys like us, who otherwise would've stuck with stock KK or buggy stock LP can enjoy the goodness of Marshmallow and Nougat roms.
Sigh...I don't write this long usually. But you made me type all of this.
---------- Post added at 12:53 PM ---------- Previous post was at 12:50 PM ----------
@Irwan Fauzi, Ok I was a bit late. But, you were too fast at that. BTW, what fid they ask you. And did they just accepted to repair it, considering it was you fault.
sasukay said:
For QFIL to work you have to use the diagnostic mode on your device. First DOWNLOAD THESE USB DIAGNOSTIC DRIVERS and install them. Then press VOL UP + POWER on the device. A menu will open where you have to choose "Download". Then the screen will turn black and then connect your phone to pc. The device manager should show USB diagnostic on 9008 on com5 or something in the PORTS. Update the driver, using the drivers I provided; if the drivers didn't get installed automatically for the phone. Then, if everything is fine, you should see your phone on QFIL. Then click on choose build and flash the row firmware for your phone, which you can DOWNLOAD FROM HERE.
Bro, its nothing like that. I'm just another guy, like you, who has done things and hence know how to do them. I'm not a dev. I have no idea how a ROM, or kernel, or for that matter how a bug is fixed or how a patch is made or even how to ise Git. So, basically I just test things, that's what I do. You can't even me with the repected devs.
And, you should not crirticise them, in any way. They cook up the roms and kernels for us for whatever time they could manage. And, note this, They do not do it for themselves. They are not making any money out of this. They are doing all this hardwork for us. So, the least you could do is to be respectful to them, for what they are doing.
And, moreover, they don't reply much at such threads because, firstly they don't have thay much time. All the spare time they have, they use it to bring something good for us. Guys like me, who have some time, are the ones who can (and should) reply and help others. Secondly, the bricking issue has been reported hundreds, or even thousands, of times now. So, instead of asking the same question again and again, which kind of is spamming the forums, one should first check google and xda if the same question has been answered earliet. I, myself, has answered the same things to folks hundreds of time now. That, even makes me angry sometimes. I'm like, Due Seriously. You could get the answer a few posts below. And even a blind person could see that. But, alas, it is what it is.
So, in all, Respect Devs, for what they are doing for us. They are not obliged to do it for us and are not even paid for it. They do it just so that guys like us, who otherwise would've stuck with stock KK or buggy stock LP can enjoy the goodness of Marshmallow and Nougat roms.
Sigh...I don't write this long usually. But you made me type all of this.
---------- Post added at 12:53 PM ---------- Previous post was at 12:50 PM ----------
@Irwan Fauzi, Ok I was a bit late. But, you were too fast at that. BTW, what fid they ask you. And did they just accepted to repair it, considering it was you fault.
Click to expand...
Click to collapse
Bro don't misunderstand me. Whatever you said is totally correct. I'm not criticizing any developer and as you said without them we would have stuck in buggy lp kk roms. But every body has their own perspective .There is no offence in not answering any question but instead of that some people insult by saying you don't know anything(Though the question is not nerdy type) . You can see this happening in WhatsApp groups as I experienced this personally.
I meant that to those people. So no offence to any developer. You need not take it to that serious . It's just my opinion and I'm sure everybody has their own opinions.
bvsbrk said:
Bro don't misunderstand me. Whatever you said is totally correct. I'm not criticizing any developer and as you said without them we would have stuck in buggy lp kk roms. But every body has their own perspective .There is no offence in not answering any question but instead of that some people insult by saying you don't know anything(Though the question is not nerdy type) . You can see this happening in WhatsApp groups as I experienced this personally.
I meant that to those people. So no offence to any developer. You need not take it to that serious . It's just my opinion and I'm sure everybody has their own opinions.
Click to expand...
Click to collapse
I can understand who you are talking about
No problem
I never considered myself above anyone so something
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Irwan Fauzi said:
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Click to expand...
Click to collapse
I would not suggest flashing a6000 s ROM on your new phone or you may end up like your a6000
Irwan Fauzi said:
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Click to expand...
Click to collapse
Don't you ever try to flash custom ROM that not supported for your phone
Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.
bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.
I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro
Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff
Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )
Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out
Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!
Yes folks,
As I said, I discovered SUPER BRICK, TOTAL BRICK, COMPLETE FAILURE or whatever yoy want to name this new brick. It has been like this: I was following the instructions to update oreo in HONOR 8 LITE, at the end I had to write some codes in twrp (advance / terminal ...) so it was starting to do the last update (sd card update.zip) and by accident I touched the screen where it appears: REBOOT, so the phone restarted but the screen is not working when it tries to enter erecovery mode, so here is the list of my problems:
- it does not work: erecovery (so I can not recover the phone)
- fastboot works: when I install something (twrp or firmware, I have tried everyone of them) the phone does not start
- if I try to go to TWRP (after installing an oreo one): the screen seems to break and you can not see anything
Please, my phone is 2 months old, man I need to make it work again, I need it.
Help help help
You should post this in Honor 8 lite forum ...
But whatever, you said that fastboot works if so you can try to use huawei update extractor and flash system,boot,recovery,cust that *should* work
Nikola6511 said:
You should post this in Honor 8 lite forum ...
But whatever, you said that fastboot works if so you can try to use huawei update extractor and flash system,boot,recovery,cust that *should* work
Click to expand...
Click to collapse
I wrote it down here because it is fully compatible and there are more roms here than the honor 8 lite forum, that´s why, it was not a mistake it is because I am desperate.
I can not install BOOT, I have tried and it does not work, anyways I need help.
Thanks in advance
alopez_666 said:
I wrote it down here because it is fully compatible and there are more roms here than the honor 8 lite forum, that´s why, it was not a mistake it is because I am desperate.
I can not install BOOT, I have tried and it does not work, anyways I need help.
Thanks in advance
Click to expand...
Click to collapse
Sry i didnt know its the same.
What error do you get when you try to flash boot.img?
Nikola6511 said:
Sry i didnt know its the same.
What error do you get when you try to flash boot.img?
Click to expand...
Click to collapse
I finally installed BOOT properly, but the problem is that I have inside the phone OREO SYSTEM and I can not find BOOT in the updates I am downloading, as I said, once BOOT was installed, it did not work because it came form nougat.
Phone is very dead.
alopez_666 said:
I finally installed BOOT properly, but the problem is that I have inside the phone OREO SYSTEM and I can not find BOOT in the updates I am downloading, as I said, once BOOT was installed, it did not work because it came form nougat.
Phone is very dead.
Click to expand...
Click to collapse
This may be a stupid question..
If i understood correctly, you can install Boot from nougat, right?
If so why dont you flash nougat rom again?
Nikola6511 said:
This may be a stupid question..
If i understood correctly, you can install Boot from nougat, right?
If so why dont you flash nougat rom again?
Click to expand...
Click to collapse
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
Im really sorry i cant help
There is a way to fix that.. but... Its too complicated and hard to do..
Since your phone is new, you probably dont want to buy new.
This is going to cost you a bit.
First you will need to find honor 8 lite or p8 lite (if you say they are the same)
that is well.. dead, open it take out a memory chip on both phone and place chip from dead phone to yours. If you dont know how to do that take it to the repair shop and they should know how to do that.
As i sad its very hard and it costs, but it works if done properly.
I saved my friends phone like that, idk what he did but phone wasnt visible in adb, fastboot and recovery didnt work just blue screen.
Note:
This needs to be done very carefully or ypur phone will be 100% dead
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
I think your EMMC memory might be fried
Nikola6511 said:
Im really sorry i cant help
There is a way to fix that.. but... Its too complicated and hard to do..
Since your phone is new, you probably dont want to buy new.
This is going to cost you a bit.
First you will need to find honor 8 lite or p8 lite (if you say they are the same)
that is well.. dead, open it take out a memory chip on both phone and place chip from dead phone to yours. If you dont know how to do that take it to the repair shop and they should know how to do that.
As i sad its very hard and it costs, but it works if done properly.
I saved my friends phone like that, idk what he did but phone wasnt visible in adb, fastboot and recovery didnt work just blue screen.
Note:
This needs to be done very carefully or ypur phone will be 100% dead
Click to expand...
Click to collapse
What about using DC PHOENIX???? What do you think????
alopez_666 said:
What about using DC PHOENIX???? What do you think????
Click to expand...
Click to collapse
Idk I never tried it, but it costs and it's not guaranteed it will work but it's worth a try
---------- Post added at 09:55 PM ---------- Previous post was at 09:46 PM ----------
If I understood correctly it will flash any file no matter what so technically it should work
Nikola6511 said:
Idk I never tried it, but it costs and it's not guaranteed it will work but it's worth a try
---------- Post added at 09:55 PM ---------- Previous post was at 09:46 PM ----------
If I understood correctly it will flash any file no matter what so technically it should work
Click to expand...
Click to collapse
DC Phoenix worked fine, it's been awesome, I installed the rom and my phone is alive, I wonder: why I couldn't do it with ADB? Why this software is so powerful? And finally, why nobody is making kind of software like this for free? I mean, dc phoenix must be like the software that Huawei technicians use in their lab and samsung has ODIN that is so powerful as well and is free.
Anyway, if anybody has a problem as mine, you have to pay but it has solution. By the way, I went to tech service and they did not do anything because I bought my phone in China and they could not touch more than european phones, but they told me something that made me think that my trouble had a solution: rewrite the rom and that point convinced me that DC Phoenix would work, and so did it. Thank you all for the info.
Same for me, how to fix please. Bricked following this "guide"
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official Emui Nougat, wanted Oreo, forced update with nocheck, everything is broke except fastboot.
When I want to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk /path/to/img" it work but can't reboot to recovery.
I press Power + Vol+ but it reboot "phone untrusted" with Vol+ for going to eRecovery (usualy it's here you can shutdown the phone) but error mode.
Maybe the OreoTWRP work after my command but can't boot into it. Please help.
alopez_666 said:
DC Phoenix worked fine, it's been awesome, I installed the rom and my phone is alive, I wonder: why I couldn't do it with ADB? Why this software is so powerful? And finally, why nobody is making kind of software like this for free? I mean, dc phoenix must be like the software that Huawei technicians use in their lab and samsung has ODIN that is so powerful as well and is free.
Anyway, if anybody has a problem as mine, you have to pay but it has solution. By the way, I went to tech service and they did not do anything because I bought my phone in China and they could not touch more than european phones, but they told me something that made me think that my trouble had a solution: rewrite the rom and that point convinced me that DC Phoenix would work, and so did it. Thank you all for the info.
Click to expand...
Click to collapse
Bro my P8lite is also bricked, I accidentally wiped the EMMC then I showed it to a repairer and he somehow took me to fastboot mode, now I can't flash anything because that repairer has partitioned the EMMC and now it is showing 486mb total storage so no ROM is flashing because of size. Can you please give me your USERNAME and PASSWORD of DC Pheonix as you've already bought it. It will solve my issue and it will also save me some money.... I will be very thankful to you....
WAITING FOR A POSITIVE REPLY.
I bought it some time ago and it was a 72 hours license and it expired so I do not have anything from that situation. I will check my computer but I will not probably find anything.
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
Hello just looking at that pic is enough. That happens cause you installed the wrong firmware. Either get a proper nougat rom for your device and install boot, recovery and system images from fastboot or a oreo version. Either way that screen means its the wrong firmware version or wrong zone. for example you can be trying to install a europe rom in a asian device. hope this helps
legionfx said:
Hello just looking at that pic is enough. That happens cause you installed the wrong firmware. Either get a proper nougat rom for your device and install boot, recovery and system images from fastboot or a oreo version. Either way that screen means its the wrong firmware version or wrong zone. for example you can be trying to install a europe rom in a asian device. hope this helps
Click to expand...
Click to collapse
Problem was solved, I used DC Phoenix and installed a rom, but I did it some time ago. Thanks anyway
Hello everyone.
First of all i was on the beta program for android 10 until like Q4 but since i was't able to play DFFOO i decided to downgrade the OS back to the last official build, and that was the android 9 june/july build.
I followed everything on the essential website in order to downgrade and i got it right, sort of. Everything was working fine except for the fact that the phone just wouldn't update at all. it'd just throw me an error, not big deal i though, until android 10 came out and since i wasn't getting it on my phone on it's own i decided to sideload it and here we are
I also folllowed everyhting on the Essential's website except for the fact of using the last Pie build i thought it was not big deal (idk if that mattered) so everything went fine until the installation reached 94% and then it said: Installation complete (i thought it was weird but not much else) next thing i do is select reboot now and boom.
All i get now is the sound of windows if i connect it to my computer and the "Qualcomm HS-USB QDloader 9008" under the ports section in device manager, no ammount of holding and pressing buttons will make it come back to life, so i come here for help, worst case scenario i'll have to buy a new one (they're pretty cheap second hand)
I'm sorry to say this to you, but you are out of luck... The QDL mode is because of 2 reasons:
-Joined D- and GND on a stripped cable
-Bootloader corrupted.
The most common thing is the Bootloader was corrupted because of 2 files: hyp.mbn and rpm.mbn. Either was downloaded bad or was flashed but have issues on those 2...
Essential won't release the Firehose files to unbrick the device. My PH-1 was bricked by May OTA and they refuse to repair my device.
In a post I made on Reddit I explain something about this issue, and what causes it. But without the Programmer and the Firehose, you can't recover the device.
Why would Andy Rubin not put out the Firehose when Essential is supposed to be a developer friendly phone!?!? Makes no sense.
IngJulian_RVLX said:
Essential won't release the Firehose files to unbrick the device. My PH-1 was bricked by May OTA and they refuse to repair my device.
.
Click to expand...
Click to collapse
Do you think there is a possibility they will release them in the future eg when new model comes out or when support for PH-1 ends? Or are other manufacturers always leaked & not "official" leak? Suppose most leaks for other phones are from service centres, vice kinda answers my own question.
IngJulian_RVLX said:
I'm sorry to say this to you, but you are out of luck... The QDL mode is because of 2 reasons:
-Joined D- and GND on a stripped cable
-Bootloader corrupted.
The most common thing is the Bootloader was corrupted because of 2 files: hyp.mbn and rpm.mbn. Either was downloaded bad or was flashed but have issues on those 2...
Essential won't release the Firehose files to unbrick the device. My PH-1 was bricked by May OTA and they refuse to repair my device.
In a post I made on Reddit I explain something about this issue, and what causes it. But without the Programmer and the Firehose, you can't recover the device.
Click to expand...
Click to collapse
Thanks for the quick reply, oh well, at least i didn't buy it at its 700 dollars lauch price.
i'd like to read that post though, mind sharing the link?
Noct1070 said:
Thanks for the quick reply, oh well, at least i didn't buy it at its 700 dollars lauch price.
i'd like to read that post though, mind sharing the link?
Click to expand...
Click to collapse
https://www.reddit.com/r/essential/comments/cku745/my_ph1_bricked_by_may_ota_qdledl_9008_and_its/
I did the same thing, and ended up in the same situation, so this is definitely a reproducible problem. Contacting Essential support in hopes that they're willing to fix... but from what I'm reading around the web it's not likely. ?
Just adding my two cents. I had this exact same issue and Essential reached out to me. Told me I could ship my phone to them and they would fix it. Low and behold, they did. At the cost of only shipping, we'll worth the wait to get the phone back.
I guess depending on warranty age and registering, retail vs eBay used purchase, etc