Database Develop

BRom Error - Obtain DRAM Failed?

Soooooo, I installed a new layer and the phone borked, hooked it up to the unbrick restore tool kit, it flashed the whole rom and failed after 100%, Now when I connect it it gives me this. Any help?

Try this: http://onlinejobwithoutanyinvestment.com/sp-flash-tool-errors-fix-brom-error/
Can you get into recovery and reformat?

Maybe as of now, try to follow this post.
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I assume you have tried the restore method posted by tomsgt. And on that thread there are a few other posts same error as you

Hello, the recent bricks appear to have something to do with a guide posted by a user recently. If you have bricked your phone, please join the hangout below where we will cooperate with you to investigate the cause of your brick and attempt to find a fix.
Join the conversation on Hangouts: https://hangouts.google.com/group/Q5wGs6508l1rqGng2
Sent from my LG G4 using XDA Labs

Various from errors
It looks like the hangout stated above is closed, but I looked at the other link and I'm hoping someone might be able to clarify. Under the brom 4032 it states:
download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
Do they mean the preloader driver? Or the preloader file that would be in the firmware or somewhere. And it goes into the sp flash tools folder somewhere? Or the firmware I'm flashing? I have the 16/2 Amazon version, and I actually have another I'm using that has been successfully rooted and bootloader unlocked. Is there something I could extract from the working phone to help jumpstart the bricked one?

Persuasion89 said:
It looks like the hangout stated above is closed, but I looked at the other link and I'm hoping someone might be able to clarify. Under the brom 4032 it states:
download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
Do they mean the preloader driver? Or the preloader file that would be in the firmware or somewhere. And it goes into the sp flash tools folder somewhere? Or the firmware I'm flashing? I have the 16/2 Amazon version, and I actually have another I'm using that has been successfully rooted and bootloader unlocked. Is there something I could extract from the working phone to help jumpstart the bricked one?
Click to expand...
Click to collapse
This is what i reed from the error list. None of the fixes that i see say to touch the preloader.
"7. Error 5054 – BROM ERROR S_DL_GET_DRAM_SETTINGS_FAIL (5054)
Fix : Need to Check load matches your target which is to be downloaded. For more info, that the file you’re trying to flash do not belong or not compatible with your phone. Verify that you are using the right version of files for your device. If so, try to formatting before flashing again."
and just to show what i read about 4032 (not the error the op has)
14. Error 4032: Operation Skill Problems
Fix : Press the volume down button (key to reduce volume), then it can trigger the yellow bar progress continue. You’d better install batteries in your mobile during flash process.
edit 1:
sorry rereading page it get confussing. there multiple error 4032 messages.
6. Error 4032 – BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail
Fix : Ensure that the files you are trying to flash are exact version of your phone model. If so, now try to formatting your phone but do not format the boot loader before flashing it. Sometimes, device that produce in 2014 also result this error code, solution is download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
This would be the best solution for BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail, SP Flash Tool is unable to enable DRAM or communicate effectively with your device issue.
but still this error does not have same text as the op

mrmazak said:
This is what i reed from the error list. None of the fixes that i see say to touch the preloader.
"7. Error 5054 – BROM ERROR S_DL_GET_DRAM_SETTINGS_FAIL (5054)
Fix : Need to Check load matches your target which is to be downloaded. For more info, that the file you’re trying to flash do not belong or not compatible with your phone. Verify that you are using the right version of files for your device. If so, try to formatting before flashing again."
and just to show what i read about 4032 (not the error the op has)
14. Error 4032: Operation Skill Problems
Fix : Press the volume down button (key to reduce volume), then it can trigger the yellow bar progress continue. You’d better install batteries in your mobile during flash process.
edit 1:
sorry rereading page it get confussing. there multiple error 4032 messages.
6. Error 4032 – BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail
Fix : Ensure that the files you are trying to flash are exact version of your phone model. If so, now try to formatting your phone but do not format the boot loader before flashing it. Sometimes, device that produce in 2014 also result this error code, solution is download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
This would be the best solution for BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail, SP Flash Tool is unable to enable DRAM or communicate effectively with your device issue.
but still this error does not have same text as the op
Click to expand...
Click to collapse
Well to clarify I also receive the 0x13be or whichever is in the op attached picture. I'm pretty sure this is what I get if I plug in my phone while completely powered down after hitting download. Red bar loads like in picture, and then error. However I've tried various button techniques as advised by other posts and sources, which yield various other errors including the 4032 and 5034. It seems like it just depends on how the setup is feeling. I'd verify which methods yield which results, but I'm having boot issues with my laptop now. My basic logic though is they're all hanging at the same spot, immediately after da load but prior to injection. Maybe this is noobish but I think it's one issue causing all of the errors, and I'm hoping that a solution for either op or I would benefit us both. I'm not very experienced but I have a feeling the preloader.bin isn't doing its thing. Will I be able to get this file with a read back of a working r1 16/2? That's a little long, and sorry if these answers are out there but I've looked around over the last week and I get pointed in a direction, but I can't find a solid answer. I'd really just like to be informed as I don't want to break anything else.

