yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] PGHammer:
That is precisely what is being worked on (by a few folks, including Android-Andi) - the Galaxy Tab 2 (also from Samsung) has (literally) the same flaw. Therefore, it's not merely a Lineage problem; it's also an AOSP problem. (Said problem is also why I did a dual-pull of Unlegacy, so I can self-compile 7.1 while waiting on the cookie to finish baking - 7.1 and 8.0 are not in the same folder - nor on the same update schedule; in fact, 7.1 will be synced weekly (so will 8.x) - however, they will NOT be synced the same day of the week. The only reason that the sync schedule would change for 8.x is if I managed to get a device that supports 8.0 now - such as a Pixel - which I don't see happening (me not wealthy - independently or otherwise).

---------- Post added at 01:45 PM ---------- Previous post was at 01:38 PM ----------

Nice to see that Magisk has other uses besides guarding SafetyNet (that was originally why I switched to it from SuperSu) - even though none of my plastic is compatible with Android/SamsungPay (rats).
[Samsung Galaxy Nexus] yossSP:
Thanks [MENTION=5153662]Android-Andi[/MENTION] , and what about MM 6.01? :)

---------- Post added at 01:04 AM ---------- Previous post was at 12:53 AM ----------

I can confirm that on last MM 6.01 UA ua_tuna-6.0.1-20171004215110, Kernel Adiutor don't show any color adjustment.
[Samsung Galaxy Nexus] Android-Andi:
Some patches didn't applied and need to check if they are need to be adapted or if these simply don't apply.

Real life work is really hard ATM and some different private life stuff I need to care about...

Be patient and we'll push security updates like always, once it's ready.

