Database Users

Factory Restore - Archive does not contain... Help.

Hey guys. My brother got himself a Nexus 7 which is his first Android, and he was playing with some tweaks or mods or something and tried flashing via recovery and has messed something up. I have tried using the Toolkits as well as doing it manually with fastboot. I am able to flash a recovery and use that, but lose it after boot (the permanent option doesn't seem to stick). But, when I try to do a factory restore with the google image, it doesnt matter if i'm doig it manual or with the toolkit, the all respond with a "archive does not contain... " boot.sig, recovery.sig, or system.sig. Here is my output:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-
jro03d\image-nakasi-jro03d.zip"
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.836s
Even if I do them manually, one at a time:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe flash boot nakasi-jro03d\image-na
kasi-jro03d\boot.img
sending 'boot' (4890 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.858s
I have also tried pushing a stock rom .zip to the /sdcard and it doesnt seem to make it either.
Feels like internal memory is corrupt. Any thoughts or ideas I can try? Also... should any custom recovery allow adb access? TWRP or CWM Touch don't seem to work.

Update... Just rebooted into bootloader and tried:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-jro03d-factory-e102ba72\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: 015d256898080e19
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4890 KB)...
OKAY [ 0.608s]
writing 'boot'...
OKAY [ 0.390s]
sending 'recovery' (5234 KB)...
OKAY [ 0.655s]
writing 'recovery'...
OKAY [ 0.343s]
sending 'system' (438656 KB)...
FAILED (unknown status code)
finished. total time: 3.292s
That's the most progress I can get. System seems to fail though. Tried multiple times.

Another note... If I boot into Recovery and adb push a file to the /sdcard, the transfer looks like it completes, but when I go to flash zip in recovery it gives me an E: Can't mount /sdcard/. Same thing if I go to the mounts and storage option and try to mount /sdcard.
Any ideas guys? Never seen this before.

Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.

Mr. Monkey said:
Update... Just rebooted into bootloader and tried:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-jro03d-factory-e102ba72\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: 015d256898080e19
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4890 KB)...
OKAY [ 0.608s]
writing 'boot'...
OKAY [ 0.390s]
sending 'recovery' (5234 KB)...
OKAY [ 0.655s]
writing 'recovery'...
OKAY [ 0.343s]
sending 'system' (438656 KB)...
FAILED (unknown status code)
finished. total time: 3.292s
That's the most progress I can get. System seems to fail though. Tried multiple times.
Click to expand...
Click to collapse
The "archive does not contain *.sig" messages are normal. The FAILED messages on sending the system image is disconcerting. Use the platform tools from Google which includes fastboot. http://dl-ssl.google.com/android/repository/platform-tools_r16-windows.zip
There is a .bat file in the factory image archive that you can run to return to stock. If you don't want to run that, at least open it up and manually run the commands in sequence.

