Database Develop

[Q] Bell Vibrant, black screen, no recovery

I've read several topics but i couldn't find the right answer. I hope you can help me.
The problem i have happened without me doing anything recent. I have never flashed any rom, and i rooted my phone for titanium backup like 2 month ago and it worked fine.The last things i did was to install pocket legend, the new mmorpg like 3 days ago.I charge my phone during night, and take it for the day in the morning. Today, the screen stayed black when i picked it up. When i reboot, the screen goes black after the samsung logo.
The problem is that i have recovery mode (the 3 buttons) disabled and when i try to connect to kies it says i am not in samsungs kies mode.. Is there a way to force it to detect my phone so i can try update it?
According to the wiki, my phone doesnt seem to be bricked as i can still see the battery charging when i plug it. Is my phone bricked? Any hope?
I know the easiest way would be to return it to the store, but i dont want them to see my personal information/rooting as i cant even factory reset it.
There is also that topic on internal sd that has failed but i think this is not my case. You can still boot into android without the internal sd right?
I've seen a topic on soldering two mini usb cable to force the phone to go into recovery mode. I not familar enough to do it. If this method could solve my problem, could anyone sell me one?
Was there an over the air update today that could've done this to my phone?
I am lost, please help i am really clueless in what is happening to me.

are you able to go to download mode
flash your phone that way with odin i had the same problem as you

download mode as in using the 3 buttons? no i cant unless there is another way?

I can't get odin to recognize my phone.. I can't get into os so no usb debugging...

read this
http://forum.xda-developers.com/showthread.php?t=819551
then it'll help you flash back to whatever you want

Okay, I know the jig will DEFINITELY work in this case. Any phone state I've come across with that jig, I can throw the phone into downloading. However, it seems that there MAY be hope for you PRIOR to using the jig. Are you familiar with the ADB commands? If so, turn on the phone, connect via USB, run cmd as administrator, navigate to the proper adb folder and under the prompt type in adb devices. If it shows any device, type in adb reboot download and it'll throw it into download mode for you.

AllGamer said:
read this
http://forum.xda-developers.com/showthread.php?t=819551
then it'll help you flash back to whatever you want
Click to expand...
Click to collapse
I think the JIG is my last resort but i dont have any solder skill
If you know anyone that could sell me one i would be very happy!
krazykidd said:
Okay, I know the jig will DEFINITELY work in this case. Any phone state I've come across with that jig, I can throw the phone into downloading. However, it seems that there MAY be hope for you PRIOR to using the jig. Are you familiar with the ADB commands? If so, turn on the phone, connect via USB, run cmd as administrator, navigate to the proper adb folder and under the prompt type in adb devices. If it shows any device, type in adb reboot download and it'll throw it into download mode for you.
Click to expand...
Click to collapse
Good to hear that the JIG would work. As for ADB commands, doesn't it need the usb to be put in debugger mode? Is there any way to do it externally, without going in the setting menu? I am not very familiar with the adb commands but if its doable i will go read about it.
Thanks for suggestions!

slay3r85 said:
As for ADB commands, doesn't it need the usb to be put in debugger mode? Is there any way to do it externally, without going in the setting menu? I am not very familiar with the adb commands but if its doable i will go read about it.
Click to expand...
Click to collapse
exactly... it's not possible via ADB in your conditions

Thanks you for help!
I still tried but it said that it couldn't find my phone.
I leaning toward making a JIG. I just have to figures out how if no one sell them

Did you really tryed Download Mode?
"Vol Down" + "Home" + "Power" instead of "Vol Up" + "Home" + "Power"?

I tried several time different combo listed on wiki without any success. About 3h long!
I bought my phone the first day it came out so i guess the hardware method is locked.
As soon as i can get it back running i will apply that new fix for the combo.
I am a bit worried about the homemade JIG, will it still work without usb debugging?

Where in the world are you?
If you are in the GTA area, then you can invite me for a coffe

slay3r85 said:
I tried several time different combo listed on wiki without any success. About 3h long!
I bought my phone the first day it came out so i guess the hardware method is locked.
As soon as i can get it back running i will apply that new fix for the combo.
I am a bit worried about the homemade JIG, will it still work without usb debugging?
Click to expand...
Click to collapse
Yes. It will. As long as the phones off and the jig is in when you turn it on
Sent from my SGH-T959 using XDA

AllGamer said:
Where in the world are you?
If you are in the GTA area, then you can invite me for a coffe
Click to expand...
Click to collapse
I wish i could but i live too far Quebec / Laurentides. I think its about 8h driving!
krazykidd said:
Yes. It will. As long as the phones off and the jig is in when you turn it on
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
Thanks you for confirming this! I ordered the components and i will try to do it myself.
Some people have done it without any solder skill ! I hope it get here fast! I didn't know i would miss my phone so much!

Seriously! ??? I just soft bricked my phone I really don't know why these software and hardware companies can't get this right the first time. I was going to by an iphone until a sales rep showed me the galaxy s and I was impressed until I saw the black screen of death. A whole lot of B.S. to fix something that should work right in the first place. I'm getting tired of faulty equipment.
My Galaxy is still under warrenty I'll bring it back to store but I'm fed up with worthless technology.

