Database Users

[Solved] Hard Reset

I forgot my pin on my GT-P7510 and even though there are only three buttons I am able to press I cannot seem to get to a menu with a clear data or reset option. Does anyone know how I may do this?
Edit: I was able to get to the menu on my GF's TAB using `adb reboot recovery`, unfortunately I don't have USB debugging enabled on my device :-/
And just FYI this is what I've discovered:
Holding volume up when powered on brings up a menu with a flashing rectangle over an Android with a shovel and the text "Downloading..." below it, or the USB logo.Using the volume up key will toggle between the two.
Selecting the Android by pressing the voume down key will bring up a "ODIN3 Download Mode (Protocol v2) menu that says the OEM:Lock is unlocked and waiting for a USB cable.
Selecting the USB logo brings up text saying Fastboot USB download protocol.
Holding volume up from the Samsung Galaxy Tab boot screen until boot will bring the device up in safe mode. (Edit: Actually volume up need only be pressed just before the animation is over when it says "Samsung").
Holding volume down after the initial boot logo appears to have no effect.
Holding both after the inital boot logo appears to have no effect.
Update: Solved! I had to manually build the fastboot application on my ubuntu machine in order for the device to appear when running `fastboot devices`. After that it simply required running `fastboot -w`.

Update
I called Samsung support this morning and they informed me that they will not support the device until it launches which is quite lame. I've basically given up trying to find the correct 3-button combo to bring up the restore screen and focused more on the fastboot and Odin3.
I've attempted to get my device recognized when using the `fastboot devices` command so that I can simply perform `fastboot -w` to reset everything however neither on my Linux box nor Windows box will the device appear.
Does anyone have any idea which drivers may work with the fastboot on this device? I've tried the google drivers included in the latest SDK.
I would really appreciate help with this, and would be happy to help out this community as much as I can once I am able to use my device.
Thanks!

bbzbryce said:
I called Samsung support this morning and they informed me that they will not support the device until it launches...
Click to expand...
Click to collapse
Wow, that's kinda weird that they would say that. At the conference they were helping everyone with the devices.

I'm pretty sure that the only way to get into recovery is through adb. It's quite unfortunate.

happilyaccosted said:
Wow, that's kinda weird that they would say that. At the conference they were helping everyone with the devices.
Click to expand...
Click to collapse
I called again later today and the guy attempted to help, however, he said that the documentation is not yet available to him.
smaskell said:
I'm pretty sure that the only way to get into recovery is through adb. It's quite unfortunate.
Click to expand...
Click to collapse
I'm fairly certain I should be able to use either the fastboot or Odin3 interface to reset the device. Anyone have experience with either on this device? Thus far I haven't been able to have the device appear on the fastboot listing.

Odin 3
Anyone have link to odin 3?

Why hasn't fastboot been posted yet?
Having a working fastboot really frustrated me.
Yesterday when I woke up, my Galaxy Tab 10.1 was turned off, and when I powered it on, it would go into an infinite loop with the boot animation. fastboot -w fixed this for me
I'm sad nobody posted their fastboot binary that actually works...so here it is! Compiled this on x86_64 Ubuntu 11.04, but it's a 32-bit binary linked against /lib32 stuff, so if you're on Ubuntu 11.04, make sure you have ia32-libs installed.

I'm having the boot loop problem, but I can ONLY get into "upload mode"
I cannot get into the USB Mode, or the Android OS reset mode that I've read accompanies the Power + Volume down button and Power + Volume up button.
So, from merely "upload mode" what can I do?

[TUTORIAL][CM11][4.4.2] CyanogenMod Tutorial for Sony Xperia Tablet Z (pollux)