comminus said:
The "archive does not contain *.sig" messages are normal. The FAILED messages on sending the system image is disconcerting. Use the platform tools from Google which includes fastboot. http://dl-ssl.google.com/android/repository/platform-tools_r16-windows.zip
There is a .bat file in the factory image archive that you can run to return to stock. If you don't want to run that, at least open it up and manually run the commands in sequence.
Click to expand...
Click to collapse
I think that's the same thing I've been trying. I did download Google's platform-tools and try with that and still got the same error. Seems like I can't write to /system. Can't even erase it:
c:\android\platform-tools>fastboot.exe flash system C:\android\nakasi-jro03d\ima
ge-nakasi-jro03d\system.img
sending 'system' (438656 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.094s
c:\android\platform-tools>fastboot.exe erase system
erasing 'system'...
FAILED (command write failed (Unknown error))
finished. total time: 0.733s
c:\android\platform-tools>fastboot.exe format system
formatting 'system' partition...
FAILED (command write failed (Unknown error))
FAILED (command write failed (Unknown error))
finished. total time: 0.889s
What are my options? Flash stock recovery, re-lock bootloader and send it in for an RMA? Anyone else know what to try?

Mr. Monkey said:
I think that's the same thing I've been trying. I did download Google's platform-tools and try with that and still got the same error. Seems like I can't write to /system. Can't even erase it:
c:\android\platform-tools>fastboot.exe flash system C:\android\nakasi-jro03d\ima
ge-nakasi-jro03d\system.img
sending 'system' (438656 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.094s
c:\android\platform-tools>fastboot.exe erase system
erasing 'system'...
FAILED (command write failed (Unknown error))
finished. total time: 0.733s
c:\android\platform-tools>fastboot.exe format system
formatting 'system' partition...
FAILED (command write failed (Unknown error))
FAILED (command write failed (Unknown error))
finished. total time: 0.889s
What are my options? Flash stock recovery, re-lock bootloader and send it in for an RMA? Anyone else know what to try?
Click to expand...
Click to collapse
Two more thoughts - 1. try updating drivers. 2. verify the sha1 hash of the factory image

Did you try switching to a different usb port? Just a thought is all.

Wow. Can't thank you guys enough. Thought this was toast. I ended up trying all of the above, haha. Even though I had done it several times. I tried multiple computers, multiple factory images, multiple programs, multiple USB ports. But somehow, maybe your encouragement, something helped. I'll watch it and make sure nothing seems fishy, because I don't know how in the world that worked.... but it did. Thank you very much.

manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Hi there
I was having the same problem but when I try to flash the system.img (or the 'image-nasaki-jop40d.zip file too for that matter) I get the following error:
"error: cannot load 'system.img': Not enough space
I have done ALL the steps found in this guide without any issues until I get to that part
Help please my wife just gave me this N7 for christmas and I can't believe I may have just bricked it!!

My solution
I understand this is an old thread but I came across it when I was having the same issues earlier today.
Oddly, using the USB cable that came with the N7 seemed to fix the multiple "FAILED" I was getting.
Using my Samsung USB cable seemed to cause the issues.
Hope this can be a solution to others that may come by this thread by googling the issue.

manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
This one helped me!:good::good::good:
Thanks a lot.

manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Works, thanks. :good:

Unlock bootloader
Mr. Monkey said:
Hey guys. My brother got himself a Nexus 7 which is his first Android, and he was playing with some tweaks or mods or something and tried flashing via recovery and has messed something up. I have tried using the Toolkits as well as doing it manually with fastboot. I am able to flash a recovery and use that, but lose it after boot (the permanent option doesn't seem to stick). But, when I try to do a factory restore with the google image, it doesnt matter if i'm doig it manual or with the toolkit, the all respond with a "archive does not contain... " boot.sig, recovery.sig, or system.sig. Here is my output:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-
jro03d\image-nakasi-jro03d.zip"
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.836s
Even if I do them manually, one at a time:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe flash boot nakasi-jro03d\image-na
kasi-jro03d\boot.img
sending 'boot' (4890 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.858s
I have also tried pushing a stock rom .zip to the /sdcard and it doesnt seem to make it either.
Feels like internal memory is corrupt. Any thoughts or ideas I can try? Also... should any custom recovery allow adb access? TWRP or CWM Touch don't seem to work.
Click to expand...
Click to collapse
You need the bootloader to be unlock. First run the command " fastboot oem unlock " . It works flawlessly after that! Awesome!

nexus 7 (mobile)
shap4th said:
You need the bootloader to be unlock. First run the command " fastboot oem unlock " . It works flawlessly after that! Awesome!
Click to expand...
Click to collapse
Hi!
I bought a second hand nexus 7 rooted. I had a problem with updating os via wifi because it doesn't update. some kind a problem. I tried to do a hard reset hoping I could just restore the device manually but I messed up so I am now stuck with just a google logo and can only access bootloader with start, bootloader, restore and power off option. I don't know what to do. please help me. I am not a tech person but if you can give me a specific instructions, I know i can manage. i saw a lot off post here that they were able to restore their device so I have faith in this site and the members are highly recommended.
thank you in advance

manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Thanks man! This works for me..

manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Thanks. This one works for my friend.
Same case, solved on spanish forum.
/showthread.php?t=748207 on htcmania(dot)com
*Note: damn spam filter

Try this website. If you have any question ask me.
You will need to install files one by one.
SImply open flash bat file see what they are doing. and do same but one by one.
Flash bootloader and radio (radio does not appear on all devices, if it's not in your tgz, you don't need it)
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
NEXUS 9 ONLY - flash this as well
fastboot flash vendor vendor.img
If you want to wipe cache and user data (full wipe), flash these
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Finally, just reboot your device, and Android should start up.
fastboot reboot

Similar issue, please help
I'm using ubuntu 14.10 LTS. I had the same issue arise so i listened reextracted (even though boot.img, system.img & recovery.img were within .zip but im still getting "critical error: extent_create_backing: calloc: Cannot allocate memory
Mmap:invalid argument
Cannot generate image
FAILED()"
Anyone has a suggestion?
---------- Post added at 11:49 PM ---------- Previous post was at 11:18 PM ----------
So as my previous and maybe above msg said i was just about to attempt adb sideload to manually update to lollipop... From the bootloader i entered recovery... My nexus 4 shut down & got stuck @ wild new boot animation for lollipop. I waited 5 minutes while the fantastic yellow, red, blue & green orbs whizzed around, shut my 4 down & now "Android is upgrading... Optimizing app x of 68." How wild is this... But i still have to lock bootloader. Hopefully it doesnt screw anything up... I'll report back asap
---------- Post added 24th November 2014 at 12:19 AM ---------- Previous post was 23rd November 2014 at 11:49 PM ----------
So I relocked bootloader... Sent several test sms & so far so good. Wifi of course works, haven't tested bluetooth but ill report back. Boy I got lucky. No more linux for me... Jk

Everything You may need to install android 5.0.1
I'm writing this so that you all will not have to go through what I just experienced when trying to flash the android 5.0.1 OTA manual update. Here are some of the errors I've gotten out of and I will give you some tips to get fix these. I always seem to encounter issues that no one else has when flashing, so here we go.
Tip 1
1.)If you are trying to flash 5.0.1 (tip applies to any version) from the google website here: https://developers.google.com/android/nexus/images ....Make sure your computer can handle ".tgz" files. This took me a day and a half to figure out. If you try to download one of the files off this website without the proper software to do so you will simply get a ".tgz" file that you cannot extract the necessary files from.
*The solution is to download winrar from http://www.win-rar.com/predownload.html?&L=0 this website. Once you do and run it the ".tgz" file will become a folder (icon should look like stacked books) and you can proceed to actually follow the instructions on the page where you downloaded the file from. I learned this the hard way.
Tip 2
If you dont really understand how to us the "ADB" tools or "SDK" and everything related sounds like a foreign language to you then watch this video: http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/. It will explain how to copy files to your device while in bootloop. Pay special attention to the part about making sure your drivers are set up correctly. Drivers always get me when I installs. This knowledge will transfer over to downloading any rom or factory image in the future.
Links for Moving files to your device while in recovery:
Here are the appropriate drivers for copying files while in recovery to the nexus 5:
http://downloadandroidrom.com/file/drivers/Android/usb_driver.zip
Here is the fastboot link: http://downloadandroidrom.com/file/tools/fastboot.zip
Tip 3
The way I installed android 5.0.1 was:
1.)I downloaded the file from the google developer website that i pasted at the top
2.)I moved that file to a folder named "root" that i created on my desktop
*In this folder i have chainfire auto root http://autoroot.chainfire.eu/ in case i need to re-root my phone, I have the adb and fastboot.zip folders in my root folder as well.
3.)I moved the folder inside the FASTBOOT folder and extracted the file that i got from the developer website here. Once this is down there is another
3.)I extract the files here. After you extract there should be another folder called "image-hammerhead-lrx22c.zip." I copied those files to the fastboot folder as well so that they are outside of the zip file. I did not remove the zip file once I copied the insides to the outside. Right or wrong this is what I did.
4.)I used the Command prompt to navigate to this directory. Watch the how to copy files video to see how to navigate using the "cd" command
*basically i typed "cd desktop" which means change directory to the desktop. Then i did "cd root"....then "cd fastboot" ...YOUR PATH MAY BE DIFFERENT.
5.)Once i was here i could follow more of the instructions on the developer website. I could run that "flash-all.bat" command to begin flashing the 5.0.1. In order to run this command you literally type "flash-all.bat."
6.)After it finished it said,
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
helpful links: http://forum.xda-developers.com/showthread.php?t=1992063
This was okay, what you dont want is falures. While 5.0.1 is being installed, if you notice it say failure in the place where everything else is saying "OKAY" you have a problem. One guy on that xda link said:
"Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img"
You can type this into cmd and do each one by one and it may work.
7.)YOU MUST MAKE SURE TO EXTRACT THAT SECOND FOLDER inside the developer file! If you don't you will get failures because the program is looking for them. That's why manually installing them may work as well.
8.)IF YOU SEE THE ANDROID WITH NO LOADING BAR UNDERNEATH this does not mean that you are bricked. I thought it did and kept flashing 5.0.1 over and over and over again. Then i just waited a bit and my phone rebooted and i say the glorious dots rotating on my screen. I lived happily ever after.
9.)Once you are finished installing 5.0.1 you will loose root. Run that chainfire auto root program.You have to boot in to the bootloader screen...NOT RECOVERY...just the screen where you see the android and you can select "start" "recovery" etc. and open up that chainfire program and hit a key to start it. There are instructions on the actual program if you need help. If you are on the bootloader screen that i am talking about and you start the program it will "auto root" that is, automatically root your phone and thats that.
10.)Download root checker off the play store to see if you are actually rooted and have a blessed day. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Let me know if you need further explanation. I'm no pro but I've failed in soooo many ways i probably could help ya out! Jesus loves you all!

