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

[demkantor]

Best guess is a bad download of twrp, check md5sum
Otherwise post all input/output from cmd/terminal

 

[ericplatham]

Hey everyone!

Cannot boot into TWRP for some reason on my Nexus 9. Running stock ROM, USBhost Fire and Ice kernel. Stock recovery works without a hiccup, but TWRP is just stuck at the bootlogo. Any guesses?

It worked yesterday, perfectly fine. I haven't made any changes to the system since yesterday, so I am out of guesses why this is happening now.

Tried:

1. fastboot erase recovery and flash twrp on top = failed
2. fastboot erase recovery and flash stock recovery = success
3. flashing twrp on top of solution 2 = fail

deleted TWRP folder with all the settings, still fails.

I've got the same issue (stuck on Teamwin boot logo)... Same setup too. Stock Rom, Fire/Ice 9.7
It worked fine before I loaded up 9.7

Haven't had a chance to troubleshoot this though since I am at the office

 

[Nikki1993]

Best guess is a bad download of twrp, check md5sum
Otherwise post all input/output from cmd/terminal

I haven't updated TWRP since 2.8.7.0, so it's not a bad download. It just stopped working out of the blue. Presumably, have something to do with the kernel, maybe? I'll poke USBhost.

---------- Post added at 07:56 PM ---------- Previous post was at 07:10 PM ----------

Went ahead and wiped everything:

• System
• Cache
• Boot
• Vendor
• Recovery

reflashed bootloader and flashed twrp alongside, boot, cache and vendor, still loops at TWRP logo... what in the world has happened...

---------- Post added at 08:03 PM ---------- Previous post was at 07:56 PM ----------

Went ahead and flashed twrp 2.8.6 instead of 2.8.7 and after a while (nearly a minute) it booted into TWRP recovery... flashing twrp 2.8.7 and stuck at logo again... what happened? I swear everything worked just yesterday and I haven't done anything to my system other than flashing custom kernel update from Fire/Ice which has never caused any recovery shenanigans...

---------- Post added at 08:10 PM ---------- Previous post was at 08:03 PM ----------

I have no idea what happened but fastboot -w fixed it. Can now properly boot into twrp 2.8.7.0 which is again weird cause I haven't touched anything regarding TWRP or system files.

 

[jupppo]

I have the same issue. I am running CM 12.1. Sometimes I get the fallen Android and sometimes it boots into TWRP. But it takes ages then.

 

[brotbuexe]

Anyone tried 6.0? My boot encryption pin does not work in TWRP 2.8.7.0, so no /data mount.
Aside this it works for flashing kernel or supersu to /system...

 

[v12xke]

Same here... LTE version, I have no boot pin set (or swipe) and the default TWRP password is not working, so I can't use install to see or run any files I've put on the root. Probably will have to unencrypt and try again.

 

[brotbuexe]

Same here... LTE version, I have no boot pin set (or swipe) and the default TWRP password is not working, so I can't use install to see or run any files I've put on the root. Probably will have to unencrypt and try again.

you can still use adb sideload in TWRP (its in advanced, start it there when connected, and then "adb sideload update.zip" on the pc).
If it shows "waiting for device" check the device on the pc in device manager (if using windows), it's possible that you have to select the google usb driver again for this type of connection.

And I guess USB OTG should work too.

 

[brotbuexe]

using format data in twrp and reboot recovery works, but after booting in system and going back to recovery it is the same.

 

[Sviborg2241]

Think we should wait for the updated TWRP. Tried to flash it over fresh Marshmallow and got that damn password encryption on start. Formatted data and ended up in bootloop - further attempts to re-flash everything led to the warning screen about corrupted device and I started getting bootloops after almost every reboot. Flashing M image even without TWRP did nothing, had to re-flash latest Lollipop first and then download an OTA to get Marshmallow working. Ugh the only thing I need is to upload the adaway-modified hosts file, and it seems like the only way to get /system mounted on full stock is to get a custom recovery.

 

[v12xke]

