Database Users

TF101 Won't Enter APX Mode

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?

Totally bricked - no ADB, no fastboot, no screen. Recognized as APX device.

Hi all!
First of all I would like to give small heads up - I've been searching XDA and web for two days and ended with no working solution.
Situation:
Suddenly my Nexus 7 (2012) just died. No charging signs, nothing. So i tried Google described and random hardware resets using buttons with no luck.
I ended with situation:
device is not turning on - no screen flickering, not even small amount of pixel light visible,
ADB - no devices found,
fastboot - no diveces found,
nvflash - only my GeForce PC card found
when I connect device to PC I have to hold power button for ~10sec and there I hear "boing" (USB dev. disconnected), "boing" (USB device connected) sounds.
device is visible as APX device with "!" mark
I've tried:
hardware reset by pressing: power button, power+volume's buttons for different amount of time,
taking back and disconnecting battery,
using different software to discover device,
editing driver .inf file to recognize my device as ADB device. It did but still no visibility via ADB or fastboot (URL: http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/),
read and tried to use things from: http://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495.
No result at all...
One more - when I unplug and then plug in battery while having back taken I can hear sound that something is "running".
Please help!

@kepisty89 You can check here. Install the driver and check your device is detecting or not, actually you've a fried bootloader.

Tahnk you @DutchMan_1990, I tried this and now ended with my device recognized as "Asus Transformer Prime APX Interface". Nothing else happened.
Any ideas?

kepisty89 said:
Tahnk you @DutchMan_1990, I tried this and now ended with my device recognized as "Asus Transformer Prime APX Interface". Nothing else happened.
Any ideas?
Click to expand...
Click to collapse
Hi, kepisty89...
Unfortunately, APX mode is generally never good news .
It usually indicates that the Nexus 7's bootloader has either become corrupted or has been erased, and effectively hardbricking the device.
-----
See here, for a post I wrote for another XDA member with similar issues to yours, back in December 2014, where I elaborate further on this problem.
-----
I suspect your Nexus 7 will require a motherboard replacement .
Rgrds,
Ged.

I have similar issue, but mine I can get to bootloader but that's it, if I try to power it on all I get is the Google and unlock padlock, can't get to recovery, but my device is seen via fastboot ADB Wugfresh NRT, but as soon as I try to write to it ie flash files or try to restore device, ADB locks up, and when it says rebooting device my nexus tries to reboot but I get a black screen and Wugfresh says waiting for device, I have to force reboot bootloader hold power button vol down for NRT to see it again in fastboot. I can also boot tempery recovery via NRT but when I select mount it pops up on PC but I can't copy anything to it, also it says I have no OS installed.
Sent from my Nexus 6 using Tapatalk

Bootloop

Hey gents,
Received my unit today which has the dreaded boot loop,
I can get onto a screen with my usb a cable mentioning something about an os.
Windows finds it (xp) i have got some drivers from modaco root zip which is and and fast boot.
Tried both drivers ,
Mad catz is found but can't use any commands get failed when i try following the root procedure.
I tried pressing the buttons to get into recovery as well but I just have a black screen no writing at all and the blue led doesn't load up.
Window cannot find the driver and has usb default but the drivers i used earlier won't work.
Any help ?

Can you get into TWRP recovery following the guides? You should have no problem once installed. Try this guide here if no OS is installed.
I had bootloop before and managed to recover easily but I used Linux. It looks like a similar method all told though.

Managed to get cmd to send files to the mojo but my screen doesn't change

K-Project said:
Can you get into TWRP recovery following the guides? You should have no problem once installed. Try this guide here if no OS is installed.
I had bootloop before and managed to recover easily but I used Linux. It looks like a similar method all told though.
Click to expand...
Click to collapse
I have fast boot now but no adb

All I can say to my friend is you will have to read thoroughly the guides around here. Have you read this one thoroughly? It says you must remove the USB cable when it says booting OS. This is typically the thing that catches many out. You need to make sure all your files are in place on the SD card once you get to recovery. In all honesty it has been a while since I did this but I used Linux and can flash one of these in seconds. If you're getting the "booting OS" message then the machine is NOT BRICKED and is recoverable.
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
From here in bold:
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Unplug the power cable and any USB cables (the dongle can stay in), insert the USB Male A-A cable in the port labelled '2.0', then insert the power cable. 'Key driver not found.. Booting OS' will appear on screen.
WINDOWS - install the device drivers from the directory you extracted above if required, then run 'superboot-windows.bat' as Administrator
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by 'sudo ./superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by 'sudo ./superboot-linux.sh'
You will see 'Booting downloaded image' and a black screen, then the screen will return to 'Key driver not found.. Booting OS'. At this point, unplug the USB cable and the power cable, wait a few moments, then reconnect the power cable to boot as normal.
You are using this method to install TWRP recovery, which will then allow you to install your choice of OS. Read, read, read everything you can. I know how it is because I spent a whole long weekend at this over last Easter. It's a drag at first but great once you figure it out.

