No matter how many times I have tried, the combination of Vol Down+Home+Power together does nothing, the phone just continues to load normally, I cannot access download mode.
My S5 (G900F) is on Android 6.0.1, which was the last software update for the phone, I would like to try 7(Nougat) but can't get anywhere near rooting or flashing.
The phone functions fine as it is, but for the last ?? Years I have used Windows Phones so android of quite alien to me but more preferable than apple. I would like to check out what's available in different builds.
anyone any ideas why it won't let me in, USB is enabled and it is in developer mode.
It can be a bit fiddly to do when you're starting off. What I normally do is press and hold in order volume down, home and then power. The boot wont start unless you press the power button so what this does is ensure that the other 2 are pressed by the time you press the power button. Only stop holding all 3 buttons down when it boots into download mode. Hope this helps
Eggleston11 said:
It can be a bit fiddly to do when you're starting off. What I normally do is press and hold in order volume down, home and then power. The boot wont start unless you press the power button so what this does is ensure that the other 2 are pressed by the time you press the power button. Only stop holding all 3 buttons down when it boots into download mode. Hope this helps
Click to expand...
Click to collapse
It doesn't work, That is what I have been doing, The Galaxy s5 screen appears, I keep holding, it disappears, vibrates and re-appears, I keep holding and it disappears again, vibrates and re-appears, it does this 5 times before I get fed up and release the power button and then the other 2, it then goes into the Samsung screen and continues loading, sometimes it goes to the "Optimising Apps" mode with the two spinning cogs before finishing the load sequence.
Thanks for the suggestion but it's not playing as it should.
comuscomp said:
It doesn't work, That is what I have been doing, The Galaxy s5 screen appears, I keep holding, it disappears, vibrates and re-appears, I keep holding and it disappears again, vibrates and re-appears, it does this 5 times before I get fed up and release the power button and then the other 2, it then goes into the Samsung screen and continues loading, sometimes it goes to the "Optimising Apps" mode with the two spinning cogs before finishing the load sequence.
Thanks for the suggestion but it's not playing as it should.
Click to expand...
Click to collapse
Weird...
Plan B - Do you have ADB installed on your computer? link: https://forum.xda-developers.com/showthread.php?t=2588979 (for windows install just in case you don't have it - if you have a Mac or Linux, you'll have to look for it).
Get familiar with ADB if not already: https://www.androidpit.com/how-to-install-adb-and-fastboot
Open command prompt (on windows), enter the command "adb reboot recovery" . It should boot into recovery.
The usual disclaimer is that I am not responsible in the unlikely event that something goes wrong to your phone or computer. Hope this helps
Eggleston11 said:
Weird...
Plan B - Do you have ADB installed on your computer? link: https://forum.xda-developers.com/showthread.php?t=2588979 (for windows install just in case you don't have it - if you have a Mac or Linux, you'll have to look for it).
Get familiar with ADB if not already: https://www.androidpit.com/how-to-install-adb-and-fastboot
Open command prompt (on windows), enter the command "adb reboot recovery" . It should boot into recovery.
The usual disclaimer is that I am not responsible in the unlikely event that something goes wrong to your phone or computer. Hope this helps
Click to expand...
Click to collapse
Thanks for the help, now we have a tale of woe. some things were best not touched, after following a fairly well detailed account of updating to Android 7 the screen filled with line after line of red text and froze.
I had to remove the battery to turn it off, now I have a brick that will not boot. I get the Samsung Galaxy S5 flash screen with a little yellow "Set Warranty Bit : kernel" at the top of the screen.
I think I had better post a new thread about this.
comuscomp said:
Thanks for the help, now we have a tale of woe. some things were best not touched, after following a fairly well detailed account of updating to Android 7 the screen filled with line after line of red text and froze.
I had to remove the battery to turn it off, now I have a brick that will not boot. I get the Samsung Galaxy S5 flash screen with a little yellow "Set Warranty Bit : kernel" at the top of the screen.
I think I had better post a new thread about this.
Click to expand...
Click to collapse
Questions that will help in assisting you: Can you still boot into download or recovery mode? What nougat ROM did you flash? What steps did you take to flash the nougat ROM? What happened?
If you can enter download mode, then you can reflash a stock ROM via odin to hopefully save your S5, you can find one on Sam Mobile. Without the right info, that is the best general advice I can give.
You can try posting a new thread to hopefully recruit more help. If you decide to do so, include the answers to the questions I have posted above. Otherwise, I am happy to attempt to assist you in recovering the functionality of your S5 on this thread.
Eggleston11 said:
Questions that will help in assisting you: Can you still boot into download or recovery mode? What nougat ROM did you flash? What steps did you take to flash the nougat ROM? What happened?
If you can enter download mode, then you can reflash a stock ROM via odin to hopefully save your S5, you can find one on Sam Mobile. Without the right info, that is the best general advice I can give.
You can try posting a new thread to hopefully recruit more help. If you decide to do so, include the answers to the questions I have posted above. Otherwise, I am happy to attempt to assist you in recovering the functionality of your S5 on this thread.
Click to expand...
Click to collapse
No, I can't get into download or recovery, I have tried with the 3 key combo and using ADB, the first still refuses to work and the ADB doesn't find the device.
Smart Switch won't connect nor will Odin.
Lineage 14-1. and open-gapps-arm-6.0-micro.
I had opened a new thread before I got your reply, how do I include your answers into that tread? "Bricked after attempted Update: Help".
Related
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.
Ok I've looked everywhere, maybe not well enough but I have and I can't find the answer to my question. I installed the new official 2.2 on the 10th when it came out in canada here. My phone has worked "ok" for the past 2 days. (lots of new force closes and some major lag in some spots that didn't happen in 2.1) but that's besides the point. Today i was trying to set up a new wallpaper and all of a sudden the screen started flashing on and off. I couldn't do anything to stop it except pull the battery. Now when I turn on the phone it just flashes the opening screen that says "Galaxy S blah blah". and the only way I can stop that is pull the batt. I've tried hard resetting and all that but it always gets stuck at the openning screen. Now I'm still noobish to android stuff. Was too scared to flash anything before the official so if you have any advice that involves other programs/pc i'd appreciate a point in the direction of a walkthrough.
I'd hate to have to send it in and wait the 2 months it takes samsung canada to get it back to me.
Thanks.
http://forum.xda-developers.com/showthread.php?t=732458
tried that, can't get into download mode. as soon as i plug it in it starts looping the boot screen.
canadianrider said:
tried that, can't get into download mode. as soon as i plug it in it starts looping the boot screen.
Click to expand...
Click to collapse
Look up the "jig" solution. That will be guaranteed to set your device on Download Mode.
It was the same problem with my Vibrant. Solved with JTAG controller. But you'll waste your warranty in that way. Try jig solution first
Adb?
Sent from my SGH-T959 using XDA App
ok i have android sdk/adb from when i pulled screen shots with 2.1 ... how could i use that to try and boot my phone
canadianrider said:
ok i have android sdk/adb from when i pulled screen shots with 2.1 ... how could i use that to try and boot my phone
Click to expand...
Click to collapse
option 1
METHOD 2: STUCK AT VIBRANT SCREEN:
(and are not able to use vol+ vol- methods to access downloader/recovery)
You will need the samsung ADB drivers installed for your phone as well as ADB...
ACCESS DOWNLOAD MODE
1) remove back cover and take our sim card and sd-card.
2) take out the battery
3) hold ALL 3 buttons down at the same time. (Vol +, Vol -, Power)
4) while holding down those 3 buttons put the battery back in
5) continue holding all 3 buttons until the vibrant disappears and reappears... once it reappears, release all 3 buttons
6) Setup ODIN and get it all setup and ready... (if you are flashing your phone via odin)
6) now connect your phone to your pc via USB cable
7) open a cmd prompt and navigate to the folder with ADB and type ADB REBOOT DOWNLOAD
8) Your phone will reboot into the download screen... go back to ODIN - A com port should now appear for your phone...
9) Click start and wait for your phone to do its thing
Option 2
***First you must have ROOT***
Download Terminal Emulator from the Market
open terminal emulator
**you may need to change to default android keyboard for proper inputting
1.) type "su" and press enter
a dialog box will appear asking for root access and say yes (obviously)
2.) type "reboot recovery" and press enter
at that moment, ur phone should reboot into Download Mode to load Alternate firmwares for like Eugene's Vibrant4 ROM etc......
this it what it should look like...
#su
#reboot download
Option 3
or you can download and install quick boot from the market which you then can make a shortcut to reboot into recovery with just one click
Sometimes it takes more than one try to get into download mode. I just take the battery out for a little while. Put it back in and hold only the volume up and down buttons while it is off and plug in the USB cable.
One thing though, when holding down the up and down volume buttons, it is very easy to mistakenly press the power button because it is exactly opposite of it.
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:
Hi guys,
Been a samsung user since S2, unfortunately ive made people bring me their devices so i can polish them, if not fix.
I got an i9505 at the moment with a very strange issues:
It boots up, hangs on the boot logo.
It boots in Download Mode, but volume up button wont work, i've opened the device and yet the button was fine.
Sometimes just connecting it to the PC using USB, the device vibrates as if it's turning on, though it vibrates every 2-3 seconds. Device is Off btw.
Recovery Mode wont boot, Home Button + Volume Up + Power Button until the thing vibrates, i release the power button, and it just hangs there. Makes me doubt it is not even reaching the point where it knows where the recovery is. However, i got it in to the blueish "booting recovery..." once, but it hanged there as well.
Am clueless here, (re)searching usually brings me near the answer, but it hasnt, i hope the answers here will do it for somebody else.
Edit: since i am doing this out of pure compassion, i have no idea what is loaded inside .
PlutoDelic said:
Hi guys,
Been a samsung user since S2, unfortunately ive made people bring me their devices so i can polish them, if not fix.
I got an i9505 at the moment with a very strange issues:
It boots up, hangs on the boot logo.
It boots in Download Mode, but volume up button wont work, i've opened the device and yet the button was fine.
Sometimes just connecting it to the PC using USB, the device vibrates as if it's turning on, though it vibrates every 2-3 seconds. Device is Off btw.
Recovery Mode wont boot, Home Button + Volume Up + Power Button until the thing vibrates, i release the power button, and it just hangs there. Makes me doubt it is not even reaching the point where it knows where the recovery is. However, i got it in to the blueish "booting recovery..." once, but it hanged there as well.
Am clueless here, (re)searching usually brings me near the answer, but it hasnt, i hope the answers here will do it for somebody else.
Edit: since i am doing this out of pure compassion, i haven o idea what is loaded inside .
Click to expand...
Click to collapse
Flash a stock rom base in your country mate via odin and you can download it from here http://www.sammobile.com/firmwares/2/ , then once your done downloading the file, Boot into Download mode (Power+VolumeDown) , Open Odin select PDA /AP , Connect both cables (Wait until you get a blue sign in Odin)and flash away.If you encounter any issues with the firmware (Any FC, Bootloop etc)Boot into recovery mode (power+vol up),Choose to wipe/factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD! Then choose reboot and you should be good to go! Have a nice day
Mate, is there a way to flash through Odin without pressing the Vol Up button, cause i am not aware of that?
I cant get past the first point of download mode, to actually enter you need to press Vol up.
PlutoDelic said:
Mate, is there a way to flash through Odin without pressing the Vol Up button, cause i am not aware of that?
I cant get past the first point of download mode, to actually enter you need to press Vol up.
Click to expand...
Click to collapse
try to remove your battery for 10 sec and put it back mate , and then try O press and hold Power+Volumedown to see if you can boot it. or you can try to connect to kies 3
Already done that tbh. Battery was off for like a day. I was hoping for that qualcomm boot mode, but doesnt seem to work.
PlutoDelic said:
Already done that tbh. Battery was off for like a day. I was hoping for that qualcomm boot mode, but doesnt seem to work.
Click to expand...
Click to collapse
I think the best u can do is get it to the service center for repair
Joku1981 said:
I think the best u can do is get it to the service center for repair
Click to expand...
Click to collapse
Hence the thread. There was no other option left.
I usually do this to gain the knowledge for future use, is this a common death for the S4. the user that had it is definitely not a flasher, what couldve gone wrong?
PlutoDelic said:
Hence the thread. There was no other option left.
I usually do this to gain the knowledge for future use, is this a common death for the S4. the user that had it is definitely not a flasher, what couldve gone wrong?
Click to expand...
Click to collapse
Options:
- WATER inside the phone
- Motherboard failed
- The phone felt to the ground
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