ROM stock
Recovery TWRP
Hi all,
I would recover data from an s6 with broken lcd.
First time i connected it to pc via usb, it was recognized in recovery mode by adb.
I tried to access data with adb shell but no contents found in folder "data". I tought "no root permission?!"
So I installed TWRP recovery via Odin. Now, when i connect it to pc it's not recognized anymore by adb "no devices attached". I just can view "Samsung Mobile USB Composite Device" under device manager in windows and an error about MTP driver installation.
How I can determine in which boot mode is the telephone?
Could you suggest me a way to try to recover data, if present?
Thanks in advance.
additional info:
when i connect the phone to the pc trough usb, it takes about 15s being recognized by windows. next windows try to install MTP driver and it fails.
In Odin it appears "added" but if I try to flash a recovery it stucks on "setup connection"
Hey guys, in a little bit of a dilemma.
My s6, for some reason, cannot pass the flashing "Samsung" logo when booting it up. I have not rooted this phone, nor have I installed a custom recovery or rom. This phone is stock as it gets.
And I need to recover the photos off the phone. Issue is, I thought it would be simple as going into recovery mode and doing adb pull/sdcard/DCIM/Camera or something like that.
BUT I do not have USB debugging enabled!!! Never even turned on developer settings.
I tried to get into bootloader and use fastboot, but fastboot devices shows up with nothing. adb commands do not work, except when I press "install update from ADB", then only the very basic ADB commands work such as adb reboot, adb sideload etc.
So I am not sure what to do from here. Fastboot is not working (I have installed the Samsung drivers from the official webpage, but I haven't restarted my computer so i will try that).
Please help me to recover these photos :crying::crying::crying:
Hi,
If Download mode is working, flash TWRP recovery with Odin.
Go to Mount, select Data partition > Enable MTP and access files from PC.
Recover your data, then flash fresh new ROM https://forum.xda-developers.com/galaxy-s6/general/guide-tutorial-howto-samsung-galaxy-s6-t4108425
My phone is running perfectly fine. But after updating my phone last week officially, my PC doesn't recognize the phone in Fastboot. I'm trying to flash a custom recovery and root it, but in CMD, when I type fastboot devices, nothing comes up.
I am in the Fastboot mode when I try to do this. My phone was rooted earlier too with no issues. Also, in the Fastboot mode, The Bootloader version and the baseband version is blank. I tried different ports and a different cable along with a different PC, nothing seems to help.
Any suggestions?
Hi, did you ever get an answer?
I am having this exact same problem as well. Computer isn't recognizing the device as a fastboot device, I can't even run the fastboot boot recovery.img command to get into recovery.
I was able to get it to recognize my phone in fastboot mode by following the directions in this post: https://forum.xda-developers.com/t/...nize-device-but-adb-can.4040635/post-84052027
Though I never was able to root or install TWRP, this did allow my computer to recognize the phone in fastboot mode.
Hello,
My screen is broken, but the phone is working. I can boot and I feel the phone working and recognising my finger to unlock. However, because I'm stupid and I didn't have the "USB debugging ON" I can't access my files via ADB or via any recovery software.
However, I can boot on fastboot and I see my device on "fastboot devides". Can I do something to access my files from there? I don't know... maybe unlock bootloader and flash any kind of TRWP with full adb or something like that.
THanks ¡
You can try QC fire flash tool wherein from EDL (emergency download, You can go to YouTube for EDL flashing) you should be able to flash custom recovery (I recommend Orangefox recovery 11.1). If you are able to flash the custom recovery you can boot into the recovery and get data via USB to your PC. Remember only to flash Recovery.img and not other IMG files
I have access to fastboot and EDL mode. Does this mean that I can also access the mode that will show the phone after the adb devices command?
If device gets booted into FASTBOOT or EDL mode then it can't additionally get accessed via ADB: this can only get achieved when device got booted into RECOVERY mode.
To clarify:
ADB ( short for Android Debug Bridge ) deals - as its name implies - with a device's Android OS.
FASTBOOT deals - as its name implies - with device's bootloader, if that isn't bricked.
EDL ( short for Emergency Download Mode ) - specific to devices with a Qualcomm Snapdragon chipset - deals with the device itself, is used if bootloader is bricked.
Thank you for your quick help. Is it possible to access adb during bootloop?
I entered something called recovery mode, but the computer doesn't recognize that any device has been connected - adb devices doesn't see anything either.
On one of the pages I read this information:
Spoiler
Ed Reynolds says:
December 2, 2018 at 4:31 am
Unfortunately, there really is no “recovery” per set, yet. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a simpler form of phone. There are no options to go into bootloader or Fastboot mode. ADB won’t get you there. Sometimes, using ADB, you can boot into a simple android recovery with no command! There you remain until hard booting back it back into full functionality. Developer is apparently working on it
Reply
Deepak Gupta says:
December 2, 2018 at 4:38 am
Hi Ed Reynolds,
Thanks for sharing your knowledge. We appreciate your efforts. Yes, stock recovery doesn’t offer many options. One has to install a custom recovery like TWRP to get over this problem and to maximize productivity.
Reply
Ed Reynolds says:
December 8, 2018 at 7:48 pm
That is correct. but, in order to install a custom recovery, one must be able to get into bootloader, in some way. Either through physical buttons or through the ADB tool. forget about using the physical buttons – they get you to the recovery that you mention, but cannot get you into Fastboot (bootloader) mode. If you use the ADB tools while in this particular recovery mode, and try to reboot into bootloader mode from there, it boots back into the system. So, using that route, you cannot ever get to a place where you can install TWRP or anything else, for that matter – including applying an unlocking code if one were available. Next, if you try to get into recovery mode using the ADB tools (not the physical buttons, you do arrive at a more “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this problem before and sometimes, using the physical buttons, you can reveal commands at this stage. However, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, you use the ADB tools to boot into bootloader mode, you return to the system! The result is, again, you cannot install any sort of custom recovery because there is no internal or external way to flash it. If you have overcome this problem, please share! It is very frustrating! Thanks. Ed
Does this mean that I will need to flash custom recovery to gain access via adb during bootloop?
Android's Recovery is nothing else than a minimalistic working Android OS, comparable to Windows Recovery Environment ( WinRE ), so it's accessible via ADB.
A Custom Recovery ( like TWRP ) isn't needed at all, because such a only is an UI version operable by touches.
So if Windows don't see device when is in recovery mode (but recognize correctly when is in fastboot mode), there is a problem with drivers?
I want to access to adb pull for backup. Device is rooted with unlocked bootloader and allowed USB debugging and no PIN password, but bootlooped after trying to restart after uninstalling YouTube app
OMG
when in Recovery mode then you've to connect device via USB-cable with computer and you can launch adb pull command on computer.
When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list
Then obviously USB Debugging didn't get enabled in Android's Developer Options.
Robert997 said:
When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list
Click to expand...
Click to collapse
As the other user said, USB Debugging is not enabled or proper drivers are not installed. The drivers for fastboot and adb are different. Search for correct drivers, disable driver signing in Windows and install the drivers.