Related
All,
I have a big problem. When I try to start my phone I get the black screen with google and the unlocked padloack, after which the screen goes dark and nothing happens anymore.
What I did before this are two things. I had been mukking around with the screen resolution (I had it set at 240 and 280, as some apps did not show up in the market) also downloaded LCD density to solve the market issue.
I then rebooted the device and entered CWM to do a backup which as far as I knew succeeded. unfortunately after rebooting, see the above.
I have tried a couple of reboots, tried restoring the nandroid (the above was the only one I had). that didn't work, so tried to connect to the PC to load a new ICS rom (original 4.0.4 by google), unfortunately my device can not go into USB mode in CMW (it comes up with UMS lunfile missing....)
so I am woring in circles. can't start the device to download a rom, can't open USM to load a ROM to start the device again.....
any help would be appriciated
thanks
Patrick
hey
flash a new ROM via fastboot then, there are enough guides
-Syn
Edit: Alternatively, flash the stock Google ROM via GNex toolkit and go from scratch.
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
Click to expand...
Click to collapse
To flash stock images the files are on your PC, not the phone.
If you can get the phone to boot into fastboot (via vol up + vol dn + power) and get your PC to recognize it you're good to go.
thats the issue. pc cannot recognize the phone, so cannot get any files from the PC to the phone (ie. cannot get a rom file to the phone...)
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
Either directly from Samsung or download the GNex Toolkit (You might want to use it anyways to flash the stock image), the drivers come with it.
After you installed the drivers and have you phone plugged in, go to the device manager to check if it is connected properly.
pwvandeursen said:
[snip]
thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
I had a similar issue with regard to my PC recognizing the drivers. I googled around and found that people were having success with installing the PdaNet drivers, so maybe you can try that too. I had installed the Android SDK as well as the PdaNet drivers, and I eventually got mine to work.
I would probably follow Efrant's links first though - if that doesn't work for you, then maybe you can try PdaNet drivers and/or installing the SDK.
Good luck.
Why not just do a factory reset from within recovery?
¢ £®0π π€XU$ |||
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
pwvandeursen said:
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
Click to expand...
Click to collapse
Good to hear you got it.
A few of you know me already from my thread where I asked a million questions before attempting to install a custom ROM on my new KF. Well, it still went completely south somehow, so here I am.
So, I'm stuck with the stock Kindle Fire logo on the screen, and and can't get it to go anywhere.
Here's what I did:
Downloaded KFU, installed the drivers, plugged in the Kindle,and ran KFU. ADB status online, boot status 4000.....so everything seemed good, from what I've learned. Also looked in Device manager, and it showed up as Android phone, or whatever it's supposed to say. I figure I'm good to go.
My plan is to install TWRP,FFF, and root it, then boot into TWRP, and flash the ROM. The first thing I did(and it seems wrong now) was try to install FFF, instead of TWRP. I think that's the wrong order, but not totally sure if it matters, but it's my assumption that it does.
So, as soon as I sent the command, for some reason, my computer got this blue screen with some message that I didn't have time to read, because it restarted right after. It still said everything looked good, so I tried again to install FFF. I think the "crash" was just coincidental, because it didn't act like that the second time, but whatever.
Anyway.......said it was installing FFF, and then it went to <waiting for device>
I figured ...ok...need to wait.
After about 10 minutes of waiting, I held the power button down until it turned off, then turned it back on, because someone said that's what you should do if this happens. Well, essentially.....since then, I've not seen anything but the Kindle Fire logo on the screen, and it feels like I've tried everything. A forum member spent some time on the phone with me, and we tried everything he knew.....no luck.
At one point, someone told me to uninstall the drivers and reinstall them, which I did, but upon reinstalling them, nothing changed, and the computer no longer even recognizes it being plugged in as a USB device, the drivers don't show now in device manager, even though I told KFU to reinstall them. To me that's weird, and seems like a major problem, because the computer isn't "seeing" the device, but that's mu humble opinion. I'm at a total loss, and would sure appreciate some help bringing this thing back.
Thanks....immensely, in advance!
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
If nothing you do results in any change, it's time to give up on Windows and create a Linux LiveUSB. Linux is extremely stable and pretty easy to set up and send adb/fastboot commands with. If you do decide to take that route, Ubuntu is pretty much the standard and version10.4 generally works better than later versions.
soupmagnet said:
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
Click to expand...
Click to collapse
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
soulweeper51 said:
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
Click to expand...
Click to collapse
Use the KFU on the laptop to install the drivers and see if that makes a difference.
soupmagnet said:
Use the KFU on the laptop to install the drivers and see if that makes a difference.
Click to expand...
Click to collapse
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
soulweeper51 said:
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
Click to expand...
Click to collapse
Yeah, that's what I meant.
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
kinfauns said:
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
Click to expand...
Click to collapse
I just did exactly what you said......plugged it in, turned it off. Turned volume all the way up, turned it on....no sound of any kind.
The weird part is when I first installed the drivers, I checked it by plugging the device in, and had adb status online, staus 4000, plus I went to the device manager, and I remember two things that said android phone. One said android phone, and the other said android something or other. And, it was seeing the device and everything seemed hunky dory, and I guess at that time it was???
I did uninstall and reinstall the drivers via KFU, and it says it's installing them, but never again have I seen anything in device manger that says Android anything. That is just wrong to me.
Personally I think you're spinning your wheels with Windows and causing yourself more headache than needed.
Create a bootable Linux LiveUSB on a thumb drive with Ubuntu 10.4 and get Android-SDK installed on it.
[Edit:]fixed spell check fail
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first.
Click to expand...
Click to collapse
Trust me.....I realized not too long after that I had done the wrong order. I even had a note to myself right here that said:
TWRP
FFF
Root
For the life of me, I don't know why I did FFF first.
All the questions I asked, and as anal retentive as I am, I totally screwed that part up, which may be the entire problem. Trust me.......I'm pissed.
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
Click to expand...
Click to collapse
Can I ask what Firekit is?
Firekit is a tool used to fix major problems easily. I would use it as a last resort because there isn't a command for just installing TWRP without the bootloader.. Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
soupmagnet said:
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
Click to expand...
Click to collapse
I'll just be honest and tell you that I have no idea what you're talking about. I don't mean that in a bad way.......I'm not some computer whiz that speaks the same language as a lot of you. Right now I wish I had left the freakin thing alone with Go Launcher Ex and called it a day. I'm really pissed off right now....that's not your fault.
I don't suppose that Factory Cable will do anything for this situation, correct? The guy said he will send it ASAP FWIW.
Had to ask.
soupmagnet said:
Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
Click to expand...
Click to collapse
Can you kindly tell me how I get to the point you're speaking of?
Sorry....this stuff is foreign language to me.
Do I have to install ubuntu on my computer?
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
soupmagnet said:
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
Click to expand...
Click to collapse
Should I trust this method?
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB
I know NOTHING about this.
EDIT: Never mind.......that's another OS......damnit!
Can't I just play dumb, and send it back? I hate to say that, but.....
I guess this is it
http://www.linuxliveusb.com/en/download
^See.......trying as hard as I can to keep a good attitude.
That will work. Download Ubuntu 10.4
hey guys.
just got a SGS3 for the wife and one for myself, coming from a long time with HTC Evos.
i'm having an embarassing situation...I don't see how to transfer files from or to the phone. I plug it in via usb, drivers installed automatically, computer told me the device was ready to be used...and nothing else. nothing popped up on the phone, nothing on my computer. the phones came with no software and Samsung's website does not list any drivers or software to download...
the phones are stock for now until I get a chance to root them this week or next weekend. in the meantime, what is the way a normal user is supposed to transfer files to/from this phone?!
I'm on Windows 7 on both the laptop and the PC, both have the same situation. with both phones...both fully stock but also updated with the latest software.
thanks for the help!
Max_Pain said:
hey guys.
just got a SGS3 for the wife and one for myself, coming from a long time with HTC Evos.
i'm having an embarassing situation...I don't see how to transfer files from or to the phone. I plug it in via usb, drivers installed automatically, computer told me the device was ready to be used...and nothing else. nothing popped up on the phone, nothing on my computer. the phones came with no software and Samsung's website does not list any drivers or software to download...
the phones are stock for now until I get a chance to root them this week or next weekend. in the meantime, what is the way a normal user is supposed to transfer files to/from this phone?!
I'm on Windows 7 on both the laptop and the PC, both have the same situation. with both phones...both fully stock but also updated with the latest software.
thanks for the help!
Click to expand...
Click to collapse
Weird...
it should pop up as a media device.
Plug it in and pull down the notification bar and touch where it says "touch for other USB options"
and make sure Media Device (MTP) is checked.
if it doesn pop up then either the drivers arent installed, or their not installed correctly.
or the cable is bad, or the USB port is bad.
or the devil is messing with you
Max_Pain said:
hey guys.
just got a SGS3 for the wife and one for myself, coming from a long time with HTC Evos.
i'm having an embarassing situation...I don't see how to transfer files from or to the phone. I plug it in via usb, drivers installed automatically, computer told me the device was ready to be used...and nothing else. nothing popped up on the phone, nothing on my computer. the phones came with no software and Samsung's website does not list any drivers or software to download...
the phones are stock for now until I get a chance to root them this week or next weekend. in the meantime, what is the way a normal user is supposed to transfer files to/from this phone?!
I'm on Windows 7 on both the laptop and the PC, both have the same situation. with both phones...both fully stock but also updated with the latest software.
thanks for the help!
Click to expand...
Click to collapse
make sure you have automatic updating on in windows, at least for the drivers. this is why i hate MTP, its such a pain in the ass. i sure hope someone gets mass storage mode goin in these soon. Make sure theres no unknown devices listed in the devices manager. then grab and install the drivers from here(although you shouldnt need them for mtp to work) http://www.samsung.com/us/support/owners/product/SPH-L710MBBSPR#
downloading now...when I plug it in, the cell phone makes a little noise. but no prompts come up under my notifications.
on the PC I found it the phone shows up under Devices & Printers, but there is no way to interact with it other than to see it's drivers and that they all apparently are up to date and functioning correctly...
ahhhhhh
Max_Pain said:
downloading now...when I plug it in, the cell phone makes a little noise. but no prompts come up under my notifications.
on the PC I found it the phone shows up under Devices & Printers, but there is no way to interact with it other than to see it's drivers and that they all apparently are up to date and functioning correctly...
ahhhhhh
Click to expand...
Click to collapse
Does it show as a plain looking generic box or does it look like an MP3 player in devices and printers?
Generic box under an "Unspecified" category. Even after reinstalling the drivers...same situation. I can't double click to open the phone and there is no prompt on my phone.
Sent from my SPH-L710 using xda premium
the phone is seeing as a modem by the PC...i'm guessing because of the drivers. can one of you tell me which drivers your phone is using (under Device Manager) so I can manually select those? I have many installed Samsung drivers, just need to know which one to pick I guess.
Max_Pain said:
the phone is seeing as a modem by the PC...i'm guessing because of the drivers. can one of you tell me which drivers your phone is using (under Device Manager) so I can manually select those? I have many installed Samsung drivers, just need to know which one to pick I guess.
Click to expand...
Click to collapse
This is crazy. I curse Samsung for this mtp ****t I swear. Under portable devices. Device name should be SPH-L710--thats what ur looking for. Will probly also be listed under modems as Samsung mobile usb modem. And in the usb devices as Samsung mobile usb composite device.another thought If you didn't already, turn on usb debugging and let it install those drivers as well. Has helped me in the past. Maybe even switchin it to download mode just so windows can see it in all modes and maybe wake the hell up.
i had usb debugging on originally, turned it off. no difference.
I went and bought a new memory card reader that supports SDXC cards, so now I can at least remove my memory card and transfer files...but still doesn't help me. I want to use that extra internal space I didn't have on my Evo 3D to add more music still to my phone...so I need to connect it to the PC somehow!
Max_Pain said:
i had usb debugging on originally, turned it off. no difference.
I went and bought a new memory card reader that supports SDXC cards, so now I can at least remove my memory card and transfer files...but still doesn't help me. I want to use that extra internal space I didn't have on my Evo 3D to add more music still to my phone...so I need to connect it to the PC somehow!
Click to expand...
Click to collapse
it blows my mind that its not working. what version of win 7 do you have? x86 or x64?
we have a laptop and a desktop, both running Windows 7 x64. we also have two of those Galaxy S3 phones. I'm running Go Launcher, my wife using the stock Wiz launcher. I have tried in different USB ports in both laptop and desktop, using different usb cables, and with both phones. with and without adb debugging enabled. same situation.
the phone shows up as a modem under device manager. under SAMSUNG Android Phone there is only SAMSUNG Android ADB Interface listed, nothing specific to this phone. I have tried changing the drivers around to different built-in samsung drivers and drivers from when I had the Galaxy Tab, nothing. I downloaded the latest drivers as they were linked above, nothing.
there are no pop-ups on either phone and nothing on the computer beyond the noise of something being plugged in...
w.t.f.
OK. Don't think its the issue but have run into this before with a Samsung phone or two. Reboot the computer and hold down f8 as its booting. When the advance menu comes up, hit *disable driver signature enforcement*. Like I said I don't think that's it but that has caused problems for me before (thanks microsoft) on x64 bit windows and a Samsung android phone so might as well rule it out.
O yeah, and just to make sure, you dont have kies installed right?
I do have Kies installed. someone now suggested I try using it to connect my phone. I open Kies, connect my phone, it says Connecting...and never goes anywhere. I did the connection troubleshooting thing, it took a while, said it was complete, plugged the phone back in, same situation.
jeez this is really stupid.
i disabled the driver enforcement option. nothing.
I rooted the phone now. installed that easy UMS apk and set the phone to MTP mode. now I have a Samsung MTP device on my device manager but none of the drivers work with it. windows couldn't find a driver, and i've tried 6 drivers manually and they all say they can't start the device.
anything else I can do now that i'm rooted?
Max_Pain said:
I do have Kies installed. someone now suggested I try using it to connect my phone. I open Kies, connect my phone, it says Connecting...and never goes anywhere. I did the connection troubleshooting thing, it took a while, said it was complete, plugged the phone back in, same situation.
jeez this is really stupid.
Click to expand...
Click to collapse
kies is the devil
its actually the opposite. You DO NOT want it installed. Uninstall kies completely. Idk how I forgot about mentioning kies.nothing but problems. Nix it and I bet this headache ends. And if u take that advice, have the phone unpluged during then removal . I would also recommend reinstalling the Samsung drivers I linked to yesterday. Then plug the phone in and I would bet smooth sail in from there
will try. now the phone shows up the "connected as media device" notice when I plug it in, and the PC sees it as an MTP device...but still not letting me use it. lets hope uninstalling KIES helps.
Max_Pain said:
will try. now the phone shows up the "connected as media device" notice when I plug it in, and the PC sees it as an MTP device...but still not letting me use it. lets hope uninstalling KIES helps.
Click to expand...
Click to collapse
Sounds like progress. I think uninstling kies will do the trick
well I uninstalled Kies, told it to uninstall any and all drivers for mobile phones. cleaned my registry. restarted my computer, installed the drivers fresh, plugged in the phone and it seems to work. for the first time it shows as a mtp device!
thanks a million. let's hope it works to transfer files.
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!
Dropped phone, broken screen/digitizer, doesn't respond to touch
Was able to see the screen a bit yesterday but now its almost all black. I mainly just need my photos off it. Tried an RMA to replace the screen but they said they had to wipe everything first
Is there any way I can pull the photos off it? I haven't tried an otg yet, but I also can't see the screen, so im not sure it would help
Is there a screen sharing program I could get w/o first installing it on my phone?
I think my phone may be rooted, i forget if i ever did, but i dont have TWRP installed on it? (i dont super know what that is but i see other people talking about it)
Any thoughts on how to pull photos off it? I tried the adb devices but the cmd prompt doesn't seem to recognize the phone
Im quite sure I have debugging enabled, just coudln't get the file transfer button hit
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Ok cool, how would i go about sorting the drivers? o.0
jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
side note.... wth is this image verification lol, ive tried like 30 of them, why is it so hard to post lol ><
Click to expand...
Click to collapse
Sorry, can't give definite answer, I know that I had an issue with drivers (device wasn't properly recognized) and tried pretty much everything that Google suggested ... Until it finally started working. I have no idea exactly what solved the issue, it was over a year and a half ago. The next time I clean installed Windows (10 in both cases) it was smart enough to automatically find right drivers.
So ... I'm guessing Googling something like "OnePlus 3 Windows # drivers" should find something useful?
About image verification: are you talking about anti-bot system that checks if you're human? Wouldn't know much about that, never personally had issues with it, but also very rarely see it on XDA as I'm nearly always checking this forum in Tapatalk app.
Sent from my OnePlus 3 using Tapatalk
jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
Click to expand...
Click to collapse
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
tnsmani said:
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
Click to expand...
Click to collapse
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Had the same issue with my Lenovo P2. Only i didn't have debugging enabled. If you have, screen mirroring should be an easy solution. You could just see ur phone screen on ur computer that way. What helped me was to forceboot the phone to recovery with the hardware buttons, then connect it to ur pc. TWRP will automatically launch MTP. When u backed up evrything, you can wipe ur device through adb
jsaden said:
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Click to expand...
Click to collapse
I don't know about Win 7. It will work on Win 10. Most likely, this should not be needed in Win 7 at all as the drivers should install whether signed or not.
Regarding copying data, a simple command of "adb pull /sdcard" will copy all the folders, files, data etc to your PC. You can also specify where you want the data copied to, simply add the path to the command above. This will work whether your screen works or not. Of course, there are other methods of copying data, you can search for it if you need it.