yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Android-Andi:
There might be still missing sepolicy for that to work, but I am sure you'll test and tell if it works now with my TWRP on latest lineageos13
[Samsung Galaxy Nexus] nayiZ:
I can tell: The update doesn't work in a automatic fashion with encryption enabled.

If you restart from lineageos (prompt) to update: TWRP is starting and prompting for the decryption-pass. Give pass and TWRP decrypt+mounts the data-partition correct. :good: Then TWRP just lands in the main menu :confused:

From the log this is a red entry at this point:

Error installing zip file '@/cache/recovery/block.map'

From the main menu I can start the update manually. Need to hit 'install' in TWRP and navigate to the folder

/data/data/org.lineageos.updater/app_updates

here is the zip located downloaded via the lineagos updater...

The update then works as intended!
[Samsung Galaxy Nexus] hga89:
Although I have not checked for the error message, this is my experience as well.
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=8437574]nayiZ[/MENTION] as a workaround you could set selinux to permissive right before the update. It should install fine now if sepolicy is the issue ATM.

You got a dmesg?
[Samsung Galaxy Nexus] osm0sis:
nayiZ | Ziyan ? :confused:
[Samsung Galaxy Nexus] Android-Andi:
Nope
[Samsung Galaxy Nexus] nailyk:
Just asked on #twrp and it is something known.

We should try to include https://gerrit.omnirom.org/#/c/22389/ . Thanks [MENTION=2605798]nkk71[/MENTION] for pointing.
[Samsung Galaxy Nexus] Android-Andi:
Thanks, I'll update in the evening. Just busy on Ooooooooooo XD
[Samsung Galaxy Nexus] nailyk:
:p first lineage oreo device: maguro!

My bad link is not good, it is to workaround the same problem but with the wipe command.

From [MENTION=912474]Dees_Troy[/MENTION] & [MENTION=2605798]nkk71[/MENTION] talk twrp don't read anymore /cache/commands or /misc after the decrypt prompt.

Looks like they would set it up like this because there are different way to implement the wipe while encrypted.
[Samsung Galaxy Nexus] nkk71:
Yeah that patch is mostly for wiping the device, if you simply want to allow/run ors scripts after the decrypt prompt, you can try changing:

https://github.com/omnirom/android_bootable_recovery/blob/android-7.1/twrp.cpp#L301

from

if (
DataManager::GetIntValue(TW_IS_ENCRYPTED) == 0
&&
TWFunc::Path_Exists(SCRIPT_FILE_TMP) || TWFunc::Path_Exists(SCRIPT_FILE_CACHE))
) {

to

if (
(DataManager::GetIntValue(TW_IS_ENCRYPTED) == 0 || DataManager::GetIntValue(TW_IS_DECRYPTED) == 1)
&&
(TWFunc::Path_Exists(SCRIPT_FILE_TMP) || TWFunc::Path_Exists(SCRIPT_FILE_CACHE))
) {

though as Dees_Troy said, it was a design decision, and I'm not aware of the full details.
[Samsung Galaxy Nexus] nailyk:
Awesome! Just think about it and your already write the patch :)

Looks good, I remember the 12.1 time, if you fail at the first decrypt prompt, script was launched before the 2nd attempt.

Thanks, will take a look at it.
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=6979267]nailyk[/MENTION] I have tried to contact Dees Troy without luck. The Omni7 trees are fine now, twrp decryption support merged. He can now switch to them if he likes. I am not on IRC, maybe you can tell him if you are on again there. To much stuff changed, would be a pain doing it over twrp Gerrit again.

He can close https://github.com/TeamWin/android_device_samsung_maguro/issues/1 after that
[Samsung Galaxy Nexus] Android-Andi:
https://gerrit.omnirom.org/25015

Compiled on Android 7 Source the recovery.img is to big to attach it here, uploaded to androidfilehost.
[Samsung Galaxy Nexus] osm0sis:
IRC is pretty much the only way to reach him.
[Samsung Galaxy Nexus] nailyk:
I included omni change about decryption long time ago but totally forget to publish build :s

Some changes are included into this twrp:

