Hi! i was changing os to oxygen 13 smt went wrong on phone and it was left in safe mode after everything was finished i pressed reboot and since then my phone has no reaction to anything literally anything! now currently trying Edl mode however so far not successful. screen is completely dark no action power keys probably dont work, even when conected to charger nothing happens is there solutions for it anyone ?
@hackslash Has been looking for someone to get their phone into EDL mode in this exact situation to try and help everyone get MSM tool access to save the phone. Your options are pretty much three.
1) Contact the community here and try to solve the issue "ourselves."
2) Pay some """contractor""" to remotrly flash your phome for a fee. (Links to this can not be posted on XDA.)
or 3) Send it back to OnePlus via RMA process. Should still be under the first year manufacturer warranty.
Related
Hi everyone,
This is my first post so I hope you are kind enough to help me with this issue.
I have an HTC 8X Blue (bought it factory unlocked) and recently I have updated it to GDR2. It happened what many other HTC 8X's user had. It bricked when I was playing some music.
I found an article that has a solution allegedly (I cannot post the link but it is the most popular solution aparently). But my problem is that I cannot enter Bootloader Mode as one of the first steps requires. My phone is simply dead, I tried every combination of buttons (hard reset and soft reset), but non is responsive. Of course, my PC does not recognize it and when I plug it in to the wall the red light does not turn on!
I do not have experience in modding or flashing or what-ever process needed (for Windows Phone), but I do know pretty much for iOS so I can learn quickly.
Any help would be greatly appreciated!
Your best option would be to get it repaired/replaced by a service center. If you're near a Microsoft store, they can take care of that for you. If not, it'll be trickier.
Otherwise, the only advice I can offer is to leave it for a while, let the battery drain entirely if you can, plug it in again, and try to start it... even if it won't boot normally, you may be able to access the bootloader mode now.
Thanks for the quick reply! I actually do not have a Microsoft Store as I live in Argentina...
I think i will try to drain the battery and restart it. Should I restart it the normal way? I mean by holding power button?
Yep, basically that.
You could also try calling HTC support and seeing if they have any other recommendations. The battery drain thing is basically just in case the phone got stuck in a weird state; resetting it that way may help.
is your phone stuck in QHSUSB_DLMODE i got my stuck there the other day. what i did was hold VOL UP, WOL DOWN and POWER all at the same time until the phone vibrated. wouldnt you know i unbricked my device.
Ok guys,
as the title says Lumia 710 is bricked.
It had last factory update and everything was working fine. Then i had to mess with it and to try to install Rataplan V9.1.
The process was working ok. By default, bootloader was in DLOAD mode, so in order to install custom ROM i needed to upgrade to Qualcomm. I have upgraded it and installed Rataplan .nb rom to the phone with NSSPro V0.54.
This is when my problems start.
The phone starts with one long vibration followed after few seconds with one short virbtation and thats it. No screen, no system, zip!
When i try to connect it again by usb to check it with NSSPro, it always starts in NAND disk mode. It does not matter do i start it normally on power button or with volume up. Its always in NAND. And it is always stuck. While the phone is connected to USB i can see Qualcomm CDMA Technologies MSM device in device manager but it has yellow mark like the driver is not installed.
I have tried several other roms, and NSS always shows that the rom is successfully installed, but the phone (other than vibration and NAND mode) is dead.
I have also tried all the solutions i could find on the net but no help. Tried, nokia recovery tool, WP recovery tool, Chimera e.t.c. Nothing works. Now i have a problem with NSS. It keeps stucking and beeing unresponsive for every option except Custom OS flash. Whatever else i click it either says tha phone is not detected or the app stucks and shuts itself down.
Is there other tool i can try?
Can i do anything to recover this phone or did i kill it?
PLEASE HELP!!!
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
droidzer1 said:
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
Click to expand...
Click to collapse
Tried allready every solution that i could find or think of, including things You described. Nothing. I was left with no other option but to send phone to service. They have a box unit with which they should be able to recover phone.
That was 2 days ago. today is third day so i am thinking that my phone has gone beyond repair. Only thing i can do is to wait and see...
Why not...?
Why not send it in real life to a windows phone expert. There should be a place to get phones repaired But, if they say that it isn't possible for them you may have rendered your phone useless. Google should be your mighty friend in this case :crying: I wish you very good luck.
Bricked Pixel 5a/QUSB code of death
Has anyone found a solution to the QUSB code of death? I entered the club last week. I was using my Pixel 5a as usual, scrolling through social media. Then suddenly, the screen freezes, the phone shuts off, reboots, freezes on the Google logo, then shuts off. Has not turned on since.
I have done all of the rudimentary “diagnostic solutions” but to no avail. When I plug the phone into my computer, the QUSB device code shows up in device manager.
I filed a request to obtain a replacement/repair with Google last week. They gave me the option to replace the device after determining it was bricked. However, Google seems to think it’s liquid damaged and ineligible for repair/replacement under the warranty. The phone has never had any sort of extensive liquid contact.
I am currently waiting to receive the same exact phone back. So far, I have not been able to find a legitimate solution other than sketchy “freezer” fixes and uncontrolled banging around the device with the hopes of it turning on again.
Has anyone figured out a legitimate solution to the same problem among multiple generations of Pixel devices?
can you get into bootloader? power on + vol down.
or a response when you have it plugged in with adb devices or fastboot devices?
or try a force off? power + vol down + vol up for about 30 seconds then try to power on again?
I have already tried those solutions. So far, nothing has worked.
wow. i don't know what's going on. mine did the same thing on sunday. got it to clean flash the official 13 with the chrome flash tool. was getting set back up and it happened again. and i just replied to another thread on here about someone it happened to. they better not tell me mine is suspected to be liquid damaged. but if they're not gonna replace it, i suppose you could try the freezer trick. and the best thing to do would probably buy a cheap 3a and trade it in for a 6a. maybe i shouldn't go with pixels anymore though. only had the 3a and now this one. they should get back to me tomorrow. i gave up trying to fix it the 2nd time it happened. wouldn't boot into userspace fastboot. never saw the qusb issue
Same thing just happened to my wife's 5a while she was browsing Facebook. There is no user accessible fix for this; while the QPST/QFIL programs may be found online, the MBN files necessary to reimage the device are not.
If you bought your device within the last 12 months, you should be able to get it repaired under warranty.
Here is the link for warranty repair.
V0latyle said:
Same thing just happened to my wife's 5a while she was browsing Facebook. There is no user accessible fix for this; while the QPST/QFIL programs may be found online, the MBN files necessary to reimage the device are not.
If you bought your device within the last 12 months, you should be able to get it repaired under warranty.
Here is the link for warranty repair.
Click to expand...
Click to collapse
My wife's phone now has this issue and we have important pictures on there we don't want lost. Is there a way to use the QPST program to get files off of the phone? Is there another way to get the files off of the phone when we cant get the device to even power on? When I plug it into a computer, I do get the QUSB device to appear.
Tl;Dr - my pixel 5a5g got the black screen of death a few months ago. Last night, I tried using the flash tool to try to flash it back to Android from GrapheneOS - so that Google would be willing to fix it maybe. Flashing seemed to fail. Unsure what to try or do next.
---------------
My Pixel has had the black screen of death for a few months now. I'm assuming it is from falling a few feet to the ground. It had a custom ROM - GrapheneOS - on it. Unless I can reflash to stock Android, it sounds like Google/ubreakifix won't look at it, and thus - no chance of repairing it for free or a smaller charge.
The other night, I tried attaching an OTG keyboard to the phone to log in to it. Since the display is black, I'm not sure it worked. I also tried several times to press where I thought the numbers for logging in would be - on my completely black screen. Somehow, I was eventually able to get my PC and Google's flash tool to recognize the phone. However, I might have messed up on some steps - because I think it might be bricked now.
I think I forgot to remove the grapheneOS key via their Web installer before trying to flash android. I used minimal abd tools to unlock the bootloader (and it still says it is unlocked)... When I tried flashing back to stock android using the android web tool, it went through the motions, but then said something like it needs to detect the phone again after flashing. And it wouldn't detect the phone again. Even if I unplugged then replugged the phone. The directions said I shouldn't/wouldn't need to press any keys on the phone for this step, but it just wasn't progressing further... So, I ended up holding the power button and volume down button - and it went into fastboot(?) again - or whatever that does.
I can repeat the steps of going thru the motions of flashing the device now, but now it gives an error saying something like it can't lock the device.
Being that the 5a screen is completely black, I have no idea what is going on - or what to do from here. I've reached out to some local repair places, but honestly, if I can't flash it myself to stock so that Google/ubreakifix would look at it, then it probably isn't worth sinking money into.... There's decent condition used ones around $120 or something out there... And ubreakifix would probably charge between $160 and $200 for screen replacement + labor - and I'm assuming that's not including a motherboard replacement - if necessary.
Ubreakifix said that they would be willing to look at it, but they can't actually do any repairs to it if it isn't running stock Android. They'd charge for the labor, and they'd temporarily use a screen to look at what it is doing/not doing... But wouldn't actually do the screen repair. I'm assuming the phone never flashed completely, but I'm hoping they can tell me if their diagnostic tools work on it - since I imagine it should work -- IF stock Android is actually installed again on it.
I've also looked into doing something like getting a displaylink adapter + display link app so that I can see the screen on the computer... But even after my multiple attempts of logging in to the phone, I can't send app downloads to the phone. Google Play store shows that the phone was "last seen" months ago... And even if I could push the app download, GrapheneOS still requires manual approval from the user to accept/finalize install of the app... Which would be pretty hard to do without seeing the screen. And obviously since I've tried flashing the phone several times last night, i have no idea what the phone is looking like. Probably app downloads are out of the question now.
Apparently you can't normally do display out of any sort with Pixel phones. The rumor I've seen on here and/or reddit is that Google got rid of it years ago, maybe so that they can sell more Chromecasts...
Does anyone have any further suggestions? I could try using scrcpy or whatever it's called, but I probably should have tried to use that before attempting to flash the phone... It's sure hard to give up on something that I spent good money on. I'd like to think there's something I haven't tried yet that I can do to save it...
You could probably try these steps:
1. Open up Device Manager on PC
2. Connect your phone
3. Hold Power + Volume Down
If you have new device in Device Manager, you can do everything with your device like flashing or try "to remove the grapheneOS key".
Edit: I'm dumb and didn't notice that part where you tried this. You should just boot into fastboot and remove that custom AVB key with fastboot erase avb_custom_key, and then reflash the phone on flash.android.com. Hope that helps!
Hey there, Hope everyone is fine. I have a pixel 4 XL 6/64 that was a running a version of android 12.xxxx something don't entirely remember that went completely unresponsive out of the blue. Doesn't turn on when holding the power button nor does holding power + volume up do anything. It was perfectly healthy with 70 percent battery when I last used it and set it down to come back in 5 minutes and see this happen. my device was oem unlocked with the bootloader unlocked and was also rooted. I was still receiving updates for android 13 which I was ignoring intentionally. Now when I connect my phone to my pc via usb it shows up as QUSB_BULK_CID:0404_SN:xxxxxxxx in device manager. From what I've read this indicates that it is in edl mode and I need a firehose to flash another rom image to the nand flash. I also see that older pixels come up with this QUSBxxxxx name in device manager and the 4 XL shows up with a different name, anyways this seems like a recurring issue with other people and since I live in Pakistan I can't get it repaired officially from google. I've got very less hope and I feel robbed. I wanted to know whether I can try anything to revive this phone as it had important data. I can see the firehose files on this forum but has it worked out for anyone else ?
I would really appreciate an experts response as I lack the required knowledge regarding this problem.
Thanks for taking out time to read this.
I also encountered the same problem, QUSB_BULK_CID: 0404_SN: xxxxxxxx, which is actually Qualcomm's 9008 mode. It's unfortunate that we have to meet in this way. I also sought help on XDA and couldn't find anything on Google.