yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] n76:
Late to the game here. . . I was running an earlier version of TWRP (I don't recall which version) on my maguro with CM10 and later CM11. With those I had the stock ext4 (I believe) file system on /data and /cache and I had the device encrypted.

Recently I installed the twrp-2.8.6.0-maguro-f2fs.img and Ziyan's ZMoD Android 5.1. Everything runs fine and it has given new life to this old phone. But when I turned on encryption I found that TWRP could no longer mount /data and/or /cache. So at the moment I am reduced to installing new system distributions using the adb sideload command and if I get an install file that needs to touch /data I will be out of luck. Good thing I figured that /system did not need to be f2fs as there is not a lot of file writes to it when running. :)

I see a previous post that indicates that 2.8.1.0 is the most recent that has encryption working on the Maguro but it is not clear to me whether or not that version supports f2fs.

Is there a version of TWRP (or any other recovery program) that supports f2fs and encryption on the maguro? It need not be the latest and other than being able to flash release .zip files found on encrypted f2fs partitions, etc., it need not have all the bells and whistles working.
[Samsung Galaxy Nexus] bamtan2:
[MENTION=912474]Dees_Troy[/MENTION], [MENTION=6204913]n76[/MENTION] has been talking about this bug for some time, and even though I think he's crazy for running encryption on a slow phone ;) maybe you can take a look at it for him :)
[Samsung Galaxy Nexus] phaleg:
I tried to install the 2.8.7 on my maguro from TWRP Manager app, I was on 2.8.6...

it did not work but at least the phone is not bricked.

Can I flash it from recovery instead? The file is a .img and not a zip
[Samsung Galaxy Nexus] z31s1g:
Yes. On the install page (were you select the file) toggle the "images" button in the lower right corner, then select the img file. Next select recovery as target partition and flash away.
[Samsung Galaxy Nexus] phaleg:
Booting recovery I realized that I was on 2.8.7 already, but I did flash again, just to be sure, since the in-app way I used was not successfully...

all good now
[Samsung Galaxy Nexus] siealex:
It always says "unsuccessful". I tried to flash 2.8.7, then rebooted to recovery (to flash the image directly), and oops... I'm already on 2.8.7...
[Samsung Galaxy Nexus] phaleg:
Same here, as you can see from the post above yours...
[Samsung Galaxy Nexus] JuanG:
Hi!

I have installed TWRP 2.8.1.0 some months ago and now I want to update to the latest version (2.8.7.0). But, when I went to download that version of the official webpage I find a note which say that it requires TWRP 2.8.4 or higher already installed. What should I do? Should I flash first 2.8.4.0 over 2.8.1.0 and then 2.8.7.0?

Thanks in advanced!
[Samsung Galaxy Nexus] :
Where have you found this note? On twrp.me (dl.twrp.me) I haven't found anything like that.

From my perspective there shouldn't be a problem to update to the latest version.
[Samsung Galaxy Nexus] JuanG:
I found in this link https://twrp.me/devices/samsunggalaxynexusgsm.html in the section TWRP install.

I appreciate your suggestion. I going to wait if somebody can contribute with others experiences.
[Samsung Galaxy Nexus] z31s1g:
You need 2840 if you want to flash the recovery image directly from twrp like it was a flashable zip (image flashing came with 2840).

It's absolutely no problem to download the 2870 image and to install it via fastboot or an app like flashify (the latter will also download the image for you).

Don't worry, go ahead and update... [emoji106]
[Samsung Galaxy Nexus] :
I couldn't agree more!
[Samsung Galaxy Nexus] JuanG:
Thnaks man! Very very useful explanation! :good:
[Samsung Galaxy Nexus] JuanG:
Finally I updated and it has worked fine. Thanks!
[Samsung Galaxy Nexus] bamtan2:
[MENTION=912474]Dees_Troy[/MENTION]

TWRP 3.0 is out! https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html

Now we just need a maintainer for Galaxy Nexus ;)
[Samsung Galaxy Nexus] Oehr:
great! i hope 3.x branch will support encryption on 4.4+ devices too! cant wait to try it out. Currently the GN build seems to fail though: https://jenkins.twrp.me/job/maguro-prod/lastBuild/
[Samsung Galaxy Nexus] Nautilus74:
...it serves someone who implements also f2fs on our GNEX ......

