Database Users

Stuck on Google Logo Bootloop - Nexus 7

My nexus 7 had the randomly turning off issue.
I did the usual; recovery mode, clear cache, attempted to install stock rom etc.
I have got to the nexus logo once, the rest of the time I'm stuck on the Google Logo. It is shown as unlock and I am able to install clockwork recovery but unable to get it past the google logo
Last time I attempted to fix the issue via fastboot:
Creating filesystem with parameters:
Size: 6453985280
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 24620
Label:
Blocks: 1575680
Block groups: 49
Reserved block group size: 391
Created filesystem with 11/394352 inodes and 52512/1575680 blocks
sending 'userdata' (102525 KB)...
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 140.156s
Your device is now stock and unrooted
Any ideas what cause the failed response and how to fix it?
thanks

have you try to install the stock imagen for nexus 7??? be sure that is your version 3g or wifi... the most of the time that problem is related to this

karma123 said:
have you try to install the stock imagen for nexus 7??? be sure that is your version 3g or wifi... the most of the time that problem is related to this
Click to expand...
Click to collapse
Yeah tried installing the stock image via fastboot. Seems to install but get an issue with boot.sig, system.sig and recovery.sig when its installing.
Would it make any difference trying to do it manually rather than doing one click method?

[Q] N7 stuck at google screen, flash write failure, (Hardware replacement advice)

