yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
The log unknown command errors aren't anything to worry about.. TWRP 3.0.3+ has support for it, but in the mean time they don't affect anything.

The no OS thing occurs sometimes with system.dat zips, and usually it worked fine, you just need to reboot recovery after installing the ROM so that it'll register the block write to the system partition, and then you can then install SuperSU and GApps.
[Samsung Galaxy Nexus] Ziyan:
I'm extremely busy with my last finals; maybe in 2 weeks or so :)
[Samsung Galaxy Nexus] phaleg:
Please, hope it will be a MM :D
[Samsung Galaxy Nexus] thagringo:
[ROM][AOSP][Unified] Unlegacy-Android (prev. OMAP4-AOSP) (10/21, 7.1!)

Nice, would you mind Sharing your Build ?

Really Interested in a Build with the microg stuff included.

Happy New Year everyone !!!!
[Samsung Galaxy Nexus] roby02091987:
Hello everyone, and happy new year!

First things first: thank you very much for your work, Ziyan!

I've installed 7.1 21/10/2016 version on my galaxy nexus and it works like a charm... it has never been so smooth and snappy.

But it has only one issue: gps does not work. I was thinking i might revert back to mm, does gps work with it?

Is there or will there be a way to fix gps in 7.1 version?

Thanks again... and very sorry for my english. I hope I didn't make too much mistakes :silly: .
[Samsung Galaxy Nexus] miomaguro:
Thanks for your suggestion: at the end I installed Nova launcher and Xposed module with Gravity Box MM and... Wow! I have a brand new and perfectly working Galaxy Nexus really as I like it! Many many thanks for this amazing ROM. :good:

Edit: I've just found one annoying bug related to the browser, that is it regularly crashes whenever you try to download anything (files or images). Is it true only for me? I'm using the Marshmallow version.
[Samsung Galaxy Nexus] martytoo:
I'm embarrassed to say that when I installed the 7.1 ROM on my Nexus and then tried to install the GAPPS listed in the second post I got an error message that the GAPPS were not compatible. I had downloaded them straight to the phone. I don't know if perhaps that is why or how I downloaded the wrong GAPPS. Worse yet CWM warned me that it detected that I no longer had root and the CWM said it could attempt to re-root for me (before the first boot). I agreed to reroot attempt but I am no longer rooted. Worse yet the Google Play services says that it needs to be reinstalled. I tried to do that by sideloading it from my phone but that didn't work either.

So here are my questions.

What is the best way to re-root?

Which recovery should I install?

Which GAPPS should I download into the phone and then use during the flash (or if I skip GAPPS what will I be missing)?

I use this phone as a music player. I have no SIM card in it for use as a phone.

