yashsingh1/xdaforums huggingface dataset:
[Google Pixel Fold] almony8:
I am now on beta 2 and still can't get root. I can flash the ota file and boot up no problem. As soon as I patch the file and try to boot it just bootloops everytime. I am using pixel flasher to patch the file. I don't have any modules or anything installed on the phone at all. Someone please help me figure out why I can't get root anymore since qpr1?
[Google Pixel Fold] Colchiro:
Have you tried using the image, instead of the OTA?
[Google Pixel Fold] almony8:
I haven't tried that, but I have always used the OTA before. Would that really make a difference? Nobody else is having this issue?
[Google Pixel Fold] sawdoctor:
Do you know how to adb a log while booting? If you can do that when your bootlooping someone in the magisk thread may know what's happening. Also if you are rooting with pixelflasher there will be a log in pixelflasher you could share with pixelflasher Dev.

I'm using latest magisk canary and root with pixelflasher if that helps

Edit

I did this once on pixelflasher and bootlooped so it might be your issue. I didn't clear pixelflasher and the patched boot img from the previous build was still there and I flashed the wrong boot img by mistake
[Google Pixel Fold] almony8:
I'll give it a try again later or tomorrow morning maybe. If it doesn't go well I will get logs. I know how to get the pixelflasher log, not 100% sure about how to get a log when I'm bootlooping though?

I'm using whatever is the latest stable one, could that be the issue? Not sure if it was canary?

As far as the last comment, I guess that is possible, but I have done this like 10 times now since the first qpr beta release and have had the same issue everytime. I have cleared everything in pixel flasher and redone it a bunch, I can't imagine that I did that everytime. Someone mentioned trying the factory image instead of the OTA, would that make a difference, thoughts?
[Google Pixel Fold] krabman:
It's not in unless I'm missing the setting.
[Google Pixel Fold] bs3pro:
If someone is running the beta, and root, download setedit app, and see if the force fullscreen setting is there, maybe us on official, can add it with root .
[Google Pixel Fold] bs3pro:
Any issues rooting the latest beta???
[Google Pixel Fold] almony8:
I am having issues rooting it, but pretty sure I didn't delete or disable all of my modules properly and just have something messing with mine. I still haven't had time to flash the special magisk and get rid of everything. Might do that later today actually. But others seem to be having no issues at all, I'm the only one I have seen mentioning any issues.
[Google Pixel Fold] dubt17:
I've got beta 2 with root, just disabled magisk modules beforehand then flashed using https://flash.android.com/ without wiping data or locking the bootloader. Also downloaded the full beta image, extracted init_boot.img, transfered to phone, patched with magisk, then sent over to my computer for fastboot to flash both init_boot slots on A and B. Been rocking this since method since the first beta for 14 on the fold and it's been holding up!
[Google Pixel Fold] cobram3:
Hi

1) I'm running Android 13 on T-Mobile. Phone is great except it gets hot and battery life is not great.

Besides looks/lock screen /aspect ratio, is Android 14 Much better on the pixel fold?

2) I am enjoying root on 13. If I accept the OTA notification, will I lose root?

Thank you
[Google Pixel Fold] sawdoctor:
Yes. Best way to update and keep root is to use pixelflasher. You can download the ota and patch the boot img and update all in one with pixelflasher
[Google Pixel Fold] krabman:
There are a lot of fixes that are Pixel Fold specific rolled into 14, don't hesitate to move to it. Another way is to flash after editing out the editing out the wipe.
[Google Pixel Fold] hanschke:
Android 14 QPR1 Beta 2.1 rolling out with Pixel bug fixes​

Factory Image — OTA
[Google Pixel Fold] cobram3:
Just want to say thank you for pixel flasher. It made it a breeze and I kept root like you said🙂
[Google Pixel Fold] Colchiro:
Are you still on the beta? Phone as key is acting up again for me. I'm on the Nov 1 update. Dropped the beta just before official Android 14 dropped.
[Google Pixel Fold] fred2546:
Regarding the beta...

I opted in because Google no longer offered me the Android 14 update after I refused it while out of the country. I kept checking for updates after my return and it never showed up. I even called Google and they suggested wiping the phone and restoring. That seemed a painful process. Some on one of the forums suggested opting into the Beta. That worked. I'm on Android 14.