Thanks, so looks like it's only using the old sysfs... Mh...
[Samsung Galaxy Nexus] kerpert:
Ziyan has definitively stopped to work with GNex?
[Samsung Galaxy Nexus] Android-Andi:
No. He's always behind the scenes active :)
[Samsung Galaxy Nexus] grognaz:
Hey, had to dust of my gn since my 5x is out for a repair and i encountered a error in twrp when i tried to flash gapps, i tried different ones, banks and open gapps and different versiona but none worked:(

Is this a known issue? I tried to install the 7.x rom, might it be related to this?
[Samsung Galaxy Nexus] guest4711:
Did you resize your System partition to 1GB?

If yes, check the partition on TWRP: Goto wipe - advanced - (select system) - resize. The partition size may be rendered to a lower size while flashing the ROM. So it may be necessary to adjust it to the real size before installing g-apps... No data will be destroyed when doing the adjustments. The filesystems tables will be updated to contain the correct values.

If not, have a look at the very good guide at [TOOL] Lanchon REPIT: The Data-Sparing Repartitioning Tool For Android - https://xdaforums.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036/post66344372
[Samsung Galaxy Nexus] grognaz:
Hm i need to check the system partition size, but i noticed that in titanium ther is 0 left on they system which might explain the super bad performace i have right now:eek:

What is the default or a good size for the system partition? Or will twrp know how to resize?

Edit: titanium backup shows 700mb sytem rom partition and 33mb free
[Samsung Galaxy Nexus] guest4711:
You need 1GB if using pico G-apps. Launchons repit (see link above) should give you this size by shrinking the (normally useless) cache partition without dataloss...

TWRP does not know how to resize, but it can correct the displayed valued to the real ones (it compares the values of the filedystem, which may be overwritten by new ROM, against the real values from the partition table and corrects it if necessary. So it can be useful to check in TWRP first.
[Samsung Galaxy Nexus] Max1306:
Hello! My Akku discharges very quickly even when the device is turned off. Is this caused by TWRP? I know, the battery is old, maybe to old.

Max
[Samsung Galaxy Nexus] runekock:
Hi Max

If the battery discharges within less than a month with the phone off, then you have a hardware problem. Most likely the battery, but it could be the mainboard as well.

But first make sure that the phone is truly off. It is possible for a phone to hang with the screen off, and still consume a lot of power. You can make sure it is off by removing and reinserting the battery.
[Samsung Galaxy Nexus] grognaz:
i always got a issue that the data partition could not unmount or got mounted again, turned out that i used some "unofficial" twrp version which caused this, once i flashed twrp-3.1.1-0-maguro.img it worked. great lets start flashing roms:cyclops:

thanks for your help
[Samsung Galaxy Nexus] guest4711:
Glad to hear. Happy flashing!
[Samsung Galaxy Nexus] Younex:
Hello, can you please link to where you found twrp 3.1.1 for maguro ? :eek:
[Samsung Galaxy Nexus] guest4711:
As usual: https://eu.dl.twrp.me/maguro/
[Samsung Galaxy Nexus] Younex:
Thanks ! I had no idea our maguro was maintained, seeing how ghost was dropped long ago... And the maintainer is Ziyan ! :eek:

Gonna try it asap :D
[Samsung Galaxy Nexus] Max1306:
After (dirty) flashing Version 20171026 the device persists during reboot on the "Google-screen". I tried several times, also with full wipe, also waiting over night. Now I try version 20171019 - more than 45min the device hangs on "Google-screen". TWRP works. Are there known problems with this versions?

Max
[Samsung Galaxy Nexus] Android-Andi:
UA 6.0 or 7.1?

What gapps you used?

What TWRP version you use?

Note: UA doesn't support F2FS, if you have used e.g. Lineage OS and switched to UA make sure you format back to ext4.
[Samsung Galaxy Nexus] Max1306:
I had version 20170918 running before. I only wanted to update.

Gapps are 7.1

TWRP is 3.0.2-0 (corrected)

Android 7.1.2

All is the same, what had worked with version 20170918.

Max

P.S. I will try it again after updating TWRP.

2. P.S.: With TWRP 3.1.1-0 the same problem. Freeze in Google-screen during first boot.

3. P.S. Version 20170918 is working.
[Samsung Galaxy Nexus] Meins321:
[MENTION=8606475]Max1306[/MENTION] i have the same problem how did you solve it?

i can't boot with the current maguro version, twrp still works... how can i "push" files to my gnex to use the older version "20170918"? The latest one doesn't boot after flashing

My system partition is ext4 but smaller than 1GB..

i will download the older version and test 7.1 from 18.09...
[Samsung Galaxy Nexus] guest4711:
Yes, wipe -- advanced -- (choose system)
[Samsung Galaxy Nexus] Bludwurst:
If you have a PC available, you can use adb to push files into your phone's internal memory.
[Samsung Galaxy Nexus] Max1306:
I've flashed the version 20170918 again and everything is ok. If you dont't have the rom on your Galaxy Nexus, then you can put it via MTP to the device. With TWRP it is possible.

Max
[Samsung Galaxy Nexus] Meins321:
Thank you everyone got it booting again with twrp and my old 6.0.1 rom, this thread suggest it is for the galaxy nexus is9250 but i downloaded mako rom not maguro..

ok have to use the tuna version woops ^^
[Samsung Galaxy Nexus] Bludwurst:
Under device name "tuna" (named so since it works on all Galaxy Nexuses — toro, toroplus and maguro)

edit: ninja'd by you :silly:
[Samsung Galaxy Nexus] Meins321:
Updater process ended with ERROR: 7

Error installing zip file '/sdcard/ua_tuna-7.1.2-20170918073244.zip'

well that didn't work grr

if i unzip the rom:

ua_tuna-7.1.2-20171026053552\META-INF\com\google\android\updater-script contains the version checks, can i modyfy it to force flash it with a maguro setting?

PS: Over the air update would be nice but i can check the thread more often if it runs :P
[Samsung Galaxy Nexus] guest4711:
Are yo shure you updated to the right TWRP?

And yes, you could modify the version check if necessary. But if yout TWRP is correct you shouldn't need...
[Samsung Galaxy Nexus] Meins321:
TWRP 3.1.1-0 for maguro? This one the latest version https://eu.dl.twrp.me/maguro/

Do i need to use REPIT to create 1GB system partition? mine is 786MB and even without gapps i cant flash or boot.. Do i need this repit file: https://androidfilehost.com/?fid=529152257862695641
[Samsung Galaxy Nexus] guest4711:
1. yes, should be right. Or use [MENTION=5153662]Android-Andi[/MENTION]'s 3.1.1-1.img on https://andi34.github.io/recovery_tuna.html which support hardware decryption

2. yes if you need g-apps.
[Samsung Galaxy Nexus] Meins321:
THANK you got it working:

1. Update your TWRP to the latest version, download img file flash and reboot

2. reboot directly to twrp, use repit script and parttion system to 1GB filesize and run it from /tmp directory

3. wipe dalvik and cache and then flash aosp zip file from this thread

4. flash gapps pico or micro

5.flash super su

gsm magura have fun :P
[Samsung Galaxy Nexus] guest4711:
Glad it worked. Happy phoning ;)
[Samsung Galaxy Nexus] OttawaNoLuck:
No luck with my Galaxy Nexus (Maguro)

Greetings! Thanks for all of the helpful info on this forum. Unfortunately I can't get it to work on my phone. I want to get to the point where I can build Unlegacy Android myself and install it on my Galaxy Nexus (Maguro) but I decided to first get the off-the-shelf .zip working first (in case my build is broken).

So here's what I've done, based on the steps from Meins321:

1) I installed TWRP 3.1.1.0 from here:

