[Q] My phone only boots into bootloader - Nexus 4 Q&A, Help & Troubleshooting

My phone was updated to 5.1 a week ago. Its stock not rooted. I was watching netflix and it got stuck so I pressed power button 10-15 seconds to turn it off. Tried to turn it on and now it only boots into bootloader .Blank screen if I try to open recovery. I am using windows 8.1 ,tried to install universal naked drivers and Skipsoft unified android toolkit but still my computer does not detect my phone. So I cannot do anything without my pc detecting my phone. Please help!.

nilay4232 said:
My phone was updated to 5.1 a week ago. Its stock not rooted. I was watching netflix and it got stuck so I pressed power button 10-15 seconds to turn it off. Tried to turn it on and now it only boots into bootloader .Blank screen if I try to open recovery. I am using windows 8.1 ,tried to install universal naked drivers and Skipsoft unified android toolkit but still my computer does not detect my phone. So I cannot do anything without my pc detecting my phone. Please help!.
Click to expand...
Click to collapse
Does your PC even detect that you plugged in your phone? A notification sound?

Flash Me Dead said:
Does your PC even detect that you plugged in your phone? A notification sound?
Click to expand...
Click to collapse
not it doesn't not, not even a sound, i tried to connect to a different pc also no help.

nilay4232 said:
not it doesn't not, not even a sound, i tried to connect to a different pc also no help.
Click to expand...
Click to collapse
Is that also running Windows 8.1? I don't have experience with 8.1 but I've heard it causes problems detecting devices. Try Windows 7, if it still doesn't pick up a sound, check your USB drivers under Device Manager. Make sure 'Google Nexus ADB is listed.'

Flash Me Dead said:
Is that also running Windows 8.1? I don't have experience with 8.1 but I've heard it causes problems detecting devices. Try Windows 7, if it still doesn't pick up a sound, check your USB drivers under Device Manager. Make sure 'Google Nexus ADB is listed.'
Click to expand...
Click to collapse
I tried it with windows 7 too , no sound or whatsoever. I am guessing internal sd card is dead or something.

nilay4232 said:
I tried it with windows 7 too , no sound or whatsoever. I am guessing internal sd card is dead or something.
Click to expand...
Click to collapse
I'm assuming you are on stock ROM with locked bootloader? It's possible when you manually powered down your phone it corrupted your ROM and recovery along with it.
This is a long shot but try to uninstall skipsoft and naked drivers. Install Android SDK. Have a read through this http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro. If you can get fastboot to register then your phone may be saved yet. Or if you already tried all this and it still doesn't work then there's nothing more I can assist you with. Good luck.
FMD

Flash Me Dead said:
Is that also running Windows 8.1? I don't have experience with 8.1 but I've heard it causes problems detecting devices. Try Windows 7, if it still doesn't pick up a sound, check your USB drivers under Device Manager. Make sure 'Google Nexus ADB is listed.'
Click to expand...
Click to collapse
Just FYI, on Windows 8.1, the issue you heard about had to do with MS pushing an Asus Generic USB Driver update which was the cause of the issue. Here is the fix: http://www.eightforums.com/drivers-...usb-issue-since-last-windows-8-1-updates.html

Related

Unable to see phone when in download mode

