I don't know how, but my S4's screen broke internally (Through pressure, according to AT&T saying they are "pressure cracks").
Beyond that
I upgraded to the S5 (Knowing if I get a replacement S4, it's likely to be upgraded which I don't want so might as well get the S5), and I would love to get my pictures and stuff back without having to repair the S4 screen. The only problem is that it has a pattern lock on it. I do not think it had USB debugging on it, but it was rooted with SS. Kies and Windows don't completely recognize the device, only that it's plugged in. Need help on getting the stuff off. Please help!!
If usb debugging is off there's not much you can do. You could try to boot into recovery and the use adb to pull files off. Try "adb devices" and see if it regonizes your device. If it does then use "adb pull/sdcard/ c:\sdcard"
Sent from my Nexus 5
jd1639 said:
If usb debugging is off there's not much you can do. You could try to boot into recovery and the use adb to pull files off. Try "adb devices" and see if it regonizes your device. If it does then use "adb pull/sdcard/ c:\sdcard"
Sent from my Nexus 5
Click to expand...
Click to collapse
Boot to stock recovery or SS recovery? Also, can you use the volume keys on SS? I haven't tried it, so if you can I could use screenshots so I can guide myself through and mount USB. Or do that through the stock recovery but I don't know if it has that option. Other than that, just booting into either recoveries doesn't detect the device....
Bumppp?
SkyAttacksX said:
Bumppp?
Click to expand...
Click to collapse
Try booting into ss and then use adb pull /sdcard/*·* c:\sdcard If it works it'll take a long time
Edited
Sent from my Nexus 5
jd1639 said:
Try booting into ss and then use adb pull /sdcard/*·* c:\sdcard If it works it'll take a long time
Edited
Sent from my Nexus 5
Click to expand...
Click to collapse
No devices attached....
SkyAttacksX said:
No devices attached....
Click to expand...
Click to collapse
Sorry man, I'm out of ideas.
Sent from my Nexus 5
You could probably send it off to mobiletechvideos who could probably pull the data off.
Brain fact! What about using Heimdall to do a partial flash. You might be able to get past that lockscreen then.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Red_81 said:
You could probably send it off to mobiletechvideos who could probably pull the data off.
Brain fact! What about using Heimdall to do a partial flash. You might be able to get past that lockscreen then.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Heimdall? Sorry for being a noob, I only had the S4 from September xD
Heimdall is an open source alternative to Odin. The MAC guys are forced to use it since Odin will not run on a MAC.
The part I was curious about is why your device does not mount as a hard drive when you plug it into your PC. Is that because of the lockscreen? I never use once personally.
It sounds like you may just have driver issues. You could even try downloading the Ubuntu LiveCD, booting to that, and then plug in your phone to see if it appears.
Red_81 said:
Heimdall is an open source alternative to Odin. The MAC guys are forced to use it since Odin will not run on a MAC.
The part I was curious about is why your device does not mount as a hard drive when you plug it into your PC. Is that because of the lockscreen? I never use once personally.
It sounds like you may just have driver issues. You could even try downloading the Ubuntu LiveCD, booting to that, and then plug in your phone to see if it appears.
Click to expand...
Click to collapse
Well, it does mount. The problem is that no files are shown since it has a lockscreen... And alright I think http://forum.xda-developers.com/showthread.php?t=2374441 that's it right?
Related
Will there me a nexus 7 root without the adb, cause last time i tried to install on my computer i couldnt get it to work properly and made my pull my hairs out.
Questions go in the Q&A section
lovenokia said:
Will there me a nexus 7 root without the adb, cause last time i tried to install on my computer i couldnt get it to work properly and made my pull my hairs out.
Click to expand...
Click to collapse
Well guessimg there will likely be an Odin version
Sent from my GT-P7510 using Tapatalk 2
animatechnica said:
Well guessimg there will likely be an Odin version
Sent from my GT-P7510 using Tapatalk 2
Click to expand...
Click to collapse
Odin is a samsung-only application but yeh, there should be ways to attain root without adb (most likely via recovery).
What about hiemdell??? The other version for ppl who can't use Odin ..idk to much about it tho
Sent from my SAMSUNG-SGH-I717 using xda premium
armyboy11b said:
What about hiemdell??? The other version for ppl who can't use Odin ..idk to much about it tho
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Same with Heimdall I believe as it was meant to be an implementation of Odin. I'm not too sure as to whether the Nexus 7 has a 'Download Mode', if it does, somebody might write an equivalent tool to use it.
Why bother with Odin or Heimdall when there's fastboot anyway ? I find fastboot to be much easier to use and it hasn't got that much of a learning curve.
This thread in the dev forum says you don't need adb:
http://forum.xda-developers.com/showthread.php?t=1742919
dbrickg said:
This thread in the dev forum says you don't need adb:
http://forum.xda-developers.com/showthread.php?t=1742919
Click to expand...
Click to collapse
The tool in that thread actually uses the ADB to perform all of it's actions, I would suggest install ADB, get the drivers working and test with "adb devices" that the drivers are working and the devices is visible and then run that tool to streamline the rest of the process for you.
I would always recommend having the ability to use ADB, especially when you're tinkering, it's always best to make sure ADB works in-case you need to perform any other tasks for the case that something goes wrong.
lovenokia said:
Will there me a nexus 7 root without the adb, cause last time i tried to install on my computer i couldnt get it to work properly and made my pull my hairs out.
Click to expand...
Click to collapse
A fastboot only method is available on modaco complete with a batch file to do all the hard work. Think you will still need to unlock the boot loader first though.
http://www.modaco.com/topic/355552-superboot-rooting-the-nexus-7/
Trying to go from paranoid android to stock 4.2, and adb won't see my device, what is the deal?
ok, nevermind
alright heres the deal, in fastboot, it won't see my device, what is the deal?
I type in "Fastboot" devcices, and it just goes to the next line. Argh i'm getting pissed
Anybody? HELP!
Cor-master said:
Anybody? HELP!
Click to expand...
Click to collapse
Have you installed the Google USB drivers from the SDK, this guide will help you out.
http://developer.android.com/tools/extras/oem-usb.html
Cor-master said:
Anybody? HELP!
Click to expand...
Click to collapse
Have you got the right drivers on your PC?
Edit: Somebody beat me to it.
I've had a folder on my desktop I've been using since I rooted my flyer back in March, and my windows sees it in the bootloader, but cmd prompt doesn't.
here's a screenshot. God I've done this crap a million times, adb works inside android, but in the bootloader it does nothing, I hate getting stumped on simple crap.
Cor-master said:
here's a screenshot. God I've done this crap a million times, adb works inside android, but in the bootloader it does nothing, I hate getting stumped on simple crap.
Click to expand...
Click to collapse
I think Windows "sees" the device as a different device when it's in Fastboot mode versus being in Recovery mode, vs. fully booted.
Try force installing the driver per these directions:
http://trevorsullivan.net/2012/07/03/forcibly-installing-the-android-usb-driver-in-windows-7/
Cor-master said:
here's a screenshot. God I've done this crap a million times, adb works inside android, but in the bootloader it does nothing, I hate getting stumped on simple crap.
Click to expand...
Click to collapse
In device manager, is there a device with an unknown driver (warning sign)? when your N7 is connected to your PC?
I just downloaded wugs root tool kit, reinstalled drivers throught it, it worked completly...yet if I manually type commands I get nothing...ugh..
screw it I wanted to do it manually so I could try and keep my data, but so be it.
I am having the same issue. Google drivers installed while device was turned on. Adb works flawlessly as long as the device is fully booted. When the device reboots into recovery, windows sees it as a different device. Reinstalling the drivers while in recovery fails.
Sent from my Nexus 7 using xda premium
I dunno what the deal is. On my vivid kernels have to be flashed through fastboot because of htcs s on crap and it always works. Even stranger toolkits work fine but manually typing commands doesn't
Sent from my HTC PH39100 using Tapatalk 2
Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Duplicate post. Please erase.
nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.
Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app
I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.
Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.
Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!
Hi all,
I've got my old Nexus 4 Device out but the only issue is I dropped it face down on a concrete floor, The entire screen is smashed. The LCD works fine, but is unresponsive to touch. I've tried accessing it through my computer but because I have a lock on it, it won't let me access the files.
It is rooted, but I'm not 100% with as my friend did it for me. He's away at the moment so can't really help me.
I had titanium backup on it. Does this mean anything?
Also I've seen the method of people wiping the cache. However this doesn't work for me as I have a different screen appear TWRP, Team Win Recovery Project, which also requires a slide to unlock....
Is there any other possible methods of obtaining my data?
If there isn't thats not too much of a problem, and Im not too concerned about losing the data, so Im open to experimentation!
Cheers guys!
Few months back I had a similar problem with my nexus 7 . Easy way is to connect a USB hub and a mouse via OTG to unlock the device and then connect it to a computer .
Let me know if it works.
Sent from my XT1022 using XDA Free mobile app
chaithanyaprasad said:
Few months back I had a similar problem with my nexus 7 . Easy way is to connect a USB hub and a mouse via OTG to unlock the device and then connect it to a computer .
Let me know if it works.
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Okay, and this would work?
An OTG cable looks like this right?:
http://www.trademe.co.nz/computers/...ssories/chargers-cables/auction-789171735.htm
Cheers
Yes, that's the OTG cable.
In my case ,I have connected a keyboard and mouse then with the mouse I have unlocked the pattern lock.
You can then take a backup with PC or a flash drive
Sent from my XT1022 using XDA Free mobile app
The N4 doesn't support OTG unless you're running a kernel that supports it (stock kernel doesn't have it).
When I cracked my screen, I used adb to send tap and swipe commands. Of course, you need to to have previously enabled USB debugging...
0mnom said:
Hi all,
I've got my old Nexus 4 Device out but the only issue is I dropped it face down on a concrete floor, The entire screen is smashed. The LCD works fine, but is unresponsive to touch. I've tried accessing it through my computer but because I have a lock on it, it won't let me access the files.
It is rooted, but I'm not 100% with as my friend did it for me. He's away at the moment so can't really help me.
I had titanium backup on it. Does this mean anything?
Also I've seen the method of people wiping the cache. However this doesn't work for me as I have a different screen appear TWRP, Team Win Recovery Project, which also requires a slide to unlock....
Is there any other possible methods of obtaining my data?
If there isn't thats not too much of a problem, and Im not too concerned about losing the data, so Im open to experimentation!
Cheers guys!
Click to expand...
Click to collapse
Since you have twrp installed you can pull files using adb
In a cmd prompt
adb pull /sdcard/
You might need to install adb and drivers first, koush universal drivers work well.
DrFredPhD said:
Since you have twrp installed you can pull files using adb
In a cmd prompt
adb pull /sdcard/
You might need to install adb and drivers first, koush universal drivers work well.
Click to expand...
Click to collapse
Sorry, I have no idea of what you are talking about. I'm a relative newbie when it comes to all this rooting and roms and stuff as my friend did this for me, but Im willing to learn?
Id be more than happy to continue this conversation through PM?
Cheers,
0mnom said:
Sorry, I have no idea of what you are talking about. I'm a relative newbie when it comes to all this rooting and roms and stuff as my friend did this for me, but Im willing to learn?
Id be more than happy to continue this conversation through PM?
Cheers,
Click to expand...
Click to collapse
Boot into twrp, then on your pc run the commands drfred said. Before you do that Google 15 second adb install. Install that
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Boot into twrp, then on your pc run the commands drfred said. Before you do that Google 15 second adb install. Install that
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Okay, so did the 15 second install, couldnt get past step 3 however. For some reason when I pressed y, it would just quit out of it.
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot or N/No to skip
3. Press Y/Yes to install ADB system-wide or N/No for current user only
4. Press Y/Yes to install Drivers or N/No to skip
5. Continue Driver installation
6. 15 seconds passed - finished!
But Im assuming its done? I booted my phone into recovery mode, and it comes up with the TWRP screen. I've plugged it in. Now do I just go into cmd and literally type in 'adb pull /sdcard/'?
Or is there added extras in there?
Cheers,
So I tried it out, but I don't think anything happened. How do I tell?
I ran that command, and it just gave me a huge message, I read through a bit of it, and I recognised the device commands, but not sure what message I should be receiving?
Cheers,
If you get a big message with all the adb options then I think you must be typing the command slightly wrong. The output should be a list of your files as they transfer.
If you run the command right but the driver or something else is wrong you'll get an error message eg. no device or device offline.
Hey, so today I wanted to install a new ROM on my SM-N900 Note 3. I flashed TWRP, and rebooted. Then I booted into TWRP and opened Android File transfer on my Mac. It kept saying please connect USB device. Other parts of the system do not read the device, however TWRP says the device is charging from my Mac's USB port. I moved to my Windows computer and connected the device. Still nothing. I tried multiple USB cables both 2.0 and 3.0. Nothing works! Can someone help me? I have no OS installed! I don't want to use ODIN or download mode because I would prefer to the install the ROM I'm trying to install because it seems silly that I have recovery access but can't access the file transfer.
Thanks, Justin
No SD Card?
justinxfan said:
Hey, so today I wanted to install a new ROM on my SM-N900 Note 3. I flashed TWRP, and rebooted. Then I booted into TWRP and opened Android File transfer on my Mac. It kept saying please connect USB device. Other parts of the system do not read the device, however TWRP says the device is charging from my Mac's USB port. I moved to my Windows computer and connected the device. Still nothing. I tried multiple USB cables both 2.0 and 3.0. Nothing works! Can someone help me? I have no OS installed! I don't want to use ODIN or download mode because I would prefer to the install the ROM I'm trying to install because it seems silly that I have recovery access but can't access the file transfer.
Thanks, Justin
Click to expand...
Click to collapse
via PC, Odin is the easiest way.
va Mobile, Recovery + ROM in SD card is the easiest way.
nijom said:
via PC, Odin is the easiest way.
va Mobile, Recovery + ROM in SD card is the easiest way.
Click to expand...
Click to collapse
I've used ODIN before but I had thought was incompatible with zips. I'll try it today though. And no, I don't have an SD card. I'm trying to move the files into my internal storage.
Thanks, Justin.
MTP doesn't work with TWRP. You'll have to use adb and push the zip to your internal storage. Then flash it through TWRP.
There are many guides on how to do this, it is very simple. Good luck
Edit- i see you're using a mac, not sure if adb works on there.. never tried myself.. always installed linux on any apple product i've owned
I haven't researched it so it might work straight away, but if not just create a vm with xp, ubuntu or something and use adb through there
Sent from my SM-N9005 using Tapatalk
celderic said:
MTP doesn't work with TWRP. You'll have to use adb and push the zip to your internal storage. Then flash it through TWRP.
There are many guides on how to do this, it is very simple. Good luck
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
That's strange, I'm pretty sure my old Nexus 7 could do this. Oh well.
Code:
adb devices
does not work. It doesn't show the device in recovery. File transfer and ADB only work while the OS is booted up.
justinxfan said:
That's strange, I'm pretty sure my old Nexus 7 could do this. Oh well.
Click to expand...
Click to collapse
Same with my old S2
It's a bug with TWRP for the n9005, i posted in the thread 4 or 5 months ago.
Sorry i've just finished work, will be back in an hour or two.
I thiught there was an ADB button in TWRP?
Sent from my SM-N9005 using Tapatalk
celderic said:
Same with my old S2
It's a bug with TWRP for the n9005, i posted in the thread 4 or 5 months ago.
Sorry i've just finished work, will be back in an hour or two.
I thiught there was an ADB button in TWRP?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
There's a button in TWRP called disable MTP or enable MTP. It has no effect. I cannot find any sign of a ADB button.
justinxfan said:
There's a button in TWRP called disable MTP or enable MTP. It has no effect. I cannot find any sign of a ADB button.
Click to expand...
Click to collapse
ADB sideload, under the advanced tab.
https://twrp.me/faq/ADBSideload.html
I just looked myself and it is there.. if there's a way of taking screenshots in recovery, somebody let me know and i'll post a pic here
Sent from my SM-N9005 using Tapatalk
Ahhh I've seen that button before. Didn't jnowbwhat it did so I didn't touch it. Now that I understand it, I'll give it a try.
Sent from my SM-N900 using XDA Free mobile app
justinxfan said:
Ahhh I've seen that button before. Didn't jnowbwhat it did so I didn't touch it. Now that I understand it, I'll give it a try.
Sent from my SM-N900 using XDA Free mobile app
Click to expand...
Click to collapse
Good luck! Let me know if you run into any problems.
Sent from my SM-N9005 using Tapatalk
Nope. Not working. Started ADB sideload from TWRP and tried to push in a random zip from my computer (about 2 mb). it said error: device not found.
bump
Someone can clarify this?