eu dot dl dot twrp dot me/maguro/twrp-3.1.1-0-maguro.img.html

2) I rebooted into TWRP and then ran the repit script from here:

androidfilehost dot com/?fid=529152257862695641

This seemed to change the /system partition to 1GB with no errors.

3) After repit finished, I think there was an option to wipe dalvik and cache, so I did that, again, no errors.

4) I downloaded the latest Unlegacy Android, copied it to the phone, and installed it from here, I did not see any errors:

builds dot unlegacy-android dot org/aosp-7.1/tuna/ua_tuna-7.1.2-20171026053552.zip

5) I downloaded gapps micro and tried to install it but it said there was not enough room. So I downloaded gapps pico and installed it, it seemed to install fine with no errors. I downloaded from here:

opengapps dot org/?api=6.0&variant=nano

6) I downloaded SuperSU and installed it from here (again, no errors):

download dot chainfire dot eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip

I then rebooted my phone and see the "Google screen" on the phone. It never gets to the animated boot logo. I've left it for 6+ minutes, is that long enough? How long should it take to get to the animated logo?

What kind of information do you need from me to help me out? Is there a way to log debug information while it's stuck in the "Google screen"?

Luckily I made a backup first and restoring it works... when I check About Phone it says:

Model number: Galaxy Nexus

Android Version: 4.2.1

Baseband version: I9250UGLL1

Thanks, and keep up the great work (hopefully I can help out at some point).
[Samsung Galaxy Nexus] Meins321:
4) you should download 20170918 thats what boots and works fine, just my gps can't be on it is missing

Please flash 7.1.rom.zip first than repid zip file from temp (just the normal way and let it fail go to mount unmount anything and then flash from temp repid script)

then flash gapps

