Database Users

FRF91 Stock for custom recovery with optional root - From lox at htcpedia

http://htcpedia.com/forum/showthread.php?t=3033
Thank you lox, you truely are an Android ninja...

man you guys work fast..

And it works too. (Like there was any doubt...)

b0dge said:
And it works too. (Like there was any doubt...)
Click to expand...
Click to collapse
Hiya mate, im on build FRF83 at the moment, can i upgrade straight to this build using this link?
Also, whats the order i flash stuff, that link confused me abit.
Im rooted and running a custom recovery, (RA 1.6.2)
Cheers!

jimbob_me said:
Hiya mate, im on build FRF83 at the moment, can i upgrade straight to this build using this link?
Also, whats the order i flash stuff, that link confused me abit.
Im rooted and running a custom recovery, (RA 1.6.2)
Cheers!
Click to expand...
Click to collapse
Yep, just put them both on /sdcard/ and flash away.
It tells you at the end of the post what order to do them in:
The three updates can be flashed at the same time (I mean without rebooting between the flashes), just flash it in this order: base system, root then addons and reboot
Click to expand...
Click to collapse

WTF? What's the diff? Anyone know?

I have uploaded all three files in one zip file : http://rapidshare.com/files/404395384/Froyo_FRF91.zip.html
I enabled trafficshare for everyone, finally I could give something back to the community!

b0dge said:
Yep, just put them both on /sdcard/ and flash away.
It tells you at the end of the post what order to do them in:
Click to expand...
Click to collapse
Just tried this, installation started and then stalled half way through. A few seconds later is aborted. Heres what it said:
E: No space left on device
E: Error writing BOOT
E: Failure at line 72
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted
Is this simply a case of me needing to free up space on my phones memory?
Any help would be wicked.
Jim

I receive the exact same error unfortunately... I've tried going from tock FRF50 as well as Cyanogen 5.0.8 with no avail.
Decided to try fastboot to run "fastboot erase boot" and see if I could get any luck there, but I was met with another problem:
"erasing 'boot'... FAILED (remote: not allowed)"

May I ask what is the function of replacing the boot.img in the root update.zip? Aren't su and Superuser.apk sufficient for root?

I was on FRF85B, invisible root!
I applied the three files in the order suggested, boom it works like a charm.
I see no visible changes, but Froyo rocks!

cmstlist said:
May I ask what is the function of replacing the boot.img in the root update.zip? Aren't su and Superuser.apk sufficient for root?
Click to expand...
Click to collapse
I see recovery-from-boot.p and install-recovery.sh in there, I'm worried about replacing those files with my bootloader still locked.
Can I just manually delete those files from the zip and then install?
kkiran said:
I was on FRF85B, invisible root!
I applied the three files in the order suggested, boom it works like a charm.
I see no visible changes, but Froyo rocks!
Click to expand...
Click to collapse
Can you still see your phone with adb while it's in recovery?

This does not work, it says signature aborted.

kkiran said:
I have uploaded all three files in one zip file : http://rapidshare.com/files/404395384/Froyo_FRF91.zip.html
I enabled trafficshare for everyone, finally I could give something back to the community!
Click to expand...
Click to collapse
Dude, you are awesome!!! I just installed all three updates and all worked perfectly . Again Thanks for the hard work!!!

kkiran said:
I have uploaded all three files in one zip file : http://rapidshare.com/files/404395384/Froyo_FRF91.zip.html
I enabled trafficshare for everyone, finally I could give something back to the community!
Click to expand...
Click to collapse
tks, try it now
edit: works fine.

Thanks!!!! Updated straight away....wouldn't know what to do updating wise without your versions of the Roms!!

I have been having the same problem when installations are flashing boot.img for awhile now. That said, the installation gave me the same error, I flashed the other two files, and it appears to be working okay. The only thing I can't do is use ADB, which isn't as much of a big deal for me.
What I LOVE about this flash is that it's using the Cyanogen kernel which has the audio values tweaked for louder earpiece volume, something that was a huge problem with Froyo. I'm much happier with this fixed now.

Am I understanding this correctly,
I'm running stock unrooted FRF91,
If I flash the second update.zip file I will be rooted and then flash the third update.zip file I will be rocking the cyanogenmod 6.0 kernel?
Eager to try, but a bit apprehensive.

tibere86 said:
Am I understanding this correctly,
I'm running stock unrooted FRF91,
If I flash the second update.zip file I will be rooted and then flash the third update.zip file I will be rocking the cyanogenmod 6.0 kernel?
Eager to try, but a bit apprehensive.
Click to expand...
Click to collapse
Yes, provided you're flashing with a 3rd party recovery like Amon_Ra's or similar.