About f2fs we are still yet to 2.8.6.0 (mod version) ....

...and the latest really stable f2fs version, in my opinion remains the Multirom 2.7.0.0 (which also has more consistent menus for the switch)
[Samsung Galaxy Nexus] rahimali:
Can anybody share download link for 3.0.0.0 please? I can't find it either here or here. Thanks!
[Samsung Galaxy Nexus] siealex:
There is no build for our device.
[Samsung Galaxy Nexus] rahimali:
Oh! I assumed there was since the OP was updated to show v3.0.0.0 :cowboy:
[Samsung Galaxy Nexus] werty100:
unnoficial TWRP 3.0 with F2FS format include

Hi i pressent part of my work of omni rom (i have problems with some apps giving errors :confused::confused:) , it is based on lastest twrp and omni sync and Marshallow kernel

Download:

http://www.mediafire.com/download/uizwqc9dwway4b9/twrp-3.0.0-tuna.img

Fighting with some apps for getting full omni rom and start development , maybe is my java problem:confused:
[Samsung Galaxy Nexus] bamtan2:
You are brilliant!!!

Does this build switch /data successfully from ext4 to f2fs, and from f2fs to ext4? The last twrp-f2s I tested from someone else could not successfully do this.

PS: note to other users: there is no reason to switch /system and /cache to f2fs. /cache is not used and /system is not written to, and f2fs makes writing faster, so it only helps /data. Leave /system alone for safety!
[Samsung Galaxy Nexus] werty100:
Yes it works data f2fs format, remember that it format you SDCARD¡¡¡¡¡

After it is formated you need to rebot again fro accesing to sdcard well , i am testing recovery the much i can fliemanager is working well also
[Samsung Galaxy Nexus] Nautilus74:
old backups (made with 2.7.0.0) will works on 3.0 ?
[Samsung Galaxy Nexus] Khizar:
There have been conflicting reports. Some say they work, other say they don't. I'd make a backup after updating twrp just in case.
[Samsung Galaxy Nexus] christianpeso:
Being that the file has Tuna in the name. does that mean that this will work on Toro devices as well?
[Samsung Galaxy Nexus] werty100:
I think it migth be if they have same recovery partiton size try it if not you just flash old twrp again and all solve
[Samsung Galaxy Nexus] osm0sis:
The buildbot tried but failed to make 3.0.0-0 for maguro/toro/toroplus. Don't feel too bad, it failed on flo (Nexus 7 2013) too. ;)

https://jenkins.twrp.me/job/maguro-prod/
[Samsung Galaxy Nexus] werty100:
Where can i put the fix for twrp 3.0.0 for my first build recovry was nto boting second one with inti.recovery.rc works
[Samsung Galaxy Nexus] osm0sis:
They've got a Gerrit and GitHub set up so you could submit patches/pull requests on either as they suggest in their release post:

https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html

And they could use a maintainer if you feel like keeping up with things:

https://twrp.me/devices/samsunggalaxynexusgsm.html

:) :good:
[Samsung Galaxy Nexus] Nautilus74:
[MENTION=4240105]werty100[/MENTION]

Are there problems or not with your twrp 3.0?
[Samsung Galaxy Nexus] Mr.FREE_Bird:
Yes, for me there are some problems... Flashing roms takes twice as much time as normal. Don't know if the problem is on my side but TWRP 2.8+ runs way better for me.
[Samsung Galaxy Nexus] werty100:
Yes tales more time flashing , but I only find this problem, the rest I test was working well , also i9000 hace this problema sometimes flashing romd i think is twrp related not gnex or I
[Samsung Galaxy Nexus] Mr.FREE_Bird:
Yes, I think that it's twrp related to... And we have to keep in mind that this is the first release of twrp 3, so maybe there are bugs which need to be fixed.
[Samsung Galaxy Nexus] massima:
Can i safely flash this twrp version on my maguro without issue?