I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
I was having a similar issue with my MBpro, nothing would recognize my phone. Tried it on another comp and bingo. I think stuff is just finicky with USB ports. Lame-o.
ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
when did u plugg ur phone in dowload mode?
try this ... load odin ... turn ur phone off!!! plugg it to the computure so when u see its charging for 30 sec. Then put the cellphone into download mode... and that should work
maldito.boss said:
when did u plugg ur phone in dowload mode?
try this ... load odin ... turn ur phone off!!! plugg it to the computure let it charge for 30 sec and the put it into load mode... that should work
Click to expand...
Click to collapse
Yea...this post made my brain hurt...and of course didn't change anything...but..thanks?
Here's another piece of info that may help nail down the problem...
Odin is able to see the phone if I boot into Clockwork recovery mode but because clockwork is up the phone can't receive a flash but Odin does see the phone with no problem. It just still won't see the phone when booted into download mode.
ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
I use windows7 64 too. I encountered tons of problems when trying to flash my epic. first my computer doesn't recognize my phone in download mode. after i wipe out all the drivers and reinstall them. finally i get my computer recognize it under download mode, but Odin froze every time during the flash.
Finally, i tried on another desktop computer with windows XP. Everything went perfectly. So maybe you should try that too.
I cannot connect to my Epic in download mode on mac os x either.
I was trying to install a lag fix, and now all my phone will do when powering on is show switch between the normal Samsung screen, and another reading "Samgung GT I9000".
I can still boot into Clockwork Recovery. But OS X will not recognize my phone.
Either that, or Heimdall isn't recognizing it and won't let me flash.
Help! Any ideas?
Pirate-M.Lifnen said:
I cannot connect to my Epic in download mode on mac os x either.
I was trying to install a lag fix, and now all my phone will do when powering on is show switch between the normal Samsung screen, and another reading "Samgung GT I9000".
I can still boot into Clockwork Recovery. But OS X will not recognize my phone.
Either that, or Heimdall isn't recognizing it and won't let me flash.
Help! Any ideas?
Click to expand...
Click to collapse
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.
Pirate-M.Lifnen said:
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.
Click to expand...
Click to collapse
I had the same problem, I couldn't connect it to 3 of my pc's. 2 xp's and one windows 7. Turned out the port on the phone it self was broken, had to take it sprint and get it replaced.
Pirate-M.Lifnen said:
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.
Click to expand...
Click to collapse
If OS X isn't recognising your phone it's likely your phone has the buggy secondary bootloader. Samsung corrected the bootloader for at least the GT-I9000 JPA firmware but I'm unsure if they have done so for other devices or firmware releases.
Unfortunately the only solution then is to use Windows or Linux. If you don't have access to a system running either of these OS then I recommend downloading a 64-bit release (assuming your PC has a 64-bit CPU) of Ubuntu, then you can download the Heimdall binaries from my website and use it to recover your phone.
i had an extremely similar issue as to what you are having. I have 3 win 7 machines and 1 xp, none worked. I went to a friends house he has 2 win 7s and an xp also didnt work. I did a general search and found all kinds of crap. One dude something about using his chicks blackberry usb cord and suddenly it worked on any and all of the machines it had previously not worked. so at the time im reading this on my chicks laptop which has a damn blackberry cord attached to it chargin her evo(go figure) ... anyway u didnt need the whole story but i have nothing to do right now.
Point is everyone says try different cords, i say try the damn blackberry cord if you happen to have one or a friend that has one.
Benjamin Dobell said:
If OS X isn't recognising your phone it's likely your phone has the buggy secondary bootloader. Samsung corrected the bootloader for at least the GT-I9000 JPA firmware but I'm unsure if they have done so for other devices or firmware releases.
Unfortunately the only solution then is to use Windows or Linux. If you don't have access to a system running either of these OS then I recommend downloading a 64-bit release (assuming your PC has a 64-bit CPU) of Ubuntu, then you can download the Heimdall binaries from my website and use it to recover your phone.
Click to expand...
Click to collapse
Is it the hardware on the Macbook pro itself? or just the OS? in other words, If I were to partition my macbook with ubuntu would that work with heimdall? would it be able to recognize my phone while it's in download mode as opposed to OSX, which couldn't...?
ldartez said:
Is it the hardware on the Macbook pro itself? or just the OS? in other words, If I were to partition my macbook with ubuntu would that work with heimdall? would it be able to recognize my phone while it's in download mode as opposed to OSX, which couldn't...?
Click to expand...
Click to collapse
In this particular instance Apple haven't done anything wrong at all, both their hardware and software is fine. The issue is that Samsung are distributing secondary bootloaders that aren't complaint with the USB specifications.
Whilst that is annoying, the good news for you is that you can simply install Linux (Ubuntu etc.) or Windows on your Macbook and you'll be able to flash just fine.

cant access usb storage