If repid worked there should be 999MB space on /system which you can see in twrp under wipe and then tick the /system box and look under advanced (just don't wipe it)

the repid script only worked from /tmp directory after it failed from sdcard before (copied itself to tmp and i ran it after i unmounted all other partitions under mount)

lanchon-repit-20170115-system=1G-cache=62M+wipe-data=same-maguro.zip

https://androidfilehost.com/?fid=529152257862695641

From What i can see is that repid did not work on your device, gapps micro and more fits just fine...

R1. no reboot out of twrp after repid

R2. run repid from /tmp or let it fail and then run it (selfcopies to /tmp)

R3. check if it worked with twrp->wipe->advance wipe->checkbox /System ->"Repair or Change"->look at the size is it 999MB -1001MB??

Please try this rom version:

ua_tuna-7.1.2-20170918073244

https://builds.unlegacy-android.org/aosp-7.1/tuna/ua_tuna-7.1.2-20170918073244.zip

https://builds.unlegacy-android.org/aosp-7.1/tuna/ua_tuna-7.1.2-20170918073244.zip.md5sum

anything else won't boot on my is9250 16GB GSM Version :P

[MENTION=2633638]Ziyan[/MENTION]

ua_tuna-7.1.2-20171026053552.zip doesn't boot it hangs

ua_tuna-7.1.2-20171019033615.zip same :(
[Samsung Galaxy Nexus] Max1306:
See my post #1818 - I'm back to Version 20170918. The versions 20171026 and 20171019 don't work - hanging in Google-screen.

Max
[Samsung Galaxy Nexus] runekock:
[MENTION=8682342]OttawaNoLuck[/MENTION]

What happens is that the rom contains a smaller system image, so when you flash it, the file system is reduced in size, even though the repitted partition is still 1GB.

Just use TWRP's resize function (I think it is under advanced wipe) after flashing the rom, and before flashing the rest. It resizes the file system to be the full partition size.
[Samsung Galaxy Nexus] OttawaNoLuck:
/system size looks ok...

Thanks! I overlooked the information in the previous posts about the newer versions not working. I'll try the 20170918 version when I have some free time and see if it works. I would like to get the latest versions working if possible and would like to help (if I only knew how).

Do you know how to checkout a specific version to build myself (like 20170918)? Maybe a diff between that version and the latest version might shed some light on things...

Out of curiosity, I checked the /system partition information just now in Wipe under TWRP, it looks ok to me, it shows:

Mount Point: /system

Present: Yes

Size: 1007MB

Free: 574MB

Removable: No

Used: 433MB

Backup Size: 433MB

So doesn't that mean it's 1GB and the repit script worked fine previously?

Is it possible that the newer versions (after 20170918) need more than 1GB in /system and is there a way to check this?

---------- Post added at 10:59 PM ---------- Previous post was at 10:51 PM ----------

Do you think this will get the latest version to work? Will I still be able to restore the backup in case it fails?

So if I understand correctly, the steps should be something like this:

1) Install TWRP 3.1.1.0 from here (if not already done):

eu dot dl dot twrp dot me/maguro/twrp-3.1.1-0-maguro.img.html

2) Reboot into TWRP and then run the repit script from here (if not already done):

androidfilehost dot com/?fid=529152257862695641

3) After repit finished, wipe dalvik and cache.

4) Install the latest Unlegacy Android from here. Or should I go back to 20170918?

builds dot unlegacy-android dot org/aosp-7.1/tuna/ua_tuna-7.1.2-20171026053552.zip

5) Use TWRP's resize function on the /system partition. Will it know the proper size or will I need to specify a precise size?

6) Install GApps from here. I'll try micro again and see if it fits after the resize above.

opengapps dot org/?api=6.0&variant=nano

6) Install SuperSU from here:

download dot chainfire dot eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip

7) Reboot phone and it should boot fully.

Thanks for your help!
[Samsung Galaxy Nexus] bamtan2:
If the builds are broken, the builds are broken, and that's it. And if these guys are telling you the builds are broken, THEY'RE BROKEN. :) This is not a professional operation. Everything is made by volunteers with minimal testing.
[Samsung Galaxy Nexus] Android-Andi:
I've started a clean build on our Jenkins, should be available in about 1 hour if someone likes to give it a shot. Else I'll try to look at it in the evening.

Someone got a dmesg or last_kmsg from the not booting builds?
[Samsung Galaxy Nexus] _MOCKBA_:
Same problem as before for me. Doesn't boot past google logo.
[Samsung Galaxy Nexus] Android-Andi:
Can't confirm, just tested it on my maguro.

