My Nexus 4 LCD cracked upon impact today and the digitizer is damaged. I want to backup my phone before I repair the LCD, currently it is:
- Rooted
- USB Debugging is enabled from settings
- Device is set as "Camera" and not "MTP"
I want to use the tool http://forum.xda-developers.com/showthread.php?t=2786395
But I cannot tick the box for USB Debugging when using the tool, so I used the following in ADB in Recovery (TWRP)
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
Click to expand...
Click to collapse
However, the device doesn't show up. In device Manager (Control Panel) and while I'm in recovery I get "mako" with a yellow triangle
for which I cannot install any driver (I downloaded them through SDK).
I think it's a driver issue and I want to get sorted to have access to my phone, any ideas or experiences would be welcome!!
Thanks!
It's probably not showing up because camera is selected instead of MTP, but my question is why do you want to back it up.... just Repair Lcd and it should be just like it was before lcd broke....
Zmax
TecheTag said:
It's probably not showing up because camera is selected instead of MTP, but my question is why do you want to back it up.... just Repair Lcd and it should be just like it was before lcd broke....
Zmax
Click to expand...
Click to collapse
Good question, I suppose I worry that something might go wrong while disconnecting/reconnecting the mobo.
boeder9 said:
Good question, I suppose I worry that something might go wrong while disconnecting/reconnecting the mobo.
Click to expand...
Click to collapse
I have a business repairing phones.. nothing is going to happen when you disconnect the lcd and reconnect the new lcd... But if your phone has a frame I would Repair the whole frame and lcd together... Its much easier then just repairing the lcd alone
Zmax
TecheTag said:
I have a business repairing phones.. nothing is going to happen when you disconnect the lcd and reconnect the new lcd... But if your phone has a frame I would Repair the whole frame and lcd together... Its much easier then just repairing the lcd alone
Zmax
Click to expand...
Click to collapse
Well that's comforting, thank you! I'm trying to get the OEM part from LG, I found it in the market here in Saudi but it's not original, just a grade A quality LCD + frame.
boeder9 said:
Well that's comforting, thank you! I'm trying to get the OEM part from LG, I found it in the market here in Saudi but it's not original, just a grade A quality LCD + frame.
Click to expand...
Click to collapse
I use either Amazon or ebay mostly Amazon because they have prime which means you get shipping free and some items you get in 2 days so if you order it on a Friday it comes on Sunday... Its free for a month and then $99 after that or you can keep making a new email every month to beat the system
Zmax
Is there any other way to get to my files on the N4? or at least control the device with the cracked LCD?
boeder9 said:
Is there any other way to get to my files on the N4? or at least control the device with the cracked LCD?
Click to expand...
Click to collapse
Is your bootloader unlocked? If so flash twrp using fastboot. Then boot into twrp and you'll be able to copy and paste files from your device to your pc. If you can't see anything on your screen it might be a little hit and miss but it should be possible.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your bootloader unlocked? If so flash twrp using fastboot. Then boot into twrp and you'll be able to copy and paste files from your device to your pc. If you can't see anything on your screen it might be a little hit and miss but it should be possible.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yup bootloader is unlocked, I have twrp already but how do I choose the options in twrp? The screen doesn't respond! Also how do I copy files using twrp?
boeder9 said:
Yup bootloader is unlocked, I have twrp already but how do I choose the options in twrp? The screen doesn't respond! Also how do I copy files using twrp?
Click to expand...
Click to collapse
You don't need to choose any options (assuming you have one of the newer versions). All you have to do is boot into it. Boot into the bootloader, hit vol down twice and then power. Let it boot and plug your device into your usb cable. The device should show up on your pc.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You don't need to choose any options (assuming you have one of the newer versions). All you have to do is boot into it. Boot into the bootloader, hit vol down twice and then power. Let it boot and plug your device into your usb cable. The device should show up on your pc.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
That's the problem though, I had set it on Camera instead of MTP, so now I only get access to files like DCIM and NOT the rest of the files. Is there any way to circumvent this and have access to all the folders?
boeder9 said:
That's the problem though, I had set it on Camera instead of MTP, so now I only get access to files like DCIM and NOT the rest of the files. Is there any way to circumvent this and have access to all the folders?
Click to expand...
Click to collapse
Have you tried booting into twrp? Twrp defaults to mtp mode so I don't think it matters what you set the device to.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You don't need to choose any options (assuming you have one of the newer versions). All you have to do is boot into it. Boot into the bootloader, hit vol down twice and then power. Let it boot and plug your device into your usb cable. The device should show up on your pc.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I got into twrp, but again i had "mako" in the control panel device manager, so neither Camera nor MTP worked BUT then:
- I installed some drivers from the N4 Toolkit, namely the samsung drivers, and they worked. NOT MTP though, I am able to get into recovery and use ADB Pull commands but again for some files transfer is interrupted by "No such file or directory" that cancels the operation - so I need to somehow transfer directories/subdirectories individually..anyone can help out here?
- Other thing, though drivers are now installed correctly now, I still can't get to MTP and I think that might due to the fact that ive enabled USB Debugging. From my experience on N4 and N6 if I disable USB debugging I can use the device as MTP, if I enable it I cannot, I can only use Camera if it is enabled - so second question: can I disable USB Debugging through ADB somehow?
Thank u all!
boeder9 said:
I got into twrp, but again i had "mako" in the control panel device manager, so neither Camera nor MTP worked BUT then:
- I installed some drivers from the N4 Toolkit, namely the samsung drivers, and they worked. NOT MTP though, I am able to get into recovery and use ADB Pull commands but again for some files transfer is interrupted by "No such file or directory" that cancels the operation - so I need to somehow transfer directories/subdirectories individually..anyone can help out here?
- Other thing, though drivers are now installed correctly now, I still can't get to MTP and I think that might due to the fact that ive enabled USB Debugging. From my experience on N4 and N6 if I disable USB debugging I can use the device as MTP, if I enable it I cannot, I can only use Camera if it is enabled - so second question: can I disable USB Debugging through ADB somehow?
Thank u all!
Click to expand...
Click to collapse
Ok, I don't know the status of your device. I know with the latest twrp you can boot into it and access your device through mtp. Adb pull is a pita if you don't know the specific location and name of files. Here's what I'd do:
1. Google 15 second adb install xda. That'll install the usb drivers and fastboot with system variables set so you don't need to worry about the path to fastboot.exe.
2. Download the latest twrp image from here http://techerrata.com/browse/twrp2/mako. Rename it twrp for simplicity.
3. Boot into your bootloader and open a command window in the same folder as twrp.img is in.
4. Run the command
fastboot boot twrp.img
5. You'll be booted into twrp and with your device connected to your pc you should see nexus4. From there it is as easy as copying and pasting files from your device to your pc.
When booted into recovery it makes no difference if you have usb debugging checked you not
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Ok, I don't know the status of your device. I know with the latest twrp you can boot into it and access your device through mtp. Adb pull is a pita if you don't know the specific location and name of files. Here's what I'd do:
1. Google 15 second adb install xda. That'll install the usb drivers and fastboot with system variables set so you don't need to worry about the path to fastboot.exe.
2. Download the latest twrp image from here http://techerrata.com/browse/twrp2/mako. Rename it twrp for simplicity.
3. Boot into your bootloader and open a command window in the same folder as twrp.img is in.
4. Run the command
fastboot boot twrp.img
5. You'll be booted into twrp and with your device connected to your pc you should see nexus4. From there it is as easy as copying and pasting files from your device to your pc.
When booted into recovery it makes no difference if you have usb debugging checked you not
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Can't thank u enough bro..flashing the new version of twrp via fastboot wont affect any of my data right?
will try this tomorrow and report back.
boeder9 said:
Can't thank u enough bro..flashing the new version of twrp via fastboot wont affect any of my data right?
will try this tomorrow and report back.
Click to expand...
Click to collapse
No, it won't touch your data.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Ok, I don't know the status of your device. I know with the latest twrp you can boot into it and access your device through mtp. Adb pull is a pita if you don't know the specific location and name of files. Here's what I'd do:
1. Google 15 second adb install xda. That'll install the usb drivers and fastboot with system variables set so you don't need to worry about the path to fastboot.exe.
2. Download the latest twrp image from here http://techerrata.com/browse/twrp2/mako. Rename it twrp for simplicity.
3. Boot into your bootloader and open a command window in the same folder as twrp.img is in.
4. Run the command
fastboot boot twrp.img
5. You'll be booted into twrp and with your device connected to your pc you should see nexus4. From there it is as easy as copying and pasting files from your device to your pc.
When booted into recovery it makes no difference if you have usb debugging checked you not
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
DUDE THIS WORKED!
One thing. The screen goes black, doesn't go to twrp but Nexus 4 shows up on my PC as MTP. Files are accessible. When I restart the device, TWRP is back to the old version I had.
Not important. Thanks a million buddy. God Speed!
boeder9 said:
DUDE THIS WORKED!
One thing. The screen goes black, doesn't go to twrp but Nexus 4 shows up on my PC as MTP. Files are accessible. When I restart the device, TWRP is back to the old version I had.
Not important. Thanks a million buddy. God Speed!
Click to expand...
Click to collapse
Glad you got it working. Twrp is your old twrp because I just had you boot into it. Not flash it. If you want to flash it, fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Related
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Are you sure the ADB driver was installed for the device? Try reading through this:
http://trevorsullivan.net/2012/07/03/forcibly-installing-the-android-usb-driver-in-windows-7/
couple things to try
As silly as it sounds with modern computers, but make sure you are plugging into the back of your PC rather than a a usb port on the front.
Also, even if fastboot devices comes back blank, try typing the fastboot oem unlock anyways. 9/10 times my computer comes up empty when I query for the device but then am able to flash recovery, unlock etc with no prob
Blueback22 said:
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Click to expand...
Click to collapse
Blueback22 said:
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Click to expand...
Click to collapse
As mentioned in the above post... I've had a handful of devices that won't return a fastboot id, however they except commands just fine.
dannymac77 said:
As silly as it sounds with modern computers, but make sure you are plugging into the back of your PC rather than a a usb port on the front.
Also, even if fastboot devices comes back blank, try typing the fastboot oem unlock anyways. 9/10 times my computer comes up empty when I query for the device but then am able to flash recovery, unlock etc with no prob
Click to expand...
Click to collapse
Thank you to everyone for your help.
First thing I did was force the driver. It was showing up under mobile devices as Nexus 10, but I pushed the Google USB drivers anyway
This didnt help show the device ID when using fastboot devices, but I followed the above instructions anyway and it unlocked.
It's now at the X boot screen and taking a while. I hope I'm not in a boot loop. I dont know why I would be as all I did was unlock the bootloader and going to give it another minute before I reboot.
OK. It did boot loop. To fix this, follow this video to do a factory reset:
http://youtu.be/T1Se7Hr9Cww
I had the same issue as you with my Galaxy Nexus recently, and force installing the USB drivers does the trick every time. I think it has to do with Windows seeing the device as a media device (external MP3 player, or similar), rather than as an ADB interface. That's why you have to tell it to forcefully install the ADB driver, so it can talk ADB, rather than treating it as a media device.
Glad you got it working. Cheers
OKay I cannot for the life of me get this to work at all. I have never had a problem unlocking an HTC device, but anytime it comes to a samsung it doesn't work. I've tried the steps listed here, I've watched a video guide on unlocking from another post, I have the SDK updated, it sees the device as Android Bootloader Interface in Device Manager, I've rebooted straight to bootloader on the tablet, I've tried two different USB ports in the rear, fastboot will not read this device or give it commands at all. No reboot, no unlock, nothing. I'm seriously starting to freak out here. Been at this for 2 and a half hours now.
Varekai said:
OKay I cannot for the life of me get this to work at all. I have never had a problem unlocking an HTC device, but anytime it comes to a samsung it doesn't work. I've tried the steps listed here, I've watched a video guide on unlocking from another post, I have the SDK updated, it sees the device as Android Bootloader Interface in Device Manager, I've rebooted straight to bootloader on the tablet, I've tried two different USB ports in the rear, fastboot will not read this device or give it commands at all. No reboot, no unlock, nothing. I'm seriously starting to freak out here. Been at this for 2 and a half hours now.
Click to expand...
Click to collapse
I'm sure you did this right, but let's walk through the steps again anyway...
1) turn on tab and plug into USB do windows can install drivers
2) force ADB drivers according to link at the beginning of this thread
( it wouldn't hurt to reboot windows between steps 2 and 3)
3) shutdown tab and lead into boot loader
- do this by holding down all buttons while tab is off. When it vibrates, let go of power button until boot loader comes up
4) make sure USB is connected to back of PC and to tab
5) open terminal by going into start menu and typing CMD
6) change directory to location of fastboot
7)type fastboot devices
8) if ID comes up, you're home free. If nothing comes up, try step 9 anyway
9) type fastboot OEM unlock
10) follow instructions on tab screen
Let us know if any step failed.
Sent from my Galaxy Nexus using Tapatalk 2
pcgeek86 said:
I had the same issue as you with my Galaxy Nexus recently, and force installing the USB drivers does the trick every time. I think it has to do with Windows seeing the device as a media device (external MP3 player, or similar), rather than as an ADB interface. That's why you have to tell it to forcefully install the ADB driver, so it can talk ADB, rather than treating it as a media device.
Glad you got it working. Cheers
Click to expand...
Click to collapse
I had to do this with the Nexus 10, as well, after messing with it for a while.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
I'm sure you did this right, but let's walk through the steps again anyway...
1) turn on tab and plug into USB do windows can install drivers
2) force ADB drivers according to link at the beginning of this thread
( it wouldn't hurt to reboot windows between steps 2 and 3)
3) shutdown tab and lead into boot loader
- do this by holding down all buttons while tab is off. When it vibrates, let go of power button until boot loader comes up
4) make sure USB is connected to back of PC and to tab
5) open terminal by going into start menu and typing CMD
6) change directory to location of fastboot
7)type fastboot devices
8) if ID comes up, you're home free. If nothing comes up, try step 9 anyway
9) type fastboot OEM unlock
10) follow instructions on tab screen
Let us know if any step failed.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've done every one of those steps to the T. Rebooted multiple times, tried different USB cables, tried every port in the back, plus both up front just for extra measure. USB port works on the tab because I'm transferring media files to it right now, it recognizes as an ADB device, drivers were also force installed from SDK Toolkit, but it won't take commands, not reboot, not ID, and certainly not unlock. The only other thing I can try is using my fiance's laptop and see if for some reason it's just an issue with my PC, because if not then it's an issue with the tablet, for whatever reason, and not being able to root this is not an option for me.
Varekai said:
I've done every one of those steps to the T. Rebooted multiple times, tried different USB cables, tried every port in the back, plus both up front just for extra measure. USB port works on the tab because I'm transferring media files to it right now, it recognizes as an ADB device, drivers were also force installed from SDK Toolkit, but it won't take commands, not reboot, not ID, and certainly not unlock. The only other thing I can try is using my fiance's laptop and see if for some reason it's just an issue with my PC, because if not then it's an issue with the tablet, for whatever reason, and not being able to root this is not an option for me.
Click to expand...
Click to collapse
If you'd like, I can remote into your computer and walk through it with you to see if I can help in anyway. Let me know.
I will PM you my phone number so you can text me if you want to try this.
I am presently having the EXACT same problem. I have a Mac mini (mountain lion) and Windows 8 (vmware). Under osx I follow all the steps and similarly I can't get fastboot to give me the ID or recognize the unlock command. In Windows it recognizes the tablet when it's booted up normally. But with fastboot in the cmd prompt I get the exact same results as in osx.
P.s. I also had the same issue with my Samsung galaxy 3. Wound up having to root it at a friend's house.
Sent from my SPH-L710 using xda premium
Blueback was able to solve all my woes, thanks!
verusevo said:
I am presently having the EXACT same problem. I have a Mac mini (mountain lion) and Windows 8 (vmware). Under osx I follow all the steps and similarly I can't get fastboot to give me the ID or recognize the unlock command. In Windows it recognizes the tablet when it's booted up normally. But with fastboot in the cmd prompt I get the exact same results as in osx.
P.s. I also had the same issue with my Samsung galaxy 3. Wound up having to root it at a friend's house.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I just fixed this for the other guy. What is the file path of your fastboot.exe file?
Its in user/downloads/root. on both my osx/windows drives.
Sent from my SPH-L710 using xda premium
verusevo said:
Its in user/downloads/root. on both my osx/windows drives.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
In your windows VM, is it inside of the Android SDK/Platform-Tools/ folder?
Sent from my Galaxy Nexus using Tapatalk 2
No its on the virtual C: drive in the downloads/root folder. Root being the folder I created to extract all relevant unlocking rooting files to
Sent from my Nexus 10 using XDA Premium HD app
verusevo said:
No its on the virtual C: drive in the downloads/root folder. Root being the folder I created to extract all relevant unlocking rooting files to
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Download and install the Android SDK. Use the fastboot tool that is inside of the Android SDK/platform-tools/ folder. I can almost guarantee success.
My win 7 didn't recognize my n10 fastboot too, so I went into device manager and updated the android 1.0 or something by selecting the main SDK folder in the android SDK as an update source
Same for adb
Sent from my Nexus 10 using XDA Premium HD app
When I turn my n7 on all I get is the android with the red triangle over it and underneath it says no command. I'm unable to do anything with it. When I press power & volume up all it does is dim the screen/undim it.
From what I've been reading, I think I need to load a recovery image, but when I try to load it, I'll either get a DLL error, or in command prompt it'll give me an error saying the image can't be loaded.
The DLL error is something like adbwin.dll & its frustrating because its in the sdk\tools folder, I can see it & I've tried setting environmental variables in control panel/system to the DLL path & I still can't get my system to see it. Any help would be appreciated.
I'm using windows 8 and the recovery image I tried was twrp 2.2.1. I'm missing a step somewhere I'm thinking.
No suggestions? Uggghhhh
Is there anyway to install drivers without enabling USB debugging?
Look up Wugfresh's Nexus Root Tool Kit.
Once you install all of the drivers it'll be a breeze....
danvee said:
Look up Wugfresh's Nexus Root Tool Kit.
Once you install all of the drivers it'll be a breeze....
Click to expand...
Click to collapse
Tried this already too just last night. I've tried using samsungs mobile phone drivers, asus', and the naked drivers. I can't get this thing to be recognized. its not even charging when plugged in to my PC. I've also tried it on a w8 PC & win 7 PC.
That's an entirely different issue then. Try a different cable?
danvee said:
That's an entirely different issue then. Try a different cable?
Click to expand...
Click to collapse
Tried a few. The original stock cable, a cable from my cell phone & a diffferent phone. I also tried different USB ports lol. I've tried everything I can think of. Thanks for the suggestions though. Open to more.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Have you tried to do something simple at the error screen with fastboot? For instance just do a fastboot devices? Does it return anything? Have you properly configured your PC to run adb and fastboot? Are you trying to run fastboot/adb from the directory all the files are stored in? I know this may be basic stuff to some, not sure of your level of skill, but even still professionals still can overlook something.
Here is the latest Android Composite ADB Interface Driver straight from SDK.
http://d-h.st/kDu
If you can get into bootloader then you can erase your existing partitons then flash all the images from the Nexus Factory Images package to restore your device to stock.
SlowCobra96 said:
Have you tried to do something simple at the error screen with fastboot? For instance just do a fastboot devices? Does it return anything? Have you properly configured your PC to run adb and fastboot? Are you trying to run fastboot/adb from the directory all the files are stored in? I know this may be basic stuff to some, not sure of your level of skill, but even still professionals still can overlook something.
Click to expand...
Click to collapse
I tried running cmd to check for fast boot devices but nothing came up. Tried root kit to detect & nothing is detected either. All my files are located in C:\ which is where I had fast boot pointed to.
I'd say I'm pretty noob at this. It was originally rooted & no orobs till this instant. I'm pretty positive adb/fast boot is installed correctly.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Username invalid said:
Here is the latest Android Composite ADB Interface Driver straight from SDK.
http://d-h.st/kDu
If you can get into bootloader then you can erase your existing partitons then flash all the images from the Nexus Factory Images package to restore your device to stock.
Click to expand...
Click to collapse
I think my problem is I can't get into anything on my tablet. I can't get into boot loader & I can't enable USB debugging. I'll try the drivers tho & see if it helps
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
thestrangebrew said:
I think my problem is I can't get into anything on my tablet. I can't get into boot loader & I can't enable USB debugging. I'll try the drivers tho & see if it helps
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
USB debugging is not needed to use Fastboot.
Have you tried power and down? That's how you get into recovery. I just reread the first post and you stated that you're pushing power and up volume.
Sent from my Nexus 7 using Tapatalk 4 Beta
I'm thinking along the lines of a hardware issue with the usb port...
yea I've tried power + down also. @ user name I'm unable to get into boot loader then. fast boot doesn't detect any fast boot devices
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
danvee said:
I'm thinking along the lines of a hardware issue with the usb port...
Click to expand...
Click to collapse
the device charges when plugged into the wall. not on the PC. so I'm sure its hardware. I'll try to post some screen shots later this evening.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Unplug the battery?
Sent from my Nexus 7 using Tapatalk 4 Beta
I was going to start dismantling it as a last resort, I'm thinking this wknd might be time to do it.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I have a broken screen and digitiser - I can see nothing at all on the screen and it does not recognise any touch movements.
The phone does appear to turn on and is recognised by my computer.
I want to retrieve all my data - photos, videos etc - from the internal SD card.
Unfortunately I did not have USB debugging enabled when the screen broke.
Is there a solution to achieve thiis?
COLDrum said:
I have a broken screen and digitiser - I can see nothing at all on the screen and it does not recognise any touch movements.
The phone does appear to turn on and is recognised by my computer.
I want to retrieve all my data - photos, videos etc - from the internal SD card.
Unfortunately I did not have USB debugging enabled when the screen broke.
Is there a solution to achieve thiis?
Click to expand...
Click to collapse
Connect with usb and copy your files to the pc You don`t need usb for that.
Thanks for your reply Gee but that was, oddly enough, the first thing I tried.
The computer recognises the device as a portable media player and there are no files found in the device.
COLDrum said:
Thanks for your reply Gee but that was, oddly enough, the first thing I tried.
The computer recognises the device as a portable media player and there are no files found in the device.
Click to expand...
Click to collapse
Maybe my original post wasn't too clear.
I need to retrieve all my data from the S4, and the conventional method of plugging in to my computer via USB does not recognise any data. Would I possibly have to select to mount the card to view? Either way, this is not an option due to the broken screen.
My next thought was to use ADB to transfer over all the content of the internal SD card, however, my S4 is not recognised using ADB (I assume as USB debugging was not enabled when my phone broke?)
So, is it possible to enable USB debugging without use of the screen on this device?
COLDrum said:
Maybe my original post wasn't too clear.
I need to retrieve all my data from the S4, and the conventional method of plugging in to my computer via USB does not recognise any data. Would I possibly have to select to mount the card to view? Either way, this is not an option due to the broken screen.
My next thought was to use ADB to transfer over all the content of the internal SD card, however, my S4 is not recognised using ADB (I assume as USB debugging was not enabled when my phone broke?)
So, is it possible to enable USB debugging without use of the screen on this device?
Click to expand...
Click to collapse
do you have custom recovery on your phone??
No, the phone is entirely stock.
I'm still holding out hope that someone has seen this happen before and knows of a solution for me to retrieve my data?
Can anyone help me with this?
COLDrum said:
Can anyone help me with this?
Click to expand...
Click to collapse
Impossible bro.
gee2012 said:
Impossible bro.
Click to expand...
Click to collapse
So, I have lost all my photos etc that are on my phone?
COLDrum said:
So, I have lost all my photos etc that are on my phone?
Click to expand...
Click to collapse
i think there is a way if you flash custom recovery
samersh72 said:
i think there is a way if you flash custom recovery
Click to expand...
Click to collapse
Can I flash customer recovery, though, as I can't see my screen?
You could install ClockworkMod Recovery and use ADB to retrieve your data while it's in recovery. You can put your phone in download mode by pressing and holding Volume Down, Home and Power buttons till it vibrates. Then press Volume Up to confirm that you want to enter download mode. You should then be able to use Odin to install ClockworkMod Recovery.
COLDrum said:
Can I flash customer recovery, though, as I can't see my screen?
Click to expand...
Click to collapse
you can boot in download mode and flash it without screen. see if odin recognize it
In my opinion if u could turn on usb debugging that would not bring back your lost data. Not really sure though. You could do that by connecting a micro usb to hdmi cable to your tv and then i guess you could use the phone there, not sure if the touchscreen would work though but worth a try..
Sent from my GT-I9500 using xda premium
Thanks - I have flashed CWM via Odin successfully.
I have installed ADB but my device does not get recognised as an ADB device - have I missed something?
COLDrum said:
Thanks - I have flashed CWM via Odin successfully.
I have installed ADB but my device does not get recognised as an ADB device - have I missed something?
Click to expand...
Click to collapse
be sure that you boot in custom recovery, connect your phone, open cmd in adb folder (shift + right click) and type (no need to enable usb debug):
Code:
adb devices
you must see the serial number (in recovery mode)
Code:
adb pull /sdcard/
use attached adb folder
samersh72 said:
be sure that you boot in custom recovery
Click to expand...
Click to collapse
Because I can't see the phone I'm not sure the state it's in.
Is it just Volume-up + Home + Power to access customer recovery?
I can now see the device in ADB.
When I run the adb pull /sdcard/ command I get an
error: device unauthorised. Please check the confirmation dialog on your device.
COLDrum said:
I can now see the device in ADB.
When I run the adb pull /sdcard/ command I get an
error: device unauthorised. Please check the confirmation dialog on your device.
Click to expand...
Click to collapse
hmmm do you read "recovery" in command line after the serial number?
there is a dialog box showed on your broken screen, try to tap on, maybe you will hit confirmation
EDIT: your digitizer is broken!......no way to recognize touch.....
I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.
You can install the recovery directly through the phone through Goomanager, but the fact that your computer doesn't recognize the device in fastboot is an issue I feel needs to be addressed. Goomanager solves the problem of the recovery, but I'm not sure about the fastboot issue.
Sent from my Nexus 4 using XDA Free mobile app
mikeric said:
I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.
Click to expand...
Click to collapse
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you, thank you, thank you. This enabled MTP mode for me in about 3 seconds on my Windows 8 PC. I had tried using Wug's toolkit both automated and manual even disabling enforcement of digital signatures on driver installation and had also installed latest ADK and Google drivers to no avail (all that got me was connection in camera mode and ability to see only DCIM). I don't remember having this kind of trouble last time I decided to play with my Nexus 4. Not sure if I was using my old Windows 7 machine then or if there is a conflict with the other drivers on my machine (I have recently flashed both Motorola and Samsung devices too). I wish you had posted a couple of hours sooner lol.
Hi All,
I bought a Nexus 4 on eBay thinking I could fix it but I am really struggling.
The nexus 4 has TWRP 2.8.6.0 but that is all.
I cannot enable USB debugging as I don't have any rom installed.
I have tried a USB OTG cable with power, but have learned that the phone still cannot output the right power? The light on my usb stick comes on but TWRP does not list any USB OTG.
This phone does not have an SD card slot, so I cannot load anthing this way.
Is it impossible to get this phone working?
Kind Regards,
breaktheblock
Try fastboot from the bootloader, and reflash
ReneX10 said:
Try fastboot from the bootloader, and reflash
Click to expand...
Click to collapse
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?
breaktheblock said:
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?
Click to expand...
Click to collapse
tbh, going back to stock is a good idea and then the door is open
https://developers.google.com/android/nexus/images?hl=en
there ya go, basically follow the instructions...
ReneX10 said:
tbh, going back to stock is a good idea and then the door is open
there ya go, basically follow the instructions...
Click to expand...
Click to collapse
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.
breaktheblock said:
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.
Click to expand...
Click to collapse
Afraid I am a Linux baby, can't help you with Windows :/
fastboot etc already on there
my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?
breaktheblock said:
my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?
Click to expand...
Click to collapse
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk
dsbnz said:
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?
breaktheblock said:
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?
Click to expand...
Click to collapse
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk
dsbnz said:
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.
breaktheblock said:
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.
Click to expand...
Click to collapse
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk
dsbnz said:
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?
breaktheblock said:
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?
Click to expand...
Click to collapse
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk
dsbnz said:
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
I use a mac, so im no use when it comes to linux variants etc.
Depending on the power of your pc, you could try using a virtual machine (i.e. virtualbox running windows xp if you have xp disk, or even windows 7). Ive done this before on the mac (xp virtual machine) and it works. This way you can install the correct drivers on a fresh install of windows, without messing with the host OS.
Otherwise, best bet is to uninstall any drivers in your current windows, and install divers from google link i posted earlier.
Sent from my LG-V500 using Tapatalk
breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?
ReneX10 said:
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?
Click to expand...
Click to collapse
nothing happens at all.
I think I have something similar to this http://forum.xda-developers.com/nexus-4/help/twrp-os-installed-connect-to-pc-t2538794
as in i'm stuffed. :crying:
As in "no devices detected" ...what is the output? Pfffft I tried!
ReneX10 said:
As in "no devices detected" ...what is the output? Pfffft I tried!
Click to expand...
Click to collapse
Just to check I am doing it correctly, I launch cmd in windows, change the directory to the location where fastboot is and type "fastboot devices". The result of this is it just gives the directory name again waiting for another command.
I hope I'm not coming across as ungrateful, I assure you this is not the case.