yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Q&A, Help & Troubleshooting] O's:
I wasn't sure if a dpi-changer app would override manual build.prop edits, but, worth a try. Thank you! Will report back.
[Galaxy Note 4 Q&A, Help & Troubleshooting] O's:
ETA: Negative. Changed build.prop dpi to ro.sf.lcd_density=560 — no help. Used TWRP File Manager to delete as many dpi changer files I could find from system/app-priv and data/data, and wiped cache/dalvik — all no help. I have no idea why it wouldn't have reverted the dpi by now. There must be something else.
[Galaxy Note 4 Q&A, Help & Troubleshooting] QuoPrimum:
Sorry about that. Perhaps you could replace systemui itself?
[Galaxy Note 4 Q&A, Help & Troubleshooting] O's:
Not your fault, of course. Any thoughts welcome. I've tried to replace System UI with other UI mods, to no avail. I'm trying different combinations of wiping and restoring between this backup and past one from before the dpi debacle. Nothing so far, but it's a mission now. If it's fixable, I'm gonna do it.
[Galaxy Note 4 Q&A, Help & Troubleshooting] ghostwheel:
you could do a dirty flash of same rom. After backup of course.
[Galaxy Note 4 Q&A, Help & Troubleshooting] QuoPrimum:
There is a guide on XDA to change dpi using adb, assuming your phone still boots.
[Galaxy Note 4 Q&A, Help & Troubleshooting] PasSlert:
I had the same issue in the past, cannot remember if I fixed it or just reflashed from zero : now I don't modify (whole system) dpi's anymore.

Any chance you can grab the RR DPI changer apk, and share it, to know the method used to change the dpi ?

Do you get bootloop ?

Or since SystemUI is "broken" it does finish boot, but ROM is unusable (notification bar appears, then disappear in loop ? Or lockscreen keep restarting ?)

Or is it the persistent "SystemUI has stopped working" that is preventing you to do any actions ?

May be flashing a dpi changer from TWRP could work... I know most of them just re-update the build.prop, but may be try the stock 480dpi from here :

https://forums.oneplus.com/threads/flashable-zips-to-change-your-dpi-on-android-6-0.401639/

Hope you'll solve this issue !
[Samsung Galaxy J7 Guides, News, & Discussion] Kello12012:
Hello Everyone....

Yesterday, I installed a custom rom on my Galaxy J7 using TWRP and Odin.

The Stock version had Android 6.0.1 but I wanted to use the latest One UI.

So I went for the PhoneZippy Rom which supported One UI and Android 9.0.1

Later the next day, I restarted my phone only to find that it showed "Custom Binary blocked by FRP Lock"

I tried various ways like flashing the stock rom again but there was no luck.

Every time I try to load TWRP or Stock android it would block the transfer.

Is there some way by which I can turn the OEM unlock on again without actually booting into android becaise the screen lights up and turns off nor does it allow me to download anything it just blocks it.

Is there any other "free" method by which I can get my OS back??

Plz help.
[Samsung Galaxy J7 Guides, News, & Discussion] dodo2244:
Look for some videos on YouTube; search for "bypass frp lock"
[Samsung Galaxy J7 Guides, News, & Discussion] Kello12012:
Thankyou but I already tried that. My Android, recovery and Sownload mode all are not working. The download mode blocks any 3rd party install.

On YT it only has the google or binary lock but I feel that the new rom re-enabled the OEM unlock in the settings.....
[Samsung Galaxy J7 Guides, News, & Discussion] Germoon:
I had the same situation. But it happened because I turned off OEM Unlock))) I just downloaded stock rom

(By SamFirm, if what), and flashed it via Odin. By the way, are you sure that you have new drivers??

It is impossible to turn on OEM Unlock in this state.

The only mode in which you can boot your phone, is download mode. Another method exists, but you need to dissasable your phone.
[Samsung Galaxy J7 Guides, News, & Discussion] Kello12012:
Thankyou, I think I saw the OEM unlock off on the new rom. Thanks, I'll try flashing the stock rom again.?
[Samsung Galaxy J7 Guides, News, & Discussion] Kello12012:
And also can you tell the other way..because I once tried flashing the stock rom which I got from Pangu.com, but it didn't work..
[Samsung Galaxy J7 Guides, News, & Discussion] Germoon:
Try to use SamFirm. This programm download official firmware of Samsung (i dunno, actually, from where it takes official roms). With this programm you can download firmware for each Samsung model))