What i have done:

Format data -> confirm by typing "yes" (note: deletes the whole internal storage!)

advanced wipe: cache, dalvic/art cache, system

reboot recovery

install the rom via 'adb sideload'

boot into system

I haven't flashed any root method and i also haven't flashed any gapps.

I am using my own compiled maguro_TWRP_3.1.1.
[Samsung Galaxy Nexus] Android-Andi:
It's a nougat rom

Why using Marshmallow Gapps on Nougat Rom?

Not sure if it's compatible with October bulletin patches
[Samsung Galaxy Nexus] _MOCKBA_:
If it would help, what I did differently is:

1. I didn't format data, but factory reset, i.e. wiped caches and system

2. installed from internal storage

3. installed pico GApps.

Does GPS work in any N rom?

Off-topic: I couldn't get Pokemon GO to work again on maguro with any rom. It used to work with CM 12 and CM 13 last year until SafetyNet thing. CM roms are failing SafetyNet consistency check even unrooted. With any Lineage rom I tried strangest thing happens - Pokemon GO is unresponsive to touch, so I cannot get past initial "choose your birthday" screen. Lineage roms do pass SafetyNet though. I couldn't see what could be wrong with Lineage roms. They Antutu about the same and leave more memory for Pokemon GO, but Pokemon GO is not responsive to touch. Any idea what changed between CM and Lineage that could make Lineage no go with Pokemon GO and what rom I should try next?

(I kinda wanted to give my maguro to kids but couldn't set it up for them).
[Samsung Galaxy Nexus] Max1306:
[MENTION=428274]moscow[/MENTION]

GPS is working with Nougat (version 20170918). The Galaxy Nexus receives GPS only. No GLONASS, no Beidou.

Max
[Samsung Galaxy Nexus] aboaboit:
That's an interesting tool, thanks.

What would be a sample filename to use as REPIT parameter to get a working partition layout in order to install this ROM, with GA nano and SuperSU?

I couldn't find example, either here or in the dedicated thread.

---------- Post added at 07:43 PM ---------- Previous post was at 06:54 PM ----------

It's out of specs, one should be happy it works :)

Mine would have very unstable connections on the 5GHz band (with ZZrom) in close proximity of the AP, whereas my 5X would hold fine, so I ended up disabling it for the sake of stability.
[Samsung Galaxy Nexus] bamtan2:
It's kind of unclear, but basically repit takes its inputs from its file name, so it comes with correct default settings. You just flash the rom, flash repit, and flash the gapps, all in that order.
[Samsung Galaxy Nexus] aboaboit:
Thanks for this ROM, I'm trying it out right now. Flashed packages in the following order, using TWRP 3.1.1:

ua_tuna-7.1.2-20171030050427

open_gapps-arm-7.1-pico-20171101.zip

UPDATE-SuperSU-v2.82-20170528234214.zip

then I wiped cache and rebooted.

I'm coming from many months of ZZrom with "nano". I went with "pico" after "nano" failed to install due to space limitations.

Phone is stuck at "Google" with a padlock, it's been already a few minutes. My spider sense tells me this isn't nominal ;)

What have I done wrong? Files were checked with signatures after downloading.
[Samsung Galaxy Nexus] Android-Andi:
Don't flash SuperSU, see if it works without that.

If still not working, don't flash gapps.

That way you'll find the breaking bit ;)
[Samsung Galaxy Nexus] bamtan2:
When this sort of thing happens to me it's just some mistake I made. Double check everything, wipe everything, and try again.
[Samsung Galaxy Nexus] aboaboit:
That's what (I think that) I did, before posting. Is there a way with TWRP to recreate the empty partitions so nothing can interfere?

I'll try REPIT with default values as per your other post, thanks.

EDIT: haven't had time to try REPIT yet, but when trying to wipe TWRP complains a lot... "failed to mount" storage, cache, system, data

