yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] manjaroid:
If your Pixel has the all clear with T-mobile and it's SIM unlocked, I believe you need a wifi connection for OEM unlock to light up and become switchable. Once that's done unlocking the bootloader with fastboot should work.
[Google Pixel 7] MotoX4:
I covered that in the OP post, but let me be more clear.

Factory reset with default setup (sim in phone, connect to Wi-Fi, log into Google Account)

Factory reset without sim, with Wi-Fi, with Google

Factory reset with sim, no Wi-Fi, with Google

Factory reset with no sim, no Wi-Fi, no Google.

Factory reset with sim, with Wi-Fi, no Google

Factory reset with default setup using 3rd party sim (TracPhone)

I don't think how I am doing this is the problem.
[Google Pixel 7] manjaroid:
Factory reset implied a wifi connection but I mention it anyway.

I thought T-mobile phones were more straight forward than than what you're dealing with. My only other ideas are wait for whatever is sideways at t-mobile to even out, or flash factory firmware.
[Google Pixel 7] MotoX4:
I don't think it is going to "even itself out" and rather this may be the new norm.

Verizon didn't exactly make a public announcement, that they would no longer allow OEM Unlocking, but rather just did it, and anyone who complained, were just told sim unlock was good enough. I think that is what may be happening here, because I'm slowly reading more post like mine, elsewhere.

A lot of people I know, pay a little over time, as opposed to the lump sum, even if they have the money (as I did). I would not be surprised if more people find themselves with the same problem.
[Google Pixel 7] manjaroid:
Everything you've described seems to support that. Sorry to hear.
[Google Pixel 7] MotoX4:
I really do hope I am wrong.

Not everyone is OEM Unlocking for personal choices or reasons, but for work related reasons, and not all of us can be buying in mass bulk from manufactures to obtain the few devices we need. For now, we are lucky some still sell individual units directly to the consumer, I guess.
[Google Pixel 7] TKruzze:
I had the exact same symptoms on an older pixel phone. To fix it (after being SIM unlocked) I factory reset the phone, then flashed the latest factory image from Googles website, then another factory reset. After that, unlock appeared.

In case you're wondering, you CAN flash a factory image even if your bootloader is locked. Also, make sure you grab the correct image (definitely NOT the Verizon image).