jimbob_me said:
Just tried this, installation started and then stalled half way through. A few seconds later is aborted. Heres what it said:
E: No space left on device
E: Error writing BOOT
E: Failure at line 72
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted
Is this simply a case of me needing to free up space on my phones memory?
Any help would be wicked.
Jim
Click to expand...
Click to collapse
I get this same error, anyone find a fix?

KRT16O Factory Image now available

For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post

Finally! I'm going to flash this on both my flo and mako. Then, along with my hammerhead, I'll have KitKats everywhere!

Was going to post this too. Just my luck that they release it the day that I'll be out all night and won't be able to update until the weekend. Maybe I'll get the OTA before then.

Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.

Zaphodspeaks said:
For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post
Click to expand...
Click to collapse
The Wifi version doesnt look like its been fully uploaded..
Deb however looks like its all there.. Check in an hour to see if the upload is complete..
The F5 key on my keyboard has taken a turn for the worst! lol

Blockberd said:
Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.
Click to expand...
Click to collapse
Maybe not completed the upload yet?

ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.

ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.

Noticed this as well -- no image.
Blockberd said:
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.
Click to expand...
Click to collapse
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.

jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
They don't work like OTAs because they don't patch the file you have in place, but rather replace the /system partition with the new one. The difference being if you installed some extra files into /system, they would be preserved during an OTA update, but would be gone after a factory image.

jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
Those factory images will reset your device to factory is flashed as told by Google. There are, however, ways to avoid that if you have a stock Android prior to the version you want to flash.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
The question is if someone has closer contact to someone at Google to inform them about that...

Great tip, thanks.
sfhub said:
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
Click to expand...
Click to collapse
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4

jbwray said:
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4
Click to expand...
Click to collapse
You could also go ahead and flash each .img file (except userdata) in bootload with fastboot to the device. That will be my way once the damn factory image is properly uploaded. ;D

sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Well atleast the Binaries are up..
So it wont be long until we will be seeing new Custom Roms, and Kernels..
Those of us that were lucky to get the OTA dont need to worry about the factory images..
I created a TWRP clean stock backup of KRT16O if I need to go back to factory settings
This is NOT, I repeat NOT a flashable zip. Its a Zip of my TWRP backup, minus the Data partition..
Just unzip into your TWRP backup folder.. It will bring your Nexus 7 Flo directly to stock 4.4..(ROOTED) It is not an OTA.
Your SD Card will remain untouched
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip

If any of you want to flash just the update to 4.4, HERE is a link, with directions HERE

sfhub said:
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Apparently calling all bootloaders 3.14 is a mistake they have chosen to propagate from JSS15R when they called the 3.15 bootloader 3.14.
So basically the 4.01 bootloader is named bootloader 3.14 in the archive.

With the stock rom, can I just flash it using a custom recovery?

yanksrock1000 said:
With the stock rom, can I just flash it using a custom recovery?
Click to expand...
Click to collapse
You can flash the OTA (the OTA requires stock JSS15R to be installed) or the update.zip that scrosler put together using custom recovery.
You can't flash the factory image from google in this thread using custom recovery. It was meant to be flashed using fastboot and with your tablet in bootloader.

Update images now available.
EDIT ** I looked at the wrong image... nothing has changed ** please delete.

jbwray said:
EDIT ** I looked at the wrong image... nothing has changed ** please delete.
Click to expand...
Click to collapse
I was in the middle of replying saying I must be blind (or some cache is getting in the way) because I couldn't find the alternate link/download

New OTA break root?

Just got a notification for OTA to 5.0.1. Anyone know if this will break root? And if it will install with CWM custom recovery?

Hello, I tried to install in my WiFi model and rooted and I got and error during the installation, so I'm waiting for the opinion of other users. ?
Sent from my SHIELD Tablet using XDA Free mobile app

I kiddy got it too, I'll wait for the zip file lol.

Ya think it is really better to install from the zip file?
Sent from my SHIELD Tablet using XDA Free mobile app

I'll be the guinea pig

I downloaded the OTA but can't find where is the ota file. Any idea where is it?
Sent from my SHIELD Tablet using XDA Free mobile app

Get an error in cwm . shucks

Does someone can post change log please?

Gilbot said:
Get an error in cwm . shucks
Click to expand...
Click to collapse
Same. My bootloader is locked and tried flashing via cwm and got error. Pls teach me how to update?
Sent from my SHIELD Tablet using XDA Free mobile app

