yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] barbatrukko:
Hi,

I did many tests.

Delete all and reinstalled many times

Also installed LineageOs, then reboot, then rswtart recovery, then reinstalled app, the reboot but not work

During setup I see icon of google service that works..., when boots ends, play store have brocken icon and messagebox tell me that many services not works.

Now I have only 2 options: 1) try older release of lineageOs, or try other distro, 2) replace CWM with TWRP

Some suggestion?
[Samsung Galaxy Nexus] MrFlashGame:
Just use TWRP. This will help. And make sure to do a clean flash if you don't had LOS before on your phone (Delete at least /system, /cache completly)
[Samsung Galaxy Nexus] barbatrukko:
I m triing to replace cmw with twrp but I have problem to use fastboot (nexus driver have problem). Other why to install TWRP over CMW?
[Samsung Galaxy Nexus] MrFlashGame:
Hm I've never tried CWM but in TWRP is a option for flashing .img files. You could look for this option in CWM. And the fastboot problem: I had this problem too, the program PDA Net helped me but it's this kind of bloatware program you normally don't want to have on your computer. Another option is to install the universal adb drivers (google is your friend ;)) and don't forget to check if you have the newest adb/fastboot clients. Please let us know if you have other issues im sure the community can help you to flash this baby :)
[Samsung Galaxy Nexus] Fediir:
How long time the first boot is ? approx.
[Samsung Galaxy Nexus] barbatrukko:
HELP, HELP, HELP!!!

UPDATE: I have tried several times to reinstall the distro and apps (sometime at same time, sometime fiirst distro, reboot then apps, etc) nothing... always same problem.

During first boot (that in some case was long) i see the app installing (with correct icon)... after boot.... googel service problems, no play icon, etc.....

After last install, i returned to recovery and i found NOT CW but CianogenMod Recovery.... :mad:

I don't know why! I did the same operation with this recovery but after clean (maybe i select wrong option) i deleted all date in sdcard, so, now I have the CyanogenMod recovery but not zip file to flash.

How i can now flash distro? (maybe come back to 5.1.1 or try another 6.x).

What I can do now? Odin? adb? what§?????

PLEASE HELP ME or my young my daughter will kill me!!!!
[Samsung Galaxy Nexus] Android-Andi:
Fastboot flash twrp after disableing recovery update in developer options.

Gesendet von meinem A0001 mit Tapatalk
[Samsung Galaxy Nexus] barbatrukko:
I will try, also if i had some problem with adb driver, i will try on other pc. After, if I can flash twrp, how i can put .zip on sdcard? adb sideload? or?

Please tell me where I m wrong:

1) if i boot in "(Volume up+ volume down+ power) cyanogenmod Recovery -> asd sideload" i woild find the device when i wrote fastboot devices? is correct?

2) if i boot in emergency (Volume down + power) "message downloading don't power of..." this mode is only for Odin?