But it is really works. Also, you can try Samsung Smart Switch. It will erase your phone. But it's offiicial Samsung Software, and it will use official rom.
[Samsung Galaxy J7 Guides, News, & Discussion] Kello12012:
Samsung Switch does not detect my device it says unsupported device.
[Samsung Galaxy J7 Guides, News, & Discussion] Germoon:
Nonono. Enter in download mode, than in top of programm look for restore or something similiar (cannot remember). Enter model and S/N of your phone. And click recover, or something similiar (really cannot remember :) )

---------- Post added at 06:07 PM ---------- Previous post was at 06:04 PM ----------

Or just use SamFirm with odin

---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------

And how it can say that your device is unsupported, if galaxy s4 mini (gt-i9195) from 2013 year support Smart Switch.
[Samsung Galaxy J7 Guides, News, & Discussion] Germoon:
How are you there??? Restored phone?? :o
[Samsung Galaxy J7 Guides, News, & Discussion] Kello12012:
Thanks for your concern but no luck yet .... I'll try again.?
[Samsung Galaxy J7 Guides, News, & Discussion] Kello12012:
Thankyou

Thanks your SamFirm idea saved my phone. I got the Stock Android back and then enabled OEM Unlock again and now I'm back on Android 9.0. Thanks again
[Samsung Galaxy J7 Guides, News, & Discussion] dodo2244:
Congs! ?
[Samsung Galaxy J7 Guides, News, & Discussion] Kello12012:
Thanks✌?
[Samsung Galaxy J7 Guides, News, & Discussion] Shaffaq:
Try chimera a pc software that unlocks frp lock and tells u which stock rom is suitable for your version
[Google Pixel 4 XL Questions & Answers] alwynjoshy:
Hi,

Can anyone can view your voicemails as visually on your dailer app. Support team said it already activated on phone. When i move my sim to older phone i can use that function but not in pixel phone
[Google Pixel 4 XL Questions & Answers] stevexyz0:
Works for me on Verizon. Who is your carrier?
[Google Pixel 4 XL Questions & Answers] alwynjoshy:
Simple mobiles by T-mobile. It was working when i was using Op6 with Custom rom. Even I tried today changing sim back to my old phone and on my custom rom oneplus 6 that feature still working. Pixel support says it was something problem with carrier wise
[Google Pixel 4 XL Questions & Answers] mattgyver:
Thread closed as duplicate of https://xdaforums.com/pixel-4-xl/help/visual-voice-mailbox-t4048125

Do no cross-post. When you post in the wrong sub-forum, please report the post to the moderator staff, and we can move it.

thanks!
[T-Mobile LG G6 Questions & Answers] InfiniteShade:
I understand that the tuner uses the headphones as an antenna. Is there a way to reroute the sound output to a bluetooth headset; 3rd party app or otherwise? As soon as I connect a BT device it turns the tuner off, even though BT is already on. Is it possible to change restrictions of the app somehow?

Thanks
[Touch Diamond, MDA Compact IV General] siklosib:
Hi,

does anybody know if this phone supports UMTS on 850 Mhz? According to the specification on the HTC Europe homepage it does not. Here in Latin America according to some salesman the version for America supports it. But since this model is not yet on the HTC Latin America homepage i'm not sure if it was already launched or if even exist a vesion for America.

thanks,
[Touch Diamond, MDA Compact IV General] jomo25:
no version for US avail yet. The US version, assuming its a GSM phone (not CDMA), would support 850. But no announcement offically about that yet. ALL CURRENTLY AVAILABLE DIAMONDS as of July 2, 2008 DO NOT SUPPORT 850 UMTS, and to date, no one has found a way to make it support 850 UMTS (i.e. it is a hardware issue, not a software or ROM issue).
[Touch Diamond, MDA Compact IV General] wfhowell:
850 usa phone

If we (I) am lucky,,,this will happen.

http://www.mobilecityonline.com/wireless/store/productdetail.asp?productid=23369

http://www.htcphonestore.com/product.asp?itemMDL=HTC_DIAMOND_US
[Touch Diamond, MDA Compact IV General] goneill:
It has been announced here in Australia that our biggest carrier, Telstra will market the Diamond exclusively for 3 months from the end of July with a 850/2100 UMTS version. Other carriers here use 900/2100 UMTS.

So where we normally get these devices early with Asia and Europe, this Telstra deal will push us back with the U.S. I don't think we will see a 900 UMTS version here till end October, unless we buy online from HK or elsewhere with compromised warranty.

Bummer.
[Touch Diamond, MDA Compact IV General] bjgtir:
Telstra in Australia has announced that the "NextG" i.e 850MHz UTMS/HSDPA diamond will be released in August
[Touch Diamond, MDA Compact IV General] ResLo:
The Diamond will go on sale in Australia on July 28th at the T-Life stores in Sydney and Melbourne.

