I was using phone normally, and installed an app from app store, and tried to run it, and force closed, and then google play force closed. So I decide to reboot phone, and it just gets stuck at boot screen. I let it wait for like 10mins then I turn off and boot into recovery, where I get errors that can't find /cache and /data. Anyway I can recover without losing my /data like rebuild partitions? Any idea what happened? I am using CM11 M7, and don't have it overclocked or anything.
Thanks,
CP
What app was it. Did you make a nandroid recently? Can you boot into recovery?
Sent from my Nexus 5 using XDA Free mobile app
Factory reset should fix it, as for recovering data it's gonna be difficult if the phone can't mount the partitions. If you have unlocked bootloader you could possibly use adb shell to dd the partition and then try to recover data from that, but without external memory I can't think how you'd do it.
jd1639 said:
What app was it. Did you make a nandroid recently? Can you boot into recovery?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The app was just a clock app from store, nothing exciting. And no I hadn't run a nandroid recently, but woudn't have helped anyway, since /sdcard is missing also which is where CWM stores backups, though I can get into recovery.
I'm home now and got onto adb, and see these errors:
mmcblk0: timed out sending r/w cmd command, card status 0x400940
Click to expand...
Click to collapse
Anyway to rebuild phone?
CptanPanic said:
I'm home now and got onto adb, and see these errors:
Anyway to rebuild phone?
Click to expand...
Click to collapse
Sounds like you should flash the factory image in fastboot.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Sounds like you should flash the factory image in fastboot.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So I tried that now, but I get
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.079s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.461s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.465s
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'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0038cfc45846559d
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
FAILED
CptanPanic said:
So I tried that now, but I get
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.079s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.461s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.465s
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'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0038cfc45846559d
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
FAILED
Click to expand...
Click to collapse
Not good. I think you're emmc had failed. What happens if you try to lock the bootloader and then reboot. Is it still locked?
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Not good. I think you're emmc had failed. What happens if you try to lock the bootloader and then reboot. Is it still locked?
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So I lock bootloader, and reboot and it is unlocked again.
CptanPanic said:
So I lock bootloader, and reboot and it is unlocked again.
Click to expand...
Click to collapse
You can try just flashing the cache.img but I think you're going to have to rma it
Sent from my Nexus 5 using XDA Free mobile app
Related
Hi There.
I just got a brand new Nexus 4 today and the first thing I tried to do was to update to the 4.3 Android version. I downloaded the factory image from Android.com. When I tried to run the flash-all.sh script I got this error:
macyccam-jwr66v trant_macbook$ ./flash-all.sh
sending 'bootloader' (2201 KB)...
OKAY [ 0.139s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.142s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (54321 KB)...
OKAY [ 3.397s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 3.399s
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'
--------------------------------------------
Bootloader Version...: MAKOZ10o
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.48
Serial Number........: 027af952120bb5bf
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MAKOZ10o'.
Update requires 'MAKOZ20i'.
finished. total time: 0.012s
Click to expand...
Click to collapse
Is something wrong with my bootloader ?
xDer_ said:
Hi There.
I just got a brand new Nexus 4 today and the first thing I tried to do was to update to the 4.3 Android version. I downloaded the factory image from Android.com. When I tried to run the flash-all.sh script I got this error:
Is something wrong with my bootloader ?
Click to expand...
Click to collapse
Your bootloader seems like it's locked. You need to unlock it first with fastboot by running "fastboot oem unlock". Note that this will wipe all data on your device, which you probably don't mind since you just got the device.
hello all
My beloved Nexus recently crashed on me and it would boot past the "google" screen :crying:. I have done research and seen some suggestion to clear this is to flash stock image back onto the device. I have tried this via the nexus root toolkit and also via ADB. Both methods give me a signature verification failed error. can anyone please help me?
C:\Users\MA7424\Downloads\fastboot>fastboot -w update image-mantaray-jdq39.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB04MPXT
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4608 KB)...
OKAY [ 0.671s]
writing 'boot'...
OKAY [ 0.118s]
sending 'recovery' (5108 KB)...
OKAY [ 0.753s]
writing 'recovery'...
OKAY [ 0.122s]
sending 'system' (522703 KB)...
OKAY [ 75.752s]
writing 'system'...
FAILED (remote: signature verification failed!)
finished. total time: 81.264s
Glennfoot said:
hello all
My beloved Nexus recently crashed on me and it would boot past the "google" screen :crying:. I have done research and seen some suggestion to clear this is to flash stock image back onto the device. I have tried this via the nexus root toolkit and also via ADB. Both methods give me a signature verification failed error. can anyone please help me?
C:\Users\MA7424\Downloads\fastboot>fastboot -w update image-mantaray-jdq39.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB04MPXT
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4608 KB)...
OKAY [ 0.671s]
writing 'boot'...
OKAY [ 0.118s]
sending 'recovery' (5108 KB)...
OKAY [ 0.753s]
writing 'recovery'...
OKAY [ 0.122s]
sending 'system' (522703 KB)...
OKAY [ 75.752s]
writing 'system'...
FAILED (remote: signature verification failed!)
finished. total time: 81.264s
Click to expand...
Click to collapse
I had this issue one time and I solved it by flashing a different kernel. Can u still get into recovery mode (volume buttons and power at the same time)? How did u get into the bootloop in the first place because that could help solve the issue.
Sent from my Nexus 10 using xda app-developers app
yep i can get into TWRP - managed to side load slimbean rom, but i'm back to the bootlooping
Glennfoot said:
yep i can get into TWRP - managed to side load slimbean rom, but i'm back to the bootlooping
Click to expand...
Click to collapse
Did you try wiping everything first before flashing? If that doesn't work download ncry toolkit. I found that when the other root toolkit fails this one works and vice versa. I'm pretty sure you can solve the issue by just wiping and flashing new ROM. Also remember after first flashing it takes longer to turn on so wait a couple minutes to make sure. A also can you tell me what u did to get into the bootloop because it will be easier to find a solution?
Sent from my Nexus 10 using xda app-developers app
It started looping after I was watching netflix and it froze (no response to touch or physical buttons) put into recovery to be too reboot bit it simply went into bootloops. Wiped everything using twrp then reinstalled room but still loping. Wiped everything (including recovery) using fastboot command's and then attempted to load stock image but this failed. Perform oem lock and tried again. Performed oem unlock and reinstalled twrp, side loaded slim rom to sd card (as sd card had been wiped) flashed rom and gapps via twrp but back to bootloop.
Sent from my GT-N7105 using XDA Premium HD app
It's your fastboot image.. My fastboot images contain the System.sig whereas yours says it doesnt
Sent from my HTC One using Tapatalk
Do you have a link or can you post a copy of yours. Very appreciated if you could
Sent from my GT-N7105 using XDA Premium HD app
Glennfoot said:
Do you have a link or can you post a copy of yours. Very appreciated if you could
Sent from my GT-N7105 using XDA Premium HD app
Click to expand...
Click to collapse
Where did you get the stock image you're trying to install? Try downloading the factory image directly from Google. You can download either 4.2.2 (JDQ39) or 4.3 (JWR66Y).
https://developers.google.com/android/nexus/images
sharksfan7 said:
Where did you get the stock image you're trying to install? Try downloading the factory image directly from Google. You can download either 4.2.2 (JDQ39) or 4.3 (JWR66Y).
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Sadly that is where i got it from, tried both 4.2.2 and 4.3. I'm starting to think my nexus might be dead.
could my laptop be causing the problem?
Hi All,
I'm using Mac Terminal, have latest SDK, adb and fastboot installed. I have Nexus 7 (2012) Wifi - Nakasi
I followed the pinned post to upgrade my 4.3 (JWR66Y) to KitKat 4.4. I rebooted into fastboot and started ./flash-all.sh
Mid way through the process had stalled so I 'control C' out of the process.
$ ./flash-all.sh
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.993s]
finished. total time: 0.994s
erasing 'cache'...
OKAY [ 1.059s]
finished. total time: 1.059s
erasing 'recovery'...
OKAY [ 0.854s]
finished. total time: 0.855s
erasing 'system'...
OKAY [ 0.490s]
finished. total time: 0.490s
erasing 'userdata'...
OKAY [ 6.154s]
finished. total time: 6.154s
sending 'bootloader' (2100 KB)...
OKAY [ 0.302s]
writing 'bootloader'...
OKAY [ 9.666s]
finished. total time: 9.969s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
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........: 015d2d4226501005
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.024s]
sending 'boot' (4990 KB)...
OKAY [ 1.045s]
writing 'boot'...
OKAY [ 1.047s]
sending 'recovery' (5530 KB)...
OKAY [ 3.340s]
writing 'recovery'...
OKAY [ 1.381s]
sending 'system' (611878 KB)...
^C
Click to expand...
Click to collapse
I ran same process and it was hanging again at the same spot. I exited the same way. Now terminal cannot find device in adb devices. I can still boot into recovery mode.
$ ./adb devices
List of devices attached
Click to expand...
Click to collapse
$ ./flash-all.sh
< waiting for device >
Click to expand...
Click to collapse
I'm not sure what to do now!!! any help would be...helpful. Please.
You need to wait a but, because the system image us about 630MB, which may take round about two minutes to get transferred and flashed.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
You need to wait a but, because the system image us about 630MB, which may take round about two minutes to get transferred and flashed.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I waited 20 minutes the first time and 15 minutes the second time.
I tried flashing using different method from fastboot (http://forum.xda-developers.com/showthread.php?t=2010312). Problems happen when flashing system.img (~600MB).
Has anyone else found out the checksums aren't working? I get an error "E:signature verification failed" when using "flash-all.sh" from recovery mode (different method i've tried)
Note: no problems updating my nexus 4
Just wanted to update you on a solution if anyone has a similar problem.
I erased the system image through fastboot.
./fastboot erase system
Click to expand...
Click to collapse
Flashed the system image for old stock 4.3
./fastboot flash system system.img
Click to expand...
Click to collapse
Ran the flash-all script
./flash-all.sh
Click to expand...
Click to collapse
System was updated and worked! I back-dated to android 4.3, then did a second flash-all script to update to the current version of android 4.4. I believe that the original factory image for 4.4 was not working. The factory image was updated a day later - this is the file i used.
Thanks to everyone in xda. The many posts I read - even not directly related to my problem - provided a solution.
I hope my next post isn't so noob
whitext said:
I waited 20 minutes the first time and 15 minutes the second time.
I tried flashing using different method from fastboot (http://forum.xda-developers.com/showthread.php?t=2010312). Problems happen when flashing system.img (~600MB).
Has anyone else found out the checksums aren't working? I get an error "E:signature verification failed" when using "flash-all.sh" from recovery mode (different method i've tried)
Note: no problems updating my nexus 4
Click to expand...
Click to collapse
Well,I got the similar problem the other day on my Nakasig when I was flashing factory images through Fastboot.
Not only did I try the "flash-all.bat" command, but I also manually inputted each command line one after another.
However, I still encountered the same issue and waited for more 30 minutes during the "sending system" process.
Even worse was that I unplugged my N7 and tried to boot it,which led me to be stuck with the Google logo.:crying:
After removing the battery and booting it into Fastboot again,this time I decided to use Wug's toolkit to flash it.:good:
And thankfully,it worked and I can grab the delicious Kitkat now.
BTW, my N7 still failed to pass Hashcheck while using Wug's automatic method, therefore I just downloaded the Factory images and used Wug's tool to navigate to the .tgz file and then flash it.It spent me around 2 minutes to complete the "sending system" process this time.
I i started to "re-update" my phone because of issues of OTA. I did everuthing fine but now after i made the all the "fastboot erases" i cant instal the android.
I was with stock rom unrooted, so following a video i went to bootloader like i saw , i connected the phone on my pc, and double-click on "flash-all" buit i'm getting a problem with images of 4.4 and 4.3
...
FAILED (remote: Already Unlocked)
finished. total time: 0.006s
erasing 'boot'...
OKAY [ 0.006s]
finished. total time: 0.008s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.021s]
finished. total time: 0.022s
erasing 'recovery'...
OKAY [ 0.005s]
finished. total time: 0.006s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.031s]
finished. total time: 0.033s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.191s]
finished. total time: 0.193s
sending 'bootloader' (2100 KB)...
OKAY [ 0.073s]
writing 'bootloader'...
FAILED (remote: invalid bootloader image
)
finished. total time: 0.086s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 01cd03df4b0e7962
--------------------------------------------
checking product...
FAILED
Device product is 'mako'.
Update requires 'grouper'.
finished. total time: 0.030s
Press any key to exit...
my phone doesnt even turn on anymore, what should i do
alan966 said:
Device product is 'mako'.
Update requires 'grouper'.
Click to expand...
Click to collapse
Well, that seems to be your problem. Looks like you flashed the nexus 7 images on your nexus 4...not a good thing.
I would first try downloading the CORRECT images and flashing those.
Chromium_ said:
Well, that seems to be your problem. Looks like you flashed the nexus 7 images on your nexus 4...not a good thing.
I would first try downloading the CORRECT images and flashing those.
Click to expand...
Click to collapse
wtf ? i downloaded this image from the google and only now i saw that everytime i clicked on the nexus 4 images it brings me to nexus 7 images
I'll try again with the correct images and report
UPDATE: i did it, kit kat is running in my phone but now google services does not work anymore with my wifi only with my 3g, cant download any app, acess any kind of google app like youtube, gmail, maps...
So I began the process being able to see the device via terminal in linux. Downloaded the firmware and proceeded to begin the flash process.
Well.... I think it is safe to say it hasnt gone as well as I had hoped.
...
(bootloader) Bootloader is already unlocked
OKAY \[ 0.015s\]
finished. total time: 0.015s
erasing 'boot'...
OKAY \[ 0.017s\]
finished. total time: 0.017s
\*\*\*\*\*\*\*\* Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY \[ 0.084s\]
finished. total time: 0.084s
erasing 'recovery'...
OKAY \[ 0.017s\]
finished. total time: 0.017s
\*\*\*\*\*\*\*\* Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY \[ 0.109s\]
finished. total time: 0.109s
\*\*\*\*\*\*\*\* Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY \[ 4.950s\]
finished. total time: 4.950s
target didn't report max-download-size
sending 'bootloader' (2100 KB)...
OKAY \[ 0.265s\]
writing 'bootloader'...
OKAY \[ 1.207s\]
finished. total time: 1.472s
rebooting into bootloader...
OKAY \[ 0.015s\]
finished. total time: 0.065s
target didn't report max-download-size
sending 'radio' (16384 KB)...
OKAY \[ 1.965s\]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 1.986s
rebooting into bootloader...
OKAY \[ 0.015s\]
finished. total time: 0.065s
extracting android-info.txt (0 MB)...
extracting boot.img (4 MB)...
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (5 MB)...
archive does not contain 'recovery.sig'
extracting system.img (629 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (Success))
\--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Success))
finished. total time: 0.000s
I had gotten to the point where all I could do was restart bootloader in the download mode.. on the device as it no longer had anything to boot in to.
The thing is now I get no life from the tablet whatsover! So before it was a flashing of the image issue and now I have no life in the tablet at all
Have I rendered this tablet as more of a paperweight as before?
Sent from my SM-N960F using Tapatalk
Boot into bootloader and try reflashing
Chinmay2006 said:
Boot into bootloader and try reflashing
Click to expand...
Click to collapse
Thats the problem now. There is no life from it whatsoever
Sent from my SM-N960F using Tapatalk
jr866gooner said:
Thats the problem now. There is no life from it whatsoever
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
Is it charging
Chinmay2006 said:
Is it charging
Click to expand...
Click to collapse
Sadly no indication on screen however can feel its warm when charging.
I have taken off the back to disconnect and reconnect the battery but that hasn't worked.
Sent from my SM-N960F using Tapatalk
@jr866gooner what device do you have and which firmware did you try to flash?
If I remember well, there were some Google firmwares which contained a defective bootloader ...
AndDiSa said:
@jr866gooner what device do you have and which firmware did you try to flash?
If I remember well, there were some Google firmwares which contained a defective bootloader ...
Click to expand...
Click to collapse
Hey! Sorry I thought I had mentioned it.. I have a Nexus 7 2012 (Grouper) model. The Google firmware I tried to flash was the 4.4.4 version labled nakasi-ktu84p.
I was looking to downgrade to get some performance back as it couldnt even cope with the app drawer being opened lol
Hmm ... looking here there is a chance that you really took one of the defective firmware versions.
If this is the case then you probably would like to have a look here or at this Github Project
AndDiSa said:
Hmm ... looking here there is a chance that you really took one of the defective firmware versions.
If this is the case then you probably would like to have a look here or at this Github Project
Click to expand...
Click to collapse
Thanks for the info. I have and intend to leave the device with its battery disconnected overnight but looking at this its a goner. Thanks Google!! I wish I'd noticed the bootloader information sooner! I sadly don't have another Nexus to massage it back to life.
I kind of wanted just a mess about tablet so I might either grab one second hand but get the 2013 model or do an insurance claim query. Not sure if that would be covered but it cant hurt to speak to someone for advice.
Sent from my SM-N960F using Tapatalk
@jr866gooner well, if you get your SBK @enderzip for sure will provide you with the blob.bin needed to unbrick your device.