repopick 22565 # twrp Adopted Storage: Add support for mixed mode sdcards
repopick 24669 # twrp disable twrp app
repopick 25015 # twrp OTA encrypted workaround
[Samsung Galaxy Nexus] hga89:
Thank you! Will try as soon as the next OS update is published.
[Samsung Galaxy Nexus] hga89:
Just installed this update of TWRP but the phone cannot boot into recovery. I reverted to the drop from August 16th.
[Samsung Galaxy Nexus] magur0:
Same for me. This build from [MENTION=6979267]nailyk[/MENTION] dated 2017-08-28 is not booting (maguro of course ;))

Meanwhile I will stay with the latest release (2017-08-16) from [MENTION=5153662]Android-Andi[/MENTION]: https://xdaforums.com/showpost.php?p=73421863&postcount=2160

The last bug I can remember in this release is that the OTA-Update can't be auto-flashed in twrp....
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=8463548]magur0[/MENTION] on last TWRP I added a change in TWRP which might solve the OTA update
[Samsung Galaxy Nexus] MrFlashGame:
Hey guys,

I think I've found a bug in the latest official TWRP 3.1.1 build: When I try to change the file system of cache to f2fs I always get ERROR 255. Every other FS changes fine and without error. I have tested this with several ROMs (Unlegacy-Android7, LOS 13) but none of them did work (I tried even without ROM installed and I still get this error). I have tested it with 3.1.1 and no other version, but I'm sure it used to work with previous TWRP versions. I attached the TWRP and Kernel log would be really nice if a dev could look into this. :)

Greetings, Nils
[Samsung Galaxy Nexus] bamtan2:
It is good to report this. But please note that /cache is not used, and f2fs is not recommended. If I recall correctly, ziyan has said that only /data supports f2fs at all, but ext4 is preferred.
[Samsung Galaxy Nexus] nkk71:
Not much to look at, your /cache partition is 61MB and mkfs.f2fs is expecting at least a 100MB partitition: Error: Min volume size supported is 104857600
[Samsung Galaxy Nexus] hga89:
OK, the same version of TWRP I reverted to.
[Samsung Galaxy Nexus] osm0sis:
Definitely working great for OTAs unencrypted. :good: :)
[Samsung Galaxy Nexus] nailyk:
dunno if it is still useful:

adb shell mount | grep "f2fs\|dm-"
/dev/block/mmcblk0p11 on /cache type f2fs (rw,seclabel,nosuid,nodev,noatime,background_gc=on,discard,user_xattr,inline_xattr,active_logs=6)
/dev/block/dm-0 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,nomblk_io_submit,data=ordered)
adb shell getprop ro.modversion
14.1-20170804-nailyk-maguro

on 13.1 I was f2fs formatted on data too.

No problem so far.

Your log report:

Error: Min volume size supported is 104857600

so it is probably a partition/fs size problem.
[Samsung Galaxy Nexus] magur0:
yea, I missed it! But I downloaded & flashed it already...

...now I'm trying to do a OTA encrypted Update from LOS13-20170819-nightly straight forward to LOS13-20170902-nightly.. stay tuned! :fingers-crossed:

-> No luck. OTA doesn't get auto-installed.

Running Recovery Commands
Error installing zip file '@/cache/recovery/block.map'
Done processing script file

Need to hit 'Install Zip' and move to Folder: /data/data/org.lineageos.updater/app_updates and select my OTA-Zip

[MENTION=5153662]Android-Andi[/MENTION] : I think it's time to move on to a new Thread? Something like [RECOVERY] TWRP 3.1.1-1 touch recovery (decryption working)
[Samsung Galaxy Nexus] osm0sis:
No need for another thread, this is the official thread (albeit the title isn't updated since Dees took out the DevDB variables when it wasn't being maintained), and these changes will get rolled into the next official build. :good:
[Samsung Galaxy Nexus] magur0:
This thread only mentions maguro... but [MENTION=5153662]Android-Andi[/MENTION] also feeds toro

