Database Info

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?

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?

Pixel 4a Not Charging after Beta update

Hi everyone,
I have a Pixel 4a that I recently bought and a couple of weeks ago I decided to try the new Android 13Beta version so I opt-in and I updated via OTG. However, after a couple of days, all of a sudden my phone stopped charging and since the phone's charge was less than 15% it didn't let me reset the phone or opt-out and get back to stable Android 12.
Now the phone is dead. I tried everything but it doesn't charge.
For the first couple of days, when I plugged in the charger, the battery icon appeared on the screen and then it showed 0% and then the icon again and 0% again and looped for over well 8 hours but didn't charge.
Now it even doesn't show the icon or the percentage.
Does anyone experience the same problem? or can anyone help me with this, please?

I've rebuilt many pixel 4a's ,, If u have adb on your puter the first place I go when there is no power is to the android flash tool just to see if there is any reaction when I hook it up, if not I break it open unplug the battery let it sit then reconnect , , you would not believe how many I revived just by doing that. But I realize everyone can't do that, when you have it hooked up to the aft hold the power button and volume down button and see if you get a reaction

hammered58 said:
I've rebuilt many pixel 4a's ,, If u have adb on your puter the first place I go when there is no power is to the android flash tool just to see if there is any reaction when I hook it up, if not I break it open unplug the battery let it sit then reconnect , , you would not believe how many I revived just by doing that. But I realize everyone can't do that, when you have it hooked up to the aft hold the power button and volume down button and see if you get a reaction
Click to expand...
Click to collapse
Thank you for your reply but as you said, unfortunately, I don't have access to flash tools and stuff like that.
I live in Turkey and since it's not a popular phone over here I believe I can't find a repair shop that has such a tool either.

GreatMimir said:
Thank you for your reply but as you said, unfortunately, I don't have access to flash tools and stuff like that.
I live in Turkey and since it's not a popular phone over here I believe I can't find a repair shop that has such a tool either.
Click to expand...
Click to collapse
Ok ,, But I would try different cables , different chargers , just to make sure,,, even if they worked before

hammered58 said:
Ok ,, But I would try different cables , different chargers , just to make sure,,, even if they worked before
Click to expand...
Click to collapse
I already did but unfortunately no luck there

after trying some methods now I managed to enter the recovery mode and everything but when I want to factory reset from recovery mode it shows this error, it doesn't even mount the system
I also can't opt-out or downgrade via system update because it doesn't charge and it says the battery level is too low.
{
"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"
}

GreatMimir said:
after trying some methods now I managed to enter the recovery mode and everything but when I want to factory reset from recovery mode it shows this error, it doesn't even mount the system
I also can't opt-out or downgrade via system update because it doesn't charge and it says the battery level is too low.
View attachment 5685913
Click to expand...
Click to collapse
I just wonder if the otg didn't damage or dirty your charging port, maybe try cleaning with some compressed air or maybe insert a toothpick or something small enough and non conductive to clean out the port or maybe there's a bent pin ??

If you're uncertain if it's a hardware or a software issue yet, I would actually suggest you do what @hammered58 suggested about physically cleaning the USB port.
Just a few weeks ago I noticed that after plugging in the type-c cable that Google provided, I had to fiddle with it so that the phone would recognize it. Tried with different cables and chargers as well, but the issue still persisted.
I think I used a paper clip to sort of "scratch" inside the port.

Lada333 said:
If you're uncertain if it's a hardware or a software issue yet, I would actually suggest you do what @hammered58 suggested about physically cleaning the USB port.
Just a few weeks ago I noticed that after plugging in the type-c cable that Google provided, I had to fiddle with it so that the phone would recognize it. Tried with different cables and chargers as well, but the issue still persisted.
I think I used a paper clip to sort of "scratch" inside the port.
Click to expand...
Click to collapse
Thank you for your suggestion to be honest I did, I even tried to clean the inside but there's no luck on that front

