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?
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
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
I was updating my Mom's Nexus 4 to 4.4 (with the intention of bringing it to the current version to address various security issues -- like stagefright), but it appears to have "soft-bricked" as some people are calling it.
- locked bootloader
- not rooted.
- stock firmware
It goes into a "bootloop"? Where the Google logo displays forever (at least 30 minutes) w/o doing anything.
Normally I'd have spent more time doing this (e.g. backing it up, etc). But due to various personal mishaps in the past year, my tech environment is incomplete and a mess. I've never had problems w/ OTA updates so I foolishly went ahead w/o an adb backup -- which would have at least given me most files (even if I have to redo the entire setup). Also, due to poor timing, I was in a rush to get this done so she'd have a week or so before her trip to get used to the small changes (yes, she freaks out over small changes like the camera UI being different). So, whenever you're doing 2 things at once, you never pay attention to one thing fully. And this is also what happened to the OTA update -- so if there were ANY error messages or anything during the update, I did not notice. =(
Unfortunately I also don't have the device in front of me (things like work get in the way of personal masochism -- aka playing with tech).
Anyhow... I'm not exactly certain if it was going to 4.4. When I downloaded the OTA images for the Nexus 4 for 4.4 and tried to flash using the flash-all tool, it complained that the bootloader was not the right one. When I pulled down 4.3 and tried to flash, it did not complain about that bootloader version. So perhaps it didn't properly flash the bootloader? In any case, is there any chance of getting at the files now before a wipe?
What confuses me, is why I cannot flash w/ a STOCK image. Aren't they signed? Even with a locked bootloader, couldn't it in theory let the right images in?
Also, I'm normally in a windows environment, but due to my machines all being down, I'm on the work MacBook Pro instead. So unfortunately I can't try WugFresh's rootkit -- although I'm not sure it would help w/ a locked boot loader.
So... the questions are:
1) Is there a way to flash to a stock OTA image w/o losing data?
2) Or if that's not possible, is it possible to get the data from the phone?
3) Or I'm out of luck and I shouldn't waste any more time trying to recover what's lost?
(Btw, I didn't lose everything -- e.g. I have photos, sms and call logs backed up. WhatsApp used to be backed up, but it seems like both the 3rd party solution and WhatsApp themselves have stopped supporting some sort of offline backup. So mainly just concerned about files in Downloads or Documents or something -- everything else I've made sure was "on the cloud".)
First you might try going into Recovery (assuming you can) and wipe the cache partition, then reboot and see if that fixes it. I have had this glitch occur during an OTA update before (It might have been the 4.4 update actually), and wiping the cache and rebooting fixed it every time.
I am trying to understand what happened and what you did exactly. You have a locked bootloader, aren't rooted, and on stock. You are saying OTA and that you tried to flash via flash-all. Are you using the term OTA and referring to the image files in the tarball as the same thing? OTA is the zip file which only contains the files necessary to go from one version to the next higher version. The .tgz factory image file has all of the image files for a complete build. You would not have been able to flash them with a locked bootloader however. Is that what happened here? You tried to flash the img files on a locked bootloader?
Are you able to boot into Fastboot? (Power off your Nexus 4, and reboot it into fastboot mode by holding the volume down button and power.) If so, will your computer recognize your device? You should install Minimal ADB and Fastboot: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 on your Mac and see if it will recognize your device.
If you can get it recognized in Fastboot, you can then just use the fastboot oem unlock command in a terminal window. If you can get the bootloader unlocked, you can then flash the image files properly to recover the device. Here are some instructions: http://www.androidcentral.com/how-unlock-nexus-4-bootloader (***This will wipe your device and you will lose your data if you have to go this route***)
The first thing I did was to try wiping the cache after recovery mode, but that did not take it out of the boot loop. AFAIK, in 4.3 you can't wipe the dalvik cache from stock recovery. Something similar also happened to me on my Nexus 4 a while back and yes, wiping the cache then did the trick (also think it was 4.4). It fixed it then on my Nexus 4, but not on the current one.
The initial flash was applied OTA. (e.g. There's been an "upgrade" icon in the notifications bar for like over a year.) So you touch the notification, it tells you to reboot and install and I let it w/o paying much attention to it afterwards until I noticed that it only displayed a Google logo afterwards (for over 30 minutes). If that flash takes longer than that, I could have screwed up and interrupted it. :crying: I can't recall how long the 4.4 takes to flash.
Since it was in a boot loop, I thought I could reflash from the tgz images from here: https://developers.google.com/android/nexus/images?hl=en, but of course w/ a locked boot loader, nothing will flash.
Looking at this thread, there seems to be a "manual" way to unlock the boot loader w/o wiping the device IF the Nexus 4 was on a version younger than 4.3.
http://forum.xda-developers.com/nex...ot-unlock-bootloader-wipe-data-t2300480/page4 - comment 35 for "steps", somewhere else for confirmation that it's not working for 4.3 and later.
So, it seems like there is no way to reflash this phone w/ anything w/o wiping the data (4.3 and after) -- which was what this question was about.
So maybe this bears repeating (to be clear). The question is:
Is there a way to recover from a boot loop caused by an OTA update from 4.3 to 4.4 when it is a stock and unrooted rom, with a stock (locked) boot loader without losing data?
-or- Is there a way to recover the data in such a state?
Of course there seems to be a way to JTAG it, but... that scares me (since I've never done that kind of stuff): http://forensicswiki.org/wiki/JTAG_LG_E960_(Nexus_4)
But I do have another question, if I accidentally interrupted the flash, is it possible to get it going again?
This might be insightful (but probably not).
--------
Code:
mbpro:occam-krt16s tofumaster$ ./flash-all.sh
sending 'bootloader' (2203 KB)...
OKAY [ 0.072s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.073s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.437s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.438s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
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: 6189744128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 23612
Label:
Blocks: 1511168
Block groups: 47
Reserved block group size: 375
Created filesystem with 11/378256 inodes and 50366/1511168 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...: MAKOZ20i
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.84
Serial Number........: 0xxxxxxxxxxxxxxb
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MAKOZ20i'.
Update requires 'MAKOZ30d'.
finished. total time: 0.010s
Code:
mbpro:occam-krt16s tofumaster$ cd ..
mbpro:Nexus4 tofumaster$ ls
occam-jwr66y-factory-74b1deab_(v4.3).tgz occam-krt16s-factory-2006f418_(v4.4).md5
occam-krt16s occam-krt16s-factory-2006f418_(v4.4).tgz
mbpro:Nexus4 tofumaster$ md5 occam-jwr66y-factory-74b1deab_\(v4.3\).tgz > occam-jwr66y-factory-74b1deab_\(v4.3\).md5
mbpro:Nexus4 tofumaster$ ls
occam-jwr66y-factory-74b1deab_(v4.3).md5 occam-krt16s-factory-2006f418_(v4.4).md5
occam-jwr66y-factory-74b1deab_(v4.3).tgz occam-krt16s-factory-2006f418_(v4.4).tgz
occam-krt16s
mbpro:Nexus4 tofumaster$ cat *.md5
MD5 (occam-jwr66y-factory-74b1deab_(v4.3).tgz) = 6f6db7729bc6b8089683bc5297a09b93
MD5 (occam-krt16s-factory-2006f418_(v4.4).tgz) = e60c3077c9bc9bd106eb3077992f0d6c
mbpro:Nexus4 tofumaster$ tar xvzf occam-jwr66y-factory-74b1deab_\(v4.3\).tgz
x occam-jwr66y/
x occam-jwr66y/radio-mako-m9615a-cefwmazm-2.0.1700.84.img
x occam-jwr66y/flash-base.sh
x occam-jwr66y/bootloader-mako-makoz20i.img
x occam-jwr66y/flash-all.bat
x occam-jwr66y/image-occam-jwr66y.zip
x occam-jwr66y/flash-all.sh
Code:
mbpro:Nexus4 tofumaster$ cd occam-jwr66y
mbpro:occam-jwr66y tofumaster$ ls
bootloader-mako-makoz20i.img flash-base.sh
flash-all.bat image-occam-jwr66y.zip
flash-all.sh radio-mako-m9615a-cefwmazm-2.0.1700.84.img
mbpro:occam-jwr66y tofumaster$ ./flash-all.sh
sending 'bootloader' (2201 KB)...
OKAY [ 0.072s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.073s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (54321 KB)...
OKAY [ 1.712s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.713s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
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: 6189744128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 23612
Label:
Blocks: 1511168
Block groups: 47
Reserved block group size: 375
Created filesystem with 11/378256 inodes and 50366/1511168 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...: MAKOZ20i
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.84
Serial Number........: 0xxxxxxxxxxxxxxb
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6194 KB)...
OKAY [ 0.200s]
writing 'boot'...
FAILED (remote: not supported in locked device)
finished. total time: 0.213s
mbpro:occam-jwr66y tofumaster$ fastboot devices
0xxxxxxxxxxxxxxb fastboot
A solution!
Okay, just to update anyone following this thread.
I sideloaded this: http: // www . androidpolice . com /2013/11/21/the-nexus-4-finally-gets-4-4-heres-how-you-can-flash-the-kitkat-krt16s-ota-manually-root-or-unlock-not-required/
And it worked. But I haven't slept in over 24 hours, so... I think I'm going to sleep now (have to be up in another 4...). Will post more details later (or answer any questions).
More details
Okay, not much to add, but sometimes these details can be helpful in the future for other people.
When I first posted this, I was past the point of diminishing returns (e.g. where anything you do creates more problems than fixes them). So I was thinking down the wrong path.
ariesgodofwar pointed out that I was trying to apply a the Factory Image over the phone which was NOT the OTA image (which contains only the things it needs to do an update). This clued me in. The OTA update is always a patch. And I'm glad the factory images did not apply because inside the .tgz is a userdata.img which would have wiped all my data anyhow. So... lucky that did not happen.
Instead, I found a signed OTA update (at Android Police) and then used the adb "sideload" technique to apply it. Fortunately, it looked like either nothing was patched successfully the first time, or it happily skipped fully patched files (e.g. maybe it was a mix between 4.3 and 4.4 which was why it was stuck in a boot-loop) and never told me about it on the logs.
Anyhow, it seems to have patched okay, and then went back to the Recovery Menu where I did another Cache Partition Wipe just in case before rebooting. After that, it went to optimizing apps and everything worked as expected. :victory:
In the link above, there's another link that shows you exactly how to get it into the Recover Menu but here it is anyhow: http: // www . androidpolice . com /2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
(btw, how on earth did I post links in the 2nd post???)
Good evening,
I'm getting the following after trying to unlock bootloader using the process found here:
https://forum.xda-developers.com/showpost.php?p=69001601&postcount=2
Here's what I get:
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE552KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 046
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// WIPE-DATA/CACHE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 536870912 bytes
Invalid sparse file format at heade
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 16384
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4096 inodes and 1294/16384 blocks
Creating filesystem with parameters:
Size: 57583562752
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14058487
Block groups: 430
Reserved block group size: 1024
Created filesystem with 11/3515680 inodes and 266738/14058487 blocks
Creating filesystem with parameters:
Size: 134217728
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 32768
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/8192 inodes and 1550/32768 blocks
sending 'config' CRC (0x884ab0fe)...
OKAY [ 0.031s]
writing 'CRC'...
OKAY [ 0.031s]
sending 'config' (512 KB)...
OKAY [ 0.031s]
writing 'config'...
FAILED (remote: permission denied)
finished. total time: 0.140s
So I'm not sure what I'm doing wrong? I tried both the .bat file and the "fastboot flash all unlock_ze552kl.raw".
I appreciate any help/advice I can get.
Thanks,
Steve
Do you tried the official app?
Sent from my Asus ZenFone 3 using XDA Labs