I went through a lot of searching and trouble to install CM11 on my Xperia Tablet Z, and I'd like to share a tutorial I made for anyone who is also wanting to accomplish this.
All links are in Dark Green because I cannot post links yet.
1. Download and extract the ADB+Fastboot+Drivers zip (alexpja.com/sony/adb-fastboot-win.zip)
2. Now we’ll unlock the bootloader.
a. If you do not have a Phone app (like I don’t on the SGP351), you can either get the IMEI from About -> Status in the settings OR you can find the IMEI right after the IC code, nearby the barcode on the bottom of the tablet.
b. If you do have a Phone app, enter *#06# to retrieve the IMEI.
c. Save this for later use.​3. Place the tablet into fastboot mode and connect it to the computer.
a. Power off the device
b. Connect USB to computer
c. While plugging in the other side of the USB cable into the tablet, hold down the Vol + button.
d. If your speakers are on, you should a sound.
e. We have to install the drivers for fastboot. Open devmgmt.msc via the Run window or in the Start menu and in Other Devices section, you should see S1 Service or S1 Fastboot (anything containing S1).
i. If it is showing a yellow exclamation mark: Follow 3.e.i.1. If it is not, continue to 3.f.
1. We need to download Flashtool and use the driver setup. Download Flashtool (unrestrict.li/flashtool) and install it.
2. Find cmd.exe, right click it, and select Run as administrator.
a. Type in
Code:
bcdedit /set testsigning on
and press enter.
b. Reboot your computer.​3. Once you have rebooted the computer, open the folder where you installed Flashtool (default: C:\Flashtool).
4. Open up the drivers folder and open Flashtool-drivers.exe.
5. Select the first two driver choices (Flashmode and Fastboot) and select “Xperia Tablet Z Drivers” and continue.
6. A new window will appear, continue on with that.
7. A window like this may appear a few times, just press Install this driver software anyway.
8. Run 3.e.2. again and run
Code:
bcdedit /set testsigning off
. Reboot your PC now or after the tutorial.​f. The LED pulse light above it should be emitting a blue-ish color. The screen will be dark.​4. Now we’ll verify if you have fastboot running.
a. Open the tools folder that was extracted from the ADB ZIP and double-click on START.cmd to open Command Prompt in the current directory (all it does is literally open cmd.exe, you can edit the script to verify).
b. Run the command
Code:
fastboot -i 0x0fce getvar version
. If you get
Code:
<waiting for device>
, then you did something wrong. Retrace your steps! (For example, I get
Code:
version: 0.5
)​5. Go to (unlockbootloader.sonymobile.com) and continue until you reach the screen where you put type in the IMEI and an email address. Type in the first 14 digits of the IMEI (remove the last one) and your email address (not sure if name is required). You should get an email instantly with the key.
6. In the Command Prompt, run
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY is the key you received in the email from Sony.
7. Download whatever release you would like to use on the tablet (I’m using CM 11 nightly) from (download.cyanogenmod.org/?device=pollux)
a. Optional: Also download gapps for Google apps such as Gmail, Google Play Services, etc. (wiki.cyanogenmod.org/w/Google_Apps)​8. Extract the ZIP file (but don’t delete it either) and copy boot.img to the tools folder.
9. If your device is still turned off, turn it on and enable USB storage mode. Copy the CM zip to either the internal storage (sdcard) or, if one is inserted, the microSD card (sdcard1).
10. Place it into fastboot mode again (#3).
11. Go back into the Command Prompt and enter:
a.
Code:
fastboot -i 0xfce flash boot boot.img
b.
Code:
fastboot -i 0xfce reboot
c. Enter recovery.
1. Once it shuts down, rapidly tap the Vol + button in order to get into the recovery.
2. Grep_The_Truth's tip: Look at the LED. It will turn orange and afterwards it'll turn purple. You want to press Vol+ as soon as it changes colors.​12. Select “wipe data/factory reset” and wipe it. Afterwards, go back to main menu.
13. Select “Install zip” and either select “Choose zip from /sdcard” (internal storage) or “Choose zip from /storage/sdcard1” (microSD card).
I’ve had varying experience with installing from the /sdcard because sometimes it doesn’t want to mount /data while wiping (/data/media which is /sdcard is safe in wipe) the tablet, so if you were to install the zip from /sdcard with the error present, it would screw things up. I prefer the microSD card route (/storage/sdcard1), and you don’t even need a big one. 512MB works just fine. The actual path would be /sdcard/0/ when looking for the cm.zip in the internal storage.
14. When you have chosen to install from either /sdcard or /storage/sdcard1, select the cm.zip and install it.
a. If you downloaded gapps.zip, install it the same way as you did with the cm.zip.​15. Go back to the main menu now and select “reboot system now”
a. Once, I had the option to install root access before rebooting, I declined (was planning on rooting after tutorial) but it gave me root anyway.​
That’s it! You can now use CyanogenMod with the Sony Xperia Tablet Z.

Getting in to recopvery
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
c. Once it shuts down, rapidly tap the
Code:
Vol +
button in order to get into the recovery.
Click to expand...
Click to collapse
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.

Grep_The_Truth said:
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Click to expand...
Click to collapse
I'll add it along with mine, because I can do it with no problem.

alexpja said:
I'll add it along with mine, because I can do it with no problem.
Click to expand...
Click to collapse
alexpja Thanks for your tutorial, this is very detailed and easy to follow.
my Xperia is SGP321.
I put it into practice and the results it gives me the "oem unlock" is:
FAILED: (remote: Command nor allowed).
I guess you should treat my tablet has the bootloader locked and not allowed (for now??) the unlocked.
I hope someone gives us the opportunity to unlock the devices and in the future can be unlocked.

I had the same experience where at times the steps were a little confusing, especially for a beginner. Each set of instructions would either leave something out or skim over it as if everyone already knew it. That's understandable since they were probably written for that audience. I soft-bricked my SGP311 at least 10 times.
I was even going to write something like this but I got lazy.
One suggestion I would offer is to request the bootloader unlock key first since it sometimes takes a little while and a person can reduce the possibility of having to stop and wait just when they are making progress.
And for anyone going this route for the first time, don't make my mistake - flash exactly what the instructions say to flash, particularly boot.img. Once you have that recovery flashed you have a lot more control over your device. If something goes wrong in a following step like getting boot loops you can still fix it. But if you get annoyed and start poking at it then you can mess up the recovery. Then you have to reset everything to stock and just about start over.
While I don't want to say something stupid like claiming the tablet is indestructible, I found that whether I got stuck in a boot loop I couldn't get out of or screwed it up so bad that all I could get from the tablet was an occasional LED flash, I could always restore it using Emma. It's annoying to have to start all over but it's a huge relief when it boots normally.

for me flashing was fine and without any error but my Tab doesn't boot up with CM flashed...any idea?

Hanging at reboot
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.

Guess my bootloader won't be unlocked. This is A lot of work. Good job on the write up though maybe one day I'll tackle it.

BOOT LOOP Step 9
All was going well, but step 9 powering on device, now its looping.....Ill use flash tools to put jelly bean on and try again, since i was trying with kitkat...why i suspect kitkat is the issue, before i used to be able to unlock and lock boot-loader with jelly bean but with kitkat it didn't work, which i then forced it via cmd

No GPS
I used the tutorial for my Pollux Windy (WiFi Only) and used the latest nightly. everything went well but my GPS is now broken. Is this a known issue?

kevinsickles said:
Is this a known issue?
Click to expand...
Click to collapse
yep! use search to find out more.

mulebreath said:
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Click to expand...
Click to collapse
Hi,
I've been trying with my Xperia Tablet Z Wi-Fi SGP311. Ran into the same problem. On reboot command the LED was stuck on red for 10 minutes and the cmd window was still open. I unplugged the USB and the LED would not turn off. Tried some things, I don't remember specifically what, but it got the LED to turn off. Now my device can't be detected. I've downloaded Emma and it is not recognising my tablet. I've tried to plug the USB in while hold Vol +, Vol -, and the Power button. No detection for any. All I can do with my tablet is make the LED flash white, purple and red in rapid succession by holding Vol + and Power for 5 seconds.
Anyone know what's happened? I suspect I've completely bricked it :L
EDIT: Apparently there are different modes which you can cycle through. If you hold down Vol + and Power for 5 seconds, the LED will flash according to which mode the tablet is in. The different modes give these flashes:
- 1 White flash
- 3 Rapid which flashes
- A white, purple and red flash in quick succession
To switch between the modes, I hold down Vol+ and Power, and after 5 seconds it will take around 3 more seconds to change modes. One of these modes will not appear unless plugged into a PC. What do these mean and can I do anything with it? Tablet is still bricked.
EDIT2: I've managed to get Emma to recognise my tablet. Turns out the modes do have different purposes. I should be fine now, problem solved. I will just leave the solution here in case anyone runs into the same problem.
Unplug your device and hold Vol + and Power for 10 seconds. At the 5 second mark your LED should flash white ONCE. Keep both buttons held and within 5 more seconds, your LED will flash white THREE times consecutively. This will allow you to enter Flashmode (plug in USB while holding Vol -) and Fastboot (plug in USB while holding Vol +). For Emma to recognise your device, enter Flashmode and you can restore and try again.

Bootloop
I've tried many times to flash cyanogenmod onto my Xperia Tablet Z (SGP311). This is a Wi-Fi only tablet and I have downloaded the versions of CM from (download.cyanogenmod.org/?device=pollux_windy) I've followed all of the steps and tried all of the versions of CM down to 10.2 (I used GApps10.2 for CM10.2). Each version gets stuck in bootloop. I've cleared all data (in CWM - wipe data/factory reset, wipe cache partition, wipe delvik cache) before flashing CM and GApps; however, when I try to clear data I get an error. This is what the tablet says:
-- Wiping Data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cacha
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skiiping format...
Data wipe complete.
Click to expand...
Click to collapse
I'm thinking the "Error mounting /data" is the problem, but I'm not entirely sure, nor am I sure of how to fix it.
Any suggestions?
EDIT: Turns out I'm just really bad with Android stuff. I ended up flashing the original Xperia software, unlocking the bootloader (according to this tutorial's instructions), then I downgraded to 4.1.2, rooted my tablet (forum.xda-developers.com/showpost.php?p=53063218&postcount=14) and installed the PhilZ and TWRP custom recoveries. I didn't get to use them in the end. For some reason CWM kept coming up no matter what combination of buttons I pressed while rebooting. After downgrading and rebooting, I followed the rest of the instructions on this tutorial (from step 7). This time I got no errors while cleaning the disk, cache and delvik cache. Flashed the zip files, rebooted the device and voila, Cyanogenmod11!
Again, I'll leave this edit here in case someone runs into a similar problem. I couldn't get any version of CM until I rooted first.