Possible Bricked Tablet - Please Help!

I think i may have bricked my nexus 10.. I was trying to install the chainfire3d application from the market, and when it rebooted, it wouldnt go past the X logo. waited for a long time, so i tried a hard reset, and still nothing. So i figured i would try using the toolkit to help fix. tried to relock, flash, and re-unlock, and it wouldnt work..after the step where you go into factory reset/wipe, it woudlnt go further. I cant get a custom recovery to install, it wont save the file. tried doing that step separately, and it seems to stick on sending the file over. this seems to be a common issue with anything i try.
The screen says:
"sending TWRP touch recovery..
sending 'recovery' (7246 KB) ...
and is just stuck there. this seems to happen in several places, with a few different things ive tried. When trying to flash the stock image, it will get stuck in similar places, perhaps not with the recovery step, but with a portion of the stock image. Been at this for a couple of hours... any help would be greatly appreciated!.
Also, as of now... it wont boot past the google logo. I can get it into fastboot by holding down the buttons, and I can get it into the stock recovery, but thats it. I don't even think adb is detecting the device. I have a feeling that may be a major roadblock to getting this thing fixed. Does anyone know how I can get the tablet to be detected by adb if i cant even get past the google logo screen at boot?
Update 1:
Still cant unbrick my device. any time i try to transfer or flash files to it... it stalls, and if i disconnect the device, i get this error:
FAILED (data transfer failure (too many links)).
Your Device will now boot into Android and detect ADB mode.
problem is, it doesnt reboot, and even if it did, it wouldnt be able to boot into android, since it wont go past the google logo when the device turns on. in fact, i cant even turn it off. only way to turn it off would be to wait for the battery to drain.
If this helps, here is what it says on the fastboot screen:
Device Information
Product Name: manta
Variant: wifi
H/W version : 8
Bootloader Version: MANTALJ12
Carrier Info: none
Serial Number: *********** (not going to publish that, lol)
LOCK STATE: Unlocked
Reboot Mode Flag: none.
anyone have any ideas at all how I can salvage this thing? Im kindof embarrassed honestly. Ive had 5 android devices prior to this one, and have rooted, flashed, and reflashed each of them countless times, and never, ever ran into this before. I could really use the help.
Quick note:
I just noticed that when i try to flash anything to the tablet, the following appears under the rest of the info i listed above.
FASTBOOT STATUS - DATA00713800 (this text is highlighted in light blue)
Update 2:
ok, so i tried to do the factory restore, and am running into the same wall as always. here is the text from the window, perhaps that may clue you into the problem:
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.tg
z
Extracting mantaray-jop40c-factory-0d641789.tar
Everything is Ok
Size: 329369600
Compressed: 326396069
Now extracting flashable Images
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.ta
r
Extracting mantaray-jop40c
Extracting mantaray-jop40c\image-mantaray-jop40c.zip
Extracting mantaray-jop40c\flash-base.sh
Extracting mantaray-jop40c\bootloader-manta-mantalj12.img
Extracting mantaray-jop40c\flash-all.sh
Extracting mantaray-jop40c\flash-all.bat
Everything is Ok
Folders: 1
Files: 5
Size: 329358105
Compressed: 329369600
Factory Images extracted. Starting Flash Process.
Now Flashing Bootloader Image..
sending 'bootloader' (1280 KB)... OKAY [ 0.232s]
writing 'bootloader'... OKAY [ 0.113s]
finished. total time: 0.345s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
Now Flashing Factory Image: Boot, Cache, Recovery, System and Userdata..
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........: R32CB01KDWW
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.002s]
sending 'boot' (4606 KB)...
Its just stuck on that last part, sending 'boot' (4606 KB)...
and under all the info on the fastboot page, the following appeared while this was happening:
FASTBOOT STATUS - DATA0047f800 (this line is highlighted in light blue)

*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)

cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
can you link it?

cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
trying that....
so far so good... dont want to get my hopes up though... below is what ive got so far in the cmd screen:
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
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........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...

Its been about 30 minutes now... and its still stuck on "sending 'system' (528847 KB)..." in the cmd window.... not sure what that means... it did take about a minute for the recovery to get sent over, and its about 100x larger in size, so i guess i will leave it connected like this for the next hour or so... and hope that it is just going REALLY slowly. Got my fingers crossed...

Battery died while waiting.... this is the complete text of the CMD screen while i was waiting.. forgot that it doesnt charge while in fastboot. got it plugged into an outlet for faster charging while its off.... hopefully when its charged up, i can try again and ill continue to progress
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
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........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3941.094s
Press any key to exit...

Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.

jodvova said:
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
Click to expand...
Click to collapse
I cant get it to load a custom recovery! any advice on how to get that going?

ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.

ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
Dumb question, if using a desktop PC are you using the front or rear USB ports? I had a similar issue where it would just get stuck on the "sending system" message. Switched the USB from front port to back port on my linux box and it solved my problem.
Sent from my Nexus 10 using Tapatalk 2

jodvova said:
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
Click to expand...
Click to collapse
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.

ltracte said:
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
Click to expand...
Click to collapse
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.

jodvova said:
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
Click to expand...
Click to collapse
couldnt get the command to work via adb, so i tried it using terminal inside TWRP, and this what it spit back at me:
/dev/block/platform/dw_mmc.0/by-name/system: clean. 11/51296 files. 6651/204800 blocks
i have no idea what that means, nor what else to do....

Fixed it!!!!

ltracte said:
Fixed it!!!!
Click to expand...
Click to collapse
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.

mskip said:
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
Click to expand...
Click to collapse
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!

Whew! So glad you finally had success & thanks for sharing. I'm reading up, research, etc. I received my N10 yesterday. I'm getting ready to unlock/root today.
Sent from my Nexus 7 using Tapatalk 2

ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
Hmm, did you try the flash-all.bat file that comes with the factory image? It does those 3 commands, + erases all partitions automatically.

ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
That's exactly what I did. Just followed the factory image flashing instruction on google's page(where you download the image file for N10). Did you figure out why it wassnt able to transfer the first time?

Boot-looping Nexus 6P - caused by Photo Sphere?

First post here at XDA - before I start with my problem, I should say thanks to everyone who posts here. I've come across this site so often when looking for information and always found it to be very helpful.
I was taking a Photo Sphere photo a few weeks ago, and after the photo had been taken, and during the processing/rendering stage, I looked away from my phone while holding it to let it work. I looked down to see the finished result about 30 seconds later and saw the Google startup screen. It appears that somehow, taking a Photo Sphere photo may have soft bricked my 6P, but I have no idea how. The phone itself was working perfectly normally prior to that.
I kept manually restarting it, powering it off, booting to recovery and restarting to see if I could get it back to normal with no success. It would occasionally, maybe one in twenty times, get to the Android boot animation, but would freeze after around 5 seconds on that, then restart again. Eventually, I thought to clear the cache partition via TWRP, so I did so and it then booted and loaded Android as normal. However, one of the first things I did was go to Settings to reset the time as it was wrong, and, as soon as it displayed the Settings screen, the phone restarted again, and no amount of cache clearing has resolved the issue since.
It's a 64GB 6P running Marshmallow 6.0.1, unlocked and rooted via Heisenberg's excellent guide and running TWRP 3.0.2.0, which was the latest available when I rooted. Right now, upon starting, it shows the "Your device software can't be checked for corruption. Please lock the bootloader." message as normal, then the Google logo, then it restarts and does the same again. I can access recovery mode as normal.
Does anyone have any ideas what steps I need to take to get my 6P operable again? Given that it booted after I wiped the cache then rebooted when I went to settings, my relatively uneducated presumption is that the root has somehow gotten messed up, but I don't know enough about troubleshooting Android to resolve it myself. I'd obviously prefer to avoid wiping it and losing data if possible. Although I'm a computer geek, I'm not 100% sure about Android ADB/fastboot commands and what to run to resolve this issue, so I thought I should defer to the experts here. I was considering flashing the factory image (part 11 of Heisenberg's guide) to see if that helped, but wasn't sure if that's the best first step to try at this point so thought it best to seek some advice rather than turn a soft brick into a hard one.
Thanks for any and all assistance!
BL: angler-03.51
Baseband: angler-03.61
Product/Variant: ANGLER-ROW-VN1
Device is UNLOCKED.
Qfuse Status: ENABLED.

Well, maybe the above is a bit too much to read...my bad habit of being verbose. Here's a tl;dr version;
Unlocked and rooted 64GB 6P running Marshmallow is boot-looping at the bootloader unlocked screen
Wiping cache only temporarily resolved
Can access recovery and fastboot as normal
Any ideas?

Well, mine appears to have done the same exact thing, but I wasn't using photosphere. Before I continue, here's my story...
I'm on vacation from Sept 1st to Sept 5th, and on the 4th(yesterday), I was browsing using Chrome before it froze and shut off on me, which then turned into a bootloop with the Google screen. Next, I did what I normally do when I have a problem, I head to recovery(depending on what I was last doing, I'd delete a file that I know caused it), but instead, I couldn't get into recovery. I tried maybe about 10 times and got into recovery twice. I removed all overlays that had to do with Substratum and deleted my cache/dalvik cache, rebooted and I got to the Android updating screen. It went through the process, froze and rebooted again. Now, I'm at the point where it's just the Google screen. I can get into the Bootloader, but nothing else. I'm thinking I'm having hardware failure or something. I attempted to do a factory image restore twice now, doing the third one as I type this before I contact Google, but yeah... I can't get into recovery or past the Google screen. Only the bootloader is accessible.
Now... As for your situation, download Wugfresh Nexus Toolkit, or follow later on in Heisenberg's guide to restore the factory image without deleting the userdata partition. There may still be a chance for you to get your data back, but for me... nah. Good luck.

