yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6a] Lada333:
That's actually mind-blowing to me. I assume moving from SD SOCs to Tensor took a lot longer than Google expected. I'm glad they are able to fix most of the issues through software updates.

I have not done much research regarding this topic, what I said was purely based on the fact that seemingly year over year, they make modding more difficult. Before my 4a I was running a OnePlus 3T, and I was absolutely devastated by the fact that Google tweaked some stuff with how the recovery works, meaning TWRP or any other custom recoveries are basically a thing of the past.
[Google Pixel 6a] Matrix1999:
I just bought one since there is a good deal going on and I managed to OEM unlock with the steps listed above. I am running 12 and not 13, not sure if that matters or not. I want to hold out on installing 13 to run custom ROMs.
[Google Pixel 6a] Twilightsparklez:
Calyx, graphene and (kind of?) Lineage are updated for 13. I actually recommend to update. My experience small with 12 made me consider returning my phone to google and getting samsung due to it being a buggy nightmare
[Google Pixel 6a] Matrix1999:
I want to upgrade as well but I have read that once upgraded to 13 you cannot downgrade due to the new bootloader is no longer being downloadable.

How to downgrade to Android 12 from Android 13 on the Google Pixel 6 series

www.xda-developers.com
[Google Pixel 6a] Aqq123:
You can still downgrade to 12L with the Developer Support Build:

Developer Support images for Pixel | Android Developers

Instructions for downloading and installing Developer Support system images for Pixel devices

developer.android.com
[Google Pixel 6a] Matrix1999:
Oh that's really good to know. I was worried that the bootloader issue may cause me headaches down the road when Lineage or other AOSP 13 ROMs become available.
[Google Pixel 6a] ritchea:
FWIW (0, I suspect), I just factory reset my direct-from-google unlocked 6a due to some other issues. OEM unlocking had never been available. To note, my Day 1 6a had to be replaced nearly immediately as it locked up after an update (or course I couldn't do anything to fix it because OEM unlock had not been available on that one, either). AT&T prepaid. I have gone through everything suggested (except be on July update) and still not available. One reset was within the system; two were through recovery. All were completed without sim in phone. OEM unlocking is still greyed out. I would go back to google, but I'd had so much problem running G-Pay with unlocked BL on my 3a, that I eventually re-locked and said to hell with it. Just reporting that, for whatever reason, bootloader unlocking is still unavailable on devices. I also just tried the toggle Developer Settings as reported in another thread--no OEM unlock.
[Google Pixel 6a] Twilightsparklez:
If its an att model, call them up. They need to unlock it or you need to wait for it to be paid off
[Google Pixel 6a] ritchea:
I appreciate your help. Sorry I wasn't clear with direct from Google unlocked. I use Att prepaid but bought carrier-free. I wish att could handle it since Google can't seem to.
[Google Pixel 6a] bobby janow:
Return it for a refund or replacement.
[Google Pixel 6a] ritchea:
I'm still considering that although the first replacement is the one I have now. It had to be replaced (no UNLOCK available, but that wasn't the reason for replacement) within a week or two of receiving it. I did this recent factory reset due to loss of cellular signal over the past couple of weeks. Yesterday, I lost the signal while my son, same phone and same cellular service/account, who was sitting next to me had no issues.--full bars. If that returns, I will have to send for a replacement.
[Google Pixel 6a] ritchea:
I realize this is very late, but I'm still looking into this since I had to (second time in two weeks) reset my phone. (this BL thing, touch screen locks up, losing mobile connectivity, and now battery only charges to 99%---that may not be new). I'm on 13--Nov update. I have this:

[sys.boot.reason.last]: [cold]

[sys.boot_completed]: [1]

[sys.bootstat.first_boot_completed]: [1]

[sys.fuse.transcode_enabled]: [true]

[sys.init.perf_lsm_hooks]: [1]

[sys.oem_unlock_allowed]: [0]

[sys.rescue_boot_count]: [1]

