How to access Nexus 4 through PC, bootloader locked and not rooted. - Nexus 4 Q&A, Help & Troubleshooting

I have the following problem. My Nexus 4's touch is broken, it can show stuff though. I need to run an app (the battle.net authenticator, otherwise I can't log in) through access from my PC, but there are some problems. It is not rooted, its bootleader is locked and everything is stock. I do have USB debugging enabled though. Also I can't do adb commands because this is a new PC and I haven't authorised it (it shows up as unauthorised on adb devices).
After a long series of experiments and a lot of googling, I found a combination of 2 programs ([email protected] and Android Control) to do what I want, and do some stuff when on Recovery Mode to activate the adb thing through cmd (most of those in this site), but my PC can't seem to even see that a device is connected when I am in Recovery Mode. I have tried reinstalling the drivers a couple of times but nothing seems to work.
Does anyone have any ideas?

Xalathal said:
I have the following problem. My Nexus 4's touch is broken, it can show stuff though. I need to run an app (the battle.net authenticator, otherwise I can't log in) through access from my PC, but there are some problems. It is not rooted, its bootleader is locked and everything is stock. I do have USB debugging enabled though. Also I can't do adb commands because this is a new PC and I haven't authorised it (it shows up as unauthorised on adb devices).
After a long series of experiments and a lot of googling, I found a combination of 2 programs ([email protected] and Android Control) to do what I want, and do some stuff when on Recovery Mode to activate the adb thing through cmd (most of those in this site), but my PC can't seem to even see that a device is connected when I am in Recovery Mode. I have tried reinstalling the drivers a couple of times but nothing seems to work.
Does anyone have any ideas?
Click to expand...
Click to collapse
As far as connecting to the PC is concerned have you tried another PC or USB cable? And since that's a battle.net authenticator you can contact their support, either via web ticket or phone (if you live in the supported countries) and after they confirm it's really yours account, they'll remove the authenticator for you.

nerotNS said:
As far as connecting to the PC is concerned have you tried another PC or USB cable? And since that's a battle.net authenticator you can contact their support, either via web ticket or phone (if you live in the supported countries) and after they confirm it's really yours account, they'll remove the authenticator for you.
Click to expand...
Click to collapse
I can see the phone just fine everywhere else, just not in recovery, so no I didn't try that. And I have tried using their support but I was in a pretty special situation for some reason and they couldn't help, but I fixed my problem. I had saved my restoration code for my authenticator ages ago and I didn't remember. Thanks for trying to help out though

Related

Hero "Device not recognized", no ADB connection - solved...NOT...MAYBE NOW?