Thanks in advance. I'll keep reading the older posts here hoping to find the answers, too.
[Samsung Galaxy Nexus] bamtan2:
I think it may be broken now and need to be reflashed. You will download 7.1 and smallest 7.1 opengapps and newest TWRP ( https://twrp.me/Devices/ ) (not CWM). You will flash TWRP, reboot, factory reset and flash 7.1 and 7.1 gapps without rebooting between. Backup important data first. Let us know if it worked!

I think this information is out of date! Download the very smallest opengapps, "pico"!
[Samsung Galaxy Nexus] martytoo:
I still need a little help as to how to re-root the phone. I rooted it once when it was brand new in 2011, I think. What is the easiest way to re-root?

Also, I thought I read that the "factory reset" was the one part of the flashing that should be skipped. Someone posted that this wipes out the IMEI code. Was that incorrect? I wiped system and wiped cache but not factory or data. With no SD card I assume if you wipe data that you have to load the zip files for the ROM and GAPPS by way of a PC. Is that correct?

Thanks for your quick reply!
[Samsung Galaxy Nexus] gialakias:
Do the procedure to install twrp recovery, rom and gapps and as soon as everything is ok, reboot to recovery and flash the latest supersu zip sr1 2.79 and you are rooted. It is very simple. Also use the advanced wipe in twrp excluding the internal storage and you are Ok. It is mandatory to format data coming from another rom.
[Samsung Galaxy Nexus] bamtan2:
There should be a guide that explains this because we're bound to make mistakes repeating it every time. :)

The ROM flash wipes /system every time, and "root" is just some files flashed to /system. So you'd flash the ROM and then flash the root package.

"Factory reset" is a standard term that means wiping the OS information stored on /data, but not your personal information on /data/sdcard or whatever it is. It's confusing I know. But in TWRP you'll see the option for a factory reset, and it'll just wipe the mind of your OS, but it will still be there. It is normal to do a factory reset when flashing any new ROM because every ROM uses different data, and they will break if they don't start with something they understand. Flashing without factory reset is called "dirty flash".

The reason your system is broken is because the opengapps installation is broken and it is not possible to repair broken gapps.

I recommend using one of the two GUI tools/toolkits for ADB found on this forum, because they help take care of things. I personally bought https://skipsoft.net/skipsoft-unified-android-toolkit/ !
[Samsung Galaxy Nexus] phaleg:
GPS works on mm
[Samsung Galaxy Nexus] martytoo:
Thanks to all three (or more) members who helped. When using CWR I had no idea why GAPPS didn't install. Once I used TWRP I received the error message that GAPPS nano was too big for the system partition.

I downloaded pico and things seem fine. bamtan2, you were correct to use pico. I assume there is no way to make the partition a bit bigger and reflash. I hope everything installs for my needs. This ROM, even with my broken version, seemed better than the last CyanogenMod that was on the phone until yesterday.
[Samsung Galaxy Nexus] martytoo:
All is well except I do not have root. Because this is being used as a media player and a remote for ROKU, Firestick and Alexa (Alexa was the culprit as "she" would not install on 4.3.1 ), the only problem I really have with no root is not being able to run Adaway.

I'll have to see whether this drives me on a quest to reroot.

As mentioned above, the second post should be edited to reflect the need for a very small GAPPS with this ROM.

But thanks x four for all the help. Three posters and the developer all get a big thumbs up. I never thought I would see this relic work so fast with a current OS!
[Samsung Galaxy Nexus] martytoo:
I have one more favor to ask. SuperSU binary is not updating. This means that even though Root Checker shows that I am rooted the Adaway app won't work because the binary isn't updating. Many users of SuperSU are having this problem. I am wondering if an older version is available that will work.

To root I cleared with a wipe and then used adb sideload to load the ROM and GAPPS Pica. I also installed SuperSU after GAPPS. But when I boot there is no binary update as far as I can tell.

One of the ideas is that the binaries don't load because the phone was rooted before the SuperSU. I cannot understand how the unroot and then reroot the phone. The unroot function in SuperSU does not work. The only app needing root that will not work is adaway - Root Explorer, Titanium Backup, and Busybox all work.

Thanks again.
[Samsung Galaxy Nexus] bamtan2:
These sound like problems with supersu and adaway, not this rom :) Visit their forums:

supersu: https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

adaway https://xdaforums.com/showthread.php?t=2190753
[Samsung Galaxy Nexus] martytoo:
Yes, you are correct. SuperSU doesn't seem to consistently update binaries. This ROM is great for my purposes, but even more amazing is that I could use this old phone as my daily carry cell phone if something happened to me S5.

I will post an answer here if I find one.
[Samsung Galaxy Nexus] amine a.b.i:
is there any new build (nougat) coming soon with bug fixed for the maguro ??
[Samsung Galaxy Nexus] girkev:
That's is a Hardware damage?

The battery unloaded to zero although the phone was shut down.
[Samsung Galaxy Nexus] runekock:
My guess is that your phone had crashed, and wasn't really off. Try looking at last_kmsg, that may say something. Without more info, there is no way to know whether it is a hardware or software problem.
[Samsung Galaxy Nexus] girkev:
No crash. I did the shutdown. But I'll take some .logs. And post them/it here .

Thanks for your guess.
[Samsung Galaxy Nexus] girkev:
Here it is. I'm unable to find the reason for the battery loss.