1a) why i donìt see fastboot devices ? I installed many samsung/nexus/us drivers, package all in one, install utility, etc etc... but nothing... (also before Crack, when starting with andoird 6 without services, i can acces to storage. is ADB the problem.
[Samsung Galaxy Nexus] MrFlashGame:
Okay mate, keep cool thats probably the most important thing for you. We will find a solution for you. To point 1: If you hold Power; Vol + and - you should come to the bootloader. Now you connect your device to your computer and open the command line where you installed your adb/fastboot (Shift and right click gives you a option for this) now you type in adb. Now you should see a long list of commands. If you see command not found or something else you are probably in the wrong directory or you have not working adb/fastboot. So if everything worked to this point type in fastboot device. (Your phone should be still in the bootloader of course) Now you should see your device listed. (Long number...). If you see <waiting for device> or something similar you have probably the wrong drivers installed (-> install Universal ADB Drivers). Now download the latest TWRP (3.1) and put it in your ADB/Fastboot folder on your computer. And then just type in (your phone is still in the bootloader) fastboot flash nameofyourtwrp.img. After that it should flash you the twrp recovery and you can install now normal flashable zips. Please never give up, I tought my phone was dead for 1,5 years until somebody here at XDA helped me.
[Samsung Galaxy Nexus] Fediir:
"Volume up+ volume down+ power" gives me a bootloader mode. You can check that your device is visible by 'fastboot devices' command.

After that if you see your device in list you can flash new recovery by 'fastboot flash recovery recovery.img'.
[Samsung Galaxy Nexus] barbatrukko:
UPDATE:

adb devices works (and listed "device id" sideload)

fastboot devices not work

So I used adb sideload to upload rom.zip again. First I used another ROM bit not worked becouse not signed.

So i used again LineageOS that is signed and all ok.

Now i m withour Gapps

So i upload gaps in sd and installed, but cyanogenmod recovery don't install becouse "signature verification failed"

I also put the .zip.md5 key...but nothing.

How i can now install gapps and more replace cyanogenmod recovery with twrp ?

and more, I installe twrp app (via apk) and tell me that device is not rooted....
[Samsung Galaxy Nexus] bwalter:
I had to use this tool to get Windows 10 to use the WinUSB driver for my Galaxy Nexus so I could "see" it in fastboot mode: http://zadig.akeo.ie/
[Samsung Galaxy Nexus] bamtan2:
If the wrong driver is installed, you must manually go into device manager, find the phone, and switch to a different driver. It's a hassle.

If you boot the ROM without google apps, the ROM is permanently broken, and you need to start from the beginning as I previously posted.

I suggest using skipsoft toolkit or wugfresh toolkit to automate a lot of this work.
[Samsung Galaxy Nexus] barbatrukko:
Ok, but now I m over this.

Now i would replace recovery (i would install twrp) or find a way to install .zip without signature inside cyanogenmod.

I now have gapp inside cell and can reboot in recovery and install both ROM e GAPP again, but can't becouse cyanogen mod recovery not install unsigned zip.

also i can't install twrp for the same reason.

Can you tell me how to force cyanogenmodrecovery to install unsigned .zip or how to use the md5 (or file asc) that i can download with the zip?

Best way for me is to install twrp first!
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=5352368]barbatrukko[/MENTION] you need to disable recovery update first in developer option, else cyanogen recovery get restored on boot.

Once you have this done, go and get fastboot working to flash TWRP.

There is no way to flash stuff not signed by lineageos from cm recovery.

Besides that: I think it's enough OT here and everything was said many times now. Further questions should move to general Q&A section because this is a development thread.

Gesendet von meinem A0001 mit Tapatalk
[Samsung Galaxy Nexus] barbatrukko:
OK, sorry for the OT.:crying:

the problem is that fastboot not work with Cyanogen recovery. I wull move to Q&A as you suggested.

Thanks!
[Samsung Galaxy Nexus] Android-Andi:
Fastboot only works in fastbootmode.

Gesendet von meinem A0001 mit Tapatalk
[Samsung Galaxy Nexus] barbatrukko:
Hi to ALL.

Finally, after change 4 PC and TRY more than 30 dirvers,tools, etc i was able to use fastboot mode.

So i changed recovery in twrp 3.1

after clean, clean cache anc clean dav.

Install Lineageos13 and gapp (form twrp on same time)

Reboot...... and......... WORKS!!!!!!

I think old CWR was not able to flash 6.1

Play store ok.....

So now can Enjoy and test ROM (that for now like more responsive than old 5.1.1)

Thanks to all!
[Samsung Galaxy Nexus] MrFlashGame:
Hey guys good news: It seems like the SIM Toolkit bug has been fixed. At least I can use this app now properly. Could someone else confirm?
[Samsung Galaxy Nexus] The Doctor04:
Google and Texas Instruments no longer support this device. Unless TI opens up their code, no one is going to be able to patch holes & security fixes. TI cut off the community years ago. Google is going to tell you to go kick rocks as well. This is the risk you take for using a device that is almost 6 years old.
[Samsung Galaxy Nexus] Android-Andi:
80% of the unpatched CVE are Qcom fixes which not apply.
[Samsung Galaxy Nexus] bamtan2:
[MENTION=4800984]The Doctor04[/MENTION] You and [MENTION=7643454]jango0[/MENTION] are talking about different things :) He's asking about the open source kernel and OS bits which can be and have been patched many times over the years.

