Database Users

[Q] can't get to recovery mode after unlocking

Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?

The robot lying on it's back is the stock recovery. You need to flash CWM/TWRP before you can do a Nandroid

itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
Do yourself a favour and learn how to use ADB instead of toolkits that do more harm than good if used by inexperienced users and you`ll learn to do it the right way.
Look here http://forum.xda-developers.com/showthread.php?t=1474956 for how to.
Youtube tutorial link http://www.youtube.com/watch?v=ZY4KSrgi-rE.

itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
If you have Rom Manager Installed and are rooted you should be able to install CWM thru it.

don't have flash recovery on rom manager
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?

itayze said:
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?
Click to expand...
Click to collapse
according to ROM Manager you already have CWM installed and its up to date. Have you tried booting into recovery using ROM Manager?

When I press reboot to recovery directly from rom manager it works...
I'm just affraid that in case that I brick or mess up something I won't be able to get to stock recovery mode.

volume down + power button = bootloader (android on his back) also called fastboot mode
use volume buttons to scroll to recovery then press power button to select it
you should then be in CWM recovery if its installed correctly.
If you are using a custom recovery your stock recovery is gone. You would have to use fastboot to flash the stock recovery image back onto the phone. Its rather simple to do as is flashing the stock image file back onto the phone.

that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Edit: I posted before you edited your comment.
even though I don't know adb, should I learn and follow this guide?
http://www.androidauthority.com/nexus-4-clockworkmod-recovery-134114

itayze said:
that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Click to expand...
Click to collapse
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312

kzoodroid said:
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium

El Daddy said:
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I call it a bug because its an annoying feature. There are a number of threads no how to remove it but using a toolkit to do it is just as easy.

thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !

itayze said:
thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !
Click to expand...
Click to collapse
Glad you got it working. I would still learn adb and fastboot. Though I too use the tool kit every now and then out of convenience.

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

Recovery won't flash

I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4

Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4

T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps

Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.

Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.

OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.

[Q] Nexus 4 "Semi-Bricked" - Boot-Loop no matter what

Hi all,
I'm pretty much at the end of my options with my Nexus 4 and hope that someone here might still have that one genius idea of how to recover the device.
When the device was still running, I've received the 4.4.2 OTA update, which worked flawlessly for about two weeks or so. The nexus wasn't rooted, and bootloader was still locked. Then Android crashed ("Keyboard Stopped Unexpectedly" - reboot), and got stuck at the coloured google bubble screen.
Another attempt to reboot only got me into a bootloop at the Google screen - and I have not even seen the bubbles any more ever since.
I unlocked the bootloader (i.e. including complete wipe), but this didn't change a thing - still boot loop.
Then I tried to install CM11: CWM installed fine through fastboot, but when I try to flash cm-11-20131217-NIGHTLY I get the error message "E:Can't copy META-INF/com/google/android/update-binary. Installation Failed". I get this (or a similar) error with other ROMs as well.
Trying to install via TWRP went even worse.. TWRP recovery installation via fastboot looks ok, but when entering recovery I again see nothing but the "Google" screen.
Trying to flash stock images from developers.google.com (no matter which one, 4.2.2, 4.4.2, or anything in between) via fastboot doesn't change much either: flashing through fastboot seems to work just fine, but booting then leads me right into the Google screen boot loop again. And: the recovery seems not to work at all after a stock image flash: bootloader is ok, fastboot also works, but selecting "Recovery" from the bootloader only gets me to the "Google" screen and I'm stuck.
So the only things which are still working are: Bootloader menu (including everything through "fastboot"), and CWM 6.0.4.3 (touch or non-touch versions), including access via adb.
At this point I don't really mind which ROM version, stock or custom, rooted or not, as long as I can continue to use my phone as a phone. Is there perhaps someone out there who still has an idea what I could try, or who can point me to the one oh-so-easy thing I forgot to do?
Some information that might help (?) from the bootloader:
PRODUCT_NAME - mako
VARIANT - mako 16GB
HW VERSION - rev_11
BOOTLOADER VERSION - MAKOZ10o
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1700.48
CARRIER INFO - None
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - disabled
Thanks a lot for your help, and please let me know if you're missing any information that might help resolve this issue.

Bad the same Problem. I flash everything from stock 4.2.2 (bootloader, radio, system, recovery... And wiped user data) then it works again.
Gesendet von meinem Nexus 4 mit Tapatalk

Flash su updater to update your binaries. Do full wipe and use a tool kit to put stock factory rom, radio, recovery etc. It's virtually impossible to brick the phone
Sent by reversed alian technology.

This shouldn't matter but why haven't you flashed the new radio and bootloader? How did you flash the factory image? If you manually flashed it reconsider flashing it with a toolkit, something like wug's toolkit. I think that should do the trick.
---------- Post added at 12:49 AM ---------- Previous post was at 12:47 AM ----------
howard bamber said:
Flash su updater to update your binaries. Do full wipe and use a tool kit to put stock factory rom, radio, recovery etc. It's virtually impossible to brick the phone
Sent by reversed alian technology.
Click to expand...
Click to collapse
Nevermind, dint read his post.

Nekator said:
Bad the same Problem. I flash everything from stock 4.2.2 (bootloader, radio, system, recovery... And wiped user data) then it works again.
Click to expand...
Click to collapse
I tried that before, without any luck. how exactly did you wipe? with cwm, fastboot? I'll gladly give it another try.

sandy-achar said:
This shouldn't matter but why haven't you flashed the new radio and bootloader? How did you flash the factory image? If you manually flashed it reconsider flashing it with a toolkit, something like wug's toolkit. I think that should do the trick.
Click to expand...
Click to collapse
I did flash the whole set of images (recovery, radio, system, whatever-is-there) from stock android 4.2.2 to 4.4.2 through fastboot. Both with the flash-all script as well as with individual fastboot flash commands. Both with the same result.

howard bamber said:
Flash su updater to update your binaries. Do full wipe and use a tool kit to put stock factory rom, radio, recovery etc.
Click to expand...
Click to collapse
Thanks, I'll try that route.
howard bamber said:
It's virtually impossible to brick the phone
Click to expand...
Click to collapse
Thanks, I guess that'll keep me going for another day or two

If a full flash to stock isn't working then there's probably a hardware fault.

namjf said:
Hi all,
I'm pretty much at the end of my options with my Nexus 4 and hope that someone here might still have that one genius idea of how to recover the device.
When the device was still running, I've received the 4.4.2 OTA update, which worked flawlessly for about two weeks or so. The nexus wasn't rooted, and bootloader was still locked. Then Android crashed ("Keyboard Stopped Unexpectedly" - reboot), and got stuck at the coloured google bubble screen.
Another attempt to reboot only got me into a bootloop at the Google screen - and I have not even seen the bubbles any more ever since.
I unlocked the bootloader (i.e. including complete wipe), but this didn't change a thing - still boot loop.
Then I tried to install CM11: CWM installed fine through fastboot, but when I try to flash cm-11-20131217-NIGHTLY I get the error message "E:Can't copy META-INF/com/google/android/update-binary. Installation Failed". I get this (or a similar) error with other ROMs as well.
Trying to install via TWRP went even worse.. TWRP recovery installation via fastboot looks ok, but when entering recovery I again see nothing but the "Google" screen.
Trying to flash stock images from developers.google.com (no matter which one, 4.2.2, 4.4.2, or anything in between) via fastboot doesn't change much either: flashing through fastboot seems to work just fine, but booting then leads me right into the Google screen boot loop again. And: the recovery seems not to work at all after a stock image flash: bootloader is ok, fastboot also works, but selecting "Recovery" from the bootloader only gets me to the "Google" screen and I'm stuck.
So the only things which are still working are: Bootloader menu (including everything through "fastboot"), and CWM 6.0.4.3 (touch or non-touch versions), including access via adb.
At this point I don't really mind which ROM version, stock or custom, rooted or not, as long as I can continue to use my phone as a phone. Is there perhaps someone out there who still has an idea what I could try, or who can point me to the one oh-so-easy thing I forgot to do?
Some information that might help (?) from the bootloader:
PRODUCT_NAME - mako
VARIANT - mako 16GB
HW VERSION - rev_11
BOOTLOADER VERSION - MAKOZ10o
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1700.48
CARRIER INFO - None
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - disabled
Thanks a lot for your help, and please let me know if you're missing any information that might help resolve this issue.
Click to expand...
Click to collapse
When you enter fastboot mode then enter recovery push the volume + button at the same time as power for 1 second keep doing this until the recovery menu shows then wipe data factory reset. This should be done after flashing a factory image. I don't think the phones bricked I believe you not doing something correctly.
Sent from my Nexus 4 using XDA Premium 4 mobile app

namjf said:
I tried that before, without any luck. how exactly did you wipe? with cwm, fastboot? I'll gladly give it another try.
Click to expand...
Click to collapse
Have you solved this issue?
Sent from my Nexus 7 (2013)

namjf said:
I tried that before, without any luck. how exactly did you wipe? with cwm, fastboot? I'll gladly give it another try.
Click to expand...
Click to collapse
Via fastboot
Gesendet von meinem Nexus 4 mit Tapatalk

greetings !
hello there ! I have a similar problem ! yesterday tried to make ( mistake obviously) the auto instal to CM13 ...something went wrong anda now it just boots and enters a black screen loop.
can acess the bootloader menu but when select recovery it just enters the loo again ....
at first I thought it could be a simple recovery reinstall but can´t get it to be recognized ( ADB ou fastboot)
how to install recovery if the device is not recognized .. ?? ( before the update worked fine )
thanks

You tried different USB cables and USB ports with the phone in fastboot mode?

Nexus 7 2012 stuck in safe mode

When I restart Nexus 7 it always boot up to safe mode. Tablet first shows bootloader menu and when I choose to start, it boot in to safe mode. It looks like volume down button is always pressed on but it don't work - does nothing in bootloader menu, and in safe mode.
I don't use it for some days. I don't remember the tablet being flooded or hit. It just appears. First I thought that it was caused by some bug in LineageOS. I made factory reset, and when it does nothing I set u Android 5.1 again but that also didn't work.
Do you have any idea why this is happening?

You mean you are always booting into recovery when starting up the device? This may happen if there is no valid boot.img / system.img installed. How did you install the current system on your device? Do you have an unlocked bootloader? Do you have the latest bootloader (4.23) installed on your device?

AndDiSa said:
You mean you are always booting into recovery when starting up the device? This may happen if there is no valid boot.img / system.img installed. How did you install the current system on your device? Do you have an unlocked bootloader? Do you have the latest bootloader (4.23) installed on your device?
Click to expand...
Click to collapse
Last thing I did is option Flash Stock + Unroot in Nexus Root Toolkit.
Yes I have bootloader 4.23.

Sorry, but I don't know what the toolkit is doing and whether everything went as expected .. that's the disadvantage of using toolkits.
Best would be to learn how to install and to use fastboot and after that you can decide either to flash stock factory image again or to upgrade to one of the custom ROMs available for the Nexus 7.
Sent from my Nexus 7 using XDA Labs

AndDiSa said:
Sorry, but I don't know what the toolkit is doing and whether everything went as expected .. that's the disadvantage of using toolkits.
Best would be to learn how to install and to use fastboot and after that you can decide either to flash stock factory image again or to upgrade to one of the custom ROMs available for the Nexus 7.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
I think you don't understand me. Nexus Root Toolkit have nothing to do with this. It works 3 years with my Nexus 4 and 1 year with Nexus 7. This problem appeared long after installation of LineageOS.
Ok, I installed Android 5.0 manually and I still have this problem.

Did you notice any error messages while flashing the stock image? Did you do a factory reset after returning to stock?
I am still thinking that your bootloader is closed and you are not really flashing / changing the ROM, but flashing fails and you are remaining in the same state as before. Just as an idea ...
Sent from my Nexus 7 using XDA Labs

I would do one step at a time assuming fastboot and adb work. Search for adb minimal. Download stock zip to same directory. Run fastboot oem unlock. Unzip stock zip and try running flash-all.bat it flashes compatible bootloader and stock zip. If that doesn't work img files are inside stock zip and can be flashed separately.
Sent from my Nexus 6 using Tapatalk

Sorry for leaving you like that.
I took the risk and ordered flex cables with volume buttons. Now the tablet works fine. I'm sorry for the trouble.