Persuasion89 said:
Well to clarify I also receive the 0x13be or whichever is in the op attached picture. I'm pretty sure this is what I get if I plug in my phone while completely powered down after hitting download. Red bar loads like in picture, and then error. However I've tried various button techniques as advised by other posts and sources, which yield various other errors including the 4032 and 5034. It seems like it just depends on how the setup is feeling. I'd verify which methods yield which results, but I'm having boot issues with my laptop now. My basic logic though is they're all hanging at the same spot, immediately after da load but prior to injection. Maybe this is noobish but I think it's one issue causing all of the errors, and I'm hoping that a solution for either op or I would benefit us both. I'm not very experienced but I have a feeling the preloader.bin isn't doing its thing. Will I be able to get this file with a read back of a working r1 16/2? That's a little long, and sorry if these answers are out there but I've looked around over the last week and I get pointed in a direction, but I can't find a solid answer. I'd really just like to be informed as I don't want to break anything else.
Click to expand...
Click to collapse
Well your attention to detail is vital. As you are one of the first to have come across this issue on this phone so when we do have a solution if will most likely become a stiky guide so to prevent further issues. Hopefully you are not past your Amazon return point. As far as I know there is not an answer on what you will need to do. So if we have time to keep troubleshooting that will be good but if you need to do a return that is understandable.

mrmazak said:
Well your attention to detail is vital. As you are one of the first to have come across this issue on this phone so when we do have a solution if will most likely become a stiky guide so to prevent further issues. Hopefully you are not past your Amazon return point. As far as I know there is not an answer on what you will need to do. So if we have time to keep troubleshooting that will be good but if you need to do a return that is understandable.
Click to expand...
Click to collapse
I have two, the other one is just going to be a backup so I'll report back if I find a silver bullet. It's recognized by PC and still trying to come back, so if I totally brick it I'll call the 60$ cost of education.

Persuasion89 said:
I have two, the other one is just going to be a backup so I'll report back if I find a silver bullet. It's recognized by PC and still trying to come back, so if I totally brick it I'll call the 60$ cost of education.
Click to expand...
Click to collapse
I feel the same way, legit bought two of these to just play around with. The mistake I made was somehow enabling format all + Download. This completely borked my phone.
I am using a S7 Edge, and i'm also on Verizon, my girlfriend is on Tmobile however and when her case comes tomorrow she will be retiring her G3 for this phone. Her phone is fine though.
Mine does the fancy download mode of just showing red at the bottom of the tool when you plug it in and the only sign of life is through the LED on the phone, like the eye of the terminator. Just a red led, constantly on.
Phone will connect instantly, but after being connected to the PC for at least 30 seconds it'll randomly make the disconnect noise and the tool will no longer recognize it, but interesting enough the LED is still on and if you hit download after the "disconnect" then actually REMOVE the cable, you'll get an error even though no download mode is present at least not visably.
If you open device manager under windows 10 for me, and then connect the phone it'll show the MediaTek under com/Ports, but after it makes the disconnect sound it's no longer there {No duh, right} Just an observation...but after a minute or so it'll automatically pop back up.
This made Colton and Mr. Mazak think that the preloader is still in tact, just everything else is out of whack.
We are currently in the process/thinking of a way to create a scatter for the entire backup of the phone (The first boot into TWRP) and seeing if there is a way to completely restore the phone from the SPFT via the new scatter/backup.
I do not know how to do this, so I am waiting on the R1 HD gods to bestow upon me their methods of wisdom and hopefully fix the brick! Colton told me it'll be a couple days, i'm in no hurry, but it's always exciting to think there's a possible fix, and considering this is an ugly problem, if it gets fixed they're going to save many phones.
etc, etc.

