Database Info

[Q] SGH-T959D constantly rebooting - cannot mount internal sd card ?!

I've been really happy with my Galaxy S Fascinate 3G+ SGH-T959D... I've got that phone brand new from Telus on February 28 2011... now we are march 18th 2012... 1 year and 2½ something weeks...
This morning, my phone woke me up, I went to a meeting (recorded 2 hours of audio of this meeting), took notes on my phone, placed calls, send sms, return home for dinner, put my phone on the table, send an sms, took a small lunch in the living room while reading and I suddently hear the booting song from the phone...
I thought the battery had drain and the phone was rebooting or something... and I don't hear nothing else after. 2 hours later, I pick up my phone to place a call and I realize my phone is rebooting constantly...
I see the telus logo, the galasy S logo flying by and then it restarts over and over...
I immediately went to my telus store (where I learn the great news that my phone is no longer under warranty by 2½ weeks), and the manager did try a new sim card, try my sim card in another phone, made me reboot my phone holding volume key and power key, tried to do a factory reset...
Nothing worked, I only see the telus logo and the galasy flying by...
My phone is not rooted (I do not understand much about that) and was using the stock telus android 2.3.2 if I am not mistaken...
What the hell did happend to my phone while it was sitting on the dining table ? It destroy itself in standby mode ???
I have tried to seek information about that issue on xda but I get so many different solution, for different devices, and mainly I see this happen when people are trying to modify their phones rom or trying rooting where mine is using a stock version...
The last thing that worries me the most is that when I connect the USB cable to my PC, it detects nothing (win7 64bit) even when in recovery mode (with the yellow android logo) where the telus guy tried to see the phone on the store computer.
Anyone can help ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try wipe data/factory reset. It will erase everything on the phone. The SD card will be untouched and you will still have pictures, music and recordings.

Still a no go...
AaRcSvN said:
Try wipe data/factory reset. It will erase everything on the phone. The SD card will be untouched and you will still have pictures, music and recordings.
Click to expand...
Click to collapse
Hi AaRcSvN, I've done this with the telus store manager and still, I get the same exact result.
The phone seems to boot up with the music and Telus logo, then I see the flying galaxy S logo and it reboots.
I have just tried it again and it does the same thing, reboot constantly and it shows the error you see in the picutre :
"E:Failed to mount /sdcard (file exist)"
"E:copy_dbdata_media:Can't mount /sdcard your storage not prepared yet. please use UI menu for format and reboot actions"
"Meida files copy failed."
What is the UI menu ?? Where and how can I get to that menu ?
Any other input would be greatly appreciated !
Thanks again AaRcSvN

Ok the UI (user interface) menu is in the picture you took. I'm guessing you scrolled the menu with the volume controls to "wipe data/factory reset" and did that.
Other people have the same problem. You might have to set up Android SDK >> http://bit.ly/GBRP39 on your computer to do some things.
Follow this first:
http://forum.xda-developers.com/showthread.php?t=1264603

AaRcSvN said:
Ok the UI (user interface) menu is in the picture you took. I'm guessing you scrolled the menu with the volume controls to "wipe data/factory reset" and did that.
Other people have the same problem. You might have to set up Android SDK >> http://bit.ly/GBRP39 on your computer to do some things.
Follow this first:
http://forum.xda-developers.com/showthread.php?t=1264603
Click to expand...
Click to collapse
Thanks AaRcSvN for following up... I've been reading a lot and indeed, a lot of people do report that issue but it is because they have tried to root or install custom rom... the thing that worries me is that mine was a clean device running stock provider software...
It's nice when you get some support when you are kind of lost and specially that I am far from being a wizz at handling these advance setup operations...
Thanks for your time and all the links about the SDK that I will install and will follow the xda thread you suggest me.

