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

[corkiejp]

We can't fix a problem we're not even sure exists. Only way to know is for someone to try it. You seem like the most logical candidate.

Flashed Android N DP2 on my Encrypted Nexus 9 last night, latest TWRP just bootloops. Is there logs for TWRP, somewhere on the device, that I could post here?

 

[Captain_Throwback]

Flashed Android N DP2 on my Encrypted Nexus 9 last night, latest TWRP just bootloops. Is there logs for TWRP, somewhere on the device, that I could post here?

I actually looked into this. It does bootloop, but if you let it keep bootlooping it'll eventually get to a decrypt prompt. So the issue is (obviously) that it can't decrypt. I haven't figured out how to fix that yet.

The only possible solution I've come up with is building TWRP with N source, but that's a lot more difficult than it sounds.

 

[corkiejp]

I actually looked into this. It does bootloop, but if you let it keep bootlooping it'll eventually get to a decrypt prompt. So the issue is (obviously) that it can't decrypt. I haven't figured out how to fix that yet.

The only possible solution I've come up with is building TWRP with N source, but that's a lot more difficult than it sounds.

Eventually got the Prompt for password. My Pin Code didn't work.

Probably not worth while building TWRP with N source until the final release.

 

[sttw1fa]

Didn't know where to post this...but it seems most appropriate here. I've done a good bit of searching and trying fastboot things with no fix so far. Not a noob with adb and fastboot, but I goofed something somewhere.

My N9 bootloops to TWRP 3.0.2-0 constantly (even after a process of wiping/formatting reflashing stock image and recovery). I can get into Fastboot (status shows UNLOCKED). During the boot process (to TWRP), the N9 gives the 'Device is Corrupt, can't be trusted message'. It doesn't ever boot the system.

Originally, the N9 came with April 6.0.1 Marshmallow (April security patch). I then used corkiejp's method of unlocking the bootloader, rooting, and loading ElementalX. Was working great, but wanted some extra few things of a custom ROM.

Went through the process of installing fhem's noobbuilds rom (as it had the May security update), but had an issue with SuperSU (it didn't show up). He suggested to go back to stock and start over......

Was trying to get back to stock on my N9 using this guide Unlock bootloader-Flash Stock

But, even after following the steps line by line (twice now), I only get a bootloop to TWRP 3.0.2-0, but, can get to fastboot screen.

Any help/ideas greatly appreciated.

 

[corkiejp]

Was trying to get back to stock on my N9 using this guide Unlock bootloader-Flash Stock

But, even after following the steps line by line (twice now), I only get a bootloop to TWRP 3.0.2-0, but, can get to fastboot screen.

Any help/ideas greatly appreciated.

If your still seeing TWRP, you haven't successfully flashed a fully stock image. As you can get to fastboot/bootloader, you could use Nexus Root Toolkit to flash the factory image, from it's soft brick/boot-loop tool.

 

[tetsuhito]

hi evry oneim' looking for some help

Since i update my N9 to Mob30g

Twrp won't work correctly

I'can't instal 3.0.2.0, the only on i can use is 3.0.0.0

I'm try to root with the su sytemless and Elemental
it's say done but in the parameters there's no elemental
and Su won't work

I also try a factory reset from twrp, say done succesfully
but when i reboot the N9 it was not reset.

Any Idea ?

thanks

 

[montbazon]

I've been using flounder version in my nexus 9 LTE, all work fine but only one thing. That's when using TWRP to make OTAs, it will get an error message about this is a flounder devices but flouder_lte are needed.
The log is here

I:operation_start: 'OpenRecoveryScript'
Running Recovery Commands
I:command is: 'install'
I:value is: '@/cache/recovery/block.map'
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
I:Installing mapped zip file '/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
sysutil: mmapped 260 ranges
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
sysutil: mmapped 260 ranges
[B]script aborted: This package is for "flounder_lte" devices; this is a "flounder".[/B]
[B]This package is for "flounder_lte" devices; this is a "flounder".[/B]
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '@/cache/recovery/block.map'
Done processing script file

I don't know whether I did the right thing and flashed the right recovery image. https://twrp.me/devices/htcnexus9.html?

Sorry could you let me know how you do solve this problem?
Actually I'm with you. My N9 has mobile. And TWRP for N9 rejects my command just like you.
Could we ask to someone? or we need to keep our device all stock?
I'm just using stock rom, twrp and ice and fire kernel.

 

