yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] z3DD3r:
@Redshadow.om

Use latest version of TWRP HH to flash ROM. Also download latest version of LineageOS 17.1 from signed folder on sourceforge
[Nexus 5 Original Android Development] snow:
@z3DD3r

I want to report two issues:

1) For some reason, when I (re)start, the device gets into boot loop. But here's the interesting part: If I connect the device to the charger/computer with a USB cable and try to (re)start the device again, the device will successfully boot into Android. This is extremely weird and I'm not sure how this is debuggable given that the weird behavior only happens when the device is NOT connected to an energy source like the computer. I'm pretty sure this issue also happens with LOS 18 builds.

2) If I use Rootify app on the device and I press "DEEP CLEAR RAM", the device will freeze a few seconds after and the screen will display something like this -> https://i.ytimg.com/vi/gXz0mzQh8eU/hqdefault.jpg I have to manually reboot the device via physical buttons when this happens. I believe this didn't happen on LOS 18, most likely something it's missing compared to LOS18 ?!

Perhaps you have some idea of how to fix these on LOS 17. 🤔

Thank you in advance.
[Nexus 5 Original Android Development] z3DD3r:
@snow,

Unfortunately idk what is going on. Without device i can't do much
[Nexus 5 Original Android Development] z3DD3r:
New build (20230217) with february security patch is out!

Please don't ask me for OTA or any bug fixes.

I don't have Nexus 5 anymore and can't provide proper support.
[Nexus 5 Original Android Development] Sir Charles82:
but you still add security patches and I'm very grateful for this service. Thank you!
[Nexus 5 Original Android Development] Renate:
It's probably a simple case of the battery dying.

Usually at some point in the boot sequence the current load is the greatest.
[Nexus 5 Original Android Development] snow:
I don't think so.

I can always replicate this weird behaviour. The device will always boot up successfully while connected to the PC/charger, but stays in the boot loop if not connected to the PC/charger.

I connect it to any energy source for a few minutes just to be sure it will get past the boot animation, and afterwards, I can disconnect it, and the battery will resist for a few hours.
[Nexus 5 Original Android Development] snow:
Wow, the issue I reported here one year ago is caused by Magisk's Zygisk.

Disabling Zygisk will allow the device to boot up correctly every time, no matter if it is connected to charger/PC or not.
[Nexus 5 Original Android Development] Faniry:
Can you help me with the installation of Gapps?

Because after installing LOS and Gapps, it caused the bootloop. Thanks
[Nexus 5 Original Android Development] ze7zez:
Use gapps built before the ROM.
[Nexus 5 Original Android Development] jjsan:
so i have flashed

lineage-17.1-20200203-UNOFFICIAL-hammerhead.zip and then

gapps pico.

phone boots without problem.

then back to recovery and flasg magisk 20.03(20300). no error in log. reboot system - stays on black screen without any logo. only long press volume- with power will bring start page.

uninstalling magisk with uninstall script - phone boots ok.

(my recovery is 3.3.1-HH)

some help?

thanks
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Try to clean flash again but now flash Magisk before rebooting your device, so flash LineageOS first, then Magisk and at last the Pico Gapps package. After that boot to system, it should boot up just fine.
[Nexus 5 Original Android Development] jjsan:
tries even just lineage and magisk. still no boot. im using android 9 with magisk 20.03 without problem. so i dont know what to do :(
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Super strange, for me it works perfect... The only thing that's different on my setup is that I run the Criterion Kernel... What happens if you clean install LineageOS, then the Criterion Kernel and at last Magisk?

Edit: I asked around in the Nexus 5 Telegram group and I got the suggestion to try to install Magisk via the Magisk Manager app instead of via TWRP. I also got informed that trying the Criterion kernel shouldn't change anything. Criterion is based on the LOS 17.1 kernel. All changes applied to this kernel does not affect issues with booting after flashing Magisk.
[Nexus 5 Original Android Development] mrvelvet:
You're not alone - I thought I might have been going crazy but am seeing the same thing with routers running 19.07.1. Other APs work fine.

However, it also might be affecting other Android devices (e.g. a Minix TV box seems to have difficulty seeing the AP) so it might be an OpenWRT bug. I thought it might be 5GHz so have tried a variety of `ath10k` firmware and module combinations but even with 5GHz disabled I couldn't get the Nexus to connect to 2.5GHz (WPA2 AES) either.

I've done a quick search on the OpenWRT forums and found that https://forum.openwrt.org/t/android-device-cant-connect-to-openwrt/54199/5 says that disabling 11w works (disabling 11w also means no WPA3). However, I also had to disable 11r to get the Nexus to connect.

So, with both 11r and 11w disabled my Nexus will once again connect to the OpenWRT AP. This sounds more like an Android wifi driver issue than an OpenWRT bug...

---------- Post added at 04:35 PM ---------- Previous post was at 03:40 PM ----------

My flash order tends to be Lineage, Magisk, OpenGapps. It has worked every time with TWRP 3.3.1-HH.

I have previously seen a bootloop with flashing, but normally rebooting to recovery after flashing a zip can help (e.g. flash Lineage, reboot to recovery, flash Magisk, reboot to recovery, flash GApps; you can try switching GApps and Magisk flash order too).
[Nexus 5 Original Android Development] juniorjpdj:
I also have problems with WPA3 (also OpenWRT 19.07.1 but not ath10k - I've mediatek wifi card in router) and I have little problems with bluetooth. It tends to crash after few minutes of tethering connection enabled (from another phone) and then bluetooth is completely dead until reboot.
[Nexus 5 Original Android Development] candra yudha tama:
Developer still update this ROM :D everyday update
[Nexus 5 Original Android Development] vipercoyote:
How is this different from the original OS on lineageos.org/ ?????
[Nexus 5 Original Android Development] z3DD3r:
What differences are you talking about? There is no original or official builds for hammerhead...
[Nexus 5 Original Android Development] candra yudha tama:
I enjoyed use this ROM and the last build 208 is more better :)
[Nexus 5 Original Android Development] candra yudha tama:
Thanks dev :good::fingers-crossed:
[Nexus 5 Original Android Development] Brideinflame:
Hello, what is the correct way to flash Builds updates? Just perform the Flash on the current version or should I always do a clean installation?
[Nexus 5 Original Android Development] z3DD3r:
Flash ROM, gapps (if flashed previously) and other mods which you installed.
[Nexus 5 Original Android Development] JackyGundam:
no i still can't boot the google logo, not i've tried every order

i tried rebooting to recovery after flashing a zip

i flashed lineage, reboot to recovery, then flash magisk, after i pressed reboot to recovery, the screen totally turned off, no backlighting, and no google logo.

I don't understand why this happened to android 10 only, and some people have this problem, while the others don't...
[Nexus 5 Original Android Development] vipercoyote:
been out the game for awhile but how do I install this? DO i have to sideload and if so how and with what software?
[Nexus 5 Original Android Development] eupalino:
To install 17.1 you have to repartition, since original system partition is too small. Read instructions here:

https://xdaforums.com/google-nexus-5/orig-development/recovery-twrp-hh-nexus-5-hammerhead-t4047653

Especially read second post.

M.
[Nexus 5 Original Android Development] sant514:
https://xdaforums.com/google-nexus-5/orig-development/recovery-twrp-hh-nexus-5-hammerhead-t4047653 And this link.

This TWRP version from z3DD3r, can to encrypt and decrypt all versions from 8 (Oreo) and up...
[Nexus 5 Original Android Development] Mark_8:
Can it be related to nexus 5 displays?

At the time of unlegacy aosp based on android 8.1 there were one standard build for all nexus 5 and one named "CAF" that it doesnt work on some with different display refresh rate;

Sincerely i dont know if this issue is related here also for android 10 :rolleyes:
[Nexus 5 Original Android Development] mrvelvet:
Did you actually try a clean flash?

Have you checked logcat output?
[Nexus 5 Original Android Development] eurochild:
guys i think that its something indeed with non original displays, mine is a cheap one bought from ebay last year and i also have the black screen after flashing magisk on android 10
[Nexus 5 Original Android Development] vipercoyote:
Yes so Im trying to install twrp but when i do it says successful but when I try to boot into recovery it goes to a screen thats says "your device software cannot be checked for corruption. please lock the bootloader" . Click to continue etc but when i do it does nothing but stays on that screen or boot in to the stock OS
[Nexus 5 Original Android Development] G小金:
Patch boot image work fine for me , wipe data after flashing magisk may achieve the same

Just need to open Magisk Manager repair after booting

Sorry for my bad English
[Nexus 5 Original Android Development] vipercoyote:
Are you replying to me?
[Nexus 5 Original Android Development] JackyGundam:
yeah i have a very clean flash

and i don't know why i don't have magisk.log

i have kmsg log
[Nexus 5 Original Android Development] n1yesuh:
Flashed it yesterday. Coming from 14.1 that was a solid ROM. And I'm loving this 17.1 so far, thank you.

Only small thing is I want the icons to look stock, not circle not square just plain old stock, couldn't find how, can you help me please?

Edit: App icons that is
[Nexus 5 Original Android Development] JackyGundam:
to be honest mine is also non-oem display...
[Nexus 5 Original Android Development] jjsan:
how can i find version of display? i bought phone, and maybe it was changed
[Nexus 5 Original Android Development] Brideinflame:
I don't know what you did in the version of 11.01.2020, but the one is perfect, the battery consumption is very low. Congratulations on the work
[Nexus 5 Original Android Development] zurohki:
I had issues with wifi, and I should have read the thread.

Having 802.11w management frame protection set to optional in OpenWRT prevents my phone from connecting with this ROM. Change it to "disabled" and wifi works fine. My phone used to have no problem connecting to this access point with the 16.0 ROM.

I don't know if 802.11w was actually *functioning* previously, but setting it to optional didn't cause any issues.

Edit: Fast transition also needs to be off. I had it on before with no issues, too.
[Nexus 5 Original Android Development] testUser69:
Anyone tried edXposed with this rom yet? Can't get either versions to work so far. After installation and a reboot I can't get past the bootloader.

Also, is there a chance we can get a version which allows signature spoofing, so we can use MicroG ?
[Nexus 5 Original Android Development] z3DD3r:
Where did you found xposed for Android Q?)
[Nexus 5 Original Android Development] testUser69:
github. com/ElderDrivers/EdXposed (I can't post links since I'm a new user)

