Database Users

[How-To] Button combos for the Blessed

Bricked your phone? You've come to the right place, if you're one of the blessed. A lot of the newer Captivates have button combinations disabled. Before you go modding your phone, make sure that you can get into download or recovery using these button combos. If you can't, your best bet is to return your phone to an AT&T store and beg for a new one.
THE BUTTON COMBOS
Power-power
Download-volume up+volume down+plug in usb cord
Recovery-volume up+volume down+power
There you have it. Thanks for reading.

What is the point of this when there are 3 methods in the Odin 3 one click thread which is a sticky? Just curious how this deserves its own thread.

When my phone was stuck at the Galaxy S logo, i was able to send the adb reboot recovery command to it to get into recovery mode.
Are bricked phones normally stuck at the logo too, or was it just me?

I wanted to link to just the button combos in the bible. Also, the one click Odin isn't a sticky anymore.
From mah fonez

Why don't you just link to a single post in a thread or post in the odin thread and link to that single post? Just a suggestion so there isn't too many threads started for just a little information like you posted. Great work on the bible though. Glad to see a lot of stuff being compiled into one thread.

How does this relate to development? With a title like this, i thought we had some button hacks.
BAH!

You should also include more than the button combinations as well if you're going to make this post useful. Simply holding the volume buttons + power will do absolutely nothing on my phone. I spent a good amount of time looking for more detailed instructions on recovery mode when the phone was new and no one posted them. There are also a lot of posts that talk about the at&t splash screen flashing and when to release the buttons but that's not terribly useful either. Download mode is a little more covered but still has lots of people giving different instructions. For those the future new people that might read this thread,
For Recovery mode:
Power off
Hold both volume buttons
Push power
Release power when you see the AT&T splash screen
Release the volume buttons a second or so later
After the splash screen goes away you should be in recovery mode
Continuing to hold all three buttons will simply cause the AT&T splash screen to flash at you. I can also continue to hold the volume buttons after releasing power but it is not needed.
For Download mode:
Power Off
Plug USB into computer
Hold both volume buttons
Plug USB into phone
The above will immediately send my phone into download mode. For flashing, most people recommend the steps below to maximize the chance of success with Odin
Power off
Remove battery, sim, microsd
Open Odin
Plug USB into computer
Hold both volume buttons
Plug USB into phone
Put battery in
You should now be in download mode and free to flash with odin.

I agree with the holding volume up and down while plugging the phone into the computer with Odin opened and configured to flash soon as it detects the phone.
All other methods only add confusion.

How do I get out of download mode?

oh nvm, I just removed battery and I could reboot it fine.

I am stuck on this screen
h ttp://img820.imageshack.us/img820/530/screenshotzz.jpg (remove space I can't post links)
I am on downloading mode but the screen looks like this I am using windows 7 64bit, I tried installing 32 bit on another partition to see if it helped but it didn't
Am I missing something or do you have to have something installed before the procedure

frozenreality44 said:
h ttp://img820.imageshack.us/img820/530/screenshotzz.jpg (remove space I can't post links)
I am on downloading mode but the screen looks like this I am using windows 7 64bit, I tried installing 32 bit on another partition to see if it helped but it didn't
Am I missing something or do you have to have something installed before the procedure
Click to expand...
Click to collapse
You have odin started before you plugged in your usb cable into your phone or computer? Does you computer recognize you phone in mass storage mode? The screen shot you provided shows the phone is not recognized by odin.

I got it now but I am stuck even further odin finished no errors and now the phone just loops on the att logo, or if I try to plug the usb both up and down volume buttons pressed to enter recovery mode again it just loops the battery charging any ideas thanks

This is all covered thoroughly in the "READ BEFORE FLASHING" sticky. Which everyone should read BEFORE flashing!!! Hey, what a coincidence.

[Q] Nexus 7 bricked on laying robot with red exclamation mark

