yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nailyk:
CM-14.1 custom gerrit setup

[MENTION=4695183]zeelog[/MENTION] Thanks for rights. Gerrit setup.

+2 list is available here (registered users only).

repo available:

android_device_samsung_maguro

android_device_samsung_tuna

android_kernel_samsung_tuna

proprietary_vendor_samsung

proprietary_vendor_ti

Ask me if anything else is needed.

(only 14.1 branches exist, I could also setup android-7.1 (omni) if needed)

[MENTION=4695183]zeelog[/MENTION] [MENTION=4544860]osm0sis[/MENTION] [MENTION=5153662]Android-Andi[/MENTION] [MENTION=2633638]Ziyan[/MENTION] Please letme know where your account is setup as I can add you +2.

(Please dont push to github, it will broke replication gerrit->github. )

hardware/ti/omap4 not setup into 'private' gerrit because this should be pushed into Linage one.

Dedicated IRC chan: ##Lineage-Maguro on freenode (registered users only). Feel free to contact me in it for any question problem.

Cheers
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=6979267]nailyk[/MENTION] thx for your efforts! We should move this to an own Thread. Atm i won't have time to do anything on Lineage but i let you know if in find any.
[Samsung Galaxy Nexus] hga89:
"Upgrading modem partitions?" Sounds risky. How does one do that? This worked fine when I was running CM 10.2.
[Samsung Galaxy Nexus] nailyk:
Thanks! But right now I did nothing except stealing [MENTION=4695183]zeelog[/MENTION] work :)

Just ended writing maguro build scripts.

And thread opened.
[Samsung Galaxy Nexus] osm0sis:
You can probably take me off of the contributors list.. while I appreciate the thought, I have really had next to nothing to do with maguro ROM development. :)
[Samsung Galaxy Nexus] nailyk:
:s done.

Try reading this thread (by osm0sis :P) should be a good starting point :)
[Samsung Galaxy Nexus] hga89:
Thank you, long thread...
[Samsung Galaxy Nexus] magur0:
Big troubles

Hello!

I use this phone and ROM (Cyanogenmod before) since long time as my daily driver. My phone is encrypted which means I can't do backups from TWRP (decryption doesn't work there).

Now I have big troubles:

Yesterday I tried to use GPS (didn't used for a long time - I think never on lineage) with a new app.

What I did to fail:

active GPS from the top tile

searched my location in the app

got the "privacy guard" pop-up-meassage if I want to allow location-access for the app

touched 'yes' -> Here the screen froze totally with the dialog box still open

Now I can't boot back in my system. It

bootloops

most of the time or it boots long time till it turns off. Eventhough I get asked for the decryption pass in the lineageos boot process and accepts the correct one. It even booted to some sort of launcher screen with clock widget and my background - but top and bottom icons and buttons where missing.

What I tried to fix:

Reboot many times (taking battery out for longer time)

Boot without simcard

Wipe Cache and Dalvik (-> wiping dalvik always fails)

sideload most recent version (2017.08.05) of lineageos

Nothing of this gave me my phone and my data back! It's still booting to death :crying:

The best I can reproduce with a lot's of patience is the initial lock-screen with my backgroud.

But anytime I do a touch input (for example sliding from buttom to unlock) it soft-reboots!

I very glad for any advice and help you can give (what/how to debug, etc.) to get my phone back a live with it's data!

THANK's a LOT!
[Samsung Galaxy Nexus] nailyk:
you could try different things

1. TWRP is able to decrypt data but fail after for whatever reasons.

You could try to decrypt 'by hand' to get your data back.

2. I guess your rom is still asking for your boot password

Build an unsecure/mod your actual rom to make it unsecure,

Decrypt by hand, fix the problem.

3. Looks like you know what exact app cause the crash (you should be able to take a logcat after decrypting)

remove it.

P.S.: commands to decrypt by hand are a mess to find:

twrp: twrp decrypt <password>

lineage: vdc cryptfs verifypw <password>

vdc cryptfs checkpw <password>

vdc cryptfs restart --> this restart the framework and end booting the system, you should try to fix before this command.

WARNING while using this on my Z3, I encountered a bug into vold who damaged the crypt header. Android was never able to start again after this, but it was probably a bug into my encrypt port.

I don't have 13.0 build environment anymore so cannot provide tools/builds anymore.
[Samsung Galaxy Nexus] runekock:
[MENTION=8463548]magur0[/MENTION]

I can see that [MENTION=6979267]nailyk[/MENTION] has written a great answer, but maybe try the simple ways first:

1) see if you can start the phone in safe mode

