yashsingh1/xdaforums huggingface dataset:
[ASUS ROG Phone 3 Accessories] ReCiDiV:
I sent my kunai back today. Too many cons. This is too much length of the phone in the hands with these controls, flimsy plastic that does not cause a sense of strength on the tires and controls as well as the case on which they are attached. After installing the cover and the controllers, it became clear that the left side of the hempad was very loose and with strong inclinations, the contacts were interrupted very often, so the joysticks were turned off and re-turned on.4 Too few games with support for the joystick as well as the inconvenient left analog stick control, through the chur long, the same Nintendo switch analog stick on the joystick is much smaller more pleasant and convenient.5 this is naturally the price, too long for such a set, there are no rubber plugs for the cover on which the jostles are attached, after disconnecting the jostles there are open bus connections with contacts, why are there no additional rubber bands to protect the attachment after disconnecting the gamepads
[ASUS ROG Phone 3 Accessories] Dreamcoat:
I'm pretty happy with my Kunai 3 gamepad, but I am facing one issue. Sometimes after connecting it in a USB handheld mode, one or none of the joy cons are working. When this happens i have to reconnect them or switch from usb mode to bluetooth and back to usb in order for them to work. Is this a software related issue?
[Touch Diamond, MDA Compact IV General] fettoskyffel:
Hello

I´ve searched the forum for similar problem but havent found anything.

I have installed RealVNC on my Diamond but it cannot connect, get error "Unable to resolve ip by name: (11001)".

But if i start YouTube application and lets it connect, exit youtube then starting RealVNC it works great.

Do i have to allow internet access or something?

Greatful for help /Stefan
[Touch Diamond, MDA Compact IV General] rhedgehog:
it sounds like it could be.

When you start VNC without already being connected to the internet, do you see the arrows moving to show a connection being made?

if not, it seems the VNC application is not initiating a network connection. this would explain why it works after opening youtube.....

Is there any settings in the RealVNC application to specify a connection to use (not used it before, i tend to use logmein)?

If not, you could always go into the com manager and turn the data connection on, before using the program.
[Touch Diamond, MDA Compact IV General] fettoskyffel:
There is no options for connection in realvnc and in com manager the dataconnection is "greyed".

When i start youtube and then go to com manager the dataconnection is on, but if i turn it off i cant turn it back on again?

Thanks for helping
[Touch Diamond, MDA Compact IV General] rhedgehog:
so it sounds like realVNC is not initiating the data connection when it is needed.

With the diamond, you should be able to manually connect using the comm manager. the fact that it is greyed out and not switchable is a little disturbing. It sounds almost as if you have the old comm manager where you can only disconnect.

Have you installed any comm managers or done any tweaks? or is it literally out of the box and you just installed VNC?
[Touch Diamond, MDA Compact IV General] fettoskyffel:
The phone was completley orignal when i tested.

Yesterday i installed "Ruu_Signed_Duttys_Diamond_5.2.20275_V1_8_Radio_1.00.25.07_Full" and the problem is the same apart from the dataconnection doesent turn of until i turn it off manually.

When its off it says "no data connection exist" in com manager.
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Sushrut1101:
OrangeFox Recovery Project

​

/*
* Your warranty is now void.
*
* I am NOT responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, I will laugh at you.
*
*/

OrangeFox is a FREE SOFTWARE​

Downloads

:

MOD EDIT: DOWNLOAD LINK REMOVED (*updated link)

Documentation and Frequently Asked Questions

: https://wiki.orangefox.tech/en/guides

INSTALLATION:

0. Backup your ROM, your data, your internal storage, and your settings/apps, to an external device

1. Download the OrangeFox zip file to your device

2. Reboot to your custom TWRP-based Recovery

3. Install the OrangeFox zip file as a normal zip

4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)

5. Enjoy!

Source Code

: https://gitlab.com/OrangeFox

Credits

:

* TeamWin - for TWRP

All our Devs and Testers
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Sushrut1101:
I have updated the link of google drive

Now Everyone can Download the File
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] RKRN3@1997:
Thanks for the awesome recovery! Fixed encryption related issues in Android 11.
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] sidrek:
Hi, when I try to download, the file is download in .bin format instead of .zip format. What am I doing wrong. Please advise.
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Sushrut1101:
I Just Downloaded and it downloads zip only

