Related
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!
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?
I am new to this site & i still have not fixed my problem
I used clock work mod i think it sucks myself I made back up and sent it to my computer put it back to tablet now it says its to big
or bad file . i am so confused what to do now .
I also tried to flash my tablet back to stock thinking it could help but i get this error . using many videos i watched how to use the tool kit
and no luck . even though the files are in there .
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >
so i can not fix it back to stock and i can not load any Custom rom backups I saved this just bites.. I hope you can assist me
thank you
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
You can ignore this errormessage. This is normal when flashing stock. I don't use cwm. I prefer twrp instead.
Flashing stock should work on any tablet. Try it manually without a toolkit. Is your device a grouper / wifi / version without 3G? Then here is a solution.
Download adb and fastboot, for example here: https://mega.co.nz/#!1c1XjIIC!dTyG200R4V3BPIfrac4xayEttP02f9tYlPkqAlqvTko . Unzip the folder.
Download the apropriate firmware for your device (nakasi): https://developers.google.com/android/nexus/images#nakasi
Extract the contents of the firmware file in your folder with adb and fastboot.
Put your nexus 7 in fastboot/bootloader mode (you can do this by pushing all three buttons on the sides simultaniously).
Open a terminal in the folder with adb and fastboot by holding shift and right clicking inside the folder.
Type (this will erase everything from your device):
: fastboot erase boot
: fastboot erase cache
: fastboot erase recovery
: fastboot erase system
: fastboot erase userdata
If you need to update your bootloader, then type:
: fastboot flash bootloader bootloader-grouper-4.18.img
: fastboot reboot-bootloader
Then type:
: fastboot -w update image-nakasi-jdq39.zip
Your device will reboot and have the latest firmware installed. Again go to bootloader/fastboot mode. Download twrp here: http://www.teamw.in/project/twrp2/103
Type:
: fastboot flash recovery nameofrecovery.img
With TWRP you can easily root your device (no need to push files), make backups, flash zips and even use USB-otg. I found it more usefull then CWM and it works perfectly with goomanager (which is free).
So I was getting ready to flash a rom and I accidently wipped my whole phone. I can still use fastboot, but when I try to flash a rom using this command
Fastboot update [Rom_Filename.zip]
I get the following error message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
does anyone know of a rom I can flash through fast boot?
I figured it out, flashed a recovery image, then pushed a rom to the phone with adb and it flashed just fine.
I wanted to get on the latest developer preview release, downloaded the system image, and flashed it to my phone, when done i tried to reboot it, but it stayed on the white google logo screen infinitely. Eventually rebooted, and now won't even attempt to boot. It just goes back to fastboot.
Any attempt to go to recovery, boot the system, or anything - gives an error "Your device is corrupt. It can't be trusted and may not work properly". It offers a link to g.co/ABH then an option to press the power to continue, when I do, it briefly flashes the google logo, then back to the bootloader. Where it has a reason shown as "error booting boot.img"
It doesn't respond to any adb or fastboot commands, but does show in the device manager as LeMobile Android Device (Android Bootloader Interface). And that's about it.
I seem to be stuck in a loop here, and would appreciate if anyone has any advice to offer.
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Ohiostyle said:
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Click to expand...
Click to collapse
Is it going from fastboot to fastbootd?
Yeah it was, it completed a lot of other read/write actions after moving over to fastbootd, before failing.
I was able to get it working by sideloading the ota file. Any system image (always factory images) that I would try to flash would fail at the same point. I have no idea why.
Ohiostyle said:
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Click to expand...
Click to collapse
you need to extract the other zip within the image and make sure you extract it where your adb tools are
tmoore3496 said:
you need to extract the other zip within the image and make sure you extract it where your adb tools are
Click to expand...
Click to collapse
Yes, I had that problem time ago (I think with the OG Pixel).
Doing what you described fixed it, now I always do it just in case.
Also updating to the latest platform tools.
Can you go into recovery? If so try sideloading an OTA file.