i have one received from customer , when i power on just hang on start-up log
to fix that i need just unlock boot loader flash the phone (using Nexus Root Toolkit1.8.6 )
but this one , root is done phone habe unlocked boot loader , when i try to flash i get this error
archive does not contain 'boot.sig'
PHP:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2203 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
OKAY [ 0.318s]
finished. total time: 0.398s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
sending 'radio' (45537 KB)...
OKAY [ 1.503s]
writing 'radio'...
OKAY [ 2.578s]
finished. total time: 4.083s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
archive does not contain 'boot.sig'
error: out of memory
any help ^
Probably is not the problem about that "sign" error but next line, out of memory error. Check if there is any storage left. If there is,... What rom do you flash with?
Addition: i had a similar problem and i couldnt instal 4.4.4, i did first install 4.2 amd after that on 4.4.4 and it was successful.
I did it by this manual:
https://developers.google.com/android/nexus/images
Sent from my Nexus 4 using XDA Free mobile app
bojanz said:
Probably is not the problem about that "sign" error but next line, out of memory error. Check if there is any storage left. If there is,... What rom do you flash with?
Addition: i had a similar problem and i couldnt instal 4.4.4, i did first install 4.2 amd after that on 4.4.4 and it was successful.
I did it by this manual:
https://developers.google.com/android/nexus/images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
This ^ boot sig error is normal
Sent from my Nexus 5 using XDA Free mobile app
yes phone work with 4.2 as you say thx for help
but i have base band version unknown
hitibiti said:
yes phone work with 4.2 as you say thx for help
but i have base band version unknown
Click to expand...
Click to collapse
Fastboot flash the 4.2 cache image
Sent from my Nexus 5 using XDA Free mobile app
how can i do that ?
thx
hitibiti said:
how can i do that ?
thx
Click to expand...
Click to collapse
Download the factory image. Extract it. Inside is a zip, extract that too. In there you'll find the cache.img. boot into the bootloader and in a cmd window on the pc use
fastboot flash cache cache.img
If you don't have fastboot set up on the pc Google 15 second adb install xda
Sent from my Nexus 5 using XDA Free mobile app
Related
So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
binaryfalcon said:
So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
Click to expand...
Click to collapse
You flash the images, then you flash TWRP, then you do a factory reset in TWRP, and install SuperSU (http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip), and then boot. You'll now have 4.4 Rooted.
binaryfalcon said:
So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
Click to expand...
Click to collapse
How long does it take to flash the image-occam-krt16o.zip? I have been waiting for 20 minutes now. This is my output from the command window
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.076s]
writing 'bootloader'...
OKAY [ 0.298s]
finished. total time: 0.375s
wickdc said:
How long does it take to flash the image-occam-krt16o.zip? I have been waiting for 20 minutes now. This is my output from the command window
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.076s]
writing 'bootloader'...
OKAY [ 0.298s]
finished. total time: 0.375s
Click to expand...
Click to collapse
You can run the flash all command, or you flash everything separately. Go to efrant's guide on how to do that here on xda. You have now flashed the bootloader succesfully, now you will have to flash the other images as well.
Sent from my Nexus 4 using xda app-developers app
why don't you install cwm/twrp first? it's a lot easier to flash in my opinion (not if you want to install the image from your computer)
but normally it just takes a few moments/minutes
Nexus 10 getting stuck at splashing screen..
Tried using flash-all.bat (Downloaded from Google developers site ) and
sending 'bootloader' (2203 KB)... OKAY
writing 'bootloader'... FAILED (remote: partition table update fail!)
rebooting into bootloader... OKAY
< waiting for device >
sending 'radio' (45537 KB)... OKAY
writing 'radio'... FAILED (remote: unknown partition...)
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: XXXXXXXXXXX
Baseband Version.....: no modem
Serial Number........: XXXXXXXXXXXX
--------------------------------------------
checking product... FAILED
Device product is '$$$$$$'.
Update requires 'mako'.
Press any key to exit...
Getting the above error ..Please help me what to do as i am unable to start the device.
This happened when i was rooting the nexus 5 ..
Hi,
It looks a bad issue... Probably something went wrong and you lost your partition table . Are you sure your bootloader is unlocked?
~Lord
sidvangala said:
Nexus 10 getting stuck at splashing screen..
Tried using flash-all.bat (Downloaded from Google developers site ) and
sending 'bootloader' (2203 KB)... OKAY
writing 'bootloader'... FAILED (remote: partition table update fail!)
rebooting into bootloader... OKAY
< waiting for device >
sending 'radio' (45537 KB)... OKAY
writing 'radio'... FAILED (remote: unknown partition...)
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: XXXXXXXXXXX
Baseband Version.....: no modem
Serial Number........: XXXXXXXXXXXX
--------------------------------------------
checking product... FAILED
Device product is '$$$$$$'.
Update requires 'mako'.
Press any key to exit...
Getting the above error ..Please help me what to do as i am unable to start the device.
This happened when i was rooting the nexus 5 ..
Click to expand...
Click to collapse
What is the mako all about is that not the code name for the nexus 4 ??
lj50036 nailed it, partition table isn't messed up, it just isn't the same for the mako, which is a good thing your bootloader still runs these checks or you were in for a brick
Be sure to download the manta firmware and try again
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
lj50036 nailed it, partition table isn't messed up, it just isn't the same for the mako, which is a good thing your bootloader still runs these checks or you were in for a brick
Be sure to download the manta firmware and try again
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What made me confused was about the Bootloader: XXXXXXXXX. It made me think that the partition table was messed up, but it probably is just mako... Download the new firmware and make sure it's manta.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1
I didn't see the mako when I first read it either, and you do get a similar message if the partition table were messed up. Actually in a sense it was as the manta and mako have different ones
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
I didn't see the mako when I first read it either, and you do get a similar message if the partition table were messed up. Actually in a sense it was as the manta and mako have different ones
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thx you a pat on the back for me....
[Q&A] [Toolkit] Wug's Nexus Root Toolkit v1.9.3 [Updated 10/28/14]: Nexus 10 Thread
Q&A for [Toolkit] Wug's Nexus Root Toolkit v1.9.3 [Updated 10/28/14]: Nexus 10 Thread
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Toolkit] Wug's Nexus Root Toolkit v1.9.3 [Updated 10/28/14]: Nexus 10 Thread. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Armeniandave said:
I was asking if it did. I just updated to lollipop without root.
I haven't tried to install twrp or root it yet.
Click to expand...
Click to collapse
I've tried it twice and it won't root my device.
---------- Post added at 08:23 PM ---------- Previous post was at 08:15 PM ----------
Evidently I have to post here since I don't have enough posts (??).
Anyhow, I upgraded to 5.0.0 via the Toolkit, well attempted to since I guess it's a bad idea if you're on an encrypted FS since it reported corruption and then wipe/reset. So I attempted to do a restore and the Toolkit keeps telling me I'm set to "Any Build" despite being set to 5.0. I tell it the correct one, go through the process again and yet it still Restore mode says it's "Any Build". I don't know if this is a bug or I'm doing something wrong since if I set it to 4.4.4 it works fine.
I'm attempting to re-flash 4.4.4 now and will see if I can restore my backup. Total clusterf...
Root Nexus 10 v1.9.4 on Lollipop.
Running Root+custom recovery script. Live log is on, and everything seems to go as it should. When final boot is done SU notifies that binaries need updating, which I accept. Then Device boots into recovery and when it returns to system SU informs that there's no binary installed..!?
Prior to this I rooted my Nexus 5 on Lollipop without issues...
Thx for your support!
Martin
To reply to myself I ran a srock+unroot script, and then tried to root once again - this time it appeared to work
Installing 5.0 through NRT limited my storage to 13.0 GB
I have a 32 GB Nexus 10 and the storage shows up as 13 GB after installing Android 5.0 through the Nexus Root Toolkit. Can someone help me with fixing that?
After you've rooted using the tool kit, message appears that describes your problem pretty well - the solution suggested by wugfresh is to perform a factory reset, IIRC - have you tried this already?
Mas
Mine did the same thing. Factory reset fixed it
13 GB instead of 64 ?
cancelled
Hashcheck Mismatch
I'm trying to flash the stock firmware to my wife's Nexus 4 so she can receive the 5.0 OTA and install it correctly. The problem I'm encountering with the "flash stock+unroot" button is that the image files always fail the hash check, as do the twrp downloads and the superSU downloads and pretty much any file that this program tries to hash will fail.
I've downloaded the hashcheck shell extension and manually verified every file I've tried to load, they ALL have correct md5sum values when compared to the md5s on the google developer page or the download page at the android filehost website. Is there any way to get around the broken hash checking? My wife is very impatiently awaiting here lollipop upgrade.
Thanks,
Sergio
Hi, i used the tool kit to flash 5.0 on my nexus 10 and i have it running fine but my status bar and soft keys background are black. I noticed in video reviews of 5.0 that they should still be translucent. Any ideas whats up?
geek wana-b said:
I noticed in video reviews of 5.0 that they should still be translucent. Any ideas whats up?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-10/help/lollipop-translucent-decor-t2938952
Trouble flashing my Nexus 10
Hey guys. I am having trouble with flashing my Nexus 10 tablet back to KitKat (due to frustrating wifi issues) after upgrading to Lollipop using the "official" method.
I had read an article on pcadvisor.co.uk about how to downgrade using Minimal ADB and Fastboot, so I started there. Everything was going well up until the point where I was to install the KitKat image.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
erasing 'boot'...
OKAY [ 0.029s]
finished. total time: 0.030s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.034s]
finished. total time: 0.035s
erasing 'recovery'...
OKAY [ 0.027s]
finished. total time: 0.028s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.035s]
finished. total time: 0.035s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.193s]
finished. total time: 0.194s
sending 'bootloader' (1280 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
rebooting into bootloader...
^CTerminate batch job (Y/N)? y
After that, I posted a question to the AndroidCentral forums. There, user rhea turned me on to Wug's Nexus Root Toolkit, thinking that it would help solve my problems. Unfortunately, I got pretty much the same errors. I was using the option to install from a soft-brick or bootloop, which sounded like my problem.
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.029s]
finished. total time: 0.030s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.034s]
finished. total time: 0.035s
erasing 'recovery'...
OKAY [ 0.025s]
finished. total time: 0.027s
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.006s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.193s]
finished. total time: 0.194s
sending 'bootloader' (1280 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.006s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
sending 'boot' (4784 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.009s
rebooting into bootloader...
Any help you guys could give me would be very much appreciated. At this point my Nexus 10 is bricked, which is bumming me out. I am seriously missing reading Flipboard in the morning while I eat breakfast.
I'm not sure if it helps, but I have included a pic of what is on my tablet's screen.
Thanks in advance,
Mike
Nexus 9 disable force encryption not working woth Nexus Root Toolkit v1.9.9
Hi everyone,
I wanted to disable the forced encryption in my Nexus 9 using the Nexus Root Tolkit v1.9.9. I succesfully installed all the drivers and apparently was able to unlock + root my device. However, when I try to disable the forced encryption the tool somehow isn't successful in flashing the new flashboot, and when the device reboots it is still encrypted.
Did anyone come accross this issue?
Thanks very much for your help!!
Nexus 10 stuck at fastboot
In my attempt to flash the new 5.0.2 update to my Nexus 10 it seems to have correctly wiped the device, but then couldn't finish pushing the new update onto it. As of right now, the device will sit at the screen shown below, and boot to the screen shown below no matter if I move to "Recovery Mode" etc. What do you believe I should do to correctly finish flashing the new update?
imgur [dot] com/a/gZNpH
Edit: It seems my problem is similar in nature to that of mdhankins 2 posts above.
stuck at "flashing custom recovery to recovery partition"
title says it all, I've got a N7 2013 Flo, android 4.4.2 KOT49H
I used this toolkit with NO problems whatsoever with my grouper, so I'm not sure what to do here, should I force close the tooklit, reboot tablet and start over or will I brick the device?
Hello,
I have tried to back on Kitkat on my nexus 4 but after flashing bootloader, my nexus doesn't boot.
Steps I follow :
1 - fastboot oem unlock ==> OK
2 - fastboot flash bootloader bootloader-mako-makoz30d.img ==> OK ?
3 - fastboot reboot-booloader ==> KO, smartphone doesn't boot
I have a black screen. When phone is plugged on AC and I press Power + Volume down for a while (15sec), a red LED blink.
Console output :
sending 'bootloader' (2203 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
OKAY [ 0.297s]
finished. total time: 0.391s
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.016s
Any solution ?
Thanks in advance.
try to flash the factory image as a whole don't flash just bootloader and all flash the whole factory image and then try to boot the device
The problem is that my nexus don't boot, so tools like fastboot don't detect it.
I can't follow the procedure to the end
Where did you get this bootloader, and why were you flashing it? A corrupted bootloader flash means it is pretty much over, without physical hardware intervention (which I'm not sure is even possible on this device), it is impossible to recover your device through software because the bootloader was the last line of defence.
Sent from my Nexus 4 using XDA Free mobile app
Hi,
I downloaded bootloader and other stuff on google website.
I give up. I waiting for new Nexus 5.
Thanks all.
Yeah unfortunately there isn't much you can do. Sorry.
Sent from my Nexus 4 using XDA Free mobile app
FIXED
Hi all! Been a member of XDA for a few years now, but only just had the pleasure of becoming a nexus user. Yesterday I decided to install the Android N preview to try it out, but decided I didn't want it on my phone. So when I got home, I wiped the phone and proceeded to flash the factory image, but no matter which image I flash it, it says "error: update package missing system.img". I have tried manually flashing each file in fastboot as I have seen in many threads, but nothing is working. I have tried restoring old TWRP backups and flashing custom ROMs in TWRP, but nothing is working. Help!
This is what the Command Prompt is saying:
sending 'bootloader' (3526 KB)...
OKAY [ 0.106s]
writing 'bootloader'...
OKAY [ 0.206s]
finished. total time: 0.314s
rebooting into bootloader...
OKAY [ 0.118s]
finished. total time: 0.119s
< waiting for device >
sending 'radio' (48600 KB)...
OKAY [ 1.151s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.327s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1733501396 bytes
error: update package missing system.img
Press any key to exit...
Did you download the right image from here?
Are you following THIS guide, TO THE LETTER?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Specifically step 10
irule311 said:
Did you download the right image from here?
Click to expand...
Click to collapse
Yep, straight from the Angler section. I've tried the latest one, as well as a few older ones. Nothing.
Soulfly3 said:
Are you following THIS guide, TO THE LETTER?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Specifically step 10
Click to expand...
Click to collapse
Hi, I followed the steps exactly, before updating my 6P to N developer preview, I had previously flashed the factory image. Thanks!
Unzip it yourself and flash em each manually.
Make sure you have the lastest fastboot tools. Im going to go out on a limb and say yours are out of date
Rxpert said:
Unzip it yourself and flash em each manually.
Make sure you have the lastest fastboot tools. Im going to go out on a limb and say yours are out of date
Click to expand...
Click to collapse
Tried that as well. Everything flashes, except the system.img.
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
Had the same problem when ai first got it.
Wugs toolkit fixed me up!
http://forum.xda-developers.com/nexus-6p/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258493
The logs make me feel like the file you downloaded is corrupted. Check the md5 maybe?
Sent from my Nexus 6P using Tapatalk
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
Probably a corrupt download, did you check the MD5 after downloading?
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
It looks like you are not in the directory with the boot.img, et al. (your post shows no boot.img,, ... ) Make sure you unzipped the image. There are 2 files you need to unzip, the one containing the bootloader and radio. In that unzipped folder will be another zip. Unzip that second folder and you'll see the boot.img, cache.img, et al. The change in to that folder from your terminal or move those files into the folder you created (if following Heisenberg's guide), then proceed.
g4slyness said:
Hi all! Been a member of XDA for a few years now, but only just had the pleasure of becoming a nexus user. Yesterday I decided to install the Android N preview to try it out, but decided I didn't want it on my phone. So when I got home, I wiped the phone and proceeded to flash the factory image, but no matter which image I flash it, it says "error: update package missing system.img". I have tried manually flashing each file in fastboot as I have seen in many threads, but nothing is working. I have tried restoring old TWRP backups and flashing custom ROMs in TWRP, but nothing is working. Help!
This is what the Command Prompt is saying:
sending 'bootloader' (3526 KB)...
OKAY [ 0.106s]
writing 'bootloader'...
OKAY [ 0.206s]
finished. total time: 0.314s
rebooting into bootloader...
OKAY [ 0.118s]
finished. total time: 0.119s
< waiting for device >
sending 'radio' (48600 KB)...
OKAY [ 1.151s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.327s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1733501396 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
I think you are using an old version of fastboot. Update it and try again. Problem was fastboot couldn't allocate enough system ram to hold the whole image or something. In the newer fastboot the file transfer was broken in to several segments.
Maybe try another USB port too won't hurt.
Gytole said:
Had the same problem when ai first got it.
Wugs toolkit fixed me up!
http://forum.xda-developers.com/nexus-6p/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258493
Click to expand...
Click to collapse
Thanks!!! It actually worked. Not sure what was wrong before, seemed as though every file I downloaded off of the google website was corrupted. Cheers!
g4slyness said:
Thanks!!! It actually worked. Not sure what was wrong before, seemed as though every file I downloaded off of the google website was corrupted. Cheers!
Click to expand...
Click to collapse
You're welcome!
Like I said I had the same problem back in November. It ended up being an outdated version of fastboot like others have stated. I coyld flash my friends Moto X Pure but not my Nexus 6P..mit was awful and brain racking. Glad all is good!