(additionally, the TWRP settings are not saved but this might be related)
[Samsung Galaxy Nexus] nrichard7029:
Have you tried re flashing the boot loader partition? Try downloading the latest system image from google and extract the bootloader.img from it. Just flash it through the existing bootloader.

https://developers.google.com/android/images
[Samsung Galaxy Nexus] aboaboit:
Tried flashing lanchon-repit-20170115-system=958M-cache=128M+wipe-data=same-maguro.zip: it failed during dry-run because p12 (userdata) has a bad magic number.

I've tried running the suggested e2fsck via adb shell but the response doesn't look good:

e2fsck -f /dev/block/mmcblk0p12
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p12

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # e2fsck -b 8193 -f /dev/block/mmcblk0p12
e2fsck 1.42.9 (28-Dec-2013)
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p12

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

Since I don't care about userdata I also tried:

~ # mkfs.ext2 /dev/block/mmcblk0p12
mkfs.ext2: lseek: Value too large for defined data type

This is how the partition table looks right now:

~ # fdisk /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT

Command (m for help): p
Disk /dev/block/mmcblk0: 30777344 sectors, 2740M
Logical sector size: 512
Disk identifier (GUID): 52444e41-494f-2044-4d4d-43204449534b
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30777310

Number Start (sector) End (sector) Size Code Name
1 256 511 128K 0700 xloader
2 1024 8191 3584K 0700 sbl
3 8192 49151 20.0M 0700 efs
4 49152 65535 8192K 0700 param
5 65536 73727 4096K 0700 misc
6 73728 81919 4096K 0700 dgs
7 81920 98303 8192K 0700 boot
8 98304 122751 11.9M 0700 recovery
9 122880 155647 16.0M 0700 radio
10 155648 1495039 654M 0700 system
11 1495040 2379775 432M 0700 cache
12 2379776 30777309 13.5G 0700 userdata
13 122752 122879 65536 0700 metadata

Any tips?
[Samsung Galaxy Nexus] Android-Andi:
Can we stay on topic? Repartitioning isn't related to this rom...
[Samsung Galaxy Nexus] guest4711:
Try to check/resize the partition with TWRP (wipe -- advanced). Or try to change the type (ext4fs -- f2fs - ext4fs). Probably the volune is/was encrypted...
[Samsung Galaxy Nexus] aboaboit:
Well, since the trouble started when I tried to install this rom it seemed reasonable to continue the discussion here: for all I knew I might have uncovered a bug.

Repartitioning was just an attempt to fix the installation errror, not the end game itself. Sorry for the trouble.

[MENTION=4545566]bamtan2[/MENTION] look like my phone has a bad eMMC firmware

If I can somehow fix it, I'll try this rom again, otherwise thanks for your help :)

EDIT: right, from the adb shell I could not recreate the filesystems but TWRP was able to do that and, to top it off, repit also ran just fine.

Still unsure about the state of the eMMC but let's pretend it's fine and move on.

I tried to flash the same three packages as when I started:

ua_tuna-7.1.2-20171030050427.zip

open_gapps-arm-7.1-nano-20171101.zip

UPDATE-SuperSU-v2.82-20170528234214.zip

The first one succeeds, then GA complains: "INSTALLATION FAILURE: This GApps package can only be installed on a 7.1.x ROM."

I am trying to boot it anyway and it is still hanging at "google"... some more testing / checking to do, then.
[Samsung Galaxy Nexus] aboaboit:
I have to thank [MENTION=8606475]Max1306[/MENTION] for his post regarding version 20170918, which was working for him on maguro.

Together with GA nano from today, it seems to be at least booting :) and possibly also working, I'm setting it up right now.
[Samsung Galaxy Nexus] Android-Andi:
Latest one boots too as you can see.

Edit:

I am sure SuperSU you guys flashed is not compatible with October Security Bulletin and the reason for your booting issues