Database Users

[Q] Nexus 7 2012 reboots

My Nexus 7 16GB 2012 has started to randomly reboot, it's running 4.4.2 and has been fine for months. This morning I switched it in, turned off the Airplane Mode and after 30 seconds or so it locked up, then reset. This happens every time I turn off Airplane Mode and switch on WiFi.
I'm wondering if there is some sort of corrupt RAM causing the issue? I've tried to do a Factory Reset, but this also fails and I end up back at square one. So I tried Nexus Root Tookit to go back to stock (all I've done previously is unlock the bootloader, no root). This also fails:
sending 'bootloader' (3911 KB)...
OKAY [ 0.516s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.745s
Any suggestions on what to try next?
This may of course be a hardware fault, the device was bought in Summer 2012 on release.

Hi, you need download image of 4.4 and flash it, because 4.4.2 image has corrupt bootloader. If not work try 4.2.2 image and update to kitkat OTA
Cheers, E11

estape11 said:
Hi, you need download image of 4.4 and flash it, because 4.4.2 image has corrupt bootloader. If not work try 4.2.2 image and update to kitkat OTA
Cheers, E11
Click to expand...
Click to collapse
Thanks for the tip, I'll give that a try.
I have been able to use the Nexus Toolkit to temporarily flash the TWRP. I test my hypothesis about an invalid file system and that fails:
/data/media/0/TWRP errno=30
Anyway, it's downloading the image now so lets see if that fixes the problem.

nigelw said:
Thanks for the tip, I'll give that a try.
I have been able to use the Nexus Toolkit to temporarily flash the TWRP. I test my hypothesis about an invalid file system and that fails:
/data/media/0/TWRP errno=30
Anyway, it's downloading the image now so lets see if that fixes the problem.
Click to expand...
Click to collapse
I'm trying KRT16S and the "Back to Stock" option. The Nexus goes to bootloader mode (so I have Android on back with open door). The flashstock.bat runs in a command tool and displays no errors, but nothing appears on the Nexus 7? The script completes, Nexus reboots and is in exactly the same state.
It doesn't seem to want to accept any kind of update.

nigelw said:
I'm trying KRT16S and the "Back to Stock" option. The Nexus goes to bootloader mode (so I have Android on back with open door). The flashstock.bat runs in a command tool and displays no errors, but nothing appears on the Nexus 7? The script completes, Nexus reboots and is in exactly the same state.
It doesn't seem to want to accept any kind of update.
Click to expand...
Click to collapse
Mmm try enter in recovery and do factory reset, if doesnt work, try image of 4.2.2 I'm sure that works
PD. And use Nexus toolkit
Enviado desde mi Xperia P mediante Tapatalk

lagoskon said:
Give a try with twrp 2.6.3.0.
Latest has issues with backups
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
From TWRP I'm able to Wipe and do Factory Reset. It says successful, but when I restart nothing has changed, still got 4.4.2 installed.
I also tried Back to stock with 4.2.2 JDQ39, device goes to Bootloader mode but fails with this error:
sending 'bootloader' (2096 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: ()
finished. total time: 0.873s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (No such device or address))
finished. total time: 0.000s

Need help, tried to flash and now NP stuck at Google boot screen with unlock icon

Hello,
I'll start off by apologizing for being a noob. I tried to follow the instructions found here but somehow I got stuck in a state where my NP won't boot up. It is stuck at the Google black screen with an unlock icon. I tried to flash the 2.1 Lollirock rom and now i'm stuck in this state.
I have the NP plugged in and can get to the bootloader screen but I can't seem to figure out how to fix this. I downloaded the boot.img and system.img files from the Lollirock XDA page.
Steps I did:
At the bootloader page -
1) fastboot oem unlock (twice)
2) the bootloader screen then said it was unlocked
3) flashboot boot boot.img
4) flashboot flash system system.img
5) flashboot -w
Everything was successful with no errors so I put enabled Normal Boot in the bootloader and it just sits at the Google screen for about a minute and loops.
I tried to download fugu-lmy48n-factory-3b9d8638.tgz from the nexus stock image page and tried flashboot flash system fugu-lmy48n-factory-3b9d8638.tgz and got the error:
< waiting for device >
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.223s]
sending 'system' (457721 KB)...
OKAY [ 16.014s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 18.417s
I unzipped the TGZ file and tried with the TAR file and got the same error.
Then I flashed CM Recovery and that worked and I can get into CM Recovery thinking I can just update with the CM12.1 rom. The problem is that I don't have the zip on the device's sd card so I had to push from ADB by doing -
ADB sideload cm-12.1-20150520-UNOFFICIAL-fugu.zip
and it starts and goes for about 46% and stops with CM Recovery stating:
E: Failed to verify whole-file signature
E: signature verification failed
Installation aborted.
I googled this and people said to turn off signature verification since most roms are signed but I can't find any instructions on how to do that....
I also found an OTA zip of 6.0 and when updating from CM via ADB sideload, it gives me the error:
E: Error in /sideload/package.zip
(Status 7)
So that's where I'm at....not sure what to do next so any help you guys can provide would GREATLY be apprciated. Thanks!!!

Disregard, I think I got it figured out. I guess I was in stock recover and not in CM Recovery. Flashed CM Recovery again and I was able to flash CM12.1. RIght now it's sitting at the loading screen with the happy blue android face.

writing 'vender'... FAILED (remote: Permission denied!)

I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.

Hey, no problem bro! It's called vendor, not vender, and the command is: fastboot flash vendor etc. This should solve your problem (Sorry for my english)

NHagney said:
I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.
Click to expand...
Click to collapse
I'm a Linux guy so you may wish to take this with a grain of salt. I have a vague memory of the same error and it was a case of a misspelled and/or miscapitalized command. I am assuming 2 things -
1) everything has worked up to this point
2)the code presented is exactly what you typed on your computer
Your error may simply be that your misspelled vendor after "fastboot flash"