GreatMimir said:
Thank you for your suggestion to be honest I did, I even tried to clean the inside but there's no luck on that front
Click to expand...
Click to collapse
I bought a 4a from a guy that said he had his wireless dongle plug into his charging port and that he drop it sticking the dongle dead center on the floor, he said since then it quit charging,, when I opened it to repair I found not only the charging port loose on the mb but it also had bent a couple of pins, after reattaching a straighting its been working

hammered58 said:
I bought a 4a from a guy that said he had his wireless dongle plug into his charging port and that he drop it sticking the dongle dead center on the floor, he said since then it quit charging,, when I opened it to repair I found not only the charging port loose on the mb but it also had bent a couple of pins, after reattaching a straighting its been working
Click to expand...
Click to collapse
Plus, AFAIK, there are no wireless charging "adapters" for the 4a that actually do work?

GreatMimir said:
Thank you for your suggestion to be honest I did, I even tried to clean the inside but there's no luck on that front
Click to expand...
Click to collapse
Have you tried using the Android Flash Tool to completely reset your device?
If that doesn't solve your issue, I think it's safe to say that you have a hardware fault.

(Edit: Deleted due to l accidentally post it in a wrong post)

Zoranix7232 said:
Thank you so much! This works really great on my SM-T580 and SM-P585Y! The only glitch l could find is that when l slide the brightness bar to the darkest the screen just go completely dark, it's like the screen is turned off (this only occur in my SM-P585Y though). l hope you'll fix this in the future.
Click to expand...
Click to collapse
Wrong thread, friend

Oh sorry l was about to post this in a thread for LineageOS for my devices. Didn't know how it went here. Sorry!

Lada333 said:
Have you tried using the Android Flash Tool to completely reset your device?
If that doesn't solve your issue, I think it's safe to say that you have a hardware fault.
Click to expand...
Click to collapse
Unfortunately I can't because it's dead and it doesn't charge at all

GreatMimir said:
it doesn't charge at all
Click to expand...
Click to collapse
Yup, sorry, I'm an idiot.
GreatMimir said:
For the first couple of days, when I plugged in the charger, the battery icon appeared on the screen and then it showed 0% and then the icon again and 0% again and looped for over well 8 hours but didn't charge.
Click to expand...
Click to collapse
This still makes me think it's a software issue, as the phone clearly detected that it's connected to a charger.
I'm not sure if you've done anything like this, but maybe give it a shot?
"
Step 2: If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
How to Disable Driver Signature Verification on 64-Bit Windows 8 or 10 (So That You Can Install Unsigned Drivers)
64-bit versions of Windows 10 and 8 include a “driver signature enforcement” feature. They’ll only load drivers that have been signed by Microsoft. To install less-than-official drivers, old unsigned drivers, or drivers you’re developing yourself, you’ll need to disable driver signature enforcement.
www.howtogeek.com
Step 3: Press the power button for 40 seconds to turn off the phone.
Step 4: Press the volume up button for 10 seconds, while connecting the device with the computer.
Step 5: Open your device-manager and make sure in "Unknown devices" is one device with the name "QHUSB_BULK".
"
Do keep in mind that this guide was written for a totally different device and for a totally different issue.
What I'm trying to get at is maybe if you manage to boot the device into this.. debug mode (?), it will bypass whatever software lock is preventing you from charging it. Again, this mode might not even be a thing for the 4a, or might not help at all. It just came to mind, curious to see if it can be of any help.