All other Telstra stores will stock it from August 4th.
[Honor View 20 Questions & Answers] Exoticwaqas:
i want honor view 20 pct-l29 9.0.0.170(c432e1r3p1) update_full_base filee

anyone if this file plz give me help me
[Honor View 20 Questions & Answers] letschky:
http://https://xdaforums.com/honor-view-20/development/stockroms-t3955026
[Honor View 20 Questions & Answers] Exoticwaqas:
link is not working with me
[Honor View 20 Questions & Answers] letschky:
oh sorry my bad

https://xdaforums.com/honor-view-20/development/stockroms-t3955026

---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------

but please at your own risk!

Some People report brick the Phone and some say it works
[Nexus 5X Android Development] theandroid02:
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

Working

All

Broken

Nothing (?)

Sources:

Device tree: https://github.com/Toomoch/android_device_lge_bullhead

Kernel source: https://github.com/Toomoch/android_kernel_lge_bullhead

Vendor source: https://github.com/Toomoch/android_vendor_lge_bullhead

Downloads:

lineage-17.1-20210714-UNOFFICIAL-bullhead.zip

lineage-17.1-20210121-UNOFFICIAL-bullhead_blod.zip

Installation:

Make full wipe (Format data and also normal wipe)

Flash normal or BLOD patched .zip

Flash GApps if needed

Flash Magisk if needed

Building:

Manifest with build guide: https://github.com/Toomoch/android_local_manifest_bullhead

Credits

Thanks to all PixelExperience contributors and thanks to @equlog for helping me solve a lot of errors.

XDA:DevDB Information

LineageOS 17.1, ROM for the LG Nexus 5X

Contributors

theandroid02

Source Code: https://github.com/LineageOS

ROM OS Version: Android 10

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Lastest Official

Version Information

Status: Beta

Created 2020-02-12

Last Updated 2020-07-17
[Nexus 5X Android Development] theandroid02:
Reserved
[Nexus 5X Android Development] nobodywasishere:
This is beautiful. Thank you. If you need devices for this let me know.

Also, do you know if it'd be possible to incorperate the bootloop fix directly in LineageOS. (github xcnathan32/4Core-Android-O-5X). I know the device charter forbids messing with clock speeds, which the fix technically does, I'd hope they would make an exception in this case
[Nexus 5X Android Development] theandroid02:
It would definitely need to be an exception, but even more it shouldn't get just merged and done because there are still devices that are not bootlooping or have been fixed, and the patch would degrade performance. The solution would be to make 2 builds, one patched and the other normal, but I think they don't want to go through the hassle that that is
[Nexus 5X Android Development] nobodywasishere:
As far as I understood it, and I could be wrong, there was no true "fix" for the device besides sending it to China to have the SoC replaced with one from a Nexus 6(?), which in itself was pretty expensive. Essentially all devices would eventually bootloop, just some last longer than others. I imagine the installation process would also have to include methods for getting out of the bootloop in order to enable adb/unlock the bootloader, which they may not like either, but these devices are everywhere and I think it's a waste to not do with them what we can. The ones that "won't turn on" are really cheap too, at $10 a piece, and after heating the motherboard with a heat gun (I'm sorry Rossmann) they turn on again, at least for a few hours. That's long enough to apply the fix and get the ROM installed.

Two builds may work but that'd be a lot. I'd rather just have the normal one and make people flash the patch during the install/update process tbh.
[Nexus 5X Android Development] Rahulmsinghvi:
Known issues and encryption?

Thanks a lot to Dev for bringing Lineage OS to this device. Before I flash just wanted to know if there are any known issues and is encryption working?
[Nexus 5X Android Development] theandroid02:
Force encryption is disabled by default. Haven't tried to encrypt it through settings, gonna try now.

Edit: don't try to encrypt, i'm labeling it as broken for now.
[Nexus 5X Android Development] panamera2011:
Hi theandroid02, I flash thi rom with last Open Gapps nano and after finish wizard app Google and Chrome does not work properly.

Before installing lineage-17.1-20200215 I was using lineage-17.1-20200115 and didn't have this problem. I have done a full wipe

Edit: Same problem also with FlameGApps.
[Nexus 5X Android Development] siemens_wolf:
Gapps，using ARM64, 10.0, Nano version. Right?
[Nexus 5X Android Development] theandroid02:
I haven't made a build in 20200215, you are probably talking about equlog's rom on his telegram group
[Nexus 5X Android Development] theandroid02:
Yes
[Nexus 5X Android Development] panamera2011:
Ok Sorry, I thought you used the same repo [emoji1]

