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???)
Related
Okay, so I'm having what I believe to be a strange issue and was hoping someone here might be able to help.
One day my Nexus 7 (2012/wifi/grouper) started to reboot while sitting on my desk. It then would go into a boot-loop. I turned if off for a bit and every time since it does the same thing. Loads up correctly but after any amount of time it will do the same thing.
So I tried a Factory Wipe & Erase. It went through the whole deal and I rebooted it; but the device didn't wipe or erase, everything was still on the device. >.>
So I decided to flash back to stock. (device was/is unlocked/rooted). Updated the SDK and made sure adb and fastboot both work correctly and that I had the most recent updates to anything available. USB drivers are current and working correctly. Fantastic I say to myself as I go through the fastboot process of returning to stock.
Code:
C:\android-sdk\platform-tools>fastboot devices
015d2d42201c1213 fastboot
I hit fastboot devices and it shows me my device, so I go through the normal bits. This is what I get:
Code:
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.283s]
writing 'bootloader'...
OKAY [ 0.596s]
finished. total time: 0.879s
Awesome! It appears everything is working fine, so I figure I might as well continue.
Code:
C:\android-sdk\platform-tools>fastboot -w update image-nakasi-krt16s.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d2d42201c1213
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.019s]
sending 'boot' (4990 KB)...
OKAY [ 0.652s]
writing 'boot'...
OKAY [ 0.177s]
sending 'recovery' (5530 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.184s]
erasing 'system'...
OKAY [ 0.021s]
sending 'system' (611886 KB)...
OKAY [ 78.120s]
writing 'system'...
OKAY [ 27.180s]
erasing 'userdata'...
OKAY [ 0.030s]
formatting 'userdata' partition...
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
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 25.415s]
erasing 'cache'...
OKAY [ 0.012s]
formatting 'cache' partition...
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
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.655s]
rebooting...
finished. total time: 134.326s
Alright, we're booting back into the device and it appears to have gone fine! But then I notice I'm still seeing the Jellybean "X" boot screen and think to myself well, that's kind of strange...The Nexus 7 loads up and...nothing changed. The device still has everything on it that it had previously, nothing has been changed or deleted.
I've tried deleting (user data such as music or videos) using Windows Explorer. I've tried File Manager and ES File Explorer via the tablet. But every, single time I turn the device back on...everything is still there!
So I guess what I'm trying to figure out is...am I high? Did I die in my sleep and I'm just not aware of it yet? Has my Nexus 7 been cast for a sequel of Groundhog's Day?
What am I missing here? I've done this time and time again but I don't think I've ever seen something like on any of my previous devices (or with this N7 in question as well...)
Hopefully I'm missing something very minor here and someone will make me feel stupid for it. I don't mind feeling stupid if it means I learn something new! (Any and all help would be greatly appreciated.)
limbonik said:
Okay, so I'm having what I believe to be a strange issue and was hoping someone here might be able to help.
One day my Nexus 7 (2012/wifi/grouper) started to reboot while sitting on my desk. It then would go into a boot-loop. I turned if off for a bit and every time since it does the same thing. Loads up correctly but after any amount of time it will do the same thing.
So I tried a Factory Wipe & Erase. It went through the whole deal and I rebooted it; but the device didn't wipe or erase, everything was still on the device. >.>
So I decided to flash back to stock. (device was/is unlocked/rooted). Updated the SDK and made sure adb and fastboot both work correctly and that I had the most recent updates to anything available. USB drivers are current and working correctly. Fantastic I say to myself as I go through the fastboot process of returning to stock.
Code:
C:\android-sdk\platform-tools>fastboot devices
015d2d42201c1213 fastboot
I hit fastboot devices and it shows me my device, so I go through the normal bits. This is what I get:
Code:
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.283s]
writing 'bootloader'...
OKAY [ 0.596s]
finished. total time: 0.879s
Awesome! It appears everything is working fine, so I figure I might as well continue.
Code:
C:\android-sdk\platform-tools>fastboot -w update image-nakasi-krt16s.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d2d42201c1213
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.019s]
sending 'boot' (4990 KB)...
OKAY [ 0.652s]
writing 'boot'...
OKAY [ 0.177s]
sending 'recovery' (5530 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.184s]
erasing 'system'...
OKAY [ 0.021s]
sending 'system' (611886 KB)...
OKAY [ 78.120s]
writing 'system'...
OKAY [ 27.180s]
erasing 'userdata'...
OKAY [ 0.030s]
formatting 'userdata' partition...
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
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 25.415s]
erasing 'cache'...
OKAY [ 0.012s]
formatting 'cache' partition...
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
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.655s]
rebooting...
finished. total time: 134.326s
Alright, we're booting back into the device and it appears to have gone fine! But then I notice I'm still seeing the Jellybean "X" boot screen and think to myself well, that's kind of strange...The Nexus 7 loads up and...nothing changed. The device still has everything on it that it had previously, nothing has been changed or deleted.
I've tried deleting (user data such as music or videos) using Windows Explorer. I've tried File Manager and ES File Explorer via the tablet. But every, single time I turn the device back on...everything is still there!
So I guess what I'm trying to figure out is...am I high? Did I die in my sleep and I'm just not aware of it yet? Has my Nexus 7 been cast for a sequel of Groundhog's Day?
What am I missing here? I've done this time and time again but I don't think I've ever seen something like on any of my previous devices (or with this N7 in question as well...)
Hopefully I'm missing something very minor here and someone will make me feel stupid for it. I don't mind feeling stupid if it means I learn something new! (Any and all help would be greatly appreciated.)
Click to expand...
Click to collapse
I'm not an expert on these things but I basically have a question for you. If you're willing to wipe out the whole thing, have you tried doing the factory reset via settings?
Sent from my Nexus 7 (2013)
Thanks for the suggestion. I have tried Factory wipe from inside the device and it says it completes and I reboot to everything on the device.
I've also tried wiping everything out using TWRP and it to gives me a completion message, but after start up everything is still on the device.
I've also went into TWRP under advanced options, used the built in file explorer and deferred everything from the "sd card". But once again the device reboots, loads up...And everything is there once more!
That's why I wasn't sure if I might be high or dead. I am completely dumbfounded by what's occurring here. -.-
Sent from my Nexus 7 (2013) running 4.4
limbonik said:
Thanks for the suggestion. I have tried Factory wipe from inside the device and it says it completes and I reboot to everything on the device.
I've also tried wiping everything out using TWRP and it to gives me a completion message, but after start up everything is still on the device.
I've also went into TWRP under advanced options, used the built in file explorer and deferred everything from the "sd card". But once again the device reboots, loads up...And everything is there once more!
That's why I wasn't sure if I might be high or dead. I am completely dumbfounded by what's occurring here. -.-
Sent from my Nexus 7 (2013) running 4.4
Click to expand...
Click to collapse
Wow! Are you there's no cameras outside your window, shooting for the next Twilight Zone movie?
The only thing I can think of is using a Toolkit like WugFresh and see if that works, other than that, I'm at a total loss.
Sent from my Nexus 7 (2013)
Oh~ ho! I have also tried Wugfresh and ADB Sideload from within TWRP; same thing occurs.
I've also moved the zip to the device from Windows Explorer to the root directory, but when I reboot to recovery to install from TWRP the file is no longer there! >_<
Sent from my Nexus 7 (2013) running 4.4
limbonik said:
Oh~ ho! I have also tried Wugfresh and ADB Sideload from within TWRP; same thing occurs.
I've also moved the zip to the device from Windows Explorer to the root directory, but when I reboot to recovery to install from TWRP the file is no longer there! >_<
Sent from my Nexus 7 (2013) running 4.4
Click to expand...
Click to collapse
I've got exactly the same problem. N7 (2012) which is constantly booting into the same state. The same apps try to update themselves from the play store, the same screen etc etc.
I've tried the basic factory reset from the menus - when it reboots nothing has changed. I've removed the other user account from the N7 that I keep locked for work use. It seems to disappear, but when I reboot its there again. I've tried booting into recovery mode, selecting "wipe data/format" (or whatever it says), it says that has gone OK, then it reboots and nothing has been changed / deleted - its still in the same state.
I've rebooted into fastboot mode and used WUGS toolkit to flash stock + unroot in the soft-brick / bootloop mode (both with the force flash option on and off), they both report it is working fine, reboots and there are absolutely no changes at all made to the device.
I turn wifi off, reboot and wifi is back on again. I enable developer options / usb debugging, reboot and they are gone again. Its as if some part of the flash storage has gone completely unwritable, but what is really odd is that whilst the device is on, it behaves as if things are changing - apps appear to update, and be installed, options get changed etc. But nothing at all "sticks" after a reboot! Plus I am lucky if the device stays booted for more than a couple of minutes, it is constantly self--rebooting.
Did you ever find a fix for this, its driving me mad!!
Matt
(Edit - placed a call to google support, and they are sending me a replacement - despite it being 18 months since purchase! Impressed!!)
larkim said:
I've got exactly the same problem. N7 (2012) which is constantly booting into the same state. The same apps try to update themselves from the play store, the same screen etc etc.
I've tried the basic factory reset from the menus - when it reboots nothing has changed. I've removed the other user account from the N7 that I keep locked for work use. It seems to disappear, but when I reboot its there again. I've tried booting into recovery mode, selecting "wipe data/format" (or whatever it says), it says that has gone OK, then it reboots and nothing has been changed / deleted - its still in the same state.
I've rebooted into fastboot mode and used WUGS toolkit to flash stock + unroot in the soft-brick / bootloop mode (both with the force flash option on and off), they both report it is working fine, reboots and there are absolutely no changes at all made to the device.
I turn wifi off, reboot and wifi is back on again. I enable developer options / usb debugging, reboot and they are gone again. Its as if some part of the flash storage has gone completely unwritable, but what is really odd is that whilst the device is on, it behaves as if things are changing - apps appear to update, and be installed, options get changed etc. But nothing at all "sticks" after a reboot! Plus I am lucky if the device stays booted for more than a couple of minutes, it is constantly self--rebooting.
Did you ever find a fix for this, its driving me mad!!
Matt
(Edit - placed a call to google support, and they are sending me a replacement - despite it being 18 months since purchase! Impressed!!)
Click to expand...
Click to collapse
Now THAT'S support! :thumbup::thumbup:
Sent from my Nexus 7 (2013)
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.
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
Infinite reboot problem
I need help, my nexus has been continously rebooting by itself. It starts, goes to my homescreen for a few seconds and reboots. I can boot in the bootloader and have tried to do a factory reset, but it just stays a long time in formatting data. After waiting a complete day I decided to stop the process and start again my tablet. It just went to my home screen and again it kept rebooting. It didn't wipe anything.
Next I tried to fastboot flash a stock image, it never gave me any kind of error. My tablet rebooted, but it just went to my home screen, and clearly the image wasn't installed. And again it started the rebooting process.
C:\Users\Username\Downloads\fastboot>fastboot flash bootloader bootloader-manta-mantamf01.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.359s
C:\Users\Username\Downloads\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Username\Downloads\fastboot>fastboot -w update image-mantaray-lmy48x.zip
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: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 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...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32CB03FJ1P
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ -0.000s]
sending 'boot' (4982 KB)...
OKAY [ 0.626s]
writing 'boot'...
OKAY [ 0.016s]
sending 'recovery' (5548 KB)...
OKAY [ 0.688s]
writing 'recovery'...
OKAY [ 0.016s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (656930 KB)...
OKAY [ 80.289s]
writing 'system'...
OKAY [ 5.318s]
erasing 'userdata'...
OKAY [ 0.020s]
sending 'userdata' (139141 KB)...
OKAY [ 16.687s]
writing 'userdata'...
OKAY [ 1.162s]
erasing 'cache'...
OKAY [ 0.016s]
sending 'cache' (10372 KB)...
OKAY [ 1.266s]
writing 'cache'...
OKAY [ 0.094s]
rebooting...
finished. total time: 106.464s
Click to expand...
Click to collapse
Also, I tried to re-lock the bootloader with fastboot oem lock, it said Ok, but the status didn't change (I have a warranty and I think is time to use it, but I need to lock the bootloader). Thanks in advance for your help.
C:\Users\Username\Downloads\fastboot>fastboot oem lock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Click to expand...
Click to collapse
Uldar said:
I need help, my nexus has been continously rebooting by itself. It starts, goes to my homescreen for a few seconds and reboots. I can boot in the bootloader and have tried to do a factory reset, but it just stays a long time in formatting data. After waiting a complete day I decided to stop the process and start again my tablet. It just went to my home screen and again it kept rebooting. It didn't wipe anything.
Next I tried to fastboot flash a stock image, it never gave me any kind of error. My tablet rebooted, but it just went to my home screen, and clearly the image wasn't installed. And again it started the rebooting process.
Also, I tried to re-lock the bootloader with fastboot oem lock, it said Ok, but the status didn't change (I have a 3 year warranty that will expire this december, and I think is time to use it, but I need to lock the bootloader). Thanks in advance for your help.
Click to expand...
Click to collapse
Hello, did you try to boot on a custom recovery ?
fastboot boot recovery x.img will work.
From there you might try formatting / installing a custom rom.
Khaon said:
Hello, did you try to boot on a custom recovery ?
fastboot boot recovery x.img will work.
From there you might try formatting / installing a custom rom.
Click to expand...
Click to collapse
Yeah, I tried to do a factory reset with twrp, but it didn't work. It stays a long time in formatting cache using make_ext4fs function and doesn't make any progress. I left it like that for 6 hours after I decided to finish the process. It started again, went to my homescreen and kept rebooting.
Uldar said:
[/HIDE]
Yeah, I tried to do a factory reset with twrp, but it didn't work. It stays a long time in formatting cache using make_ext4fs function and doesn't make any progress. I left it like that for 6 hours after I decided to finish the process. It started again, went to my homescreen and kept rebooting.
Click to expand...
Click to collapse
What is the output of " adb shell dmesg" when you are inside the recovery mode ?
Seems that most likey your eMMC is dead.
timed out sending SET_BLOCK_COUNT command, card status 0x400d00
Click to expand...
Click to collapse
You could try formatting with f2fs but fi you already tried unlock/lock I don't think it will helpas it erase the whole storage.
Khaon said:
Seems that most likey your eMMC is dead.
You could try formatting with f2fs but fi you already tried unlock/lock I don't think it will helpas it erase the whole storage.
Click to expand...
Click to collapse
Thanks a lot for your help, I'm going to send it under warranty and see if they can fix it. I hope they don't reject it because the bootloader is unlocked.
PIT files
My nexus 10 has the boot loop problem and I think I have been left with the only option of Re-Partition but I need the PIT file. Can anybody help or provide this file?
I have tried everything else (fastboot, adb, temporary custom recoveries, Nexus Root Toolkit) with no success.
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