Thats what i get for being hung over. I'm over here trying to run this as admin all kinds of nonsense. Wondering why this went so smooth last night now running into this. I still don't have a working device. After restarting the device I don't get the OS only the initial google screen. Edit: nevermind. It just posted. TY guys. On to Android 'N' maybe Nuttybar?

Asus ZenFone 2 Laser 551KL Z00TD soft-bricked in bootloop

Hi XDA Community,
I'm in a bit of a pickle. Yesterday my Zenfone started to bootloop and I tried to reset to fabric settings in bootmode but it didn't do anything. Afterwards I put the stockrom (Lollipop) and the latest rom (Marshmallow) and installed them. No errors, but it is stuck in bootloop and I can only enter fastboot mode now and it gets stuck there.
Tried Intel SoC solution, no results and also QFil but it isn't shown under ports.
How can I unbrick it?
Thank you very much.

The way I did it
If you install the latest version of twrp it should automatically boot correctly as if nothing happened. it's strange, but every brick I have had has been fixed that way.

utahja1 said:
If you install the latest version of twrp it should automatically boot correctly as if nothing happened. it's strange, but every brick I have had has been fixed that way.
Click to expand...
Click to collapse
Tried it.
This is the error that it gives me.
g:\adb and recovery>fastboot boot twrp-3.1.1-0-Z00T.img
downloading 'boot.img'...
OKAY [ 0.944s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.953s

So, I finally managed to install the latest version of TWRP and SuperSU (don't know which version, tried two of them and thee TWRP install and finally one of the stuck).
I tried back2stock with 1.14 and 1.17 firmware, but the same problem happened. Bootloop and bootloop, on and on and on. The curious thing is that I didn't encounter any error message during installations so what could be the problem. Is there a log I can see to disover what could be the solution.
Thank you.
adriantamas said:
Tried it.
This is the error that it gives me.
g:\adb and recovery>fastboot boot twrp-3.1.1-0-Z00T.img
downloading 'boot.img'...
OKAY [ 0.944s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.953s
Click to expand...
Click to collapse

fastboot flash boot failed

trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?

Did you solve the problem?

i think you can try https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-restore-hard-bricked-lost-t3838461

ISCYamil said:
Did you solve the problem?
Click to expand...
Click to collapse
Nope. The reason I want to flash stock boot image or patch boot image because of every time flash new flyme rom via TWRP, the phone always rooted and Magisk is not working to hide root. Now I just use as is. The banking app cannot be working with rooted phone.

hall060679 said:
trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?
Click to expand...
Click to collapse
I had the same problem just earlier today. What did the trick for me was installing the ROM using TWRP recovery. Move the stock ROM (you need to zip it for the process) into phone's root directory using your computer and then in TWRP tap on "Install" and find the zipped stock ROM and confirm. Let us know.

try fastboot flash bootimg instead.