Mi 9 SE using Tapatalk
[Nexus 5X Android Development] Unipo:
Thank you very much OP
[Nexus 5X Android Development] a8962383:
Chrome isn't working

I have used pico Gapps.
[Nexus 5X Android Development] theandroid02:
I'll look into it as I finished my exams just now.
[Nexus 5X Android Development] piekay:
Is Safetynet working yet?

Edit: It is working
[Nexus 5X Android Development] piekay:
Same for all other browsers and Disney+, Netflix, couldn't test Prime Video yet.

Seems to be a network error:
[Nexus 5X Android Development] panamera2011:
I think that this project is dead. Try Lineage 17.1 by equlog, the best ROM Android 10 for N5X

https://androidfilehost.com/?w=files&flid=304349

Mi 9 SE using Tapatalk
[Nexus 5X Android Development] zEdosh:
is there a thread for it? I would like to read some comments about it.

I'm searching the most fast and lag free rom for this phone
[Nexus 5X Android Development] panamera2011:
There no a thread for this ROM, equlog develop it for some friends as you can read in Nexus ROM thread.

I have tried all ROM with Android 10 and Lineage 17.1 by equlog is the best, smooth and stable ;)
[Nexus 5X Android Development] dbuf7:
Other than bluetooth, this build works very nicely, and keeps this device alive and usable. Would love to see an occasional security release, but if that is not meant to be, many thanks anyway!!
[Nexus 5X Android Development] zEdosh:
So i can use it with my daily driver? No bugs at all/little bugs?
[Nexus 5X Android Development] panamera2011:
Yes this ROM is the best for daily driver.

Personally I will use it for a long time :)

Mi 9 SE using Tapatalk
[Nexus 5X Android Development] zEdosh:
at the first boot it says that decryption failed even if my phone isn't encryped. so i cannot boot the system UI properly. What should i do?
[Nexus 5X Android Development] panamera2011:
Backup your internal strage, go to into recovery end format data, factory reset, wipe system, wipe data, wipe dalvik, wipe cache end reinstall the ROM

Mi 9 SE using Tapatalk
[Nexus 5X Android Development] zEdosh:
and for the gapps? any suggests?
[Nexus 5X Android Development] panamera2011:
Open Gapps 10 nano or pico. personally I prefer pico