Judge584 said:
Does someone can post change log please?
Click to expand...
Click to collapse
Android Central has the log change. It's bug fixes really.
Also, in this thread a user states that apparently only with the full 5.0.1 can you install it with CWM.
http://forum.xda-developers.com/shi...p-nvidia-shield-tablet-ota-android-5-t2982677
You will lose root and CWM after the reboot but those took about 3 minutes to get back .. easy peasy. I'm now at 5.0.1 on my shield with root and CWM.
Cheers.

Hello aegern,
deletes the full update all the data? can you give me the recovery and root attach files?
Thanks

Gilbot said:
Get an error in cwm . shucks
Click to expand...
Click to collapse
This should help. Let me know if it works:
http://forum.xda-developers.com/shield-tablet/general/5-0-1-ota-rooted-shield-tablets-dl-t2983104

d4m45cuz said:
This should help. Let me know if it works:
http://forum.xda-developers.com/shield-tablet/general/5-0-1-ota-rooted-shield-tablets-dl-t2983104
Click to expand...
Click to collapse
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?

GMrMadrigal said:
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
Click to expand...
Click to collapse
So here's what I did:
Download the full OTA then reboot to CWM (assuming your rooted + recovery) and unmount system partition ( I believe all others were unmounted) and then delete system, data, cache partitions respectively. Then flash the OTA zip followed by latest supersu.
Just tested this method and I have a rooted 5.01 32GB LTE US model working flawlessly. Even managed to take out the top spot in Hwbot Prime for the Shield (woops to newb for links I see lol)

l0ud_sil3nc3 said:
So here's what I did:
Download the full OTA then reboot to CWM (assuming your rooted + recovery) and unmount system partition ( I believe all others were unmounted) and then delete system, data, cache partitions respectively. Then flash the OTA zip followed by latest supersu.
Just tested this method and I have a rooted 5.01 32GB LTE US model working flawlessly. Even managed to take out the top spot in Hwbot Prime for the Shield (woops to newb for links I see lol)
Click to expand...
Click to collapse
I really appreciate your advice but I get the same error
-- Installing: /storage/sdacrd1/lte-full-5.0.1.zip
Finding update package...
Opening update package...
Installing update...
This package is for "shieldtablet" device; this is a "ardbeg".
E:Error in /storage/sdacrd1/lte-full-5.0.1.zip
(Status 7)
Installation aborted.
I've tried with a few zip updates through in xda but nothing. I guess is because the CWM recovery image but Im not an expert on this and cant be sure if flashing the stock recovery will let me make the OTA successfully. But neither i have found the stock recovery image

GMrMadrigal said:
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
Click to expand...
Click to collapse
GMrMadrigal said:
I really appreciate your advice but I get the same error
-- Installing: /storage/sdacrd1/lte-full-5.0.1.zip
Finding update package...
Opening update package...
Installing update...
This package is for "shieldtablet" device; this is a "ardbeg".
E:Error in /storage/sdacrd1/lte-full-5.0.1.zip
(Status 7)
Installation aborted.
I've tried with a few zip updates through in xda but nothing. I guess is because the CWM recovery image but Im not an expert on this and cant be sure if flashing the stock recovery will let me make the OTA successfully. But neither i have found the stock recovery image
Click to expand...
Click to collapse
Look in this thread: [.zip] Nvidia Shield Tablet OTA Android 5.0.1, first page posted by user SeVIIn.
Use that zip file, no issues with it.

l0ud_sil3nc3 said:
Look in this thread: [.zip] Nvidia Shield Tablet OTA Android 5.0.1, first page posted by user SeVIIn.
Use that zip file, no issues with it.
Click to expand...
Click to collapse
Nice, I'm going to download it, and I'll tell if it work! :fingers-crossed:

GMrMadrigal said:
Nice, I'm going to download it, and I'll tell if it work! :fingers-crossed:
Click to expand...
Click to collapse
So, did it work for you? I've tried the file in both this link and the official update and get the same thing with both. I'm still on KK and I can't install either the 5.0 or the 5.01 updates. I get the same "this is an ardbeg" error with any update I try to flash, and I'm flashing the full files, not the incremental updates. In fact, I have two tablets (both lte) and I updated the first one to 5.0 a week ago, no problem, but the new one I just bought, I can't even though I'm using the same files (cwm and update). I'm stumped.
Bah. nm. I went back and reinstalled the recovery from here again, http://forum.xda-developers.com/shi.../recovery-cwm-recovery-nvidia-shield-t2848064. Flashed 5.01 just fine. Not sure where I got the other recovery.