2) see if you can access the phone from a computer, when LOS is started as much as it can. Try both PTP and adb.

When you have copied as many files as you are able to, wipe data to get the phone back to normal.
[Samsung Galaxy Nexus] magur0:
1.) I didboot in TWRP 3.1.0-0 (always asks for decryption password but is not able to decrypt) and go to: Advanced > Terminal: twrp decrypt <password>

Output:

Attempting to decrypt data partition via command line
Failed to decrypt data

(Same Error message when starting TWRP with right password)

It's asking for decryption password @ booting but I don't have any coding skills. With my skills I was able to upgrade the rom via adb sideload but that's already top notch for me!

I know what App (Tour App) I used. But I used it before and never had troubles. I think more there is something dangerous broken related to GPS combined with the inbuilt privacy-guard. And that's the reason why it first froze and know isn't able to boot properly to the launcher.

How can I make use of the lineagos command when I'm not able to boot? I just have fastboot via bootloader and adb via TWRP :confused:

Thank's for your input! :good:

---------- Post added at 07:18 PM ---------- Previous post was at 07:14 PM ----------

Hi there,

1.) Dump question: How can I start lineageos in safe mode? I know how to access the bootloader and recovery... :confused:

2.) It doesn't mount as media/storage device. But I can try further to safe some data. My priority right now is to safe the whole system! :o

Thank's for your input!
[Samsung Galaxy Nexus] Android-Andi:
Not sure if it works, but you can decrypt using TWRP? If yes, you should be able to delete mentioned app and hope it's able to boot again.

---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------

And btw. Via adb pull you can get important files if decrypt works in twrp
[Samsung Galaxy Nexus] magur0:
Hi [MENTION=5153662]Android-Andi[/MENTION] ,

sadly my decryption in TWRP never worked! It is reported from some user that it *sometimes* works. But I tried already 10 times and had no luck!

I'm also quite sure that the App itself didn't caused the problem... but anyway: Right now I'm still locked out of my phone :crying: ... what a sh*t!
[Samsung Galaxy Nexus] Android-Andi:
We can do some testing using different TWRP. I could compile one or two for you (maybe tomorrow, maybe Wednesday). I remember from tab2 there's 2 kernel commits needed to have working encryption on CM13, I'd need some time to find it.

---------- Post added at 07:44 PM ---------- Previous post was at 07:38 PM ----------

[MENTION=4544860]osm0sis[/MENTION] stupid question. If I change the anykernel to point on recovery instead boot partition it'll replace the zImage of recovery?
[Samsung Galaxy Nexus] magur0:
I would love to! I can flash the recovery via fastboot so there is nothing which can brake on the system side. I also think [MENTION=5840086]zyian[/MENTION] did work a solution for the "decryption"-problem in TWRP for maguro... but he was halted at a certain point (last year?)...

EDIT: A TWRP with working decryption would be the greatest outcome of my misery for everybody :D
[Samsung Galaxy Nexus] Android-Andi:
If I am not wrong I can modify the AnyKernel to replace the zImage of your current TWRP. I am home in next 2 hours and can make you a modified zip.

Our recovery has a own partition and own zImage ;) some older devices don't have.

For TWRP I need to check Omni source first, so might be Wednesday until I can post a complete TWRP.
[Samsung Galaxy Nexus] runekock:
https://support.google.com/nexus/answer/2852139?hl=en