Well, I am up and running on the N9 LTE. Wug Fresh came out with a modified boot.img making unencrypting very easy using the flash-stock and no-force encrypt. As soon as it booted I installed TWRP and flashed Elemental X 4.0 and then SU 2.49 Beta. Once rooted I used Titanium Backup to restore all my apps. Even used the backup of the Google App to restore all my shortcuts so all my icons are where they used to be in 5.1.1. Only problem is upon booting I get the weird boot msg below "Your Device Is Corrupt...." others have been getting. TWRP is working normally and allowed me to make a full backup. Other than a 10 sec. delay in boot, the tablet is working perfectly.
https://support.google.com/nexus/answer/6185381?hl=en

 

[brotbuexe]

I made a comment on the github issue page: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/500
If anyone finds interesting stuff about the encrpytion issue, maybe report it there too.

 

[v12xke]

Running 6.0 unencrypted on N9 until sorted. No TWRP issues including flashing, backup/restore, etc. Focusing on the more popular Nexus forums (6,5) for an emerging fix, but nothing yet.

I made a comment on the github issue page: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/500
If anyone finds interesting stuff about the encrpytion issue, maybe report it there too.

wut?

 

[Ltdrev]

Issue here too with being unable to mount anything but eh if sideload works!
wtfn

*edit*
No encryption in my case just "blank" at twrp boot prompt and then adb sideload & ignore errors...

Yeah sideloaded elementalx 4.01 and supersu beta 2.52, works.

 

[Manu270891]

Issue here too with being unable to mount anything but eh if sideload works!
wtfn

*edit*
No encryption in my case just "blank" at twrp boot prompt and then adb sideload & ignore errors...

Yeah sideloaded elementalx 4.01 and supersu beta 2.52, works.

I can't use ADB Sideload. It gets stuck at "Starting ADB sideload feature..." and I can't install TWRP and SuperSU on Android 6 because of the encryption bug. How can I get the ADB Sideload feature working? Thanks!

 

[Ltdrev]

I got into fastboot flashed recovery (twrp in my case) then booted into it> advanced> adb sideload, the errors and "starting adb sideload" .
We're there! Yes yes!
From your desktop terminal window then;
adb sideload "path to file" ,
Command should work!
Assuming you have adb and working properly.

 

[fhem]

I can't use ADB Sideload. It gets stuck at "Starting ADB sideload feature..." and I can't install TWRP and SuperSU on Android 6 because of the encryption bug. How can I get the ADB Sideload feature working? Thanks!

Probably need to update your adb version Need v1.0.32

 

[adrok76]

\hi, could someone advise me what I should do, I have fresh M images installed and have flashed twrp, should I hit cancel when it asks for a password? last time I entered default_password and data corrupted, had to reflash stock

 

[WhammyDroid]

Anyone tried 6.0? My boot encryption pin does not work in TWRP 2.8.7.0, so no /data mount.
Aside this it works for flashing kernel or supersu to /system...

I am seeing the same thing. I have even tried a factory reset and re-encrypting the data partition.

TWRP still will not decrypt the partition.

Edit: BTW, who's the developer supporting the device? @Dees_Troy, is this you?

 

[Captain_Throwback]

USBhost's TWRP builds are more stable, faster than this official TWRP with an old kernel......This really lags a lot

Sent from Nexus 9

Then @USBhost should submit the changes to gerrit so we can all benefit .

---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------

I am seeing the same thing. I have even tried a factory reset and re-encrypting the data partition.

TWRP still will not decrypt the partition.

Edit: BTW, who's the developer supporting the device? @Dees_Troy, is this you?

It is @Dees_Troy, who I know has been diligently working on trying to figure this out. In the meantime, patience is in order. That, or don't encrypt the device.

 

[v12xke]

While waiting for the M compatible version of TWRP to come out, I noticed TWRP backups using compression have tripled or quadrupled in time on the N9 since running M vs. L. I'm unencrypted and a backup with compression takes 35-40 minutes. (2.9 GB), while uncompressed takes about 10 minutes (5.76 GB). Looking in the recovery log file the only thing I found unusual was the line TW_INCLUDE_Crypto :=true (which I am not). By contrast the N6 takes about 7 minutes to backup a similar size image compressed. Average backup rate for files systems is 2 MB/sec for the N9 vs. 12 MB/sec on the N6. I don't know why this is but I thought it was important to note, and I haven't read of anyone else testing backup times. Next time you run a compressed backup report back and let's compare times.