Yeah exactly what I'm dealing with, well first I was getting a flashy home screen after boot. Re flash didn't work so I took the bad advice of format+DL. The thing I don't get though is if it's not the preloader then why won't ANYTHING flash.
Have you tried a read back? Because every option on my end is just a brick wall right after initialization. I figured if preloader is intact then it would at least attempt to read the memory blocks, or let me attempt a format, or anything. My phone's picked up properly by two PCs, and really the red bar is the da handshaking the preloader to lock the phone in that state during the flash right? Or Chinese to English translation is more difficult to understand than I expected.
Regardless I'm just a noob with too much free time. I'm Trying to make a bootable drive for my laptop so I can put in work, but latest Ill be at it here in a couple hours once I'm free. I'm convinced this is fixable so I'm going to pull everything I can from the working phone and see what I can figure out. Ill be back to consult the thread before I do anything big though. Hopefully I can contribute some to this. I have a vision of how this is going to work, but I couldn't explain it for the life of me.

Gytole said:
I feel the same way, legit bought two of these to just play around with. The mistake I made was somehow enabling format all + Download. This completely borked my phone.
I am using a S7 Edge, and i'm also on Verizon, my girlfriend is on Tmobile however and when her case comes tomorrow she will be retiring her G3 for this phone. Her phone is fine though.
Mine does the fancy download mode of just showing red at the bottom of the tool when you plug it in and the only sign of life is through the LED on the phone, like the eye of the terminator. Just a red led, constantly on.
Phone will connect instantly, but after being connected to the PC for at least 30 seconds it'll randomly make the disconnect noise and the tool will no longer recognize it, but interesting enough the LED is still on and if you hit download after the "disconnect" then actually REMOVE the cable, you'll get an error even though no download mode is present at least not visably.
If you open device manager under windows 10 for me, and then connect the phone it'll show the MediaTek under com/Ports, but after it makes the disconnect sound it's no longer there {No duh, right} Just an observation...but after a minute or so it'll automatically pop back up.
This made Colton and Mr. Mazak think that the preloader is still in tact, just everything else is out of whack.
We are currently in the process/thinking of a way to create a scatter for the entire backup of the phone (The first boot into TWRP) and seeing if there is a way to completely restore the phone from the SPFT via the new scatter/backup.
I do not know how to do this, so I am waiting on the R1 HD gods to bestow upon me their methods of wisdom and hopefully fix the brick! Colton told me it'll be a couple days, i'm in no hurry, but it's always exciting to think there's a possible fix, and considering this is an ugly problem, if it gets fixed they're going to save many phones.
etc, etc.
Click to expand...
Click to collapse
So just a quick question here. Something clicked for a second. In this description you said Windows shows connected then lost , during the spft process?
If this is case means phone is not realy off.
But if I misunderstand the order nvm.
Maybe disconnecting battery is needed for your situation.

mrmazak said:
So just a quick question here. Something clicked for a second. In this description you said Windows shows connected then lost , during the spft process?
If this is case means phone is not realy off.
But if I misunderstand the order nvm.
Maybe disconnecting battery is needed for your situation.
Click to expand...
Click to collapse
Disconnected the battery, ran the return to stock, red download and red led light only. Same boat.

So just a quick question here. Something clicked for a second. In this description you said Windows shows connected then lost , during the spft process?
If this is case means phone is not realy off.
But if I misunderstand the order nvm.
Maybe disconnecting battery is needed for your situation.
Click to expand...
Click to collapse
I thought the same as well but I was a little afraid to try and get in there to do it. New laptop is coming weds so I haven't had a way to work on this but it's worth a try. I kinda thought the same.
Disconnected the battery, ran the return to stock, red download and red led light only. Same boat.
Click to expand...
Click to collapse
How difficult is it to remove? I'm assuming there's some soldering involved?

Persuasion89 said:
I thought the same as well but I was a little afraid to try and get in there to do it. New laptop is coming weds so I haven't had a way to work on this but it's worth a try. I kinda thought the same.
How difficult is it to remove? I'm assuming there's some soldering involved?
Click to expand...
Click to collapse
Nope. Just remove all the screws underneath the removable cover then the backplate is held in by snaps, I used a guitar pick to pry the edges from the rest of the frame and it popped right out. Do note its rather stiff and flimsy so pry with care.

Gytole said:
Nope. Just remove all the screws underneath the removable cover then the backplate is held in by snaps, I used a guitar pick to pry the edges from the rest of the frame and it popped right out. Do note its rather stiff and flimsy so pry with care.
Click to expand...
Click to collapse
I might give this a shot. also I've read about the test point flashing by grounding one of the pins, Apparently that's how they do it in the factories. If it doesn't work and I'll have it apart anyway I might give it a shot.