I'd be very glad if you could tell me.
[Samsung Galaxy Nexus] girkev:
Here the log file and another weird behavior. Almost 49% consumption for others? What's that?
[Samsung Galaxy Nexus] mlsoftlaberge:
Yes this is hardware damage, of some sort.

The battery of the galaxy nexus is 5 years old, and does not retain the charge a long time.

In my case, two hour of use max before recharging.

Or 16 to 18 hours, when Idle.

or 10 photos with flash, and the battery is 0%

Did someone managed to find new batteries for the galaxy nexus, and how much does it cost?
[Samsung Galaxy Nexus] Punkiderma:
I searched them for a lot of time. Bought like 5 or 6 of them.

For my experience:

- original batteries (from Samsung, with NFC antenna) are impossible to find

-All the batteries you see with Samsung sticker are fake, so they don't have the NFC antenna and doesn't last as long as the original ones

-Compatible batteries that has the same size of the original battery don't last very long

-With a big extended battery you can get almost 4 hours of screen(but I was on KitKat with the old ddk the last time I tried).

They are the only one usable IMHO, but they are big and heavy. The Galaxy Nexus is beautiful, with the extended battery cover it loses a lot of appeal (and it's harder to make it fit into your pocket)

They all costs around 12 €, so you can give them a try ;)
[Samsung Galaxy Nexus] bamtan2:
I bought many batteries, and they are all bad except for one. It is a fake Samsung from an eBay listing that no longer exists. If we could know the real manufacturer, we could ask them to make more. But if I needed to buy another battery today, I would need to buy many batteries again and pray 1 is good.
[Samsung Galaxy Nexus] mlsoftlaberge:
Does someone have news about [MENTION=2633638]Ziyan[/MENTION] , since there is no new posts about the status of our rom for a long time.

Is he to continue to support maguro, and what about LineageOS ?
[Samsung Galaxy Nexus] bamtan2:
He posted in the past few weeks that he is studying and will make a new build when he's ready :)
[Samsung Galaxy Nexus] :
Last year I bought two original batteries directly from Samsung. They had to order them from another service centre but did have them in stock nevertheless. This was in South Korea though. I have no idea if they still sell them in other countries.

They cost around 20,000 KRW (~ 17 USD) each.
[Samsung Galaxy Nexus] eKeith:
https://www.batteriesplus.com/batte...us-_-(uk)-gt=i9250-_-gt=i9250m#finder-box-top
[Samsung Galaxy Nexus] thekoumi:
I need help please

I've flash this rom with the Open GApps Nano via CWM and i had message that GApps not compatible with device system.

After reboot i have lost custom recovery and root. PC cant recognize device. In dev options the usb configuration stuck to charging and i can't change it to any other option. I can't even download a file manager or a web browser. In other words this is a disaster. In the screenshot you can see the only apps that came with this rom. Any suggestion please?
[Samsung Galaxy Nexus] osm0sis:
Open GApps has never supported CWM. Get out of the dark ages and use TWRP. :silly:
[Samsung Galaxy Nexus] bamtan2:
Two things went wrong. You must use TWRP, so find the TWRP thread on this forum. Secondly, the documentation on the front page of this thread is wrong. You must use the very smallest opengapps. Nano is too big.

Sorry it all went bad for you :( Use an adb tool or a nexus toolkit to flash twrp, factory reset, and start over. Good luck! :)
[Samsung Galaxy Nexus] thekoumi:
Thanks for the reply

I've already tried adb sideload and Nexus toolkit. But it's useless. The phone stuck on usb charging and i can't change it to mtp. Two different Pc can't see my device.
[Samsung Galaxy Nexus] thekoumi:
Me caveman

Do you have any suggestion or what?
[Samsung Galaxy Nexus] osm0sis:
Pretty clearly, flash TWRP, then reflash ROM, SuperSU and GApps then all should be well. :)
[Samsung Galaxy Nexus] thekoumi:
Thanks for the reply