K-Project said:
All I can say to my friend is you will have to read thoroughly the guides around here. Have you read this one thoroughly? It says you must remove the USB cable when it says booting OS. This is typically the thing that catches many out. You need to make sure all your files are in place on the SD card once you get to recovery. In all honesty it has been a while since I did this but I used Linux and can flash one of these in seconds. If you're getting the "booting OS" message then the machine is NOT BRICKED and is recoverable.
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
From here in bold:
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Unplug the power cable and any USB cables (the dongle can stay in), insert the USB Male A-A cable in the port labelled '2.0', then insert the power cable. 'Key driver not found.. Booting OS' will appear on screen.
WINDOWS - install the device drivers from the directory you extracted above if required, then run 'superboot-windows.bat' as Administrator
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by 'sudo ./superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by 'sudo ./superboot-linux.sh'
You will see 'Booting downloaded image' and a black screen, then the screen will return to 'Key driver not found.. Booting OS'. At this point, unplug the USB cable and the power cable, wait a few moments, then reconnect the power cable to boot as normal.
You are using this method to install TWRP recovery, which will then allow you to install your choice of OS. Read, read, read everything you can. I know how it is because I spent a whole long weekend at this over last Easter. It's a drag at first but great once you figure it out.
Click to expand...
Click to collapse
Done exactly what you wrote and i just get this boot loop again

Right currently installing android tv whoop
Followed the Russian site 4pda they have a good write up
Basically i just had two commands
So downloaded openrecovery and then fastbooted to open recovery .

Android TV launcher stayed in boot loop but cm 12.1 is working great

Excellent! Glad you got it going. Yes it's effectively two commands really, but you have to have everything in place.
You're getting a bootloop on Android TV, but my understanding is that will disappear once you flash the SuperSu zip. But if you're good with CM 12.1 I'd stick with that. I never tried Android TV since CM 12.1 did everything I need.
Have you flashed your GApps? I'd go for the nano set.

Yes i flashed gapps but fancied trying android TV again basically you don't flash root when asked i don't think you can root android TV without bricking.
I have a different launcher on it now by chain fire halauncher and kodi running.
I've yet to put emulators on it.
Controller is not the best for android TV to be fair constantly switching modes....
Quick question can the controller pair to a smartphone without the dongle.
As I've tried holding start down for five seconds it goes purple than flashes blue and red but my phone can't find it

sutty86 said:
Yes i flashed gapps but fancied trying android TV again basically you don't flash root when asked i don't think you can root android TV without bricking.
I have a different launcher on it now by chain fire halauncher and kodi running.
I've yet to put emulators on it.
Controller is not the best for android TV to be fair constantly switching modes....
Quick question can the controller pair to a smartphone without the dongle.
As I've tried holding start down for five seconds it goes purple than flashes blue and red but my phone can't find it
Click to expand...
Click to collapse
I'm sure someone round here said you could but it wasn't worth it as performance wasn't so good. The retail one doesn't need a dongle fwiw, and connects to the phone just fine.
Yeah, with CM 12.1 I've managed to minimise mode switching on the pad as it is as you say a bit of a pain. I only switch to mouse mode when using Google Play or shutting down the system. Other than that I occasionally swipe apps away by double tapping the Home button, and that needs mouse mode. Otherwise all emulator, game and KODI use is via the pad mode.

Big Big problem - No fastboot with Controller method and pc!!

I try update my nvidia shield tv 2017 but now the System bootloop on Android circles animation (dont start box).
- I try fastboot with Controller but dont work (many, many times)
- I try conect to pc but dont connect device with fastboot
bricked bootloader??
I dont have solutions.... please help.
Sorry my english

Try un plugging the power then plug a USB keyboard in and hold the A and B key and then plug the power back in.

same problem for 3 days, can not enter fastboot mode. my shield is in bootloop

Shot in the dark, but have you tried different USB ports on the computer? I know in my case, some otherwise working ports will not work with the shield. Seems to be very fussy when it comes to which ports I choose. None of my front ports work on this desktop, I have to plug into rear ports in order for my computer and shield to see each other.
Also be sure to use the original cable that came with the shield.

Also make sure USB debugging is on.

Any fix ? Same problem

Have you tried "adb reboot bootloader" in command prompt when the android logo is looping?

I have no Android logo i have no os just twrp and twrp with no access adb and fastboot command dont work on NVIDIA logo

If you put lineage os on a usb stick can twrp read the usb stick? If so, you can install the zip file of lineage with gapps...once that's installed and booted up, you can enable usb debugging in the developers options and fastboot and adb should work again.

How can I get into bootloader mode of Shield TV 2017 (16G)

After flash the OS downloaded for official website, the box stuck at the first screen, I think I should wipe data to enter into the system, but without bootloader interface, I can do nothing!
Then I check the forum, find some way like below:
(1) Unplug SHIELD TV.
(2) Connect SHIELD controller to SHIELD TV with a USB cable (use port closest to HDMI).
(3) While holding the A and B buttons at the same time, connect power to SHIELD TV.
I tried many times, and press A and B buttons at different moments, but it did not work at all!
How can I get into bootloader mode?
Would someone help me to save my Shield Brick and tell me what to do?
Thank you very much!

Hello!
Have a look here: https://nvidiashieldzone.com/shield-android-tv/android-7-nougat/shield-tv-2017-root/
And proceed Step 1, Step 2 and Step 3 to 3.1.4 (Type “adb reboot bootloader” and hit enter. The Shield TV should reboot into the bootloader screen.)