I tested Google's methods, and they work on my LOS 7.1.
[Samsung Galaxy Nexus] osm0sis:
Yup, absolutely. :)
[Samsung Galaxy Nexus] magur0:
Thank's very much. The Safe Mode is working on my LOS 13 (=Android 6) with encryption enabled. It asks for decryption password (has already 'safe mode' down in the left corner then) and continues booting when I provide the right passphrase. I get the LOS boot animation for looong time... sadly the screen just turns black... but then again boot animation... short virbrate noise(?)... boot animation... black.... -> I think it's bootlooping with soft-restart :(

Thank's for the hint anyway! Can be useful in the future...

Btw: Your version is probably LOS 14 (=Android 7.x)
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=8463548]magur0[/MENTION] you can flash this in TWRP, it'll replace the zImage of your TWRP. Will be the easiest solution.

If you still have issues, please take a dmesg and use adb to pull /tmp/recovery.log
[Samsung Galaxy Nexus] magur0:
Can you throw me the command to flash this right? I guess via fastboot - but which command? I don't want to kill my lineagos by accident ;)
[Samsung Galaxy Nexus] Android-Andi:
Via your current TWRP.
[Samsung Galaxy Nexus] magur0:
That's smart :D Flashing right now... :fingers-crossed:

---------- Post added at 10:15 PM ---------- Previous post was at 09:58 PM ----------

No luck. Still can't decrypt in TWRP. Tried 3 times to password with the initial password prompt and 10 times via command line.

How can I deliver a dmseg: Just the copy log function in twrp?
[Samsung Galaxy Nexus] Android-Andi:
adb pull /tmp/recovery.log

adb shell dmesg > dmesg.txt

---------- Post added at 10:55 PM ---------- Previous post was at 10:45 PM ----------

Btw. I guess you did, but make sure you rebooted twrp once after the kernel flash.

I'll see what I am able to do tomorrow, 12 hours working day in front of me and not sure if I a am able to do much after that.

I let you know if I have something for you.
[Samsung Galaxy Nexus] nailyk:
xda totaly broken for me today, cannot thanks you :s [MENTION=5153662]Android-Andi[/MENTION] While looking at twrp decryption I noticed that lineage have a specific init file with a specific service for decryption. Maybe it could be useful. [MENTION=8463548]magur0[/MENTION] weird, every case I see with decryption problem in twrp it decrypted fine, then fail to read data, then reboot.

Here it seems you are not able to decrypt. With some luck, your device is encrypted for a long time and it is software only. If you encrypted your device long time ago, try an older version on twrp.me.

Also you could try 'default_password' into twrp (in case something goes wrong while creating dm-crypt header. )

One last thing, you should take a look at logcat while doing decrypt attempt. Maybe you will reach the max tries count (dunno how it is for lineage).
[Samsung Galaxy Nexus] magur0:
So, first: enjoy your work! ;)

I rebooted for the new kernel and did it again now to get the dmesg.txt and recovery.log. I tried 3 times with the dialog in the beginning and 3 times with command line to decrypt:

TWRP Dialog failed decrypt:

I:Set page: 'decrypt'
I:Set page: 'trydecrypt'
I:operation_start: 'Decrypt'
crypt_ftr->fs_size = 28397534
Using scrypt with keymaster for cryptfs KDF
Invalid hex string
Failed to convert passwd from hex, using passwd instead
could not find any keystore module
Failed to init keymaster
Signing failed
kdf failed
failure decrypting master key
Failed to decrypt master key

Terminal failed decrypt:

I:Set page: 'terminalcommand'
I:Command 'decrypt ***********' received
I:Set page: 'singleaction_page'
I:operation_start: 'TWRP CLI Command'
Attempting to decrypt data partition via command line.
crypt_ftr->fs_size = 28397534
Using scrypt with keymaster for cryptfs KDF
Invalid hex string
Failed to convert passwd from hex, using passwd instead
could not find any keystore module
Failed to init keymaster
Signing failed
kdf failed
failure decrypting master key
Failed to decrypt master key
crypt_ftr->fs_size = 28397534
Using scrypt with keymaster for cryptfs KDF
could not find any keystore module
Failed to init keymaster
Signing failed
kdf failed
failure decrypting master key
Failed to decrypt master key
Failed to decrypt data.