EDIT: Corrected below.
[Google Pixel 7] MotoX4:
I am going to have to wait to see if I can do that or not. 1 of the T-Mobile agents gave me some bad advice. They wanted me to be sure I was using the latest software and perform a software upset. I was already on the February 2024 release (this month's release). https://developers.google.com/android/ota

The T-Mobile agent had convinced me that if we could force it to perform a full cycle, by upping the OTA ROM build, it may correct the issue, and it was suggested I could opt into the Android Beta https://www.google.com/android/beta Google's website reports you can opt into or out of Android 14 QPR2, but I currently have Android 14 QPR3. My timing is the problem, as I opt in during their transition phase. If I opt out of the beta, I don't receive the current public version (phone stays on Android 14 QPR3 Beta 1). I need to wait until they release the next beta, whether that is Beta 1.1 or 2.0, so long it is the next build. Then I can downgrade back to stable, and attempt what you suggested.

Because right now, if I perform a manual installation using the OTA Release (see 1st URL), it would correctly abort, claiming what I have on my device is already newer.
[Google Pixel 7] Furious Froyo:
Corrected.
[Google Pixel 7] 41rw4lk:
What exactly is confirmed?
[Google Pixel 7] TKruzze:
Only YOU have the ability to unlock your bootloader. It doesn't confirm a thing. Try my recommendation above AFTER T-Mobile provides the SIM unlock.

While it is possible that you both are the first 2 people in the universe to have acquired Pixel devices from T-Mobile that can't be unlocked, I would think that there would be far more noise if this was their new policy.
[Google Pixel 7] TKruzze:
You're welcome! :unsure:
[Google Pixel 7] Furious Froyo:
Since you seem to know, you stated you can flash a factory image with the bootloader locked. Could I go from T-Mobile to global with it locked?
[Google Pixel 7] Lughnasadh:
How are you flashing a factory image with a locked bootloader? The only way I know is to sideload the Full OTA zip, or if you have OEM Unlocking enabled, to use Android Flash Tool which will unlock your bootloader for you if you have that enabled.
[Google Pixel 7] TKruzze:
As I wrote above, I also thought that my phone was also unable to be unlocked on an older Pixel device. However, the steps I took to remedy the problem were a bit different from what I wrote above after looking back at my original Reddit post on the steps I took to unlock my bootloader on a carrier locked device.

That said, once your device is bootloader unlocked you should be able to flash whatever factory image you want. However, I only see Standard, Verizon, and Softbank images available with the latest Stable Factory images (Feb 2024). [ @MotoX4 ]

The problem with getting older is what you remember to be true isn't always so :rolleyes:.

You are, indeed, correct that you can only sideload the OTA on a locked bootloader. As my answer above indicated, my recollection of events from 3 years ago wasn't quite accurate.

However, one thing I would strongly recommend to anyone on a carrier purchased Pixel is to unlock the bootloader and then immediately flash a full factory image, followed by a second factory reset. Doing this will ensure that the device is exactly the same as if it were purchased directly from Google with all carrier cruft removed. If you're not planning to root the device, I would also recommend re-locking the bootloader to ensure device integrity.
[Google Pixel 7] Talysdaddy:
This thread is confusing, so is TMO's Pixel 7's bootloader unlockable or was the OP flipping out for no reason, they didn't factory reset at the end was their only issue preventing the unlock? My Pixel 6 had to factory reset at the end too..

OP kind of vanished after someone mentioned factory reset, Im assuming felt embarrassed and will ditch that account forever? All the abandoned accts due to owners feelin crunchy, they need a day of remembrance..
[Google Pixel 7] rodken:
Possibly, carrier-locked phones will become less attractive to modders in the future if that's the hand we are dealt.

Carrier-locked phones might become less appealing for some, if not all modders, but it's difficult to predict their complete disappearance. The future might see a shift in modding techniques or a rise in used unlocked phone prices, keeping carrier-locked phones maybe somewhat relevant in the modding scene.
[Samsung Galaxy A52s 5G] Deleted member 12802856:
Hi there,

I must have something missed while flashing LineageOS 20 to my device...

Some tips would be appreciated, as I'm new to this whole process :)

At first I flashed TWRP 3.7.0 according to BlackMesa123's tutorial. This worked like a charm.

I proceeded by flashing the latest BL and CP (but not CSC) images via Odin from BlackMesa123's Samsung firmware repo to be able to install an Android 13 based ROM (I installed all available OTA updates while the device was still running the stock ROM... I got Android 12).

Then I flashed LineageOS 20.0 for microG. It booted and on first sight seems to work well... Except WiFi.

I can turn it on but it never would discover any networks. When trying to turn on the hotspot, it disables itself again after a few seconds and showing the text "Error".

Otherwise, I can make phone calls, use mobile data and Bluetooth is able to discover nearby devices.

Could this be some firmware issue (eg. flashed for wrong region, wrong, mismatching images, do I need CSC?, etc.) ?

Thank you for your help!

zw.
[Samsung Galaxy A52s 5G] Deleted member 12802856:
Problem solved:

I flashed BL and CP from the latest Samsung firmware (A528BXXS6FXA1), which belongs to Android 14 / OneUI 6. LineageOS 20 seems to work with that, except that WiFi does not work.

Installing LineageOS 21 immediately solves the problem.

I'd rather like to use LineageOS 20 for microG, but that's unfortunately no longer possible as for the latest Android 14 based Samsung firmware, SW Ref. has been increased to 6. So downgrading to SW Ref. 5 versions of CP and BL (which come with Android 13 based ROMs) is no longer possible

Downgrading CP was possible... So I tried this (leaving BL at it's newest version). But that didn't solve the wifi problem unfortunately.

Can't wait for LOS 21 to be supported officially on this phone... so thanks to everybody here investing their time and working on this! :)

zw.
[Samsung Galaxy A52s 5G] Simon1511:
As I already said a few times (in both the LOS 20 and 21 threads): Android 14 / OneUI 6 firmware is not, and will not be, supported by LineageOS 20.

[ROM][14.0][ENCRYPTION] Official LineageOS 21 for A52s 5G

LineageOS is a free, community built, aftermarket firmware distribution of Android 14, 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...

xdaforums.com

Also I've personally been daily driving 21 for a few weeks now without any issues, so you might just want to install 21 and then upgrade to the official builds once they're out.
[Samsung Galaxy A52s 5G] Deleted member 12802856:
Typing this from my phone running exactly this ROM. Works perfectly :)

There is one thing I'd like to ask, though.

Did you try to enable gesture typing in the stock AOSP keyboard? In my previous ROMs (until LOS 18) I just copied over a library which I got from OpenGapps and it worked. - And I got quite used to it.

For the Android 14 AOSP keyboard, I tried the same. Copied over libjni_latinimegoogle.so into the lib64 folder which I extracted from the appropriate MindTheGapps-ZIP.

Unfortunately this doesn't work anymore or I got the wrong lib.

Do you know of anybody who got this to work? I'm using microG and want to avoid Google Keyboard if possible.

Thanks!

zw.
[Samsung Galaxy A52s 5G] Simon1511:
Under Settings -> System -> Keyboard -> Touchscreen keyboard (not sure if its called like that in English) -> AOSP keyboard you can enable gesture typing, you don't need to swap any libs for it to work.
[Samsung Galaxy A52s 5G] Deleted member 12802856:
Unfortunately I do not seem to find it.

I went to: (Settings) -> System -> Keyboard -> Screen Keyboard -> AOSP Keyboard

I don't see any settings regarding gesture typing.

Could you send me a screenshot or anything?

I recall, in my older ROMs, exactly these settings appeared when copying over the lib.

Thanks!

zw.
[Samsung Galaxy A52s 5G] Simon1511:
This is with LineageOS 21 + MindTheGapps installed (in German, sorry). Not sure if MTG added it or not.
[Samsung Galaxy A52s 5G] Deleted member 12802856:
My phone is German as well, so no problem :). Exactly this menu "Gesteneingabe" is missing. I don't have MindTheGapps because I'm using microG.