It is my daily phone. Thank you
[Samsung Galaxy Nexus] werty100:
I think yes it is stable, only a lot of time regarding to installing ROMs but i think it is only in some roms deppending on updater-script becouse i have compile a AOSP 6.0.1 rom that i hope it works well , it has flashes in a normal period time but OPENGAPPS 6.0 takes more than rom i think is related to TWRP and updater script old ones orders
[Samsung Galaxy Nexus] siealex:
After flashing this TWRP throws "Keep the system partition read-only?". What must I click there?
[Samsung Galaxy Nexus] osm0sis:
Your choice, but tuna isn't really an Android Pay candidate or subject to OTAs anymore so there's no real reason I can think of to keep system r/o.

Unrelated but I'd like to point out our recovery is now "running" a higher version of Android than our system can. Oh, irony. :p
[Samsung Galaxy Nexus] massima:
FLASHED SUCCESSFULLY:D, i just want to say thank you for your efforts and for sharing your built image.
[Samsung Galaxy Nexus] siealex:
Also flashed successfully, now backing up my files for switching to F²FS.
[Samsung Galaxy Nexus] siealex:
Can I restore a TWRP backup from EXT4 to F2FS? I tried to restore it and got a clean data partition on first boot.

PS, it is actually not clean! It's simply inaccessible via ADB...

PPS, my sdcard folder has moved to sdcard/0. WTF?
[Samsung Galaxy Nexus] osm0sis:
They're all just tar.gz if I recall correctly, the only trick is the filename is used to determine the partition format, so if you change the part of the name that says ext4 to f2fs it should work.. Unless something else has gone wrong.
[Samsung Galaxy Nexus] Oehr:
upgraded to 3.0. Takes a loooooong time to start. Probably because I still cannot mount encrypted /data... I thought thats fixed now or does it only apply to marshmallow encrypted data? (im still on lollipop atm)
[Samsung Galaxy Nexus] phaleg:
I don't find the 3.0 version for maguro on their website...

Where is it?

Is it currently working alright?

Is it worth to upgrade from 2.8.7
[Samsung Galaxy Nexus] osm0sis:
Homebrew maguro build posted a couple pages back:

http://xdaforums.com/galaxy-nexus/d...h-recovery-t1592689/post65213301#post65213301

Read from there to decide if you want to update it or not.
[Samsung Galaxy Nexus] phaleg:
Maybe I wait for an official TWRP release :)
[Samsung Galaxy Nexus] siealex:
The official release will not support F²FS.
[Samsung Galaxy Nexus] siealex:
Installing OpenGapps Micro takes 30..40 minutes instead of 2 minutes. Does anyone experience this bug?

PS, it completely froze at "fixing permissions and contexts", I can't flash anything now. I'm on F2FS, so I can't use any other versions. Are there any earlier TWRP builds with F2FS support?
[Samsung Galaxy Nexus] rahimali:
http://xdaforums.com/showpost.php?p=53156720&postcount=1577
[Samsung Galaxy Nexus] werty100:
You can take out battery and no problem i do it everu time and it fully works

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] siealex:
I've found here TWRP 2.8.5.0 with F2FS support and it flashed all packages in 5 minutes.
[Samsung Galaxy Nexus] osm0sis:
Hmm.. Now marked disabled. Not a good sign..

https://jenkins.twrp.me/job/maguro-prod/

https://jenkins.twrp.me/job/toro-prod/

https://jenkins.twrp.me/job/toroplus-prod/
[Samsung Galaxy Nexus] thagringo:
sh!t, does that mean they will drop it eventually ??

i hope they dont and someone skilled can maintain it !

cheers
[Samsung Galaxy Nexus] kingracer:
Hi, i cant find link to 3.0, on official site there is no 3.0 version for maguro :( Here is screenshot
[Samsung Galaxy Nexus] Nautilus74:
twrp 2.8.6.0 f2fs

twrp 2.8.0.0 f2fs

twrp 2.7.0.0 f2fs
[Samsung Galaxy Nexus] massima:
Some posts ago http://xdaforums.com/showpost.php?p=65213301&postcount=1872 you will find an unofficial version of twrp 3.0.0-0 (F2fs support).

Without a maintainer will be hard to have an official version:crying:
[Samsung Galaxy Nexus] osm0sis:
Not sure. Bit of a mixed message still with this thread being updated, and "Support Status: Current" listed on the device page:

https://twrp.me/devices/samsunggalaxynexusgsm.html

Just probably not a good sign when it's disabled on the build bot.
[Samsung Galaxy Nexus] phaleg:
In understand your delusion, maguro is a great phone, but in the end of the day, what is wrong with last 2.8.7 ?

It works great to me
[Samsung Galaxy Nexus] kingracer:
Nothing wrong with it, i just wanted to try smth new :)

