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 ?
Every time I boot my phone it goes to Android system recovery.
I'm trying to connect my phone with Odin to flash stock rom but I can't get my phone into download mode.
I press power button + VOL down + home button but it doesn't do anything, it just goes straight to recovery.
I should also note that my volume UP button doesn't function anymore.
Is there anything else I can attempt to save my device? Please help!
Thanks!!!
It may be a bootloader problem. Had something similar on another device and flashing the bootloader again helped.
You already gave your answer. Your volume up button is causing the problem. Fix it.
It's not software related.
You can buy a JIG on the web,this is a micro usb whithout a cable connected and cost 2 times nothing.
You shut down the phone put the JIG in the usb port and the device starts up in download mode,handy when you have problems with the volume rockers,like you do.
This works on all Galaxy devices,and everyone with a Galaxy should have this,i have it for years now and i could not whithout it.
http://galaxyworld.nl/usb-jig-download-reset-mode
My Nexus 7 (2012 wi-fi) won't turn on anymore. The screen doesn't show anything, not even the bootloader. When we plug it to the PC, it seems to be recognizing a different device (such as a camera, I don't know) and just for a second not even installing the drivers.
After asking a technician, he found that the battery (working with another N7) was working properly and no damage was found. Is there any hope? Anything we can do?
Model: Nexus 7 wi-fi (2012) - 32Gb
Was running: A custom ROM/kernel based on android 5.1.1
When Plugged to pc: APX device
Thanks
If you are lucky, the device is stuck in APX mode. Let it charge for some time (1-2 hours) and then press the power button for at least 20 seconds. In that case the devcie should leave APX mode and you should be able to boot to bootloader / recovery / ... again. If not, I suppose some hardware issues with your device.
I didn't work
AndDiSa said:
If you are lucky, the device is stuck in APX mode. Let it charge for some time (1-2 hours) and then press the power button for at least 20 seconds. In that case the devcie should leave APX mode and you should be able to boot to bootloader / recovery / ... again. If not, I suppose some hardware issues with your device.
Click to expand...
Click to collapse
I did that, I checked the battery charge with my other nexus 7 (my mother has the same tablet) and I long pressed the power button but nothing happened. In the other hand, I plug it to the pc again and it recognized an APX device "installing" the drivers (are installed but don't do anything). I read other forums about APX mode and i tried the button stuuf plug/unplug they were talking about other things that i don't unerstand.
I will edit the original post to bring more information. Thank you
Hello, I have a problem with my storm. Two days ago I received it and flashed the then latest cm13 and its corresponding recovery. Everything seemed to work just fine until yesterday when there appeared to be an ota update. After the download finished, the phone rebooted itself and is since then stuck with a black flickering screen. Every attempt to start the phone using recovery or bootloader seems to fail, as the phone keeps showing me the black flickering screen, no matter the combination of keys (vol+/vol-) I use to turn it on. If during the black screen I plug the phone to the computer adb can actually see the phone but says it's not authorized to perform any command. On the other hand fastboot won't even see the device.
Is there anything else I can try before sending it back to wileyfox?
Thank you in advance
I've made some progress, I found out that the device can be forced to Qualcomm HS-USB QDLoader 9008 mode by turning it off and then connecting it to usb while holding vol+ and vol-.
I've also found the stock firmware at https://cyngn.com/support.
Now it would be great if somebody could help me, and the others in my situation, to figure the wole QFIL unbricking out, because I'm overwhelmed, and can't seem to find the right info on google.
Thanks to anyone who'll care to help, or share some info
I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.
miSAKe said:
I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.
Click to expand...
Click to collapse
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.
maxxie00 said:
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.
Click to expand...
Click to collapse
Sorry to hear you are still having trouble, it does sound like the same issue, was a CM13 update from the last couple of days, upon reboot I saw the wileyfox logo but when the Cyanogen logo would normally show during boot it displayed a black screen, which would flicker every few seconds. Holding vol- and power to reboot resulted in the same thing so I was unable use recovery.
When the display was black and connected via USB I was able to see the device using ADB but like you no commands were authorised.
Leaving the phone plugged in via USB and holding down vol+ and power until it rebooted I was able to enter fastboot, once the fastboot prompt was displayed on the screen I attempted using fastboot to boot from a custom recovery, unfortunately that just resulted in the same blank screen for me. I also tried booting the stock recovery with the same result, I admit I did not try many older CM recoveries, but I wanted to revert to CM12.1 anyway, as the accelerometer and gyroscope not working in CM13 at the moment is no good for me.
Only thing that worked was a stock restore, so I think something beyond the recovery got broken as you could not even boot a previously working recovery.
For the sake of sanity it may be work getting someone else try booting it into fastboot before resorting to Wileyfox support. Though your phone is really new so could claim a refund or replacement from the seller, that would probably be faster.
FYI if you do end up sending it to Wileyfox support they do flash it back to stock, I had a broken screen replaced, was repaired and back to me in just under 2 weeks.
What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot
maxxie00 said:
What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot
Click to expand...
Click to collapse
Hi,
Just tried a few combinations to check timings for you.
Powered off, not plugged in, holding vol+ while plugging in phone end of usb connected to computer, keep holding vol+ -> boots straight to fastboot.
Powered on, already connected to computer via usb, holding vol+ and power, release power when vibrates to indicate reboot but keep holding vol+ -> boots straight to fastboot.
Are you seeing the black and white Wileyfox logo when first booting? When going to fastboot it should skip that. If you are not seeing the logo it might not show the fastboot screen either. You can try following the steps above and then issuing fastboot devices from a command/shell session to see if you are in fastboot mode.
I hope that is of some help.
Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...
maxxie00 said:
Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...
Click to expand...
Click to collapse
No problem, I hope you have more luck with the replacement.
Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you
maxxie00 said:
Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you
Click to expand...
Click to collapse
Hello again,
So these 5 methods work for me, someone else may have other experiences:
Phone powered off, hold vol+ while connecting USB, other end of USB already plugged into PC, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on, already connected to USB, other end of USB already plugged into PC, hold vol+ and power until reboot vibrate, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on and in OS, already connected to USB, other end of USB already plugged into PC, debug enabled, from ADB console, adb reboot fastboot or adb reboot bootloader
Phone powered on and in OS, advanced reboot options turned on, hold power, select reboot, select bootloader, reboot
Phone powered on and in Recovery, select reboot to bootloader
Currently I am running stock everything.
Perhaps try different USB cables or ports, though I still get to fastboot without the USB cable plugged in.
My Storm was a pre-order so is one of the first releases, it is possible they have changed something since.
Edit: I have come across a thread on the Cyanogen forums which implies this may be related to encrypting your device: http://forum.cyanogenmod.org/topic/117661-bootloader-hangs/ - I see you have been there already
as reference mine is not encrypted at the moment
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Conrad-007 said:
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Click to expand...
Click to collapse
Hi, Conrad-007...
This is very strange - your Nexus 7 is clearly 'bootable' (sort of), with a functioning bootloader, ie., it's not hardbricked... or you wouldn't be seeing the Google logo.
In the distant past, back when I used to experiment with custom kernels on my Nexus 7, it sometimes required the POWER BUTTON+VOL DOWN buttons be pressed and held down for a good 30 seconds or more, to generate the necessary 'interrupt', and force the device into the bootloader.
My first instinct, is to suggest you may possibly have a problem with your VOL DOWN button, and maybe it's stuck somehow or not making contact.
It also occurred to me, that you might be able to access the bootloader with...
Code:
adb reboot bootloader
...or possibly...
Code:
adb reboot fastboot
...and even...
Code:
adb reboot recovery
But unfortunately, I'm pretty sure you need to be running fully booted Android or booted into a custom recovery (eg., TWRP) before you can issue ADB commands. I haven't tinkered around in this area of Android for a couple of years now, so my memory of the specifics is a little hazy.
Anyhow, here's a fairly comprehensive listing of Nexus 7 button presses/interrupts, which maybe of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
--------------------------------
Anyway, just some thoughts that might give you some clues/ideas, that may resolve your problem.
Good luck, and I hope you find something that works.
Rgrds,
Ged.
Thanks Ged for the detailed answer.
Unfortunately it seems that my Nexus is not booting complete (not finishing the booting sequence due to corrupted bootloader?) and so I cannot send to it any adb or fastboot command...
I read in the meantime that holding the VOL up button while powering up the Nexus, it will bring it in the APX mode (whatever this mean) and indeed, my computer recognize it as "APX" device.
I hope at least that this is a good sign and a first step to bring my Nexus back to life... but I have no idea what is the APX mode and what can I do in this mode to attempt to save my device...
Do you (or somebody else) have (has) an advice or tutorial for me concerning this?
Regards,
Conrad
Hi Conrad.
I'm in exactly the same situation (I've mistakenly posted a duplicate thread here https://forum.xda-developers.com/nexus-7/general/bricked-tilapia-t4005149). Let's continue here. So:
1. I spent 4 hours trying all possible button press combinations, including VERY long presses. I didn't notice any APX device or Uknown device connected to Windows. I might have missed it, you gave me hope. I will check again.
2. APX mode enables low level access to the chipset via nVidia tool nvflash. You probably came accross these threads here on xda:
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-using-t3342364
https://forum.xda-developers.com/showthread.php?t=2564615
https://forum.xda-developers.com/showthread.php?t=2455927
https://forum.xda-developers.com/showthread.php?t=2340237
I haven't so far, as I was not aware of the visibilty of the tablet in Windows. I will check again.
Well, I must have been blind not to have seen all the posts here on xda and everywhere else. I went through the threads and now I know:
1. I can see the tablet in APX mode in Windows. Possibly I could correctly set up the driver.
2. This would be totally useless, since I hadn't backed up necessary blob.
I have a new paperweight