But it really looks like MindTheGapps installs the necessary stuff then.

I found the libs inside the zip file.

I may have just failed to install them properly. Just copying these to the system partition didn't work.

Will try to figure this out by looking at what the MindTheGapps zip is doing during installation.

Thanks for confirming that it should work on LOS 20/21!
[Samsung Galaxy A52s 5G] Deleted member 12802856:
It works now.

Needed to move it to /product/lib64

For some reason I did not investigate further, I can't do it via TWRP (the file just disappears after booting LOS). I did it via ADB while the system runs and restarted the keyboard afterwards.
[Nothing Phone 2] Noryakky:
If you have root, you can try:

echo 255 > /sys/class/leds/led_strips/all_brightness

echo 0 > /sys/class/leds/led_strips/all_brightness
[Xiaomi Mi CC9 / Mi 9 Lite Questions & Answers] antwoine.westlee:
Use the official LineageOS 20 incl. weekly updates until the end of 2023 incl. Magsik. From then on I suspended the updates for a few weeks.

Then I installed an update from February. After that, the message "Problems with the SD card ... Format SD to fix ..." plus a constant popup with the message "com.android.providers.media is constantly terminated".

I have formatted the SD card several times both internally and externally on the PC.

The message that there was a problem with the SD card was still there, as was the message with the Android service.

After that I realized that I could no longer download at all. With every attempt, whether Playstore, browser or other app, only the message "com. android etc etc crash" came up, but installed apps could still access and save their data even if they were not on external storage.

I then waited for 3 more Lineage updates and flashed them in the hope that the error would be fixed, but nothing. Then I flashed a few versions from December that were running, but the error was not fixed there either.

The tip I found was to stop the Android service and then clear the cache etc. there. The service could not be stopped with board means and no cache could be deleted.

The service could not be stopped with on-board means and the cache could not be deleted either. I then helped with the app SD-Maid which still had root rights.

Stopped the service, deleted the cache and memory, restarted the service. The message was gone until the next attempted download.

I then deleted the app "com.android.providers.media.*" via adb in the hope that it would be reinstalled with a new update. Lineage update done, Gapps installed. The file is still missing, but now my SD card has completely disappeared from the Android administration and is no longer displayed, I see a lot of free memory there ... 97 of 128GB free. But when I want to download something from the Playstore, it says I have no free memory. Apps can no longer save anything either. But I can still install apps normally via ADB, which then also work.

How can I reintegrate my SD card or generally regain access to the internal memory without losing data?