Technically there could be security bugs in the closed source bits, but we can't help that, and all the bits on top are very new and secure.

Only the very newest devices might have fewer vulnerabilities than this one with new code. Most devices around the world probably haven't been updated for years... Google says 30% still use Android 4.x.
[Samsung Galaxy Nexus] MrFlashGame:
[Q] Does this ROM have init.d support? I would like to test something with init.d but I'm not sure if LOS supports it.

Greetings, Nils :)
[Samsung Galaxy Nexus] Android-Andi:
Did a fast walk through it and pushed some commits on gerrit, some work left, feel free to continue.
[Samsung Galaxy Nexus] Android-Andi:
Kernel for maguro, toro and toroplus attached. Adresses the following CVE:

CVE-2016-9794

CVE-2016-9793

CVE-2016-9754

CVE-2016-8655

CVE-2016-7915

CVE-2016-7911

CVE-2016-7910

CVE-2016-6786-CVE-2016-6787

CVE-2016-6136

CVE-2016-2184

CVE-2016-1583

CVE-2016-10208

CVE-2016-10088

CVE-2016-10044

CVE-2015-8966

CVE-2015-8963

CVE-2015-8962

CVE-2015-8019

CVE-2015-8019

CVE-2014-9420

Let us know if you face any new issues.

Don't be confused about the "CM" in the zip name, just updated it to display "lineage" next time (Add make bootzip task)

Changes can be found here.

Edit:

Only meant to work on Lineage13! Don't use it on other roms!

UA and Slim already have those patches applied for a while now.
[Samsung Galaxy Nexus] guest4711:
Thanx for the clarification.

Tried without luck on slim7.
[Samsung Galaxy Nexus] MrFlashGame:
Hi guys,

as I had some free time yesterday I decided to rework the maguro "prebootanimation" logo (This thing where you see the google logo and a lock before the bootanimation starts). I updated the google logo to the newest from 2015 and I took the lock from LineageOS. I think this gives our phones a much newer look, but I have no idea how I can integrate this in my system and I don´t know if it´s even possible to add. I hope maybe [MENTION=2633638]Ziyan[/MENTION] or [MENTION=5153662]Android-Andi[/MENTION] could take a look at this.

Greetings Nils :)
[Samsung Galaxy Nexus] guest4711:
Nice work, but probably only for your exercise. The logo is displayed by the bootloader with loads your ROM or your recovery. So the lock shows its state: Whether the bootloader is still locked or unlocked already.
[Samsung Galaxy Nexus] osm0sis:
I wrote a command line tool for this awhile back! You can find it linked in my Odds as Ends thread. "logohack.sh" I believe. :)
[Samsung Galaxy Nexus] Fluke1969:
My phone is stuck on the first boot, at the "preparing to start" phase. It never got past this point.

imgur(.com)/a/Di5ly

(cant post links, a photo with the issue im having.)
[Samsung Galaxy Nexus] MrFlashGame:
Sorry I didn't know that such a modification is already available. But your solution is really great! Two questions: Do your mod persist a /system wipe? And in which location do I have to save my pngs that the script can find it?
[Samsung Galaxy Nexus] osm0sis:
You supply the location as an argument on the command-line, so wherever, but /sdcard would be logical. Yes, the modifications are to the bootloader's sbl partition, so they survive a full wipe, and also for that reason should be done with care. I've made every precaution I could in my scripting to prevent a corrupt bootloader, but recognize that the potential is there and you make such mods at your own risk. :)