Persuasion89 said:
I might give this a shot. also I've read about the test point flashing by grounding one of the pins, Apparently that's how they do it in the factories. If it doesn't work and I'll have it apart anyway I might give it a shot.
Click to expand...
Click to collapse
If you do try to find the "meta" mode. Still can't flash anything yet. Unless you made your own backup before original flash. Because the files in the convert and unbrick section are not the complete ROM. Since you are stuck from doing a format all, I don't think those will do it.
But I do think it is a good idea to find a stable way to get phone connected to PC so it can be flashed though

just see something about vcom drivers. and the op screenshot shows usb driver(lower right corner of photo). it should be a vcom driver(lower right corner of photo)

mrmazak said:
If you do try to find the "meta" mode. Still can't flash anything yet. Unless you made your own backup before original flash. Because the files in the convert and unbrick section are not the complete ROM. Since you are stuck from doing a format all, I don't think those will do it.
But I do think it is a good idea to find a stable way to get phone connected to PC so it can be flashed though
Click to expand...
Click to collapse
so i have a full rom backup. or at least it should be. I also have a full TWRP backup i cant use on my SD card. MT Droid tools doesnt support this chipset though, so I dont know how else to get this readback i did chopped into partitions.

Just wondering, how many phones are bricked? Of these bricked phones how many were caused from flashing witha VM? And how many used the format function to try and recover?

Am I Screwed? Please Help!

So I barely used my phone yesterday, just hotspot for my dad's iphone to upload some pics from his phone to my gdrive while we were out, check notifications from my lockscreen, and whatsapp my wife a couple times. That was done no problem. Hours later without using my phone it was lagging badly, and wouldn't start up certain apps like LastPass, Free Adblocker Browser, and I installed Malwarebytes and did a scan and found nothing, but it would crash instantly upon opening after that as with the other 2 apps. I didn't try many apps, some I would tap on and no response, but that was 1 or 2 apps. The odd thing is my Play Store was uninstalled somehow, which would make me think it was a virus which is why I tried Malwarebytes.
Since that didn't work I did some searching and saw some advice online to boot into recover and wipe the cache partition. I did this and it booted up fine, and I went to sleep. I wake up today, and the phone appears dead. No signs of life. Although, I did put it on the wireless charger and the light changed as if it was charging. I plugged it into my computer and saw in Device Manager under Ports it loaded "Qualcomm HS-USB QDLoader 9008" successfully. I've read if that shows (is this EDL mode?) it can be recovered. It's not showing now after I tried a hard reset, but the wireless charging light still changes. CORRECTION: QDLoader just reappeared as I type this message!
Is this a hard brick? Is my phone finished? Please help with anything you can think of! Like I said there's no signs of life on the actual phone. I tried the hard reset too.
My Note8 is USA Unlocked SM-N950U1 being used in Canada, I don't know the bootloader version, but I THINK it's 5, I haven't installed any malicious/modded apps, I'm not rooted.
Please please help!
Thanks!

delan007 said:
So I barely used my phone yesterday, just hotspot for my dad's iphone to upload some pics from his phone to my gdrive while we were out, check notifications from my lockscreen, and whatsapp my wife a couple times. That was done no problem. Hours later without using my phone it was lagging badly, and wouldn't start up certain apps like LastPass, Free Adblocker Browser, and I installed Malwarebytes and did a scan and found nothing, but it would crash instantly upon opening after that as with the other 2 apps. I didn't try many apps, some I would tap on and no response, but that was 1 or 2 apps. The odd thing is my Play Store was uninstalled somehow, which would make me think it was a virus which is why I tried Malwarebytes.
Since that didn't work I did some searching and saw some advice online to boot into recover and wipe the cache partition. I did this and it booted up fine, and I went to sleep. I wake up today, and the phone appears dead. No signs of life. Although, I did put it on the wireless charger and the light changed as if it was charging. I plugged it into my computer and saw in Device Manager under Ports it loaded "Qualcomm HS-USB QDLoader 9008" successfully. I've read if that shows (is this EDL mode?) it can be recovered. It's not showing now after I tried a hard reset, but the wireless charging light still changes. CORRECTION: QDLoader just reappeared as I type this message!
Is this a hard brick? Is my phone finished? Please help with anything you can think of! Like I said there's no signs of life on the actual phone. I tried the hard reset too.
My Note8 is USA Unlocked SM-N950U1 being used in Canada, I don't know the bootloader version, but I THINK it's 5, I haven't installed any malicious/modded apps, I'm not rooted.
Please please help!
Thanks!
Click to expand...
Click to collapse
Sorry but your phone is finished..