I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!

tp_88 said:
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
download a proper stock (not bricked) firmware for your device and flash with flashtool.

Rootk1t said:
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Click to expand...
Click to collapse
What makes you think that the stock firmwares I've tried are bricked? I've since my post tried one which I downloaded through Flashtool - same result.

[Q] Bootloop, cant get into fastboot

Hi
I rooted my nexus 10 some months ago. All worked fine until yesterday. I wanted to go back to original firmware and used the WUGs nexus root toolkit to download 4.4.3 version and flash it. But afterwards the tablet doesnt boot anymore. Google logo appears and then the circle thing never goes away. I searched many threads, and all base on going into fastboot and flash again, but thats the problem. I cant get into fastboot. The usual combination (Power and vol+ and vol-) doesnt work! I tried many other combinations with different timings, longer press only vol+ and power ...., I always get to google logo after it vibrates.
Is there any other way to get into the fastboot mode ?
Can I connect it to the computer and interrupt the boot process when I switch it on via the PC?
thanks in advance
regards
Erich

Try to connect it to PC with original usb cable and run "adb devices".
If you see Nexus device, you can try "adb reboot recovery" and upload a ROM to /sdcard with "adb push" for flash it.

Hi
Thanks for your relpy.
But thats the problem, even if I could upload a file with adb, which is not working, how would I flash it if I cant get into fastboot or recovery mode ???
thanks anyway
regards
Erich