You contact me on Telegram MOD EDIT: DOWNLOAD LINK REMOVED and I will Guide you :)

Or Rather Join This: MOD EDIT: DOWNLOAD LINK REMOVED for Support :)
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Sushrut1101:
Telegram Support for This Build : MOD EDIT: DOWNLOAD LINK REMOVED

Join this group for Support :)
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Deleted member 11233617:
Try downloading again.. i have downloaded it's downlaoaded in zip format and even flashed
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] harukidesu:
And I can't use sideload to send zips
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] rishisur8:
again 0 mb showing..no internal storage..what is this problem?
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Sushrut1101:
Join MOD EDIT: DOWNLOAD LINK REMOVED For Support
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] LEGACY710:
works great, looks great. could not ask for anything more :)
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] Botsadid101:
can I flash android 11 roms with this?

:):)
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] ZainBilq:
Yes, you can flash.
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] hjs85:
Can I flash this from maurinfro twrp?
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] RKRN3@1997:
Yes
[Xiaomi Poco X2 ROMs, Kernels, Recoveries, & Other ] strongst:
Thread closed until kernel sources are provided.

OP: Please check your Message-Inbox for more information.

You can read about it HERE why it's mandatory to post actual kernel sources according to GPLv2.

Thanks

strongst

Forum Moderator
[Samsung Galaxy S10e Questions & Answers] 4b4ddon:
When I heard that the Android 11 version for the Galaxy S10 was available, I was anxious and found a way to download the update through the Frija program. But the Instagram option just disappeared. Does anyone know what may have happened? This absence is directly reflecting on Instagram!
[Samsung Galaxy S10e Questions & Answers] okij:
Just as a guess: Maybe Instagram is not compatible to Samsung's Android 11 / OneUI 3 camera app yet?

I don't have Instagram on my S10e (still running on Android 11) and I don't have an Instagram option in Camera app either. So it might be part of the Instagram app.
[Samsung Galaxy S10e Questions & Answers] navcar:
Found an official statement from Samsung - sadly it's been removed in Android 11 :(

Help&Contact Us | Samsung Gulf

Help&Contact Us

www.samsung.com
[Samsung Galaxy S10e Questions & Answers] CurlyBlonde:
What did the instagram mode do ? Take pics and upload them directly to insta ?
[Samsung Galaxy S10e Questions & Answers] Cryptomaniac13:
I didn't quite understand the problem either.
[Samsung Galaxy S10e Questions & Answers] tshelb:
I get it, this sounds tricky. The Android 11 update or how you got it might have messed with your apps, like Instagram. Have you checked app settings or updated Instagram from the app store? Updates can sometimes cause problems. If it keeps going wrong, maybe ask Samsung support for help. Hope it gets fixed soon!
[Google Pixel 5 Guides, News, & Discussion] Az Biker:
Why This Thread?

I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for anyone who might still be uncertain about "update" procedures, I've followed thie below method twice now with no issues at all,> None of my data was lost and I kept my EX kernel!.

If You Want To Unlock Your Bootloader and Root Your Pixel 5:

This guide takes you step by step through bootloader unlock, using magic to patch the boot image and get your device rooted.

If You're Already Unlocked & Rooted, and Want To Update The Factory Image And Re-Root:

If you're already rooted and want to update to the next factory image, just follow the standard update factory image routine for the Pixel series of devices, then following the below:

After extracting the primary factory zip, and the secondary zip that is created from the first extraction (all done within the platform tools folder with the fastboot app)

Edit the FLASH-ALL file.... keep the -w for a clean install that wipes everything, or remove the -w to keep your data.

This will install the latest factory image and remove root.

Now, follow these steps here, they're perfect. (

these are the same instructions for unlocking bootloader, and initial install of Magisk listed above

)

If you were previously rooted, and just updating the next factory image, you can skip the entire sections on installing and hiding Magisk manager in the above instructions, (these settings remained in Magisk Manager when I did this).

And you're done!

KNOWN ISSUE:

* * * MagiskHide Props Config IS NO LONGER WORKING * * *