Right... I spent the last 6 hours reading through the forum and Googling about this problem. I learnt a lot (!), but cannot solve the problem, and I now hope someone can help me
Sorry for the lenghty post, but there's a lot of information to share...
Yesterday, my long-awaited Nexus 7 (8Gb) finally arrived. It worked just fine for an hour or so: I got online without any issue, Calendar, Photos, GMail and Contacts were nicely synching and I was really starting to get impressed about the speed and features.
I did download a couple apps, more specifically Aldiko & Moon+ Reader ebook reader apps, and Facebook).
Suddenly --I believe I just started the Facebook app-- the screen turned black and showed strange stripes. The device rebooted and got stuck on the black screen with the white "Google" text. I let it sit there for a while and then instinctively tried to power-off the device by holding the power button for 10 seconds or so. It did indeed reboot, but when the tablet booted up, it popped back to the black Google screen and just sat there.
FYI: The USB cable was connected all of the time, and the first time I plugged the Nexus in, my Win 7 64bit machine recognized the tablet and loaded the drivers for it.
When it got stuck, I decided to continue charging it, thinking that maybe the battery wasn't fully charged and the cause of the problem. I hooked it up to the official charger in a wall socket and let it sit there for a while, while I started searching the web for a solution. After about 30 minutes, when I had read about the power+volume button combination, I tried this combination (until then the Google page showed for more than 30 minutes). The Nexus indeed showed the Fastboot screen, and I had to plug it back in the PC's USB to get the buttons "start", "recovery mode", "power off" and "restart bootloader" working. None of them had any effect.
The fastboot screen showed the product name "grouper", the lock state as "locked"; the bootloader as version 3.34 and the HW version as ER3.
I downloaded the "Nexus root toolkit" from WugFresh and tried to flash it back to "stock" with Android 4.1.1 JRO03D. The tool did show my serial number, btw.... Until then, I had good hopes, but then it went wrong: the tool downloaded the files, unpacked them and said something about "wiping flash" and everything froze. After about 20 minutes, I concluded it had locked-up and unplugged the device.
It now seems to be completely "bricked"...
I can no longer get to the fastboot screen; Not even with the 3-button trick... it always shows the Google screen and immediately shows the "dead robot" screen with the exclamation mark.
The Nexus does not start up Android, so I cannot activate ADB/ USB debugging...
The device is no longer recognized by my PC; the PC doesn't make the "USB hooked up/disconnected" sound anymore
I tried uninstalling the drivers and installed the "naked drivers", no solution -- they show up with yellow exclamation marks
I installed the SDK, and "fastboot.exe devices" shows nothing
I downloaded the "Nexus 7 Toolkit 2.0"; I cannot access the tablet, no serials show, drivers cannot be installed
FYI: I did not try to root it or unlock it. I rebooted my PC, I power-cycled the Nexus, I changed USB ports, sigh...
I'm afraid I actually bricked my device... If so indeed, and given the fact that I cannot access the device with any of the tools/toolkits, is there anything I can do to put it back to factory settings?

Someone else may chime in with some help, but I think using the toolkit screwed you. Had you just used fastboot while you had the bootloader up you could have reflashed the stock rom yourself using the file from here and these commands.. but since you can't get into the bootloader now I think its hosed, but I could be wrong though.

I just noticed that when I press the power + volume up button, my PC detects it as an "Asus Transformer Prime APX Interface"?
Would this be another "way in"? (found something about NVflash on Google?)

Here are two threads on the topic, however I don't think they restore it that way since mostly its done thru the bootloader
http://forum.xda-developers.com/showthread.php?t=1879228
http://forum.xda-developers.com/showthread.php?t=1882753

and people still continue to use toolkits because its easier. in reality its just easier to mess upon your device. reading through the forums i have yet to see someone that messed up their device with fastboot oem unlock amd fastboot flash recovery recovery.img.

To be honest; I feel the toolkits are great for people that know what they're doing and understand the process and are just looking for a quick way to do it.
People that are new to the rooting scene and don't understand the process are the people that SHOULDN'T be using these toolkits. They need to learn about the process and do it a few times manually before even attempting the toolkits.

OK guys, I got the message and yep, shouldn't have used the toolkit. **guilty** :cyclops:
But what advise do you guys have? Would the APX/NVFlash path make sense?
Or can you advise how to get support from Google/Asus in Belgium (bought tablet in Staples US )
thanks!