"Also, is there a chance we can get a version which allows signature spoofing, so we can use MicroG ? "

In case you've overlooked my recently edited message :)
[Nexus 5 Original Android Development] z3DD3r:
Thanks for the link.

In any case i will not add anything additional to support edxposed or microg. If it doesn't work then it is a problem of edxposed or microg. Rom compiled without any changes in the LOS source code...
[Nexus 5 Original Android Development] unknowndrop:
Hello.

I have a problem with the charging animation while the phone is turned off. The charging animation does not go away after unplugging the charger - As having a broken power button, I had to wait till the battery was drain to 0% to turn the phone on by pressing both volumen button (and pluging the charger) and starting the phone via fastboot (connected to PC).
[Nexus 5 Original Android Development] testUser69:
After going back to LOS 14.1 (from 17.1) my sensors aren't working anymore. Do I have to flash something to make them work again? I tried 17.1 again and there they do work. So it's not a hardware issue.
[Nexus 5 Original Android Development] ljanzen:
Wireless solution

Thanks to mrvelvet & zurohki. After doing a full clean flash of the phone I was still running into wireless issues. Disabling 802.11r & 802.11w in a secondary SSID allowed me to connect without issue. Not sure if this is a lineage or openwrt problem but it's unfortunate to have to turn off security features on up-to-date devices. I did note that leaving 802.11 as optional also prevented me from connecting, had to explicitly disable. Would still love to see WPA3 get compiled in, but my phone feels more responsive, especially after a long idle. Battery life on long idle is also improved (confounded by wipe of phone, smaller app re-install base).
[Nexus 5 Original Android Development] Prototype18:
Seems a great rom now. I found a trick for magisk just sideload it directly after rom and gapps. But now i cant get mobile data to work at all. Any idea what should i check?

European sim

Edit :

For the love of god i cant get out of EDGE. Cant get LTE or 3G.
[Nexus 5 Original Android Development] dahawthorne:
I see that a few people have had problems with Magisk. I did too up until today. It appeared to install ok, but on reboot there was no sign of Magisk Manager and there was no root.

This morning I performed exactly the same routine as before - full wipe & format, downloaded the ROM of 16th, Magisk Canary, OpenGapps 10 of 15th, and used the TWRP HH v3 to install them - ROM & Gapps first, reboot, back to TWRP, install Magisk - and it all worked fine. I've since flashed z3DD3r's TWRP v4, and all seems smooth. Great job, z3DD3r - thank you.
[Nexus 5 Original Android Development] Mark_8:
Maybe i could be wrong but with android 10 and magisk tons of things are changed; the installation of this new android is becoming more and more challenging :highfive::highfive:
[Nexus 5 Original Android Development] JackyGundam:
nope u can't find the version:crying:
[Nexus 5 Original Android Development] ProBird79:
Everything is working great here! Thanks a ton for keeping this old device feeling new!