Can you enter to downoad mode ?
on power off condition, press & hold vol down & bixby button, then press power button until download mode appear

ariey said:
Can you enter to downoad mode ?
on power off condition, press & hold vol down & bixby button, then press power button until download mode appear
Click to expand...
Click to collapse
Nothing shows on the screen whatsoever, but it does show life on the wireless charger, and in Windows 7 Device Manager under Ports it shows Qualcomm HS-USB QDLoader 9008.
I'm taking the phone to the official Samsung Service Centre where I live for a free diagnostic to see if they can do anything.

I think I'm stuck in what's known as EDL Mode which I see no solution for, but I could be wrong.

MrMike2182 said:
Sorry but your phone is finished..
Click to expand...
Click to collapse
Samsung Service Centre's can't even repair it?

delan007 said:
Samsung Service Centre's can't even repair it?
Click to expand...
Click to collapse
The service center could fix it yes.. If it's stuck in EDL mode maybe take a look at the root thread for version 5 of the bootloader because they might have a way out of that.. Do you have a picture of the screen it's stuck on?

MrMike2182 said:
The service center could fix it yes.. If it's stuck in EDL mode maybe take a look at the root thread for version 5 of the bootloader because they might have a way out of that.. Do you have a picture of the screen it's stuck on?
Click to expand...
Click to collapse
The phone screen is black as in off. It hasn't turned on since it bricked. Only signs of life are the wireless charger light coming on showing the phone as charging, and the qdloader 2008 on my computer. I didn't see version 5 of the bootloader anywhere, but I may be looking in the wrong spot?
Thanks for the help!

delan007 said:
The phone screen is black as in off. It hasn't turned on since it bricked. Only signs of life are the wireless charger light coming on showing the phone as charging, and the qdloader 2008 on my computer. I didn't see version 5 of the bootloader anywhere, but I may be looking in the wrong spot?
Thanks for the help!
Click to expand...
Click to collapse
I suggest you just take it to the service center because I think your internal memory card is done.. A phone doesn't just normally brick itself. It's not able to find an operating system which is why it's not doing anything.

MrMike2182 said:
I suggest you just take it to the service center because I think your internal memory card is done.. A phone doesn't just normally brick itself. It's not able to find an operating system which is why it's not doing anything.
Click to expand...
Click to collapse
Looks like you're right bro, I took it in and they said no signs of life, and wasn't a battery fault as they tried a new one. He said the motherboard is fried. This was at an official Samsung Service Centre too.
Thanks everyone for the help!

This is interesting, I have the SM-N950U1 and mine just basically did this 3 days ago now. I woke up and the phone was dead (was working the night before, left on charge and went to bed). Since then I was able to turn it on a few times and do the wipe/data delete, but now I'm stuck only being able to kinda get into download mode.
I wonder if there is an issue wit the SM-N950U1 models...

I would take your device to a Samsung Service Center and let them take a look at it.

iceepyon said:
I would take your device to a Samsung Service Center and let them take a look at it.
Click to expand...
Click to collapse
I was able to do this in to a Samsung repair center the other day, they took one look at it and handed it back to me and said it wasn't something they could deal with. They recommended sending it to Samsung directly. I took it to a uBreakiFixit store, which is what Samsung recommended. I heard the guy in the back talking about it saying it needed to be re-flashed and the OS put back on and he handed it back to the front desk guy who relayed the message to me, hah!
Oh well, now its a paperweight...

Question Why is my phone not turning on after restarting?

Hello, guys! I had my Xiaomi Redmi 9t for 6 months now and so far I only encountered minor problems, not until now. Before that, I never did turned my phone off for a very long time or I have never restarted it, but since I noticed that my GPS was crappy---because it didn't show any accurate data while I'm using the Strava app to track my bicycle rides. So, I restarted it and after that the screen just went total black, it never responded despite of how long I pressed the power button, and also I just unplugged it from the charger because it was almost full. I was also able to use it few minutes after the restart without any problems, I heard from other users who owned this phone that this also the same problem they are encountering.
Also, it's not bricked or anything because it was still functioning normally. For not being bricked, I cannot access the fastboot mode since I cannot even turn it on.

If you try to charge it again, does the screen turns on then shows a charging animation?

dinsel said:
If you try to charge it again, does the screen turns on then shows a charging animation?
Click to expand...
Click to collapse
It doesn't do anything. There's no display neither a vibration.