Please follow THIS LINK for the Universal Safetynet Fix that replaces the MagiskHide Props Config process.

If you know an easier, shorter, more efficient, or UPDATED method, please share it and I'll make the necessary corrections/adjustments (y)
[Google Pixel 5 Guides, News, & Discussion] l7777:
My method is updating via the OTA packages. Similar to using the factory image but no editing of files.

Download the factory image for your current software version.

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

developers.google.com

Extract the boot.img from #1

Download the factory image of the version you're updating to.

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

developers.google.com

Download the OTA image for the version you're updating to.

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Turn off magisk modules

Apply the boot.img from step #2 (I save this from my previous update so I can skip steps 1 & 2 above.)

adb reboot bootloader

fastboot flash boot "path to boot.img"

fastboot reboot (this is a sanity check to make sure things are normal. The phone should be normal and without root. It can be skipped if you wish, simply use the fastboot menu on the phone and boot to recovery skipping steps 4 & 5.)

Sanity check phone

adb reboot recovery

Once in recovery hold the power button and click volume up

Use the volume keys to highlight "Apply update from ADB"

Click the power button.

On your computer run: adb sideload "path to #4" and wait for it to finish. You'll get status on the adb command and on the phone.

Once finished restart the phone and let it finish the update.

Your phone is now updated but without root.

Extract boot.img from #3 above.

Copy it to the phone

Open magisk manager and patch the boot.img you just copied

Copy the patched boot.img file created by magisk manager back to your computer

Apply this file using fastboot

adb reboot bootloader

fastboot flash boot "path to patched boot.img"

fastboot reboot

Turn on your magisk modules and test

You can now delete 1, 3, & 4. I save #12 for the next update. This eliminates the need for 1 & 2.

You should now have an updated rooted device.
[Google Pixel 5 Guides, News, & Discussion] zeepzorp:
Thank you. Well-written, just a few minor corrections.

Download the factory image for your current software version.

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

developers.google.com

Extract the boot.img from #1

Download the factory image of the version you're updating to.

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

developers.google.com

Download the OTA image for the version you're updating to.

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Apply the boot.img from step #2 (I save this from my previous update so I can skip steps 1 & 2 above.)

adb reboot bootloader

fastboot flash boot "path to boot.img"

fastboot reboot (this is a sanity check to make sure things are normal. The phone should be normal and without root. It can be skipped if you wish, simply use the fastboot menu on the phone and boot to recovery skipping steps 4 & 5.)

Sanity check phone

adb reboot recovery

Once in recovery hold the power button and click volume up

Use the volume keys to highlight "Apply update from ADB"

Click the power button.

On your computer run: adb sideload "path to #4" and wait for it to finish. You'll get status on the adb command and on the phone.

Once finished restart the phone and let it finish the update.

Your phone is now updated but without root.

Extract boot.img from #2 above.

Copy it to the phone

Open magisk manager and patch the boot.img you just copied

Copy the patched boot.img file created by magisk manager back to your computer

Apply this file using fastboot

adb reboot bootloader

fastboot flash boot "path to patched boot.img"

fastboot reboot

You can now delete 1, 3, & 4. I save #12 for the next update. This eliminates the need for 1 & 2.

You should now have an updated rooted device.
[Google Pixel 5 Guides, News, & Discussion] l7777:
Thanks, updated the original.
[Google Pixel 5 Guides, News, & Discussion] hamooz92:
Thanks for the instructions. I was able to re-root the device, but I couldn't pass SafetyNet Attestation.

My P5 has updated to: 11.0.0 (RQ1A.210105.003, Jan 2021)

I used MagiskHide Props Config (updated) method. which is:

#su

#props

#1 (edit device fingerprint)

#f (Pick a certified finger print)

#7 (google)

#20 (pixel 3a)

#3 (Android version 11)

#y (restart)

The devices rebooted but still, no SafetyNet pass.
[Google Pixel 5 Guides, News, & Discussion] l7777:
Altering the model prop doesn't work for safety net any longer. There is a safetynet-fix magisk module you can use.
[Google Pixel 5 Guides, News, & Discussion] Az Biker:
I just flashed the safety net fix myself and it worked like a charm.