It does not survive a bootloader flash, naturally, and coexists nicely with RePIT. It also requires JPEGs because that's what Google/Samsung used. Closely read and follow my instructions in my linked logohack posts in that thread to know how to properly prepare the images to be used in the script.
[Samsung Galaxy Nexus] Childe89:
Hello, I´m not using this phone much anymore, just as backup device, but flashed newest nightly and It´s nice to see this device is still supported :) And how much RAM was made available since the first Lollipop builds :)

Everything I tried worked in last nightly, except minor problem in Camera - switching between main and front cameras closes Camera app, so you have to reopen app after each switch - but I suppose It´s RAM allocation issue, and more free ram is worth it :) But might be on my side also, because my device performance is suffering by very slow eMMC (famous V3U00M) and fstrim just makes it a bit better, so It´s usable :) (that´s also the reason I switched to different device)
[Samsung Galaxy Nexus] LeoHart:
Can someone explain me, why I get an error 4 in TWRP if I flash the su(arm).zip from the LineageOS page?
[Samsung Galaxy Nexus] Android-Andi:
Lineage Team knows about it and had it fixed, idk why they never made it public. I compiled one from source myself, link in OP.
[Samsung Galaxy Nexus] MrFlashGame:
Hey folks,

I've found another bug in the newest LOS nightly: If I hear music and turn the display off and turn it on again and want to take a photo over the lockscreen while the music still runs the music stucks and I have to jump over to the next song to fix this bug. I hope this gets fixed soon even it's a small bug.

Greetings, Nils
[Samsung Galaxy Nexus] nailyk:
IIRC someone here recently bought a maguro to dev on it.

Can this person share me his github/gerrit account?

I would like to start working on 14.1 for maguro with the actual dev community.

Thanks in advance.
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=6979267]nailyk[/MENTION] github.com/andi34 , but i don't think lineage and roms based on lineage are the best places for non QCOM devices anymore. Things changed a lot within last years... It happens quite more often you need to fix bugs introduced by CAF which aren't ifdefed properly... And if you find the broken bits you will have a lot of fun explaining what and why you are fixing it before it get merged (if it ever gets merged). Atm i think UA is the best place to work on.
[Samsung Galaxy Nexus] nailyk:
Thanks!

UA?

I recently talk with the SII maintainer. They have some pending changes (maybe merged now) for our/their soc and they are running 14.1 onto it. (cannot find the gerrit link right now)

I have big hope it will works.

Also I still have this link: https://zeelogkang.blogspot.fr/ where there are some 14.1 builds :)
[Samsung Galaxy Nexus] Android-Andi:
UA = Unlegacy Android.

Time is the most killer for me atm, still need to replace my LG G4 asap because i lost all my data twice in a short time (known official problem with bootloop on that phone... And it'll be back sooner or later...) and still need to find a part time job.

On lineage it took a while to bring the common omap4 hw repo almost inline with the stuff our omap4 team brought to us... And still it's missing tuna support in some parts which makes maintaining unneeded complicated.

Another killer on official Lineage for tuna: i am quite sure they won't accept unified builds ;)
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=6979267]nailyk[/MENTION] btw i think you mean the exynos4 Galaxy S2 (i9100)? The omap Galaxy S2 (i9100g) isn't worked on anymore afaik, at least no one actively working together with us and i haven't heared from that device since kitkat/ beginn of lollipop (?).
[Samsung Galaxy Nexus] :
I don't think unified would be a problem for Lineage, for example LineageOS for OnePlus 3 and 3t is a unified build for both too
[Samsung Galaxy Nexus] nailyk:
Thanks for the anwsers.

Yes unified trees are good. We^wThey are bringinup shinano (xperia z2,z3 and variant) with a 'unified' tree and the official is on the go.

Yes I would say the 'g' one, because, afaik, it is the same soc as us.

I remember seeing that huge framework commit, with some #ifdef tuna. Into the comment they said everything is fine but didnot test maguro.

I will try to highlight the old maintainer ( [MENTION=5746995]doriandiaconu[/MENTION] ) on irc, maybe he can share me the link again.