Hey Curiousn00b, thanks for sharing your story. It seems really weird that they're just dying so suddenly and so fatally with no hardware failures. I'm wondering if this is part of a larger issue.
I just tried flashing the factory images for MHC19I as per part 11 of Heisenberg's guide and, alas, no luck. The images flashed fine, but it's still doing the same thing as before.
Is there anything else I can do to get it to a usable state again without completely wiping it? Should I try another factory image, maybe an earlier one? And, if I do have to wipe it, can I re-flash TWRP recovery and take a backup first?
Here's my log output for confirmation. Thanks again, I appreciate your reply.
Code:
C:\SDK\platform-tools>fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.105s]
writing 'bootloader'...
OKAY [ 0.237s]
finished. total time: 0.345s
C:\SDK\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.013s
C:\SDK\platform-tools>fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.202s]
writing 'radio'...
OKAY [ 2.855s]
finished. total time: 4.060s
C:\SDK\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\SDK\platform-tools>fastboot flash boot c:\angler\images\boot.img
target reported max download size of 494927872 bytes
sending 'boot' (12045 KB)...
OKAY [ 0.287s]
writing 'boot'...
OKAY [ 0.387s]
finished. total time: 0.676s
C:\SDK\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\SDK\platform-tools>fastboot flash cache C:\angler\images\cache.img
target reported max download size of 494927872 bytes
erasing 'cache'...
OKAY [ 0.018s]
sending 'cache' (5752 KB)...
OKAY [ 0.161s]
writing 'cache'...
OKAY [ 0.226s]
finished. total time: 0.409s
C:\SDK\platform-tools>fastboot flash recovery C:\angler\images\recovery.img
target reported max download size of 494927872 bytes
sending 'recovery' (12977 KB)...
OKAY [ 0.337s]
writing 'recovery'...
OKAY [ 0.406s]
finished. total time: 0.747s
C:\SDK\platform-tools>fastboot flash system C:\angler\images\system.img
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.561s]
sending sparse 'system' (478066 KB)...
OKAY [ 12.529s]
writing 'system'...
OKAY [ 6.772s]
sending sparse 'system' (483054 KB)...
OKAY [ 12.458s]
writing 'system'...
OKAY [ 7.038s]
sending sparse 'system' (480089 KB)...
OKAY [ 12.603s]
writing 'system'...
OKAY [ 14.026s]
sending sparse 'system' (469850 KB)...
OKAY [ 12.264s]
writing 'system'...
OKAY [ 22.259s]
sending sparse 'system' (55828 KB)...
OKAY [ 1.530s]
writing 'system'...
OKAY [ 2.856s]
finished. total time: 104.912s
C:\SDK\platform-tools>fastboot flash vendor C:\angler\images\vendor.img
target reported max download size of 494927872 bytes
sending 'vendor' (185185 KB)...
OKAY [ 4.567s]
writing 'vendor'...
OKAY [ 15.101s]
finished. total time: 19.670s
C:\SDK\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.008s
C:\SDK\platform-tools>

Seems like it's possible for you to be in the same exact situation as me, unless you can boot into recovery. I can't do that.
If you can boot into recovery, just take your files off the device and go for a full wipe. I think my device hard bricked itself somehow... You may be soft-bricked, but in the worst case, hard bricked. :c

Yep, I can't boot into recovery either right now because I flashed the factory image. I'll try to re-flash the TWRP recovery and see how it goes.
I can't believe a software issue can get to the stage of hard-bricking your phone while doing nothing other than unlocking and rooting it, and even putting it back to factory and doing a full wipe doesn't resolve it. I really hope I don't get to that stage, although it's disappointing to hear that you've had that experience. Thanks again for your feedback, I'll update once I've attempted to re-flash.

So I finally got around to flashing the TWRP 3.0.2.0 recovery again and still no dice, so I made a start on the backup process.
One thing I wanted to check before I do the full wipe and reinstall stock, though - my partitions in TWRP showed this from the Backup screen;
Code:
Boot (32MB)
System (1850MB)
System Image (3072MB)
Vendor (173MB)
Vendor Image (200MB)
Data (0MB)
Cache (0MB)
Recovery (32MB)
EFS (8MB)
This may just be paranoia, but which of those is the user data (apps, files, photos etc.) stored in? I get that the Data partition is wiped when doing the stock image install, so that's fine, but I presume System would be the OS itself - and I'm pretty sure I have more than 2-3GBs of data on my 6P, but the largest there is 3GB.
Also, using Backup from the TWRP main menu, how do I restore the user data once I've got it back up and running again without killing the OS again? Can I selectively choose what to restore?
I've copied the TWRP backup folder to my laptop using adb pull, so that's safely stored there for now. Just wanted to check before I totally wipe everything and start clean.
Thanks.

MarkB16 said:
So I finally got around to flashing the TWRP 3.0.2.0 recovery again and still no dice, so I made a start on the backup process.
One thing I wanted to check before I do the full wipe and reinstall stock, though - my partitions in TWRP showed this from the Backup screen;
This may just be paranoia, but which of those is the user data (apps, files, photos etc.) stored in? I get that the Data partition is wiped when doing the stock image install, so that's fine, but I presume System would be the OS itself - and I'm pretty sure I have more than 2-3GBs of data on my 6P, but the largest there is 3GB.
Also, using Backup from the TWRP main menu, how do I restore the user data once I've got it back up and running again without killing the OS again? Can I selectively choose what to restore?
I've copied the TWRP backup folder to my laptop using adb pull, so that's safely stored there for now. Just wanted to check before I totally wipe everything and start clean.
Thanks.
Click to expand...
Click to collapse
Did you verify any contents in TWRP that you pulled to ur PC? . In TWRP go to advanced and then file explorer, you should see your data.
Edit: Data would be where the user data is stored (pictures, downloads, etc.)
I terms of restoring data, I've always gone with Titanium Backup but in this case not sure you'd be able to as it sound like u can't boot into the OS and see ur apps?

