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
Related
I'm currently attempting to root my atrix but I've come across a problem that I can't seem to be able to solve through googling or otherwise.
I'm using the tutorial stickied on the Atrix homepage labelled [HOWTO MAY16].
I got as far as step 8 and my phone passed the sbf flash using RSD lite but continuing on with the process to step 13 where it is asking me to type "fastboot oem unlock" into cmd I get an error message telling me that cmd is waiting for my device but nothing seems to happen.
I've tried reinstalling drivers (64 bit), restarting computer, restarting phone, trying different leads/usb sockets with no change to my result.
The exact thing that I'm doing with cmd is to navigate to the platform-tools folder, open adb, open flashboot and then attempt fastboot oem unlock.
Additional information:
UK Orange Atrix 4G running 3.4.4
using IHOP sbf file
running windows 7 64-bit, using the 64-bit drivers.
Do you have access to win 7 or xp? Win 8 is really new and possibly that could be the problem. Worth a shot.
pre4speed said:
Do you have access to win 7 or xp? Win 8 is really new and possibly that could be the problem. Worth a shot.
Click to expand...
Click to collapse
Ops, typo. I'm running Windows 7 64-bit. I'll edit my post when xda allows me to.
Unlock
Enter the bootloader program by powering off the phone, Hold the volume down key and the power at the same time. The phone will be in the bootloader program when it powers up, use the volume down key to scroll through bootloader menu options. the second option will be fastboot program. Select the fastboot option with the volume up key, this will enter the fastboot mode of operation. Connect the phone to the PC via USB cable. Enter the directory where the fastboot program resides on the PC. Type the Fastboot oem unlock command. If sucessful a message will display on PC retuned by the phone. Reboot phone and unlocked will display in the upper left corner of the phones display. Continue to follow the original post, flash recovery, root phone, flash custom ROM. Happy Flashing, Enjoy! :fingers-crossed:
fdaconta said:
Enter the bootloader program by powering off the phone, Hold the volume down key and the power at the same time. The phone will be in the bootloader program when it powers up, use the volume down key to scroll through bootloader menu options. the second option will be fastboot program. Select the fastboot option with the volume up key, this will enter the fastboot mode of operation. Connect the phone to the PC via USB cable. Enter the directory where the fastboot program resides on the PC. Type the Fastboot oem unlock command. If sucessful a message will display on PC retuned by the phone. Reboot phone and unlocked will display in the upper left corner of the phones display. Continue to follow the original post, flash recovery, root phone, flash custom ROM. Happy Flashing, Enjoy! :fingers-crossed:
Click to expand...
Click to collapse
I just gave it another try and it gets stuck after I type fast boot oem unlock. I definitely have the right directory but I still get stuck here. Cmd just tells me it's waiting for my device and stops there. I think it's a driver issue after a bit of googling but the official drivers aren't working. This socks.
I had a similar problem with my device not showing up. There wasn't really a big fix for it but I just waited longer before trying to execute the command. I'm not sure if you're experiencing the same thing I did but when it couldn't detect my device it just hadn't been recognized by the computer yet. Make sure your drivers are working (connect usb and select every option on the pull down menu and are sure the device gets installed). After that do the same thing as before for fastboot but make sure you securely plug it in and wait for the computer to detect your phone before you move forward
Sent from my MB860 using xda app-developers app
Hi,
I. Have gotten myself into quit a frustrating situation. My nexus 7 was unlocked, rooted and had several different custom roms installed at various times and had never had a problem. But then one time in particular, when trying to flash a rom (which I can't even remember which one it was,) after the rom had "successfully" been flashed, it rebooted to the splash screen, which it stayed at for a very long time; before just turning into a series of flashing vertical lines that never end. I can use the power+vol- method to get to fastboot, but not recovery; it would appear that my recovery has been wiped as I get the same google splash screen loop as when I try to boot. My problem is that nothing I do allows me to successfully connect the device to my pc (w7, 32bit.)
I have uninstalled any conflicting drivers, un/re-installed the proper drivers from like 7 different guides, I have also tried two different nexus root toolkits. I even tried to use a Linux machine to no avail. I have switched USB cables, everything I have tried has not worked. This is by no means my first foray into android devices, I even freshly installed my android SDK and still my computer just fails to recognize the nexus 7 in fastboot mode.
Any tips or advice would be a godsend. Thanks.
This sounds like a issue a few people have been having.. As far as i know as of a week ago there is no solution . You need to flash the boot-loader it sounds like. There is a thread about this. Search for NV FLASH .. OR APX MODE. Sorry for being lazy and not looking for the thread for you..
They may have some things in that thread that you have not tried.
Turn your Nexus off and plug it into your computer. Does your Nexus start charging? A completely bricked Nexus wouldn't charge. If it starts charging, then try turning it on into Fastboot mode.
Sorry, I'm no dev. Just a random thought to try. But if your Nexus can charge you shouldn't be fully bricked, hopefully. At least this is what I think.
When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2
My bro bricked his N7
He was rooted and unlocked, flashed a rom now it bootloops on the logo. Now when doing adb devices, it doesnt detect the device when in bootloader, went to device manager and shows problem with driver. Tried other drivers but says its up to date. Thing is I just upgared his friends N7 with the same drivers so I know thats not a problem.
It wont go into recovery either. Now when it is bootlooping, the decive is recognised when doing adb devices. So can I flash a factory image when it is bootlooping or does it have to be in fastboot?
TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-
dramdrum said:
When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
it doesn't even acknowledge that I plugged anything in to the computer at all.
chismay said:
TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-
Click to expand...
Click to collapse
Just goes to bootloader?
Edit seems to be working now even though when doing adb devices in fastboot it doesnt list the device id
In fatboot mode you don't have adb access - down load a recovery image and name recovery.img
Hold shift and right click in the folder recovery.img is in
Choose open command here, in cmd type
fastboot devices
If you see your serial number proceed
fastboot flash recovery recovery.img
When finished reboot to recovery and flash rom of choice
ps, you have had to either change your path in enviromental variables to include platform-tools from the sdk or have both fastboot.exe and recovery.img in the same folder that cmd is pointed to
Sent from my HTC Vision using xda premium
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
herghost said:
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
Click to expand...
Click to collapse
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
jombo2323 said:
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
Click to expand...
Click to collapse
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
herghost said:
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
Click to expand...
Click to collapse
you are 100% positive you did EXACTLY what i said?
I have no idea what went wrong
That's the problem with toolkits though. People don't know what they're doing and when something goes wrong you don't know how to fix it!! I understand where toolkits come from, but they are only useful if you know what happens in the background when you click on a button.
Thread Moved
Thread belongs in Q&A. Not the Dev Forum
Post moved.
MD
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
erica_renee said:
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
Click to expand...
Click to collapse
You Star
Put me on the right track, my PC was basically assuming that it was my S3, in the end I removed everything with samsung in it from the registry, uninstalled all the drivers then tried again, correctly showing as a nexus and not a samsung
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
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.