Lada333 said:
Yup, sorry, I'm an idiot.
This still makes me think it's a software issue, as the phone clearly detected that it's connected to a charger.
I'm not sure if you've done anything like this, but maybe give it a shot?
"
Step 2: If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
How to Disable Driver Signature Verification on 64-Bit Windows 8 or 10 (So That You Can Install Unsigned Drivers)
64-bit versions of Windows 10 and 8 include a “driver signature enforcement” feature. They’ll only load drivers that have been signed by Microsoft. To install less-than-official drivers, old unsigned drivers, or drivers you’re developing yourself, you’ll need to disable driver signature enforcement.
www.howtogeek.com
Step 3: Press the power button for 40 seconds to turn off the phone.
Step 4: Press the volume up button for 10 seconds, while connecting the device with the computer.
Step 5: Open your device-manager and make sure in "Unknown devices" is one device with the name "QHUSB_BULK".
"
Do keep in mind that this guide was written for a totally different device and for a totally different issue.
What I'm trying to get at is maybe if you manage to boot the device into this.. debug mode (?), it will bypass whatever software lock is preventing you from charging it. Again, this mode might not even be a thing for the 4a, or might not help at all. It just came to mind, curious to see if it can be of any help.
Click to expand...
Click to collapse
Thank you so much,
Since I couldn't do anything to revive the phone, I had to send the phone back to Germany (where I bought the phone) so I would be able to file a repair request.
I'll let you guys know what was the exact problem when I get a detailed assessment of the issue from Google

GreatMimir said:
Thank you so much,
Since I couldn't do anything to revive the phone, I had to send the phone back to Germany (where I bought the phone) so I would be able to file a repair request.
I'll let you guys know what was the exact problem when I get a detailed assessment of the issue from Google
Click to expand...
Click to collapse
Aww, man, I wish I'd thought of this sooner.
Was your device still under warranty?
Absolutely be sure to update us when you get the info from Google.

Hi, Is it resolved? How much they charged for the repair? I am facing the same issue after my phone updated to Android 13.

Dead android phone data recovery - What are my options?