Tried it - installed and started normally, but stucked on flashing ROM, so i reverted to 2.8.7, and will hope that 3.0 will be released 'cause it's better looking and also has a multilanguage support, that's nice :)
[Samsung Galaxy Nexus] bamtan2:
I remember each version having a different bug, so I'm not sure what to recommend to anyone :)
[Samsung Galaxy Nexus] bamtan2:
FYI, [MENTION=4831205]vocoderism[/MENTION] is trying to fix a f2fs backup-restore bug in TWRP, and he needs testers to help. Here are the bug reports: http://xdaforums.com/showpost.php?p=65625960&postcount=3940

Here is his latest test build of TWRP: http://xdaforums.com/showpost.php?p=65697576&postcount=3969

I have committed a $10 USD bounty to whatever developer fixes this bug. Any other readers are welcome to contribute as well. Good luck and thank you to all volunteer developers!

CC: [MENTION=5405242]norton75[/MENTION], [MENTION=6598907]spryka[/MENTION], [MENTION=5038522]tomasz86[/MENTION]
[Samsung Galaxy Nexus] tlwhitec:
I'm in for another $10.
[Samsung Galaxy Nexus] jeffy1986:
how to root galaxy s6 edge

how to root s6 edge that wont boot into recovery mode
[Samsung Galaxy Nexus] massima:
Wrong thread, this recovery is for Samsung Galaxy Nexus.
[Samsung Galaxy Nexus] Nautilus74:
2.7.0.0 is perfect, and most user friendly for f2fs switch! ;)....:

I hope 3.0.0 becomes stable (and fast) as 2.7.0.0 Multirom
[Samsung Galaxy Nexus] massima:
A simple question:D: on my Nexus7 (2012) the official release of TWRP 3.0 supports by default the f2fs, i tested it and it worked.

Does the normal unofficial maguro 3.0 TWRP version format a f2fs partition? I cannot test it immediately.

Thank you

EDIT: i tested all 3.0 versions and they failed to flash the OMAP4 AOSP on partitions with the f2fs, i'm sad that would have been a great improvement of performance for our old phone :crying:.
[Samsung Galaxy Nexus] massima:
I found these versions:

twrp 2.8.4.0 f2fs

twrp 2.8.5.0 f2fs

Could anyone try them???
[Samsung Galaxy Nexus] thepasto:
If someone wants to try here there's a new 3.0 build.

Let me know if it works for you.
[Samsung Galaxy Nexus] massoudsh:
This version have a f2fs support?!!
[Samsung Galaxy Nexus] massima:
TWRP supports by default the f2fs and other fs (on my nexus7 i can confirm it). 3.0 versions of twrp weren't able to mount a f2 filesystem (normal version of twrp by vocoderism), to flash correctly the OMAP4 AOSP rom (f2fs version of twrp by vocoderism) and to flash in a reasonable time a rom+gapps (the twrp in this thread).

I did tests some post above, i'm temporary using the slow ext4 on my only phone:eek:.
[Samsung Galaxy Nexus] thepasto:
I currently run omap4-aosp with f2fs data. I flashed it with the .img i posted. AFAIK use f2fs on system it's worthless.... But correct me if i'm wrong!
[Samsung Galaxy Nexus] massima:
TWRP 3.0.1-0 is out now for all currently supported devices.

What’s new in 3.0.1-0:

support new CM 13.0 pattern encryption (sultanqasim)

fix slow flashing issue due to modprobe (present on only some devices) (#twrp)

libtar updated to latest upstream and fixes (jcadduono)

fixes for loading custom themes (_that)

TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)

translation updates - added Italian:), Czech and Polish and significant updates to Dutch

progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)

fix input box text display (Dees_Troy)

reboot option after zip install complete (bigbiff)