Your device is dead booted. The cause might be related to hardware. So, what I recommend for you is to bring that to a service center to get fixed or replaced. F.

dinsel said:
Your device is dead booted. The cause might be related to hardware. So, what I recommend for you is to bring that to a service center to get fixed or replaced. F.
Click to expand...
Click to collapse
yeah, there are a lot of fellow Filipino users who complained about the same problem. But I think it's also about the latest firmware update, because my younger sisters had the phone but they did not have any of my problem and their firmware versions aren't updated yet.

And just to think of it, the latest update also made my phone cranky. The wifi suddenly turns off and on and the GPS thing (which i mentioned in the post).

You have not been able to press the power + volume button for 10 seconds to achieve something?

ceesarsu said:
You have not been able to press the power + volume button for 10 seconds to achieve something?
Click to expand...
Click to collapse
No. He can't.

derunheimlich said:
Hello, guys! I had my Xiaomi Redmi 9t for 6 months now and so far I only encountered minor problems, not until now. Before that, I never did turned my phone off for a very long time or I have never restarted it, but since I noticed that my GPS was crappy---because it didn't show any accurate data while I'm using the Strava app to track my bicycle rides. So, I restarted it and after that the screen just went total black, it never responded despite of how long I pressed the power button, and also I just unplugged it from the charger because it was almost full. I was also able to use it few minutes after the restart without any problems, I heard from other users who owned this phone that this also the same problem they are encountering.
Also, it's not bricked or anything because it was still functioning normally. For not being bricked, I cannot access the fastboot mode since I cannot even turn it on.
Click to expand...
Click to collapse
Plug it into a computer. Search for device manager in the windows search box. If it shows 'Qualcomm 9008' or something like that, it can be fixed but only in a service center. If it shows 'unknown usb port' then you lack the usb drivers, but still can be fixed. If it does not show in computer, not even 'unknown usb device', your device is not bricked, it is gone for good (or maybe the usb port is fried and also the battery drained, you can replace them as a last resort)

Did it get wet?

LR7875 said:
Plug it into a computer. Search for device manager in the windows search box. If it shows 'Qualcomm 9008' or something like that, it can be fixed but only in a service center. If it shows 'unknown usb port' then you lack the usb drivers, but still can be fixed. If it does not show in computer, not even 'unknown usb device', your device is not bricked, it is gone for good (or maybe the usb port is fried and also the battery drained, you can replace them as a last resort)
Click to expand...
Click to collapse
LR7875 said:
Plug it into a computer. Search for device manager in the windows search box. If it shows 'Qualcomm 9008' or something like that, it can be fixed but only in a service center. If it shows 'unknown usb port' then you lack the usb drivers, but still can be fixed. If it does not show in computer, not even 'unknown usb device', your device is not bricked, it is gone for good (or maybe the usb port is fried and also the battery drained, you can replace them as a last resort)
Click to expand...
Click to collapse
I turned it over to the service center yyesterday. They told me that it'll be fixed tomorrow or friday. Which I'm really hoping.

blackhawk said:
Did it get wet?
Click to expand...
Click to collapse
No. I haven't even dropped it

Had the same problem today, phone is updated to the lastest firmware. Just woke up and the phone isn't even turning on, tried fastbooting while charging but nothing at all on the screen. Didn't get it wet nor dropped it. Guess we gotta replace the phone huh.

I don't update. The first thing disable is OTA updates. Many apks still running factory load versions as well.
In over 1.5 years on Pie, no factory resets due to malware. My current load is over a year old, still fast and stable.
Rule#1 if your OS is running fast, stable and fulfilling its mission... let it be.

blackhawk said:
I don't update. The first thing disable is OTA updates. Many apks still running factory load versions as well.
In over 1.5 years on Pie, no factory resets due to malware. My current load is over a year old, still fast and stable.
Rule#1 if your OS is running fast, stable and fulfilling its mission... let it be.
Click to expand...
Click to collapse
Completely agreed if you have a Xiaomi. I regretted updating to MIUI 12 because it is s l o w.

LR7875 said:
Completely agreed if you have a Xiaomi. I regretted updating to MIUI 12 because it is s l o w.
Click to expand...
Click to collapse
Doesn't matter what OS; leave a strong running OS alone... as long as you understand it's vulnerabilities. Even a malware forced reload be easier than putting up with a doggy OS every second of every day