black screen help plz
hey guys i have a galaxy s vibrant which will turn on nd the home nd back nd other buttes will turn on but my screen wont any idea what it might be ?

[Q] Sprint Hero boot problem

Does anyone have any idea why a Hero would for no apparent reason while sitting on a charger go into a reboot cycle only bringing up the htc sign and then the phone with triangle and exclamation point and do nothing else? the phone has never been rooted or anything just did that on its own.
Would running the Regawmod rooter exe possibly fix this?
Also i have another Hero i was given that i have tried to run the rooter on but everytime i do i get the error "Necessary HTC drivers are missing".
i have tried three different versions of HTC sync since i don't know where to get the drivers seperately. all with the same result. any help will be greatly appreciated.
Thanks in advance

Tap my avatar or search the hero dev section for my thread on how to install adb. Try those drivers and see if they work for you. If they do then try the hero rooter or run the ruu.
#Root/Hack-Mod_Always*

no luck. still have the orange triangle and exclamation point, tried the ADB thing and its not recognizing that the phone is there. but when i plug the phone into the computer it acts as though it is mounting as an external drive but when i click the drive letter it says to please insert a disk.
when i try holding the home and power button i get an error at the bottom of the screen that reads "E:Can't open /cache/recovery/command"

Tuvan03 said:
no luck. still have the orange triangle and exclamation point, tried the ADB thing and its not recognizing that the phone is there. but when i plug the phone into the computer it acts as though it is mounting as an external drive but when i click the drive letter it says to please insert a disk.
when i try holding the home and power button i get an error at the bottom of the screen that reads "E:Can't open /cache/recovery/command"
Click to expand...
Click to collapse
Ok what steps did you take?? Details please?? And when you setup adb did you type adb devices??? And how did you go about setting up adb???
#Root/Hack-Mod_Always*

i went through the steps in your post minus the mobile stream tether and i can't enable usb debugging because the phone will not boot up at all. it has been this way since last night. was just sitting charging and then went into a reboot cycle only bringing up the HTC logo then after awhile of that ended up at the screen its at now with the phone with the triangle and exclamation point.
i did type adb devices but it didn't come up with anything in the list of attached devices.
Edit: i did put the easy tether on the computer but since i can't access the usb options on the phone i can't set up the debugging. i don't know whats up with the phone

Tuvan03 said:
i went through the steps in your post minus the mobile stream tether and i can't enable usb debugging because the phone will not boot up at all. it has been this way since last night. was just sitting charging and then went into a reboot cycle only bringing up the HTC logo then after awhile of that ended up at the screen its at now with the phone with the triangle and exclamation point.
i did type adb devices but it didn't come up with anything in the list of attached devices.
Click to expand...
Click to collapse
The mobile stream steps were the android drivers I originally suggested you to try. So try those drivers and see if they work for you. I posted that thread for users who were having trouble with the htc drivers
#Root/Hack-Mod_Always*

ok well i hooked up the working hero so it would install the drivers, which it did, then i hooked up the hero that is stuck for no apparent reason on the error screen and i was finally able to run the regawMOD rooter but i guess because it doesn't have usb debugging enabled it won't allow anything to happen.
just trying to sort out what happened to this phone for it to be stuck at this error screen. nothing has ever been done to it just happened last night while it was charging

Tuvan03 said:
Does anyone have any idea why a Hero would for no apparent reason while sitting on a charger go into a reboot cycle only bringing up the htc sign and then the phone with triangle and exclamation point and do nothing else? the phone has never been rooted or anything just did that on its own.
Click to expand...
Click to collapse
What you're seeing is the stock bootable recovery image. Pulling the battery and powering it on again should make this go away. Have you already tried that?

jasonmaloney said:
What you're seeing is the stock bootable recovery image. Pulling the battery and powering it on again should make this go away. Have you already tried that?
Click to expand...
Click to collapse
yes have already tried this a couple times, now it just sits at the phone with triangle and exclamation point. won't do anything else

well took the phone to sprint and they deemed it unsalvageable so i guess this is moot. he tried all the standard resets etc. so thanks for all the help but guess the phone is a brick now. wouldn't replace it because the moisture indicators had been tripped.
youd think there would be a way to reforce the OS onto the phone to try to get it going again.

If it was sitting on the charger and went bad, perhaps your charger fried it in some way. Sorry to hear your loss, but look it as an opportunity to get an better phone

Question Bricked Pixel 5a/QUSB code of death

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.

Question [SOLVED] Pixel 7 Dead(?)

Was installing the new build using flash-all.sh (without wipe) as I was rooted with Magisk.
Installer got stuck halfway. Disconnected, tried booting, got an error message saying device may have been corrupted or something like that.
The phone doesn't boot at all now, not even to the bootloader. Literally nothing shows up on the screen.
Any help would be greatly appreciated.