other mostly invisible bug fixes and improvements
[Samsung Galaxy Nexus] osm0sis:
Judging by the thread title not getting updated it looks like maguro dropped off the support list. :(

One of the guys already rolling their own should contact the TWRP guys in #twrp and ask to be maintainer. I'm sure you could bring it back.
[Samsung Galaxy Nexus] aosp:
[MENTION=912474]Dees_Troy[/MENTION] [MENTION=4831205]vocoderism[/MENTION] [MENTION=4544860]osm0sis[/MENTION]

Tuna has hardware backed disk encryption support now

https://github.com/OMAP4-AOSP/android_device_samsung_tuna/commits/aosp-6.0-smc

https://github.com/OMAP4-AOSP/android_kernel_samsung_tuna/commits/aosp-6.0-smc

https://github.com/OMAP4-AOSP/proprietary_vendor_samsung/commits/aosp-6.0-smc
[Samsung Galaxy Nexus] aosp:
[MENTION=4831205]vocoderism[/MENTION] [MENTION=1143630]osmosis[/MENTION] [MENTION=2633638]Ziyan[/MENTION]

http://gerrit.twrp.me/#/q/project:android_device_samsung_tuna
[Samsung Galaxy Nexus] osm0sis:
Lookin' pretty empty!
[Samsung Galaxy Nexus] thepasto:
Here's a TWRP 3.0.2 for tuna. Let me know if you find problem or some missing.

Thanks!
[Samsung Galaxy Nexus] LuckOne79:
Link seems Brocken :confused: Thanks anyway :good:
[Samsung Galaxy Nexus] PythonNut:
It worked for me.
[Samsung Galaxy Nexus] osm0sis:
Nice! Hopefully better than the 3.0.0-0 ones people had compiled, which had random reboots and soft-bricking issues. :good: :)
[Samsung Galaxy Nexus] PythonNut:
I can also confirm that the bug that was causing F2FS backups to take an eternity seems to have been fixed in your build. Thanks a bunch! This is probably going to save me more than a dozen hours a week.
[Samsung Galaxy Nexus] LuckOne79:
Thanks again. Tried it again and could dl it ...
[Samsung Galaxy Nexus] osm0sis:
Hmm very much not working here! :eek:

recovery.log

Flashed back to TWRP 2.8.7.0 and all is mounting and working correctly again. No errors like this on any of the previous 3.0.0-0 homebrew builds either. Any ideas?
[Samsung Galaxy Nexus] thepasto:
It's a bit weird for me! I can't reproduce your problem. From the log the only thing i can see, is about SELINUX status, it shows Full SELinux support is present, when it's not.

Could you try to "Fix Context" on advanced tab? Make sure to follow the advice, so get a backup before doing that!

Thanks
[Samsung Galaxy Nexus] osm0sis:
E:Primary block device '/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata' for mount point '/data' is not present!
Failed to mount '/data' (Invalid argument)
I:Actual block device: '', current file system: 'ext4'
Unable to recreate /data/media folder.

Fixing contexts won't have any effect on /dev or the fstab being borked. I'll swap in the ramdisk root and etc files from one of the 3.0.0-0 builds (which work.. but aren't stable) to see if we can narrow down where the problem lies.
[Samsung Galaxy Nexus] thepasto:
Here's a new build. And here's my log.

If you can find something let me know!! Thanks again
[Samsung Galaxy Nexus] nailyk:
Hi,

thanks for the build. I test it just now (wanna test a rom but unable to flash as my device is encrypted).

I just boot your recovery (fastboot boot ...)

And there is a lot of errors.

Maybe I do something wrong?

Edit: official CM12.1 (20160310) software encrypted with default password.
[Samsung Galaxy Nexus] thepasto:
Ok, it seems we know the reason now! There are some problem with encryption. [MENTION=4544860]osm0sis[/MENTION] do you have encrypted partiton too?

Thanks
[Samsung Galaxy Nexus] nailyk:
Good new!

I wipe to install AOSP 6.0.1 and as someone says earlier the phone says the the encrypted storage is now 'hardware backed'... :o

P.S.: It is a test/devel phone so I am able to make (almost) every test you want.
[Samsung Galaxy Nexus] osm0sis:
Nope. Unencrypted here.
[Samsung Galaxy Nexus] PythonNut:
I'll give it a shot with encryption.
[Samsung Galaxy Nexus] PythonNut:
Yeah. It looks like the recovery doesn't work with encryption. :(

EDIT:

Specifically, the recovery never asks me for the encryption PIN, so it's unable to access /data, among other things.
[Samsung Galaxy Nexus] osm0sis:
Yeah, seems like it's acting as though mine is encrypted even though it isn't. Pretty weird. I notice in the errors it's got /tee -> dgs stuff from OMAP-AOSP hardware backed encryption, maybe that's messing it up. I'm on the latest CM13, though that shouldn't matter.
[Samsung Galaxy Nexus] Ziyan:
Since the latest 6.0 ROMs use hardware backed encryption, I think you need to include the keystore module in the recovery image, though I'm not really sure about it - I never done, or honestly, thought about the recovery parts. The are some links towards the end of this discussion that might help.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=1608879]thepasto[/MENTION], I switched the zImage from your 0406 .img with the zImage from [MENTION=4240105]werty100[/MENTION]'s 3.0.0 .img (also built from a 6.0.1 tree) and it works, so there's something borked in your kernel source apparently! :good:

I also changed ro.product.device in default.prop from tuna to maguro since no zips are really set up to look for tuna, just the old maguro/toro/toroplus still. :)

