I wrote this awhile back to provide known methods to enter each of these modes. I know it's rather wordy, but may help those that are newer to all this. See the link below for a more concise write-up. I'll try to keep this updated with any corrections and/or new methods and feedback is very welcome.
How To Enter APX, Fastboot Mode and Recovery menu
Special thanks goes out to tobdaryl for providing the foundation for this guide and to daws for
providing a previously unknown method (USB cable plug in while tablet is turned off).
Pertinent links:
The methods below written more concisely by tobdaryl: How to enter APX mode or Bootloader-recovery menu
Universal Naked Drivers (for APX/ADB/Fastboot modes): [ADB/FB/APX Driver] Universal Naked Driver 0.72
To install the SDK tools & drivers in Windows 7 (and other versions?): [HOWTO] Install Google SDK and ADB drivers...
The following instructions are written on how to enter APX mode. To enter Fastboot and Recovery modes, simply follow the same instructions but use the Volume Down button. Once the message: "Checking for RCK.. press key <Vol_Up> in 5 sec to enter RCK" is displayed, follow the displayed instructions to enter the desired mode. Note: The screen remains blank in APX mode.
When your tablet is turned off, to enter APX mode:
Make sure your USB cable is connected to your tablet and PC. While pressing the Volume Up button, press the Power button for a few seconds, and then release both buttons.
Make sure the USB cable is not plugged into your tablet (but is connected to your PC). While pressing the Volume Up button, plug the USB cable into your tablet. Release the Volume Up button after a few seconds (modified from daws' suggested method).
When your tablet is up and running, to enter APX mode:
Turn your tablet off and wait a few seconds. Connect your USB cable to your tablet and PC. While pressing the Volume Up button, press the Power button for a few seconds, and then release both buttons.
Make sure your USB cable is connected to your tablet and PC. Open a command prompt on your PC, navigate to the folder containing adb.exe, type: adb reboot and hit the Enter key while holding down the Volume Up button until the screen remains blank for a few seconds.
From a tablet based terminal emulator, type: su and hit the Enter key, then type: reboot and hit the Enter key while holding down the Volume Up button until the screen remains blank for a few seconds. One suggested app (by tobdaryl) is the free Android Terminal Emulator from Google Play. Note: You must be rooted for this to work.
Press the tablet reset with a paperclip while pressing the Volume Up button until the screen remains blank for a few seconds (the reset is located about either 25mm or 1" below the sdcard slot). Note: Do not press hard!
When your tablet is in Fastboot mode, to enter APX mode:
While pressing the Volume Up button, press the Power button for 10 seconds. Release both buttons a few seconds after the screen goes blank. One variation is to wait and press the Volume Up button immediately after the screen goes blank and then release it after a few seconds. If you wait too long to press the Volume Up button, your tablet will just boot up normally.
Make sure your tablet has the USB cable connected to your PC. Open a command prompt on your PC, navigate to the folder containing fastboot.exe, type: fastboot -i 0x0B05 reboot and hit the Enter key while holding down the Volume Up button until the screen remains blank for a few seconds. One variation is to wait and press the Volume Up button immediately after the screen goes blank and then release it after a few seconds. If you wait too long to press the Volume Up button, your tablet will just boot up normally. Note: Newer versions of fastboot.exe do not require the "-i 0x0B05" option.
Or, as a last resort!
Remove your tablet's cover, disconnect the battery, press and hold the volume up button, and reconnect the battery!
The following instructions are written on how to switch from one mode to another (not covered above).
When your tablet is up and running, to enter Fastboot or Recovery mode:
Make sure your USB cable is connected to your tablet and PC. Open a command prompt on your PC, navigate to the folder containing adb.exe, type: adb reboot-bootloader and hit the Enter key. Once the message: "Checking for RCK.. press key <Vol_Up> in 5 sec to enter RCK" is displayed, follow the displayed instructions to enter the desired mode. Note: I was unable to verify this method possibly due to having the AndroidRoot.mobi custom bootloader. This method only performs a regular reboot for me.
From a tablet based terminal emulator, type: su and hit the Enter key, then type: reboot bootloader and hit the Enter key. Once the message: "Checking for RCK.. press key <Vol_Up> in 5 sec to enter RCK" is displayed, follow the displayed instructions to enter the desired mode. One suggested app (by tobdaryl) is the free Android Terminal Emulator from Google Play. Note: You must be rooted for this to work, Note2: I was unable to verify this method possibly due to having the AndroidRoot.mobi custom bootloader. This method only performs a regular reboot for me.
When your tablet is in APX mode, to enter Fastboot or Recovery mode:
While pressing the Volume Down button, press the Power button for 10 seconds. Release both buttons a few seconds after the screen goes blank. One variation is to wait and press the Volume Up button immediately after the screen goes blank and then release it after a few seconds. If you wait too long to press the Volume Up button, your tablet will just boot up normally. Once the message: "Checking for RCK.. press key <Vol_Up> in 5 sec to enter RCK" is displayed, follow the displayed instructions to enter the desired mode.
When your tablet is in Fastboot mode, to enter Recovery mode:
Make sure your tablet has the USB cable connected to your PC. Open a command prompt on your PC, navigate to the folder containing fastboot.exe, type: fastboot -i 0x0B05 reboot-bootloader and hit the Enter key. Once the message: "Checking for RCK.. press key <Vol_Up> in 5 sec to enter RCK" is displayed, press the Volume Up button within 5 seconds. Note: Newer versions of fastboot.exe do not require the "-i 0x0B05" option, Note2: I was unable to verify this method possibly due to having the AndroidRoot.mobi custom bootloader. This method only performs a regular reboot for me.
When your tablet is in Recovery mode (TWRP v2.3.x), to enter Fastboot mode:
Select the "Reboot" option and then select the "System" option while pressing the Volume Down button until the screen remains blank for a few seconds. Once the message: "Checking for RCK.. press key <Vol_Up> in 5 sec to enter RCK" is displayed, wait 5 seconds for the icons to appear, and follow the instructions to select/confirm fastboot mode. One variation is to wait and press the Volume Down button immediately after the screen goes blank and then release it after a few seconds. If you wait too long to press the Volume Down button, your tablet will just boot up normally.
When your tablet is in Recovery mode (TWRP v2.3.x), to enter APX mode:
Select the "Reboot" option and then select the "System" option while holding down the Volume Up button until the screen remains blank for a few seconds. One variation is to wait and press the Volume Up button immediately after the screen goes blank and then release it after a few seconds. If you wait too long to press the Volume Up button, your tablet will just boot up normally.
Nice guide! Thanks for taking the time to gather the information and create this guide.
It is clear, detailed, and easy to follow.
It should be a stickied.
Hi I tried connecting my device to my computer after holding down the buttons to get into APX mode. And after about 5 seconds I heard a connection sound then Windows told me the USB device malfuntioned. Any idea why?? I'm trying to fixed my friend's soft bricked tablet which cannot get into fastboot mode.
firtvid20 said:
Hi I tried connecting my device to my computer after holding down the buttons to get into APX mode. And after about 5 seconds I heard a connection sound then Windows told me the USB device malfuntioned. Any idea why?? I'm trying to fixed my friend's soft bricked tablet which cannot get into fastboot mode.
Click to expand...
Click to collapse
A couple of quick thoughts if it's not the device itself: check to make sure the cable is good, try a different USB port, and try re-installing the drivers (using the Universal Naked drivers, specifically the APX one included in the package). I've had troubles on one pc where it would connect and disconnect - it was either the USB port acting flaky or the OEM cable I was using...
Watching Windows device manager, is it showing it as an APX device or something else before it disconnects? Also, what kind of error?
Hopefully some others may have added suggestions...good luck!
wha2do said:
A couple of quick thoughts if it's not the device itself: check to make sure the cable is good, try a different USB port, and try re-installing the drivers (using the Universal Naked drivers, specifically the APX one included in the package). I've had troubles on one pc where it would connect and disconnect - it was either the USB port acting flaky or the OEM cable I was using...
Watching Windows device manager, is it showing it as an APX device or something else before it disconnects? Also, what kind of error?
Hopefully some others may have added suggestions...good luck!
Click to expand...
Click to collapse
Ah I seemed to fix it when I held down the volume button while the tablet was off and plugged it in. Thanks for the help!
firtvid20 said:
Ah I seemed to fix it when I held down the volume button while the tablet was off and plugged it in. Thanks for the help!
Click to expand...
Click to collapse
No problem at all and glad to hear it wasn't a complicated fix! With APX and other modes, do have the two methods. Holding both buttons at same time, but I do find somehow it doesn't always recognize them (maybe I'm not holding the volume button solidly?). As worked for you, the other option is to have it powered off, hold the volume button, and then plugging it in to get it to power on and go into APX mode (remembering it's just a black screen but can tell by checking Windows device manager - mostly mentioned for any others that may come across this!).
If have more questions on the rest of the restore process, might be good to start a fresh post for the remaining steps. Good luck with getting it back up and going!
Hi @wha2do,
This morning I followed a guide written years ago instructing "-i 0x0B05" as part of a fastboot flash, which was a problem considering I used the latest fastboot available ...
Thanks to your guide, I removed that portion and it worked like a charm. Thank you man
cristobal.digital said:
Hi @wha2do,
This morning I followed a guide written years ago instructing "-i 0x0B05" as part of a fastboot flash, which was a problem considering I used the latest fastboot available ...
Thanks to your guide, I removed that portion and it worked like a charm. Thank you man
Click to expand...
Click to collapse
Whew, it hit me how long ago that was posted, but glad to hear it helped! I def appreciate the post
I don't know if all this info was ever collected into one post; if not, here it is. The times given are approximate times to hold the buttons continuously.
[size=+1]Starting from Device OFF Condition:[/size]
Power (2-3 seconds) -> Normal OS Boot**
Vol-Up + Power (1-3 seconds) -> APX Mode
Vol-Down + Power (6-8 seconds) -> Bootloader/fastboot Mode (keep both buttons pressed until you see the droid lying on his back).
[size=+1]Starting from APX Mode:[/size]
Power (10-15 seconds) -> Normal OS Boot**
[size=+1]Starting from booted or boot-looping OS:[/size]
Power (10-15 seconds) -> Normal OS Boot**
** Bootloader Interrupt: In any of the cases where you hold the power button down to try to break out of the current operating mode, if you press the Vol-Down button right after you first see the black and white screen with the Google logo, the tablet will proceed immediately to bootloader/fastboot mode, rather than booting the normal OS. You need to be ready though - you only get about 1 or 2 seconds to do this! (Thanks to RMXO for pointing this out) Note that this means you can get to the bootloader directly from any other mode!
This also explains why, when attempting a cold start using Vol-Down + Power, if you accidentally let go of the vol-down button when the screen first lights up, the Nexus 7 will boot to the normal OS. In this case, pressing Vol-Down initially is actually superfluous - what makes the device go into bootloader/fastboot mode is the Vol-Down press immediately following the google splash screen - there actually is no unique "Go to fastboot from a cold start" method.
[size=+1]Starting from Bootloader/Fastboot Mode:[/size]
Follow the instructions on-screen.
[size=+1]Starting from Stock Recovery Splash Screen:[/size]
Power + Vol-Up simultaneous press -> gets you to the hidden stock recovery Menu.
For me, pressing Vol-Up first and then Power does not seem to work here - they seem to need to be pressed simultaneously.
[size=+1]Starting from Custom Recovery:[/size]
Follow the instructions on-screen.
[size=+1]Screen Shot in Booted OS[/size]
Press Power + Vol-Down Simultaneously & hold for about 1 second. The simultaneous part seems to be important, as well as holding them down together for the one second or so. A fine example of a simply horrid UI implementation. (Google, can your Grandma perform this trick?)
[size=+1]Safe Mode Boot[/size]
From a cold start boot (press & release Power button), wait 2 seconds after the B&W Google (bootloader) splash screen appears, then press and hold Vol-Down button until the normal OS boot is fully completed (lock screen or home screen appears)
[size=+1]Discussion.[/size]
1) These results can depend on the bootloader version; I tested all of the above on the v4.13 bootloader under the following scenarios: (a) unlocked bootloader and custom recovery, (b) unlocked bootloader and the JOP40D stock recovery, and (c) locked bootloader and JOP40D stock recovery. I noted no differences in button-press responses due to these different configurations.
2) Note that in APX mode, there are absolutely no indications on the screen that the device is actually turned on. The ONLY way to see this is to plug it in to a computer, and you will see/hear the device insertion. I am able to enter APX mode without being plugged in, and then afterwards plug into the PC, or cold start it into APX mode plugged in to the PC at cold-boot. If I unplug the tablet in APX mode and then attempt a re-insert, Win 8 is unhappy with the device.
3) If you are stuck in a bootloop pay special attention to the Bootloader Interrupt note above - this is how you get out of a bootloop and into the bootloader or recovery!
4) The JOP40D Stock Recovery has a two minute (120 sec) timer running - if you do not progress to the (hidden) menu within this time, an automatic boot to the regular OS will occur.
[size=+1]Bonus Info: USB Device IDs in each mode[/size]
Bootloader/Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000 (Android Phone -> Android Bootloader Interface)
USB\VID_18D1&PID_4E40
Stock OS, ADB Debugging Off, PTP Storage
USB\VID_18D1&PID_4E43&REV_9999 (Portable Devices -> Nexus 7 ) ["PTP"]
USB\VID_18D1&PID_4E43
Stock OS, ADB Debugging Off, MTP Storage
USB\VID_18D1&PID_4E41&REV_9999 (Android Phone -> Android ADB Interface)
USB\VID_18D1&PID_4E41
(Note: MTP Seems to need to have ADB Debugging enabled - 4.2.1/JOP40D)
Stock OS, ADB Debugging ON:
USB\VID_18D1&PID_4E42&REV_9999&MI_01 (Android Phone -> Android Composite ADB Int)
USB\VID_18D1&PID_4E42&MI_01
(when in MTP storage mode)
USB\VID_18D1&PID_4E42&REV_9999&MI_00 (Portable Devices -> Nexus 7 ) ["MTP"]
USB\VID_18D1&PID_4E42&MI_00
(when in PTP storage mode)
USB\VID_18D1&PID_4E44&REV_9999&MI_00 (Portable Devices -> Nexus 7 ) ["PTP"]
USB\VID_18D1&PID_4E44&MI_00
APX Mode:
USB\VID_0955&PID_7330&REV_0103 (Other Devices -> APX)
USB\VID_0955&PID_7330
Custom Recovery - TWRP 2.3.3.0
USB\VID_18D1&PID_D001&REV_9999 (Android Phone -> ?varies? )
USB\VID_18D1&PID_D001
If you are aware of other escape sequences using the physical buttons to navigate through different device modes, or differences in these behaviors in earlier bootloader revisions, let me know.
Revision History
---------------------------------------------------------------------------------
2013-02-04 Initial Revision
2013-02-08 Added USB Bus Hardware IDs for PTP mode
2013-03-29 Added Safe Mode
I was running stock rooted Android KK 4.4.4 on Nexus 2012 Wifi Only with bootloader as unlocked. I attempted the Lollypop update 5.0.2 by OTA but it gave an error while installing and device rebooted to Kit Kat normally.....working fine. OTA was not getting done for some reason may be because i was rooted.
I downloaded the factory image nakasi-lrx22g-factory-2291c36b.tgz from google and attempted to flash it using Nexus Root Toolkit(v 2.0.2) with option "No Wipe Mode" as selected and then the device ran into fastboot mode... NRT run commands like erase system etc then the script gave an error "Failed" "remote -invalid state" while attempting to write bootloader. I thought that the problem is with "No Wipe" selected so i re-attempted it with "No Wipe" being unselected. BUt same error.
I searched the forum & found that the issue may be due to incorrect/corrupted bootloader. I replaced the bootloader-grouper-4.23.img which was in the factory image with the 4.23 bootloader taken from JWR66V as most people over XDA have said that its the working bootloader.
I had flashed the img downloaded from here - http://forum.xda-developers.com/showpost.php?p=45043044&postcount=15
Flashing succeeded and Nexus Root Toolkit did not give error this time it said "OKAY" instead of "FAILED". But it did not proceed forward to flashing other files like system img etc. NRT was stuck at the Flash Bootloader - OKAY cmd.
I powered of the Tablet and Powered On again it showed "Booting Failed" at the Google Screen. I rebooted into Fastboot mode with "vol- and power" held together. It displayed the same screen as it did before i.e. displaying the information of Bootloader.
Product Name - Grouper
Variant - Not Defined Yet
HW Version - ER3
Bootloader version - 4.23
Baseband version - NA
Signing - Not Defined Yet
LOCK STATE = UNLOCKED
Then I read somewhere that after flashing the Bootloader img you have to run the bootloader by rebooting tablet with vol+,vol- and power button all held together.
I did that and wat i saw on computer screen was "APX device found" (((((
The device went into APX mode and since 2 days has not come out.
I tried pressing Power button for like 3mins with power adapter connected/disconnected by usb
I tried pressing vol- and power button for more than 5min. with system connected/disconnected with usb
Nothing worked...
I am wondering what took the device to APX because the bootloader was good one from "JWR66V". It was flashed with success by Nexus Root Toolkit. the device did run into fastboot mode once after flashing it. The Device went into APX after all the 3 keys "vol+ vol- and power" were pressed together. But according to key combo terms APX mode is activated when "Power" and "vol+" are pressed and it exits when "Power" alone is held for 15+ seconds.
What I feel now is that the device is in APX looping (similar to Bootlooping) due to some reason. Corrupted Bootloader can be one of that but its unlikely as flashing was successful and img used was authentic. One more reason of APX looping may be that nothing apart from Bootloader is present in it, no system no recovery. only bootloader is present.
Now what do I do to come out of APX ? Power button and Power+vol- etc not working tried them numerous times. It won't accept fastboot or adb commands as its in apx mode.
Its Out of Warranty so only 2 options left for me now
1. Battery Removal
2. NVFlash
I want to keep things simple so I am thinking of battery removal first. Does the battery removal reset nexus 7 ?
I have a feeling that its effect is same as the power button holding for 15sec. but will have to try. Although the Warranty is voided but will Asus people agree to provide paid service to me if i myself attempt battery removal by opening the back side of the device.
Incase this dont work I will move to nvflash
But I have a few questions regarding nvflash.
1. Does nvflash require blob n sbk even for an unlocked bootloader?
2. I can generate the SBK for my device using the CCSN number and try though but I want only a simple command which will reboot nexus into fastboot mode exiting APX mode.
any help will be appreciated.
BrightHeart said:
I was running stock rooted Android KK 4.4.4 on Nexus 2012 Wifi Only with bootloader as unlocked. I attempted the Lollypop update 5.0.2 by OTA but it gave an error while installing and device rebooted to Kit Kat normally.....working fine. OTA was not getting done for some reason may be because i was rooted.
I downloaded the factory image nakasi-lrx22g-factory-2291c36b.tgz from google and attempted to flash it using Nexus Root Toolkit(v 2.0.2) with option "No Wipe Mode" as selected and then the device ran into fastboot mode... NRT run commands like erase system etc then the script gave an error "Failed" "remote -invalid state" while attempting to write bootloader. I thought that the problem is with "No Wipe" selected so i re-attempted it with "No Wipe" being unselected. BUt same error.
I searched the forum & found that the issue may be due to incorrect/corrupted bootloader. I replaced the bootloader-grouper-4.23.img which was in the factory image with the 4.23 bootloader taken from JWR66V as most people over XDA have said that its the working bootloader.
I had flashed the img downloaded from here - http://forum.xda-developers.com/showpost.php?p=45043044&postcount=15
Flashing succeeded and Nexus Root Toolkit did not give error this time it said "OKAY" instead of "FAILED". But it did not proceed forward to flashing other files like system img etc. NRT was stuck at the Flash Bootloader - OKAY cmd.
I powered of the Tablet and Powered On again it showed "Booting Failed" at the Google Screen. I rebooted into Fastboot mode with "vol- and power" held together. It displayed the same screen as it did before i.e. displaying the information of Bootloader.
Product Name - Grouper
Variant - Not Defined Yet
HW Version - ER3
Bootloader version - 4.23
Baseband version - NA
Signing - Not Defined Yet
LOCK STATE = UNLOCKED
Then I read somewhere that after flashing the Bootloader img you have to run the bootloader by rebooting tablet with vol+,vol- and power button all held together.
I did that and wat i saw on computer screen was "APX device found" (((((
The device went into APX mode and since 2 days has not come out.
I tried pressing Power button for like 3mins with power adapter connected/disconnected by usb
I tried pressing vol- and power button for more than 5min. with system connected/disconnected with usb
Nothing worked...
I am wondering what took the device to APX because the bootloader was good one from "JWR66V". It was flashed with success by Nexus Root Toolkit. the device did run into fastboot mode once after flashing it. The Device went into APX after all the 3 keys "vol+ vol- and power" were pressed together. But according to key combo terms APX mode is activated when "Power" and "vol+" are pressed and it exits when "Power" alone is held for 15+ seconds.
What I feel now is that the device is in APX looping (similar to Bootlooping) due to some reason. Corrupted Bootloader can be one of that but its unlikely as flashing was successful and img used was authentic. One more reason of APX looping may be that nothing apart from Bootloader is present in it, no system no recovery. only bootloader is present.
Now what do I do to come out of APX ? Power button and Power+vol- etc not working tried them numerous times. It won't accept fastboot or adb commands as its in apx mode.
Its Out of Warranty so only 2 options left for me now
1. Battery Removal
2. NVFlash
I want to keep things simple so I am thinking of battery removal first. Does the battery removal reset nexus 7 ?
I have a feeling that its effect is same as the power button holding for 15sec. but will have to try. Although the Warranty is voided but will Asus people agree to provide paid service to me if i myself attempt battery removal by opening the back side of the device.
Incase this dont work I will move to nvflash
But I have a few questions regarding nvflash.
1. Does nvflash require blob n sbk even for an unlocked bootloader?
2. I can generate the SBK for my device using the CCSN number and try though but I want only a simple command which will reboot nexus into fastboot mode exiting APX mode.
any help will be appreciated.
Click to expand...
Click to collapse
U have done it in wrong way
U should have flashed the recovery and system and bootloader manually without nrt
Are able to detect your device via computer in fastboot mode
shivambhai said:
U have done it in wrong way
U should have flashed the recovery and system and bootloader manually without nrt
Are able to detect your device via computer in fastboot mode
Click to expand...
Click to collapse
I used NRT normally as its directed in NRT's thread. Bootloader taken from "JWR66V" was flashed successfully but NRT didnot proceed forward. I powered of the tablet then pressed both volume plus & minus buttons along with power button simultaneously, I read somewhere that pressing all 3 butons is needed to start the bootloader, This resulted in device going in APX mode, although APX mode is activated by holding only vol plus and power button simultaneously. The device seems to be looped in APX i.e. not coming out of it.
It was detectable as a fastboot device earlier but after it went into APX its detected as an "Unknown Apx device" asking for driver, The Asus Transformer Pas driver is installable for it, but i doubt will it work in nvflash.
I jus need a little information about battery removal & nvflash. I have googled about them already but had a couple of queries which I have posted above.
Thanxxxx
Update
Okay last night I attempted battery removal from the device. I took off the back panel of nexus 7 and disconnected the battery cable which is connected to motherboard socket. I reconnected it after 10mins and still no success. I removed it again and connected the device to computer by USB and I found something very strange. the computer detected the Nexus 7 as "Unknown APX Device" even after the battery was disconnected. I was wondering from where is the device drawing power to run? Is it by computer's USB port alone or is there any other power source in nexus7's motherboard like a CMOS cell is present in Computer's MotherBoard which keeps the clock ticking.
Whatever may be the case but it seems that APX Mode is capable of running in minimal power input.
Next test which I performed was to Hold the power button while it was connected to system by USB. After about 7-8secs the device powered off as the computer displayed USB device disconnected message and sound but it repowered on its own in next couple of seconds and again it was detected as "APX device" . Same result observed with simultaneous holding of volume minus+power button as well.
Now I have every reason to believe that device is hard bricked and looped in APX i.e. The Bootloader is corrupted or is not running due to some reason. The device has no option but to go in APX and sit there forever unless its flashed at low level.
I would like to give nvflash a try but i know that theres no1 yet who has made it success and then the only option remaining for me is to visit Asus service center and get some paid service done.
Query - If I visit Asus service center then will they perform software reprogramming i.e. Bootloader fixing or will they replace the hardware ? Incase if they replace the hardware then will they replace the whole board or just the memory unit(which contains Bootloader) from the board?
Experts here please put some light on this
No idea brightheart
Did you have any luck with this BrightHeart? I seem to be in the same boat now...
BrightHeart said:
Okay last night I attempted battery removal from the device. I took off the back panel of nexus 7 and disconnected the battery cable which is connected to motherboard socket. I reconnected it after 10mins and still no success. I removed it again and connected the device to computer by USB and I found something very strange. the computer detected the Nexus 7 as "Unknown APX Device" even after the battery was disconnected. I was wondering from where is the device drawing power to run? Is it by computer's USB port alone or is there any other power source in nexus7's motherboard like a CMOS cell is present in Computer's MotherBoard which keeps the clock ticking.
Whatever may be the case but it seems that APX Mode is capable of running in minimal power input.
Next test which I performed was to Hold the power button while it was connected to system by USB. After about 7-8secs the device powered off as the computer displayed USB device disconnected message and sound but it repowered on its own in next couple of seconds and again it was detected as "APX device" . Same result observed with simultaneous holding of volume minus+power button as well.
Now I have every reason to believe that device is hard bricked and looped in APX i.e. The Bootloader is corrupted or is not running due to some reason. The device has no option but to go in APX and sit there forever unless its flashed at low level.
I would like to give nvflash a try but i know that theres no1 yet who has made it success and then the only option remaining for me is to visit Asus service center and get some paid service done.
Query - If I visit Asus service center then will they perform software reprogramming i.e. Bootloader fixing or will they replace the hardware ? Incase if they replace the hardware then will they replace the whole board or just the memory unit(which contains Bootloader) from the board?
Experts here please put some light on this
Click to expand...
Click to collapse
Same Issue!
seanet1970 said:
Did you have any luck with this BrightHeart? I seem to be in the same boat now...
Click to expand...
Click to collapse
Looks like this problem is quite common and mostly affecting Nexus 7 2012 devices. Mine to got botched after a OTA update. Any possibilities of Google fixing this /RMA beyond warranty ?
Ok so here's what happened.
Couple days ago I mistakenly selected "install now" while attempting to postpone the OTA on my VS980. Phone was rooted on stock ROM via stump root and I had not installed a custom recovery yet.
Phone then would only show the LG screen and display an error. No download mode or recovery.
So I utilized a VM running Ubuntu and pushed the sdl1, aboot, rpm, tz and TWRP 2.7 to the phone.
upon restart of the phone It would only start up into fastboot mode. The only other thing it would do is bring up the hardware key mode ( done by pressing vol-, pwr, vol+ at the same time)
Phone would report two errors upon being plugged into the computer and the computer only recognizes the phone as an adb device in device manager
"EP1/out FAIL nfo=40pg0=f910700"
"usb_read() transaction failed"
So I installed the adb on windows and in terminal on Ubuntu. I also installed the unified LG drivers, SDK and the google USB drivers. I now get the same error messages but the fastboot mode now constantly resets.
here is what it goes through
"fastboot mode started"
"reset"
"portcharge"
"fastboot: processing commands"
"reset"
"EP1/out FAIL nfo=40pg0=f910700"
"portcharge"
"usb_read() transaction failed"
"fastboot: oops!"
"fastboot: processing commands"
"reset"
"EP1/out FAIL nfo=40pg0=f910700"
"portcharge"
"usb_read() transaction failed"
"fastboot: oops!"
"fastboot: processing commands"
this goes on and on....
any ideas on where to go from here?
You could try pushing fal.img like you've pushed those other files, rather than using the fastboot.
Id love too, but my comp isn't recognizing the phone when plugged in
Were you in bulk mode originally when you wrote the partitions to the phone? If so, i'm surprised you can't enter twrp. Just to rule out and error, be sure you're holding down power for no less than 15 seconds to power off the phone all the way. Then press and hold both volume down and power simultaneusly until the lg logo comes up. Then quickly release both buttons and immediatly press and hold them both again until the factory reset screen comes up. Accept factory reset to enter twrp.
If that is all a rehash, so be it. Just want to make sure you're using the correct method. Many people fail to hold down power long enough on the initlal shutdown making all the steps after that a moot point. Also you don't want to be connected to usb when doing the above procedure.
Hi all,
I have just recently rooted my 306SH, the rooting process was fine. The problem started when I flashed an incompatible twrp image. Now I can't boot into anything it seems, no recovery, no fastboot and the power button will show only the logo screen. If connected to a power source the red led light will stay on even if unplugged. The device can be completely shut down and the red light off if I hold the down+volume and power down for few seconds.
I can connect it to my computer via usb by holding up+volume and power (green led light) . I installed google usb driver onto the android device and it stays connected for about 30 seconds to 1 minute. I tried using command prompt and SDK by typing "adb reboot recovery" but get an error message "error: device '(null)' not found.
Things I have installed on my computer:
(ADB, fast boot and drivers) https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
SDK Platform-tools
306SH:
Google USB driver
Is there anything I can do from my computer? I was thinking maybe I can flash in an image to replace it. And also my sim card pops out and can't be set back in, is this due to the incorrect flashing?
Any help or input is greatly appreciated, I've been working on this for a while and is getting no where.