The same with the SD card, how do I bind them again so that it is displayed to me again in Android? If it is due to this deleted service, why is it not simply reinstalled with the new update. You can somehow force a real update at Linage where everything is really overwritten. It seems to me that when charging the full image, only a part of the update really overwritten and not completely everything as with the only installation! There should be a "force" command here!?

btw: tody a new Linage Update was released "lineage-20.0-20240213-nightly-pyxis-signed.zip" if i will flash it the normal way in recovery:

after verification ...

assert failed: update_dynamic_partition(package_extract_file("dynamic_partitions_op_list"))

ERROR recovery: Error in /sideload.package.zip (status1)

Install campleted with status 1.

Installation aborted

WTF is this now?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pradipbaral3:
Is there any Custom Kernel for stock MIUI 14 for poco f3?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] bozinsky73:
There are a lot of them.

Balaam and N0kernel are the most stable and used for Miui
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] evnimaster:
Balaam works great
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pradipbaral3:
Does it have any issues for MIUI 14 ??

Are you Using One for Daily Driver??

I know it must have many Pros but does it have any cons?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pradipbaral3:
Does they have any issues for MIUI 14 ??

Are you Using One for Daily Driver??

I know it must have many Pros but does it have any cons?

For Gaming which one should I choose?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] bozinsky73:
I use N0KERNEL and it's just amazing. No issues found so far. It needs you to download and flash dtbo for Miui version.

Search for it and you won't regret
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pradipbaral3:
Can I get the Link for it?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] GolDeN_xXx:
Can you share with us the download link?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] evnimaster:
Here iti is ... there is a dedicated thread in this same forum, also ...

BAALAM Kernel - Xiaomi SM8250 Platform