Considering it doesn't seem anyone has used NVFlash to restore it looks like you are going to have to return/exchange/RMA whatever option is available to you, unless its figured out

i see you pressing volume up and down and power button to get into the bootloader.. but thats wrong. its power button + volume down to get into the bootloader(maybe thatll make a difference for you). but yea, chances are that youll need to go for an exchange/repair.

Nvflash should work though. I haven't used it since.my last tablet and.unfortunately I forget how to use it. I don't think zip files can be used. I think someone could help him that knows how to set up a folder of files for nvflash.

simms22 said:
i see you pressing volume up and down and power button to get into the bootloader.. but thats wrong. its power button + volume down to get into the bootloader(maybe thatll make a difference for you). but yea, chances are that youll need to go for an exchange/repair.
Click to expand...
Click to collapse
hi, the combination did the job before, but just to be sure, I have tried them all:
power + vol up + vol down: black Google screen, followed by the dead robot with exclamation mark sign...
power + vol down: black Google screen, followed by the dead robot with exclamation mark sign...
power + vol up: Goes into APX mode (and PC chimes)

bigooze said:
hi, the combination did the job before, but just to be sure, I have tried them all:
power + vol up + vol down: black Google screen, followed by the dead robot with exclamation mark sign...
power + vol down: black Google screen, followed by the dead robot with exclamation mark sign...
power + vol up: Goes into APX mode (and PC chimes)
Click to expand...
Click to collapse
robot with an exclamation is the stock recovery. it wants to be flashed with the stock google image https://developers.google.com/android/nexus/images#nakasi

simms22 said:
robot with an exclamation is the stock recovery. it wants to be flashed with the stock google .img
Click to expand...
Click to collapse
Hmm... And how would one do this? What tool should be used?

bigooze said:
Hmm... And how would one do this? What tool should be used?
Click to expand...
Click to collapse
read the page and links provided there, the instructions are there.

simms22 said:
read the page and links provided there, the instructions are there.
Click to expand...
Click to collapse
Dont think you can flash those files thru recovery, I already posted that link for him unfortunately without the bootloader I think hes hosed
In order to use these files, you need to have the fastboot tool in your PATH. That tool is compiled as part of every configuration of the Android Open-Source Project and is the tool used to flash custom builds on your device. On GNU/Linux systems, this also implies that you have configured USB access as mentioned in the machine setup instructions.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
Click to expand...
Click to collapse
When the android with the red mark comes up, press power+vol up, does the recovery come up?

simms22 said:
read the page and links provided there, the instructions are there.
Click to expand...
Click to collapse
Oops... getting late here -- didn't notice the link...
Anyway, the instructions indicate the use of the fastboot tool, which do not work :crying:

Haven't seen this before..

Hi guys,
I recently installed Simple ROM (Stock Android 5) for my G2 D802 however, I've found a need to downgrade back to 4.4.2. I went to flash a stock rooted 'H' version of the ROM which i've used before however during the flash, I got the error 'error executing updater binary' during the process.
After searching on google, it seems that I needed a newer version of TWRP (I had to change to a 'bumped' version to install the Simple ROM).
Having flashed 2.8.4 of TWRP, I rebooted the device however I now have the following issues:
- The device boots, shows the LG logo and the LED flashes
- The device never finishes it's boot
- I can not access recovery mode using the key combinations required
- The device doesn't seem to turn 'off'. When I press and hold the power button, the screen goes blank (though, still on) and then shows the LG logo again
I suspect, that because I cannot turn it off, I cannot boot to recovery.
Any thoughts on a quickfix?
EDIT: - It seems that I CAN turn the device off by holding vol UP, DOWN and POWER for a few seconds. I can get into download mode this way..