blackhawk said:
Doesn't matter what OS; leave a strong running OS alone... as long as you understand it's vulnerabilities. Even a malware forced reload be easier than putting up with a doggy OS every second of every day
Click to expand...
Click to collapse
MIUI android 11:
Unfortunately, system UI has stopped.
Me:
Grabs a drill

LR7875 said:
MIUI android 11:
Unfortunately, system UI has stopped.
Me:
Grabs a drill
Click to expand...
Click to collapse
Yeah the whole Hulk SMASH thing... maybe a lobotomy is more civilized.

LR7875 said:
MIUI android 11:
Unfortunately, system UI has stopped.
Me:
Grabs a drill
Click to expand...
Click to collapse
At the moment my mobile is all great, it is a little more fluid with android 11

No idea, man. Sounds serious problem.

My Google Pixel 4 XL Dead Overnight!

Hello XDA community yesterday I was using my pixel phone normally and it was working fine today morning I woke up to check time on my phone but my phone was dead, screen was completely pitch black, charging phone doesn't work screen stays dead, even its not going to bootloader it feels like phone is completely dead but when I connect it to pc I hear connection sound and a random pop up show that device is not detected etc. I searched on internet and it feels like when I was sleeping because my phone was on charging and WIFI was connected( normally I don't use WIFI I use mobile data) maybe a software update was installed which made phone software & drivers to get corrupted because nothing is working nor its charging, booting, vibrating its completely dead
I searched on internet and also installed QUALCOMM drivers on my pc that unknown popup while connecting while to pc shifted into
Qualcomm HS-USB QDLoader 9008
and I also get know that a firehose file can maybe fix my phone because maybe bootloader is corrupted or anything if anyone can help me in this matter I will really appreciate it. Thanks!