When I connect my hero (VillainRom 10) to my PC (Win7 64) all I get is a "USB Device not recognized" error, the phone is being charged, but I get not ADB connection.
Plus, I get the "connect to PC" dropdown on the phone, selecting something (e.g. disk drive) has no effect however.
It really randomly stops working and as randomly works again for a short period of time.
I have tried different USB ports, the cable that shipped with the Hero and a normal miniUSB cable, HTC drivers and those that come with the SDK, removing battery while connected, restarting Phone and PC etc etc.
Once I saw that some dust gathered in the Hero's USB port, so I removed it and it worked after that. Some time later it stopped working however and I can't get it working again although everything is perfectly clean.
This is especially annoying since I started developing a game for Android and debugging is almost impossible now :[
All help is greatly appreciated!
Have you tried...
adb kill-server
adb start-server
(adb devices)
I had the same issue under Linux, where this helped, I don't know about Windows though (doesn't hurt to try though)
I had this the other day, go to Device Manager, find the ADB device, and then get it to download drivers of the net. For me, the drivers downloaded where for the HTC Dream, but still, it worked and now I have the ADB connection works
Hope this helps
I had a similar problem and I solved it by installing HTC Sync.
^ +1
installing HTC Sync worked for me
Thanks for all those tips, but I actually tried all of them, restarted adb server, I can't load new drivers via device manager because my Hero is not being displayed as ADB device but as "Unknown" (but I manually tried different drivers) and I also have HTC Sync installed.
You have some other ideas?
(meanwhile I'll try some stuff myself if I have time)
Could it be the USB cable?
I uninstalled HTC Sync, uninstalled ALL usb drivers (except keyboard and mouse, using usbdeview) installed VillainRom 12 on my Hero, downloaded and installed HTC Sync and 64-bit drivers from softpedia and now it seems to work more or less stable.
I hope it continues to do so and that this here may help someone else!
Argh!
stopped working after reboot...
now it's switching from nothing happening at all when I plug it in, showing me the "Device not recognized" error, or, in very few cases, working for several seconds, then loosing the connection.
I start to believe that this is a hardware defect, but why did it use to work in the past then??
Thanks alot for your help!
Not using a 64 bit machine worked for me. Although it took 5 computers, this fixed the problem for me.
(should note I was also having troubles rooting on my x64 machines.)
Defn shouldn't have upgraded everything to 64-bit. Doh!
Sent from my Super Duper EzHero using XDA App
Tried on a 32-bit XP laptop - didn't work :[
but thx
edit: tried on another win7 x64 laptop - nothing happened at all !?
i've been on ALL the same problem with you
and i'm tiring to find the way out
hope anyone can help us too....
Good to hear I'm not alone! Let me know if you find out something (whatever it is)!
2 days ago it suddenly worked perfectly as if nothing had happened all the while.
programmed happily... next day pc boot - good ol' "device not recognized"
it seems to be exactly this problem:
http://blogs.msdn.com/b/usbcoreblog...cted-or-comes-up-as-unknown-device_3f00_.aspx
now I/we need to find out what causes this on the hero
somthing that could have to do sth with it working 2 days ago is that my hero's battery was completely drained and it was force-shut down. Only after attaching power I could boot the hero. Then also the usb connection (with adb) worked.
very strange...
edit:
someone else seems to have the exact same problem on linux (so it's os independant)
http://forum.xda-developers.com/showthread.php?t=653295
another guy with a potentially interesting solution in post #7
http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7211035
which leads to this:
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
(I will try it nao
update: got it working (let's see how long by doing the following)
(you'll need the android sdk for it)
shut down hero
remove and reinsert battery
boot into fastboot (Hold [back] and [power] key)
open cmd
cd into the andoid sdk tools dir (for me cd C:\android-sdk-windows\tools)
exectute "fastboot oem boot"
let hero boot
now you should have at least adb connection, now unplug and plug hero and you should have full connection (sd-card, whatever you want)
if that didn't help you can try the stuff from this link (posted that earlier already):
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
(I had planned to do all the steps, but the first one already fixed it - strange)
edit:
works on 1 other PC I've tested so far - will try our car's pc next
update: stopped working again, not even fastboot was able to connect
removing the battery while in fast boot while being plugged to the pc and reinserting the battery fixed it
strange strange...
Remove phone from PC
Uninstall htc sync
Run usbdeview-x64 and remove any htc (or unrecognised usb devices)
Restart
Reinstall HTC Sync - latest version .33 or something
Plug in phone (allow it to get drivers from windows update etc, if not use the ones in the HTC Sync folder)
I did this several times but it didn't help as my problem is a problem of the hero, not of the pc not finding the right drivers.
Send it back for repair then...
I will first try fixing it myself

[Q] help for nook touch rooting from China

Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
I've been thinking about this, and if I could just set up the android version of astrill directly in the micro sd (directly set up on nooter) I could then access youtube and finish the job properly.
Do you know if it's in any way possible to do that?
I wonder if you'd be able to use Orbot to be able to gain access to Youtube...
Karibou3 said:
Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
Click to expand...
Click to collapse
Read this, its all contained on my manual tutos, adb is gained just by changing uramdisk, there is one for wifi and another for usb, please, check which one you are using, then, follow this:
Here there is a list of all the tutos:
http://forum.xda-developers.com/showthread.php?t=1380400
and here the ones you should read:
Setting up adb manually on the nook touch:
Making the manual process LESS PAINFULL
Setting up root access on NST through adb and installing busybox:
Hope it helps.
For the youtube thing, just set adb correctly (when you get it right) sideload an app to use a proxy, or tor, or anything you like, and try to login on Youtube.
I'm really sorry for not responding to this
I managed to get it rooted in the few days after my post, and I didn't any email notifications of your replies (didn't check on control panel, i'm new here, please don't hurt me )
I found a chinese source for rooting (a seller on taobao.com explained it. The Chinese are quite fond of the nook because it's the only foreign e-reader you can use to read Chinese apparently, and Chinese e-readers are both more expensive than the nook AND crappy.
Anyway I painstakingly translated it and got it to work
what you tell me about the proxy is new to me though, I thought android couldn't run a proxy, that's great news not just for youtube but the zillions of website China blocks and that I could use my nook to check, I'll have a go at it when I get near a wifi network.
cheers

[Q] Nexus 4 no longer recognised as a device on Mac OSX

Hi Folks,
I've been unable to sync photos to iPhoto on my Mac (10.9.2) for a few months now. Decided to upgrade to latest 4.4.2 (update from google) but it's still not recognized as a device. As far as I remember if I had it in MTP mode, when I plugged the phone in iPhoto used to open with options to sync photos.
I previously rooted the phone with CWM and SuperSU, the device does appear in the list when I run:
$ ./adb-mac devices
List of devices attached
01637f56g7814390 device
When USB debugging is turned on, a message "USB debugging connected" appears on screen, but iphoto doesn't see the device, and nothing in Disk Utility either. Android File transfer says: "No Android device found".
Any help to get photo sync / file transfer operational again much appreciated.
Thanks
The 4.4.2 update seems to be fine, haven't noticed anything weird, certainly no 'bricking', it's the photo syncing / device detection that still doesn't work (it wasn't syncing before the upgrade). I'm looking for some troubleshooting ideas, like log files to look at, or some options to try. I've tried several usb cables, same result.
[Edit: the poster I was replying to deleted their comment about their phone getting bricked, oh well]
Found the option, it's buried in
Settings>Storage>...Menu>USB computer connection>Camera (PTP)
very intuitive thank u google
Hopefully this will be helpful to someone else out there

Need to bypass lockscreen/gain access to adb - Broken screen

So I have a bit of an issue. Somehow last night, after trying to help my parents with our home theater system, with the device laying on a soft surface, the LCD (not the glass) somehow broke. I am really not sure how this happened, the phone itself didn't fall, it was laying on a bed the entire time. When I went to grab the phone and turn it on, I was pretty surprised. You can see what I mean in the attached file.
Now the problem with this is, while I would normally just walk into the Sprint Store, complain and get a new phone. I am not in the US for another 5 months. In the mean time of trying to figure out what to do, I would like to at the very least, grab any files off my phone, or back up my phones' file structure.
I am able to do a minimal amount of tapping on the phone, only on the upper half of the screen, but I can't see anything, nor does the device respond with any touch data from the bottom half.
I obviously can't access the files if the device is locked, which means I have to bypass the lock screen. I found this guide, but unfrotunately, Method 1 didn't work, and I can't get adb to recognize my phone for Method 2.
I also have tried using CWM (the non-touch version) to backup my data, but I let it sit there for 45 minutes and I couldn't tell if it was finished or not. It didn't appear to actually be doing anything.
Could someone help me navigate around this or provide some assistance in allowing me to just get the files off the phone while I search for a new one?
With that being said, does anyone have some recommendations? I was thinking of getting a Motorola X or Nexus 5.
EDIT: Update:
I have access to terminal via Cerberus shell. I was able to use Method 2 to disable the lock screen (or in this case set it to Swipe). It is still pretty difficult to use the phone but I can at least backup whatever data I still do have on the phone to my laptop.
Would anyone be able to give me some advice as to uninstall applications or XDA xposed modules via shell? Or perform a backup or enable ADB debugging?
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Darnell0216 said:
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Click to expand...
Click to collapse
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
slixzen said:
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
Click to expand...
Click to collapse
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Darnell0216 said:
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Click to expand...
Click to collapse
I have a sony xperia P that I am using right now until the replacement phone I got arrives. Any idea how I could use that? I have had minimal success with the phone so far in trying to get that phone to flash custom recoveries, to root the device (not sure why, but my laptop just doesn't want to seem to do it, even using automated tools).
Is it better to just wait for the replacement phone to arrive and grab what I need from that and push it? Could you link me to any guide or steps that you used with yours?
Thanks for such quick responses by the way!
EDIT:
Flashing TWRP and booting into recovery with command prompt open and running adb devices / fastboot devices does not show any devices available.
Is there a specific menu setting or other option I need to use to be able to run adb?
When you use TWRP, the phone will be recognized by the PC but the driver doesn't install correctly off the bat. Go to Device Manager and look for your phone. You may need to click the View -> Show Hidden Devices option. Update the driver manually by selecting the one provided by your manufacturer. Some have a dedicated ADB driver for specific functions (bootloader, etc).
The adb key is stored in data/misc/adb/adb.keys -You can pull this file from any other android connected to that PC (or just copy it if you have a root explorer) and push it to the broken one if necessary. This will bypass any ADB authorization issues while the phone is fully booted and let you see the screen.

SM Bus Controller failed to install Win7 x64

I'm trying to use LG PC Suite and LG Bridge on a laptop running Windows 7 x64 Pro. I have updated the chipset with the latest driver, but every time I try to install the LG drivers, the SM Bus Controller fails to install. The PC cannot see the device, even though I have switched USB mode to file transfer. I have a Mac as well, and the same thing happens there (not recognizing the device is connected via USB). Is the software just way out of date and not yet compatible with the V20, or is there a fix that needs to happen. I'm perfectly comfortable using the command line/terminal or hacking the registry, if that's what it takes...
Thanks to anyone that can help!
I did remove the SM Bus Controller from device manager and then re-installed the LG device driver. It did not attempt to reinstall SM Bus drivers, but instead installed MTP drivers successfully. I had high hopes after that, but it's still not working. Sigh.
bgibson72 said:
I'm trying to use LG PC Suite and LG Bridge on a laptop running Windows 7 x64 Pro. I have updated the chipset with the latest driver, but every time I try to install the LG drivers, the SM Bus Controller fails to install. The PC cannot see the device, even though I have switched USB mode to file transfer. I have a Mac as well, and the same thing happens there (not recognizing the device is connected via USB). Is the software just way out of date and not yet compatible with the V20, or is there a fix that needs to happen. I'm perfectly comfortable using the command line/terminal or hacking the registry, if that's what it takes...
Thanks to anyone that can help!
Click to expand...
Click to collapse
What are you trying to accomplish?
Have you installed minimal adb\fastboot?
Frankly, I don't use Windows or Mac so I am next to no help there.
'Sudo pkg install android-tools-adb android-tools-fastboot' was all I've needed to do.
Is your usb a known good cord? Verify this first. Then, Windows device manager, plug in your phone, watch for something to show on device manager. Click on device, double check there that everything shows as working properly?
If phone is not showing up on a number of computers, make sure USB cable is good.
elijah420 said:
What are you trying to accomplish?
Have you installed minimal adb\fastboot?
Frankly, I don't use Windows or Mac so I am next to no help there.
'Sudo pkg install android-tools-adb android-tools-fastboot' was all I've needed to do.
Is your usb a known good cord? Verify this first. Then, Windows device manager, plug in your phone, watch for something to show on device manager. Click on device, double check there that everything shows as working properly?
If phone is not showing up on a number of computers, make sure USB cable is good.
Click to expand...
Click to collapse
I have adb and fastboot both. I want to connect to the PC/Mac for purposes of synching/sharing music, photos, etc. I could use linux too, but I don't have an VM's or a box spun up with anything atm. Yes, the cord I'm using is a good cord. I can see the internal and SD card when I connect, just can't use the LG apps. Oddly enough, there wasn't anything showing with the yellow sign under Device Manager. I'm guessing it's just a compatibility issue and I should just forget about it and just push files to my device with adb. Oh well--I thought it was worth a shot.
bgibson72 said:
I have adb and fastboot both. I want to connect to the PC/Mac for purposes of synching/sharing music, photos, etc. I could use linux too, but I don't have an VM's or a box spun up with anything atm. Yes, the cord I'm using is a good cord. I can see the internal and SD card when I connect, just can't use the LG apps. Oddly enough, there wasn't anything showing with the yellow sign under Device Manager. I'm guessing it's just a compatibility issue and I should just forget about it and just push files to my device with adb. Oh well--I thought it was worth a shot.
Click to expand...
Click to collapse
I understand now. I don't think I can help you there. I run an owncloud instance, and just back all my hooey up there.. manually tho. Sorry dude.
elijah420 said:
I understand now. I don't think I can help you there. I run an owncloud instance, and just back all my hooey up there.. manually tho. Sorry dude.
Click to expand...
Click to collapse
It's cool, thanks anyway. Just trying to simplify things. Don't ask why I thought the OEM's software was gonna solve that, lol.
Well, tbf, even though I don't use it (simply because I dislike vendor lock in - owncloud or a sftp session is mostly hardware agnostic.) I do understand the idea that one should expect the **** that come on the phone to work properly. It *should* be a selling point - 'our apps work for their stated purpose!'

Categories

Resources