Will the updater work in Settings>System>Updater or is that only if it's hosted on Lineage servers?

Also, I have an app icon in my app drawer with a circle around it. When I try to open it it says, "To view this content, install and set up a web browsing app." I do have a default web browsing app already selected (Chrome) though so I'm at a loss. What is this rogue app icon?
[Nexus 5 Original Android Development] bluetooth-bug:
I can also confirm that bug. It's a Trebuchet launcher issue. You get that icon when you install OpenGApps and you update Chrome from the Play Store. For some reason OpenGApps comes with an old version of TrichromeLibrary.apk and that gets updates as well. And because of that for some reason you get that Bugdroid icon with no description in your launcher.

Tried installing Pixel Launcher but that crashed for me every single time I tried to launch it so I have to live with this until it's fixed.

Also I have an issue with the app Hijacker. I cannot install the Nexmon firmware and tools. When I try to do that I cannot use them. Not sure if the firmware is installed or not or management utilities are not working because of the strict SELinux policies and there's still some denials.

3rd issue is that USB Mountr is crashing after I select an ISO file.

These are what I found and I'm trying to fix somehow. All these used to work just fine on LineageOS 14.1. If you know how to fix these please let me know. Everything went smooth during repartitioning, installing ROM, GApps and Magisk 20.3 as well. It's a great ROM and on my first charge I had over 3 hours of screen-on time. I have the original screen and battery.
[Nexus 5 Original Android Development] timgoodwin:
Try Rootless Pixel Launcher from Playstore - works well for me. If you want the left-swipe Google functionality you also need to install Pixel Bridge app, available here: https://www.xda-developers.com/rootless-pixel-launcher-google-play-store-pixel-bridge/
[Nexus 5 Original Android Development] z3DD3r:
Try new build from 2020-02-19. Clean flash is required! I've fixed some sepolicies for charger. Please send me the last_kmg log if u will see this error again.

Remove /persist/sensors folder. You can do it from TWRP for example. Mount the Persist partition and remove /persist/sensors folder via the FileManager. DO NOT REMOVE OTHER FOLDERS!

This is a bug of Trebuchet. Such icon can appear and disappear after installing or updating apps from play store. No solution rn. Ignore it or change the launcher.

Have u tried latest test build of OpenGapps from 2020-02-16? A lot of users reported that Pixel Launcher works.

Send me the logcat and dmesg right after issue occurs. There really can be some SELinux denials which i wasn't aware of...
[Nexus 5 Original Android Development] bluetooth-bug:
Hope I did it right. I installed management utilities in all the possible places that Hijacker offered. On LineageOS 14.1 only one of them worked and that was vendor/sbin if I remember correctly. There it was the second option. I rebooted and I was able to see networks in the list in monitor mode.

dmesg.log

*snip*

logcat.log

*snip*

I do see nexutil and airodump-ng denials. Here's a link where you can find Hijacker: https://github.com/chrisk44/Hijacker
[Nexus 5 Original Android Development] z3DD3r:
There is no airodump-ng denials. At least i see only untrusted_app denials which i won't solve cos it will lead to security vulnerability. In any case Hijacker doesn't work even if selinux is set to permissive. So this is not a SELinux problem.

https://github.com/chrisk44/Hijacke.../com/hijacker/InstallFirmwareDialog.java#L198. This will not work on Android Q cos of SAR. If root can't be remounted as rw then nothing can be installed. So i suggest you to contact developer of the Hijacker and ask him to solve issues for SAR.
[Nexus 5 Original Android Development] z3DD3r:
[MENTION=9675018]bluetooth-bug[/MENTION]

Looks like USB Mountr also doesn't support Q. Path to file can't be parsed and USB Mountr crashes. Here is the log when u trying to select .iso using the standard Files app from the Download link in the menu:

02-19 17:49:20.926 9323 9323 E AndroidRuntime: java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=2, result=-1, data=Intent { dat=content://com.android.providers.downloads.documents/document/raw:/storage/emulated/0/Download/BSMP_ARM.iso flg=0x1 }} to activity {streetwalrus.usbmountr/streetwalrus.usbmountr.MainActivity}: java.lang.NumberFormatException: For input string: "raw:/storage/emulated/0/Download/BSMP_ARM.iso

As u can see there is a raw: in the beginning of the input string. This is incorrect. App parses entire url incorrectly.

But if you will navigate to file staring with Nexus 5 in the menu (sdcard root) then everything works correctly.

PS: USB Mountr is deprecated by developer.
[Nexus 5 Original Android Development] trungamox34:
My N5 refuses to boot to system and reboots back to recovery after attempting first boot . I've tried several times, resized the partitions and flashed the ROM with and without Gapps, but the result was the same. Really don't know why :)
[Nexus 5 Original Android Development] dahawthorne:
Do a full wipe of all partitions in TWRP (the new HH 4 version), and also format data (type "yes" to confirm). Then while still in recovery copy ROM, Gapps Pico and Magisk Canary to your device. Install ROM & Gapps, reboot, then back to TWRP to install Magisk if you want root. It's probably the format that you've missed.
[Nexus 5 Original Android Development] bluetooth-bug:
[MENTION=7268092]z3DD3r[/MENTION]

Thank you for checking. USB Mountr works with that workaround. I was able to boot Parted Magic. I know it's deprecated and looking for another open source alternative. This should work the way it is for now.

As for the Pixel Launcher crashing, 20200219 pico GApps also crashes. I checked SourceForge for that test version but I was only able to find a micro version. Would this test version or micro fit on the system partition?

Hijacker can rest for now. I would still try replacing firmware manually and drop in tools in TWRP as experimentation but I don't know if that would even work. I will still keep in in installed even if it's broken.

And the phantom icon that's LineageOS bug so eventually they will fix it.

Everything else I tried is working perfectly. Wifi does work, VPN, I was able to receive phone calls and messages. Mobile data also worked, at least I saw the little x disappearing from the signal strength icon. GPS got a lock too.
[Nexus 5 Original Android Development] z3DD3r:
U can find micro and stock test packages here https://sourceforge.net/projects/opengapps/files/arm/test/

Idk if micro will fit on the system partition but u can use gapps-config.txt to exclude some apps. Read the instruction at https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
[Nexus 5 Original Android Development] bluetooth-bug:
[MENTION=7268092]z3DD3r[/MENTION]

Found a solution for Hijacker. It's working properly now. I replaced original fw_bcmdhd.bin with Nexmon patched one that has monitor mode support. I could only do it in TWRP thanks to your SAR build. I needed to chmod 644 the fw_bcmdhd.bin. Then I placed nexutil in /system/bin and chmod 755 that in TWRP. After that I rebooted and it's working properly.

Probably I will need to do this every single time I update the ROM till Hijacker gets SAR support.

For now I will stick with Trebuchet launcher and hope that phantom icon bug gets fixed. It's at the end of the list so probably I won't see it that often.

This means everything is working like a charm! The way I like it.
[Nexus 5 Original Android Development] z3DD3r:
It's not mine) It is Android 10 feature...

Yes. But u can create a flashable zip and flash it after the ROM in TWRP. It is a temporary solution but a bit better then do everything with hands every time u update the rom...

:good:
[Nexus 5 Original Android Development] z3DD3r:
Hi there

Everyone who can't boot LOS 17.1 (with or without Magisk) should try this experimental build: https://sourceforge.net/projects/ha...20200221-EXPERIMENTAL-hammerhead.zip/download

Let me know if your device will boot normally.
[Nexus 5 Original Android Development] jjsan:
finally able to boot with magisk ;)

had to use magisk manager canary (maybe should test last one - but it was closing to i installed canary - works ok)

used TWRP RR.H v4

many thanks
[Nexus 5 Original Android Development] candra yudha tama:
I try it and can boot normally used magisk last version.... should I used this experimental for daily ????
[Nexus 5 Original Android Development] z3DD3r:
:good:

U can. There is only one change related to boot issue. In other terms this build is equal to build from 2020-02-21. Or u can wait for build 2020-02-22 where this fix will be included.
[Nexus 5 Original Android Development] candra yudha tama:
I will wait build 2020-02-22:)
[Nexus 5 Original Android Development] FlyingInTheDark:
Is the source code on github up to date? I am getting a build error:

build/make/core/binary.mk:1323: error: device/lge/hammerhead/camera/QCamera2/HAL/Android.mk: camera.msm8974: C_INCLUDES must be under the source or output directories: /libstagefrighthw /libgralloc.