Anyway. Would be good enough to edit the first post and link the most recent version... :good:
[Samsung Galaxy Nexus] LibertyMonger:
Guy's, I'm on an old version of TWRP v2.7.0.0 and having a problem fastboot flashing recovery to the latest. I don't have the option to flash from recovery since I am not on at least v2.8.6 so I am not sure what I'm doing wrong. I am in fastboot mode and it just says "waiting for device"

I normally use the HTC fastboot for my HTC devices but tried to use my original adb folder and neither is working. Does someone know of a Zip file? Thanks. It's been so long since I turned on my maguro

---------- Post added at 06:12 PM ---------- Previous post was at 06:02 PM ----------

I think I got it done with the app.

***EDIT The TWRP app did not work so now I have no recovery. guess I will keep trying.
[Samsung Galaxy Nexus] bamtan2:
I never remember how to do stuff from the command line. Not only do the drivers get screwed up, but I just plain forget the commands and button combinations. Try using skipsoft or wugfresh toolkit!
[Samsung Galaxy Nexus] ____Mdd:
[MENTION=3795321]LibertyMonger[/MENTION] i assume you have rooted, so you can use "flashify" app (if PC and TWRP itself not working.)

- download app (link below)

- download latest TWRP img

-from app, select recovery img and downloaded one.

- flash through flashify.

Play store link: https://play.google.com/store/apps/details?id=com.cgollner.flashify
[Samsung Galaxy Nexus] LibertyMonger:
Ok thanks buddy. Also I'm thinking it may have something to do with the drivers on my PC. I use it for my HTC phones as well so I may need the galaxy nexus driver. Thanks again.

Yes I think it's my windows drivers. Thanks buddy

Flashify didn't work either but I am downloading the windows driver now. I always seem to forget about that part lol.
[Samsung Galaxy Nexus] LibertyMonger:
Skipsoft isn't working for me. It recognizes my device then it doesn't when trying to flash recovery. i wonder if I have to uninstall all of my HTC drivers? Here is a screenshot
[Samsung Galaxy Nexus] runekock:
No tool can help if you haven't got the driver right. Check in Windows device manager after the phone enters fastboot mode, is there an unknown device?

The phone has a different USB id in fastboot mode, so you need a different driver. Last time I tried, I couldn't find one, so I modified the USB id in the inf file, and that worked. Or you could try searching for a universal driver.

Really, I always recommend Linux for this. Download a boot CD or USB key with Debian or such.
[Samsung Galaxy Nexus] LibertyMonger:
I can't believe this sh%t Lol. It recognizes fastboot when the phone is booted but won't recognize fastboot in fasboot mode. I have uninstalled every single driver and tried reinstalling but I am getting nowhere. I should have just left the recovery I had.
[Samsung Galaxy Nexus] osm0sis:
Recovery has nothing to do with fastboot.

Did you go into Developer Options, enable USB Debugging and accept your computer's RSA signature? That avoids adb devices showing offline when in recovery.

I've never had an issue with forcing all my devices to use the latest ADB and Bootloader drivers from the Android SDK.
[Samsung Galaxy Nexus] bamtan2:
Getting the right driver is a hassle, but if you download one of the appropriate driver packs and manually go into device manager and fiddle to switch the galaxy nexus over to a different driver, you should eventually get on one that works for what you're trying to do.
[Samsung Galaxy Nexus] LibertyMonger:
I have no recovery. Yes I know that. I am trying to flash a recovery. I want to install a recovery manually I use fastboot flash recovery so therefore I need fastboot to work. I'm updating all of my sdk stuff now.

---------- Post added at 04:17 AM ---------- Previous post was at 04:03 AM ----------

I finally figured it out guy's, sorry for the mess. I updated my SDK and went ahead and tried UniversalAdbDriverSetup_20150930 and finally got fastboot flash recovery to work. It's just been so long I had to brush up on some things. thanks for all your help I really appreciate it.

---------- Post added at 04:35 AM ---------- Previous post was at 04:17 AM ----------