Will start looking at all of this the coming week.

Also I think 14.1 will be good as many 'low-ram-device' users (~1Go) report smoothest device on N than M.

Am really not an expert so will try to paste what I find here.
[Samsung Galaxy Nexus] ____Mdd:
[MENTION=6979267]nailyk[/MENTION] [MENTION=5153662]Android-Andi[/MENTION]

You can also talk to "Motorola Droid Razr" community.. they got RR-N and AICP and Lineage as well.. that also has omap4430..

See here: https://xdaforums.com/droid-razr/development

On my another device, Moto G4 plus, that's also unified and has official support from most of ROMs, you can give it a try.. best of luck..:good:
[Samsung Galaxy Nexus] bamtan2:
Thank you for this nailyk! We have had many good and generous developers come through this community, and it is crucial that we all welcome new developers who will take the place of those who have departed!

In my experience CM12.1 is the most stable and performant recent version of android for this device. I believe this is because it received the most attention from the largest group of developers for the longest period of time. It would be a real achievement for someone to bring UA or LOS14 up to the same quality standard.
[Samsung Galaxy Nexus] nailyk:
Thanks for your encouragements.

I know am not skilled enough to make something as good as the 12.1 but will do my test to help the devs.

AFAIK there is another N rom for maguro, maybe it can help us.
[Samsung Galaxy Nexus] ____Mdd:
Yes there is but for tuna (unified), DU, SAOSP and Pure Nexus.. they are based on AOSP (UA) , by yuuji, he post on google+ , read here: https://xdaforums.com/showpost.php?p=69354816&postcount=16

Slim7 by android-andy also..
[Samsung Galaxy Nexus] guest4711:
And LineageOS 14.1 unofficial (unified), see

http://zeelogkang.blogspot.com
[Samsung Galaxy Nexus] Android-Andi:
Let's leave this here as it's a topic here and there now:

https://www.lineageos.org/Safetynet/
[Samsung Galaxy Nexus] Android-Andi:
AnyKernel for maguro, toro and toroplus attached. Adresses the following CVE & LVT:

CVE-2016-9794

CVE-2016-9793

CVE-2016-9754

CVE-2016-8655

CVE-2016-7915

CVE-2016-7911

CVE-2016-7910

CVE-2016-6786-CVE-2016-6787

CVE-2016-6136

CVE-2016-2184

CVE-2016-1583

CVE-2016-10208

CVE-2016-10088

CVE-2016-10044

CVE-2015-8966

CVE-2015-8963

CVE-2015-8962

CVE-2015-8019

CVE-2015-8019

CVE-2014-9420

LVT-2017-0001

LVT-2017-0002

The LVT commits are an workaround/fix for an Lineage SU vulnerability because it is not fixed in su source yet.

Attached AnyKernel should work on all roms from 4.4 up to 7.1 (only kitkat has an own kernel config and that's why there's an seperate zip attached) - it is not specific for LineageOS.

All mentioned CVE and LVT commits can be found on LineageOS gerrit.
[Samsung Galaxy Nexus] guest4711:
Thank you Andi. I'm just testing your kernel on LOS 14.1 and it's looking good so far... :good::good::svetius:
[Samsung Galaxy Nexus] nailyk:
Are you using this zeelogkang builds?

I was not able to find their sources.

What about this: https://github.com/doriandiaconu/build_tools ?
[Samsung Galaxy Nexus] _yen_:
kernel and device tree should be here:

https://github.com/zeelog

bye

yen
[Samsung Galaxy Nexus] nailyk:
It seems we are some (wanna) working on this device. What about pushing repos into a github organisation?

Am also able to add it into my gerrit instance.

Also does an IRC chan exist for this device?

What is your opinion?
[Samsung Galaxy Nexus] guest4711:
Yes, I'm using his builds, but I'm not compiling it myself (as I do on my FreeBSDs...)

Havent had a look on this repo.
[Samsung Galaxy Nexus] DandyElf:
Found bug