When I plug it into my PC, the phone starts charging but there is no option to mount the USB storage...
any ideas?
waylman said:
When I plug it into my PC, the phone starts charging but there is no option to mount the USB storage...
any ideas?
Click to expand...
Click to collapse
THANK YOU!!! I've been waiting for someone else to have the same problem!!! I'm relieved it's not just mine. I'm assuming you did a manual install also? Is yours rooted? One person suggested ClockworkMod but I'm a little nervous about rooting. I've been doing the manual installs but that's as for as I wanna go. I can't stand the idea of bricking my phone.
My phone is new out of the box!
I found that on two Windows XP machines USB storage doesn't work. I then plugged it into a Win7 box and it worked perfectly. I also used a different cable with the Win7. Try a different cable and try Win7.
waylman said:
My phone is new out of the box!
I found that on two Windows XP machines USB storage doesn't work. I then plugged it into a Win7 box and it worked perfectly. I also used a different cable with the Win7. Try a different cable and try Win7.
Click to expand...
Click to collapse
I have Windows XP on my work PC and Windows 7 Premium 64 on my home notebook and the USB worked fine on 2.3.3. Every since I did the manual install of 2.3.4 the USB functionality is gone. I'm thinking maybe the ROM is used wasn't incomplete. It's beginning to look like the only way to fix this is to root my phone
FWIW I did the manual update (full rom) and USB storage works fine on my Windows 7 Ultimate x64 box.
Haadkoe said:
FWIW I did the manual update (full rom) and USB storage works fine on my Windows 7 Ultimate x64 box.
Click to expand...
Click to collapse
Yeah, I'm thinking maybe the one I installed wasn't the full ROM. As soon as I see people saying it works great I go ahead and use it. Do you know of any possible fixes without rooting?
No first hand experience, but would it be possible to download the full rom and manually flash it again?
Sent from my Nexus S using XDA App
Haadkoe said:
No first hand experience, but would it be possible to download the full rom and manually flash it again?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Trying to figure that out. I've been told try ClockworkMod and go back to 2.3 but I'm trying to do it without rooting.
Try a different USB port
If the update was incomplete, the update would have failed the signature check. The first time I connected my Nexus S after manually patching to 2.3.4, Windows 7 Professional X64 did not detect it when connected. I unplugged it and used a different USB port and it worked. I then tried the original port and it also worked. I would try a different USB port and a scan in Device Manager before changing the ROM.
SpookyTunes said:
If the update was incomplete, the update would have failed the signature check. The first time I connected my Nexus S after manually patching to 2.3.4, Windows 7 Professional X64 did not detect it when connected. I unplugged it and used a different USB port and it worked. I then tried the original port and it also worked. I would try a different USB port and a scan in Device Manager before changing the ROM.
Click to expand...
Click to collapse
I also have Windows 7 Prof. 64 bit, but switching to different ports didn't work. It won't install the drivers. What else could that mean if it isn't the ROM?
I had this problem immediately after flashing CWM.
I booted into the ROM, then, while the USB was plugged in, powered off the device, and turned it back on. It then seems to work everytime I turn on the device, as long as I don't boot into recovery.
Me too
.
I had a the same problem with my SGS.
The trick for me did: disable usb-legacy-support in your motherboard-bios.
Have you tried re-installing USB driver from the latest android SDK?
Kind of strange, it was working great yesterday and today couldn't connect. Right clicked on android_winusb.inf and selected install and it started working again. Not sure what could have changed from one day to the next. But at least I know what to do when it happens again.
suksit said:
Have you tried re-installing USB driver from the latest android SDK?
Click to expand...
Click to collapse
Never tried that. Doesn't that involve rooting or unlocking the bootloader? Both of those wipe the USB storage.
derekwilkinson said:
I had this problem immediately after flashing CWM.
I booted into the ROM, then, while the USB was plugged in, powered off the device, and turned it back on. It then seems to work everytime I turn on the device, as long as I don't boot into recovery.
Click to expand...
Click to collapse
Don't have a custom ROM. All I did was manual bootload 2.3.4 on stock Android. The weird thing is when it's plugged in(charging only) and I turn it off, it starts to power down and then freeze. The screen doesn't go black until I pull it out. Then when I plug it back in it automatically powers back on. Basically, I can't seem to plug it in while it's powered off.
I have no idea why but my suddenly works again. Im happy but confused
You shouldn't need any drivers at all for windows XP vista 7 ect. Mounting your SD card, using flash drives... all use the same USB mass storage divice driver built into windows.
Sent from my Nexus S using XDA App
suksit said:
Have you tried re-installing USB driver from the latest android SDK?
Click to expand...
Click to collapse
Yes, I just tried this. It still doesn't seem to work. It keeps saying my drivers are up to date but it's still not connecting to my USB storage.

Focus 1.3 bricked