I'm assuming I cannot change that to a "1" since my BL is locked. I can find no reason for this as I have model GA03715-US of Model GX7AS bought directly from Google, no carrier involved (unlocked). AFAICT, the wrong software has been applied.
[Google Pixel 6a] bobby janow:
Sorry you're going through this but it's an aberration and not normal behavior. I just received another 6a, put my sim in, logged in and OEM was grayed out. Did the update (still A12 but a later one) factory reset and OEM unlock was available. That is the way it's supposed to be. No need to remove a sim, put in a different one, go on wifi only, that's just nonsense if you bought it unlocked from Google. No signal drops other than the usual Verzion crap and now fully updated to A13 November update. As I said before, this is a flawed device and you should return it for your money back if you still can. A replacement will be refurbished and that should be uncacceptable but unfortunately all you might be able to get if you're outside the return window.
[Google Pixel 6a] ritchea:
Thanks. Unfortunately, it was pre-purchased before release. (It's about the 12th Google/Pixel device I've owned.) If I could "trade-in" on a 7, I'd think about it. That isn't an option now. Current phone was replaced during the second week after the ota caused a bootloop. That one was new.
[Google Pixel 6a] ectavgen:
Having the same issue with my wife's P6a. The one that I got was on A13 from the box and OEM toggler was working. The other one (with problem) was wшер A12. I've installed all the security patches all the way to A13 with settings been reset — still no luck. BTW both phones are from Japan (GB17L).
[Google Pixel 6a] Lada333:
Are we 100% sure on that? Mine also had OEM unlocking greyed out out of the box, even after an update to A13. I didn't really care too much for it. Few days ago, I went to see if it's still greyed out, and it no longer is? I have done nothing to my device. No updates since, no nothing, it just seemingly happened overnight? How the hell does that work anyway?
[Google Pixel 6a] ectavgen:
I think that Google have some database of IMEIs and when you set up your phone it checks if the device should be locked or not. And it could be possible if this option is checking not once but any other time.
[Google Pixel 6a] lafester01:
Just got my pixel and had to follow the steps here to allow unlocking. Android 12, direct from google.
[Google Pixel 6a] ritchea:
2nd reply as an update. I posted in the other thread my experience this morning. After the last reset, a few of the issues seem to have disappeared. I'm slowly re-installing the apps to see if any create problems. As the other post states, Google is not, at this time, willing to send a replacement. I'll wait a month for a reply from the escalation team before I serious.
[Google Pixel 6a] bobby janow:
Well you're more patient than I would be, that's for sure. They really should replace it especially since your son's device behaves correctly and was ordered the same day. Let us know when you can get it unlocked. It seems like they are just blowing you off since you are a nice guy. The squeaky wheel gets the grease, just sayin'.
[Google Pixel 6a] ritchea:
It's cool. I try to be "nice," but I've gone the limit with both Comcast and Samsung (not to under mention straightening out a very disorganized and unresponsive MSC ship CS desk/business center while on 25 days from Italy through Norwegian fiords last spring), and each ended up well. Patience is the technique but determination is the winning hand. I only ask for what each has promised. Google promised an unlocked device. That's what I expect to have. My wheel may not squeak, but it will keep rolling for months, if needed.
[Google Pixel 6a] bobby janow:
Words to live by. Keep us posted. If you need a strong arm my fees are reasonable.
[Google Pixel 6a] fix-this!:
Just bought my 6a from Best buy. It's unlocked. The OEM is greyed out as well. I'm on the lastest android 13 December patch. Any ideas?
[Google Pixel 6a] ritchea:
and to bobbyj, too,

Google support contacted me a little over a week ago saying that they would send me a replacement phone. It took a day or so to get the email to "purchase" it, but it was delivered next day after that. It wasn't in the regular box, but I think it's a new device--just part of the "for replacement" bin? When I turned it on, it was on Nov update. I started up the phone without a sim and did not connect to internet until I was directed to do so when trying the next step: trying to toggle the OEM unlock which was grayed out. (OMG! Really?) Connected to internet. OEM still greyed out. Well, having tried every trick posted, I went with the easiest: toggle Developer Options button. Nothing. #2--factory reset. Nothing. #3 toggle the DO button again. This time, the OEM unlock was available to toggle. I did. After that, I continued the setup; inserted the sim, and copied from my current phone.; updated to Dec. I checked the OEM unlock toggle: still available; still sitting on the allow side where I put it. I have checked it out a few more times and, so far, it's still available.

Returning the phone was also very fast and easy.

I did combine several of the many "fixes" (no sim, no internet, no sign-in) with the factory reset scheme. To Fix-this!, if you factory reset and toggle the Developer Options switch, and OEM Unlock doesn't become available, take it back for another. (I know from my son's phone, that these steps are not always necessary.) If you have to contact Google, Chat worked well.
[Google Pixel 6a] sysKin:
My 6a just got an update (TQ1A.230105.001.A2) and after rebooting, the OEM Unlocking option became available -- for the first time in my phone's history.
[Google Pixel 6a] ck.chunkeat:
May I know which set is your 6a? US or JP set?