adaimespechip said:
Hi guys,
I recently installed Simple ROM (Stock Android 5) for my G2 D802 however, I've found a need to downgrade back to 4.4.2. I went to flash a stock rooted 'H' version of the ROM which i've used before however during the flash, I got the error 'error executing updater binary' during the process.
After searching on google, it seems that I needed a newer version of TWRP (I had to change to a 'bumped' version to install the Simple ROM).
Having flashed 2.8.4 of TWRP, I rebooted the device however I now have the following issues:
- The device boots, shows the LG logo and the LED flashes
- The device never finishes it's boot
- I can not access recovery mode using the key combinations required
- The device doesn't seem to turn 'off'. When I press and hold the power button, the screen goes blank (though, still on) and then shows the LG logo again
I suspect, that because I cannot turn it off, I cannot boot to recovery.
Any thoughts on a quickfix?
EDIT: - It seems that I CAN turn the device off by holding vol UP, DOWN and POWER for a few seconds. I can get into download mode this way..
Click to expand...
Click to collapse
Make sure you're trying both combinations possible for recovery, PWR + VOL DWN > PWR + VOL DWN method as well as the PWR + VOL DWN > VOL DWN + VOL UP method. You may be on a different recovery then what you think (happened to me once). The fact you can enter download mode is great however, worst case you can always return to stock.

d00lz said:
Make sure you're trying both combinations possible for recovery, PWR + VOL DWN > PWR + VOL DWN method as well as the PWR + VOL DWN > VOL DWN + VOL UP method. You may be on a different recovery then what you think (happened to me once). The fact you can enter download mode is great however, worst case you can always return to stock.
Click to expand...
Click to collapse
Thanks for this. I've tried recovery both ways, and neither work unfortunately. I'm going to plug it into PC Suite and see if that picks anything up, failing that i'll grab a kdz. :/

adaimespechip said:
Thanks for this. I've tried recovery both ways, and neither work unfortunately. I'm going to plug it into PC Suite and see if that picks anything up, failing that i'll grab a kdz. :/
Click to expand...
Click to collapse
Okay good luck. Make sure you grab your kdz file from a site like http://www.lg-firmware-rom.com using your IMEI.

d00lz said:
Okay good luck. Make sure you grab your kdz file from a site like http://www.lg-firmware-rom.com using your IMEI.
Click to expand...
Click to collapse
Not going so well.. Installed everything on my Windows machine but it doesn't seek to pick up the device in download mode.
If I select 'Read phone information' on the Flash tool, it stops responding and I end up needing to close it. Also, in the Flash tool, what should I select under 'select type' - it defaults to CDMA..
I can skip the 'read phone info' bug and just hit START which then loads the 'select country and language' view, then the LG Mobile Support which doesnt pick up the device.
help?

adaimespechip said:
Not going so well.. Installed everything on my Windows machine but it doesn't seek to pick up the device in download mode.
If I select 'Read phone information' on the Flash tool, it stops responding and I end up needing to close it. Also, in the Flash tool, what should I select under 'select type' - it defaults to CDMA..
I can skip the 'read phone info' bug and just hit START which then loads the 'select country and language' view, then the LG Mobile Support which doesnt pick up the device.
help?
Click to expand...
Click to collapse
Have you installed the LG Drivers? Link
If you have, when your phone is connected open device manager on your PC and see if you can spot your android device, or anything that represents your device.
Everything you need to select is in that thread I Iinked you too.
You dont need to change anything within the tool, keep cdma selected and just make the language english, you can keep the country on korea it doesnt matter.

d00lz said:
Have you installed the LG Drivers? Link
If you have, when your phone is connected open device manager on your PC and see if you can spot your android device, or anything that represents your device.
Everything you need to select is in that thread I Iinked you too.
You dont need to change anything within the tool, keep cdma selected and just make the language english, you can keep the country on korea it doesnt matter.
Click to expand...
Click to collapse
Yup AFAIK everything is installed. The device was picked up by the machine as it did ask me install more drivers.
The main issue seems to be sat with the LG mobile support tool. It continuously fails due to an error and nothing progresses on the device itself.
The only thing i've noticed is that the bottom of the device screen, shows 'B18' and 'Rooted'. The B# keeps increasing, though?

adaimespechip said:
Yup AFAIK everything is installed. The device was picked up by the machine as it did ask me install more drivers.
The main issue seems to be sat with the LG mobile support tool. It continuously fails due to an error and nothing progresses on the device itself.
The only thing i've noticed is that the bottom of the device screen, shows 'B18' and 'Rooted'. The B# keeps increasing, though?
Click to expand...
Click to collapse
The B is just your current battery percentage. It will increase as it gathers charge from the USB connectivity, nothing to worry about.
As for why there's no communication between the software and your phone, I can't explain that but it's obviously looking like a driver problem. Try opening the LG Flash Tool log file found in C:\LGMobileUpgrade\log.txt.
Copy and paste the entire log onto pastebin and I'll have a look at it for you.