Hi there.
I had Focus 1.3 with official at&t windows phone 7
After I tried to install MAGLDR, it became a brick((
Now it doesn't respond to any keystrokes, charging, or connecting to PC..
Can I do something with my phone without jtag?
I have one more Focus 1.3, WORKING
If the second one could help to restore first, it will be beautiful.
follower90 said:
Hi there.
I had Focus 1.3 with official at&t windows phone 7
After I tried to install MAGLDR, it became a brick((
Now it doesn't respond to any keystrokes, charging, or connecting to PC..
Can I do something with my phone without jtag?
Click to expand...
Click to collapse
Even I had my FOCUS bricked yesterday but brought it back to life using WP7 Downloader.
When I had plugged it into PC, I checked device manager and luckily it showed up there So i followed this Youtube video(http://www.youtube.com/watch?v=YJVo68x5DDQ) and flashed an ATT Rom and it started working :good:
I am not so lucky((
follower90 said:
I am not so lucky((
Click to expand...
Click to collapse
Try it in different USB ports. I'm sure that it will show up in the device manager. While using WIN7, when an external device is detected it makes a small sound that is your hint that it has been detected actually this sound from windows was the very thing that prompted me to check Device manager

[Q] USB and recovery problems after OTA upgrade to 4.3

I took the OTA to 4.3 on my Nexus 7. It was previously unlocked and rooted, but had no kernels, etc changed. After the update ran, I lost root as expected, however, in trying to get it back, I've discovered I'm having a couple of other issues.
First, the device is no longer working properly via USB on my PCs. On both my Win 7 and Win 8 PCs, the device won't properly connect to where I can browse files or anything else. On the Win 8 computer, I see a Nexus 7 device in Device manager, but drivers won't install. I downloaded the drivers from the Asus site, but trying to manually install them doesn't work on the Win 7 machine, and on the Win 8 machine, they install but don't seem to be working with the Nexus 7 as it still shows a problem in Device Manager.
The tablet also will not boot into recovery mode. I can power it up into fastboot mode, but if I select "Recovery Mode" and hit the power button, I just got the Android with the red triangle for a few minutes before it boots back into the OS. After doing some searching, I saw where you might need to have it plugged into a PC to get it to go into recovery, but that doesn't work, either (might be tied to the USB problem).
Ideas?
Did you turn on developer options, and USB debugging? Have you tried USB connection type PTP instead of MTP?
If you have the stock recovery, the red triangle and Android are normal. You can bring up a blue options menu by pressing the power and volume up buttons from the red triangle Android.
Sent from my rooted Nexus 7 @ 49.4 mpg
exglynco said:
Did you turn on developer options, and USB debugging?
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
Yes.
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
exglynco said:
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
I was using the stock drivers off the Asus page. I'll look around for the two you mention. I assume they're posted on here somewhere.
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Red Devil said:
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Click to expand...
Click to collapse
Without USB access? That's my dilemma.
OK, I'm getting closer. I got TWRP installed and rerooted it. I had to do the "Revoke USB debugging authorizations" on the Dev Options screen. Then it would work via ADB.
Still not browsing files yet on my desktop, but at least I know I'm talking to it. So now I'll play with the driver installation a bit.
EDIT: Well, drivers reinstalled for about the 4th time, and it's still not allowing me to browse files from my desktop. Galaxy S4 works fine as soon as I plug it in, even if I also uninstall it's drivers. Ideas? I obviously have it working over USB because I can give it commands and reboot it via the PC.
OK, try this one. Plug in your tablet to pc, go to hardware manager, find your Android Device then choose Uninstall (choose Remove all drivers for this device), unplug and plug in your tablet again. Your Windows should discover few new devices (mine has discovered three) and download drivers for them then you should see Android ADB Interface in Android Devices and Nexus 7 in Mobile Devices.
--edit--
I've solved my issue
http://forum.xda-developers.com/showthread.php?p=44322739#post44322739
Already been done that road multiple times.
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
xxut said:
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
Click to expand...
Click to collapse
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I personally did all of those things. After having the Nexus "forget" all the other PC authorizations on the dev screen, I finally got it to accept ADB commands, just not to properly install drivers that would allow me to browse files like it had done on 4.2.
SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
xxut said:
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
Click to expand...
Click to collapse
Try turning off usb debugging. My tablet cannot connect to pc but with usb debugging off it at least recognises tablet as a media device and this enables me to view its files
.but still the problem of not being able to root

KitKat on Nexus 7 Failes

My problem is basically getting my nexus 7 to connect to the pc... This is what I've done. and what happends...
When I first connected it, I got no message at all, and nothing happened, then I changed the cables around, I changed the USB Pports... and by some mysterious wounder I found a combo of pad, port and cable that made my nexus go your connected as MEdia Device... BUT my computer wont see it.. hmm.. changed it to camera mode, and still nothing. Then I turned off USB Debug. Still nothing, but wen I turned it back on, I got the message that I was connected, and I got to install some drivers, and NExus popped up as a camera in windows 8... Started up the nexus toolkit thingy (I love simplicity) And there it popped up.. rebooted to fastboot, and no luck... windows wont recognize the damn driver. And I have done everything I can think of except install linux and try it there... IT wont connect in Fastboot mode, Not a chance... I've tried to unindatll all the drivers, and their files. everything I can think of... I've followed like 20 diffrendt howto s on the same problem, and no luck...
So how would a guy like me go about doing this in linux... is there a tool made for it? Do I need to do it all by commands? Is there a howto?
In my win8 64bit the nexus 7(2012) does show up as a portable device, but MTP works and there's no issue with sending or pulling files. currently it's running stock kitkat 4.4 (KRT16S).
like you I suspect it's a driver issue with windows. If you could locate the device on device manager (try View\Devices by connection and look under PCI Express Root Complex and comb for USB Host Controller\USB Root Hub\Generic USB Hub), delete the entry for Nexus7 and scan for hardware changes again. This forces the system to look for correct driver(s) for your nexus.
Some guides on updating drivers are in fact concerned with the ADB interface, which is needed for USB debugging. In your case, if it's just accessing the internal storage of your Nexus you want to solve, those info may not be relevant.
krrasmuss said:
My problem is basically getting my nexus 7 to connect to the pc... This is what I've done. and what happends...
When I first connected it, I got no message at all, and nothing happened, then I changed the cables around, I changed the USB Pports... and by some mysterious wounder I found a combo of pad, port and cable that made my nexus go your connected as MEdia Device... BUT my computer wont see it.. hmm.. changed it to camera mode, and still nothing. Then I turned off USB Debug. Still nothing, but wen I turned it back on, I got the message that I was connected, and I got to install some drivers, and NExus popped up as a camera in windows 8... Started up the nexus toolkit thingy (I love simplicity) And there it popped up.. rebooted to fastboot, and no luck... windows wont recognize the damn driver. And I have done everything I can think of except install linux and try it there... IT wont connect in Fastboot mode, Not a chance... I've tried to unindatll all the drivers, and their files. everything I can think of... I've followed like 20 diffrendt howto s on the same problem, and no luck...
So how would a guy like me go about doing this in linux... is there a tool made for it? Do I need to do it all by commands? Is there a howto?
Click to expand...
Click to collapse
Installing fresh SDK won't hurt.
holynoob said:
Installing fresh SDK won't hurt.
Click to expand...
Click to collapse
The USB drivers are available in a zip file here: http://developer.android.com/sdk/win-usb.html
and instructions are here:http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
For drivers and devices on your system browse http://www.nirsoft.net/ for the free utilities
DriverView
USBLogView
DevManView
USBDeView
Update
peterk-1 said:
The USB drivers are available in a zip file here: http://developer.android.com/sdk/win-usb.html
and instructions are here:http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
For drivers and devices on your system browse http://www.nirsoft.net/ for the free utilities
DriverView
USBLogView
DevManView
USBDeView
Click to expand...
Click to collapse
Basically I would like to have ¤.¤ installed on my Tablet. Right now I have 4.2.2 SmoothROM installed, and whilst this works for me, I'd like to get the update.
In the past, I used the Toolkit to root and install stuffies... Until the last update to SmoothROM wheres I used GooManager thingy...
When I started this I got the Tablets to connect using PTP whilest in Android, but not in Fastboot mode. So I downloaded the 4.4.kitkat Offisial ROM and tried to install that in recovery, after a full wipe, BUT that ended in me having to install SmoothROM again. And now the Tablet wont connect at all... I have deleted all drives, and reinstalled them... I've tried 3 diffrent Wondows USB driver, but no luck there... I've tried like 5 diffrent USB data cables, in all 4 of my USB ports, on 2 diffrent machines, both win 7 and win 8... AND still no luck... now all the machine says that it cannot identfy the device...
Tomorrow, I will end up installing linux, and try there... At the moment I loathe all things called windows drivers...!!!!
EDIT:
Great news... I found a cable, I havent used in a long time. THis is the original cable that came with the Nexus, and I havent used it in a long time because it had some bad connections. Felt like the plug was loose, but now it made the whole thing work without any problems at all...
So I found the cable, used USBDeView to delete all drivers assossiated with the nexus. plugged it in while in fastboot, and BANG installed. rebooted it, and BANG installed.

Categories

Resources