I think what patzzz is saying is that it depends on your bootloop, often is the case that when someone is in a bootloop the kernel does initiate and adb is functional. Not always but at times for sure.
So if so you can attempt
adb reboot recovery
Or
adb reboot bootloader
If the above doesn't work than you will have to continue trying to boot to bootloader manually with key presses (which I believe is power on while holding volume down)
Best of luck!

Hi
Thanks for the tip. Unfortunately it doesnt work. It made a batch file which calls adb devices and adb reboot bootloader in a loop, so it can send it to the device if it is found, but the tablet isnt regonized, tried some reboots and no luck, adb cant find it )))-:
regards
Erich

It seems a brick, but you can try using fastboot command instead of adb:
Code:
fastboot devices
fastboot reboot-bootloader

hundsmiachn said:
Hi
I rooted my nexus 10 some months ago. All worked fine until yesterday. I wanted to go back to original firmware and used the WUGs nexus root toolkit to download 4.4.3 version and flash it. But afterwards the tablet doesnt boot anymore. Google logo appears and then the circle thing never goes away. I searched many threads, and all base on going into fastboot and flash again, but thats the problem. I cant get into fastboot. The usual combination (Power and vol+ and vol-) doesnt work! I tried many other combinations with different timings, longer press only vol+ and power ...., I always get to google logo after it vibrates.
Is there any other way to get into the fastboot mode ?
Can I connect it to the computer and interrupt the boot process when I switch it on via the PC?
thanks in advance
regards
Erich
Click to expand...
Click to collapse
I suggest you do a factory reset from the stock. You have gone back to stock firmware so you should have stock recovery. I had this happen once and this work for me.

