Related
If you want to offer help PLEASE read through the thread, or at least the initial post. It seems like I'm repeatedly answering the same questions that were already answered.
I've tried to boot in APX and all I get is the black screen, yet neither Windows 7 64bit/Linux Mint 64 on one PC and Windows XP on another don't detect it at all. I know the cable works because when I had CWM installed I could see it attached via ADB. I'm a b30
Edit: I managed to get the stock ROM back on it, but it still doesn't want to boot into the bootloader/APX mode. I know it's not necessary but I would like to have it as a failsafe for the future.
brando56894 said:
This all started with me wanting to go back from AOKP to stock, I flashed a rooted version of 9.2.1.17 and it kept telling me to update, but when I did it failed because CWM was installed. It also wiped my system. I found 9.2.1.24 but couldn't flash it because TWRP wouldn't stick. I tried to install the stock recovery, which worked in a sense that it removed CWM but left me with just the Android and the exclamation point (I can't seem to get past that no matter what I do [vol +, Vol -, power or any combination of those] ) I decided to use NVflash to get back to complete stock and start over.... The only problem is that Windows 7 doesn't even detect the TF when its in APX mode, hence it doesn't ask me to install the drivers, nor will they install manually.
So my TF is soft bricked and nothing works. I'm going to reboot into Linux now to see if I can get nvflash working. Any other suggestions?
Edit: Linux Mint didn't detect it either I know it's not the cable since I was able to see the TF via ADB when I had CWM installed. Also the major thing that is worrying me is will the TF be recoverable if the battery dies? I have no way of knowing if it is actually off or just in APX mode, I obviously can't do a battery pull and I can't power it down from the recovery or the OS. IIRC it also won't charge when it is in recovery and I'm assuming the same is true for boot-up and APX mode.
Click to expand...
Click to collapse
Same to me-- win7 does not recognize my tf 101- apx is installed-works with another transformer well- if i do vol down and then vol up i see the laying android with exclamation mark.
no solution till now- hope you had more luck-
By the way- try to load it normal - in my case it works.
kind regards
gandalf
I just tried connecting it to an older Dell with a P4 in it and it doesn't detect it either, it just seems like the TF doesn't want to boot into APX mode. I'm doing Vol + and Power from both the recovery and from the initial splash screen, then it reboots to a black screen which I'm assuming is APX mode. From the black screen I've tried Vol + and Power for as long as 30 seconds and still nothing. There were also times when it would sit at the initial splashscreen and then go to a black screen, then I'd try to enter APX mode from there but it would be the same thing.
I've been contemplating getting a Nexus 7, partially because I lightly stepped on the screen of my TF one night and damaged it enough to cause the LCD crystals to break (there about two or three grayish "lines" where I stepped on it) but not hard enough to crack the glass. The screen will also flicker some times on that side and will also randomly shut the screen off. Maybe this is a sign telling me to get a N7?
Do you have debug mode enabled?
Where did you get the win 7 APX mode software. Some links in this site are to defective software. Go to the SDK kit site and download the software there. http://developer.android.com/sdk/index.html
Rumbleweed said:
Do you have debug mode enabled?
Where did you get the win 7 APX mode software. Some links in this site are to defective software. Go to the SDK kit site and download the software there. http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
Debug mode is for ADB, not APX. Debug mode is set in Android and with APX no Android is loaded.
I have used the live cd of Ubuntu 11.10 without installing any driver by myself. It recognized the TF with APX in my case.
There is no debug mode considering that the OS isn't installed. AFAIK debug mode is only necessary to use ADB while booted into Android. APX is something that is built in to the device. I downloaded the drivers from android.mobi which has an "unroot/unbrick" package, that doesn't matter though because Windows never asks me to install the driver so the drivers don't seem to be the problem, considering Linux (which doesn't require any drivers) doesn't see the device either.
I had the same, downloaded the drivers, but couldn't install.
After I made sure I had the correct drivers, I clicked in hardware settings on the thingy with the exclamation point, I choose manual search and had Windows search the entire c:\ drive, after a while it installed
Sent from my Transformer TF101 using xda premium
That's my problem guys. APX mode/unknown device doesn't show up in device manager
oi, than I cant help you, sorry
I think it's F'ed because I took it apart to make sure it was turned off by disconnecting the battery and then did the power and Vol+ combo but the PC still doesn't detect it.
1. your battary is empty, charge it
2. your battary is done.
3. your power key or vol-up key do not work.
4. you did not press two keys in the same time long enough
5. cable doesn't work
6. usb port doesn't work, try another one.
7. you did not pay attention on the sound of device connected nor the device list.
8. your windows broke. try another pc.
---------- Post added at 11:39 PM ---------- Previous post was at 11:33 PM ----------
get a micro sd and copy rom to it and flash, since you said cwm works ok
vista1984 said:
1. your battary is empty, charge it
2. your battary is done.
3. your power key or vol-up key do not work.
4. you did not press two keys in the same time long enough
5. cable doesn't work
6. usb port doesn't work, try another one.
7. you did not pay attention on the sound of device connected nor the device list.
8. your windows broke. try another pc.
---------- Post added at 11:39 PM ---------- Previous post was at 11:33 PM ----------
get a micro sd and copy rom to it and flash, since you said cwm works ok
Click to expand...
Click to collapse
1 & 2 It boots up to the initial splash screen and to the android recovery so the battery is ok
3. The Vol + does work unless it suddenly died because I was using it moments before I bricked it
4. I would say 30+ seconds is long enough
5. The cable does work because it charges the unit and when I had CWM installed I could see it via ADB
6. Tried another port, nothing
7. The sound is definitely noticeable and it's kind of obvious if it's not in the device manager list
8. I tired two different computers, and three different operating systems. Including Linux.
I know you are trying to be helpful but ALL of these were answered in previous posts, if not the OP.
I'm having the same issue with my pad not booting into APX, might I ask how you got the stock ROM back on it without APX?
Luckily I had the stock recovery installed and I was able to place the OTA on A MicroSD card and named it so that it would flash automatically once I booted into the recovery.
Sent from my Transformer TF101 using Tapatalk 2
Edit: here's how to do it
baseballfanz said:
Download the latest official firmware from Asus.
Extract the zip from within and rename it to "EP101_SDUPDATE.zip" (without the"" )
Put it on the root of your sdcard
Boot into stock recovery and it should flash it
Click to expand...
Click to collapse
I have to go with #5. My Transformer would charge when using my cord and so I thought it was good. Plugged it into the computer and nothing. Switch to my wife's cord and the computer saw it instantly. It was then able to see APX mode.
Yea it was actually the cord being stupid, when I got back to my house I tried my other cord and it connected just fine. I actually just sold my TF yesterday to a friend for $250 so that I can get a Nexus 7
Sent from my ADR6425LVW using Tapatalk 2
So this is making me thing that my cord is the issue, but I tried 3 different cords and none of them recognized. Is it possible the device itself has a faulty connection?
It's entirely possible, have you tried a different computer/different USB ports first though?
Tried every port on two machines as well as in linux. My HTC G2 connects just fine to everything.
You may be screwed Do you have the dock? Does it connect and charge fine with that?
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
So I am installing the Nexus 7 in my car as the head unit, but am now stuck with this issue.
I unlocked, and rooted the device, and used the fastboot oem off-mode-charge 0 command and it worked.
Anytime the Nexus 7 receives power it turns on.
However the device battery died completely and now when I plug it in to charge, the screen stays black, buttons do nothing, and eventually it boots up, but immediatley powers off as the battery is at 0 % and has the red ! mark.
I can't even use the fastboot command to reverse it since the device can't stay on.
What the heck can I do?
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Username invalid said:
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Click to expand...
Click to collapse
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
@Username invalid
Yes, but will the command be executed before the device dies again?
---------- Post added at 09:46 AM ---------- Previous post was at 09:44 AM ----------
When you're in bootloader, you don't need debugging enabled since the fastboot protocol comes into play, not ADB (which requires debugging to be enabled). Root is also unnecessary. At least that's what I have learnt in the past 5 months I have had this.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
sgt. meow said:
@Username invalid
Yes, but will the command be executed before the device dies again?
Click to expand...
Click to collapse
There is not enough time for me to set debugging on before the device dies. It stays on for maybe 5 seconds at the home screen then powers off.
Is there a way I could charge the battery a little bit bypassing the Nexus?
Can I splice in the pos and neg of the usb charger to the pos and neg of the battery?
I'd highly discourage the battery direct charging bit.
Username invalid said:
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
Click to expand...
Click to collapse
I'm not sure at all.
I used the R3 Nexus 7 Superboot to push the original command. I had downloaded fastboot from somewhere else, and put it in the Superboot folder to get it to push the command.
By the way sorry for taking so long to reply in between. Since I am a new user, I have to wait the 5 minutes in between posts.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Username invalid said:
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Click to expand...
Click to collapse
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Jeremi1023 said:
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Click to expand...
Click to collapse
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I will do that and let you know what I see.
Just gotta wait for the thing to turn on. It's very random right now.
Okay, I was able to get into bootloader, and I I did "fastboot devices" and nothing came up.
Also checked device manager and no Android or anything like it in there.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Jeremi1023 said:
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Click to expand...
Click to collapse
http://d-h.st/kDu
Username invalid said:
http://d-h.st/kDu
Click to expand...
Click to collapse
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Jeremi1023 said:
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Click to expand...
Click to collapse
Uninstall your current one first.
Username invalid said:
Uninstall your current one first.
Click to expand...
Click to collapse
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Jeremi1023 said:
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Click to expand...
Click to collapse
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Username invalid said:
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Click to expand...
Click to collapse
Yeah I have a desktop I could try it on.
I've never plugged the Nexus in to the desktop, so it should be a complete clean install of drivers.
If Windows recognizes the nexus on the desktop, what should I do?
Do I need to uninstall anything it may install on its own?
I figure I will end up installing the drivers you previously provided.
Hi,
I tried a lot of other rooting applications and have had no luck with any of them. Then I found Wug's Nexus Root Toolkit. It works for my Nexus 4 (Jelly Bean 4.3) - until I came to the "Full Driver Configuration Guide" - where it gives a message: "ADB device was not found".
I have tried it over several times to no avail. Can anyone offer any clues as to what may be causing this?
btw, I am running the Wug's Nexus Root Toolkit v1.7.2 on Windows 8.
Thank you,
David
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
I am having the same problem. Where/how does the phone ask you to confirm USB debugging? It asks me when I turn it on, but not again later.
I have tried 3 or 4 different drivers, but, although the device is recognised by Windows 8, it is not recognised by Root Toolkit.
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
studacris said:
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
Click to expand...
Click to collapse
I'm not quite sure how this was supposed to help. My problem is that the ADB drivers do not seem to work on my computer. I have just tried installing the Android SDK (which comes with its own ADB drivers), having first uninstalled all the existing drivers. It did not help.
Not entirely sure where to go from here.
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
studacris said:
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
I had installed PDANet from within Root Toolkit, and it didn't work. Just now, I uninstalled everything again, and installed PDANet from their web site. Still get no ADB device in Root Toolkit. [NB I didn't have PDANet on the phone, but it seems to be there now]
I tried running adb from the android SDK, and it says "error: device not found".
However, I noted there was an adb prompt on the phone when I first plugged it in, this time (which I told to always accept).
[Later]
Wierd - it is now a bit further on. This is what I did:
Started PDANet on the phone, and enabled USB tethering.
Started PDANet on the computer, and it connected to the phone. At this point the USB debugging permission thing came up again, and I accepted it (also ticking the box to always accept).
Unticked USB tethering on the phone again.
Stopped PDANet on the computer (right click on icon, exit).
Tried the Root Toolkit again (pressed Root button), it connected to the device, and put it into fastboot mode.
The boot loader appeared on the phone, and the computer said "Checking Fastboot Status".
It seemed to stay like that for ever.
Killed the root toolkit. and tried again.
Left the computer for a while, and when I came back, it had completed.
So, it seems to be working now.
And when you try using fastboot directly instead of the toolkit....... what happens?
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
studacris said:
And when you try using fastboot directly instead of the toolkit....... what happens?
Click to expand...
Click to collapse
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Best idea i didnt notice too
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
Thanx !!!!!!!
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Thank you so much! This solved it for me :good:
nikkilocke said:
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Click to expand...
Click to collapse
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Click to expand...
Click to collapse
I found the same solution, changing over from MTP to CAMERA suddenly had the toolkit recognise the phone and could boot it to unlock then root it... Previously, I had installed PDA drivers...
I am astonished how PATHETIC nexus phones/tablets are at simply connecting to a PC. I am baffled at the attempt by google to make their devices as UN-plug & play friendly as possible... bizarre! I have a N10, N7 and have had two N5's and all have the same PITA random disability....
grrr...
Mark.
So the Nexus toolkit is able to see the Nexus 7 as a media device but not Windows ?
marcelin99 said:
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
Click to expand...
Click to collapse
So the Nexus 7 toolkit is able to see the Nexus 7 as media device with this method, but not Windows ? That's strange because Windows is supposed to see your files within the Nexus via Mtp mode. Is it that google removed the ability for Windows to be able to see Nexus 7 files in Android kit kat 4.4.2. What should I do then if I simply want to view files inside Nexus as a non root user ? B.T.W I'm currently on stock kitkat 4.4.2 build KOT49H. Therefore, I'd gladly appreciate it if anyone out there would answer this question and thanks in advance. Feel free to PM me on this so we can "talk" about this. : )
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Success.
Well, mtp connection works perfectly fine in my Windows 7 machine. But on my xp machine I could never get it to work no matter what driver combination I used.
I can see the reason they changed to mtp but I found mass storage to be much more user friendly.
Sent from my Nexus 4 using XDA Free mobile app
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Stuck on fastboot screen
GranPaSmurf said:
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Click to expand...
Click to collapse
Hi
Happy New Year to all! unfortunately I am left with the unusable nexus 7 that happened last night.
I was going crazy with the lags with lollipop and was waiting for the 5.0.5 update OTA but the delay was making me go crazy so I decided to take the risk of manually flashing the image using ADB and SDK.
Like many others pointed, I knew how to enable my computer to see my device by switching from MTP to PTP mode from my earlier rooting experience with Samsung, HTC and others. So that was not an issue for me.
I was following a tutorial from androidcentral and half way through I went to check a tutorial on youtube which I think caused the disaster. After I executed the adb devices no devices were detected and like I said I went and changed the MTP mode to off and bingo now my device was detected.
I executed device unlock and currently my device is in unlocked bootloaded state which is displayed in the fastboot screen where I am stuck now. Following the youtube instead of flashing each separately bootloader first and then the factory image I jumped to 'flash-all.bat' command...I saw something say on my command prompt on pc that completed in so many seconds or minutes which led me to get anxious and since no rebooting happened on the device I went and manually tried to press the power button.
From that time I am stuck on the fastboot screen. I can cycle through 'power off', restart booloader, recovery mode and start. But when I select 'restart bootloader' it comes to 'start' in the same mode and when I select that I can see a tiny 'Booting failed' in white letters in tiny fonts on the top left side of the 'Start'. I cannot go past this state.
Since I know the last time I had enabled 'usb debugging' and MTP off before everything went wrong I am presuming those states are still intact. I can see status on 'reboot bootloader' screen that my bootloader is unlocked.
Now, when I try to go through the process again my device is seen in device manager but when I send 'adb devices' command it cannot detect any devices. If my device is usable I can atleast go into settings to see if my MTP state and usb debugging status. Now I don't have that option. I even tried the Nexus Root Toolkit - everything is fine but until it tests the driver to finally say 'ADB device not found'.
After browsing so many posts I spotted there were some posts that said there is some discrepancy between the device id as listed by the driver to what actually is usb.inf, which all is too technical and overboard for me. And finally left me thinking that it is some issue of Windows PC as someone pointed that the ADB device was detected on a MAC. So I am now thinking to give it a shot in a mac machine as a final attempt to recover my device.
Anyone please suggest a solution, apologies if this is covered by someone elsewhere in the forum if so please point me there. I will make sure that from next time I will never do a manual flash of factory image.
please help!
It sounds like you are on top of it, but haven't hit the right combination yet. Thanks for the quote and I am sorry I am unable to offer any help. As mentioned in my post, I have switched to the Galaxy Mega and was pleasantly surprised by the OTA upgrade to 4.4. Now I am trying to figure out how to root it.
So if you been messing around with your fire and got to the point that it wont want to get past the loading screen or something or you may have messed up during the root process you can use these steps to restore your Fire
MOD EDIT: THE FIRMWARE LINKED HERE IS NOT SAFE AT THIS TIME, LINK REMOVED AND THREAD CLOSED.
Steps.
1. MAKE SURE YOU HAVE ALL YOUR ADB DRIVERS INSTALLED!! and if you dont know how to check this thread
2. Download the amazon frimware above and keep it where you can flash it.
3. Boot into recovery (Volume Down + Power at the same time)
4. Select "adb sideload" or whatever it says using your volume keys and press the power to select
5. Now adb sideload <frimware>.bin
6. Its probably gonna take 5- 10 minutes so be patient and then once the recovery options come up make sure you wipe every thing and cache as well
7. Reboot gonna take another few minutes BE PATIENT!!
8. Now your back to your stock frimware.
I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do? :crying:
Darkside1984 said:
I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do? :crying:
Click to expand...
Click to collapse
Try installing ADB drivers in Device Manager while the Fire is in recovery. If you do it correctly, when you do ADB Devices, it should come up as Sideload.
Sent from my KFFOWI using Tapatalk
Troubleshooting
Device may not connect to PC until you select apply update from ADB,
check device manager, Fire should be listed ADB sideload or adb composite interface, when in recovery mode
If device is in adb sideload mode
Code:
adb devices
should return
Code:
G000HXXXXXXXXXXX.........sideload
if not drivers are not correct
Manually Fix Drivers
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Error
cannot read 'adb sideload update-kindle-37.5.2.2_user_522053820.bin'
Make sure Firmware.bin file is in same location, that is listed in command prompt
(ex: C:\Program Files (x86)\Minimal ADB and Fastboot>)
sd_shadow said:
recheck device manager, drivers are not correct, Fire should be listed adb composite interface, when in recovery mode
Click to expand...
Click to collapse
It's strange but when the tablet is in recovery mode, PC doesn't recognise it. The device manager doesn't show any related device. I've reinstalled drivers and nothing... Even I made the same procedure in another PC (also with W10) and nothing... There's no trail of any "Android device" in device manager when the tablet is in recovery mode. I'm seriously confused and I don't know what else to do...
Looking for a miracolous hard factory reset...
EDIT: I see that the battery is low. Does this have something to do with Recovery troubles?
i posted some basic using adb instructions in my amazon index
Using ADB
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
Darkside1984 said:
It's strange but when the tablet is in recovery mode, PC doesn't recognise it. The device manager doesn't show any related device. I've reinstalled drivers and nothing... Even I made the same procedure in another PC (also with W10) and nothing... There's no trail of any "Android device" in device manager when the tablet is in recovery mode. I'm seriously confused and I don't know what else to do...
Click to expand...
Click to collapse
try disconnecting from pc, power off fire, boot into recovery, connect to pc
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
you have to select apply update from ADB, before device will connect to pc
---------- Post added at 11:12 AM ---------- Previous post was at 11:03 AM ----------
Darkside1984 said:
I see that the battery is low. Does this have something to do with Recovery troubles?
Click to expand...
Click to collapse
possible, not sure if Amazon blocks flashing, if battery is low, i know motorola does.
You do not want battery to die during firmware install, it can brick a device.
Try charging battery.
sd_shadow said:
i posted some basic using adb instructions in my amazon index
Using ADB
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
try disconnecting from pc, power off fire, boot into recovery, connect to pc
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
you have to select apply update from ADB, before device will connect to pc
---------- Post added at 11:12 AM ---------- Previous post was at 11:03 AM ----------
possible, not sure if Amazon blocks flashing, if battery is low, i know motorola does.
You do not want battery to die during firmware install, it can brick a device.
Try charging battery.
Click to expand...
Click to collapse
Thanks for your help.
It seems that there are some advances but a new problem appears. Finally the PC recognised the tablet into recovery's sideload option but a new error appears. I can't sideload with success 'cause of this message "You need adb 1.0.32 r never to sideload to this device. Installation aborted". Strange because I've installed the newer ADB drivers...
Darkside1984 said:
Thanks for your help.
It seems that there are some advances but a new problem appears. Finally the PC recognised the tablet into recovery's sideload option but a new error appears. I can't sideload with success 'cause of this message "You need adb 1.0.32 r never to sideload to this device. Installation aborted". Strange because I've installed the newer ADB drivers...
Click to expand...
Click to collapse
try
Code:
adb version
---------- Post added at 12:38 PM ---------- Previous post was at 12:38 PM ----------
should get
Code:
Android Debug Bridge version 1.0.32
Revision d15680a64678-android
sd_shadow said:
try
Code:
adb version
Click to expand...
Click to collapse
:-S
"Android Debug Bridge version 1.0.31"
Now I remember that "adb-setup-1.4.3.exe" installer didn't work for me. How could I install the last version?
Darkside1984 said:
:-S
"Android Debug Bridge version 1.0.31"
Now I remember that "adb-setup-1.4.3.exe" installer didn't work for me. How could I install the last version?
Click to expand...
Click to collapse
try link in my Using adb post
Wow! Hallellujah. I finally got resurrect my Fire. Thanks a million!
Darkside1984 said:
Wow! Hallellujah. I finally got resurrect my Fire. Thanks a million!
Click to expand...
Click to collapse
great
care to post some details about what worked?
Drivers version?
adb method?
Sent from my KFFOWI using Tapatalk
after side loading I needed to switch off the device and restart in order to start the final "Installing the latest software"-sequence
sd_shadow said:
great
care to post some details about what worked?
Drivers version?
adb method?
Click to expand...
Click to collapse
Sure!
I deleted my adb folder and follow the steps in your thread here. So it got the right adb version (1.0.32) and I finally could sideload properly the bin file. I think that the point is that PC just recognizes the Fire (as ADB composite) when you are into 'adb sideload' option, not in the recovery main menu.
5th Gen Kindle Fire - MT65xx Preloader problems
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
hochichi said:
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3238740
[HOWTO] How to restore firmware on your device + Amazon Firmware
hochichi said:
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
Click to expand...
Click to collapse
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
fozzibab said:
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
Click to expand...
Click to collapse
Following your comment, I ran the .BAT while watching Device Mgr. Prior to running it, I had the Android device apparently successfully installed. It had its own folder in Dev Mgr without any [!]. Running the .BAT, that disappeared and Android migrated down to Other Devices. It's now next to the same Unknown Device that I haven't been able to update drivers for.
I tried pointing both to the latest_USB_drivers zip from Shadow's recommended thread. According to Win7, it's 'unable to install' from that unzipped folder or any of the others I've pulled from various threads.
fozzibab said:
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
Click to expand...
Click to collapse
did you try booting to recovery?
Sent from my KFFOWI using Tapatalk
sd_shadow said:
did you try booting to recovery?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
With the Fire disconnected, I booted to recovery (Volume Down + Power) and got a list. Not knowing what to pick, I chose the Bootloader option. It started to boot in FASTBOOT mode. Plugged it in, went to Dev Mgr. Both Android Device and Unknown Device showing in Other Devices. Pointed the Android Device driver to the latest_USB drivers from your other thread. Windows says unable to install your Android. Tried same thing with Unknown Device. Unable to install.