I also left the magisk config prop module installed (just because)

Are all your other Magisk settings in order (magisk hide, checking all the boxes under GooglePlay , etc.)?
[Google Pixel 5 Guides, News, & Discussion] narf0815:
current build number is RD1A.200810.021.A1

one the ota site there's only one "EU carrier" images different than the current one: RD1A.201105.003.B1 (NOV 2020). should i use this one or can i also use the this one f.e. RQ2A.210305.006 (nothing specified):unsure:
[Google Pixel 5 Guides, News, & Discussion] tlxxxsracer:
You may find my video helpfu too but it more pertains to installing the DP1 for Android 12, but the update process is practically the same.. For rooting Android 12, it seems we need to disable verity/verification of boot images, otherwise flashing a modified boot img will just boot immediately to fastboot again.
[Google Pixel 5 Guides, News, & Discussion] l7777:
In your case yes I'd probably use RQ2A.210305.006.
[Google Pixel 5 Guides, News, & Discussion] dhrv:
Thank you, l7777 and zeepzorp. This is also the way I would have done it. Out of curiosity and to reduce manual steps in between, would it work to restore the original boot.img to unroot and then use the normal OTA updates inside Android? Without a spare phone or a TWRP backup I hesitate to try this.

Also, when following the manual update steps, is it safe to skip versions in between, e.g. update directly from January to March versions? In my past 10 years of manually updating ROMs I have never used any OTA update functionality from inside Android and I noticed that the OTA update process, which was performed in mid January 2021 when unpacking the phone, updated the ROM in the following order, each separated by reboots in between:

Shipped version: 11.0.0 (RD1A.200810.021.A1, Oct 2020, EU carriers)

1st OTA update: 11.0.0 (RQ1A.201205.011, Dec 2020, All carriers except AT&T and Verizon)

2nd OTA update and at that time current version: 11.0.0 (RQ1A.210105.003, Jan 2021)

Why did it not skip the version in between and directly update to the January version?
[Google Pixel 5 Guides, News, & Discussion] Az Biker:
As far as skipping monthly updates, I only update every other month (unless there's a massive update for security) and I've had zero issues. Just updated to March from January, no problems.
[Google Pixel 5 Guides, News, & Discussion] philharmon:
I'm having a hard time understanding your instructions. I apologize in advance but, could I get a more detailed list of instructions?
[Google Pixel 5 Guides, News, & Discussion] Az Biker:
Follow these instructions, they're pretty much step for step.

https://android.gadgethacks.com/how...ide-for-beginners-intermediate-users-0348101/

They're included in my OP (hyperlinked) as well.

If you have a specific question, just ask!
[Google Pixel 5 Guides, News, & Discussion] l7777:
Be warned, nothing after step 20 in that guide is valid any longer. Passing safetynet requires a different magisk module.

GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com
[Google Pixel 5 Guides, News, & Discussion] Az Biker:
Which is why the following warning has been written in the OP since Feb 2021:

KNOWN ISSUE:

* * * MagiskHide Props Config IS NO LONGER WORKING * * *

Please follow THIS LINK for the Universal Safetynet Fix that replaces the MagiskHide Props Config process.
[Google Pixel 5 Guides, News, & Discussion] biTToe:
Has anyone tried the Pixel update and software repair tool

Google Pixel - Update and Software Repair

to go from Android 10 to 11?

Then modify the boot image with Magisk and fastbooting that?

ƒ
[Google Pixel 5 Guides, News, & Discussion] l7777:
That assumes that people read the OP. :eek:

It will almost certainly perform a factory reset in the process.
[Google Pixel 5 Guides, News, & Discussion] madmack:
Just sharing how I do it in case someone is interested in a shorter path:

1. Download the new full factory image

2. Extract the file. Then extract boot.img from the image zip file within.

3. Copy boot.img to your pixel 5

4. Patch it with magisk

5. Move back the patched file, rename it to boot.img

6. Update the original zip file titled image-redfin-r*.zip with the new boot.img file (override the older one)

7. Edit flash-all file by removing -w so it won't wipe your device clean

8. Flash with flash-all

No need to unroot and reroot.
[Google Pixel 5 Guides, News, & Discussion] donlu30:
So no need to disable modules or anything?
[Google Pixel 5 Guides, News, & Discussion] andybones:
I always do, and would suggest it, as a Module could very easily be incompatible with the new update. What has worked for me since I've owned the device since release is this:

1) disable all modules (remove them if you want, but I just disable)