Also, how long has it been since you had the 6a?
[Google Pixel 6a] sysKin:
G1AZG, bought in Australian retail.

Have had it since Black Friday.
[Google Pixel 6a] KGBagentIvan:
I've read that update to Android 13 modifies bootloader
[Google Pixel 6a] V0latyle:
The update increments the bootloader anti-rollback on a successful boot of Android 13. That's all it does - prevent downgrading the bootloader. This was done to patch an exploit discovered in the Pixel 6 series Android 12 bootloader.
[Google Pixel 6a] ritchea:
YAY! for you. Google support said they were working on it. I was willing to wait, but they sent a replacement. It, overall, does seem to be free if issues. The Jan update improve fingerprint reader for me.
[Google Pixel 6a] i-hate-phones:
I just want to post here to warn anyone considering buying this piece of trash phone to think again, and choose a different model. I never would have bought a google phone in the first place because I fully expected issues like this from an awful corporation like google, but I wanted to try GrapheneOS and pixels are the only option..

I bought an unlocked phone and I am unable to enable unlocking no matter what I try. I got it on sale for a good price, forgot about it until the return window closed, and now I am stuck with this POS that refuses to let me enable unlocking. I have tried sideloading the latest updates, factory reset probably 30 times, nothing works.

This is completely unacceptable. My $300 device that I OWN should not have to phone home to google, in the process sending them my wifi local data and god knows what else, just to allow me to use it the way I want. The modern state of technology is truly pitiful, and big brother google sure as heck doesn't care about anyone they can't profile and make money off of. I'm convinced at this point that this is just blatant datamining. Honestly I'm about to just throw this thing out the window and try to forget about it.

Update: using public wifi and running some sort of '''update''' (even though I had already sideloaded the most recent OTA...) has enabled OEM unlocking. I would still advise anyone to not purchase this phone if they care about privacy and don't want to feed google their data. Walking down to the shopping center in the cold was a pain in the a** but after having given google $300 of my hard-earned dollars I refuse to give them a single iota more. This is blatant datamining, not a 'bug' and a big F U to those of us who prefer to use custom android builds and generally expect to own the devices we pay for. Death to google I say, and if GrapheneOS wasn't so promising I would just sell this thing on ebay.
[Google Pixel 6a] MONGTAY:
Is there currently a way to enable OEM unlock on Pixel 6a from Verizon?
[Google Pixel 6a] mike.s:
No, and it's unlikely there will be.
[Google Pixel 6a] tmittelstaedt:
I just picked up a Pixel 6a 2 days ago running A12 and it had the option greyed out. Running all updates including the update to A13 and connecting the phone to wifi and giving it a few hours fixe the problem. The phone is a model GX7AS
[Google Pixel 6a] mmead1143:
^^

run back thru the thread - I too had the issue and figured it out via this thread. Can't remember now but you will find the exact issue - GL
[Google Pixel 6a] bdizzle1686:
I bought mine back in mid December 2022, option was greyed out, performed a factory reset about 2 weeks later, and option was available, and has been since .

Yes, it sucks that a factory reset is required to fix the issue, but y'all are making too much of an issue about it.

Every phone I've ever owned (from Samsung, to htc, to Motorola, to Lenovo-rola, to Nexus, to Pixels, have all had their own issues..

This is by far my favorite phone I've ever owned, (and I've owned ALOT)

Do yourself the favor, factory reset it and enable OEM unlocking. Presto all better
[Google Pixel 6a] induna:
Just another data point. I bought my 6a just before Christmas. It arrived with Android 12 and OEM unlocking greyed out. It continued to be grayed out after updating to 13 and stayed that way until just the other day. I rebooted the phone because it was acting funny. It was a very long reboot but afterwards OEM locking was available. I have no idea what happened.
[Google Pixel 6a] EliteBlackKaiser:
I'm pretty sure their are some pixels devices on some carriers who don't support the bootloader unlock. And most carriers have put a stop to bootloader's being unlocked until the phone is paid off to prevent modifications/ warranty voiding while they still own the phone.

For example I received my 6a from Spectrum Mobile , opened it up , turned the phone one and tried every step you mentioned and with no luck it was still greyed out. Ended up finding out I couldn't get Spectrum to send the unlock until I paid the phone off... When I paid the phone off within minutes they sent the unlock confirmation to my phone and I was able to factory unlock my phone...