Yesterday, I was using my Nexus 7 tablet and it suddenly restarted itself. Since then it's been stuck at the Google screen every time I try to start the tablet.
Some info on my tablet:
- Running Kitkat 4.4.2 unrooted (did not update to 4.4.3 or 4.4.4)
- Can enter fastboot mode
- Cannot enter recovery mode (just gets stuck at google screen when I enter it)
- My warranty has ran out
I've tried to flash the device but I get this error:
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.745s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.sig'
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 05848e98
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.000s]
sending 'boot' (7014 KB)...
OKAY [ 0.234s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.153s
Press any key to exit...
I trawled through every thread I can find on this forum about this error, most of the time people just send it back to RMA for repairs. (however, my warranty has ran out)
Has anyone had this error and fixed it?
If this is a hardware problem and I want to fix this myself, what hardware do I need to buy? Is a new motherboard enough?

[Q] Nexus 4 bricked ? Please help to understand – Please !

Was on : LSv3.2 ROM / AK.355 AOSP kernal / All of a sudden phone rebooted and ended up in Bootloop
Phone Boots to Boot loader and Recovery just fine , TWRP showing 0MB as storage space. And getting following logs when I try to do MOUNT or FORMAT operation.
E: Cannot munt storage /Data/system etc
And same issue in fresh FAASHING, I get the following message
E: FAILED (remote: flash write failure)
Does this mean my Flash Memory is gone and need to change Motherboard fix issue ? Please let me understand the issue, Any help is deeply appreciated.
RA

Hey.. No relax.. Your software is messed up.. Do this--->>>
1. download the nexus factory image from Google developers
2. download wugfresh toolkit
3. Go to "flash stock+unroot" and tick device is softbricked
4. navigate to the factory image you have downloaded
5. let the toolkit finish,
PS:- DO NOT INTERRUPT THE FLASHING PROCESS
The device should boot up
Sent from my Nexus 4 using XDA Free mobile app

I tried it first; it didn't work (Nexus Root Toolkit by WugFresh) gave same message :crying:. I tried flashing standalone using fastboot commands that also gives same error. Copied the full log from NRT
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
sending 'radio' (45537 KB)...
OKAY [ 1.453s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.469s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
Creating filesystem with parameters:
Size: 14129561600
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3449600
Block groups: 106
Reserved block group size: 847
Created filesystem with 11/863264 inodes and 95427/3449600 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.03
Serial Number........: 003a98544753509d
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot' (6366 KB)...
OKAY [ 0.219s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.328s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...

Oh... yup... flash memory is bad
Sent from my Nexus 4 using XDA Free mobile app

Thanks @ arkangel72.
Any other opinion from anyone ? Please let me know
RA

I browsed the net.. You have to take your phone to LG.. You have a hardware failure
Sent from my Nexus 4 using XDA Free mobile app

Thanks Sir - I have replace the logic board and phone back to work. (Got a Phone whose screen was damaged and swapped the boards) I have followed YouTube video on Nexus 4 fixes to conduct the board replacement, Pretty easy and straight forward.
RA

cant unlock bootloader, tried every method I can find

Command Prompt for manual input...
------------------------------------------------------------------
Try typing "adb help" or "fastboot help" for a full cmd list and syntax info.
Enjoy...
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot oem
unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 5.157s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot oem
unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 7.991s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot -w
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
erasing 'userdata'...
OKAY [ 0.020s]
sending 'userdata' (137526 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.041s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>
Click to expand...
Click to collapse
My nexus7 is stuck in a 'groundhog day' scenario, no matter what I do after reboot it reverts to it's former state, factory reset has no effect and I cant unlock to reflash, any advice? thanks

Everything I've read on this suggests a bad emmc chip or something along that lines.
I do suggest you try different drivers, perhaps from this thread...
http://forum.xda-developers.com/showthread.php?t=1907796
But if it won't unlock , you're dead in the water as far as Modifying goes.
I would return it and get another personally. ?

Darth said:
Everything I've read on this suggests a bad emmc chip or something along that lines.
Click to expand...
Click to collapse
thanks for replying, pretty sure that was the case
Darth said:
I do suggest you try different drivers, perhaps from this thread...
http://forum.xda-developers.com/showthread.php?t=1907796
But if it won't unlock , you're dead in the water as far as Modifying goes.
I would return it and get another personally.
Click to expand...
Click to collapse
been like this since the 4.3 ota update, asked around at the time, nobody had a clue, seems to be a common fault now, Google were not interested... might try Asus

[SOLVED] Unable to manually install nexus 7 (2012) wifi ADB driver

Hi All,
I did a bit of searching and I haven't come across anyone in my situation, but I'm sure it's happened before. I dusted my nexus 7 (2012) wifi model off that I haven't used in a couple years and I was reading up on re-flashing stock and un-rooting. I'd used the NRT previously so I went back to that. I plugged the tablet into one of my USB3 slots and ran through the manual driver installation. Tested ADB and Fastboot and they both functioned.
I didn't care for retaining any data, I just wanted to upgrade to the newest from 4.2.1 which the tablet was running. When running the 'flash stock + unroot' to version 5.1.1 through the NRT, it ran into an error after wiping the partitions whereas it seemed to be an issue with USB3. The specific error:
"data transfer failure (too many open files in system)"
At this point it had wiped the device, but was unable to load anything back on. After looking into the issue, it appears that it was a result of having the device plugged into USB3... I've since plugged the device into USB2, however, I'm unable to get the drivers to recognize in Windows 8.1... I uninstalled the unrecognized device drivers for the USB2 device, rebooted, and attempted a clean install of both the default Google and Universal drivers (in separate install attempts). Neither of which appear to allow NRT to provide ADB access. The manual installation method was what I used for the USB3 ports, but AFAIK the ADB portion requires you to plug the device in with USB debugging enabled and install the drivers on that device. Since I can't load into anything other than the bootloader, I don't believe I can perform this step.
Am I SOL or is there potentially something I can do to breathe life back into this device? Any recommendations would be appreciated!
Thanks,
Nate

Turns out this was stupid easy using Linux (Ubuntu)... Thanks to Zesty01 for building the below thread:
http://forum.xda-developers.com/showthread.php?t=2647106
--
I had the image already downloaded from NRT toolkit so I just had to copy it over.
$ sudo apt-get update && sudo apt-get install -y android-tools-adb android-tools-fastboot
$ rsync -av --progress /complete/image-nakasi-lmy47v/ nexus7/
$ cd nexus7/
$ ls -la
total 764688
drwxr-x--- 2 derp derp 4096 Sep 5 10:48 .
drwxr-x--- 12 derp derp 4096 Sep 5 10:48 ..
-rw-r----- 1 derp derp 54 Apr 7 2015 android-info.txt
-rw-r----- 1 derp derp 5308416 Dec 31 2008 boot.img
-rw-r----- 1 derp derp 5875712 Dec 31 2008 recovery.img
-rw-r----- 1 derp derp 665042344 Dec 31 2008 system.img
-rw-r----- 1 derp derp 106792476 Dec 31 2008 userdata.img
$ sudo fastboot devices
015d18ad5c14161a fastboot
$ sudo fastboot flash system system.img
erasing 'system'...
OKAY [ 0.127s]
sending 'system' (649455 KB)...
OKAY [ 76.742s]
writing 'system'...
OKAY [ 32.124s]
finished. total time: 108.992s
$ sudo fastboot flash recovery recovery.img
sending 'recovery' (5738 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.362s]
finished. total time: 1.051s
$ sudo fastboot flash boot boot.img
sending 'boot' (5184 KB)...
OKAY [ 0.641s]
writing 'boot'...
OKAY [ 0.342s]
finished. total time: 0.983s
$ sudo fastboot -w
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
erasing 'userdata'...
OKAY [ 1.015s]
sending 'userdata' (137526 KB)...
OKAY [ 16.503s]
writing 'userdata'...
OKAY [ 8.402s]
erasing 'cache'...
OKAY [ 0.119s]
sending 'cache' (9052 KB)...
OKAY [ 1.101s]
writing 'cache'...
OKAY [ 0.636s]
finished. total time: 27.776s
$ sudo fastboot reboot
rebooting...
finished. total time: 0.120s
After about 10 minutes of the system loading, it's back up and accessible! Hope this helps someone else!
Nate