Hello. Found bug in lineage-13.0-20170603-nightly-maguro-signed.zip : NFC toggle in the Quick Settings doesn't work. Any idea how to fix?
[Samsung Galaxy Nexus] Android-Andi:
Logcat & dmesg?
[Samsung Galaxy Nexus] nailyk:
Hi,

just opened ##Lineage-Maguro on freenode. Feel free to join :)

Am looking for a github organisation name before pushing all the needed repos into gerrit.
[Samsung Galaxy Nexus] DandyElf:
LogCat:
[Samsung Galaxy Nexus] Android-Andi:
Thx [MENTION=4252380]DandyElf[/MENTION] , there's an selinux denial we need to fix which is easy. I'll commit it tomorrow if [MENTION=2633638]Ziyan[/MENTION] hasn't done until :)

Edit: on gerrit https://review.lineageos.org/#/c/176930/
[Samsung Galaxy Nexus] Android-Andi:
Attached a kernel to use on Lineage13 only!

- Includes all security updates like previous AnyKernel i posted some days ago

- should fix NFC Tile

[MENTION=4252380]DandyElf[/MENTION] maybe you can test and report if the NFC Tile works after flashing the kernel?
[Samsung Galaxy Nexus] LeoHart:
[MENTION=5153662]Android-Andi[/MENTION]

Thanks for the information.

I noticed an other strange issue. If I want t install an apk from sd I get the Parse Error.

I can't understand why:

Install Apps from unknown sources is checked

Google > Security > all unchecked

Any advise what is wrong? :(

I only want to install the Netflix App. Unfortunately Google make the decision to anger the custom rom user :rolleyes:
[Samsung Galaxy Nexus] DandyElf:
Two days normal flaing. NFC on/of Tile works great.
[Samsung Galaxy Nexus] Android-Andi:
NFC tile should be fixed on next official weekly too :)
[Samsung Galaxy Nexus] ExecutorElassus:
I come back here from time to time to ask this question: I have the last CM nightly from December still on my maguro-phone. It's pretty buggy still (random reboots, half of which result in not being able to recognize the SIM card, camera is super-yellow, etc.), but I'm not sure I can install this onto my encrypted storage. For one, half the time I boot into recovery I can't mount the storage at all, and even then loading a ROM often fails.

Second, I'm wondering: does the LOS ROM have a similar extended featureset like the old CM builds did? Or is it more stock Android?

Sigh: is my phone just dying in general on the hardware side?
[Samsung Galaxy Nexus] aaronrw:
In many instances I cannot get touch feedback to work while playing games? Ex temple run hungry shark evolution. Any workaround thanks to all this is pretty awesome to run on an older device
[Samsung Galaxy Nexus] Huzaifa7755:
I had the same problems with some games(not all), my fix was pressing the button while having a finger touching the screen.
[Samsung Galaxy Nexus] aaronrw:
Is this kernel included in later releases ? Thank you for all you've done to keep tuna up to date
[Samsung Galaxy Nexus] Android-Andi:
NFC should be fixed, all the CVE fixes still on gerrit
[Samsung Galaxy Nexus] hga89:
Does whole-file system encryption work on this device running CM 13? File access for encrypted files does not work on my Tab S2.
[Samsung Galaxy Nexus] beymanlope:
When it will be available in version 14.1 with android 7.1.2?
[Samsung Galaxy Nexus] nailyk:
Oh. I think you where the +2 of maguro but looks like [MENTION=2633638]Ziyan[/MENTION] is. Cant you ask them for +2?

Also as nobody answered about my gerrit question why not asking for opening the 14.1 branches into the official repos, based on 13.0?

Dunno if you have a slack access but I can ask on IRC if you mind.

Thanks for the work on this device!
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=6979267]nailyk[/MENTION] we are both on Lineage Slack too but we are tired of fixing CAF issues Lineage introduces here and there...

I am not planning to work on 14.1 for tuna.

Ziyan will look into the open kernel commits once he has time, i don't have merge rights.