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 !

I keep getting an error when trying to copy to sc card

every time I try to copy pictures, or anything actually, to my sd card on my nexus 5, I'm getting this error. it completely stops the file copy and I have to physically disconnect my phone and reconnect it to try again. I'm at a loss of what to try to get this to work. I need to get the files copied to my phone but this is making it absolutely impossible.
{
"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"
}

phab3k said:
every time I try to copy pictures, or anything actually, to my sd card on my nexus 5, I'm getting this error. it completely stops the file copy and I have to physically disconnect my phone and reconnect it to try again. I'm at a loss of what to try to get this to work. I need to get the files copied to my phone but this is making it absolutely impossible.
Click to expand...
Click to collapse
Try installing these usb drivers http://img.media.xda-developers.com/images/XDA2013/header/xdaLogo.png and see if that works.

gee2012 said:
Try installing these usb drivers http://img.media.xda-developers.com/images/XDA2013/header/xdaLogo.png and see if that works.
Click to expand...
Click to collapse
I'm just seeing a link to the xda logo

phab3k said:
I'm just seeing a link to the xda logo
Click to expand...
Click to collapse
Sorry http://forum.xda-developers.com/showthread.php?t=1514942.

gee2012 said:
Sorry http://forum.xda-developers.com/showthread.php?t=1514942.
Click to expand...
Click to collapse
i've tried those, and when I use that, I only get adb, I can't access it through my computer.

I get the same error trying to copy files from PC

Interesting.
I also got errors during transferring some photos across last night.
I ended up disconnecting, setting the USB connection method to the "camera" one (forget the names), this seemed to transfer the files fine. Then i needed to do some music, so disconnected and switched back to other usb method, and seemed to transfer fine after that!
MIght have to keep an eye on it!

Have you tried clearing media storage data and cache?

I have also been receiving this error when trying to drag all my photos from my mac to the N5. My previous phone was an S3 so I dragged them all to my mac and attempted to drag them to the N5.
I was partially successful but after every photo dump, I would restart the phone and that allowed me to get about half my files on the phone. Took much longer than expected. I am going to attempt to get the other half on tonight

I zipped up all my files and copied across the zip file and then unzipped them on the phone, and that worked a treat
Sent from my Nexus 5 using XDA Premium 4 mobile app

I have the exact same problem...not possible to transfer all my old files from N4 to N5. constant crashes which always need reconnecting USB..pissing me off...

Stylez Ray. said:
I have the exact same problem...not possible to transfer all my old files from N4 to N5. constant crashes which always need reconnecting USB..pissing me off...
Click to expand...
Click to collapse
I'm still having the problem as well. I'm glad it's not just me though. I wonder if google has been alerted to the issue yet.

phab3k said:
I'm still having the problem as well. I'm glad it's not just me though. I wonder if google has been alerted to the issue yet.
Click to expand...
Click to collapse
I'm honestly kind of pissed how there are ALWAYS issues. Nexus 4 had issues, pretty big ones, and now so does the Nexus 5. Like they really didn't test if the goddamn thing would be able to transfer files with a computer? I don't understand what the deal is with them.

BravoMotorola said:
I'm honestly kind of pissed how there are ALWAYS issues. Nexus 4 had issues, pretty big ones, and now so does the Nexus 5. Like they really didn't test if the goddamn thing would be able to transfer files with a computer? I don't understand what the deal is with them.
Click to expand...
Click to collapse
agreed, and I did call google tonight, they were unable to offer any sort of help. the girl on the phone sounded like it was her first day, and as someone who worked in tech support for 8 years, I sure as hell know how a fresh agent sounds. she kept trying to get me to just use google+, which I had to reply that I know I can do that, but that isn't solving the problem, she didn't seem to get it. I might call in again and see what I can find. she said she was submitting it as a bug though and that other people have been calling in about it.

I was trying to bulk copy media from pc to N5 and was getting explorer crashes on my pc
I then tried it via AirDroid and it all worked perfectly
I freaking HATE MTP
Sent from my Nexus 5 using xda app-developers app

But you guys have to realize we can't be ok with using other software or apps to transfer files! Really this is pissing me off, such an easy task as using USB to transfer files HAS to work! I hope someone finds a solution or knows what the problem is.
I tried some drivers, uninstalled and cleaned them but no success...I don't even know what causes this. Sometimes I transfer many files for like 5 minutes and it crashes, sometimes it happens just after 3 or 4 files...doesn't matter if photo or music or which kind of file, it is a random pattern.
Please don't wipe data of media storage as it kills all your ringtones!
Imagine all those Apple boys wouldn't be able to use the cable to transfer their files to the macbook! No one would say : just use an app for that...sorry!

Stylez Ray. said:
Imagine all those Apple boys wouldn't be able to use the cable to transfer their files to the macbook! No one would say : just use an app for that...sorry!
Click to expand...
Click to collapse
so go buy an iphone
the point is, if you don't like the way something works, you have the options...use them!

oh come on...are you kidding? please think about your sentence "if you don't like the way something works"...you want to say the phone isn't meant to be used with an usb cable? are you freakin kidding me? you really can't be serious! they bundle a cable and you seriously want to tell me it's not designed to work that way?????
This is my 24th smartphone I owned and transferring files was never an issue, and as this is a basic operation one does almost every day it should just work!

yes it should, i agree with you ..I wish it were plain old usb storage
I tried MTP maybe 3 times when I got the N4 year ago and it sucked, so I stopped using it
stop banging your head against a wall and use an alternative method
Sent from my Nexus 5 using xda app-developers app

called google play support again today and the person I spoke to was another airhead. what is up with their support line basically not being able to help at all?