That's it I guess...
well, after trying methods found in the thread you submitted me to read where it seems there was a lot of hope, I read this :
"E:Can't mount /dev/block/mmcblk0p1 error you got means internal SD failure, this usually means it needs a PCB replacement (a new motherboard)"
That information was found in this post
After the manipulation found in the thread, I now have a different screen which display this :
I even have the format sd card now (which I did not have before) but even when I try this, I get a dead phone blank screen after the galaxy S splash screen at startup...
which seems to seal the faith of my phone... I know owe 320$ balance to my provider for a confirmed dead phone...
So for all people who have this issue and specially with mmcblk0p1 error, it seems that we have a dead sd card on our motherboard...
Thanks for all the great information

Confirmed dead phone mmcblk0p1 error
I sent my phone to an authorized samsung service center and they confirmed what I have read in the preceeding forum about the mmcblk0p1 sdcard error...
They need to replace the motherboard of the phone, a 300$ job...
So if you get this error, I am not saying it is not fixable but as I read, there is a good chance that your phone is dead and need motherboard replacement.
I got that error on a original phone, not running custom roms and not being unlock or rooted. The phone simply died by itself sitting on the kitchen table. On my phone, this error is due to a failing internal sdcard.
Good luck with your phone if you have the same error and if by any chance you were able to start your phone again with this error, share your findings.

wooohoooooooo !
After a couple calls and maybe two hours of my time, Samsung greatly agreed to fix my phone free of charge even though the warranty was out of about 3 weeks.
It has been a roller coaster over the phone but the final result is a fully functionnal phone.
So thumbs up for Samsung. If you are in a similar situation of being out of warranty for 2 or 3 weeks, if you think your time is worth it, call samsung and discuss calmly with the operator.
Just a note on one thing that happend to me. I bought my phone with my master card which has a double extention warranty plan. You buy something that has 1 year, the master card warranty will ad another year of corverage.
When I bought my phone, on the receipt, it was displayed 1 Galaxy S Fascinate 529$ -480$ balance in exchange of a 3 year contract. Total that had been paid was actually 56.99$.
The salesperson at Telus convince me to get the balance as I wanted to buy the phone in one shot. She explained me that if I keep my phone for 3 year, it will only cost me 56.99$ but if I end my contract, I have to pay the balance (480$/36months remaining).
What I had not though at that time is if the phone break after the warranty, you'll have to pay your balance for a non working piece of equipement. In my mind the full price of the phone was covered.
Even though I explained to master card that I needed to pay that phone if I cancel my contract and that it was a balance and not a rebate, they would only conver the initial amount at the moment of the payment which is 56.99$.
Conclusion, if you have such a warranty coverage on one of your credit card, be sure to pay entirely your item because if it has a balance, it won't be covered.
Will I buy another Samsung product? absolutely. Will I suggest to buy Samsung product to someone else? absolutely. I am pleased with their service and I am pleased that they actually care about their customers. It was nothing for them to authorized that repair and they made a long time Samsung customer happy that will spread his story positively.
Thanks Samsung and everybody that help on the forum !

SIM Card Not Detected in xt925

I bought an xt925 on eBay. It originated in Latin America (I believe Claro Puerto Rico). I am trying to use it on AT&T, using CM 10.2.
I have tried everything I can find to get this phone to detect the SIM card. I cut my SIM card from my previous phone. It still works with an adapter in the previous phone (Samsung Captivate). It also works without the adapter in a Nokia Lumia 920. I tried putting in my girlfriend's SIM from her iPhone 4S into the xt925, but that wasn't detected either. I have tried flashing several other ROMs (CM 10.1, Slim, Xenon, etc.) with the same results.
I have done a lot of searching, and it seems everyone else having a similar problem does not see their Baseband or IMEI. I see both of those things fine. It's acting as if there is no SIM in there at all. No voice, no data.
If I go to Network Operators in the settings, it detects AT&T and T-Mobile as options. When I try to manually select either of them, it says "Your SIM card does not allow a connection to this network."
Can someone steer me in the right direction? Do I have a hardware issue? Modem/radio?