Man i need suggestion how to make device visible again to any PC. After that i know what to do. I can't change usb connection thru dev options to mtp or anything else. Stuck on charging...
[Samsung Galaxy Nexus] osm0sis:
Is your bootloader locked or something? Use the key combination to reboot to bootloader and fastboot flash twrp. If it's still not showing up via USB when in the bootloader you've got a bigger problem.
[Samsung Galaxy Nexus] _yen_:
Hello,

have you tried to manually reboot in bootloader and then to flash twrp via fastboot? This worked for me on a soft bricked maguro with damaged recovery.

Yup, osm0sis was faster...
[Samsung Galaxy Nexus] bamtan2:
[MENTION=3390093]MWisBest[/MENTION] [MENTION=2633638]Ziyan[/MENTION] and friends: See this interesting post about F2FS and SuperSU :) https://xdaforums.com/showpost.php?p=70492947&postcount=8793
[Samsung Galaxy Nexus] musical_chairs:
So let me get this straight: If you want to update f2fs beyond a certain point, all your users will need to do a full backup, reformat, and restore? If you apply those kernel fixes, every user on f2fs who installs your ROM will find their phone unable to boot? Or did I read that incorrectly?

That doesn't sound like it qualifies as a usable file system to me.
[Samsung Galaxy Nexus] osm0sis:
Or don't update it and apply those 2 patches. Either way they're required to fix the f2fs issues with loopback mounts/deadlocks affecting SuperSU.

I think you only need to reformat if it corrupts things from using a recovery/kernel without the patches.
[Samsung Galaxy Nexus] vortex-5:
So I guess the main bug with Nougat right now is that GPS is non functional?
[Samsung Galaxy Nexus] _yen_:
You're right, even if GPS seems functional for some peoples (not me); other bug is that ROM should be permissive.

bye

yen
[Samsung Galaxy Nexus] vortex-5:
Cool thanks I'll wait until there's a solution for the GPS before moving over it's a feature I do use pretty often.
[Samsung Galaxy Nexus] hollandais:
GPS works fine, inside home, on mine with one of the rom's you can find in Andi's github.

I uses the 20161231 one.

http://builds.unlegacy-android.cf/aosp-7.1/espresso/

Envoyé de mon Galaxy Tab 2 en utilisant Tapatalk
[Samsung Galaxy Nexus] bamtan2:
What the heck! Where did this come from! :) http://builds.unlegacy-android.cf/aosp-7.1/tuna/

Build servers seem to be popping up everywhere now that CM is gone?! :)
[Samsung Galaxy Nexus] Ziyan:
We still need to create some selinux rules before those 7.1 builds are fully functional though :) but 4.4, 6.0 should be totally fine.
[Samsung Galaxy Nexus] 2450687:
I have the same problem。I must chose 3G for “preferred network type” so that the APN will keep，although my phone only support 2G of

China mobile。I think this will increase the battery consume。

I have other problems：

1. the music player can not use，it shut down immediately after startup。

2. the wifi status is “connected，no internet ”，but surf the Internet and apps is OK。and the connect speed is only 65m，but my another phone is 135m。

Fortunately，my GPS is OK。
[Samsung Galaxy Nexus] phaleg:
Can I update your aosp_mm_tuna_2016-07-25.zip with a MM build from http://builds.unlegacy-android.cf/aosp-6.0/tuna ?

Otherwise, do you think you will release another MM build ?

Thanks :highfive:
[Samsung Galaxy Nexus] musical_chairs:
4.4 builds are good. Mobile data had been broken for me on toro on 7.1 last I tried it, I got frustrated trying to fix it and have been on 4.4 for about two months. It's been nice to have everything just work with no hassle.
[Samsung Galaxy Nexus] fromfree:
I just dirty flashed 20170109 build and apparently all is working as aspected! :good:
[Samsung Galaxy Nexus] 2450687:
I find that the APN will be empty after picking up a incoming call 。
[Samsung Galaxy Nexus] Master94ga:
Someone tried the last rom 7.1 from that link? http://builds.unlegacy-android.cf/aosp-7.1/tuna/