[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

note 20 android 13 0 B storage Bug

Hi all
I updated my note 20 ultra 5g from 12 to 13 by OTA PDA: N986BXXS5GVK9 and working fine but when I wake up morning while my device charged I found it 0 B storage so I restart my device and memory again normal. This practice am doing daily without any improvement.
If I go into the Settings > Storage section, all I see are 0 B everywhere. Calls, and receiving & sending messages in WhatsApp/SMs app works fine too. All apps that needs to store on internal user storage can't do it because its not there.
I did some actions like below:
I disabled the 4GB of extra RAM.
I cleared applications cache by ccleaner.
in the apps section in settings, 3 dots top right, special access and activate access to all media storage.
I am attaching some images if they can be of any help to anyone.
still issue not solved and I don’t want to reset format my device
regards
{
"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"
}

That last image is showing -1B available storage.
Try clearing the system cache on the boot menu. Otherwise you're headed for a factory reset. Make sure all critical data is redundantly backed up... now.
Lol, Android the 13th

blackhawk said:
That last image is showing -1B available storage.
Try clearing the system cache on the boot menu. Otherwise you're headed for a factory reset. Make sure all critical data is redundantly backed up... now.
Lol, Android the 13th
Click to expand...
Click to collapse
thanks a lot
but these pictures not mine but same my issue 0 B.
i tried yesterday to off my device and push power & + volume tell Samsung display appear but i cant find recovery and device start normal

the dreamer said:
thanks a lot
but these pictures not mine but same my issue 0 B.
i tried yesterday to off my device and push power & + volume tell Samsung display appear but i cant find recovery and device start normal
Click to expand...
Click to collapse
You need to have a usb cable plugged in to get to recovery. Can't remember when they changed this .....

dvhttn said:
You need to have a usb cable plugged in to get to recovery. Can't remember when they changed this .....
Click to expand...
Click to collapse
Samsung's a mess. It's not like that on the N10+ Android 9/10. I think it's hardware mod rather than firmware?
Lol, I forgot abut that because I don't have to do it. Guess some fools were pocket factory resetting. Can't have that

yesterday i wiped cash & repair apps by connecting USB cable to my laptop by recover mode and working ok
but
today early morning 2:30AM i used my devise and found it -1 B like the picture so i did wipe cash again and waiting today if again memory storage lost or not

the dreamer said:
yesterday i wiped cash & repair apps by connecting USB cable to my laptop by recover mode and working ok
but
today early morning 2:30AM i used my devise and found it -1 B like the picture so i did wipe cash again and waiting today if again memory storage lost or not
Click to expand...
Click to collapse
Yeah, that's not acceptable behavior.
Dismount and remove SD card. See if that helps.
If you're stateside take it to a Samsung Experience center at a Best buy. They have advanced diagnostics, allegedly.
Factory reset. This could be malware. Reload with care, keep the trashware like WhatsApp off it. Bare bones load at first and then gradually add more apps. Social media apps are malware and should never be installed; login by browser only if you must visit them. This saves your battery and decreases your exposure.
If all that fails reflash firmware to last known good version ie older than is on it preferably. This is another reason I don't upgrade/update firmware; less variables and you can spot odd behavior faster . A known playing field makes troubleshooting much easier. Troubleshooting new firmware can be very time consuming*...
That last possibility is a hardware failure. However I still think the most likely suspect is a 3rd party app. If you do a reload lockdown all updates for all apps. Do a few or one at a time over the course of days. Keep a log*.
*this can get bloody. Consider using more advanced tools to find the app or process responsible for the behavior. I never had to do this with Android but you may need to. With Windows I did it more than once.

blackhawk said:
Yeah, that's not acceptable behavior.
Dismount and remove SD card. See if that helps.
If you're stateside take it to a Samsung Experience center at a Best buy. They have advanced diagnostics, allegedly.
Factory reset. This could be malware. Reload with care, keep the trashware like WhatsApp off it. Bare bones load at first and then gradually add more apps. Social media apps are malware and should never be installed; login by browser only if you must visit them. This saves your battery and decreases your exposure.
If all that fails reflash firmware to last known good version ie older than is on it preferably. This is another reason I don't upgrade/update firmware; less variables and you can spot odd behavior faster . A known playing field makes troubleshooting much easier. Troubleshooting new firmware can be very time consuming*...
That last possibility is a hardware failure. However I still think the most likely suspect is a 3rd party app. If you do a reload lockdown all updates for all apps. Do a few or one at a time over the course of days. Keep a log*.
*this can get bloody. Consider using more advanced tools to find the app or process responsible for the behavior. I never had to do this with Android but you may need to. With Windows I did it more than once.
Click to expand...
Click to collapse
thanks a lot for support
since my last wipe for cash my note working fine and no issue for memory tell now

the dreamer said:
thanks a lot for support
since my last wipe for cash my note working fine and no issue for memory tell now
Click to expand...
Click to collapse
Did you try to clear the davlik cach in recovery mode sometimes it help to refresh it

next_1989 said:
Did you try to clear the davlik cach in recovery mode sometimes it help to refresh it
Click to expand...
Click to collapse
i don't remember if i saw this option or no
but i did 2 steps only
wipe catch
&
repair apps
working fine tell now

Sometimes it happens like this because of flashing wrong pit files or after you remove frp or change the system files so the best way to make sure is do s backup with switch on your pc and flash the stock rom and restore your backup and check again

Try it and let me know

next_1989 said:
Sometimes it happens like this because of flashing wrong pit files or after you remove frp or change the system files so the best way to make sure is do s backup with switch on your pc and flash the stock rom and restore your backup and check again
Click to expand...
Click to collapse
why should i flash my device while its working fine

the dreamer said:
why should i flash my device while its working fine
Click to expand...
Click to collapse
If its working fine then dont flash sir