spunks3 said:
Did you verify any contents in TWRP that you pulled to ur PC? . In TWRP go to advanced and then file explorer, you should see your data.
Edit: Data would be where the user data is stored (pictures, downloads, etc.)
I terms of restoring data, I've always gone with Titanium Backup but in this case not sure you'd be able to as it sound like u can't boot into the OS and see ur apps?
Click to expand...
Click to collapse
Yep, if I go to TWRP, I can view the backups in the \sdcard\TWRP\backups\[serial number] folder, and now that I've done adb pull, they're on my hard drive, too.
Exactly, yeah, it's still boot-looping, so I can't get into the OS to run Titanium Backup or migrate any data. It's still looping at the "Device can't be checked for corruption" screen. I followed Heisenberg's guide to re-flash the stock images and didn't flash userdata. Why would the data partition show as being empty in TWRP unless the partition has been royally messed up when the phone had it's original heart attack?
And, if the data partition is where userdata is stored, I presume that means the data on the phone is already gone? Dumb question, I think I know the answer already, but don't understand how it could have happened when I didn't wipe it myself.

MarkB16 said:
Yep, if I go to TWRP, I can view the backups in the \sdcard\TWRP\backups[serial number] folder, and now that I've done adb pull, they're on my hard drive, too.
Exactly, yeah, it's still boot-looping, so I can't get into the OS to run Titanium Backup or migrate any data. It's still looping at the "Device can't be checked for corruption" screen. I followed Heisenberg's guide to re-flash the stock images and didn't flash userdata. Why would the data partition show as being empty in TWRP unless the partition has been royally messed up when the phone had it's original heart attack?
And, if the data partition is where userdata is stored, I presume that means the data on the phone is already gone? Dumb question, I think I know the answer already, but don't understand how it could have happened when I didn't wipe it myself.
Click to expand...
Click to collapse
You should be able to confirm if the data is really there or not by going into TWRP > Advanced > File Manager.
You should also check to see if data and cache are mounted in TWRP.
I haven't gone over Heisenberg's steps yet but, since you've already attempted to flash userdata, whatever you had is most likey gone.
Try the following via fastboot for erasing everything and starting from scratch.
NOTE: THE FOLLOWING COMMANDS WILL ERASE EVERYTHING ON YOUR PHONE.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader [name of your file].img
fastboot reboot-bootloader
fastboot flash radio [name of your file].img
fastboot reboot-bootloader
fastboot flash recovery [name of recovery file].img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
fastboot format userdata
fastboot format cache

That's what I'm saying - at no point have I ever entered the command fastboot erase userdata - I specifically wanted to keep the data and do a backup, and the phrase userdata would be a big red flag to me, so I wouldn't enter it unless I knew for sure the data was already gone. I'm wary of even touching the data partition, so I've been sure to follow all of the commands very carefully. I've been in I.T. for a while, I know the danger of running the wrong command.
I can see that there are data files in the backups, however the data.ext4.win file is only 6KB, so I guess there's no data there.
I don't know how to mount the data and cache partitions in TWRP - I can see the option to do it, but have no idea what it does.
Thanks again.

Mine was the Camera app doing the HDR processing. For the first few times it happened, it was random - the crash and bootloop will happen after taking 2-3 photos. Today, it finally hung while processing HDR and it never recovered. Sigh, seems like I need to send my phone to Huawei. I have tried all sorts of flashing to no avail.

kurtisnet said:
Mine was the Camera app doing the HDR processing. For the first few times it happened, it was random - the crash and bootloop will happen after taking 2-3 photos. Today, it finally hung while processing HDR and it never recovered. Sigh, seems like I need to send my phone to Huawei. I have tried all sorts of flashing to no avail.
Click to expand...
Click to collapse
So my phone isn't the only one with an aversion to taking photos? I don't understand how just taking a photo could cause this unless there's a massive software bug somewhere that requires a very specific set of conditions to brick your device. Would you mind letting me know what Huawei say to your issue? I'm curious as to what they think could cause a failure of this degree.

MarkB16 said:
That's what I'm saying - at no point have I ever entered the command fastboot erase userdata - I specifically wanted to keep the data and do a backup, and the phrase userdata would be a big red flag to me, so I wouldn't enter it unless I knew for sure the data was already gone. I'm wary of even touching the data partition, so I've been sure to follow all of the commands very carefully. I've been in I.T. for a while, I know the danger of running the wrong command.
I can see that there are data files in the backups, however the data.ext4.win file is only 6KB, so I guess there's no data there.
I don't know how to mount the data and cache partitions in TWRP - I can see the option to do it, but have no idea what it does.
Thanks again.
Click to expand...
Click to collapse
If at anytime you did 'fastboot flash userdata userdata.img' you've overwritten the data partition and lost the data :-/ wish I could help more...

MarkB16 said:
So my phone isn't the only one with an aversion to taking photos? I don't understand how just taking a photo could cause this unless there's a massive software bug somewhere that requires a very specific set of conditions to brick your device. Would you mind letting me know what Huawei say to your issue? I'm curious as to what they think could cause a failure of this degree.
Click to expand...
Click to collapse
I've just collected my phone again from Huawei. They replaced the motherboard (new imei number). Sent in at 11.30am today and is ready by 4pm. Applaud Singapore Huawei service center for their super fast turnaround time. Totally was expecting at least a week of repair lol.
Mine was bricked completely - internal storage was accessible from twrp but that was about it. Flashing new roms with everything wiped didn't help. Flashing pure nexus also will sometimes hang and reboot. Sometimes it'll be successful.