Hi everyone,
This is the setup:
Phone: Samsung S4 mini (GT-i9195)
OS: Lineage OS (can't remember the version, but I guess 17.1 or 18.1)
Recovery: TWRP (can't remember which version)
After I had a phone call I put the phone on the table. Some minutes later when I came back the app switcher and back button backlight was on, but there was no reaction when I touched the screen or any other buttons. Removing and returning battery had no impact, as well as using the charger.
I noticed when I connected it to my Windows PC via USB cable, I hear the windows sound for connecting and some seconds later the sound for disconecting.
When pressing the phones power button for 10 seconds while connected to pc, I hear sound for disconnecting and a moment later the sound for connecting. In any case I can't see the device on my PC as it would normally be the case.
Before, when the phone was working I had a working setup for scrcpy, with ADB debugging activated, but this doesn't seem to work as well, so my noobish guess is that the phone does not load Lineage OS at all.
So here I am at the end of my knowledge and I want to ask here, what are my option in order to recover my data (all on phones memory, not SD card)?
Thanks so much for any help!

Sounds like a hardware failure, if so if you can correct the problem... maybe a connector making poor contact. If it's the mobo you're boned.
Is the battery known good?
Always use the SD card as a data drive; all critical data goes there. Then redundantly backup the SD card to at least two hdds that are physically and electronically isolated from each other and the PC. Otherwise this can happen again.

Thank you very much @blackhawk for your answer and the attempt to help!
blackhawk said:
Is the battery known good?
Click to expand...
Click to collapse
Yes, battery is OK
blackhawk said:
If it's the mobo you're boned.
Click to expand...
Click to collapse
really, there is no way to get data from the internal chip?
wouldn't it maybe be possible to unsolder the chip and put it in a working s4 mini?
blackhawk said:
Always use the SD card as a data drive; all critical data goes there. Then redundantly backup the SD card to at least two hdds that are physically and electronically isolated from each other and the PC. Otherwise this can happen again.
Click to expand...
Click to collapse
Yes, you're absolutely right. For long time I want to have a setup exactly as you have described. I started with it, but unfortunatley not everything was set to be synced with my NAS. Most of the stuff is on external SD, but some is not. With some apps you even have the issue that can't use external SD and which force you to use the onboard memory, like for example Signal does.

The chipset is likely a BGA form factor, all the solder pads are underneath it. You need use a hot air station and have the skillset to use it.
It would then need to be reflowed onto the donor board. Some overseas houses might do it relatively cheaply. Not a common practice except by data recovery $pecialists.
The SD card should contain no running apps as it's bandwidth is limited. Apps that allow backup there like ColorNote can be auto backed up though.

Step one: When a crippled device makes a "bong" when connected to a PC, find out what it is.
Is it the bootloader, charger, fastboot, ADB, MTP or who knows what?
I find usblog.exe helpful. See: http://www.temblast.com/windows.htm
If you're on Linux, just do lsusb -v when it bongs.

Renate said:
Step one: When a crippled device makes a "bong" when connected to a PC, find out what it is.
Is it the bootloader, charger, fastboot, ADB, MTP or who knows what?
I find usblog.exe helpful. See: http://www.temblast.com/windows.htm
If you're on Linux, just do lsusb -v when it bongs.
Click to expand...
Click to collapse
Thank you @Renate , good tip!
When phone without battery gets connected to PC, this is what usblog 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"
}
But what does it tell me now? How exactly can I find out in what state my phone currently is?
Next I wil try to get some linux running and see what lsusb -v shows me.

blackhawk said:
The chipset is likely a BGA form factor, all the solder pads are underneath it. You need use a hot air station and have the skillset to use it.
It would then need to be reflowed onto the donor board. Some overseas houses might do it relatively cheaply. Not a common practice except by data recovery $pecialists.
Click to expand...
Click to collapse
Looks to me like an acceptable solution if I can't get it any other way and really want to get the data.

Oh, this is an older device. You may have a chance. Do you think that /data is encrypted?
Right now you have the silly VCOM driver installed. I'm prejudiced against them. You'll still be able to reinstall it if this doesn't work.
Get Zadig https://zadig.akeo.ie/ and install the WinUsb driver on 05c6/9008
Get edl.exe from my sig.
Code:
C:\>edl.exe /lhello
Copy the output (minus the serial number if you care) and paste it here.
If it gives you can't read/can't write, do a LONG power press until it bongs and try again.
That slash-ell-hello is just something to get it moving. Next you'll use slash-ell-loader-with-a-serious-name.

Thanks again for your guidance @Renate !
I deinstalled the COM driver, installed WinUsb driver and run edl.exe as you have explained. Unfortunately it seems I always get:
Found EDL 9008
Could not read device
even if I do the LOOong power press until bong-move.
What does this mean and what options do I have left?

That's strange. It's possible that you have a recalcitrant device.
I put some motivation in the code.
Go and download the new version of edl.exe
Make sure you have the new one, 136,704 bytes.
MD5 028533aaec778cc0c1357525a7bf503c

Thanks for the new version, but the output is unfortunatley not much different to before:
Code:
Found EDL 9008
Resetting Sahara
Could not read device
Eventually worth mentioning: I have a second Samsung S4 mini (with broken display). If I connect it to my PC, I get the connecting-bang, if I then run edl with your parameter the output is always:
Code:
Could not find EDL device

I think that this is so old it's using a different protocol.
Maybe you should check out https://github.com/bkerler/edl which is the "standard" EDL client.
(I was so frustrated with this Python version that I wrote my own native Windows version, YMMV.)
On your 2nd device it's probably in fastboot mode or something or even ADB.
That's why you should run usblog.exe on it.
A broken screen is not a big deal, you can view the screen even without installing any software.
Try adbgrab.exe It's much slower than scrcopy or something, but it works on (most) anything.

I looked to see if that unit supports Sahara. I found this thread: https://forum.xda-developers.com/t/...-pc-as-qualcomm-hs-usb-qdloader-9008.3508606/
Maybe you should try getting your 2nd unit in EDL? If it connects then you know there is a problem with your 1st unit.
Maybe Samsung intentionally crippled EDL for security reasons?