Hi [MENTION=6979267]nailyk[/MENTION] ,

it's a quite fresh install from July so no software encryption anymore. Also my passphrase and unlock pin is different (App: SnooperStopper), but the passhrase is correct and get's accepted when I try to boot in Lineageos (which fails in the end and the launcher). Could you drop me a line how to logcat with adb & twrp? Thank's a lot!
[Samsung Galaxy Nexus] Android-Andi:
You can get a dmesg & logcat from boot too? Best after encryption
[Samsung Galaxy Nexus] magur0:
Can you give me a hint how to achieve this? I have a linux client with adb on board :p
[Samsung Galaxy Nexus] Android-Andi:
adb shell dmesg > dmesg.txt

adb shell logcat > logcat.txt
[Samsung Galaxy Nexus] nailyk:
no without unsecured boot.

and imho it is now the only way to get the data back:

1. decrypt with vold,

2. transfer backup / run twrp binary

3. wipe

as twrp report keystore problem. IIRC since 3.1 twrp should fall back to vold decrypt but from the log it do not look like it does.

If you cant build right now I probably should be able to provide an unsecure boot.img with 14.1 unpackbootimg/mkbootimg.

edit: maybe after the decrypt there is a way to reset confidentiality settings. IIRC it is an xml file into /data.
[Samsung Galaxy Nexus] Android-Andi:
12 hours working day today, not sure after work, guess Wednesday I have a few more minutes
[Samsung Galaxy Nexus] nailyk:
here is the unsecured boot: https://releases.nailyk.fr/maguro/newboot.img

fastboot boot newboot.img

wait device ask for passphrase,

connect to adb

vdc checkpw <your password> (or verifypw don't remember)

then data will be decrypted you can change/backup/etc...

Other case:

with the unsecure adb you will be able to get the full logcat, maybe you will be able to fix the bootloop problem.

P.S.: reread the warning some post earlier about manual vdc decrypt.

P.S.2: with fastboot boot kernel is lost at every reboot but am not sure if it will work, don't have my maguro right now.

Good luck!

edit: [MENTION=8463548]magur0[/MENTION] am surprised you didn't anwserd. Am wondering if you missed the post so am highlighting you into ;)
[Samsung Galaxy Nexus] magur0:
dmesg throws the same as before. Starting from

[ 0.000000] Initializing cgroup subsys cpu

the second command throws:

/sbin/sh: logcat: not found

[MENTION=6979267]nailyk[/MENTION]

How can I decrypt with vold? I guess I need to flash something for the recovery? I'm not able to build anything but happy to test everything provided :cowboy:

I have TWRP 3.1.0-0 and Lineage OS 13 since July installed. Therefore it should be a hardwarebacked encryption.
[Samsung Galaxy Nexus] nailyk:
We crossesd post.

Also if you can join some irc chan like freenode#lineageos or freenode#twrp it could be easiest.

Good luck.
[Samsung Galaxy Nexus] hga89:
Although I have not had any problems running L13 on my encrypted GN, I would very much like to able to decrypt in TWRP and thus use TWRP to install software etc.

Let me know if I can help testing.
[Samsung Galaxy Nexus] entux:
anyone else having a hard time connecting (or staying connected) to certain wlan hotspots? wlan is VERY flaky for me in general with L13.
[Samsung Galaxy Nexus] magur0:
Thank's a lot. I managed to boot the image via fastboot and now I'm at the decryption prompt.

magur0@work ~ $ fastboot boot newboot.img
downloading 'boot.img'...
OKAY [ 0.729s]
booting...
OKAY [ 0.361s]
finished. total time: 1.090s

I tried to find more about the commands - but like you sad it's a pain. I don't want to kill it (damage my crypt header).

Also the inbuilt help doesn't work - or better: i can't use the vdc command at all :confused:

magur0@work ~ $ adb shell
~ # vdc --help
/sbin/sh: vdc: not found
~ #

Meanwhile my searches I found this one here:

https://android.stackexchange.com/questions/105972/softbricked-my-device-with-encryption

I don't know if this information is still valid (over 2 years old)? I'm even more scared now to try.... :( I have just one shot and no backup :rolleyes:

PS.: I joined freenode #lineageos & #twrp as magur0 :cool:
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=8463548]magur0[/MENTION] http://xdaforums.com/showpost.php?p=67975081&postcount=2014
[Samsung Galaxy Nexus] magur0:
thank's for the hint [MENTION=5153662]Android-Andi[/MENTION] -> Here is my reply: https://xdaforums.com/showpost.php?p=73350485&postcount=2141
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=8463548]magur0[/MENTION] [MENTION=6979267]nailyk[/MENTION] I'll see if I find some time this weekend, end of August I have some more time around my birthday.
[Samsung Galaxy Nexus] magur0:
Where is the party? :laugh: No, seriously! If the problem with decryption would be solved in TWRP this old device will be fresher than never and two of the most important things should then work:

OTA Updates with the in build updater (

fast and easy security updates!

) :cowboy:

Finally to be able to do nandroid backups of the whole phone (

live a life wituhout fear!

) :angel:

Even more when I read this here (https://xdaforums.com/galaxy-nexus/...-2-7-1-0-touch-recovery-t1592689/post73344977) that the hardware encryption in the galaxy nexus is FULLY OPEN SOURCE :victory:
[Samsung Galaxy Nexus] lippomano:
google play services has stopped continuosly

Hi I follow the guide and I have flashed many other rom but now with lineage 13 on galaxy nexus (maguro) when I install arm-6.0-pico gapps and reboot I see that google play and other gapps has stopped.

I try to follow this install webview implementation but of course in lineage 13 there isn't.

What I can try to do?
[Samsung Galaxy Nexus] guest4711:
Did you really follow the instructions in post #1, especially regarding no reboot between flashing ROM and g-apps?

Google Apps can be found at [URL]http://opengapps.org/?api=6.0&variant=pico[/URL] - beware that only the pico version will fit, unless you [URL="https://github.com/Lanchon/REPIT#lanchon-repit"]change your partition sizes[/URL]! Also, starting from M, it's recommended to install gapps before the initial boot so the permissions are properly set up.
[Samsung Galaxy Nexus] lippomano:
did I am constrained to use adb: adb push filename.zip /sdcard/ ? (I have just copy-paste the zip to sdcard)

Or maybe is because I have old version of twrp (2.5)?

I didn't reboot after flash lineage, I try wiping cache and dalvik and without wiping cache and dalvik before install gapps but doesn't work
[Samsung Galaxy Nexus] Android-Andi:
Use twrp 3.x
[Samsung Galaxy Nexus] guest4711:
Simply copying it to sdcard is ok. You should not use an old TWRP, try it with the newest one from here: https://xdaforums.com/galaxy-nexus/...-2-7-1-0-touch-recovery-t1592689/post73421863

And have a look at the messages when flashing g-apps: Potentially you may run out of space if your systems partition is too small.
[Samsung Galaxy Nexus] lippomano:
With twrp 3 all works fine
[Samsung Galaxy Nexus] guest4711:
Thanks for reporting back...
[Samsung Galaxy Nexus] hga89:
Yes, I have that same problen, even with the latest nightly from last week.

---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------

I am now running the nightly from last week on two GNs, one encrypted, the other one still unencrypted. I continue to have some problems with the phone running with encrypted file system (I have not seen any of the problems below on the unencrypted phone but I do use the latter less right now):

- It sometimes reboots on its own when I am not using the phone, suddenly I just see it's back on the password screen.

- It seems every other time I boot, it hangs on "starting apps" after the password has been entered. I then reboot and this time it works. I have not seen it hang on the Google logo any more.

- Sometimes the networks is not initialized (shows -1) in the setup menu. The only way to resolve this is to reboot and then it may hang, see above.

Otherwise it works very nicely and it is such a difference from CM 10.2 I used to run! Thank you!
[Samsung Galaxy Nexus] entux:
i switched to 14.1 as my daily driver and my wlan woes went away.
[Samsung Galaxy Nexus] hgmichna:
LineageOS 13.0 to 14.1

Which version is that? A beta test version of LineageOS?
[Samsung Galaxy Nexus] entux:
this one https://xdaforums.com/galaxy-nexus/development/dev-lineageos-14-1-t3649194 and yes it works fine (for me anyway).
[Samsung Galaxy Nexus] guest4711:
See [DEV][α] LineageOS 14.1 [maguro][2017-08-14] - https://xdaforums.com/galaxy-nexus/development/dev-lineageos-14-1-t3649194/post73228162

Edit: [MENTION=4653019]entux[/MENTION] was faster. ;)
[Samsung Galaxy Nexus] hgmichna:
LineageOS 13.0 to 14.1