isharted said:
I bought an xt925 on eBay. It originated in Latin America (I believe Claro Puerto Rico). I am trying to use it on AT&T, using CM 10.2.
I have tried everything I can find to get this phone to detect the SIM card. I cut my SIM card from my previous phone. It still works with an adapter in the previous phone (Samsung Captivate). It also works without the adapter in a Nokia Lumia 920. I tried putting in my girlfriend's SIM from her iPhone 4S into the xt925, but that wasn't detected either. I have tried flashing several other ROMs (CM 10.1, Slim, Xenon, etc.) with the same results.
I have done a lot of searching, and it seems everyone else having a similar problem does not see their Baseband or IMEI. I see both of those things fine. It's acting as if there is no SIM in there at all. No voice, no data.
If I go to Network Operators in the settings, it detects AT&T and T-Mobile as options. When I try to manually select either of them, it says "Your SIM card does not allow a connection to this network."
Can someone steer me in the right direction? Do I have a hardware issue? Modem/radio?
Click to expand...
Click to collapse
The phone is either SIM locked or the US carriers are blocked via NV Item 8322:
http://forum.xda-developers.com/showthread.php?t=2166542
You have to be running the stock firmware (not CM) to perform the unlock.

kabaldan said:
The phone is either SIM locked or the US carriers are blocked via NV Item 8322:
http://forum.xda-developers.com/showthread.php?t=2166542
You have to be running the stock firmware (not CM) to perform the unlock.
Click to expand...
Click to collapse
Ah, that makes sense. Thanks for the reply, kabaldan. I'll see if I can make some time to work through this tonight and post my results.
The eBay post said it was unlocked, but I doubt it went though that process.

I flashed the stock firmware and went through the steps. It was reading all of the data fine (IMEI, ESN, PESN, etc.). When I did a read on 8322, it populated the Data box with 00. However, the Read button was red instead of green. Not sure if that's expected.
I rebooted the phone. Still the same issue. I went ahead and wrote 00 to 8322. Still no difference.
Is there a way I can tell if it is SIM locked?

I'm bumping this because it fell off the first page. Does anyone have any advice for me?

Im having a similar issue with a razr hd (xt925)
My problemis that the phone does not read an item 8322. Any help help for us both is appreciated!:cyclops:

DaNpPR said:
My problemis that the phone does not read an item 8322. Any help help for us both is appreciated!:cyclops:
Click to expand...
Click to collapse
It sounds like you actually have the XT926 which is typically for Verizon. You'll need to do the NV edit on 8322, if the button shows up red then something is wrong. Check to make sure you have proper drivers for ADB / etc and are booted into the proper mode when doing the edit (I can't remember now -- Factory mode comes to mind. It appears to boot normally but when you get into the OS you'll see the battery icon with a ?.
Your EBay seller is technically correct, the phone is unlocked for every carrier except ATT/TMobile in the US (without the NV edit).
-- Dan

I have decided to give this another try. I'll post some data to explain what I'm seeing. Can anyone tell me if the symptoms I see are consistent with a locked SIM card? Or could it possibly be another issue?
Here's what I get from RadioComm
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone know what the red Read button means?
Here's the full output if that helps:
Code:
Sending 'NVRead' command with data '822000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' to the radio...
Sent to radio: 268220000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004C647E
Returned from radio: 26822000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500F41A7E
NVRead ==>SUCCESSFUL
Time to execute command: 0.012 seconds.
Command timeout set to : 15 seconds.
EDIT: I after doing the NV item 8322, I haven't tried a newer SIM card. I put in a "dummy" SIM from a phone that was purchased and never activated, and the SIM errors went away. I'll try to pry away someone's newer, valid SIM tonight to see if I have any luck.

I went to the AT&T store and swapped out my old SIM card for a new micro SIM card. With an adapter, the new SIM with all of my older AT&T phones. I'm still getting no SIM detected on my xt925.
What else could be my issue? Does the AT&T SIM card have some protection that's blocking the xt925 from reading it? I am pretty sure other people are using AT&T SIM cards with xt925.
The only other data I have is that I purchased a Nokia Lumia 920 a while ago as an upgrade for a different line in my family plan, but I never activated that phone or SIM. If I take the SIM out of that phone, the xt925 reads the information fine. It reads the phone number of the line that I "upgraded."

