[Q] nexus not accepting stock image - signature verification fail - Nexus 10 Q&A, Help & Troubleshooting

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?

Related

[Q] Can't restore nexus 7

Hi all,
Since I'm new to this forum I was not allowed to post on the developers threat, so I made a new one hoping some one could help me.
My new nexus 7 arived a few days ago and I had rooted it using the Nexus root Toolkit 1.5.4. (android 4.1.2)
Than I installed a new custom rom (PARANOIDANDROID 2.2) on the nexus but I did not like that rom so I wanted to restore it back to the stock rom.
When I tried that using the Nexus root toolkit 1.5.4 I kept saying FAILED.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2092 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 0.098s
rebooting into bootloader...
FAILED (remote: (Nv3pBadReceiveLength))
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...: 3.41
Baseband Version.....: N/A
Serial Number........: Not relevant I guess...
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4896 KB)...
OKAY [ 0.585s]
writing 'boot'...
OKAY [ 1.763s]
sending 'recovery' (5240 KB)...
OKAY [ 0.628s]
writing 'recovery'...
OKAY [ 1.342s]
sending 'system' (446268 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 6.425s
I think it's going wrong with the first step (Sending 'bootloader').
I'm restoring to android 4.1.2 because that one is using bootloader 3.41 and if I try to restore to android 4.1.1 I get some other error messages with the bootloader.
This is on a windows 7 x64 bit machine, I tried 2 different cables, the stock cable and the cable from my nexus s3 with both didn't fix anything and I tried every usb port (for some reason only usb3.0 ports work with my computer...)
I even tried restoring to stock + unroot on 2 other computers (win 7 x64 and win 2008 r2 x64) and both are stuck at: sending 'bootloader' (2092 KB)...
So basicly I do get in to fastboot, but I can't get any further than that, Recovery mode gives my an open android with a "!" in its "belly" and the option "Start" get me stuck at the bootlogo from the custom rom (PARANOIDANDROID 2.2).
I hope you guys can help me with this anoying problem.
Btw. I'm sorry for my bad english, this isn't my motherlanguage and it's late.
EDIT: the tablet is stuck on "google" with an unlocked lock logo when I try to turn it on.
EDIT2: On windows 8 x64 it is saying too many links.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2092 KB)...
FAILED (data transfer failure (Too many links))
fisnished. total time: 0.124s
rebooting into bootloader...
FAILED (coomand write failed (Unknown error))
finished. total time: 0.639s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.703s
fixed!
kanuva said:
Hi all,
Since I'm new to this forum I was not allowed to post on the developers threat, so I made a new one hoping some one could help me.
My new nexus 7 arived a few days ago and I had rooted it using the Nexus root Toolkit 1.5.4. (android 4.1.2)
Than I installed a new custom rom (PARANOIDANDROID 2.2) on the nexus but I did not like that rom so I wanted to restore it back to the stock rom.
When I tried that using the Nexus root toolkit 1.5.4 I kept saying FAILED.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2092 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 0.098s
rebooting into bootloader...
FAILED (remote: (Nv3pBadReceiveLength))
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...: 3.41
Baseband Version.....: N/A
Serial Number........: Not relevant I guess...
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4896 KB)...
OKAY [ 0.585s]
writing 'boot'...
OKAY [ 1.763s]
sending 'recovery' (5240 KB)...
OKAY [ 0.628s]
writing 'recovery'...
OKAY [ 1.342s]
sending 'system' (446268 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 6.425s
I think it's going wrong with the first step (Sending 'bootloader').
I'm restoring to android 4.1.2 because that one is using bootloader 3.41 and if I try to restore to android 4.1.1 I get some other error messages with the bootloader.
This is on a windows 7 x64 bit machine, I tried 2 different cables, the stock cable and the cable from my nexus s3 with both didn't fix anything and I tried every usb port (for some reason only usb3.0 ports work with my computer...)
I even tried restoring to stock + unroot on 2 other computers (win 7 x64 and win 2008 r2 x64) and both are stuck at: sending 'bootloader' (2092 KB)...
So basicly I do get in to fastboot, but I can't get any further than that, Recovery mode gives my an open android with a "!" in its "belly" and the option "Start" get me stuck at the bootlogo from the custom rom (PARANOIDANDROID 2.2).
I hope you guys can help me with this anoying problem.
Btw. I'm sorry for my bad english, this isn't my motherlanguage and it's late.
EDIT: the tablet is stuck on "google" with an unlocked lock logo when I try to turn it on.
EDIT2: On windows 8 x64 it is saying too many links.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2092 KB)...
FAILED (data transfer failure (Too many links))
fisnished. total time: 0.124s
rebooting into bootloader...
FAILED (coomand write failed (Unknown error))
finished. total time: 0.639s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.703s
Click to expand...
Click to collapse
I just kept trying and it fixed itself, eventually I let the battery die than I charged it for 2 hours and I tried it again on my windows 7 machine wich gave this error message: FAILED (data transfer failure (Too many open files in system)).
I'm getting the same "Too many open files in system" error
kmad86 said:
I'm getting the same "Too many open files in system" error
Click to expand...
Click to collapse
I'm getting similar errors
well i fixed this by putting the usb cable into a usb 2.0 port instead of the 3.0 one.
So try another usb port if you still have problems.
Same here. Fixed it afterall!
Was about to give up on Nexus 7 2012 due to write failed messages when flashing the larger files like system.img and complete roms including factory roms 4.4.4 to 5.1.1. (upon booting stuck on animated google logo)
I did notice the error messages were different in output as was the time at which they apeared after pressing the enter(return) key. Another indication may have been the slowing down in responseness of the fastboot commands (erase,format,reboot-bootloader etc).
The less obvious solution, which makes no sense at all to me, was to switch USB ports on my MAC 27 (late 2013) . I ended up with sucesfull flashing using the last USB port on the right. That is on the right when sitting in front of it while the ports are on the back....
To sum it up: Not all USB ports are the same afterall? Wether 2.0 or 3.0 or voltages i have no idea. Suppose same may be true for PC's of any brand.
Don't try giving up.
Same here. USB 2.0 FTW!