But now the question is can I opt out of the Beta and not have to wipe the phone or jump through other hoops. I just would like to return to a normal (ha! ha!) state with non-beta Android 14. I did get another update just in the last two or three days.
[Google Pixel Fold] Colchiro:
Sorry, you took bad advice. The official fix for your problem is to opt out of the beta, Google sends you the official Android 14 and you need a wipe.

A better option would have been to sideload the OTA using Pixel Flasher.
[Google Pixel Fold] Colchiro:
Another option would be to sideload the latest Android 14 image (not the OTA) with Pixel Flasher and not wipe. If you have any goofiness or bad behavior, then you'd want to wipe. The full image is the only way to go back to a previous Android version.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel Fold] sawdoctor:
Don't think you can go from beta back to stable without a wipe can you? Thought it would fail
[Google Pixel Fold] Colchiro:
I've never gone back to a previous major version, so can only speculate. A decade ago you could. No clue how the current tools work. I know officially, a wipe is required when quitting a beta.
[Google Pixel Fold] fred2546:
DARN (read more colorful language here!!!!!!!!!!!!!!!!!!!!!!!!)
[Google Pixel Fold] dubt17:
I am still on the beta, I ran into one day where I was expiriencing the same loss of my Car not recognizing my phone as a key, and had to manually unlock in the Tesla app, as well as manually lock when I walked away. I rebooted and so far I haven't had the issue again.

I'm on the latest beta: felix_beta-u1b2.230922.013-factory-891a0b61
[Google Pixel Fold] Colchiro:
A reboot helped mine as well. Also think I'm experiencing some random reboots at night. I'm rooted to use adblock, but no mods.
[Google Pixel Fold] sawdoctor:
#Android #A14QPR2

Android 14 QPR2 Beta 1 Changelog & Known issues

Changelog:

• Fixed an issue that caused the package manager to crash when installing some apps.

• Fixed an issue that sometimes prevented users from submitting feedback using the Android Beta Feedback app.

• Fixed an issue that sometimes prevented a device from connecting to a 5G network when it was available.

Known Issues:

• An issue with some apps that use the meta-data element unconventionally prevents these apps from being installed by the system.

• Sometimes when a user unlocks the device using their fingerprint, there is no haptic feedback.

• For Pixel Fold devices, sometimes after a user unlocks the device while it's folded, the inner display doesn't turn on after unfolding the device.

• The Assistant At a Glance widget sometimes displays weather information for the wrong location.

Follow @PixelHubUpdates

Lot of fold bugs
[Google Pixel Fold] bs3pro:
All good on latest beta, rooted too.
[Google Pixel Fold] fred2546:
Okay, you more knowledgeable BETA testers. I see an UPDATE is available but I also see that there's some info that says the Beta can be abandoned without having to wipe the device. Any info on this would be appreciated.

I have PAUSED the download. I just not very keen on having to wipe the device. But then again, BETA's can be interesting. And if you folks have been doing BETA for a while, have there been other opportunities along the way where you could opt out without wiping. In other words, might there be further beta's where that "opt out without wiping" might again be available?
[Google Pixel Fold] sawdoctor:
As i understand it QPR1 beta will become the new stable so you can opt out. Once you are in QPR 2 you have to stay or wipe to leave until QPR3 comes out and QPR2 becomes new stable. I off course bow to people with more knowledge than me
[Google Pixel Fold] fred2546:
Oh, so, presumably this OFF-Track does come up periodically so that I could stay until the next time they offer this opt-out without a WIPE. As you might detect I am not really inclined to wipe and restore.
[Google Pixel Fold] sawdoctor:
The betas are quarterly so I'm guessing every 3 months a beta becomes a stable and you can opt out without a wipe. So if you flash QPR2 in 3 months QPR 3 will be released and you can opt out without wiping. Not 💯 certain on this but think I'm correct.
[Google Pixel Fold] Haizum74:
According to the google

You can opt out of the programme at any time to return to the stable public version of Android. When you opt out of the programme, all user data on the device will be wiped.