Having serious issues connecting S6 to Macbook Pro!

Hey!
I don't know if this is a common issue or if there has been any possible resolution to this problem, but recently I tried to connect my phone to my Macbook using Android File Transfer, and it wouldn't connect to the phone, giving me the error no Android device found or something? I've used it before through AFT like a good while back though, several months, and it was very touch and go even then, sometimes connecting and most times not.
I googled for every possible solution, and even went as far as checking MTP was enabled, enabling USB debugging, uninstalling AFT and trying to use Smart Switch.... the list goes on.
The funny thing is, even Smart Switch refuses to see my phone and can't pick up a connection. I have ordered a new original S6 data cable just in case it is literally the cable but I'm actually doubting it's to do with the cable itself and more to do with either the phone or the software.
I'm not sure what else I can do at this point... is there any fix or solution to this? Other than the fact the battery life is pretty abysmal I do actually like this phone (when it behaves!) so I don't want to just end up giving up on it.
For now, I've been using Airdroid but it's only a temporary solution as I only get so much allocated data transfer on the free version (?) and I prefer just connecting a cable, selecting everything and pulling it over to a folder. Sigh.
FTR, my phone is not rooted (though I'm wondering if it might be worth doing so)

AFT doesn't work with the S6. Might do on Marshmallow if it ever happens. SideSync for Mac works. I installed an earlier version & had to disable whatever the new security feature is called. You might not need to with current version (4.2.0.15125_9).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Ah, I've not heard of this. I'll look into it! Thanks.
Would be great if Marshmallow could finally be released for the S6.. been playing this waiting game for sometime now.

zemblance said:
AFT doesn't work with the S6. Might do on Marshmallow if it ever happens. SideSync for Mac works. I installed an earlier version & had to disable whatever the new security feature is called. You might not need to with current version (4.2.0.15125_9).
Click to expand...
Click to collapse
AFT does work with the S6, but you need to have Smart Switch (and its associated drivers) completely uninstalled first.

andrewNY said:
AFT does work with the S6, but you need to have Smart Switch (and its associated drivers) completely uninstalled first.
Click to expand...
Click to collapse
I've never had smart switch installed (TBH - never heard of it till your post, this is my 1st Smasung phone) and AFT has never worked for me

zemblance said:
I've never had smart switch installed (TBH - never heard of it till your post, this is my 1st Smasung phone) and AFT has never worked for me
Click to expand...
Click to collapse
Yeah, it's not the most reliable piece of software in my experience. Even when it works, I've had it glitch out on me while transferring files (even on a officially supported phone like a Nexus).

andrewNY said:
AFT does work with the S6, but you need to have Smart Switch (and its associated drivers) completely uninstalled first.
Click to expand...
Click to collapse
zemblance said:
I've never had smart switch installed (TBH - never heard of it till your post, this is my 1st Smasung phone) and AFT has never worked for me
Click to expand...
Click to collapse
I also had problems even before trying to install Smart Switch, so I don't entirely think it could be this.. and if even Smart Switch is not working for me then I'm not sure what it's more likely to be?
andrewNY said:
Yeah, it's not the most reliable piece of software in my experience. Even when it works, I've had it glitch out on me while transferring files (even on a officially supported phone like a Nexus).
Click to expand...
Click to collapse
So there's no particular piece of software that works properly with the S6? I also had the glitching out problems originally when I managed to connect it to the S6 but when it stopped working I haven't been able to get it connected since.

Been there, done that.
Had the same issue few week earlier. Gave up on it.
I tried everything from Samsung Kies (I do know that the S6 is not supported by that software but I was desperate), Smart Switch, SideSync, AFT...the list goes on and on.
Nothing worked out for me so now I have my MacBook Air (my primary "PC" which I have with me all the time), my Sammy phone and an USB stick to transfer files between my MB and Windows PC at home and later to my phone.
It really disappoints me that Sammy is unable to make an app that works with both Mac and Windows
PS: There is no fix for this nor will ever be until Samsung figures something out (but we all know what a crap company Samsung is when dealing with their software) so yea, you should rather save your time and do something else instead of trying to fix this (dont do the same mistake I did wasting like 2 weeks on this problem).

Damn. I figured I was hoping for too much when I decided to get another Samsung phone haha. Typical. So without a PC or something there's not much I can do about it...? I love how it's been almost a year and still no fix for this kind of problem.
Thanks anyway, if this is something that can't be helped, I guess there's not much I can do :/ I also spent a good amount of time trying to get it working about a couple weeks back but nothing worked. Guess it's a lost cause for now!

[FIX] Pixel 3 QUSB_BULK_CID:xxxx_SN:xxxxxxxx

Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting this phone to work again?

aespinal said:
Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting this phone to work again?
Click to expand...
Click to collapse
if it doesnt power on then how are you connecting to the pc? i dunno about this but you might need to do some hard troubleshooting. replace the battery and if that doesnt work then you might have a bad motherboard.

droidbot1337 said:
if it doesnt power on then how are you connecting to the pc? i dunno about this but you might need to do some hard troubleshooting. replace the battery and if that doesnt work then you might have a bad motherboard.
Click to expand...
Click to collapse
I'm just connecting it through USB to my pc, I have never rooted it, it was in perfect condition, the battery was healthy, it just happened overnight.

aespinal said:
I'm just connecting it through USB to my pc, I have never rooted it, it was in perfect condition, the battery was healthy, it just happened overnight.
Click to expand...
Click to collapse
Oh.... Okay. In that case, get into recovery by pressing vol+ and powering on. If that doesn't work, then get into fastboot and see if your pc detects your device.

aespinal said:
Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting this phone to work again?
Click to expand...
Click to collapse
Interesting. I have the same problem and it started a few days back. Nothing would appear on screen, not even the charging sign if I plug it in. However, when i connect it to my PC, i get the same popup. It was a perfectly healthy phone until this. I have given it in to a repair shop here in Dubai as there's nothing much I could do with a black screen.

I have this same issue. I was able to install QFIL and the Qualcomm driver, but I can't located the firehose (.mdn of .elf?) files to complete the steps in this guide: https://forum.xda-developers.com/t/guide-how-to-return-to-stock-flash-images-with-qfil.3901510/.
Am I on the wrong track? Should I use this as an excuse to get a 4a?

averaVT said:
I have this same issue. I was able to install QFIL and the Qualcomm driver, but I can't located the firehose (.mdn of .elf?) files to complete the steps in this guide: https://forum.xda-developers.com/t/guide-how-to-return-to-stock-flash-images-with-qfil.3901510/.
Am I on the wrong track? Should I use this as an excuse to get a 4a?
Click to expand...
Click to collapse
Did this just happen to you today? I'm having the same issue. Wondering if google pushed an update or had a security breach or something that killed multiple phones.

Last night around 11pm (EST). The phone was charging, I went to unlock it and nothing, just a blank screen.

Sorry to necro this thread, but this literally just happened to me over night. Did anyone find any solutions or am I SOL?

twizted786 said:
Sorry to necro this thread, but this literally just happened to me over night. Did anyone find any solutions or am I SOL?
Click to expand...
Click to collapse
I was SOL. The 4a is nice ¯\_(ツ)_/¯

OK, this is really getting weird. My wife's phone just did the exact same thing. I've never seen anything like this so I thought it was an oddball thing, but this thread tells me otherwise. I wonder if the Pixel 3 is just a ticking time bomb or if we all did something to brick them. I know in my case, I just recently (2 weeks ago) replaced her charger with an Anker charger from Amazon. Figured maybe that could be part of the reason. Anyone else have any suspicions as to what might have caused the issue? I'm going to work on trying to bring it back to life or at the very least recover as much information from the device as possible, so if anyone's already working on that, please share with the group!

Another Pixel 3 here, same symptoms - died overnight last night, no visible signals on the device but plugging to a pc shows QUSB_BULK. Can't detect the device with adb. Attempts to power cycle don't seem to achieve anything.
As far as causes, no idea. It picked up the monthly update earlier in the week and was rebooted then. No change to the way it had been getting charged.

Same thing happened to my Pixel 3XL last night. Reached out to Google support and they said the only option was to get it repaired for $380. Ended up picking up a Pixel 5 today instead.

Wow! This has to be some kind of major update done by Google to brick people's phone like this. This happened on my POCO F1 phone after connecting to a OnePlus Dash Charger. Be careful guys just take warranty services and hope you will at least get a refund on the amount you have invested.

Oh wow this literally just happened to me today. I picked my phone up from my desk and checked my notifications, put it down and then picked it up 10 minutes later and it was completely bricked. This is what Device Manager shows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone was at 50-60%. I've tried everything. I guess next would be to let it die and see if it boots back up. I have some important data on this phone that wasn't backed up. I hope there's a fix .

Same thing happened to my Pixel 3 this morning. Everything was fine last night, woke up this morning and the phone won't turn on or reboot. Power button isn't responsive, Power button + Volume down to get into recovery mode is also not responsive. When I connect my phone to my PC I also get QUSB_BULK_CID:xxxx_SN:xxxxxxxx.
I did some searching around and it sounds like the phone might be stuck in Emergency Download Mode? Anyone have a solution on how to fix this issue?

Phone is stuck in Qualcomm's Emergency Download (EDL) mode. We need a signed, model specific "firehose" programmer to be able to restore an OS. While some manufacturers publish these files, Google does not. Unless one leaks for our specific model, Google has just destroyed our phones and rendered them useless while we slept. Don't go out and by another Google phone because they just killed your current one.
Exploiting Qualcomm EDL Programmers (1): Gaining Access & PBL Internals
Research & Exploitation of Qualcomm EDL Firehose Programmers: From PBL (Boot ROM) Extraction, Research & Analysis to Secure Boot Bypass in Nokia 6. (Part 1)
alephsecurity.com

Anyone have any luck finding the "firehose" / "mbn" file for the pixel 3? Mine crapped out a few days ago just like others described above. It had no physical damage whatsoever.

Same thing happened to my Pixel 3 this morning. Everything was fine last night, the phone won't turn on or reboot. Power button isn't responsive, Power button + Volume down to get into recovery mode is also not responsive. When I connect my phone to my PC I also get QUSB_BULK_CID:xxxx SN:xxxxxxxx.
Stuck in Emergency Download Mode? Anyone has a solution on how to fix this issue?
Anyone has the solution !! Please help !!!​

Same issue here, set it on the table and came back 15 minutes later. Black screen, QUSB_BULK_CID when attached to PC USB, and reboot into recovery attempts unsuccessful. Mine also did an OTA update within the last week.
Very frustrated but more than that... have important files and can't get them off the device. Has anyone been able to retrieve their files at least?

Phone hard bricked after new stock GPS update

Hi!
My wife woke up this morning with a bootlooping S7 (G930F). She had scheduled the new samsung GPS update to be installed tonight.
This morning the phone showed "failed to mount /efs", similar to this image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After showing this log, the phone went back to a android logo and it looped to the log/error again.
I tried booting it to download mode, but that seemed to have bricked the phone completely. It is no longer recognized by any PC, it doesn't react to any button press (or a combination thereof).
Do people have a similar problem with their S7 and the new stock update of Samsung? Any idea how to possibly fix this? Is there any data left on the device to salvage?
I was thinking of opening the back and trying to reconnect the battery, in the hope to get it recognized again by a PC.
Thanks!

Fineness5618 said:
(...)
I tried booting it to download mode, but that seemed to have bricked the phone completely. It is no longer recognized by any PC, it doesn't react to any button press (or a combination thereof).
(...)
Click to expand...
Click to collapse
Charge the battery and try again.

I'll try it without a new one first, as I'll have to buy that on aliexpress or something. However if there is nothing to salvage on the device, I don't really want to buy a new battery just to maybe get it unbricked.

i have the exact same failure with this update

I'm having the same issue. Did anyone figure this out?
Fineness5618​tight13​ze7zez​

Nope, tried to open the phone and disconnect and reconnect the battery. However this sadly didn't fix it. I'm really not sure what broke in the phone, maybe the battery or maybe another part of the thing.
I've since broken down the phone in pieces, pierced the memory chips and recycled it.
Sorry for the bad news.

Fineness5618 said:
Nope, tried to open the phone and disconnect and reconnect the battery. However this sadly didn't fix it. I'm really not sure what broke in the phone, maybe the battery or maybe another part of the thing.
I've since broken down the phone in pieces, pierced the memory chips and recycled it.
Sorry for the bad news.
Click to expand...
Click to collapse
Thanks for letting me know. I'm thinking about calling Samsung or the carrier since it seems like the GPS update broke the phone. I know they don't support the phone any longer but since they issued a update to it maybe they will help I'm also thinking about using odin to reload either the stock rom or a custom rom.

shaggy2 said:
Thanks for letting me know. I'm thinking about calling Samsung or the carrier since it seems like the GPS update broke the phone. I know they don't support the phone any longer but since they issued a update to it maybe they will help I'm also thinking about using odin to reload either the stock rom or a custom rom.
Click to expand...
Click to collapse
Good luck! It sure seems to be Samsungs fault so you can definitely try that route.
In my case I wasnt even able to use Odin so I hope you can get it working with your device.

Fineness5618 said:
Good luck! It sure seems to be Samsungs fault so you can definitely try that route.
In my case I wasnt even able to use Odin so I hope you can get it working with your device.
Click to expand...
Click to collapse
If it didn't work for you it probably won't work for me. I found this link in a reddit thread for the same issue. The person who shared it said it shows the same issue at the beginning of the video. Video seems to be how to fix it.
https://www.reddit.com/r/GalaxyS7/comments/wsclmm/_/il6ivrm

shaggy2 said:
If it didn't work for you it probably won't work for me. I found this link in a reddit thread for the same issue. The person who shared it said it shows the same issue at the beginning of the video. Video seems to be how to fix it.
https://www.reddit.com/r/GalaxyS7/comments/wsclmm/_/il6ivrm
Click to expand...
Click to collapse
Yeah found that too. Didn't work for me sadly.

shaggy2 said:
If it didn't work for you it probably won't work for me. I found this link in a reddit thread for the same issue. The person who shared it said it shows the same issue at the beginning of the video. Video seems to be how to fix it.
https://www.reddit.com/r/GalaxyS7/comments/wsclmm/_/il6ivrm
Click to expand...
Click to collapse
Same issue with my S5 or similar. Final software update kills the phone.

Is this related to Lineage on the phones, or are you talking about bricked phones with original stock ROM?

FRQD75 said:
Is this related to Lineage on the phones, or are you talking about bricked phones with original stock ROM?
Click to expand...
Click to collapse
literally says stock in the thread name

Fineness5618 said:
Hi!
My wife woke up this morning with a bootlooping S7 (G930F). She had scheduled the new samsung GPS update to be installed tonight.
This morning the phone showed "failed to mount /efs", similar to this image:
After showing this log, the phone went back to a android logo and it looped to the log/error again.
I tried booting it to download mode, but that seemed to have bricked the phone completely. It is no longer recognized by any PC, it doesn't react to any button press (or a combination thereof).
Do people have a similar problem with their S7 and the new stock update of Samsung? Any idea how to possibly fix this? Is there any data left on the device to salvage?
I was thinking of opening the back and trying to reconnect the battery, in the hope to get it recognized again by a PC.
Thanks!
Click to expand...
Click to collapse
try leaving it to charge while in recovery as kernel is loaded there and handles charging.
after device is somewhat charged download full latest firmware from samfw.com and try flashing it with odin if device gets recognized, use csc and not home csc to format data

Ok, so LOS does not use the part of the Stock ROM for GPS?
I thought, GPS, NFC, etc... are "recycled" from the original SW