/** I am not responsible for bricked devices, dead SD cards, thermonuclear* war, or the current covid-19 pandemic caused by you following these* directions. YOU are choosing to make these...

www.pling.com
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] bozinsky73:
[KERNEL][AOSP/MIUI] N0Kernel 2.4

DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FLASHING THIS KERNEL AND ITS YOUR CHOICE TO DO IT OR NOT TO DO IT AND YOU'RE THE ONE DOING IT. I JUST WANT TO HELP OTHERS OUT. REQUIREMENTS: UNLOCKED BOOTLOADER AND AOSP BASED ROM, IT...

xdaforums.com

search for latest update, starting from the link given in the OP message
[Oppo Find N] webernard:
Hello'

I'm trying to activate the Google Assistant on my Oppo Find N2:

I launch the application, it opens a window which tells me 'set Google as default assistance application...'

I click on the button which takes me to the 'digital assistant app' settings

I click on assistant application, and I select Google (the choice already checked when I get there is 'none')

I go back after checking Google (no other choice)

and there, the assistant is launched at the bottom of the screen is displayed 'hello how can I help you'

and I can make a voice request

but if I open recent apps and close everything,

Google assistant closes and I have to start the whole operation again,

the choice of the assistant does not remain in memory, each time, 'none' is not reset by default in the choice of assistants, in the device settings!

I would like Google Assistant to launch when I say hey Google or when I longpress the home button

btw, in google settings, there is a message 'hey google is not available on this device'

Can you help me please ?

Thanks in advance
[FYT Android Head Units] lurebat:
Most people here post faults and errors, which is fair, but is there an headunit you glad you got? Didn't cause you issues?

I'll pay as much as needed
[FYT Android Head Units] Teddis007:
Don't get a DAINAV......if you want support, they are terrible.
[FYT Android Head Units] lurebat:
How's IYING? They have ones with all the specs for relatively cheap
[FYT Android Head Units] Teddis007:
Sorry, I don't know. I am on my first Android and trying to better it.
[FYT Android Head Units] j0hn83:
It all depends on what you want from your head unit.

If you want the latest and greatest processor, high ram/storage, etc, then you want the newest generation UIS7870SC devices.

It's very new, not yet completely stable and it's much more locked down with regards to modding and rooting the unit

If you want what's still a high spec unit with the ability to mod it somewhat, with a more stable platform that's been refined over a few years then you want to go for a UIS7862S device.

Most of the units between resellers are very similar with the only real difference between devices being the screen, MCU, the DSP audio processor, bluetooth chip and radio chip.

Support varies quite a bit between resellers.

I found with most sellers I've dealt with that if you aren't asking for support during Chinese daytime working hours then you might be stuck with slow 1 question / 1 answer per day support.

All these Chinese aftermarket units have their quirks and flaws in the software. If you can't live with some of them then you would be better buying a known brand (Sony, kenwood, pioneer, etc) but even they aren't perfect.

Compatibility with your specific car is also something to consider. Some cars makes/models have premium audio systems that might not be compatible with the canbus boxes supplied for that particular car. Usually the seller lists these on their product page but not always.

Personally I've went with a Mekede M6 Pro Plus (2k screen version) with the highest available RAM and with an optional HDMI IN port added.

I was considering upgrading to a 7870 chip device but I'm holding off to see how the platform develops and whether anyone works out a way to do some kind of proper modding/flashing of the head units.
[FYT Android Head Units] Teddis007:
@j0hn83 , how do you determine what BT chip you have ?
[Windows Mobile Development and Hacking General] xtep:
New opera build extracted from latest (30/12/2008) Omnia ROM:

http://www.megaupload.com/?d=MH67LC7D

It has the same features (zoom style, scroll window, etc) than previus builds from Omnia ROMs

Enjoy :)
[Windows Mobile Development and Hacking General] conflipper:
very nice, i have always considered omnia opera builds some of the best.

any chance you have a link for the rom?
[Windows Mobile Development and Hacking General] TrYde:
In the line of the 1957 ? Great i'm gonna test it :)
[Windows Mobile Development and Hacking General] TrYde:
Played a bit with this version, Flashlite 3 worked after reinstall on memory (i had Opera on SD and this one is on memory)

I can't tell if it is much faster than the build 1957, but it scrolls fast, the zoom is smooth and there is no landscape issues with my kaiser when using the hardware keyboard. I also noticed that it lags less than previous build when scrolling/zooming with flash stuff on the page.

I love it :)
[Windows Mobile Development and Hacking General] sparhawk6:
Darn, didn't fix two of my issues - Stars don't show up on the Google Reader Iphone version (google.com/reader/i) and my phone is still identified as a mobile device for ESPN.com. The mobile version loads automatically and I cannot get the regular version to load, even though in my settings I have it set to identify itself as a desktop computer.

Anyone else run into these issues?
[Windows Mobile Development and Hacking General] barty22:
Thanks!

Anyone got a mirror? I can't download this thing from megaupload, very weird!
[Windows Mobile Development and Hacking General] itwasntme187:
Just installed this version and now everytime i start my phone is just insists on loading up opera on its own, and if i close it, it will just fire it back up every minute

very annoying!
[Windows Mobile Development and Hacking General] itwasntme187:
I found the culprit...

the application OperapreL.exe was loading up everytime so i just moved it to a different location so the phone cant load it... and now it works fine :)
[Windows Mobile Development and Hacking General] gogorob:
mirror

http://rapidshare.com/files/178322331/Opera_v9.5_build_15233_QVGA.cab
[Windows Mobile Development and Hacking General] SprintGuy765:
I tried installing this to my sister's touch and it was saying installation was unsuccessful. the program or setting cannot be installed because it does not have sufficient system permissions
[Windows Mobile Development and Hacking General] lesscro:
This Opera version is awesome...

FAST, cool interface... Flash 3 work now...

Zoom bar in right side... no keyboard problem...

wow ! i think one of better Opera build tested for me...

THX for this gift ! happy new year ! :D:D:D
[Windows Mobile Development and Hacking General] WildSioux:
Any way to get a SD version please?

I am using the 2520 version from the omnia that is the two file upgrade from the 1957 version. The omnia versions have always been the best.

Thanks
[Windows Mobile Development and Hacking General] VidMan:
Can one of you guys please try https://secure.k12planet.com in this build. Im still on build 2128 because every build after this one results in the site saying that the browser is incompatible. I need this site to work for school. Thanks.

Edit: If it works, the page will show a login screen. Wait until the page stops loading because on the Opera builds where it doesn't work, it briefly shows the login screen before quickly changing to the browser incompatibility page.
[Windows Mobile Development and Hacking General] WildSioux:
^^^vidman...that site loaded for me on 2520
[Windows Mobile Development and Hacking General] ngagephone:
Hi can any one tell me how to get the zoom slider on this version thanx.