I think my s6 is almost dead. Yesterday, I hiked in the rain and the screen started malfunctioning. Today the only thing I can get it to do is odin download mode. I flashed twrp so that still works, but I can't seem to boot to twrp.
Is there any way I can retrieve files, specifically the pictures from yesterday, while in download mode? Adb doesn't work. Just hoping for some way.
Ok, I have been able to get booted to TWRP, but adb doesn't connect from there, with device not being found?
H0wdy said:
Ok, I have been able to get booted to TWRP, but adb doesn't connect from there, with device not being found?
Click to expand...
Click to collapse
From within TWRP, can you try going to Mount and then Enable MTP? See if this enables your computer to see the phone. You may have to toggle Enable MTP on and off a few times.
If you can get this working, use TWRP to make a full backup and copy that to your PC.
koop1955 said:
From within TWRP, can you try going to Mount and then Enable MTP? See if this enables your computer to see the phone. You may have to toggle Enable MTP on and off a few times.
If you can get this working, use TWRP to make a full backup and copy that to your PC.[/QUOTE
I wasn't able to before, but I will keep trying.
Click to expand...
Click to collapse
Related
Howdy y'all,
So I was rooting and flashing and when I tried to flash after successfully rooting the device, I went to wipe everything in TWRP and then flash another ROM. Well, something happened and it gave me an error saying it could not wipe (I think it was OTG something something, it's been 2 weeks now since I did this), and now it won't allow me to transfer ANYTHING from the computer to the device. It will not allow me to create folders, nothing. I have uninstalled the drivers, installed the drivers and tried SO many drivers. Anyone able to provide me a suggestion? The odd thing is on the device itself, I can create folders and everything, but when it connects, eventually, I can open the device from my computer, BUT when I attempt to create a folder, the PC gives me an error dialog saying that the device is not there anymore.
Any help would be greatly appreciated!
Thanks!
kassem277 said:
Howdy y'all,
So I was rooting and flashing and when I tried to flash after successfully rooting the device, I went to wipe everything in TWRP and then flash another ROM. Well, something happened and it gave me an error saying it could not wipe (I think it was OTG something something, it's been 2 weeks now since I did this), and now it won't allow me to transfer ANYTHING from the computer to the device. It will not allow me to create folders, nothing. I have uninstalled the drivers, installed the drivers and tried SO many drivers. Anyone able to provide me a suggestion? The odd thing is on the device itself, I can create folders and everything, but when it connects, eventually, I can open the device from my computer, BUT when I attempt to create a folder, the PC gives me an error dialog saying that the device is not there anymore.
Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Have you tried using ADB push to get a new rom onto the device? Also I'd do a permission repair
Edit: As a side note, I don't think it's possible that you did actual damage to your device. It's probably just the software that's messed up. If you want a sure way to fix it, try downloading and flashing the stock factory image.
Funzo22 said:
Have you tried using ADB push to get a new rom onto the device? Also I'd do a permission repair
Edit: As a side note, I don't think it's possible that you did actual damage to your device. It's probably just the software that's messed up. If you want a sure way to fix it, try downloading and flashing the stock factory image.
Click to expand...
Click to collapse
Thanks so much for the reply. I just finished doing a complete stock re-image of the original bootloader and OS, but I'm still getting the same error message. I'll attach an image below of the error I keep getting.
Any more suggestions?
kassem277 said:
Thanks so much for the reply. I just finished doing a complete stock re-image of the original bootloader and OS, but I'm still getting the same error message. I'll attach an image below of the error I keep getting.
Any more suggestions?
Click to expand...
Click to collapse
Is it possible for you to try with a different computer?
Funzo22 said:
Is it possible for you to try with a different computer?
Click to expand...
Click to collapse
Unfortunately no and not for a very long time. Shoot.
kassem277 said:
Thanks so much for the reply. I just finished doing a complete stock re-image of the original bootloader and OS, but I'm still getting the same error message. I'll attach an image below of the error I keep getting.
Any more suggestions?
Click to expand...
Click to collapse
Have you done a wipe data factory reset?
It wasn't clear from what you described.
Bootloadeer wouldn't help and neither would ROM as this problem has to do with /data
sfhub said:
Have you done a wipe data factory reset?
It wasn't clear from what you described.
Bootloadeer wouldn't help and neither would ROM as this problem has to do with /data
Click to expand...
Click to collapse
Sorry about the lack of clarity. I have wiped multiple times, cleared all caches, dalvik, etc. I have installed and uninstalled ALL devices from USBDeview pertinent to anything ADB or android related.
kassem277 said:
Sorry about the lack of clarity. I have wiped multiple times, cleared all caches, dalvik, etc. I have installed and uninstalled ALL devices from USBDeview pertinent to anything ADB or android related.
Click to expand...
Click to collapse
Have you rebooted your PC?
Have you reconfirmed you are using mtp rather than ptp?
Does your /sdcard show more directories than dcim and pictures when viewed in adb shell?
sfhub said:
Have you rebooted your PC?
Have you reconfirmed you are using mtp rather than ptp?
Does your /sdcard show more directories than dcim and pictures when viewed in adb shell?
Click to expand...
Click to collapse
I have rebooted multiple times
I am in debugging mode as well as in ptp mode and my sdcard shows that I do have many folders there, however in my computer it is only showing DCIM and pictures.
kassem277 said:
I am in debugging mode as well as in ptp mode and my sdcard shows that I do have many folders there, however in my computer it is only showing DCIM and pictures.
Click to expand...
Click to collapse
That's your problem right there. PTP mode is camera mode, so you only get access to a couple of directories. Switch to MTP mode (menu under Settings / Storage).
tni.andro said:
That's your problem right there. PTP mode is camera mode, so you only get access to a couple of directories. Switch to MTP mode (menu under Settings / Storage).
Click to expand...
Click to collapse
I've tried MTP mode before and I get nothing. In fact the computer doesn't recognize the tablet is there. It's odd b/c I have done EVERYTHING I can think of and read about to install drivers (multiple kinds, like PDA, android, RAW, etc) and uninstall drivers. It sounds like a driver issue but I don't think it is.
EDIT: ok so after switching to MTP mode on the tablet, I went to device manager and uninstalled the "portable ADP drivers" as some people were saying they had issues that were similar to mine (but not exactly) here (http://forum.xda-developers.com/showthread.php?t=2380978&page=1).
After doing so, I unplugged and re-plugged the N7 back in and had it re-install the drivers from the Google USB drivers that I downloaded onto my desktop. That allowed me to get it to work and access the internal SD card on the device. BUT, when I go back into the PTP mode (camera) mode, I still have the same issue where I cannot creat subdirectories, transfer anything to the device AND I cannot see any directories except for DCIM and pictures. Really weird. Both modes obviously worked before I rooted it. Now that I have unrooted and gone back to bare bone stock I am still not getting it to work.
kassem277 said:
BUT, when I go back into the PTP mode (camera) mode, I still have the same issue where I cannot creat subdirectories, transfer anything to the device AND I cannot see any directories except for DCIM and pictures. Really weird. Both modes obviously worked before I rooted it. Now that I have unrooted and gone back to bare bone stock I am still not getting it to work.
Click to expand...
Click to collapse
That is how ptp mode is supposed to work.
That is why people prefer mtp mode.
kassem277 said:
BUT, when I go back into the PTP mode (camera) mode, I still have the same issue where I cannot creat subdirectories, transfer anything to the device AND I cannot see any directories except for DCIM and pictures.
Click to expand...
Click to collapse
Like I said, that's what you get in PTP mode. You are able to write to those 2 directories though (not the root directory).
Really weird. Both modes obviously worked before I rooted it. Now that I have unrooted and gone back to bare bone stock I am still not getting it to work.
Click to expand...
Click to collapse
No way. PTP mode is restricted on purpose. Here is the commit:
https://android.googlesource.com/pl...er/+/1e950b8090d90bbf92e528a974ecb8c5c48dff84
Thanks guys. I appreciate all the continued help and patience. Now that I went back and thought about it, I was only transferring images WHEN it was working before. It is all good now that my silly drivers were all sorted out. Really odd how the drivers just took a crap on me like that. Weird. All is well now though and I can get back to studying my PDF's for school.
Thanks again y'all!
Thanks guys. I appreciate all the continued help and patience. Now that I went back and thought about it, I was only transferring images WHEN it was working before. It is all good now that my silly drivers were all sorted out. Really odd how the drivers just took a crap on me like that. Weird. All is well now though and I can get back to studying my PDF's for school.
Thanks again y'all!
Sad day today.. dropped my S6 Edge and the result was a shattered front screen. I can't use any of the touch function, but the phone does appear to work partially ( I still get email alerts on my connect android wear).
I wanted to perform an adb backup , I'm able to connect the phone to my computer, however, when I give the :
adb backup -all -f C:\backup.ab command, it wants me to unlock the device and confirm the backup operation.
I tried unlocking with my fingerprint but it's not working. I can't see anything on screen, other than a flashing light.
Any other suggestions how to backup/ transfer data from phone? sadly kies no longer works which would have worked...
Thanks for all help in advance.
That sucks big time. Turn the phone off, put the phone in download mode and issue the commands that way. This will by pass the phone asking you to unlock it.. See if that works for you.
grneyez said:
That sucks big time. Turn the phone off, put the phone in download mode and issue the commands that way. This will by pass the phone asking you to unlock it.. See if that works for you.
Click to expand...
Click to collapse
I just tried that. When I give the adb backup command screen reads: "waiting for adb Mode" and does not seem to progress. when I loaded odin it does seem to recognize phone ready to go so the connection is live.
any other suggestions?
Are you rooted? If so, do you have developer options checked?
S6 edges is not rooted. Developers options was enabled previously since I had used Helium for date transfer from my older S5 to edge.
Not sure why you can't ADB in download mode. Wish I could of been more helpful.. Maybe someone else will be able to help.
grneyez said:
Not sure why you can't ADB in download mode. Wish I could of been more helpful.. Maybe someone else will be able to help.
Click to expand...
Click to collapse
So I rooted my phone even though the screen is cracked. I tried everything I could think of, not much to lose anymore.
I can still access the adb , shell, but still having same issue.
I tried the pull command but I get an error after screen starts creating a list " No such file or directory"
Any more suggestions?
Can anyone please assist to get data off an S3 which sticks at the blue-backed throbbing SAMSUNG splash screen just after the android rocket take-off.
The history is that the phone started constant-rebooting and I left it off for a few weeks. Then I took it into a shop to get the power switch replaced and the repairer noticed that it no longer reboots, it just sticks at that SAMSUNG screen. When neither of us could get it into safe mode, he diagnosed that it was "definitely" a software problem. Resetting caches from recovery mode doesn't do anything and as I am trying to get data off it, I am a bit reluctant to follow other solutions I have found here and do a master reset!
I THINK this device is rooted (with towelroot)? See below
I can get to an Odin screen and can get the device recognised on the computer and wondered if I could do resets from there with one of the 4 files included with 3.07. Curiously enough one of them did succeed (though the success was too quick to convince me it had actually flashed very much) and the device did reboot but still got stuck at the same splash screen! Taking the battery out and restarting/cleaning caches again etc didn't help and now, none of the Odin files will 'flash' successfully, which is why I am not sure if I am still rooted or if something is returned to stock. I am just not sure which file or what exactly flashed successfully and what it did to the ROM, bootloader, CID, etc etc etc. SO I am assuming that if I can still load Odin and get the S3 recognised, it is still rooted.
Is there anything else I can try either through odin or independently to get me into the os please? I have loaded skipsoft and run it and it has connected to the S3 (and changed things) just by connecting to the computer in download mode: But I can't see where in skipsoft I can diagnose or correct whatever is wrong
Flash TWRP via Odin, boot into TWRP, mount data partition, connect the phone to a computer, and try to copy the phone's data to the computer.
What that guy said ^^^ Install a new OS for your system which should replace your old one. You don't need to boot TWRP if you are going to boot a new OS. My method involves you losing all your data so you have been warned. You can get the stable version for that here http://techbeasts.com/update-t-mobi...o-android-4-3-jelly-bean-t999uvuemjc-guide/2/. Good luck
Thanks for that guys but I have apparently already loaded Philz and it SAYS it has backed up the data and/or storage to sc card and I am wondering if Ican restore it to a new Galaxy J7. I especially need to figure out if I can restore telephone text messages from the S3 onto the J7 but i could make do for the moment with knowing whether such messages have made their way onto the SD card.
Yes, I am a bit reluctant to do a full wipe and restore until I can figure this out.
Or if I can access the files through my computer as you suggest, what file / format would they be in?
If you used Philz to create a backup, I don't think you'll be able to restore the data to the J7, but I could be wrong because Philz hasnt been updated for a long time which means there may be no Philz for the J7.
Philz can only be restored with Philz and possibly cwm.
I got Philz installed through Skipsoft but am wondering whether there is any newer utility I can install over whatever Skipsoft has put there? Or is that what TWRP is?
I am a bit reluctant to install anything through TWRP if it is going to not only overwrite the OS but also delete all the data I am trying to access! But is there any utility which might conceivably get my phone working again without deleting all my data please?
If I load T999UVUEMJC_T999TMBEMJC_TMB,md5 through Odin, will it delete all my data??
Flashing twrp should not over write the rom, only the recovery.
Was the phone recognized as a removable when it was booted into philz?
audit13 said:
Flashing twrp should not over write the rom, only the recovery.
Was the phone recognized as a removable when it was booted into philz?
Click to expand...
Click to collapse
Why did you ask me that? 'cos I was pretty sure it was recognised but checked again and it isn't recognised by the computer at all when I plug it in (and obviously isn't recognised by Odin)
Philz shows as Touch 6.26.6 and ClockworkMod v 6.0.4.8
Why would I ask? Because twrp can mount the phone as a removable drive to copy off the data as you wanted to do in your original post.
audit13 said:
Why would I ask? Because twrp can mount the phone as a removable drive to copy off the data as you wanted to do in your original post.
Click to expand...
Click to collapse
Sorry to harp but are we agreed generally that there is no way of getting this phone working again, - whether with some utility or by re-flashing the stock or some new ROM?
Once the phone starts hanging at that third throbbing SAMSUNG screen, is it effectively dead save only for the purposes of getting data off it as a media device please? I really need to access my text messages and couldn't even identify them on a file directory and wouldn't know what format they were in if I could access the file browser. That was sorta a last resort but I am now downloading T999UVUEMJC_T999TMBEMJC_TMB for installation through Odin? Or for installation through Philz if I can get the file onto the SD card.
Did you try twrp and use a otg usb?
It really depends on how much your time is worth.
audit13 said:
Did you try twrp and use a otg usb?
It really depends on how much your time is worth.
Click to expand...
Click to collapse
I will keep retrying to see if it is something I am doing wrong but whereas Skipsoft installed easily, i dont seem to be able to install twrp on this nonbooting pda?
If the phone is not recognised by the computer, either the drivers are not working properly, the USB port is damaged, or the USB cable is not compatible with Odin.
Until the phone is recognised in Odin, you can't flash a stock rom from sammobile.com.
audit13 said:
If the phone is not recognised by the computer, either the drivers are not working properly, the USB port is damaged, or the USB cable is not compatible with Odin.
Click to expand...
Click to collapse
I am not exactly a newbie at this but I am beginning to wonder if I havent just got a developing massive hardware failure. I have tried a number of computers, including ones which formerly recognised the computer/cable/S3 setup and none can now recognise the phone, eg in Odin.
The phone is detected on plugin to Windows 10 (with the recognition beep) and is then not seen in windows explorer. Changing cables doesn't do anything. I am assuming it should automatically appear on the drop-down menu in TWRP's app in the playstore. That menu only shows a phone I plugged into the system about 6 months ago (without it being rooted) and asks for root permissions on this now-nonexistent phone.
The phone is not now recognised as it was up till only a few days ago in XP. Nothing is now recognised on a Mac, though on all three units the phone charges.
Restarting in download mode a few times changes nothing.
audit13 said:
.Until the phone is recognised in Odin, you can't flash a stock rom from sammobile.com.
Click to expand...
Click to collapse
The only other thing I can think of is putting some TWRP file (?) on an SD card, booting into recover/Philz and can i not install TWRP or reflash some ROM from there?
I'm not sure if twrp can be flashed from Philz as I have always flashed TWRP via Odin.
You have done everything I would have done to get the phone recognized short of a installing a fresh installation of a Windows OS.
You could also try Heimdall (http://glassechidna.com.au/heimdall/).
I have unlocked the phone and installed Twrp.
I have wiped everything on the phone.
i am able to boot into Twrp, but when i plug in the USB it does not show as MTP device.
I need to copy the ROm to the phone in order to Flash it, how can i fix this.
Thanks for your help.
rony925 said:
I have unlocked the phone and installed Twrp.
I have wiped everything on the phone.
i am able to boot into Twrp, but when i plug in the USB it does not show as MTP device.
I need to copy the ROm to the phone in order to Flash it, how can i fix this.
Thanks for your help.
Click to expand...
Click to collapse
Make sure to install Motorola Device Manager on Windows.
Or use Linux, where everything actually works.
Installed still, device doesn't show up!
Can you try some other port and/or cable ? Or does the device show up in device manager or in the notifications as setting up?
tywinlannister7 said:
Can you try some other port and/or cable ? Or does the device show up in device manager or in the notifications as setting up?
Click to expand...
Click to collapse
Thanks for your reply.
Well i have another Htc phone as well , when i plug it in in recovery it shows in windows as MTP but with Motorola it doesn't show up.
But after installing the system it shows up in windows normally..
@rony925 Your Computer Is Missing MTP Driver Install It Manually
Go To C Drive/Windows Folder Search for WDMTP.inf Right Click on It and Hit Install (Your Phone Needs To Be Connected to Computer During Installation with MTP Mofe )
Thanks i will try it out.
rony925 said:
I have unlocked the phone and installed Twrp.
I have wiped everything on the phone.
i am able to boot into Twrp, but when i plug in the USB it does not show as MTP device.
I need to copy the ROm to the phone in order to Flash it, how can i fix this.
Thanks for your help.
Click to expand...
Click to collapse
Try this
Install it manualy in device manager and choose the MTP USB type.
I'm on DP3 and had flashed elementalx with temp TWRP. Now I am unable to get file transfer nor ADB to pull up on my phone. I'm unable to upgrade to DP4 due to custom kernel, and can't use ADB to restore boot.
taylor310 said:
I'm on DP3 and had flashed elementalx with temp TWRP. Now I am unable to get file transfer nor ADB to pull up on my phone. I'm unable to upgrade to DP4 due to custom kernel, and can't use ADB to restore boot.
Click to expand...
Click to collapse
Try different USB A to USB C cables and ports for starters, and make sure your platform-tools are up to date. You may have to factory reset to get pc to phone connection. And even then there are no guarantees. ?
I was able to get it working. I turned of USB debugging and back on and now it connected.
Phew!
taylor310 said:
I was able to get it working. I turned of USB debugging and back on and now it connected.
Phew!
Click to expand...
Click to collapse
Oh nice! There's another possible solution to the ever growing list of....OH CRAP! My pc isn't recognizing my device anymore!