[Q] Failed KitKat 4.4 Fastboot

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.

[Q] Stuck on boot animation stock and custom roms

Hi all, first off, yes I have read quite a bit and I am completely stumped on this one.
A buddy from work dropped off his Nexus 4 and asked about the "bootloop" it is stuck in. Looking at it, this is not a boot loop as far as I can tell. He said he used the http://www.wugfresh.com/nrt/ to do a root, but it apparently went wrong (he said it reported successful completion).
What I have done thus far:
Download Google stock rom and flashed that following their instructions in the "flash-all.sh" file for Kit-Kat. Tried to go into recovery, but the recovery just gives the android with the red triangle above it and hangs. On boot the screen shows the "Google" logo with the unlocked symbol and then shows the kit-kat boot animation but just sits there and never finishes. I gave it about 30 minutes but no luck.
I can get into bootloader and then flash a recovery (CWM for Mako), which then allows me to get into CWM and either flash a custom ROM (tried latest PA beta) with the same hang on boot.
Tried to custom erase system, boot, recovery with the instructions below:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-clockwork-6.0.4.7-mako.img
boot to recovery
set up for sideload in CWM
adb sideload pa_mako-4.1-BETA2-20140310.zip
reboot
Same result, just hangs on reboot with animation for boot.
I tried flashing the radio and bootloader back to 4.3 and then flashing the stock rom for the Google ROM occam-jwr66y-factory-74b1deab.tgz which is where I am at now with it just sitting at animation if the X lighting up.
I just noticed that when I plug it in to my workstation it recognizes the device sort of and shows that it is mountable, but then just hangs and never loads the directory structure like normal.
Another thing to note, when I mount /system and /data in CWM and "adb shell" into the phone, the /sdcard/0 location shows empty, which as far as I know this should be populated with the usual sdcard user directories, maybe??
Any help would be appreciated. I noticed that if I hold both the volume up and volume down buttons it says it is in "Download" mode, didn't know that was a thing outside of Samsung devices.
Ouput from flashing with Google stock 4.4.2 ROM:
sudo ./flash-all.sh
[sudo] password for jscott:
sending 'bootloader' (2203 KB)...
OKAY [ 0.089s]
writing 'bootloader'...
OKAY [ 0.311s]
finished. total time: 0.401s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.790s]
writing 'radio'...
OKAY [ 2.541s]
finished. total time: 4.332s
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........: 0221a297d9d67206
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.253s]
writing 'boot'...
OKAY [ 0.356s]
sending 'recovery' (6888 KB)...
OKAY [ 0.287s]
writing 'recovery'...
OKAY [ 0.398s]
erasing 'system'...
OKAY [ 0.579s]
sending 'system' (713960 KB)...
OKAY [ 26.844s]
writing 'system'...
OKAY [ 40.883s]
rebooting...
finished. total time: 69.615s
Recovery was broken again.
Had to flash recovery again to get in but I can "adb shell" the phone no problems.
If more information is needed or someone has a sure fire way to fix this same problem please hit me up, but at this point I am at a loss.
Just found out that the phone may have died when the "wugfresh" script was running, but he said that it died afterwards, since I wasn't there I don't know for sure how this all played out.
Oops, I just posted the same problem a few minutes ago. In my defense to the moderators, your thread wasn't posted when I started writing mine.
Anyhow, have you tried flashing the 4.2.2 factory image? That is the only one I manage to boot, but my IMEI and network are gone...
MtG92 said:
Oops, I just posted the same problem a few minutes ago. In my defense to the moderators, your thread wasn't posted when I started writing mine.
Anyhow, have you tried flashing the 4.2.2 factory image? That is the only one I manage to boot, but my IMEI and network are gone...
Click to expand...
Click to collapse
Same thing on my side with the 4.2.2 ROM. Loads fine, but no IMEI or anything like that. Not sure what the deal is with it.
Allowed OTA update and now I get the android bot with the red triangle when trying to go into recovery, but it says "no command" under it. On boot the device just hangs at "starting apps." and doesn't move past that.
Sideloaded PA 3.99 mako for the phone and it just hangs on boot animation as it has done previously before successfully flashing the 4.2 factory image. Not sure what the deal is but a solution for this would be awesome as I am totally stumped.
I have been dealing with this for a few months, and what I have done to get it to work is let it sit for a few hours. Then give it a shot. About half the time my phone boots up. Once it's booted up everything works, but if I need to reboot for any reason your screwed for a few hours.
It started happening for me once the 4.4 update rolled out, and ever since it has been doing this. I asked on here a few time and got no responses.
Sent from my Nexus 4 using Tapatalk
NeCr0mStR said:
Same thing on my side with the 4.2.2 ROM. Loads fine, but no IMEI or anything like that. Not sure what the deal is with it.
Allowed OTA update and now I get the android bot with the red triangle when trying to go into recovery, but it says "no command" under it. On boot the device just hangs at "starting apps." and doesn't move past that.
Sideloaded PA 3.99 mako for the phone and it just hangs on boot animation as it has done previously before successfully flashing the 4.2 factory image. Not sure what the deal is but a solution for this would be awesome as I am totally stumped.
Click to expand...
Click to collapse
I met the same problem. My nexus 4 met this problem about 4 or 5 times. at first time, I tried restarting the phone and sometimes it might boot successfully, then everything works fine. Second time the reboot doesn't work any more, but flash stock with the newest factory ROM works fine(4.3 at that time), at this time I backup all my data. After I met this more, I found this problem arose only when the phone automatically shutting down because of the dead battery. Yesterday I met this problem again because of the dead battery, and at this time only reboot the phone with 4.2.0. I tried all other factory stocks from 4.2.0 to 4.4.2. Hope you can solve this early. And ask me any information you need.
NeCr0mStR said:
Hi all, first off, yes I have read quite a bit and I am completely stumped on this one.
A buddy from work dropped off his Nexus 4 and asked about the "bootloop" it is stuck in. Looking at it, this is not a boot loop as far as I can tell. He said he used the http://www.wugfresh.com/nrt/ to do a root, but it apparently went wrong (he said it reported successful completion).
What I have done thus far:
Download Google stock rom and flashed that following their instructions in the "flash-all.sh" file for Kit-Kat. Tried to go into recovery, but the recovery just gives the android with the red triangle above it and hangs. On boot the screen shows the "Google" logo with the unlocked symbol and then shows the kit-kat boot animation but just sits there and never finishes. I gave it about 30 minutes but no luck.
I can get into bootloader and then flash a recovery (CWM for Mako), which then allows me to get into CWM and either flash a custom ROM (tried latest PA beta) with the same hang on boot.
Tried to custom erase system, boot, recovery with the instructions below:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-clockwork-6.0.4.7-mako.img
boot to recovery
set up for sideload in CWM
adb sideload pa_mako-4.1-BETA2-20140310.zip
reboot
Same result, just hangs on reboot with animation for boot.
I tried flashing the radio and bootloader back to 4.3 and then flashing the stock rom for the Google ROM occam-jwr66y-factory-74b1deab.tgz which is where I am at now with it just sitting at animation if the X lighting up.
I just noticed that when I plug it in to my workstation it recognizes the device sort of and shows that it is mountable, but then just hangs and never loads the directory structure like normal.
Another thing to note, when I mount /system and /data in CWM and "adb shell" into the phone, the /sdcard/0 location shows empty, which as far as I know this should be populated with the usual sdcard user directories, maybe??
Any help would be appreciated. I noticed that if I hold both the volume up and volume down buttons it says it is in "Download" mode, didn't know that was a thing outside of Samsung devices.
Ouput from flashing with Google stock 4.4.2 ROM:
sudo ./flash-all.sh
[sudo] password for jscott:
sending 'bootloader' (2203 KB)...
OKAY [ 0.089s]
writing 'bootloader'...
OKAY [ 0.311s]
finished. total time: 0.401s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.790s]
writing 'radio'...
OKAY [ 2.541s]
finished. total time: 4.332s
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........: 0221a297d9d67206
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.253s]
writing 'boot'...
OKAY [ 0.356s]
sending 'recovery' (6888 KB)...
OKAY [ 0.287s]
writing 'recovery'...
OKAY [ 0.398s]
erasing 'system'...
OKAY [ 0.579s]
sending 'system' (713960 KB)...
OKAY [ 26.844s]
writing 'system'...
OKAY [ 40.883s]
rebooting...
finished. total time: 69.615s
Recovery was broken again.
Had to flash recovery again to get in but I can "adb shell" the phone no problems.
If more information is needed or someone has a sure fire way to fix this same problem please hit me up, but at this point I am at a loss.
Just found out that the phone may have died when the "wugfresh" script was running, but he said that it died afterwards, since I wasn't there I don't know for sure how this all played out.
Click to expand...
Click to collapse
You have to keep flashing the Stock ROM...that's what saved me
Sent from my Moto G
GameAware said:
You have to keep flashing the Stock ROM...that's what saved me
Sent from my Moto G
Click to expand...
Click to collapse
So you had the same problem and managed to solve it by flashing the stock rom multiple times? How many times did you have to do it, and have you had that problem since?
MtG92 said:
So you had the same problem and managed to solve it by flashing the stock rom multiple times? How many times did you have to do it, and have you had that problem since?
Click to expand...
Click to collapse
Yes I had the same problem and flashed the ROM the first time, but still nothing. I then flashed it again and it booted up as normal. No problems since.
Sent from my Moto G