WOW the legendary Osmosis, it is really awesome you are still around and willing to help us out Buddy, really appreciate that. I was using your kernels way back when I had this phone new. Great to see you thanks for all you have done for this community! I was just really rusty, I shouldn't have posted anything, things started to click back and I was able to figure it out. Thanks again to everyone who tried to help, it's not like that in other phone threads cause they die off rather quick I guess. Definitely one of the many benefits of having a Nexus or Pixel!
[Samsung Galaxy Nexus] rahimali:
Try the universal naked drivers. They work perfectly for my GNex
[Samsung Galaxy Nexus] osm0sis:
Add this to the bottom of init.recovery.tuna.rc in [MENTION=5153662]Android-Andi[/MENTION]'s 3.1.1-1 for some nice color correction in recovery:

on property:init.svc.recovery=running
wait dummy 1
write /sys/devices/platform/omapdss/manager0/cpr_coef "205 0 0 0 202 0 0 0 256"
write /sys/devices/platform/omapdss/manager0/cpr_enable 1
[Samsung Galaxy Nexus] bamtan2:
I don't have a link to andi's build for everybody, but is there anything we can do to make all this official? it is very optional, but I trust that your numbers are an improvement for everybody.
[Samsung Galaxy Nexus] Android-Andi:
I've talked to the TWRP team to fork latest Omni source for tuna but didn't happened. So hw encryption stays broken on official TWRP until they fork the source. Once they forked we can contribute more improvements if needed.
[Samsung Galaxy Nexus] bamtan2:
I know you all put a lot of work into making Omnirom work for us, specifically so twrp would fork it. I think I should email and ask them for this.
[Samsung Galaxy Nexus] Android-Andi:
I've pinged deestroy again, last try...

We've tried here also already: https://github.com/TeamWin/android_device_samsung_maguro/issues/1
[Samsung Galaxy Nexus] nailyk:
He is active right now on IRC. Gonna try to talk about this with him.
[Samsung Galaxy Nexus] osm0sis:
The original Android-Andi 3.1.1-1 is here: https://androidfilehost.com/?w=files&flid=208209

My color correction might be a bit aggressive for everyone since my panel has gotten particularly bad (yellow and burn-in) over the last year. This balances mine out pretty decently, but if yours is better at all this will probably come out very blue. I still think the old colorcontrol struck a better balance than this newer omapdss one, with the separate contrast, multiplier and gamma controls, but I digress..

So that all said, if you do want to give it a try, I've uploaded my mod here: https://basketbuild.com/devs/osm0sis/osmods
[Samsung Galaxy Nexus] nailyk:
Can someone test encryption on https://releases.nailyk.fr/twrp-3.1.1-0-maguro.img please?

The omnirom on my maguro refuse to encrypt and no time to debug it for now.

662 [ 6.497589] type=1400 audit(1511970034.945:3): avc: denied { read write } for pid=170 comm="vold" name="mmcblk0p13" dev=tmpfs ino=4157 scontext=u:r:vold:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
663 [ 6.511260] type=1400 audit(1511970034.945:4): avc: denied { open } for pid=170 comm="vold" name="mmcblk0p13" dev=tmpfs ino=4157 scontext=u:r:vold:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
664 [ 6.511688] type=1400 audit(1511970034.945:5): avc: denied { getattr } for pid=170 comm="vold" path="/dev/block/mmcblk0p13" dev=tmpfs ino=4157 scontext=u:r:vold:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
665 [ 6.516784] init: Service 'tf_daemon' (pid 162) exited with status 2
666 [ 6.516845] init: Service 'tf_daemon' (pid 162) killing any children in process group
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=6979267]nailyk[/MENTION] twrp runs in permissive by default and it's decrypting not encrypting. should be a rom problem. Easy to test: set ROM Kernel to permissive and try again.
[Samsung Galaxy Nexus] nailyk:
yes. I already made a permissive kernel : https://releases.nailyk.fr/tuna_kernel_unsecure_20171129.img (adb unsecure + permissive).

Log in my previous post is rom one. That is why I cannot test the twrp provided and BigBiff want a check before releasing it.
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=6979267]nailyk[/MENTION] Just charging my phone and giving it a quick try. Private life is hell ATM and don't have much time :(
[Samsung Galaxy Nexus] Android-Andi:
Works. Encryption on UA6.0, your TWRP can decrypt it.
[Samsung Galaxy Nexus] nailyk:
Great many thanks! Just pinged BigBiff on IRC about it.