And currently on LOS 20 , magisk , and modules.
[Google Pixel 6a] john-aurelio:
I solved the problem
[Google Pixel 6a] john-aurelio:
go to settings and then go down to reset options enter and press erase all data.
[Google Pixel 6a] kisjoska:
I have the same problem. What to do?
[Google Pixel 6a] Bobbore89:
Stessa cosa con moto g42 sto aggiornando il software e provo a vedere le varie cose che ho letto
[Google Pixel 6a] Wyattx17:
I bought 2 pixel 6a's from the google fi store and both of them were locked. On one of them, I went through the upgrades to android 13 and it was still greyed out. I did 3 factory resets and I was able to toggle OEM unlocking in the developer options. It seems like random luck to me. Not sure what I did to be honest.
[Google Pixel 6a] Singlespeed10:
My understanding is that the A4RGB17L is for the Japan market only.
[Google Pixel 6a] TechX1991:
you nearly always have to connect either to wifi or cellular signal before oem unlock will pop up. This isn't new.

Also, your clear issue with google shows you shouldn't use an iphone or android phone either way. All android phones data mine. All iPhones data mine. Your windows computers and macOS computers data mine.

You're just paranoid, and it shows lol
[Google Pixel 6a] wpscully:
Installing Android 14 solves this, for an unlocked phone bought directly from Google. But I had to do a full system reset.
[Google Pixel 6a] nwpfh:
I solved it.

I do checkin of "Prepare your device" at below link.

Flash with Android Flash Tool | Android Open Source Project

source.android.com
[Touch Pro, Fuze ROM Development] Keystone:
Now that as of the past few weeks several carriers in North America have released the CDMA version of the Raphael, should the forums and members now make a strong distinction for ROM development with TWO separate forums under the titles "GSM Raphael ROM Development" & "CDMA Raphael ROM Development"?? :cool:

I've already made quick edits under the Raphael wiki to change the "Raphael upgrading/cooking/flashing" to be preceded with GSM. ... plus added a strong warning under the Raphael hardSPL page that it is only for the GSM model.

If would be great if all developers could from now on title the ROMs and SPLs as per the device they are intended for rather than what is now a generic but potentially incompatible blanket heading of 'Raphael.'

No sense in encouraging confusion and n00bs bricking their phone.

....I'm still a Titan owner and have been used to having our own isolation where device specific development-confusion is rare.
[Touch Pro, Fuze ROM Development] dontdo_that:
[CDMA/GSM][ROM][LANGUAGE][DATE]rom name and version (Build)[STATUS]

like that?
[Touch Pro, Fuze ROM Development] reyjabs:
It's a good point and I vote for this notion.
[Samsung Galaxy A50 Questions & Answers] Qrrty:
Yesterday I decided to upgrade the Android version of my Samsung Galaxy A50 from 9 Pie to 10 (and after that I wanted to upgrade it to Android 11), buy after the installing process of Android 10 finished, my phone was not able to start anymore, showing me the Android Recovery page and the error “/system/bin/tune2fs is missing”. The upgrade to Android 10 didn’t work.

I think I should install some firmware with Odin, but I never did that before. Also, my phone isn’t rooted. Can someone tell me how to do it? And, in view of the fact that I want Android 11 at the end, should I search for Android 9, 10 or 11 firmware? Can you “jump” from Android 9 to 11?
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] Speedy15928:
I have a Redmi Note 11 Pro 5G running Magisk which passes safetynet but google pay still doesn't work.

I heard I can try spoofing my fingerprint with MagiskHidePropsConf but I do not have a certified fingerprint for my Redmi Note 11 Pro, and it's not on the existing list - any ideas?
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] Vincent Foxx:
I use SELinuxModeChanger+11.0, and also use magisk hide. Then enable magisk hide in the settings, then go to the superuse tab (the one with a shield icon on the bottom) and start togging all google services.

works for me
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] Speedy15928:
What does selinuxmodechanger do? Never heard of it.

And yeah I added all Google services to the blacklist
[Redmi 9 / Poco M2 Questions & Answers] sadfunda:
long story short, I uninstalled updates for default "Files" filepicker (com.google.android.documentsui), and I cant find a way to get the more recent version back.

xiaomi system app updater doesnt have it, playstore doesnt have it.

I tried xiaomi ADB tools to see if I could get it back, there was no option

I tried ADB adb shell cmd package install-existing com.google.android.documentsui , it didnt seem to do anything even though I got operation sucess

I downloaded the same rom from c.mi.com, unpacked the system.new.dat.br and it had no .apk like that at all