I have the last one available here :)
[Samsung Galaxy Nexus] girkev:
its booting right now

Yet...
[Samsung Galaxy Nexus] Ziyan:
Yes, consider that as my updated builds :) includes everything I used to include in my builds.
[Samsung Galaxy Nexus] Master94ga:
Tell me if it starts please. :)

Also did you did a clean installation or dirty flashed on the last 7.1 available here?
[Samsung Galaxy Nexus] mlsoftlaberge:
I am sorry to report that the ua_tuna-ota-20170114.zip (version 7.1) does not boot on my maguro.

I had to revert to 2016-10-21 to unstick the google logo.
[Samsung Galaxy Nexus] Ziyan:
Unfortunately, until I say so here, none of the updated 7.1 UA builds will boot.
[Samsung Galaxy Nexus] girkev:
All fine. Except the sim has not been detected.

---------- Post added at 06:31 PM ---------- Previous post was at 06:27 PM ----------

My maguro did biot. Bu thet sim won't be detected.
[Samsung Galaxy Nexus] phaleg:
Awesome!

I guess they need pico gapps, correct?
[Samsung Galaxy Nexus] amine a.b.i:
whats the best build for the maguro device
[Samsung Galaxy Nexus] Ascendinghuaweim860:
Have you guys figured out how to get LTE working on the Toroplus? I'm on CM13 But I'm assuming that's dead :(
[Samsung Galaxy Nexus] yossSP:
MarshMallow or Nougat? That is the question...

Hi all, I have installed last MM build from:

builds.unlegacy-android.cf/aosp-6.0/tuna (2017/01/09)

Everything goes well (even GPS), it's fast and reliable. But I have a doubt, should I wait till next Nougat (with GPS functional) or should I stay in MM with everything functional and good performance?

Is N release better in any aspect than MM?, obviously I miss the new improvements in Android N that have developed Google, but I mean general performance and hardware related issues.

I prefer an older Android release, faster and more stable than the newer one with more issues or slower.

Anybody can tell? Thanks in advance!
[Samsung Galaxy Nexus] phaleg:
Stay with MM and enjoy...
[Samsung Galaxy Nexus] yossSP:
Thanks for your response, but... I'll be grateful if you could you explain it more :)
[Samsung Galaxy Nexus] phaleg:
If you read a bit the thread, you will find explanation...

to make it short, MM offers the best ration in performance and you are on a new rom
[Samsung Galaxy Nexus] yossSP:
Perfect summary :good:. Thanks a lot.

That's the perfect reason to stay in MM :)
[Samsung Galaxy Nexus] 2450687:
There is a new update for MM today，is OK？
[Samsung Galaxy Nexus] yossSP:
Yes it is, hot and fresh :)

I haven't installed it yet.
[Samsung Galaxy Nexus] vortex-5:
So right now unlegacy 6.0 is stable and the current UA builds of 7.1 are not bootable?

I flashed the current UA ua_tuna-ota-20170115 that's on the 7.1 branch just for testing and I noticed it sat at the google logo for about 10 min not doing anything the phone wasn't doing any work since it was pretty cool to the touch.

I'll try the UA 6.0 builds since CM13 is dead we're no longer getting security patches there.
[Samsung Galaxy Nexus] hollandais:
The 7.1 are bootable. But you should know that they're not finalized and can give problems.

Sent from my P5110 with 7.1...

Envoyé de mon Galaxy Tab 2 en utilisant Tapatalk
[Samsung Galaxy Nexus] _yen_:
UA 7.1 builds (from unlegacy site) for tuna are generally bootable if you rebuild a permissive kernel to flash from recovery. I say generally because last few builds doesn't boot at all for me even with a permissive kernel on top.

bye