[Q] Help, Phone just bricked itself.

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

Stuck in a bootloop from restore

I've restored a back up through TWRP and now my phone is stuck in a bootloop. I can't get in TWRP either, as that bootloops too.
I think the issue is that I've restored a vendor image. How can I fix this if I can't get into recovery?
Can someone please help me here?
I would go into Heisenberg's guide which is stickied in the general section. Flash stock images and TWRP via fast boot. Read the guide in its entirety.
Random Barnics said:
I've restored a back up through TWRP and now my phone is stuck in a bootloop. I can't get in TWRP either, as that bootloops too.
I think the issue is that I've restored a vendor image. How can I fix this if I can't get into recovery?
Can someone please help me here?
Click to expand...
Click to collapse
Your phone shouldn't loop from restoring a vendor image, as long as it's the right vendor image that was backed up with the ROM. Exactly what did you backup/restore? You haven't really given enough information here.
I was running Dirty Unicorns 6.0.1. When I backed it up, I checked all of the extra parts to back up. I restored everything.
Random Barnics said:
I was running Dirty Unicorns 6.0.1. When I backed it up, I checked all of the extra parts to back up. I restored everything.
Click to expand...
Click to collapse
When I asked exactly what you backed up, I did mean exactly. When you say you checked all of the extra parts, what do you mean? That isn't very specific. Do you mean you checked every box? If so, you don't need to do that, you only need to select system, data, boot, and vendor. So restoring your backup and only selecting to restore those.
Heisenberg said:
When I asked exactly what you backed up, I did mean exactly. When you say you checked all of the extra parts, what do you mean? That isn't very specific. Do you mean you checked every box? If so, you don't need to do that, you only need to select system, data, boot, and vendor. So restoring your backup and only selecting to restore those.
Click to expand...
Click to collapse
Yeah. I checked every box, and restored everything I backed up. I think we're on the same page now
Random Barnics said:
Yeah. I checked every box, and restored everything I backed up. I think we're on the same page now
Click to expand...
Click to collapse
Alright, do what I said and only restore system, data, boot, and vendor.
Heisenberg said:
Alright, do what I said and only restore system, data, boot, and vendor.
Click to expand...
Click to collapse
As noted in the initial post, I can't do anything as neither the rom nor the recovery load,
I went with the dude's advice about flashing the rom and recovery through fastboot, and they're not working.
This is the terminal output I get when trying to flash the recovery.
[email protected]-3-11:~/Android/Sdk/platform-tools$ fastboot flash recovery twrp-3.0.0-1-angler.imgtarget reported max download size of 494927872 bytes
sending 'recovery' (16904 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.246s]
finished. total time: 0.756s
It still freezes and doesn't load when I try and access it.
The following results are what I get when trying to flash a rom in fastboot
[email protected]-3-11:~/Android/Sdk/platform-tools$ fastboot flash zip DU_angler_6.0.1_20160301-2335.v10.0-OFFICIAL.zip
target reported max download size of 494927872 bytes
sending 'zip' (432013 KB)...
OKAY [ 11.485s]
writing 'zip'...
FAILED (remote: Permission denied!)
finished. total time: 11.491s
Don't flash a ROM flash Stock Images and go from there.
dratsablive said:
Don't flash a ROM flash Stock Images and go from there.
Click to expand...
Click to collapse
Ok. Why though? Not doubting your advice. Just wondering.
Random Barnics said:
Ok. Why though? Not doubting your advice. Just wondering.
Click to expand...
Click to collapse
Because you want to get your phone to boot normally. Once you can boot to stock, you can then flash TWRP, then custom rom and then only restore the /data portion of your backup.
My mistake, I missed the part where your recovery won't boot. Flash the factory images as the other fella said, that'll get your phone booting at least. Don't restore the data portion of your backup over the stock ROM though, that'll cause major problems.
PS. You can't flash ROM zips with fastboot.
Ok, cheers guys.
I've tried to flash the stock rom. It's not working. Here's the terminal results:
[email protected]-3-11:~/Android/Sdk/platform-tools$ ./flash-all.sh
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
OKAY [ 0.207s]
finished. total time: 0.327s
rebooting into bootloader...
OKAY [ 0.080s]
finished. total time: 0.080s
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.265s]
writing 'radio'...
OKAY [ 2.174s]
finished. total time: 3.439s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: angler-03.51
Baseband Version.....: angler-03.61
Serial Number........: CVH7N15A25000202
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.021s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (12045 KB)...
OKAY [ 0.319s]
writing 'boot'...
OKAY [ 0.181s]
sending 'recovery' (12977 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.194s]
erasing 'system'...
OKAY [ 0.046s]
sending 'system' (1966888 KB)...
FAILED (remote: data too large)
finished. total time: 1.232s
[email protected]-3-11:~/Android/Sdk/platform-tools$ reboot fastboot
reboot: Need to be root
[email protected]-3-11:~/Android/Sdk/platform-tools$ ./flash-all.sh
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.117s]
writing 'bootloader'...
OKAY [ 0.208s]
finished. total time: 0.325s
rebooting into bootloader...
OKAY [ 0.080s]
finished. total time: 0.080s
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.328s]
writing 'radio'...
OKAY [ 2.174s]
finished. total time: 3.502s
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.013s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: angler-03.51
Baseband Version.....: angler-03.61
Serial Number........: CVH7N15A25000202
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.021s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (12045 KB)...
OKAY [ 1.109s]
writing 'boot'...
OKAY [ 0.190s]
sending 'recovery' (12977 KB)...
OKAY [ 0.829s]
writing 'recovery'...
OKAY [ 0.194s]
erasing 'system'...
OKAY [ 0.312s]
sending 'system' (1966888 KB)...
FAILED (remote: data too large)
finished. total time: 2.823s
Random Barnics said:
Ok, cheers guys.
I've tried to flash the stock rom. It's not working. Here's the terminal results:
*snipped
Click to expand...
Click to collapse
Instead of using the flash-all script flash the images manually. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Instead of using the flash-all script flash the images manually. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks.
I'll try again when I get up, as it's almost 2.30am here.
Heisenberg said:
Instead of using the flash-all script flash the images manually. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks for your help Heisenberg. That last piece of advice got everything working perfectly
Random Barnics said:
Thanks for your help Heisenberg. That last piece of advice got everything working perfectly
Click to expand...
Click to collapse
Excellent, great to know
He probably restored boot system system image vendor vendor image data efs recovery......
dontbeweakvato said:
He probably restored boot system system image vendor vendor image data efs recovery......
Click to expand...
Click to collapse
Yeah we already established that.

Categories

Resources