d00lz said:
The B is just your current battery percentage. It will increase as it gathers charge from the USB connectivity, nothing to worry about.
As for why there's no communication between the software and your phone, I can't explain that but it's obviously looking like a driver problem. Try opening the LG Flash Tool log file found in C:\LGMobileUpgrade\log.txt.
Copy and paste the entire log onto pastebin and I'll have a look at it for you.
Click to expand...
Click to collapse
Ah good. Thanks!
See below - There were 2 log files, this is the most recent..
http://pastebin.com/JRBmQ1q6
EDIT: further to this, i've looked at the LG mobile support tool on it's own.. That seems to get a lot further than when it's called upon from the update tool. However the battery is now too low.

adaimespechip said:
Ah good. Thanks!
See below - There were 2 log files, this is the most recent..
http://pastebin.com/JRBmQ1q6
Click to expand...
Click to collapse
May I suggest putting your kdz file in the LG Flash Tool folder.
Also does the LG Flash Tool stay at 0% or does it increase before failing? May I also suggest trying this on other Operating Systems if at all possible.

d00lz said:
May I suggest putting your kdz file in the LG Flash Tool folder.
Also does the LG Flash Tool stay at 0% or does it increase before failing? May I also suggest trying this on other Operating Systems if at all possible.
Click to expand...
Click to collapse
I'll give that a go in a moment.
The Flash tool increases several times before failing. Is there a Mac version of the flash tool?

adaimespechip said:
I'll give that a go in a moment.
The Flash tool increases several times before failing. Is there a Mac version of the flash tool?
Click to expand...
Click to collapse
Not that I'm aware of. Have you tried a hard reset?
Take your phone and turn it off.
Wait while your device is shutting down.
Then, press volume down button and power button together until the LG logo appears on the screen.
When the LG logo is displayed, let go of the power button, keep pressing the volume down key and then press once more the power button.
Once you do that, on your LG G2 the factory reset menu will be displayed.
Press power button in order to agree and wait while the hard reset is being completed.

d00lz said:
Not that I'm aware of. Have you tried a hard reset?
Take your phone and turn it off.
Wait while your device is shutting down.
Then, press volume down button and power button together until the LG logo appears on the screen.
When the LG logo is displayed, let go of the power button, keep pressing the volume down key and then press once more the power button.
Once you do that, on your LG G2 the factory reset menu will be displayed.
Press power button in order to agree and wait while the hard reset is being completed.
Click to expand...
Click to collapse
That requires booting into the recovery though right? I can't get to that point. So yes, i've tried that but the LG logo just shows, and does not get to the reset or recovery screens.
The device just sits at the LG logo screen with the LED pulsing and changing colours.

adaimespechip said:
That requires booting into the recovery though right? I can't get to that point. So yes, i've tried that but the LG logo just shows, and does not get to the reset or recovery screens.
The device just sits at the LG logo screen with the LED pulsing and changing colours.
Click to expand...
Click to collapse
No, you could just do it while the phones turned off.
Instructions to do a Master Reset with Hardware Keys can be found here.
The only other option I can give you is attempting the old manual kdz method found here, sorry .

All fixed - first time.. Issue was down to a crappy Windows machine at the office.. Thanks for your help.

Full brick lg k8 k350n 2016

Hello, as the title says I have a full brick, I have tried to testpoint without results, when connecting to the pc install drivers and disconnected after 3 seconds, lgup does not recognize the model, the problem was when installing a custom rom that said the web that was for my cell phone lg k8, I lost the guarantee, what can I do ?.
I've tried everything already and on google I find nothing. Thank you.

I have already researched a bit and the boot.img is the kernel is what I installed, is there no economic way to repair the kernel? a software?

