[RECOVERY][flounder] TWRP 3.1.1-0 touch recovery [2017-05-19]

[jd1639]

Anyone? I tried to flash a factory image but in the end i got the message that there was no boot.img???
After a reboot i only see the words Google and after that it's again stuck at the flashing teamwin logo????

I can enter the fastboot menu

I would download the twrp recovery image again and flash it in fastboot

Sent from my Nexus 9 using XDA Free mobile app

 

[demkantor]

Anyone? I tried to flash a factory image but in the end i got the message that there was no boot.img???
After a reboot i only see the words Google and after that it's again stuck at the flashing teamwin logo????

I can enter the fastboot menu

Double check md5sum for match
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
fastboot reboot-bootloader
Now select recovery

 

[thebrainkafka]

Where did twrp save backups?

 

[jd1639]

Where did twrp save backups?

/sdcard/BACKUPS/your serial number/

Or look in /data/media/0

Sent from my Nexus 9 using XDA Free mobile app

 

[pantmunu]

Anyone? I tried to flash a factory image but in the end i got the message that there was no boot.img???
After a reboot i only see the words Google and after that it's again stuck at the flashing teamwin logo????

I can enter the fastboot menu

If u flashed your recovery via flashify .. that might happen. Your system is wiped unfortunley. Thats what happened to . Had to flash the rom manually. Or.if u have a backup just reatore it . And flash the recovery via adb

 

[tyea]

I don't have to root to get the recovery to stick do I? I flashed with fast boot, but didn't erase recovery prior to that. Is that my problem for the custom recovery not sticking?

Sent from my Nexus 6 using Tapatalk

 

[USBhost]

ok guys i did some edting to twrp

i fixed the flounder problem
also made it look a bit better

https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery/

 

[jlokos]

If u flashed your recovery via flashify .. that might happen. Your system is wiped unfortunley. Thats what happened to . Had to flash the rom manually. Or.if u have a backup just reatore it . And flash the recovery via adb

I flashed the update today with flashify which was updated yesterday. I successfully flashed TWRP 2.8.2.1 and rebooted to recovery with no issues.

---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------

ok guys i did some edting to twrp

i fixed the flounder problem
also made it look a bit better

https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery/

Excellent. thank you. I'll give it a whirl when I get the chance. This will allow me to flash lollipopollooza without doing any editing.

 

[USBhost]

Excellent. thank you. I'll give it a whirl when I get the chance. This will allow me to flash lollipopollooza without doing any editing.

yep

 

[pantmunu]

I flashed the update today with flashify which was updated yesterday. I successfully flashed TWRP 2.8.2.1 and rebooted to recovery with no issues.

---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------



Excellent. thank you. I'll give it a whirl when I get the chance. This will allow me to flash lollipopollooza without doing any editing.

They might have updated again. And he might have flashed an earlier version . Not sure. But i was on the aosp rom whn that happend to me after flashing via flashify .

 

[jlokos]

They might have updated again. And he might have flashed an earlier version . Not sure. But i was on the aosp rom whn that happend to me after flashing via flashify .

I'm running flashify 1.8; I also updated to the new SuperSU Beta. So, I don't know if either or both might have solved the issue, assuming it was solved as I'm on the stock rom. It might be a question to address with aosp developer. I'll be cautious in updating TWRP with flashify after I flash the aosp rom.

 

[USBhost]

I'm running flashify 1.8; I also updated to the new SuperSU Beta. So, I don't know if either or both might have solved the issue, assuming it was solved as I'm on the stock rom. It might be a question to address with aosp developer. I'll be cautious in updating TWRP with flashify after I flash the aosp rom.

You can also do this

su -c dd if=location of recovery of=/dev/block/platform/sdhci-tegra.3/by-name/SOS

 

[buffal0b1ll]

aromafm doesn't seem to be supported. Are there plans to add?

Sent from my Nexus 9 using XDA Free mobile app

I was wrong about aromafm not working. It works fine. I had forgotten to tick the Theme Setting>Use Aroma File Mangler. @z31s1g

 

[vomer]

Double check md5sum for match
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
fastboot reboot-bootloader
Now select recovery

worked thanks

 

[oRAirwolf]

Thanks for fixing the issue with flashing custom roms @USBhost.

 

[USBhost]

ok guys new version

hopefully fixed the format problem that always encrypts data
and its running the FIRE-ICE kernel R10

https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery/

 

[tyvar1]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind.

Thank you so much for TWRP for the nexus 9 just wondering if you will fix flounder problem

(Using USBHost version atm )

 

[Skid71]

ok guys new version
hopefully fixed the format problem that always encrypts data
and its running the FIRE-ICE kernel R10
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery/

For my own clarification purposes... the linked recovery above is for encryption issues while using Fire-Ice? If this is the case, may as well use it as I would like to try other kernels as well.

 

[USBhost]

For my own clarification purposes... the linked recovery above is for encryption issues while using Fire-Ice? If this is the case, may as well use it as I would like to try other kernels as well.

Well the recovery only needed a ramdisk change
But i thought it would be cool having a custom Kernel in a recovery
So i put it in

But if you guys don't like it then I will use the stock kernel

 

[Skid71]

Well the recovery only needed a ramdisk change
But i thought it would be cool having a custom Kernel in a recovery
So i put it in
But if you guys don't like it then I will use the stock kernel

@USBhost
As a first time Nexus owner, I'm trying to educate myself on fastboot/adb.
I would like to keep everything separate ie; kernel, recovery, etc. Please excuse my ignorance on this.
Can I still use your modified TWRP (device identifier change) if wanting to try stock, fire-ice, and elemental kernels?

Thank you