[NovaSlim]

Hi, I succesfully unlocked my flounder and flashed the latest twrp, however when I reboot into recovery(either from the bootloader menu or with adb fastboot recovery it shows me the "no command" window and nothing happens, what am I doing wrong?

nvm, I tried again and it worked this time.

 

[corkiejp]

@NovaSlim

Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.

Quoted from the TWRP site, where you downloaded from. TWRP needs to be boot first after flashing.

 

[PieceKeepr]

I just recently got a Nexus 9 and I have been trying to figure out exactly what I need to back up in order to do a full restore in the event that I need to. Maybe I'm not searching the right terms but can't find any documentation about it. I'm pretty sure I don't need vendor and vendor image as long as the ROM I would restore is built for my current image. I'm not sure about system image though. On my phone I back up system, data and boot but the Nexus has system and system image so I'm not sure if I need both.

Any help with understanding what the various images contain and what I need for a usable backup would be appreciated.

Sent from my Nexus 9 using Tapatalk

 

[DowntownRDB]

I just recently got a Nexus 9 and I have been trying to figure out exactly what I need to back up in order to do a full restore in the event that I need to. Maybe I'm not searching the right terms but can't find any documentation about it. I'm pretty sure I don't need vendor and vendor image as long as the ROM I would restore is built for my current image. I'm not sure about system image though. On my phone I back up system, data and boot but the Nexus has system and system image so I'm not sure if I need both.

Any help with understanding what the various images contain and what I need for a usable backup would be appreciated.

Sent from my Nexus 9 using Tapatalk

@PieceKeepr On all my tablets I only back up system, data and boot. I do not back-up cache, recovery or vendor. Several people in this thread have had restoration failed with unable to mount vendor partition which is why I do not back-up vendor in TWRP. However, I do keep a copy of latest vendor zip on the tablet just in case I need it sometime. Hope this information is helpful.

 

[placebo_domingo]

I actually looked into this. It does bootloop, but if you let it keep bootlooping it'll eventually get to a decrypt prompt. So the issue is (obviously) that it can't decrypt. I haven't figured out how to fix that yet.

The only possible solution I've come up with is building TWRP with N source, but that's a lot more difficult than it sounds.

Would formatting userdata in fastboot make it possible to flash? I'm going on the belief that 'fastboot format userdata' will decrypt.

 

[Captain_Throwback]

Would formatting userdata in fastboot make it possible to flash? I'm going on the belief that 'fastboot format userdata' will decrypt.

Even if that works, it'll just re-encrypt when you boot into Android (unless you patch the boot.img to prevent it). In which case, you can just wait until TWRP stops looping and finally gets to the prompt, cancel the decryption prompt and Format Data/Wipe Encryption in TWRP. So I'm not sure how that would help.

 

[corkiejp]

The only possible solution I've come up with is building TWRP with N source, but that's a lot more difficult than it sounds.

Probably not worth while building TWRP with N source until the final release.

Will you now be building TWRP for the Nexus 9 encrypted? With Android Nougat near completion.

 

[Captain_Throwback]

Will you now be building TWRP for the Nexus 9 encrypted? With Android Nougat near completion.

N source won't be merged into TWRP until Nougat is released. And then I'm sure it'll take @Dees_Troy a while to merge in the changes. So be patient - it'll come.

 

[placebo_domingo]

Even if that works, it'll just re-encrypt when you boot into Android (unless you patch the boot.img to prevent it). In which case, you can just wait until TWRP stops looping and finally gets to the prompt, cancel the decryption prompt and Format Data/Wipe Encryption in TWRP. So I'm not sure how that would help.

I flashed a modified boot image then did a data format, then flashed twrp. I got twrp to load without bootloops!.. but I also managed to blow away the OS. LOL.

Learn by destroying.

 

[nanaandoh]

I flashed a modified boot image then did a data format, then flashed twrp. I got twrp to load without bootloops!.. but I also managed to blow away the OS. LOL.

Learn by destroying.

Where could I find the modified boot image?

 

[corkiejp]

Where could I find the modified boot image?

If you root the device, supersu will modify the boot image to enable decryption.

 

[thebrainkafka]

Is there a New Version supporting Android N?

 

[Captain_Throwback]

Is there a New Version supporting Android N?

Yes.