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

frov

Senior Member
Dec 31, 2014
424
186
73
Tilburg
Upgraded to Dec 2016

I was a bit anxious to root my new 2nd hand N9 (I have quite some other, rooted devices). I read on it being encrypted and so. So after factory reset and some use I flashed in the latest stock image of October and went forward from there: I took Chainfire auto-root and used that to get to root level. With that I could run the TWRP app and flash in 3020-1. I rebooted imm. into recovery and I was happy to see the familiar entry screen of the latest TWRP. So all is well on the N9 and all root apps run OK, like AdAway (systemless). The End :)
Now it was time to upgrade the Nexus 9 to the December image of 7.1.1. Making some notes here on this successful action.
First I made a backup of the important apps with TitaniumBackup and copied these files over to the (Windows) PC.
I DL-ed the image file from https://developers.google.com/android/nexus/images, and got file volantis-nmf26f-factory-dcb1615a.zip.
I also updated the Android SDK on the PC to make sure I have the latest platform-tools, like adb and fastboot: SDK-Manager and run it as administrator:
tools/Android SDK Tools: 25.2.4
tools/Android SDK Platform-tools: 25.0.3
As I also use TotalCommander and the ADB plugin in there, I made sure that plugin is also the latest: http://www.totalcmd.net/plugring/android_adb.html
Connect the N9 to the PC over USB.
I used the ADB plugin to reboot the Nexus9 to bootloader: ADB Plugin --> Power --> Bootloader
The N9 then comes into the basic screen of the bootloader. There is seen that it is (of course) still Unlocked.
On the PC I extract the DL-ed zip file into the c:\Program Files (x86)\Android\android-sdk\platform-tools directory. This is only so that the fastboot command is found.
On the PC I then opened a CMD shell as administrator and went into the platform-tools dir.
I ran the bat file called flash-all.bat. That takes some minutes to flash over all partitions.
The N9 reboots and I enter all data for my account. The N9 runs again, but now 7.1.1 Dec 2016 :eek:

Then I took ChainFire's Autoroot tool in CF-Auto-Root-flounder-volantis-nexus9.zip and ran that as follows:
I extracted the zip file in some dir. I saw it came with its own platform-tools like fastboot, but I wanted it to use the latest ones in c:\Program Files (x86)\Android\android-sdk\platform-tools.
So, in the platform-tools dir, c:\Program Files (x86)\Android\android-sdk\platform-tools, I created a "tools" dir similar as what the bat file root-windows.bat expects.
In that tools dir I placed the files from the platform-tools dir: AdbWinApi.dll, AdbWinUsbApi.dll, fastboot-windows.exe.
I also removed the 'OEM unlock' section in the bat file as my N9 was already totally unlocked and so.
So effectively the only real line left over in the bat file was this one: tools\fastboot-windows.exe boot image\CF-Auto-Root-flounder-volantis-nexus9.img
In a CMD shell (as administrator) I ran that bat file and it made the N9 be flashed and reboot into that image: it shows a pirate Android figure and does it magic.
It then reboots once or twice and comes back into Android. Now with root :eek:

I then uploaded the latest TWRP image in twrp-3.0.2-1-flounder.img to the N9 and used the new TWRP tool for flashing that into Recovery:
https://play.google.com/store/apps/details?id=me.twrp.twrpapp
I used the ADB plugin in TotalCommander to boot the N9 into Recovery: ADB --> Power --> Recovery
It then reboots into the familiar TWRP Recovery tool :eek:

I used that to flash in the latest SuperSU: SR1-SuperSU-v2.79-SR1-20161221223537.zip
I still wiped cache and so and rebooted into system.
So that again took a bit of time, but then it booted into 7.1.1.
Copied over all TitaniumBackup files to the N9.
Installed TitaniumBackup from the PlayStore and used that to restore all apps.
That is it :D
 
  • Like
Reactions: dmantilal

DowntownRDB

Senior Member
Dec 13, 2010
762
515
0
Good morning all. Has anybody tried a restore using the new TWRP 3.1.0-0 yet? I'm trying one now but seems to be taking a super long time which is what prompted me to post here. 3.1 installed without issue and made a back-up without issue but I've never seen it take this long to restore a back-up.
 

Bryanx86