Double-check your download and make sure you have panther for Pixel 7.
Depending on what is corrupted, it may be very difficult to recover. With Qualcomm SoCs you can use a low-level tool like QPST (Qualcomm Product Support Tool). For Exynos you can often use ODIN. For Pixel, ODIN doesn't work and there aren't any QPST files (prob never will be).
I don't know how it works on linux, but on Windows I open Device Manager and plug my phone in. Depending on what you see will determine next steps.

Hung0702 said:
Double-check your download and make sure you have panther for Pixel 7.
Click to expand...
Click to collapse
Yes, the images are for panther.
Hung0702 said:
I don't know how it works on linux, but on Windows I open Device Manager and plug my phone in. Depending on what you see will determine next steps.
Click to expand...
Click to collapse
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.

dewri21 said:
Yes, the images are for panther.
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.
Click to expand...
Click to collapse
Unfortunately your only option is repair. Find a Google certified repair center such as uBreakiFix. Your device should still be under warranty. The tools necessary to recover a device when the bootloader fails are not publicly available.

V0latyle said:
Unfortunately your only option is repair. Find a Google certified repair center such as uBreakiFix. Your device should still be under warranty. The tools necessary to recover a device when the bootloader fails are not publicly available.
Click to expand...
Click to collapse
I have had pixel phones disassembled and have hooked them up to the android flash tool and they were recognised , even though the screens were blank the tool knew what was connected. Its a shot it might beable to help .

hammered58 said:
I have had pixel phones disassembled and have hooked them up to the android flash tool and they were recognised , even though the screens were blank the tool knew what was connected. Its a shot it might beable to help .
Click to expand...
Click to collapse
The Android Flash Tool works via ADB, so if the bootloader is corrupted or fails for some reason, that isn't an option.
Pixel devices (at least Snapdragon ones) do have the Qualcomm USB mode, but Google's prescribed means of repair in this situation is to simply replace the mainboard; most repair stations do not have QPST or the necessary files to restore the bootloader.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
I have not come across a pixel device that cannot be restore...Google basically made this phone indestructible from software stand point.
use the above link to restore phone.

In the future I would suggest removing magisk before updating, would save yourself a lot of trouble. Just backup your modules to a folder on your phone and you can get them back quickly

Is it possible for you to take a pic of what your phone says? I think i ran into a very similar situation but i was able to access fastboot, just want to see if it's the same error i got

Make sure that
1. The latest adb is saved to the folder you extracted the factory image file
2. There is enough disc drive space available
Then rerun the flashall.bat from that folder

dewri21 said:
Yes, the images are for panther.
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.
Click to expand...
Click to collapse
Yikes. I had that happen to two Pixel 5a phones.
They booted into Qualcomm mode. I checked windows device manager and saw that it was a device, using qcomm, and there is no way to repair this one was rooted, one wasn't rooted.
I ended up buying a pixel 6 and 7.
Also, I noticed this occurred during the monthly patch cycle.
There is no way to get into the bootloader, fastboot, recovery, or safe mode.
I hope that isn't the situation with the 7s as well.
Good luck, please post your findings!

Vio281 said:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
I have not come across a pixel device that cannot be restore...Google basically made this phone indestructible from software stand point.
use the above link to restore phone.
Click to expand...
Click to collapse
Not really. That’s how I broke it while updating. My phone wouldn’t boot at all and wasn’t even detected by my mac and windows pc. Had to send it to the service center.
t3chwizard said:
In the future I would suggest removing magisk before updating, would save yourself a lot of trouble. Just backup your modules to a folder on your phone and you can get them back quickly
Click to expand...
Click to collapse
Thanks, I will do that.
J0nhy said:
Is it possible for you to take a pic of what your phone says? I think i ran into a very similar situation but i was able to access fastboot, just want to see if it's the same error i got
Click to expand...
Click to collapse
It was just a black screen. It wouldn’t boot into any menu whatsoever.
Sui77 said:
Make sure that
1. The latest adb is saved to the folder you extracted the factory image file
2. There is enough disc drive space available
Then rerun the flashall.bat from that folder
Click to expand...
Click to collapse
Yes, that’s how I initially updated which somehow broke it. Anyway, got it repaired for free since it’s in warranty.
grandpajiver said:
Yikes. I had that happen to two Pixel 5a phones.
They booted into Qualcomm mode. I checked windows device manager and saw that it was a device, using qcomm, and there is no way to repair this one was rooted, one wasn't rooted.
I ended up buying a pixel 6 and 7.
Also, I noticed this occurred during the monthly patch cycle.
There is no way to get into the bootloader, fastboot, recovery, or safe mode.
I hope that isn't the situation with the 7s as well.
Good luck, please post your findings!
Click to expand...
Click to collapse
Hi, I had to send in the phone for a repair. It was a free repair since the phone’s in warranty.

That happened to me with Pixel 6 Pro. The screen only showed the charging icin and wouldn't respond and the phone was getting hot. I ended up rebooting it by holding the power key and one of the volume buttons (don't remember which one) for like 30-40 seconds and that rebooted it and from there I got to recovery mode and flashed the image via sideload.

Question Black screen of death / GrapheneOS Pixel 5a

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!