spunks3 said:
If at anytime you did 'fastboot flash userdata userdata.img' you've overwritten the data partition and lost the data :-/ wish I could help more...
Click to expand...
Click to collapse
But I didn't, that's what I mean - it's like the data partition has been wiped for no reason at all, or it was part of the initial failure. I haven't run any commands which should touch that partition.
Am I right in thinking that, at this stage, the my data is unrecoverable, and the best bet is just to try to get the phone back up and running again? Are there any other checks I could try to confirm the data is already gone?
Thanks, I do appreciate your input.
kurtisnet said:
I've just collected my phone again from Huawei. They replaced the motherboard (new imei number). Sent in at 11.30am today and is ready by 4pm. Applaud Singapore Huawei service center for their super fast turnaround time. Totally was expecting at least a week of repair lol.
Mine was bricked completely - internal storage was accessible from twrp but that was about it. Flashing new roms with everything wiped didn't help. Flashing pure nexus also will sometimes hang and reboot. Sometimes it'll be successful.
Click to expand...
Click to collapse
Nice, glad they got it sorted so quickly for you. Hoping I can get mine running again, but I'll contact them if I can't.

MarkB16 said:
But I didn't, that's what I mean - it's like the data partition has been wiped for no reason at all, or it was part of the initial failure. I haven't run any commands which should touch that partition.
Am I right in thinking that, at this stage, the my data is unrecoverable, and the best bet is just to try to get the phone back up and running again? Are there any other checks I could try to confirm the data is already gone?
Thanks, I do appreciate your input.
Nice, glad they got it sorted so quickly for you. Hoping I can get mine running again, but I'll contact them if I can't.
Click to expand...
Click to collapse
Hmmmmm... The only other thing that comes to mind is trying something like a fastboot pull command

I've done a full adb pull for all the partitions already, and the data partition file was only 6KB.

One thing I clearly forgot about - I can use File Manager to confirm if the data is there. I've checked there, and all of the files and folders on my device still appear to be shown as normal - if I check /sdcard/DCIM/Camera, I can see my photos, if I check /sdcard/Downloads, I can see stuff I've downloaded, etc. However, when I go to the TWRP menu and choose Backup, the Data partition is 0MB. Tapping Refresh Sizes doesn't change anything.
So if the userdata is stored on the Data partition and I can confirm the files are still on the phone, how is the Data partition showing as 0MB in the Backup screen? What on earth is going on?

The data partition that you backed up isn't userdata, it's the installed apps partition. There is a separate partition for userdata. When installing a new rom, wiping /data in twrp is always a good idea but it won't touch your userdata.
You should be able to mount your phone to your PC while in twrp and copy all your data over, then proceed w a full factory flash to try and correct your problem. When you mount it, it will show up on PC just like a thumb drive.

[GUIDE] Update with fastboot

Guide for installing new security update with fastboot and with a bootloader-unlocked Pixel XL.
This is basically the same thing as usual but with the new structure.
If you have modified a little the stock android (hosts file, root, kernel, etc.), you may experience a fail in OTA update;
If you have a bootloop/soft brick/not sure of the state of your android system;
This is the solution.
This WILL NOT delete your data and apps. This will remove your custom kernel/root/hosts/recovery through (which is a good thing because it will be clean then).
I assume you already have anything to do fastboot command. If not, see this good thread.
1) Download your system image for Marlin (Pixel XL) on google website.
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
2) Unzip the file marlin-nde63v-factory-a66866ba.zip
3) Unzip inside the new directory (marlin-nde63v) the image-marlin-nde63v.zip
4) Reboot into bootloader
Code:
adb reboot bootloader
5) Execute fastboot commands (assuming the bin is on your PATH)
Code:
fastboot flash bootloader bootloader-marlin-*.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
Here we go, you have a fresh unrooted vanilla android with latest security patch.
6) To add TWRP and Root:
Code:
fastboot boot /path/to/twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
Root thread for more information.
TWRP thread for more information.

** Reserved **

cam30era said:
@firewave,
Thanks for posting the guide. Just like Nexus devices except for the slot files. After unzipping the factory image, I do notice 15 additional files (other than boot, system, vendor, etc) that I've never seen before on a Nexus device. Do you happen to know what those are for, and why we don't flash them if doing a manual fastboot flash?
Thanks, in advance....
Click to expand...
Click to collapse
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.

firewave said:
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.
Click to expand...
Click to collapse
aboot is actually part of the bootloader.

death2all110 said:
aboot is actually part of the bootloader.
Click to expand...
Click to collapse
yep, it's why I'm unsure what to do with. Probably nothing.
I will loopmount the file at home and see.

Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.

wx9kvh said:
Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.
Click to expand...
Click to collapse
In the op in bold, he said it will not erase your data or apps

C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result

dablitzkrieg said:
C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result
Click to expand...
Click to collapse
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.

chapelfreak said:
In the op in bold, he said it will not erase your data or apps
Click to expand...
Click to collapse
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.

wx9kvh said:
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.
Click to expand...
Click to collapse
That makes sense, our posts are an hour apart or so.

Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
I appreciate the help. The link you provided me, I've downloaded it, but for some reason cant launch the app after I unzip the file. I've been at this for like 4 hours. I've tried so many different things and can't get past the Google screen. Please help

I was able to utilize the old tool. I'm all set. Thanks

chapelfreak said:
That makes sense, our posts are an hour apart or so.
Click to expand...
Click to collapse
Lol. No big deal haha.

Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
Scott...can I flash the radio.img from V to the Verizon X. This radio is horrible

ADB Sideload Works too
Alternatively, use the instructions found on this page followed by a re-flash of your preferred kernel and a fastboot boottoroot to regain root.
https://developers.google.com/android/nexus/ota

So i just followed all of these instructions, and when going into about phone, it shows that i am now on an N build and still with the October security patch. What did i miss?
Update :
I believe I fixed the issue. The little window with the commands in it for some reason had scrolled up and I missed the flashing the "bootloader-marlin-*" step.
Update 2 :
I am now on X with the November security update. GREAT GUIDE!

Followed it to a T and soft bricked mine so now trying to find a way to fix or toss it out the windows haha. Just a heads up guys.
Ended up using the skipsoft tool and pushing a factory update same results but lost data/apps no biggie.