[ Attachment removed since there is a newer working nightly ]
[Samsung Galaxy Nexus] thepasto:
Hmm... Well it's the default Ziyan kernel. The same it's running on OMAP4-AOSP to be clear. ATM i'm ill, so i will release a new build later, maybe this evening!

Thanks
[Samsung Galaxy Nexus] thepasto:
New daily realease :D

I buit it with cm13 sources, hope to solve your problem. I have no news about encryption since i'd like to start from a fully working recovery, before adding other features.

As always let me know if you have problems or suggestions!!

Thanks
[Samsung Galaxy Nexus] osm0sis:
Works perfectly sir, great job! :D
[Samsung Galaxy Nexus] bamtan2:
Attention: [MENTION=5405242]norton75[/MENTION], [MENTION=6598907]spryka[/MENTION], [MENTION=5038522]tomasz86[/MENTION].

[MENTION=6906944]PythonNut[/MENTION] reports that your F2FS restore bug has been fixed: http://xdaforums.com/showpost.php?p=66217744&postcount=1932

Can 2 out of 3 of you confirm that this is true? Please find the latest [MENTION=1608879]thepasto[/MENTION] TWRP build here: http://xdaforums.com/showpost.php?p=66243256&postcount=1948

When you report back that this bug is indeed fixed for you, [MENTION=5290873]tlwhitec[/MENTION] and I will deliver our $10 bounties to the successful developer! :)

CC [MENTION=912474]Dees_Troy[/MENTION] [MENTION=4831205]vocoderism[/MENTION] [MENTION=4240105]werty100[/MENTION]
[Samsung Galaxy Nexus] thepasto:
If the bug is really fixed, please, if you want to give money, send them to the real developers!! I only built what others have done!!

So don't spent money for me, give them to OMAP4-AOSP team, their job is really impressive!
[Samsung Galaxy Nexus] massima:
With the latest version i cannot mount anymore via OTG my usbpen, all previous versions were able to mount it:rolleyes:. It is a very important feature
[Samsung Galaxy Nexus] thepasto:
Ok as i wrote above, i built it with cm13 sources, because of some problem with omap4-aosp kernel with some device.

It seems cm13 has not usb otg working too, i already reported here the problem.

I tried to look at it, but i'm an old dev :D, and i'm really rusty! I hope [MENTION=2633638]Ziyan[/MENTION] or someone else could solve it!

Thnks
[Samsung Galaxy Nexus] PythonNut:
Hmm... I just gave restoring a backup another shot, and this one's been running for several hours. I'm not sure what's changed between this backup and the last one... They're about the same size. But do confirm if the issue has been solved for you guys. That's what matters after all.
[Samsung Galaxy Nexus] :
The bug is still present :(

Everything got stuck after restoring around 600MB out of 2700MB. At this point it is faster to just restore the apps using Titanium Backup and reset the system settings manually than waiting for TWRP to finish.
[Samsung Galaxy Nexus] osm0sis:
Backup and restore is working fine here with [MENTION=1608879]thepasto[/MENTION]'s latest build.