Noman8 said:
Hello XDA community yesterday I was using my pixel phone normally and it was working fine today morning I woke up to check time on my phone but my phone was dead, screen was completely pitch black, charging phone doesn't work screen stays dead, even its not going to bootloader it feels like phone is completely dead but when I connect it to pc I hear connection sound and a random pop up show that device is not detected etc. I searched on internet and it feels like when I was sleeping because my phone was on charging and WIFI was connected( normally I don't use WIFI I use mobile data) maybe a software update was installed which made phone software & drivers to get corrupted because nothing is working nor its charging, booting, vibrating its completely dead
I searched on internet and also installed QUALCOMM drivers on my pc that unknown popup while connecting while to pc shifted into
Qualcomm HS-USB QDLoader 9008
and I also get know that a firehose file can maybe fix my phone because maybe bootloader is corrupted or anything if anyone can help me in this matter I will really appreciate it. Thanks!
Click to expand...
Click to collapse
Did you try both
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
already?
Here is a guide on how to get ADB working:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Do you have OEM Unlocking enabled? Maybe unlocked bootloader (if your bootloader is dead and you haven't unlocked it previously, there might not be much hope for you)? If you can't even get into recovery/fastboot mode, you are in deep.

Morgrain said:
Did you try both
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
already?
Here is a guide on how to get ADB working:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Do you have OEM Unlocking enabled? Maybe unlocked bootloader (if your bootloader is dead and you haven't unlocked it previously, there might not be much hope for you)? If you can't even get into recovery/fastboot mode, you are in deep.
Click to expand...
Click to collapse
Yes i have tried both nothing is working my phone was fresh it wasn't rooted,its bootloader was locked it was basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i hear connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...

Noman8 said:
Yes i have tried both nothing is working my phone was fresh it wasn't rooted,its bootloader was locked it was basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i hear connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...
Click to expand...
Click to collapse
You might want to wait some time, until the battery runs out/depletes. Then try to charge it/start it. But that route will take a couple of days.

Noman8 said:
No my phone was fresh it wasn't rooted,its bootloader was locked it basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i head connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...
Click to expand...
Click to collapse
Morgrain said:
You might want to wait some time, until the battery runs out/depletes. Then try to charge it/start it. But that route will take a couple of days.
Click to expand...
Click to collapse
Ahan i see btw thanks for replying!

Noman8 said:
Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
Yes, your pixel is now dead. Similar to what happened with my Pixel 2.

NinjaCoool said:
Yes, your pixel is now dead. Similar to what happened with my Pixel 2.
Click to expand...
Click to collapse
Yes

pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose

r1pp3d2 said:
pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose
Click to expand...
Click to collapse
hi brother can it be fixed with firehose? please reply
and what are exact steps to flash Firehose!

r1pp3d2 said:
pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose
Click to expand...
Click to collapse
i am trying to flash this firehose to my pixel but it is requiring 2 more files "RAW PROGRAM & PATCH" FILE if u can help me here i will appreciate that!

That would be the backup of the phone. These are not backups.

Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.

nicauderan said:
Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.
Click to expand...
Click to collapse
Google doesn't just kill phones like that. My Pixel 4XL is still find, hell my Nexus 6 still works.

nicauderan said:
Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.
Click to expand...
Click to collapse
You are not getting your pixel back now u can replace motherboard now like i did i ordered new motherboard from ali express and Replaced it!

Just received motherboard from Ali and the pixel respawned.

Was charging my pixel 4, it was 100% charged for a good few hours, I woke up around midnight and was playing a game on my phone when suddenly it went black. I unplugged the phone and tried a few fixes. After crying it out and leaving it uncharged I plugged it into my portable charger where the lights came on, still nothing on my phone. I also tried plugging into my computer and no sounds or any sign it had been plugged into my computer from both phone or computer. I was thinking if this is a battery issue it should at least do something on my computer right? I have tried again to plug it into my portable charger and this time no lights on the portable charger. Maybe this isn't the right thread but I figured I'd post here anyway, any suggestions, should I take it to a shop? I'm not tech savvy, could it be a display or battery issue or a motherboard issue like above?
also to note, I had both the front and back glass changed almost a year ago now, and except from one dead pixel on the screen from the original glass break its been fine.
Also to note, I recently moved from Australia to Canada and am using a plug converter that my laptop computer is also plugged into and its fine, so I'm thinking it wasn't a power surge? It has two usb ports and a Au plug on the same converter plug.

Oh, you are not alone. 3 days after Android 13 update, I woke up, my Pixel 4XL alarm went off, used Android Auto to go to work and listen to music, checked email on it at work, plugged it in to my Pixel approved charger/cable as always, picked it up hours later and .... brick. No response to charger plug/unplug even with various other plugs and cables. No response to 30 sec of pressing power or power with up/down volume combos. It was a brick, just like many other Pixel 2,3,4,5 owners reported after various updates over the years, courtesy of Qualcomm chips and Google's lack of quality checking chips. Today's lesson: Stop paying Google for trash. It happened to me 280 days after the warranty expired. Google said that if it was from the Android 13 update, I should take it to UbreakitIfixit near me and they will fix it under an extension of 1 year to the warranty. We'll see. Sadly, it will still have Google's low grade Qualcomm chip design after the repair.

Question Need a little help...

First time posting here. And I have tried all that i can think to do. My daughter has a Google Pixel 5a, that was not backed up to the cloud, for which she dropped and the screen doesnt work...like black screen. I have tried some of the tools to back it up, but requires USB debugging on, and I am not sure she had dev tools turned on and I cannot figure out what to do. Device seems to turn on as PC can read it. Any ideas? I am stumped. I tried the button sequence to try to get into adb fastboot but i havent had any luck yet.

bskramer79 said:
First time posting here. And I have tried all that i can think to do. My daughter has a Google Pixel 5a, that was not backed up to the cloud, for which she dropped and the screen doesnt work...like black screen. I have tried some of the tools to back it up, but requires USB debugging on, and I am not sure she had dev tools turned on and I cannot figure out what to do. Device seems to turn on as PC can read it. Any ideas? I am stumped. I tried the button sequence to try to get into adb fastboot but i havent had any luck yet.
Click to expand...
Click to collapse
Check Device Manager when the device is plugged in. If it shows up as Qualcomm something or other, the only way to recover it is via a mainboard replacement, which will wipe data.
Even with ADB/fastboot, it's not possible to back up the phone without root.

Shows up as MTP...No qualcom

bskramer79 said:
First time posting here. And I have tried all that i can think to do. My daughter has a Google Pixel 5a, that was not backed up to the cloud, for which she dropped and the screen doesnt work...like black screen. I have tried some of the tools to back it up, but requires USB debugging on, and I am not sure she had dev tools turned on and I cannot figure out what to do. Device seems to turn on as PC can read it. Any ideas? I am stumped. I tried the button sequence to try to get into adb fastboot but i havent had any luck yet.
Click to expand...
Click to collapse
I just found out from my local UBreakIFix that Google has extended their warranties for all screen issues on the Pixel 5a, which means you could get a free screen replacement. My warranty expired back in Aug 22 and they gave me a free replacement for my black screen. It was done in 20 minutes. https://support.google.com/pixelphone/answer/11833075?hl=en