This is odd i followed the instructions trying to flash X to my phone coming from NDE63P and somehow ended up on NDE63N (Ignore this i missed a command)

What steps do I need to add if I want to completely restore back to factory settings (format userdata)? Or would it be the same to just factory reset through the newly restored stock recovery?

Failed to load system.img for OS 7.1.1 on Nexus 6P

Hi,
I am currently flashing my Nexus 6P with OS 7.1.1
After executing flash-all.bat as suggested on Android factory images i get the below error:
"sending 'bootloader' (3532 KB)...
OKAY [ 0.103s]
writing 'bootloader'...
OKAY [ 0.202s]
finished. total time: 0.317s
rebooting into bootloader...
OKAY [ 0.081s]
finished. total time: 0.084s
sending 'radio' (48728 KB)...
OKAY [ 1.086s]
writing 'radio'...
OKAY [ 2.175s]
finished. total time: 3.267s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.018s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1473177068 bytes
error: update package missing system.img
Press any key to exit..."
Can anyone help out in this? Not sure what does failed to allocate -1473177068 bytes means? How can I solve this.

Try flashing each IMG file manually.

Don't use the flash-all.bat program. Manually type in your fastboot commands.
Extract that big ZIP you have in the same folder with your flash-all.bat. You'll see a bunch of img files called vendor.img, system.img, etc.
Once extracted, run the following commands in order. Replace "partition" with the img file name. Example: fastboot format system
fastboot format partition (if it gives an error, try fastboot erase partition).
fastboot flash partition imgfile
fastboot format cache
fastboot reboot-bootloader
Examples of what things should look like:
fastboot format system
fastboot flash system system.img
fastboot format cache
fastboot reboot-bootloader
<once rebooted, shouldn't take more than 2 seconds>
fastboot format vendor
fastboot flash vendor vendor.img
fastboot format cache
fastboot reboot-bootloader
<again, reboot, ~2 seconds>
If at any time it says it can't format memory type or something similar, usually this is for bootloader, radio and boot partitions, use fastboot erase boot (fastboot erase bootloader, fastboot erase radio).
Do this for each of the files, except for userdata - don't even flash that, just format userdata and skip the flash userdata part.
Also, flash your recovery of TWRP, the latest, and make sure that you boot to recovery first, before you boot the phone all together.

Did you verify the checksum of the image?

DON'T DO THAT...
Wiltron said:
fastboot erase bootloader
Click to expand...
Click to collapse
This will be your last fastboot command... Phone bricked.
To the OP, you should solve your flash-all problem as this script is the recommended way to flash factory images. You need some disk space (like 4 or 5GB)

rchtk said:
DON'T DO THAT...
This will be your last fastboot command... Phone bricked.
Click to expand...
Click to collapse
As long as you flash the bootloader again prior to rebooting you're fine.
I do this weekly with new builds of various ROMs.

Wiltron said:
As long as you flash the bootloader again prior to rebooting you're fine.
I do this weekly with new builds of various ROMs.
Click to expand...
Click to collapse
I find it way too risky tbh and don't see any added value in doing this.

rchtk said:
I find it way too risky tbh and don't see any added value in doing this.
Click to expand...
Click to collapse
Yeah, no reason to advise this. Especially in a thread of someone who may or may not be comfortable using fastboot. Risk > Reward 100%
Not like any 'gremlins' get left behind when updating a bootloader.
OP, just read and follow the beginner sticky thread and you'll do just fine. This one.

RoyJ said:
Yeah, no reason to advise this. Especially in a thread of someone who may or may not be comfortable using fastboot. Risk > Reward 100%
Not like any 'gremlins' get left behind when updating a bootloader.
OP, just read and follow the beginner sticky thread and you'll do just fine. This one.
Click to expand...
Click to collapse
Thank you RoyJ.....it worked

I did the "fastboot flash system system.img" and it says "FAILED <remote: data too large>. Never have any problem with the monthly updates before.

wormbaby11 said:
I did the "fastboot flash system system.img" and it says "FAILED <remote: data too large>. Never have any problem with the monthly updates before.
Click to expand...
Click to collapse
Googling wasn't much help in this case, found threads mostly for old HTC phones around 2013. However I did find one user trying to install 7.1 on his 5X which was able to solve his own issue by updating his Android tools in the SDK.
If you don't already have it, download and install the Android SDK. Follow the link I posted above and there's a section about how to install it.
Open the SDK Manager and under the section named "Tools" you should see; "Android SDK Tools" & "Android SDK Platform-tools".
Check to see if there's an update. I just noticed there is an available update on my PC. SDK Tools & SDK Platform-tools updated versions are 25.2.3 & 25.0.1, respectively. Update and reboot your PC and that should solve your issue. Let us know if that works for you.
Edit: Also, this is more than just a monthly security update. It was a bump up from 7.0.0 to 7.1.1. In any version bump like that, it never hurts to make sure the SDK is up to date.

Thanks Roy, that did the trick.
RoyJ said:
Googling wasn't much help in this case, found threads mostly for old HTC phones around 2013. However I did find one user trying to install 7.1 on his 5X which was able to solve his own issue by updating his Android tools in the SDK.
If you don't already have it, download and install the Android SDK. Follow the link I posted above and there's a section about how to install it.
Open the SDK Manager and under the section named "Tools" you should see; "Android SDK Tools" & "Android SDK Platform-tools".
Check to see if there's an update. I just noticed there is an available update on my PC. SDK Tools & SDK Platform-tools updated versions are 25.2.3 & 25.0.1, respectively. Update and reboot your PC and that should solve your issue. Let us know if that works for you.
Edit: Also, this is more than just a monthly security update. It was a bump up from 7.0.0 to 7.1.1. In any version bump like that, it never hurts to make sure the SDK is up to date.
Click to expand...
Click to collapse

Glad to hear you got it working!

[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work