New official release should be up soon :)

Dunno if you get our emails but maguro/tuna maintainers are now:
[MENTION=2633638]Ziyan[/MENTION], you & me for

https://github.com/TeamWin/android_device_samsung_maguro

https://github.com/omnirom/android_device_samsung_maguro/

https://github.com/omnirom/android_device_samsung_tuna

https://github.com/omnirom/android_kernel_samsung_tuna

& samsung + ti vendor repo.

twrp jenkins use omnirom tuna device tree, not a forked one.
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=6979267]nailyk[/MENTION] Toro and toroplus should be used from Omni too. 6.0 & 7.1 trees on Omni are up-to-date and I am pushing all our goodies always there too.
[Samsung Galaxy Nexus] Android-Andi:
Not sure when official 3.2 TWRP is available, until that you can use the one by me

http://andi34.github.io
[Samsung Galaxy Nexus] bamtan2:
Congratulations to [MENTION=912474]Dees_Troy[/MENTION] [MENTION=6979267]nailyk[/MENTION] [MENTION=5153662]Android-Andi[/MENTION] and all others who helped! TWRP 3.2 is official for maguro! We made it just in time! Toro is not ready yet, but Andi has provided unofficial builds above which are just as good!

*Clap clap clap*

https://dl.twrp.me/maguro/twrp-3.2.0-0-maguro.img.html

I will use this opportunity to suggest that everyone donate to your favorite volunteer developer!

:good: :highfive: :highfive: :highfive:
[Samsung Galaxy Nexus] Android-Andi:
Ok, official changelog here:

https://twrp.me/site/update/2017/12/01/twrp-3.2.0-0-released.html

Maguro should have hw encryption support while toro and toroplus might not have!

toro tree got updated yesterday, toroplus tree today.

https://dl.twrp.me/toro/twrp-3.2.0-0-toro.img.html

https://dl.twrp.me/toroplus/twrp-3.2.0-0-toroplus.img.html
[Samsung Galaxy Nexus] osm0sis:
I turned my color correction for the recovery into an injector AK2 add-on zip to automate the process for 3.2.0+, because AK2 is good for everything. ;)

Anyone interested can grab from my BasketBuild mirror:

https://basketbuild.com/devs/osm0sis/osmods

Edit: Attached below since BasketBuild seems dead again. :rolleyes:
[Samsung Galaxy Nexus] Android-Andi:
Stupid question and slightly OT: your ak scripts don't support lzma compressed ramdisks, right?

On tab2 I'd need to replace the zImage only for some user but I think it doesn't work because ramdisk is lzma compressed and fails there ( option to skip unpacking und repacking of ramdisk might solve it too)
[Samsung Galaxy Nexus] osm0sis:
As of a week ago (and a bugfix this morning testing out the above zip ;)) it now supports all the popular ramdisk compression formats, just like my AIK project. :D

I'll consider how best to add a fallback to "OG AK" mode, for those who don't need ramdisk mods, as well.
[Samsung Galaxy Nexus] kerpert:
Someone tried to decrypt phone’s data with 3.2.1.0 under UA 7.1.2?

I would be sure it can before encrypt my Maguro.

EDIT

Answer is NO.
[Samsung Galaxy Nexus] Android-Andi:
adb pull tmp/recovery.log

adb shell dmesg > dmesg.txt

Attached both here.