dgjenkins said:
So, did it work for you? I've tried the file in both this link and the official update and get the same thing with both. I'm still on KK and I can't install either the 5.0 or the 5.01 updates. I get the same "this is an ardbeg" error with any update I try to flash, and I'm flashing the full files, not the incremental updates. In fact, I have two tablets (both lte) and I updated the first one to 5.0 a week ago, no problem, but the new one I just bought, I can't even though I'm using the same files (cwm and update). I'm stumped.
Bah. nm. I went back and reinstalled the recovery from here again, http://forum.xda-developers.com/shi.../recovery-cwm-recovery-nvidia-shield-t2848064. Flashed 5.01 just fine. Not sure where I got the other recovery.
Click to expand...
Click to collapse
Hi dgjenkins, sorry answer so late. So, answering you first, not, it did not work for me. I actually did give up, the bad was that I tried so many ways to do it that I freezed the tablet and did not start again. Well, looking out there, I found this amazing video who saved my tablet of bust it again the wall and start from the original firmware.
https://www.youtube.com/watch?v=GsMo1tPlIFU
I did intal the Minimal ADB and Fastboot
Copy the image files in to the Minimal ADB and Fasboot directory c:\Programs Files (x86)\Minimal ADB and Fastboot
Ope Minimal ADB and Fastboot
-Type: fastboot flash recovery recovery.img
-Type: fastboot flash boot boot.img
-Type: fastboot flash system system.img
-Type: fastboot flash userdata userdata.img
-Type: fastboot flash staging blob
-Type: fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
And done . I can now install the updates from the stock firmware. Maybe I will root it again once a stable way to root the shield tablet appear out there. :cyclops:
Happy Holidays and Thanks for the interest! :good:

Nvidia updates definitely trump Android ones. These days, Google is in the habit of pretending that a nexus 5 camera bug is worthy of a new Android version (that was KitKat) or that an update is a great place to break functionality (App Ops, also with KitKat). Anything that's not a minor version with updates you know you want... Avoid on a non Nexus unless you have a great reason for it.
Manufacturers besides Google, see, they do this thing I like to call quality control. They generally release an OS that is ready for the hardware and software*. Crazy, right?
* unless that hardware is, say, the pen

Factory images with January security patch now available

This update is known as 6.0.1 (MMB29S): https://dl.google.com/dl/android/aosp/shamu-mmb29s-factory-fc7b590e.tgz
Anyone want to confirm that we can still use systemless root for this update?

Xplicit84 said:
Anyone want to confirm that we can still use systemless root for this update?
Click to expand...
Click to collapse
why, whats the point? why wouldnt you be able to use systemless root with it?

simms22 said:
why, whats the point? why wouldnt you be able to use systemless root with it?
Click to expand...
Click to collapse
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.

Xplicit84 said:
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.
Click to expand...
Click to collapse
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out

Everything's fine for me.

FYI, the radio.img and bootloader.img are the same as MMB29K, so they don't need to be flashed. Boot.img and cache.img are the same size, but I'll flash them anyway. System.img is a different size, so it definitely needs to be flashed.

Looks like the kernel is the same.
Sent from my Nexus 6 using Tapatalk

anyone having trouble downloading the new system image from the site?

simms22 said:
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out
Click to expand...
Click to collapse
While this is true. These security updates are meant to target thing like the root exploits. So while things may still work don't be surprised if it does start needing updates each time Google pushes a security patch. It's a cat and mouse game that will be played until Google manages to lock it down to the point that it is not worth it to root.

maddoggin said:
anyone having trouble downloading the new system image from the site?
Click to expand...
Click to collapse
The factory image download was very slow. Timed out the first time. Second time it worked OK, but still took about 30 minutes.

Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk

tsongwh said:
Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk
Click to expand...
Click to collapse
I second this too. Thank you in advance

i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.

daimonmustdie said:
i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.
Click to expand...
Click to collapse
Stock w/ systemless root and Elite kernel.
To applying the update I downloaded the factory image from https://developers.google.com/android/nexus/images untar and unzip image-shamu-mmb29s.zip to get at the system.img file. Then did fastboot flash system system.img, just finished booting and and 'upgrading' my apps. It looks like something in boot.img changed too, but everything seems to be running perfectly fine without flashing it; note that I do have a custom kernel installed, so that might have something to do with it.
If you also fastboot flash boot boot.img then you will likely need to go through the root process again to modify the boot.img to allow root to work properly.
Code:
$diff shamu-mmb29k shamu-mmb29s
Binary files shamu-mmb29k/boot.img and shamu-mmb29s/boot.img differ
...
Binary files shamu-mmb29k/recovery.img and shamu-mmb29s/recovery.img differ
Binary files shamu-mmb29k/system.img and shamu-mmb29s/system.img differ