at this point im considering just downloading it from apkmirror and trying to install it with ADB (i have no root)

my redmi 9 is model M2004J19AG, firmware MIUI Global 12.0.2.0 Stable(QJCMIXM) android 10

i dont want to update to 12.5 cause i seen there are problems with it, but i have the option to OTA to 12.0.4. still scared of losing data or something being broken, and not even solving the issue

any input would be welcome
[Redmi 9 / Poco M2 Questions & Answers] adhilfuad:
See

DocumentsUI | Android Open Source Project

source.android.com
[Redmi 9 / Poco M2 Questions & Answers] VPH20:
Go to system/priv-app/Googledocumentsui

Copy all apks to such as documents

Install all with a split installer package manager
[General Topics] GrayJack:
Hi All.

Let's assume I have two SIMs on phone.

SIM1 corresponds to roaming, the carrier supports VoLTE and VoWiFi so I can easily enjoy home pricing for calls and messages as soon as I have WiFi.

SIM2 corresponds to local provider and allows to have access to 4G internet for quite cheap price.

The task is to make SIM1 working using SIM2 internet in the places where WiFi is not available.

This approach sometimes is called as "pseudo-VoWiFi" and works on iPhones and latest Samsung phones with One UI 4.

My question: is it possible to realize such pseudo-VoWiFi on any Android phone? For instance, now I have two network interfaces:

View attachment 5687821

Is there any way to forcely push routes to IMS service to use rmnet0 rather than swlan0 to make VoWiFi working with mobile internet?

Any suggestions/ideas on this?
[Windows Mobile Development and Hacking General] gregzem:
Hi

I couldn't find answer at the forum in existing posts so I'm asking about it here.

I need to extract files from WM6.1 Emulator image file, e.g. PPC_USA.bin.

I can extract file system from .nbh files (e.g. XPERIA ROM), but when I try to do same steps for PPC_USA.bin, tool says, that there's no boot sector. I can't figure out what is .bin: is it .nbh, .nb or .bin which we usually get when it's extracted from .nb?

Thank you.

Greg
[Windows Mobile Development and Hacking General] ghettofreeryder:
Copy the bin file into the root of this directory, and run prepit

http://www.megaupload.com/?d=6RQD783K
[Windows Mobile Development and Hacking General] gregzem:
Thank you so much.
[Windows Mobile Development and Hacking General] nir36:
next time, ask your questions in the Questions & Answers section.

thanks.

(and again, DONT answer questions here!)
[Nubia Red Magic 7 Pro] abm09:
hello guys i have a problem when i root the device

i unlock bootloader then reboot after that the device is looping cant start up

any fix or wipe option

tried vol up + power i got

<!>

i think its Brick so any unbrick tool
[Xiaomi Mi 11 Ultra] aygul12345:
Hi,

Im testing my phone without, NON-TWRP.

After root, and shutdown/restart the phone, the phone boots automaticly to Miui recovery instead of starting the phone normally...

After 10 min, the phone starts in the normall mode with root.

How to fix this that the phone that the phone doesnt boot into recovery mode of Miui?
[Xiaomi Mi 11 Ultra] krepsz:
Reflash tje boot.img from the rom.
[Xiaomi Mi 11 Ultra] aygul12345:
If I flash the orginal boot.img of the current rom, then its unrooted. But If I patch the current/boot.img of the current rom and flash it with the modified_magisk_boot.img file, it boot into the bootloop recovery; MUIU Recover 5.0
[Xiaomi Mi 11 Ultra] krepsz:
Ok. Than you have to reflash the rom. I mean its helps.
[Xiaomi Mi 11 Ultra] aygul12345:
What do you mean to reflash the rom?

I flashed now the orginal boot.img and now the phone boots but without ROOT.

Now, If i take the orginal boot.img to magisk_modified_boot.img (fastboot flash boot magisk_patched-25200_MSizj.img) then the phone gets in the recovery-MUIU 5.0 Bootloop.

So what am doing wrong?
[Xiaomi Mi 11 Ultra] krepsz:
Patch again the boot.img and flash it trough fastboot.
[Xiaomi Mi 11 Ultra] aygul12345:
Same result... the next boot is into the MUIU Recovery bootloop.
[OnePlus 9] Yasser.d:
Hi everyone! I have a question! Does anyone know how to install a custom rom on the oneplus 9 t mobile with OOS 12? Do I have to downgrade or can I install a rom that has android 12 by default?

My version its LE2117_11_C.19