Hi all
First, let me say I've read everything I could find on data recovery of a broken S6, and tried all the data recovery software I could find (Dr.Fone, Easus, etc.). Nothing has worked which is why I'm asking here.
Background: my daughter dropped her S6 down a flight of stairs. The screen is well and truly broken. There is no light behind the back and recent buttons. There is no noise. When she gave it to me there was a pulsing pale blue light.
But, it's not completely dead. When plugged into my PC it's recognised by various drivers (Samsung ADB, USB composite device).
I tried Dr.Fone and after a number of attempts got it to be recognized as being in download mode. Unfortunately, it fails with "Flash recovery package failed."
I tried using adb directly. adb devices showed it as being in recovery mode, so I used abd shell and I could do ls, but I'm not a savy adb user so don't know what to do next.
All the threads I've seen end up recommending recovery software, which hasn't worked for me, so if anyone can tell me if it's possible to recover data using adb I'd really appreciate knowing what commands to use.
Thanks
afzal_b said:
Hi all
First, let me say I've read everything I could find on data recovery of a broken S6, and tried all the data recovery software I could find (Dr.Fone, Easus, etc.). Nothing has worked which is why I'm asking here.
Background: my daughter dropped her S6 down a flight of stairs. The screen is well and truly broken. There is no light behind the back and recent buttons. There is no noise. When she gave it to me there was a pulsing pale blue light.
But, it's not completely dead. When plugged into my PC it's recognised by various drivers (Samsung ADB, USB composite device).
I tried Dr.Fone and after a number of attempts got it to be recognized as being in download mode. Unfortunately, it fails with "Flash recovery package failed."
I tried using adb directly. adb devices showed it as being in recovery mode, so I used abd shell and I could do ls, but I'm not a savy adb user so don't know what to do next.
All the threads I've seen end up recommending recovery software, which hasn't worked for me, so if anyone can tell me if it's possible to recover data using adb I'd really appreciate knowing what commands to use.
Thanks
Click to expand...
Click to collapse
*bump* Anyone?
afzal_b said:
*bump* Anyone?
Click to expand...
Click to collapse
Have you rooted your Samsung S6 G920F? Some third-party tool can recover data from broken Samsung Galaxy S6 920F but need root access.
Send your phone to be fixed in customer service central.
Related
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
MrAwesome75 said:
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
Click to expand...
Click to collapse
ya but i havent even tried loading a file into odin cause it wont see my device
and i have installed the samsung drivers but after this happened my pc wont see the phone
has to be a way to get a connection between the pc and phone
I'm not an expert so I'm not sure. Do you have the correct drivers installed on PC?
---------- Post added at 06:34 AM ---------- Previous post was at 06:30 AM ----------
Try different Odin versions. And make sure you have the proper drivers installed on the PC.
ya ive actually read that it probably doesnt have the function running to talk with the pc cause it cant boot. im all set up to reset the phoone. just need it to appear in my odin
..does kies still work?
[email protected] said:
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
Click to expand...
Click to collapse
When you boot to system
It doesn't show anything right ??
but the touch is still functioning
Sent from my GT-i9300 running cm11 using tapatalk.
when i just boot it goes to download mode and says "could not do do normal boot"
i can access recovery mode and download mode but i cant get drivers to show it, and it used to show it until i did this, can i put a file on my micro SDcard from my pc via card reader then install it in recovery mode ? like firmware or a memory wipe reset?
If you can get into recovery, I believe that would be possible. Couldn't hurt to try. As long as you can get into recovery and all the recovery functions work, I don't see why you couldn't.
fixed it!
well after two nights of reading i got my pc to discover the device by changing ports three different times to find one that seamed to like it. and also installed kies and installed the drivers from them, (figured couldnt go wrong after as many as ive used from samsung and others). so win7 pro / altered boot command and only stock options afterwards sucks big time. ty all for helping me
never let up
Hey everyone. I couldn't find an answer to this that I could follow and that worked for me as I'm not very technically inclined.
My HTC One X recently died after having a low battery and now whenever I try to turn it on (even when it is fully charged), it gets to the lock screen, but I can only access everything for about 5 seconds before it restarts again. I know I have USB debugging enabled, and I can get to the screen that shows up when I hold down the power button and the volume-down button.
What I want to do, before doing a factory reset and praying that ends the bootloop, is recover my photos which I stupidly did not back up anywhere. I can connect my phone to my laptop, which runs on Windows 8, but it is not recognized as it normally would be (ie: I can't access files directly). I've gotten to the point where I can see "FASTBOOT USB" on my phone when it is connected and I've restarted my PC so that it is able to identify it in the Device Manager. I have also gone through the steps of downloading a universal naked driver and choosing the driver under the Device Manager, so when I use a command prompt my phone shows up in fastboot devices. (I used minimal fastboot and ADB)
But what can I do now? I have never tampered with my phone, so it is locked or unrooted. I'd like to keep it that way if possible, but I'm having a hard time understanding how I can retrieve my photos. Should I use ADB commands, and if so, how do I get to the point where my PC recognizes my phone under ADB devices? Or is there a better way? I'm also not very familiar with custom roms, TWRP, CWM, etc.
I'd appreciate a brief walk-through if possible as, like I said, I don't normally do this sort of thing. Thank you!
thepenrosesteps said:
Hey everyone. I couldn't find an answer to this that I could follow and that worked for me as I'm not very technically inclined.
My HTC One X recently died after having a low battery and now whenever I try to turn it on (even when it is fully charged), it gets to the lock screen, but I can only access everything for about 5 seconds before it restarts again. I know I have USB debugging enabled, and I can get to the screen that shows up when I hold down the power button and the volume-down button.
What I want to do, before doing a factory reset and praying that ends the bootloop, is recover my photos which I stupidly did not back up anywhere. I can connect my phone to my laptop, which runs on Windows 8, but it is not recognized as it normally would be (ie: I can't access files directly). I've gotten to the point where I can see "FASTBOOT USB" on my phone when it is connected and I've restarted my PC so that it is able to identify it in the Device Manager. I have also gone through the steps of downloading a universal naked driver and choosing the driver under the Device Manager, so when I use a command prompt my phone shows up in fastboot devices. (I used minimal fastboot and ADB)
But what can I do now? I have never tampered with my phone, so it is locked or unrooted. I'd like to keep it that way if possible, but I'm having a hard time understanding how I can retrieve my photos. Should I use ADB commands, and if so, how do I get to the point where my PC recognizes my phone under ADB devices? Or is there a better way? I'm also not very familiar with custom roms, TWRP, CWM, etc.
I'd appreciate a brief walk-through if possible as, like I said, I don't normally do this sort of thing. Thank you!
Click to expand...
Click to collapse
Try Power the Device Up in Safe Mode - HTC One®
Do you know the model number? Is it the AT&T or Rogers? s720e, G23, 720, 325...
sd_shadow said:
Try Power the Device Up in Safe Mode[/URL] - HTC One®
Do you know the model number? Is it the AT&T or Rogers? s720e, G23, 720, 325...
Click to expand...
Click to collapse
I tried going into safe mode and nothing changed! It didn't break the bootloop, so I guess it isn't an app that's causing the problem. It's with Rogers, but I don't know the model number... I got it in North America if that helps.
thepenrosesteps said:
I tried going into safe mode and nothing changed! It didn't break the bootloop, so I guess it isn't an app that's causing the problem. It's with Rogers, but I don't know the model number... I got it in North America if that helps.
Click to expand...
Click to collapse
It's likely a s720e then, but
I will request that this thread be moved to AT&T One X Q&A, Help & Troubleshooting
Where you should be able to find out for sure.
Next step is likely flashing a custom recovery like TWRP or CWM then you could, mount sd card/storage and copy photos.
see AT&T One X Q&A, Help & Troubleshooting Frequently Asked Questions by Heisenberg
[INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up (Updated 5/8/14) by redpoint73
Edit: It seemed as it solved itself, look in the replies for details
So i have had my gs7 rooted for a year or longer. Yesterday i rebooted my phone and got the error message "Custom binary blocked by FRP lock". Sadly, when i enter download mode and plug it into a pc with odin installed, it is not recognised. Odin does not say anything about a phone plugged in, and windows says the usb is not recognized.
What i think have caused this:
I downloaded an app that allowed me to record internal audio
I turned off developer options, and my stupid ass did not realize that is where oem unlock is located.
What i have tried:
Resetting to factory settings (from recovery mode)
Deleting cache (from recovery mode)
Using odin, but odin does not even recognize my phone
Tried using another computer with odin
tbh, looking at the other posts, i think i messed up. I dont want to send it in for repairing because i will have to pay a lot of money. I have tried sending it in for repairing a while ago. Then my problem was that i could not call with it, but they wanted me to pay the price for a new phone to repair my old phone, since i had rooted it. I did not accept it so i got my phone back, and managed to fix the issue myself. I hope i manage to fix the issue this time aswell.
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
cooltt said:
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
Click to expand...
Click to collapse
I have samsung usb drivers installed, and download mode has always been working and has always been recognized by odin ever since this happened. And online all i find is that i should boot into download mode and try using odin, but odin does not recognize my phone, nor does my computer.
10krlan said:
I have samsung usb drivers installed, and download mode has always been working and has always been recognized by odin ever since this happened. And online all i find is that i should boot into download mode and try using odin, but odin does not recognize my phone, nor does my computer.
Click to expand...
Click to collapse
Please pay attention to guides when messing about with your phone, OEM and Debugg are critical to being able to modify.
Look here for a solution.
https://www.mobikin.com/android-backup/computer-does-not-recognize-android-phone.html
cooltt said:
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
Click to expand...
Click to collapse
SOLVED!
The issue fixed itself, im not sure what i did. I was suddenly able to connect my phone to odin. Just incase someone reads this with the same problem. This is what i did: installed smart switch and rebooted my computer. Uninstalled and reinstalled samsung usb drivers.
Before i did those things the issue was still there, i was ready to use smart switch, but i tried odin one last time and it worked. Now samsung pass tells me my phone is rooted, even though it is not (my root dissapeared after resetting my phone), its not that big of an issue, just thought id let you know
Hi everyone,
A couple of days ago I rooted my Op6 and then decide to flash No limits rom via recovery (blu spark), as I was used to do with my last android phone, the Samsung Galaxy Note II.
Unfortunately I missed something and now it is stuck in the bootloader screen. Nothing works from the phone and I couldn’t revive it. I use a Mac but I tried all tools that are adviced here on XDA with my friend’s Sony Vaio but without success.
I managed to update drivers but I cannot run a flash-all.bat and I cannot use MSMdownload tool.
How can I do? Thanks to anyone who will manage to help me!!
EDIT: Sorry, just noticed you say you cant use the MSM tool. This one worked for me.
You could try this
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
Worked for me.
Check the guide about unbricking and if You are unable to use flash-all.bat so you Have to flash commands One by One. It's worked for me a few of months ago.
It doesn’t work either that way. I updated my drivers, but no computer is recognizing the phone.
I tried from changing usb cable or port to changing computer, to change methods.
I didn’t found any solution here on XDA, I tried everything!!
Make sure u use the cable included with the phone. Some cables doesn't work
Neither. I tried with the original and two others that I have.
if possible do you have windows? the flash-all.bat works for windows and is better to use(i was unable to use it normally in linux). What happens when you show flash.bat?
I tried Mac and Windows. On Windows it always shows in terminal "waiting for any device", even if I uploaded the drivers and made everything possible.
Did you put your OP6 into fastboot mode in correct way? I mean you might be doing the wrong procedure when entering fastboot mode.
It happened to me for the first time, I came from Samsung and I thought the phone needs to be stayed on the fastboot menu screen just like Samsung but no.
You need to turn it off and reboot it while pressing home and vol down button simultaneously until the PC recognize.
Good luck unbricking~
I always powered it on via power+volume up before connecting to the usb cable, because connecting it while powered off always resulted to power it on automatically on bootloader screen
Hi,
Yes, I know, there's a million topics about this and I'm pretty sure I tried them all!
Long story short: been running Lineage OS on my Tab 2 for a while but it's been sitting in a drawer. Saw a video about using old tablets for emulating retro consoles and the Tab works a dream for that. So I bought a Bluetooth controller for better gameplay but it just wouldn't work under Lineage so thought I'd flash the original ROM back onto it to see if that would work. I'm not a n00b, but haven't done it for a while so thought to be safe I'd follow a guide. All seemed to be working well when Odin crashed and left me with the Firmware Upgrade Failed error.
I've been trying for about four hours to get it back, but having no luck. I've tried the latest version of Odin, as well as the old 1.7 version I was using; tried Kies, tried uninstalling Kies; tried uninstalling the stock drivers MS installed when connected, no go. Interestingly Odin doesn't seem to see the Tab at all now, so I tried the UniversalADB installer, tried installing ADB drivers as well as Samsung drivers manually, but nothing works, it just sits at "connecting" but never actually does. Also tried different stock ROMs to no avail. I think my issue is with the ADB drivers, just don't know how to fix it.
I don't know what to try now. Any advice?
Using MS Surface Pro (2017) running Win10.
Not allowed to post screenshots, but do have some.
Thanks.
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Tab_Triggerhappy said:
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Click to expand...
Click to collapse
Hi,
Thanks for your reply and sorry it's taken me so long to respond; I've got several health issues I have to work around!
I can't get into the OS at all, it's just stuck at the "Firmware upgrade..." screen and there's nothing else I can do with it.
It was rooted and I was running TWRP recovery, but can't access it at all now. I did a wipe in TWRP but was still able to boot into it before I ran Odin. Odin worked fine, then it just stopped for reasons unknown and now there's nothing I can do with the Tab at all.
I see this in Device Manager: samsung mobile usb cdc composite device. Have tried manually installing driver but nothing seems to work.
Have tried it on my Mum's Win7 machine, but to no avail. I really need ADB drivers but I can't install them without turning on debugging on the Tab and I can't do that because I can't get out of this blasted error screen!
There's literally nothing else I can say about it as this is all that's happening.
Annnnd, now it doesn't seem to want to hold a charge. :crying:
Thanks again.
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Tabby22020 said:
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Click to expand...
Click to collapse
Maybe a longshot, but you can test if this free version can access the tab:
https://www.tenorshare.com/products/reiboot-for-android.html
No use buying if it can't.
But since Device Manager sees something it's worth a shot.
Do you have to longpress power button to turn it off?
If so... when the screen goes off, have you tried to quickly let go of the power button and immediately press it again together with Volume Up?
Or down, for download instead of Recovery.
With my P3100 it was much easier with no charger plugged in...
Edit:
Tried the software and my tab is OK, but no connection established anyway. Only result was that I couldn't access tab in File Explorer and MTP state... only PTP.
In Device Manager I got a new Android Device: Something like Google Nexus ADB... sorry but I uninstalled it directly without noting exact name.
Replugged USB cable and MTP working again.