Stock ROM, TWRP
I have followed the instructions and flashed only the system.img..Nexus 6 - Unlocked, Rooted, Stock ROM, TWRP. It appears everything is running well and the Update notification hasn't appeared..this update was constantly appearing in the notification window and was reported as 5.8mb downloaded patch.
Thanks for your help.

New TWRP version.

So I just noticed there's a new TWRP build up for us! Just thought I'd throw this out there, not sure what's different.
https://dl.twrp.me/shamu/

the only change is "Bring back /misc"
you should update if you are using cm14.1, cmupdater can cause bootloop with twrp 3.0.2.0 or older

8zabi said:
you should update if you are using cm14.1, cmupdater can cause bootloop with twrp 3.0.2.0 or older
Click to expand...
Click to collapse
I was struggling with this this morning. I was stuck in Recovery but managed to get back into System by doing a Reboot Bootloader, then Start. Then I downloaded the new TWRP and flashed it, all is well now. Would have been easier if I had access to a computer this morning.

psycho_asylum said:
I was struggling with this this morning. I was stuck in Recovery but managed to get back into System by doing a Reboot Bootloader, then Start. Then I downloaded the new TWRP and flashed it, all is well now. Would have been easier if I had access to a computer this morning.
Click to expand...
Click to collapse
Flashify is usually good for that!
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en

Boot into recovery
Select install
Select near the bottom IMG button
Select IMG file
Select type of IMG ( boot, recovery)
Slide to start once finished reboot to recovery and check version
Reboot to O's
Profit
Sent from my Nexus 6 using XDA Labs

Read several posts about bad download. Before flashing check the size of TWRP version 3.0.2.1. The file size is 11,3 Mb.
https://dl.twrp.me/shamu/

tsjanda said:
Boot into recovery
Select install
Select near the bottom IMG button
Select IMG file
Select type of IMG ( boot, recovery)
Slide to start once finished reboot to recovery and check version
Reboot to O's
Profit
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Put phone into bootloader mode. Hold shift and right click to "Open command window here" where you have ADB and your TWRP file (assuming Windows PC). Type "fastboot flash recovery twrp-3.0.2-1-shamu.img". Easier, quicker, and potentially safer IMO.

Dopamin3 said:
..... "fastboot flash recovery twrp-3.0.2-1-shamu.img". Easier, quicker, and potentially safer IMO.
Click to expand...
Click to collapse
That's the most basic method, but with the app FlashFire you don't need a PC.

NLBeev said:
Read several posts about bad download. Before flashing check the size of TWRP version 3.0.2.1. The file size is 11,3 Mb.
https://dl.twrp.me/shamu/
Click to expand...
Click to collapse
Thank you for this. If you are using Tapatalk latest app it opens the link in its own browser and the download is only 6.92k. Opening in chrome beta and downloading gets the whole file downloaded.
Sent from my Pixel XL using Tapatalk

NLBeev said:
That's the most basic method, but with the app FlashFire you don't need a PC.
Click to expand...
Click to collapse
Depending on version you don't even need FlashFire. TWRP can flash the updated image.

Strephon Alkhalikoi said:
Depending on version you don't even need FlashFire. TWRP can flash the updated image.
Click to expand...
Click to collapse
In this case not possible, because the flashed version of TWRP-recovery was corrupt.

NLBeev said:
In this case not possible, because the flashed version of TWRP-recovery was corrupt.
Click to expand...
Click to collapse
I guess I took your post out of context, since your post didn't mention a corrupt download, but earlier posts did.

Strephon Alkhalikoi said:
I guess I took your post out of context, since your post didn't mention a corrupt download, but earlier posts did.
Click to expand...
Click to collapse
That's imaginable, because I had to edit the post.
I have made a mistake; didn't check the file size. After reboot to recovery, I noticed that a corrupt IMG was flashed.
EDIT
Version 3.0.3-0 available see next post.

TWRP-recovery version 3.0.3-0 for Nexus 6 available.
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img.html

3.1.0-0
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img.html
What's new:
https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/

Installed version 3.1.0-0. With all the changes themes need to be reworked. Also, there are rumblings in the XDA article discussion thread that Aroma does not work on this recovery. I'll have to check that.
EDIT: Aroma working perfectly here, as far as I can tell.

I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.

chaibaby said:
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
Click to expand...
Click to collapse
only one way to know, so try it and report back

wase4711 said:
only one way to know, so try it and report back
Click to expand...
Click to collapse
Will do when I am home later on tonight then report back.

chaibaby said:
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
Click to expand...
Click to collapse
Usually, yes. I would backup up personal data onto PC before trying.