reboot

1a) un-hide Magisk if you hide it

2) download the latest factory image

2a) extract and remove the -w from flash-all as to not lose anything

2b) while I'm doing this, I pull the boot.img and put onto my Internal storage sdcard

2c) (optional) backup your internal storage, just incase

3) adb reboot bootloader

4) flash the factory image

5) reboot

6) patch the boot.img from 2b

7) adb reboot bootloader

8) fastboot flash boot magisk_patched_boot.img

9) re-enable the magisk modules 1 at a time

9a) go to the XDA threads of certain modules known to cause issues with updates, and make sure it's compatible BEFORE re-enabling that module

10) done
[Google Pixel 5 Guides, News, & Discussion] madmack:
Never did and my modules always work when I reboot into the new rooted firmware.
[Google Pixel 5 Guides, News, & Discussion] donlu30:
So I flashed the update and no problems, but flashing the patched boot I get "failed to write to partition not found". Any suggestions?

So I flashed the update and no problems, but flashing the patched boot I get "failed to write to partition not found". Any suggestions?
[Google Pixel 5 Guides, News, & Discussion] andybones:
It's not a very good suggestion for others to do this, because everyone uses different Modules.

Many Modules need to be updated for each OTA, or at the least, check the files against the new OTA files, and see if the Module needs anything updated within.

Such as these 2 Modules I use:

https://xdaforums.com/t/august-5-2021-pixel-tweaks-for-pixel-5-with-color-picker.4184067/

https://xdaforums.com/t/mod-magisk-...res-for-pixel-devices-pixel-5-thread.4246253/

Others may be at a risk of bootloop from this suggestion.

Simply disabling the module takes no more than a toggle off and a reboot, and can save a lot of headache. And they will be at risk of bootloop once on the new OTA and re-enabling the module. Which is why I suggested in my previous post to also enable them 1 at a time, and to better yet, check the XDA thread before hand, especially for known at risk modules such as the ones I linked above.

Umm. Off the top of my head would be something wrong with the patched boot.img (maybe it didn't transfer fully?)

or out-of-date fastboot drivers installed.
[Google Pixel 5 Guides, News, & Discussion] andybones:
Hey guys,

Sorry, update on this,

And someone please correct me if I am wrong.

EDIT: disabling the modules is suggested

Disabling the Magisk modules I suppose is more apart of my OCD,

thinking on it again,

I don't believe it to be necessary,

as once the new factory image is flashed,

it flashes the stock boot.img,

which will un-root you,

thus making step 1) disabling all modules, not needed.
[Google Pixel 5 Guides, News, & Discussion] donlu30:
So I would say correct, but to an extent. Modules related to themes have given me trouble. Caused me to wipe the other day... But you won't have an issue until you flash the patched boot.
[Google Pixel 5 Guides, News, & Discussion] andybones:
Hey sorry, I think I may be mis-understanding.

So, this is in relation to taking the OTA, and the steps I initially outlined?

If I am reading this correctly, and I may not be.

A Magisk Module with theming components, such as something like this:

https://xdaforums.com/t/august-5-2021-pixel-tweaks-for-pixel-5-with-color-picker.4184067/

which modified the SystemUIGoogle (Statusbar) and NexusLauncherRelease (Pixel Launcher) .apks --

caused you to have to wipe your device the other day?

Because you didn't disable the Magisk Module with theme before flashing the Factory image?'

I'm having a hard time understanding why this would have caused the need to wipe.

Unless you mean, you flashed the Factory image, then re-enabled the Magisk module 1 by 1 and had an issue.

That would make more sense to me.

And until you flashed the patched boot.img you are not rooted.

As for theme, I mentioned in this post

https://xdaforums.com/t/updating-pixel-5-factory-image-re-rooting.4215295/post-85434681

"9a) go to the XDA threads of certain modules known to cause issues with updates, and make sure it's compatible BEFORE re-enabling that module".