Database Develop

[Q] WW 10.26.1.7 firmware zip

Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink

Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
Why can't you download an earlier firmware?

schmeggy929 said:
Why can't you download an earlier firmware?
Click to expand...
Click to collapse
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
schmeggy929 said:
i downloaded the asus firmware for 10.14.1.47. extract zip and you get a user.zip. extracted the boot.img. I fastboot erase boot, system, format system, data and cache(as you did)
fastboot -i 0x0B05 flash boot boot.img then
fastboot -i 0x0B05 flash system blob then
fastboot -i 0x0B05 flash system UL-K00C-US-10.14.1.47-user.zip
rebooted back into fastboot and bootloader showed 10.14.1.47 version.
Click to expand...
Click to collapse
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108

Ikkerens said:
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Click to expand...
Click to collapse
you are going to get that along with a few more errors. Wait until it is done. It will take like 10 mins and finish.
when it is done reboot in bootloader and you should see the version change.

schmeggy929 said:
you are going to get that along with a few more errors. Wait until it is done. I will take like 10 mins and finish.
Click to expand...
Click to collapse
You're getting this wrong, it does not do anything. The process immediately quits.

Ikkerens said:
You're getting this wrong, it does not do anything. The process immediately quits.
Click to expand...
Click to collapse
Ok when you get that message do you get a blinking curser?

Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here

lpdunwell said:
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
Click to expand...
Click to collapse
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).

Ikkerens said:
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Click to expand...
Click to collapse
forget what I wrote here. I opened a thread with unbricking instructions. Good luck

lpdunwell said:
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
Click to expand...
Click to collapse
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.

Ikkerens said:
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Click to expand...
Click to collapse
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?

lpdunwell said:
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
Click to expand...
Click to collapse
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)

Ikkerens said:
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Click to expand...
Click to collapse
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.

Sad story. What would have been the safe thing to do, if others wish to root their devices?

Snah001 said:
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Click to expand...
Click to collapse
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)

Ikkerens said:
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Click to expand...
Click to collapse
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.

pelago said:
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Click to expand...
Click to collapse
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Snah001 said:
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
Click to expand...
Click to collapse
Already too late, it has been RMA'd, and then, I had nothing to flash it with.

Ikkerens said:
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Click to expand...
Click to collapse
Well I meant, what should a root user do to try and protect themselves against bricking their device like you did? Is it a matter of making sure that CWM or TWRP is on the device as a recovery partition? And are those available on TF701T yet?

Oh dear. That's a lot gone wrong.
Cwm is available and that works.
It's made by drgravy. I use it in my unbrick tut.
All i can say is, root --> cwm --> backup.
Sent from my GT-I9505 using xda app-developers app

That CWM wouldn't boot for me :/

help me my razr xt890 is not booting

So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !

doud1998 said:
So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !
Click to expand...
Click to collapse
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.

Hazou said:
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.
Click to expand...
Click to collapse
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me

doud1998 said:
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me
Click to expand...
Click to collapse
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.

Hazou said:
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.
Click to expand...
Click to collapse
I'm really sorry to annoy you for that but i don't get what you mean by "section E"

doud1998 said:
I'm really sorry to annoy you for that but i don't get what you mean by "section E"
Click to expand...
Click to collapse
I meant, in my signature under my post u can find within the link INDEX/GUIDE, ALL Things RAZR I under paragraph/ section E a link to all the firmwares available for the Razr I.
But in this case i will post the full link to the firmware site, here.

I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)

i tried to flash recovery_signed but i have the error
Checking fs on partition pds...
E:can't repaire partition pds
E:failed to mount PDS partition

doud1998 said:
I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)
Click to expand...
Click to collapse
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back

Hazou said:
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back
Click to expand...
Click to collapse
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)

+> i don't have any backup and i can't go to recovery , when it turns on it automaticly stuck to the ap fastboot menu

doud1998 said:
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)
Click to expand...
Click to collapse
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:

waj3k said:
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:
Click to expand...
Click to collapse
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?

doud1998 said:
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?
Click to expand...
Click to collapse
I know, I just uploaded Deodexed Retail Great Britain ICS:
Here you go. There should be a download icon at the top.