Mi 9 SE using Tapatalk
[Nexus 5X Android Development] theandroid02:
New build released based on PixelExperience tree with no bugs and an integrated BLOD patch as suggested by [MENTION=9955215]nobodywasishere[/MENTION], you no longed need to flash the .zip patch. I recommend a full wipe because of the tree change and rebooting after the setup wizard.
[Nexus 5X Android Development] gmurli.android:
I installed the BLOD version along with nano gapps and it installed fine. I was also pleasantly surprised to see that the VOLTE is enabled (first android 10 I'm seeing this option under Network settings) but i'm not sure that if its actually working.

Basically the network switches from LTE to 3G/H+ when a voice call is in progress. I installed the factory dec 2018 image and with 8.1, the network does stay at LTE when a voice call is in progress.

If anyone has insights here, please let reply.

thanks.
[Nexus 5X Android Development] lakshay18:
Eh, you pushed the commits too early xD

Check new VoLTE commits (F pushed :P).
[Nexus 5X Android Development] theandroid02:
New build today I guess :laugh:
[Nexus 5X Android Development] treesap:
Edit: Ignore below original message. 5th times the charm, apparently. It only took <5 minutes for initial boot. I didn't flash gapps this time, so it seems that's the problem.

Further update: So the latest version of gapps, seems to be incompatible. After multiple tries, it still did not work. I flashed the 2020-05-30 version and had no problems booting.

And another update: I'm calling it quits for tonight. Initial setup for older version gapps kept force quitting every minute or so. Will try some more tomorrow. Any tips are appreciated.

Original message:

How long should the first boot take? I've waited more than 45 minutes on the animated loading screen. I don't recall first boot taking quite this long when I flashed earlier (8.x) ROMs. I've tried it a few times (with both the normal and the BLOD-patched versions), with the same result. Am I not waiting long enough, or am I doing something wrong in these steps? (I feel like I must be doing something wrong.)

Steps I took:

Re-flashed to stock with final official release of Android (just to confirm proper phone operation—everything worked great)

Flashed latest TWRP

Wiped everything but internal storage (should I be wiping system? I believe I tried with and without, but it'd be nice to know.)

Flashed Lineage 17.1 (BLOD and normal)

Wipe cache/dalvik (tried without wiping, also)

Flashed gapps nano

Reboot

Thanks!
[Nexus 5X Android Development] theandroid02:
Sorry, I forgot to mention that wiping system is required and also the Format data option as it unencrypts the storage if it was encrypted. New build coming in aprox. two hours EDIT: nope definetly not 2h

Also, opengapps work fine here, july 6 version
[Nexus 5X Android Development] Hapoofesgeli:
Thank you for this!

I do face some random bugs but most important one being camera not working. (BLOD)
[Nexus 5X Android Development] kum4423:
When charging a phone, Led indicator light does not work...

lineage-17.1-20200602-UNOFFICIAL-bullhead-BLOD
[Nexus 5X Android Development] theandroid02:
New build: 20200612

Changelog:

Enable call recording, Snap camera and Trust USB restrictions.

Fix notification LED and maybe camera crashes (PixelExperience change).

Kernel is now upstreamed to 3.10.108

Update build fingerprint to Dec 2018 OPM7.181205.001

June security patch

Links: https://github.com/Toomoch/android_device_lge_bullhead/releases/tag/20200612
[Nexus 5X Android Development] gmurli.android:
Thanks. Does this update include any new VOLTE commits?
[Nexus 5X Android Development] theandroid02:
It includes everything from the lastest PixelExperience. I belive it should work with VoLTE but I can't test it.
[Nexus 5X Android Development] gmurli.android:
Great. I'll test it out and let you know. thanks
[Nexus 5X Android Development] berom:
volte usually doesn't work on android 9 and 10 ROM. I haven't tested the volte patch from PE 10 yet.
[Nexus 5X Android Development] Hapoofesgeli:
Camera still broken (doesn't crash outright this time though), just black screen and then crash after a while.
[Nexus 5X Android Development] gmurli.android:
I am unable to boot this on my 5X. I even tried applying the BOD patch separately. I have gone back to lineage 15.1 with the June security patch.
[Nexus 5X Android Development] kum4423:
Led indicator light and Camera fixed!!! Thanks!!!
[Nexus 5X Android Development] theandroid02:
For all I know it should work, as my device is blod and I checked the blod build. Make sure you wiped dalvik, cache, system and also used the option on the bottom right in the wipe section "format data" if you are coming from an encrypted rom.
[Nexus 5X Android Development] gmurli.android:
I tried various things

fastboot format userdata -> wipe everything -> adb sideload <zip> -> wipe cache -> boot to system

fastboot format userdata -> wipe everything -> format data with twrp -> adb sideload <zip> -> wipe cache -> boot to system

fastboot format userdata -> wipe everything -> format data -> copy zip and install from twrp -> wipe cache -> boot to system

Neither the 0612 nor the 0602 images would boot.

Suspecting a hardware failure, i went back to stock to dec 2018 which installed fine. I then followed the above steps and installed lineage 15.1 with june security patch and it booted OK.

I would love to generate logs but no thread can give me clear instructions on how to get adb logcat working WHILE the phone is booting. Suggestions welcome.

thanks

thanks
[Nexus 5X Android Development] kum4423:
1. Boot your device into TWRP recovery. You can simply Google how to enter recovery mode on your device.

2. In TWRP recovery, click on Wipe » Advanced Wipe. Here select the following options dalvik cache/ART. Do not select the option which reads ‘Internal Storage‘ at any cost, as it will wipe off EVERYTHING, including your ROM file.

3. Go back to TWRP main menu, tap on Install and select the Lineage OS Zip file.

4. After selecting the .zip file, do Swipe to Confirm Flash on the bottom of the screen to begin the custom ROM installation process. This may take some time.

5. Once your ROM is successfully flashed, you’ll see Wipe cache/Dalvik option, select it and then do Swipe to wipe on the bottom of the screen.

6. Now flash the Lineage OS Gapps file similarly like you flashed the ROM file.

7. After flashing both ROM and Gapps files, reboot your device.

https://kum4423.hateblo.jp/entry/2020/06/11/170138

Good luck boy!
[Nexus 5X Android Development] gmurli.android:
I have tried what has been stated above. In addition to all these steps, I also tried flashing using adb sideload <zip> from TWRP. Furthermore, I followed the same steps and the latest Bliss ROM + nano gapps does boot successfully. Again I'd love to provide logs if anyone can provide how to pull logs with adb logcat DURING a boot.

thanks
[Nexus 5X Android Development] dangpzanco:
hi, are there any plans on turning this into an official build of LineageOS?

thanks for your efforts
[Nexus 5X Android Development] Fl0k1337:
+1
[Nexus 5X Android Development] shhnedo:
[MENTION=3396071]dangpzanco[/MENTION] [MENTION=8158901]Fl0k1337[/MENTION]

https://xdaforums.com/showpost.php?p=81763345&postcount=4