Database Info

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!

How To Guide EDL test points and blank-flash boost mobile

Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
{
"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"
}

*Update*
Thank you @vache and all at Motorola Blankflash (telegram) for everything
. . . . Only for this specific release
XT2131-1_DENVER_BOOST_11_RRES31.Q3-60-47-2-2-2_subsidy-BOOST_DISH_regulatory-DEFAULT_cid50_CFC
1. Decompress "blankflash_file".zip
2. Short the edl test points. while holding the "tweezers" on the 2 test points plug the device into PC.
3. After you see the device connected , or hear the connected sound , release the "tweezers" from the test points.
4. Run blank-flash.bat/.sh (choose which one depending on what os you have on your PC.)
!!WARNING!!
DO NOT turn off!! DO NOT unplug!!
5. Wait for device to reboot to fastboot mode. (if your Denver/Osaka does not reboot to the bootloader then you do not have the correct blank flash file)
6. Flash the stock firmware to your device (flash with lmsa, tiny-fastboot-script, platform-tools or cli. it's up to you)
Now your device should be working again. I HOPE this small bit of information helps you out as much as it helped me.
For the love of Moto!
Guide by @sosthenisRR aka sosRR (yeah like the flying kind )

This did work on my mine which I bricked a month ago. I was able to run the bat file on my windows PC so it said "Waiting for devices", short the pins, plug in my usb cable and then wait a minute or 2 for it to boot into fastboot. Then I ran the lenovo recovery tool and flash it back to life.

duffman452001 said:
This did work on my mine which I bricked a month ago. I was able to run the bat file on my windows PC so it said "Waiting for devices", short the pins, plug in my usb cable and then wait a minute or 2 for it to boot into fastboot. Then I ran the lenovo recovery tool and flash it back to life.
Click to expand...
Click to collapse
Yeah it did work with me too he is the greatest.

Thank you so much it did work with me LOVE..

Hmmm..
So I tried this method about a week ago BUT I didn't see this post then and I used a blanlflask from lolinet...it didn't turn out good. It began just fine, but it only flashed the first item, it seemed like it was flashing the partition scheme and it concluded, ending with
"Finished." then said rebooting to fastboot but the screen went black...and stayed black. I can only get a blink from charging led if I hold down power long enough....might this file be worth a shot? I can still get into EDL. Appreciate any advice?

I have a terrible situation at hand thanks to Motorola really screwing me, hard, in regards to a Repair. Long story short, I went from having a moto One 5G Ace to being sent a VERY used, worn, older and completely different model device. Motorola has some balls, let me tell ya. Anyways, the device does not boot and it is not bootloader unlocked. I received it and immediately called Motorola Repair/Tech Support within about 20-30 minutes of it being delivered to me; they tell me to send it in for repair in it's original box. I won't mention how they kept the original box, claiming to have thrown it away because it had a hand-written note on a white sticker on the side that clearly indicated this was a "loaner" device...oh wait, I mentioned it. Anyways, I can't unlock the bootloader, because OEM Unlock was not open in Developer Settings. I also can't boot, flash, or load anything. LMSA recognizes the device as the XT2131-1 and downloads the appropriate firmware. It begins the rescue, but at 32% it fails, rebooting the phone to the "NO VALID OS FOUND" black/red screen and LMSA states something like "We're sorry, but it's unsafe to rescue this device at this time."
I've tried multiple Windows machines, Windows 8, 10 and Windows 11 hosts. I've tried MX Linux, Linux Mint, Ubuntu, etc., but I can't get anything to flash/rescue. I then found this page and, at first, still couldn't reach blankflash. However, here we are two-three months later and with a friend's help I am able to get into EDL. I ran this blankflash, which is the ONLY blankflash that actually recognized the device, but it finishes and simply reboots back to the Bootloader screen. I'm afraid maybe I unplugged it too quickly. Is there any advice that anyone has about what I could be doing wrong? Or what I should try? Any opinions on the BEST Linux/Windows OS to use for things like this? Thanks, in advance, to everyone and anyone reading this, if you have any pointers, please do help me out. Motorola really screwed me but I've filed complaints appropriately about that-in the meantime though it'd be nice to have a phone again after almost 6 months of not having one at all...I keep refraining from buying a different device on principal...and things have been so tight for me, financially, this year. So any help I would greatly, greatly appreciate!
Thank you,
Clint

csann said:
I have a terrible situation at hand thanks to Motorola really screwing me, hard, in regards to a Repair. Long story short, I went from having a moto One 5G Ace to being sent a VERY used, worn, older and completely different model device. Motorola has some balls, let me tell ya. Anyways, the device does not boot and it is not bootloader unlocked. I received it and immediately called Motorola Repair/Tech Support within about 20-30 minutes of it being delivered to me; they tell me to send it in for repair in it's original box. I won't mention how they kept the original box, claiming to have thrown it away because it had a hand-written note on a white sticker on the side that clearly indicated this was a "loaner" device...oh wait, I mentioned it. Anyways, I can't unlock the bootloader, because OEM Unlock was not open in Developer Settings. I also can't boot, flash, or load anything. LMSA recognizes the device as the XT2131-1 and downloads the appropriate firmware. It begins the rescue, but at 32% it fails, rebooting the phone to the "NO VALID OS FOUND" black/red screen and LMSA states something like "We're sorry, but it's unsafe to rescue this device at this time."
I've tried multiple Windows machines, Windows 8, 10 and Windows 11 hosts. I've tried MX Linux, Linux Mint, Ubuntu, etc., but I can't get anything to flash/rescue. I then found this page and, at first, still couldn't reach blankflash. However, here we are two-three months later and with a friend's help I am able to get into EDL. I ran this blankflash, which is the ONLY blankflash that actually recognized the device, but it finishes and simply reboots back to the Bootloader screen. I'm afraid maybe I unplugged it too quickly. Is there any advice that anyone has about what I could be doing wrong? Or what I should try? Any opinions on the BEST Linux/Windows OS to use for things like this? Thanks, in advance, to everyone and anyone reading this, if you have any pointers, please do help me out. Motorola really screwed me but I've filed complaints appropriately about that-in the meantime though it'd be nice to have a phone again after almost 6 months of not having one at all...I keep refraining from buying a different device on principal...and things have been so tight for me, financially, this year. So any help I would greatly, greatly appreciate!
Thank you,
Clint
Click to expand...
Click to collapse
Motorola Blankflash
Request blankflash by giving device informations
t.me
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Start from scratch but remember need to use the last firmware that was on the phone when you choose a blankflash file

Hello. I have been able to get this tool to work with my own specific flash file for an XT2131-1 RETUS. When I boot the flash file, it still shows that the bootloader is locked. Is there any way too boot into fastboot with a blankflash file and make sure that it is unlocked?

Please help I have model xt2163dl and can't find the test points. Please help

Kireej said:
Please help I have model xt2163dl and can't find the test points.
Click to expand...
Click to collapse
You may have to find them yourself.
A voltmeter can help. You need one point that measures 1.8V (voltage source) and another that's close to 0V (GPIO).
If you have a resistor (maybe 470 ohms to 2.2k) you can connect things together without worrying too much about vaporizing anything.
That's a low enough resistrance for the GPIO for EDL boot.

Renate said:
You may have to find them yourself.
A voltmeter can help. You need one point that measures 1.8V (voltage source) and another that's close to 0V (GPIO).
If you have a resistor (maybe 470 ohms to 2.2k) you can connect things together without worrying too much about vaporizing anything.
That's a low enough resistrance for the GPIO for EDL boot.
Click to expand...
Click to collapse
Not sure of what any of that means. I can't find anything on Google or anywhere else. Seems as if someone here has to have the same model as me. The waiting game begins lol.

Renate said:
You may have to find them yourself.
A voltmeter can help. You need one point that measures 1.8V (voltage source) and another that's close to 0V (GPIO).
If you have a resistor (maybe 470 ohms to 2.2k) you can connect things together without worrying too much about vaporizing anything.
That's a low enough resistrance for the GPIO for EDL boot.
Click to expand...
Click to collapse
Ok I got a voltmeter but not sure how to use it. Here is the meter and the phone.

Oops, my apologies.
The original post was talking about the XT2131 (which is Qualcomm SDM480) and EDL.
The XT2163DL is a Mediatek Helio G25,
There are similarities, but also differences.
I can say with high confidence that Qualcomm EDL is (always?) using a 1.8V voltage source and a GPIO with a pull-down resistor.
I don't really know what Mediatek is doing. Assuredly no voltage is over 1.8V but I don't know if it's pull-up or pull-down,
In any case, I would still look for conspicuously adjacent test points where one measures 1.8V and one near zero.
I would still not want to connect random things together without checking and without a resistor.
The absolute worse would be hitting a test point for a backlight (which could be as high as 30+V).
Some Mediatek things show BROM and Preloader when they boot up anyway.
Are you sure that you're not seeing them?
Good luck

Renate said:
Oops, my apologies.
The original post was talking about the XT2131 (which is Qualcomm SDM480) and EDL.
The XT2163DL is a Mediatek Helio G25,
There are similarities, but also differences.
I can say with high confidence that Qualcomm EDL is (always?) using a 1.8V voltage source and a GPIO with a pull-down resistor.
I don't really know what Mediatek is doing. Assuredly no voltage is over 1.8V but I don't know if it's pull-up or pull-down,
In any case, I would still look for conspicuously adjacent test points where one measures 1.8V and one near zero.
I would still not want to connect random things together without checking and without a resistor.
The absolute worse would be hitting a test point for a backlight (which could be as high as 30+V).
Some Mediatek things show BROM and Preloader when they boot up anyway.
Are you sure that you're not seeing them?
Good luck
Click to expand...
Click to collapse
Yes all I get when I plug the phone in is a whitesh blue led light blinking on the top right corner. If I hold vol+ or vol- and power it will stop blinking for a minute then start again. Computer will not recognize the device and I am completely unable to get into fastboot to flash stock firmware. This all started when I accidentally flash firmware from a different year.

If you're on Windows, you should count the "bongs" when your device boots.
My usblog.exe can be helpful in identifying things that pop up.
My enumusb.exe can show what has ever popped up on your Windows.
Both can be found here.
Code:
C:\>enumusb /l /v0e8d
0E8D:2000 7&279c4dc7&2&6 2023-02-08 04:14 MT65xx Preloader
0E8D:201C 1483GR123456789 2023-02-08 04:14 Port_#0006.Hub_#0005
0e8d is Mediatek

Ok fount the points then I run the flash blank boot script then it says this after I let go of tweazers

Renate said:
If you're on Windows, you should count the "bongs" when your device boots.
My usblog.exe can be helpful in identifying things that pop up.
My enu
musb.exe can show what has ever popped up on your Windows.
Both can be found here.
Code:
C:\>enumusb /l /v0e8d
0E8D:2000 7&279c4dc7&2&6 2023-02-08 04:14 MT65xx Preloader
0E8D:201C 1483GR123456789 2023-02-08 04:14 Port_#0006.Hub_#0005
0e8d is Mediatek
Click to expand...
Click to collapse
Thank you I got usblog to work but the other opens then closes. Also I'm not quite sure what to do with this information. It shows up as an unknown USB device and as soon as I take the tweazers off it disconnects from computer. The blank flash exe never detects the device.

0000/0002 is often a USB gadget under Linux that is not initialized at all.

Renate said:
0000/0002 is often a USB gadget under Linux that is not initialized at all.
Click to expand...
Click to collapse
Any idea at all of how to get this thing unbricked? Test points is where I keep ending up but again as soon as I let go of tweazers it disconnects.

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?

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