give me the right access (i'm [email protected])

Sorry, forgot to set it to public, should be fixed now.

so now i have to flash the boot.img or what? i'm not really sure what to do with this zip

You need to flash custom recovery and then you can install a zip.
Here is a tutorial on how to use recovery, if you're unsure.

i can't make works neither cwm nor twrp

doud1998 said:
So here is my problem, after trying to install a custom rom on my razr i, i may have broken something in the system
Click to expand...
Click to collapse
may i ask you what u have exactly done to install your "custom rom"?
1. Bootloader unlocked?
2. Custom Recovery installed?
3. How did you installed your rom?
4. Which custom rom?

Unable to install OTA LRX21O

Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash the OTA LRX21O (I'm on LNX07M) in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??

RandoTheKing said:
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash LRX21O in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
Click to expand...
Click to collapse
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.

akellar said:
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
Click to expand...
Click to collapse
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.

RandoTheKing said:
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
Click to expand...
Click to collapse
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).

Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
well what will you do for future updates? Full wipe?

RandoTheKing said:
well what will you do for future updates? Full wipe?
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)

Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
jj14 said:
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Click to expand...
Click to collapse
Any instructions on how to do that? I'm assuming I can still get the update that way

RandoTheKing said:
Any instructions on how to do that? I'm assuming I can still get the update that way
Click to expand...
Click to collapse
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Edit - flash the cache.img instead of just erasing cache

I had trouble flashing the factory image initially. I kept getting an error so I used this method and it worked perfectly. Hope it helps. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865

So i am root and have done a bit of work on my Nexus 6 (changing system sounds, setting it up and a few other things) If i want to install LRX21O, what is the step by step to do that and after i install it if i do a Nandroid Backup, can i restore the backup on LRX21O? I am currently on LNX07M.

I am curious as well. Also do you happen to have a link to the file to just update.?
EDIT... Found it. Will flash when home
Sent from my Nexus 6 using XDA Free mobile app

jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Click to expand...
Click to collapse
Should that be `fastboot format cache`?

jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
Actually, you should just flash the cache.img

jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
You don't reboot into recovery if you are using fas boot. You boot into boot loader at least that's how I've done it on every Nexus that I've had.
Edit - flash the cache.img instead of just erasing cache
Click to expand...
Click to collapse
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
You can use both commands to first format, then flash the new one it doesn't really matter. I've used both methods
jj14 said:
Actually, you should just flash the cache.img
Click to expand...
Click to collapse

Need help upgrading to 5.1, Tired of flashing all the things.

My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.

Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.

I tried using tge NRT to flash it back to stock but it didn't work.

I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.

http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1

When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...

celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!

Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!

You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.

prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.

rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again

kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.

Nexus 6 stuck at google screen , Need Assistance.

So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you

I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app

faraz90 said:
So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you
Click to expand...
Click to collapse
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.

Evolution_Tech said:
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.
Click to expand...
Click to collapse
gee2012 said:
I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.

faraz90 said:
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.
Click to expand...
Click to collapse
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.

simms22 said:
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.
Click to expand...
Click to collapse
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
If your Android SDK is more than 6 months old, you may need to update it. Google updated fastboot to allow flashing these very large files.

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
Click to expand...
Click to collapse
No, by using fastboot commands.. The location of the images you flash is irrelevant.
faraz90 said:
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
Either there is a problem with the system.img (redownload) or there is a problem with the flash memory on your device.
You could flash a custom recovery and use that to flash a zipped ROM to see.if that makes any difference.

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.

Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.

simms22 said:
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.
Click to expand...
Click to collapse
gee2012 said:
Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.
Click to expand...
Click to collapse
I think he has already used fast boot to flash the system.img

rootSU said:
I think he has already used fast boot to flash the system.img
Click to expand...
Click to collapse
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem

I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052

gee2012 said:
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem
Click to expand...
Click to collapse
Nope. He used the correct commands. There is no correct folder.

Evolution_Tech said:
I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052
Click to expand...
Click to collapse
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks

faraz90 said:
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks
Click to expand...
Click to collapse
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.

Evolution_Tech said:
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.
Click to expand...
Click to collapse
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!

faraz90 said:
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!
Click to expand...
Click to collapse
*ahem*

rootSU said:
*ahem*
Click to expand...
Click to collapse
haha ofcourse thanks alot to you for suggesting that idea

faraz90 said:
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
!
Click to expand...
Click to collapse
Possibly because your Android SDK tools are out of date(specifically fastboot).