tattoosmistery said:
I have already researched a bit and the boot.img is the kernel is what I installed, is there no economic way to repair the kernel? a software?
Click to expand...
Click to collapse
Well when you install/flash wrong kernel things can get very ugly, or it can refuse to flash in your case it seems like a hard bricked. Did you tried guides for unbricking from this and K10’s forum? Can you access fastboot?

I've been 10 days
Professor Woland said:
Well when you install/flash wrong kernel things can get very ugly, or it can refuse to flash in your case it seems like a hard bricked. Did you tried guides for unbricking from this and K10’s forum? Can you access fastboot?
Click to expand...
Click to collapse
I've been 10 days and all day, I read all the tutorials but all say that I enter fastboot or download mode my cell phone k8 does not react to enter those modes I have tried everything and by software is impossible at least for me , voya try to create a jib usb with 990k resistors that I saw a video on YouTube that explained how to do it if it does not work I will try to talk to a friend who has the octopus to see if it can be fixed since it has support for my model, thanks and Anything that can help me to repair it would be very grateful.

tattoosmistery said:
I've been 10 days and all day, I read all the tutorials but all say that I enter fastboot or download mode my cell phone k8 does not react to enter those modes I have tried everything and by software is impossible at least for me , voya try to create a jib usb with 990k resistors that I saw a video on YouTube that explained how to do it if it does not work I will try to talk to a friend who has the octopus to see if it can be fixed since it has support for my model, thanks and Anything that can help me to repair it would be very grateful.
Click to expand...
Click to collapse
I'm not sure what are talking about here. However can you enter fastboot, how do you mean phone doesn't react?

Professor Woland said:
I'm not sure what are talking about here. However can you enter fastboot, how do you mean phone doesn't react?
Click to expand...
Click to collapse
The mobile does not go in any way with any combination of possible keys, I do not know where the testpoint is, it does not go into the download mode and it does not even leave the logo of lg.
Sorry for my english I use the google translator.

tattoosmistery said:
The mobile does not go in any way with any combination of possible keys, I do not know where the testpoint is, it does not go into the download mode and it does not even leave the logo of lg.
Sorry for my english I use the google translator.
Click to expand...
Click to collapse
So the LG logo appears?
We'll try this :
Press the power key until it gives you vibrate or any sign that phone is going to power on, the press and hold volume down it should give you all black screen with text on bottom saying fastboot mode. If it doesn't try all this but with volume up instead of volume down. I'm not even sure how to enter fastboot since I usually do it from ADB.

Professor Woland said:
So the LG logo appears?
We'll try this :
Press the power key until it gives you vibrate or any sign that phone is going to power on, the press and hold volume down it should give you all black screen with text on bottom saying fastboot mode. If it doesn't try all this but with volume up instead of volume down. I'm not even sure how to enter fastboot since I usually do it from ADB.
Click to expand...
Click to collapse
I already tried all the key combinations and it does not react.Thanks

tattoosmistery said:
I already tried all the key combinations and it does not react.Thanks
Click to expand...
Click to collapse
Well if it's not recognized in any way when turning on then it's hard brick sorry

Is there no program to launch it fastboot directly?

Mine was bricked.
My solution was to enter in download mode, because other modes just rebooted the phone.
So follow this, and luck:
1-you need a PC turned on and the USB cable plugged already
2-quit the battery of the phone
3-now the phone is obviously off, you have to put the battery in WHILE holding volumen up button and then plug the USB still holding that button
It will enter download mode.
If step 3 doesn't work, try the same but with power button held too, with volume up.
Follow this then:
https://www.mylgphones.com/how-to-unbrick-lg-k8-k350-phone-with-lg-up.html

carwave said:
Mine was bricked.
My solution was to enter in download mode, because other modes just rebooted the phone.
So follow this, and luck:
1-you need a PC turned on and the USB cable plugged already
2-quit the battery of the phone
3-now the phone is obviously off, you have to put the battery in WHILE holding volumen up button and then plug the USB still holding that button
It will enter download mode.
If step 3 doesn't work, try the same but with power button held too, with volume up.
Follow this then:
https://www.mylgphones.com/how-to-unbrick-lg-k8-k350-phone-with-lg-up.html
Click to expand...
Click to collapse
It does not Word.

N7 (tilapia) stuck at logo - no fastboot access ...

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