Good to hear, thanks!

It says, "Status: Alpha". I will consider testing it too.

Getting Android 7 on this phone is a miracle!
[Samsung Galaxy Nexus] osm0sis:
Hmm.. are the Recents/Overview display glitches fixed in that 14.1 fork?
[Samsung Galaxy Nexus] lippomano:
Is It possibile ti play Pokémon go with this Rom in the galaxy nexus?
[Samsung Galaxy Nexus] MrFlashGame:
Yes. But you need to pass the Safetynet test to play Pokemon Go I think. That means no Xposed and Magisk root (if you need root) to bypass googles checks and to play Pokemon Go.

Greetings Nils
[Samsung Galaxy Nexus] osm0sis:
Hmm I tried to encrypt to test [MENTION=5153662]Android-Andi[/MENTION]'s updated TWRP, but the device just soft boots to the boot animation and then stays there. I hard rebooted it after 1.5 hours and it booted fine so no encryption appears to have taken place.

Any ideas?
[Samsung Galaxy Nexus] gorgooger:
Um ... yes, don't encrypt ...

Yea, I know, sounds like a dumb and lazy answer, but as long as encryption is not supported, you should not use it.

I tried myself, and there is no chance to make it work at the moment, as fas as I know.

You will have to go into rescue mode and do a factory reset, so sorry.

---------- Post added at 09:27 AM ---------- Previous post was at 09:20 AM ----------

Does anybody know whether MHL or wireless display is going to be implemented anytime soon?
[Samsung Galaxy Nexus] magur0:
Wierd! I have my LOS13 encrypted since long time (since it's released?) and before I was running CM13 with encryption. Till now only problem was that TWRP couldn't handle the decrypt process and upgrades needed to be sideloaded via adb. But these times are over since august this year :fingers-crossed:

[MENTION=5153662]Android-Andi[/MENTION] (and other participants like [MENTION=6979267]nailyk[/MENTION] & [MENTION=2633638]Ziyan[/MENTION]) have created a TWRP with working decryption (Version 3.1.1-1 from August 24th)

Don't use it unencrypted! (no lazy answer! true! so true!)

EDIT: for MHL...

I'm not sure but I think it's not supported and nobody is working on it.. IIRC there is some proprietary code included -> no fun!
[Samsung Galaxy Nexus] gorgooger:
Ah, I just realized that miracast actually can work.

It doesn't work with a renkcast2 stick, but with windows10 as sink.
[Samsung Galaxy Nexus] osm0sis:
Must have been an older version where encrypting worked then, perhaps before the LOS rebrand. Hopefully one of the maintainers can look into it at some point now that we've got a recovery that can handle it again. :good:
[Samsung Galaxy Nexus] Android-Andi:
Got a dmesg and logcat from failed decryption?
[Samsung Galaxy Nexus] osm0sis:
It's not decrypting that's the problem, it's encrypting (under Security | Encrypt phone) that's not working. I'll try and get a logcat and dmesg, hopefully it'll grab something useful before the soft reboot likely breaks the connection.