Senior Member
Apr 8, 2016
769
328
0
RockNRoll
Now it was time to upgrade the Nexus 9 to the December image of 7.1.1. Making some notes here on this successful action.
First I made a backup of the important apps with TitaniumBackup and copied these files over to the (Windows) PC.
I DL-ed the image file from https://developers.google.com/android/nexus/images, and got file volantis-nmf26f-factory-dcb1615a.zip.
I also updated the Android SDK on the PC to make sure I have the latest platform-tools, like adb and fastboot: SDK-Manager and run it as administrator:
tools/Android SDK Tools: 25.2.4
tools/Android SDK Platform-tools: 25.0.3
As I also use TotalCommander and the ADB plugin in there, I made sure that plugin is also the latest: http://www.totalcmd.net/plugring/android_adb.html
Connect the N9 to the PC over USB.
I used the ADB plugin to reboot the Nexus9 to bootloader: ADB Plugin --> Power --> Bootloader
The N9 then comes into the basic screen of the bootloader. There is seen that it is (of course) still Unlocked.
On the PC I extract the DL-ed zip file into the c:\Program Files (x86)\Android\android-sdk\platform-tools directory. This is only so that the fastboot command is found.
On the PC I then opened a CMD shell as administrator and went into the platform-tools dir.
I ran the bat file called flash-all.bat. That takes some minutes to flash over all partitions.
The N9 reboots and I enter all data for my account. The N9 runs again, but now 7.1.1 Dec 2016 :eek:

Then I took ChainFire's Autoroot tool in CF-Auto-Root-flounder-volantis-nexus9.zip and ran that as follows:
I extracted the zip file in some dir. I saw it came with its own platform-tools like fastboot, but I wanted it to use the latest ones in c:\Program Files (x86)\Android\android-sdk\platform-tools.
So, in the platform-tools dir, c:\Program Files (x86)\Android\android-sdk\platform-tools, I created a "tools" dir similar as what the bat file root-windows.bat expects.
In that tools dir I placed the files from the platform-tools dir: AdbWinApi.dll, AdbWinUsbApi.dll, fastboot-windows.exe.
I also removed the 'OEM unlock' section in the bat file as my N9 was already totally unlocked and so.
So effectively the only real line left over in the bat file was this one: tools\fastboot-windows.exe boot image\CF-Auto-Root-flounder-volantis-nexus9.img
In a CMD shell (as administrator) I ran that bat file and it made the N9 be flashed and reboot into that image: it shows a pirate Android figure and does it magic.
It then reboots once or twice and comes back into Android. Now with root :eek:

I then uploaded the latest TWRP image in twrp-3.0.2-1-flounder.img to the N9 and used the new TWRP tool for flashing that into Recovery:
https://play.google.com/store/apps/details?id=me.twrp.twrpapp
I used the ADB plugin in TotalCommander to boot the N9 into Recovery: ADB --> Power --> Recovery
It then reboots into the familiar TWRP Recovery tool :eek:

I used that to flash in the latest SuperSU: SR1-SuperSU-v2.79-SR1-20161221223537.zip
I still wiped cache and so and rebooted into system.
So that again took a bit of time, but then it booted into 7.1.1.
Copied over all TitaniumBackup files to the N9.
Installed TitaniumBackup from the PlayStore and used that to restore all apps.
That is it :D
You describe very well
 
Last edited:

_litz

Senior Member
Oct 29, 2011
594
268
0
Alpharetta, GA
Fails on a fresh/factory reset N9 w/latest (June) update.

Asks for decryption password, like before ... so something's changed and the "decryption" fixes no longer work.
 

dictionary

Senior Member
Dec 3, 2009
4,509
1,562
0
Fails on a fresh/factory reset N9 w/latest (June) update.

Asks for decryption password, like before ... so something's changed and the "decryption" fixes no longer work.
Hmm? If it's a fresh factory reset device, you'll need to decrypt it again with twrp. You'll lose all your data on the device though. Just press cancel, then go to wipe. Then advanced, then wipe data. It'll ask you to type yes. Once done, you're decrypted. Then load up one of the files that removes encryption (while still in twrp) and flash it. Tada
 

_litz

Senior Member
Oct 29, 2011
594
268
0
Alpharetta, GA
Hmm? If it's a fresh factory reset device, you'll need to decrypt it again with twrp. You'll lose all your data on the device though. Just press cancel, then go to wipe. Then advanced, then wipe data. It'll ask you to type yes. Once done, you're decrypted. Then load up one of the files that removes encryption (while still in twrp) and flash it. Tada
Actually, after some experimentation, I found using the PIN as the password worked too ...
 
  • Like
Reactions: nsfgp and Kandydish

Gold Ribbed

Senior Member
Sep 28, 2014
357
71
58
Not sure what has happened but after using twrp for ages something has gone wrong. Wipe, factory reset and restore functions will not work. Tried restoring latest Google stock and flashing twrp again but nothing changes. Any ideas what the problem is please?
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone