[Q] N7 stuck at google screen, flash write failure, (Hardware replacement advice) - Nexus 7 Q&A, Help & Troubleshooting

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?

Related

Can't flash my system

Hey,
one day my phone suddenly stopped working properly so i rebooted it. But instead of rebooting it had a bootloop.
I erased the whole phone and tried to flash the stock image but I get the following errors:
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.109s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.125s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.782s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.798s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
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........: XXXXXXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot' (6366 KB)...
OKAY [ 0.250s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.343s
Press any key to exit...
Now I can not boot the phone or even open recovery mode...
What should I do? Is my Phone bricked? Can I repair it?
Hope you guys will help me.
Thank you for every hint
Seems like bad eMMC. RMA if the phone's under 2 years.
DrFredPhD said:
Seems like bad eMMC. RMA if the phone's under 2 years.
Click to expand...
Click to collapse
Is it for me possible to change the eMMC?
If yes where can I buy one ?
Forget about it. eMMC is a BGA part, you need professional tools or a lot of luck to change one at home successfully. If you could get a new motherboard it would be better, but I don't recommend it as a new motherboard would come blank or clone IMEI and you have no way of changing it to original one, and a used motherboard may have other problems/barred IMEI.
DrFredPhD said:
Forget about it. eMMC is a BGA part, you need professional tools or a lot of luck to change one at home successfully. If you could get a new motherboard it would be better, but I don't recommend it as a new motherboard would come blank or clone IMEI and you have no way of changing it to original one, and a used motherboard may have other problems/barred IMEI.
Click to expand...
Click to collapse
So what should I do now?
My phone is older than 2 years...
You could try follow this guide, but I don't think it will help (it's mainly for people who don't have working bootloader mode). http://forum.xda-developers.com/showthread.php?t=2347060
Failing that, new phone time. Moto G has similar specs at a good price.

[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

[Q] Boot loop, unable to write to 'system'

Hi,
I've been trying to put Nethunter on my nexus and seems to have bricked the device.
My main issue is being unable to write to 'Bootloader' and' 'System'. See below for the problem I'm having.
I've tried a number of different images and variations on the steps but nothing seems to work. Any help would be great! Thanks
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.031s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.062s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.062s]
finished. total time: 0.062s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.016s]
finished. total time: 1.031s
sending 'bootloader' (2100 KB)...
OKAY [ 0.469s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.625s
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 'vendor.img'
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
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d24bc7d10080f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (5184 KB)...
OKAY [ 1.062s]
writing 'boot'...
OKAY [ 0.188s]
sending 'recovery' (5738 KB)...
OKAY [ 1.188s]
writing 'recovery'...
OKAY [ 0.203s]
erasing 'system'...
OKAY [ 0.047s]
sending 'system' (649455 KB)...
OKAY [131.703s]
writing 'system'...
FAILED (remote: (BadParameter))
finished. total time: 144.578s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Hi, if you restart do you have the same apps and system there was before? Or is all erased as it should be according to your erase actions in fastboot?
If all works the same as it was it seems you have the same problem as us. There is unfortunately still no solution for this problem. If it is only a bootloader writing problem I also can't help you out, sorry.
See http://forum.xda-developers.com/showthread.php?t=2588911
There is nothing. It gets stuck on the google logo and never gets past that stage so I assume it's been completely wiped.

Nexus 7 2012 Wi-Fi stucked at bootloader

Hi all, I'm really a newbie and hope you can help me with my Nexus 7 2012 wi-fi.
I tried to downgrade to 4.4.4 ( becasuse from 5.0 the tablet was unusable) following the instructions I found on gottabemobile.
I unlocked the device and everything seemed ok but when I try to write the new image with flash-all.bat I get the following errors, like the computer can't communicate with the device.
Code:
...
OKAY [ 0.000s]
finished. total time: 0.000s
erasing 'boot'...
FAILED (remote: (Timeout))
finished. total time: 2.044s
erasing 'cache'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
erasing 'recovery'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
erasing 'system'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
erasing 'userdata'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
sending 'bootloader' (2100 KB)...
FAILED (remote: (Timeout))
finished. total time: 2.028s
rebooting into bootloader...
FAILED (remote: (Nv3pBadReceiveLength))
finished. total time: 1.014s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 14569963520
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3557120
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/889440 inodes and 97309/3557120 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
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d2856b1400802
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4994 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.179s
If I try a fastboot devices I can see the serial number of the tablet but it is stucked in fastboot mode.
The bootloader is v. 4.23, product name is grouper, the image I'm using is image-nakasi-ktu84p (nakasi-ktu84p-factory-2c6e4d6f.tgz)
In computer management I see Android Device > Android Bootloader Interface
What did I do wrong? Have I bricked the device or it can be saved? Thanks in advance for any help.
Did you try with a different USB cable / a different USB port? Because it looks really as a communication problem.
Nevertheless be sure not to flash one of the factory images which contain a defective bootloader! Normally I am unpacking the factory image and flash boot.img and system.img manually by fastboot, i.e.:
- fastboot flash boot boot.img
- fastboot flash system system.img
Thanks for your help AndDiSa: I changed cable and port and flashed the images one by one and it worked!
Just one question: is Android 4.3 faster that 4.4 on the Nexus 7? Will I miss something big if I downgrade to 4.3?
You should probably even try 6.x

Can't update bootloader from LJ12 to MF01...

Hey all,
My nexus 10 randomly started bootlooping a while back (i was on some custom firmware on something like 4.2, but never bothered to update because I rarely used it). Today I decided to take the plunge and try and restore this thing to stock firmware, so I tried to install the stock firmware on the google site for 5.1.1... and it didn't work. This was the log:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
erasing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.020s
erasing 'recovery'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.021s
sending 'bootloader' (1280 KB)...
OKAY [ 0.163s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.294s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 14273216512
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3484672
Block groups: 107
Reserved block group size: 855
Created filesystem with 11/871408 inodes and 96018/3484672 blocks
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB053T9E
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ12'.
Update requires 'MANTAMF01'.
finished. total time: 0.018s
Press any key to exit...
Apparently, despite writing the MF01 bootloader to the tablet, it didn't take. I tried to do this manually with fastboot, but this also didn't hold - my tablet still defiantly displays its bootloader version as MANTALJ12.
Is there anything I can do to beat the new version into its head? Did I mess something up? Or am I just SOL?
Thanks in advance...

Categories

Resources