During the beta program’s release cycle, there will be stable releases to the public (the official platform release followed by Quarterly Platform Releases (QPRs)). When you apply the stable release update for the version that you’re beta testing, you can opt out without a data wipe for a limited time until you apply the next beta update.
[Google Pixel Fold] fred2546:
Do they always warn you as shown in the screenshot I posted. That is will they provide the same warning screen the next time there's this so-called stable release so that I can opt at at that time? While I use to beta test HP Palmtop devices back in the day, I've not really played with beta versions in a while.

As explained, I only opted to get the beta since Google stopped offering me Android 14 after I initially refused it.
[Google Pixel Fold] cobram3:
Last night I got a system message that a required security update needs to be installed

I installed it and the phone rebooted as the system had said it would, I woke up to see my phone no longer has root :(

@sawdoctor Can I use pixel flasher again to gain root without wiping? I was never on any beta and I never had to wipe moving from 13 to 14.

If you can slightly detail the steps, super appreciate it
[Google Pixel Fold] Colchiro:
Sure. That's how many of us got root the first time.
[Google Pixel Fold] sawdoctor:
If it happens again (you have an update forced on you) don't reboot. Open magisk and select install to inactive slot. This should root the update and when you reboot magsik/root is installed already.

But yes just patch and flash boot img with pixelflasher again without wipe
[Google Pixel Fold] krabman:
It's OEM unlock that gives you the no avoid wipe.
[Google Pixel Fold] hanschke:
Less than a week after the initial release, Google is rolling out Android 14 QPR2 Beta 1.1 as a smaller bug fixer.

There are just two fixes/changelog entries for AP11.231020.016 (Pixel 5a, Pixel 8, and Pixel 8 Pro) and AP11.231020.016.A1 (all other devices).

Fixed an issue that sometimes caused some apps to be removed after a system update was installed and then prevented those apps from being installed again. In other cases, affected apps couldn’t be installed on a device even if they hadn’t been installed previously.

Fixed other issues that were impacting system stability, performance, and connectivity.

Factory Image — OTA
[Google Pixel Fold] hanschke:
Google rolling out Android 14 QPR2 Beta 2 for Pixel​

QPRs are relatively stable and launch as betas rather than developer previews. Google officially says they are “suitable for general use.” Known issues include:

Sometimes when a user unlocks the device using their fingerprint, there is no haptic feedback.

For Pixel Fold devices, sometimes after a user unlocks the device while it’s folded, the inner display doesn’t turn on after unfolding the device.

The Assistant At a Glance widget sometimes displays weather information for the wrong location.

Google notes the following fixes in AP11.231117.006 with the December 2023 security patch:

Fixed an issue where battery usage information that was reported in system settings was sometimes incorrect. (Issue #312121998)

Fixed an issue where the fingerprint icon on the lock screen would sometimes display before other information had loaded in always-on display mode. (Issue #311265905)

Fixed an issue that sometimes caused the biometric prompt to crash, causing it to be dismissed before a user could interact with it.

Fixed an issue that sometimes caused the Internet Quick Settings tile to indicate that there was no Wi-Fi connection, even when the device was connected to a Wi-Fi network.

The Android Beta Feedback app is available on Pixel devices to submit bugs. You can access it from the app drawer or via Quick Settings to file bugs in the Google issue tracker, while the Android Beta community is on Reddit.

Android 14 QPR2 Beta 2 is available for the Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, and Pixel 8 Pro, as well as the Android Emulator.

Most people will be installing via the Android Beta Program, but you can also flash or sideload. If you need help, here’s our full guide on installing Android 14.

Pixel Fold: Factory Image — OTA
[Google Pixel Fold] sawdoctor:
Reports of people losing root and it breaking zygisk so may want to hold off updating for a few days if you intend to root
[Google Pixel Fold] hanschke:
are you sure? I have patched the boot file with latest magisk canary and all work fine here.
[Google Pixel Fold] sawdoctor:
Try enabling zygisk. The update has been merged and is in the debug app
[Google Pixel Fold] bs3pro:
Root does work, but zygisk is broken
[Google Pixel Fold] sawdoctor:
Use the debug app. You need to rename to zip and flash and then name back to apk and install the apk . It's a signature issue so can't just install
[Google Pixel Fold] bs3pro:
Hmmm, i just installed it no problem as an app
[Google Pixel Fold] bs3pro:
Unfortunately themer is partially broken on new build.
[Google Pixel Fold] hubono:
Magisk was updated and the zygist issues were resolved
[Google Pixel Fold] lorddunlow:
So I tried the "install to inactive slot" before reboot after my phone installed the OTA. But upon reboot, I received "your device is corrupt" message and then it hung on the Google screen. Tried to flash and patch OTA via PixelFlasher after that, but it fails and then I reboot into my old version (with root intact). Very strange. If it helps the console in PixelFlasher gives the following at the end of the process that fails:

Device Model: felix

Device Active Slot: a

Device Mode: f.b

Has init_boot partition: True

Device Bootloader Version: felix-1.0-10140901

Device Unlocked: True

slot-retry-count:a: 2

slot-unbootable:a: no

slot-successful:a: yes

slot-retry-count:b: 0

slot-unbootable:b: yes

slot-successful:b: no

My phone is working fine (on the old version, but now I'm a little nervous to proceed. Any advice?
[Google Pixel Fold] fred2546:
My Pixel Fold requires multiple taps or maybe I should say TAPS to awaken the unfolded screen. I would like to opt out of the Beta but not have to deal with losing data/settings/whatever.

Forgive me if I can't quite figure out when I can do that. When can it be done? Should I not install or update any further system updates under Beta - my last was December.

Thanks from someone who has only done this Android beta route this one time and definitely needs direction.
[Google Pixel Fold] sawdoctor:
You can't leave the beta without wiping until qpr2 becomes stable round about march unfortunately
[Google Pixel Fold] krabman:
IMO after updating the beta they should resign the stock ROM with a date after, and this problem would be gone. Super easy; enough so I think they purposefully don't do it for reasons unknown to me.
[Google Pixel Fold] hanschke:
Android 14 QPR2 Beta 3​

Developer- and user-reported issues​

Fixed an issue where SPIR-V sequences of OpShiftLeft followed by OpShiftRight didn’t produce the expected results for ARM Vulkan driver versions 43.0 and 44.0. (Issue #314048080)

Fixed issues that sometimes caused Bluetooth connections to be interrupted for some devices. (Issue #315324137, Issue #317798832)

Fixed issues that sometimes caused a device to crash or become unresponsive after restarting. (Issue #317282987, Issue #316689583, Issue #316188779)

Fixed issues that in some rare cases caused devices to reboot while in idle mode. (Issue #316903919, Issue #316557374)

Fixed an issue that caused live wallpapers to stop animating. (Issue #312869160)

Fixed an issue that prevented Google Assistant from activating in some cases. (Issue #311934282)

Other resolved issues​

Fixed an issue that sometimes caused multi-finger gestures to stop working.

Fixed an issue where the device’s screen didn’t initially turn on when the screen was double-tapped or the power button was pressed.

Fixed an issue that sometimes caused higher than usual CPU usage during video playback.

Fixed a system issue that sometimes caused poor audio quality or higher power consumption when making calls.

Fixed an issue where the keyboard was always shown even if the “Swipe up to start search” setting was disabled in system settings.

Fixed an issue where sometimes when a user unlocked the device using their fingerprint, there was no haptic feedback.

Fixed an issue for Pixel Fold devices where sometimes after a user unlocked the device while it was folded, the inner display didn’t turn on after unfolding the device.

Fixed various issues that were impacting system stability, performance, connectivity, camera, and accessibility.

Factory Image — OTA
[Google Pixel Fold] sawdoctor:
Finally fixed the inner screen not turning on
[Google Pixel Fold] hanschke:
Root worked with magisk 26404 worked again. So I dont need to wait until patches are merged.
[Google Pixel Fold] fred2546:
It appears to have fixed the problem I had with the Inner Screen staying dark when UNfolding.
[Google Pixel Fold] sawdoctor:
That's fantastic news, i got myself in a world of pain trying to fix 26404 and still recovering might even have to do a full wipe or very least wipe Google play services which is a pia.

All your root apps still working? Main ones for me are Pixelxpert and colorblendr
[Google Pixel Fold] hanschke:
Swift Backup Work and Pixel Launcher Mods too
[Google Pixel Fold] sawdoctor:
How did you install 26404 ? I've tried to update through the app with direct install (on beta3) and I still lose root
[Google Pixel Fold] hanschke:
I use IT since I wrote here. I have done the manager update inside magisk from your APK. Flash the full Image without wipe and patched the init boot and use adb for flashing and have root
[Google Pixel Fold] sawdoctor:
So you didn't do direct install? You patched the boot img from within the app and then flashed the patched boot img with adb?
[Google Pixel Fold] hanschke:
I was on the 03 Magisk from you. I have the channel on Canary yes and just updated to the latest version of the manager.

Then simply installed Android 14 beta 3 with flashall.bat but removed the -w. Took the unpacked init boot from the image and patched in Magisk 26404 (65207f96) and switched to fastboot and installed according to the instructions https://xdaforums.com/t/successfully-rooted.4600551/.

After the reboot everything is available and I could not find out that something is not working so far. That was the reason why I wrote this and I would have warned you to stay with the old version.
[Google Pixel Fold] sawdoctor:
Ok so I figured out the issue. Magical overlays module was making me lose root, as soon as I enabled it in Magisk and rebooted i lost root. Just booted safe mode and then reboot again with all modules disabled and i got root back.

I am now having an issue with lsposed unfortunately, don't know if you have the same error

Edit

It was updating shamiko that caused lsposed issues. Went back to shamiko 0.75 and error went away
[Samsung Galaxy Tab A series Questions & Answers] typiclagabriel:
Hi! First post so I had a quick question I was looking for custom ROMs for this device and i came along a androidfilehost page anyways does the SM-T350 ROMs work with an SM-T380?
[Redmi Note 10 Pro] Deekshan:
Is anyone able to use DualSense controller on Android 13 with the correct mapping on Redmi Note 10 Pro? I'm on Xiaomi EU MIUI 14.0.20 and the mappings are still wrong (X is square etc). I tried many magisk modules but the issue persists.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] G H 4 D Z:
Hello guys its my first time to post a question.. how about the android 13 encryption error in custom recovery.. how fix it?
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] zgfg:
A13 has a different FBE Data encryption than A12 (and A12 different than A11)

Unless you found TWRP/OFox/SHRP or so where dev/users claim that it supports A13, it won't work

Official TWRP.me does not support A13 - their page says that development for A13 has started

---

Assuming of course that you tried by entering your Android screen unlock pin and that TWRP (when supporting FBE = File Based Encryption) answers that it successfully decrypted for user 0, but not for user 9 (second space, work profile and so - custom recoveries never successfully decrypt for user 9)
[General Questions and Answers] YoshiTheGamerYT:
Google Play Services discontinued many android versions, example:

Android 2.2 in 2013 or 2014, Android 2.3 and 3.0 in 2016, Android 4.0 in 2019 and Android 4.1-4.3 in 2021.

And Google Play Services will discontinue android 4.4 in this 2023?

Because every 2 or 3 years Play Services discontinues an older android version.
[General Questions and Answers] xXx yYy:
What's the problem with that?
[Nokia 7.1 Questions & Answers] Troughy:
So today I unlocked the bootloader on my Nokia 7.1, and I tried to install LineageOS on it

I haven't done anything like this before so I just tried following the instructions found here

I got to #14 but the phone just got stuck on the android one screen, it did not boot into twrp.

I have been trying so many different things, wiped everything (from the older twrp the partition tool installed, and I tried sideloading lineageos with that but it just didn't work, (Flashing A/B zip to inactive slot: B and on PC: Total xfer: 0.00x and it just says Failed on the phone) but right now I can't even install the stock rom because I can't find the stock rom online! At least not from official sources, the post on here is old too and the stock rom is just gone from sourceforge

So right now I probably deleted the stock rom and don't know how to reinstall it

tbh I just wanted to root the phone cos I've never done that before but I've also heard of lineageos and decided to go with that
[Nokia 7.1 Questions & Answers] Troughy:
alright so i just renamed the file to twrp.img and with fastboot boot twrp.img now it booted into twrp and I'm currently sideloading lineageos... what a waste of time