(Taken from TWRP)
[Samsung Galaxy Nexus] kerpert:
:( I have already cleaned all.

After started the encrypton the phone reboot showing for half a second the follow (without text)

then has followed the android white animated logo, after 4h30min in this phase I removed the battery and powered it on,

at the decryption password window, it says like "the password is fine but data is corrupted" with a reset button (that doing nothing even with a reboot in twrp),

I made a fresh complete install formatting the DATA (writing YES) and all the other patitions.
[Samsung Galaxy Nexus] hga89:
Is there any way we can get TWRP to support encryption/decryption for Android 7.1? I just installed Zeelogs version of L and I'd like to encrypt my data partition,

https://zeelogkang.blogspot.se/2017/05/lineageos-141-unofficial-712-gnex-tuna.html
[Samsung Galaxy Nexus] goTouch:
Great recovery.... thx!
[Samsung Galaxy Nexus] yellowdie:
Hey, so I've been using TWRP for a while now and I love it. But back in the day, it was always "wipe data x3, wipe cache x3, wipe dalvik x3." Is that still necessary these days? Or is once enough? And when fixing permissions, does doing it a second time benefit anything? I'm still stuck in my old ways, so I wipe data, cache, dalvik, and system two or three times each, in that order, before flashing anything new. Thoughts?
[Samsung Galaxy Nexus] Timmyfoxeh:
I haven't had issues doing a single "factory reset"
[Samsung Galaxy Nexus] codesplice:
I've never heard of the need to wipe multiple times - or to do anything multiple times, really. So no, just once for wiping and for permissions. If the permissions are already fixed, how is fixing them again going to accomplish anything extra?
[Samsung Galaxy Nexus] Dees_Troy:
Outside of putting more wear and tear on your device, draining your battery, and taking up more of your time, doing these things more than once doesn't accomplish anything.
[Samsung Galaxy Nexus] yellowdie:
That is fantastic to hear! And does just one 'Factory Wipe' really do everything you need to do?
[Samsung Galaxy Nexus] The Gingerbread Man:
Wipe system is needed sometimes too, like if changing roms

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
I just came from the OG Epic 4G with CWM, and it was a religious wipe everything three times. Don't know if that's just an Epic or CWM thing, or if it's just old thinking.

Wow. Why the heck didn't I think about asking this sooner! I would have saved myself so much time! lol

Thanks guys! One 'factory reset' + 'wipe system' for me from now on! :laugh:
[Samsung Galaxy Nexus] bobsbbq:
Is there a download link for the 2.2.1? I tried to download it from the goo app but I can't seem to get it to work. (Of course this is the first time I have used this app)
[Samsung Galaxy Nexus] shockem:
You can try the website.
[Samsung Galaxy Nexus] Dees_Troy:
Most of the time you don't even need to wipe system. Most ROM installs wipe system during the zip install process.
[Samsung Galaxy Nexus] creeve4:
Where did you hear that there is a 2.2.1 version? Nothing on their website.
[Samsung Galaxy Nexus] etoy:
http://goo.im/devs/teamwin/twrp2
[Samsung Galaxy Nexus] creeve4:
There is no 2.2.1 for the GNex (maguro)
[Samsung Galaxy Nexus] azeem.droid:
Just love the interface. Cwm suddenly looks so messy now lol:D
[Samsung Galaxy Nexus] Savant:
Haven't went back to cwm because of this recovery.
[Samsung Galaxy Nexus] The Gingerbread Man:
Especially since their new style of backing up stuff. I'm converted to this officially, not only is it nicer to look at but also much more functional. I don't see why more people don't switch tbh

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] !crazy:
I actually prefer CMR Touch interface over this, it looks better IMO and is much smoother/faster but it doesn't support encryption, and that's the reason I have switched.
[Samsung Galaxy Nexus] kobik77:
+1 for that.

The only reason I see is people who are so frightened to "mess" with their recovery and legacy stuff.

It actually does support encryption with on-screen keyboard for entering your password!
[Samsung Galaxy Nexus] !crazy:
Yes twrp supports it, that's why I am using it now.
[Samsung Galaxy Nexus] badpanda:
whats up with goo manager saying "there is no open recovery available for your device" I have a galaxy nexus maguro(gsm) never had this happen to me before wtf.. Also I noticed under browse compatible ROMs I only get two now.. (projectfnv, teameos.) I dont even get CM9 or any other roms...

very frustrating. I am rooted, busybox, the works. Everything was working fine before today. so what happened?
[Samsung Galaxy Nexus] :
Via twitter:

"Goo.im will have some extended downtime for maintenance/upgrades over the weekend, you won't be able to flash twrp via goo manager. -- eyeballer (@eye_baller)"

Sent from my Galaxy Nexus running cm10