Hi
I will try it with fastboot too, maybe it works....
How can I do a factory reset without recovery mode ?
thanks
regards
Erich

hundsmiachn said:
Hi
I will try it with fastboot too, maybe it works....
How can I do a factory reset without recovery mode ?
thanks
regards
Erich
Click to expand...
Click to collapse
https://support.google.com/nexus/answer/4596836?hl=en
1.If your tablet is on, turn it off.
2.Press & hold the Power, Volume Up, and Volume Down buttons at the same time for several seconds. You'll see the word "Start" with an arrow drawn around it.
3.Press the Volume Down button twice to highlight Recovery mode.
4.Press the Power button to start Recovery mode. You'll see an image of an Android robot with a red exclamation point and the words "No command."
5.While holding down the Power button, press the Volume Up button.
6.Use the volume buttons to scroll to "Wipe data/factory reset," then press the Power button to select it.
7.Scroll down to "Yes - erase all user data," then press the Power button to select it.

>>2.Press & hold the Power, Volume Up, and Volume Down buttons at the same time for several seconds. You'll see the word "Start" with an arrow drawn around it.
Thats the problem, it doesnt work! Tried it a dozent times, only Google logo appears.....
regards
Erich

hundsmiachn said:
>>2.Press & hold the Power, Volume Up, and Volume Down buttons at the same time for several seconds. You'll see the word "Start" with an arrow drawn around it.
Thats the problem, it doesnt work! Tried it a dozent times, only Google logo appears.....
regards
Erich
Click to expand...
Click to collapse
Are your volume keys even working?
Sent from my Nexus 10 using Tapatalk

Delete

Volume Down jammed - can't boot past the bootloader

Hi
The Volume Down button is jammed (the phone fell and landed on its edge slightly crushing the frame where the volume down is). Curiously the Volume Up button still increased the volume.
After turning the phone off the problem came when turning on the phone as it now only boots into the bootloader as a result of the jammed Volume Down button.
Once in bootloader mode, the volume up/down buttons do not change the reboot options - it appears the stuck Volume Down button is causing this.
The way to fix this is to take the phone apart (as per the Youtube clips) and physically straighten the frame.
This is no easy task, so the question: is there a way around this so that the phone can boot?
It's rooted and fastboot commands work. (I installed TWRP but can only boot to recovery with adb).
Any help will be appreciated. Thank you.

fastboot reboot system?

fury683 said:
fastboot reboot system?
Click to expand...
Click to collapse
No, the device is reading the hardware correctly and booting to bootloader. The only way to fix this is to fix your device.

akellar said:
No, the device is reading the hardware correctly and booting to bootloader. The only way to fix this is to fix your device.
Click to expand...
Click to collapse
He said he could still issue fastboot commands. If the device is OFF and he has to press the POWER button to turn it on, it is reading the VOL DOWN as being pressed as well. If he issues the reboot command in Fastboot, it should boot into system because he won't need to press the POWER button and VOL DOWN (being pressed by the bent frame) at the same time, right?
OP also said he could get to recovery from ADB, but I think he meant Fastboot because ADB is only available when you are booted to Android.

Clarification
"I installed TWRP but can only boot to recovery with adb" is unclear.
I was meaning that one can only boot directly to recovery using adb. In fastboot, one can't get to recovery.
At the moment adb can't be used - only fastboot.
When I issue the fastboot reboot command, it just returns to the bootloader. I was hoping it would bypass the Volume Down state, but sadly no.
Thanks for your input though - I knew it was a longshot.
By the way, the phone wasn't dropped, but came out of my pocket going up some stairs - the bigger size makes it not as stable!

A bit late to reply, but for the sake of the next guy that comes looking, the command you were looking for is:
Code:
fastboot continue
This should tell the bootloader to boot into system.
You are still right about not being able to boot into recovery from bootloader (that's the headache I am currently having)

Any way of disabling the volume key altogether without doing anything physical to the phone?
I tried editing Generic.kl from /system/usr/keylayout/, but that only makes a difference when the phone is booted, not before that. Any way to disable the key before the phone has booted?
Cuz this is my mum's phone and she will have no idea what "fastboot" is

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