yen
[Samsung Galaxy Nexus] vortex-5:
So has anyone compared CM13 to unlegacy 6.0 performance wise? I hear from some it's the same other's its smoother anyone want to weigh in on this?
[Samsung Galaxy Nexus] vortex-5:
how do you flash without losing TWRP?
[Samsung Galaxy Nexus] osm0sis:
Let TWRP write to system to disable recovery overwrite, or flash SuperSU since it also stops this.
[Samsung Galaxy Nexus] hollandais:
What do you mean with "losing twrp"? You can't lose unless you flash another kind of recovery... Do you mean that you lost root?

Envoyé de mon Galaxy Tab 2 en utilisant Tapatalk
[Samsung Galaxy Nexus] vortex-5:
I mean I flashed unlegacy it and replace the recover with the stock recover from ua_unlegacy so I had to put it back manually with oem unlock. I'll see if super su resolves this in the future.

Is the super SU bug still present causing bootloop?
[Samsung Galaxy Nexus] vortex-5:
Does anyone know if you can hide the google search bar in this rom (6.0.1) ?

I may have to go with another launcher but just checking in case I don't have to.
[Samsung Galaxy Nexus] KillahKiwi:
I'm semi certain you can just uninstall the google search app and the search bar will be gone with it.
[Samsung Galaxy Nexus] yossSP:
You can use Nova Launcher. It can disable/enable/customize the search bar in any ROM.
[Samsung Galaxy Nexus] vortex-5:
Device identification. I noticed after upgrading that the device identifies itself as tuna instead of maguro. This prevents tools like bootunlocker from working so you can unlock recovery flashing without running oem unlock (and wiping all your data first).

Does anyone know how to unlock the recovery via adb / or terminal without wiping user data first? Since an app can do it I'm pretty sure there's a root level terminal command one can execute to enable it. Also I noticed that TWRP 3.0.2 can't seem to save prefs when on UA-tuna vs CM13
[Samsung Galaxy Nexus] Hydre:
To unlock/flash the recovery, you can use the very good Android Toolkit available for example here
[Samsung Galaxy Nexus] vortex-5:
Never mind I extracted some source code form the bootunlocker app:

dd obs=1 count=1 seek=124 of=/dev/block/platform/omap/omap_hsmmc.0/by-name/param

I figured this was very specific did a search on here and it lead me to osmosis odd's an ends there's a boot unlocker in there that does not require oem unlock command.

https://xdaforums.com/showthread.php?t=2239421

Or you can grab it directly here:

http://xdaforums.com/attachment.php?attachmentid=3783994&d=1466008756

Thanks Osmosis
[Samsung Galaxy Nexus] osm0sis:
I noticed the guys started naming it "tuna" so I added it to the supported list in my zip. I'll do so as well for my unofficial Boot Unlocker App builds if/when I have time to get around to making them. ;)
[Samsung Galaxy Nexus] vortex-5:
Security patch level from October 6 for ua-tuna-ota-20170116.zip?

In the about menu the security patch level seems pretty out of data is it just the case that no one updated the string or is the security patch level indeed from back in October?
[Samsung Galaxy Nexus] _yen_:
for version 6.0.1 aosp repos where updated on December patch level (6.0.1_r77). Development seems focussed on version 7.1.1 which is instead quite up-to-date (January 5th).

bye

yen
[Samsung Galaxy Nexus] vortex-5:
So this is still true for the marshmallow 6.0 rom? I don't see a build for the 10th on that rom.
[Samsung Galaxy Nexus] _yen_:
Nope, January 10th build I'm speaking is from the 7.1.1 branch, I firstly think you are speaking of it... I modified my post later.. 6.0 was updated to December patch level for all aosp repos, for which I can see on github. Sorry for misunderstanding.

BTW 7.1.1 builds are not bootable "as is"

bye

yen
[Samsung Galaxy Nexus] danvrez:
it's because they moved the kernel.mk to vendor/unlegacy.

maybe it breaks the kernel build because it stuck in google screen.
[Samsung Galaxy Nexus] 2450687:
http://builds.unlegacy-android.cf/aosp-7.1/tuna/

the 20170117 build can not find the SIM card,there is no baseband.

Anybody have the some problem?