yashsingh1/xdaforums huggingface dataset:
[Android Stick & Console AMLogic based Computers] HungryChimp:
How to become a donated member sir?
[Android Stick & Console AMLogic based Computers] Englishpatient76:
yes you can donate to my upi dm me for details
[Android Stick & Console AMLogic based Computers] Englishpatient76:
i dont understand the process,can you elaborate more
[Android Stick & Console AMLogic based Computers] rahimsahil:
Sir Mera matlab ye ki jab stb Naya hota hai aur wo update hota hai toh hum uska switch off karde, jab switch on karenge toh uska software remove ho jayega aur wo show karega ki app pendrive se software daliye mene esa ek bar 2021 wale box ke sath kiya tha , means box brick ho jayega
[Android Stick & Console AMLogic based Computers] soniadarsh63:
Can work on 2022 model stb

If yes pls guide proceigure
[Android Stick & Console AMLogic based Computers] nishant6577:
Sir what is the password of atv 6.0 please dm ,

Also is there any update on v3 ?
[Android Stick & Console AMLogic based Computers] Englishpatient76:
Only for donated members
[Android Stick & Console AMLogic based Computers] Culaxy-so:
Kudos to your hard work🎉
[Android Stick & Console AMLogic based Computers] Englishpatient76:
2022 models cant be unlocked as of now, just hold on for a month.
[Android Stick & Console AMLogic based Computers] avirus:
Appreciate your hard work bro..I have b200 on 7.3.7 version..will you be able to help on this? I can also experiment on this box as the bootloader is locked and also can support your development..kindly suggest
[Android Stick & Console AMLogic based Computers] Englishpatient76:
I dont have any b200 box for testing ,but will try my best ,my priority is for d200 and c200.
[Android Stick & Console AMLogic based Computers] avirus:
Bro I can try on my box anything you say, it's just that if you have time, I am ready to experiment..also bro, I will support by donating..it's just that no body touches b200
[Android Stick & Console AMLogic based Computers] Englishpatient76:
sure will keep you in loop once i start working on b200..as of now i dont have any box.
[Android Stick & Console AMLogic based Computers] Piyoosh_Singh:
Good to see you back.
[Android Stick & Console AMLogic based Computers] Englishpatient76:
no
[Android Stick & Console AMLogic based Computers] Chiro1314:
Hey, do i have to donate again here? I actually became donated member few months back? Anyway you can verify it? Or should I donate again? (Using your atv 5.0 at the moment)
[Android Stick & Console AMLogic based Computers] Englishpatient76:
contact support group for passwords
[Android Stick & Console AMLogic based Computers] S_Sabhnani:
Already donated.. at time of 5.0. can i get password??
[Android Stick & Console AMLogic based Computers] Insomniac05:
Will it be possible to include the jio universal remote setup app in these roms? The package can be extracted from jio's firmware but when trying to install on atv that doesn't happen.

Can that app be ported somehow?
[Android Stick & Console AMLogic based Computers] shbhmmry:
I have been facing an issue if anyone has any solution please help. I am using jio kodi + botallen for viewing tv channels. It has been working fine for months but now some channels like andtv and few more are throwing an error while playing other like sony channels are working fine. My os atvgold 6.1. kodi version 19.3 box JSHD200 v2.
[Android Stick & Console AMLogic based Computers] CHAPPiE18:
Since some channels are not working, maybe because of source issue.
[Android Stick & Console AMLogic based Computers] shbhmmry:
that might have been the case if it was everywhere i can run those channels via kodi in my mobile on android 12 and also on my PC windows 10 . Here is an detailed log from kodi .

And also i am able to play andtv but not andtv HD.

Start checking logs from 2022-11-02 14:19:23.025 timestamp.
[Android Stick & Console AMLogic based Computers] sahilkaul1:
Welcome back bro. Nice to see you again. May i get the change log from 5 to 6 and password for 6 to test it. I am a donor already.
[Android Stick & Console AMLogic based Computers] shbhmmry:
Issue seems to be resolved but not sure still monitoring for issues.

Followed the guide.

How to Fix One or More Items Failed to Play Kodi App Error

Users encounter "Playback failed: One or more items failed to play" error while using Kodi media player app. How to fix the streaming issue?

www.windowsdispatch.com

step - clear the cache worked

Ping me in the donor group.
[Android Stick & Console AMLogic based Computers] CHAPPiE18:
Thats nice.

Btw you tagged different person 😅
[Android Stick & Console AMLogic based Computers] Oswald Boelcke:
Moderator Announcement

Thread has been closed and download links removed.

Regards

Oswald Boelcke

Senior Moderator
[Google Pixel 7 Pro] Homeboy76:
Reserved
[Google Pixel 7 Pro] binary**#:
Double-check your root command, I guess it's wrong. Instead of fastboot flash boot init_boot magic_patched....img, it should be fastboot flash init_boot magic_patched....img
[Google Pixel 7 Pro] Kkooly:
Also for unlocking the bootloader, aren't you supposed to reboot into bootloader mode? Your instructions say "Boot fastboot mode". You can't actually run the unlock command in fastboot mode.
[Google Pixel 7 Pro] Homeboy76:
When you boot the bootloader you are in fastboot mode :)
[Google Pixel 7 Pro] Kkooly:
Oh Sorry! I thought when you ran "adb reboot fastboot" it went into fastboot mode I had to run "adb reboot bootloader". So they both are technically fastboot then? my bad!
[Google Pixel 7 Pro] Kkooly:
Thank you for this!
[Google Pixel 7 Pro] Homeboy76:
This article will help you understand bootloader mode/fastboot mode:

How to Enter Fastboot Mode on Android Devices | Bootloader Mode
[Google Pixel 7 Pro] simplepinoi177:
yeah...when I first was rooting pixel (back for my pixel 2), it was quite confusing that you would "reboot [to] bootloader" to boot into "fastboot" mode (being counter-intuitive to re"boot" into something else when trying to simultaneously "boot" the original intended o_O), and all of this is NOT done in recovery mode (which is for something completely different) like I had gotten familiar with doing for my Galaxy S5 (which is where one would do all the "rooting" commands and what-not).... pretty confusing...

that and figuring out the two different slots, active/inactive thing was most confusing!
[Google Pixel 7 Pro] few__:
ro.product.first_api_level must be 32 or less to pass safetynet
[Google Pixel 7 Pro] eragonshurtugal:
I wonder when we will have custom kernel/rom that reenables miracast
[Google Pixel 7 Pro] ihavenolifee:
Anyone with Magisk Delta currently have it working with safety net?
[Google Pixel 7 Pro] simplepinoi177:
there's a lot happening getting safety net to completely pass right now. There's a lot of "test" module fixes based off of Displax's USNF that have all had varying degrees of working -- the most established fix to be working (specifically for the P7P) is his original "test" fix; not his MOD 2.0 fix he has published right now.

In any case, you should check out the last 3-4 pages of the thread below and/or check out the OP to see directly which fix seems to work; be warned that you will not use Magisk Delta and from the OP you'll see how it's a "fluid" situation right now and there's a lot of back and forth as to what's working and what's not.

https://xdaforums.com/t/unlock-boot...net-working-again-all-relevant-links.4502805/
[Google Pixel 7 Pro] ihavenolifee:
I found this earlier and found the test module to work for now.

thanks for the reply though!
[Google Pixel 7 Pro] loonix:
Upgrading from P4XL and was looking for the standard @Homeboy76 thread and here we are ! Thanks again. Will be my bookmark for the next couple of years 👍🏼
[Google Pixel 7 Pro] madmuthertrucker:
I'm so glad to see this here. Your guides are detailed and easy to follow. Thank you.
[Google Pixel 7 Pro] Homeboy76:
"...it give me this error "FAILED (remote 'failed to flash partition (init_boot_a)')" Strange!

When I got that error it was because I patched the boot.img instead of the init_boot.img and tried to flash it with fastboot flash init_boot magisk_patched...img.
[Google Pixel 7 Pro] klark1kent:
@Homeboy76 The links under OTA images section in Prerequisites are generating downloads for an Oriole build:

"oriole-ota-tp1a.221005.002-5e69c530.zip"

That has to be a mistake right?
[Google Pixel 7 Pro] Homeboy76:
It is a mistake, thanks for the feed back. (y)

It is fixed.
[Google Pixel 7 Pro] Lughnasadh:
Nope, lol.

Really wish people who open up Github issues would provide logs, but that's a rant for another day 🙃
[Google Pixel 7 Pro] xdagee:
Anyone pass SafetyNet successfully? I have gone through the thread, but I don't see any.
[Google Pixel 7 Pro] Homeboy76:
Do OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,

5. Root/Reroot with Magisk and Pass SafetyNet.,

• Pass Safety Net with SafetyNet Fix

use

Displax's safetynet-fix v2.3.1-MOD_2.1.zip file

.
[Google Pixel 7 Pro] xdagee:
right, got to work by just flashing safetynet & clearing cache on Google Play Store.
[Google Pixel 7 Pro] innit:
I chose direct install in magisk app and now have a bootloop. Phone boots up and it looks like home screen will show up but then it reboots. Don't know what to do and don't want to lose data.

Tried flashing stock boot.img & init_boot but still not booting.

Can access bootloader but not recovery (neither from bootloader nor through adb).

Any help?
[Google Pixel 7 Pro] Homeboy76:
This is the first time I've heard of

direct installing

Magisk bootlooping/failing. Thanks for the feedback.

I hope the following fixes the bootlooping.

Do OP (Post 1), 2. Install/Update Factory Image keep data, wipe data,...

• Important Note(s):

4. If you phone bootloops

@innit, Did you flash the init_boot.img to boot slots?

fastboot flash init_boot --slot all init_boot.img
[Google Pixel 7 Pro] innit:
Already did that and it didn't work. Could I just reflash factory image with Pixel Flasher & tick "Keep data"? Would that be enough to get it to boot?
[Google Pixel 7 Pro] Homeboy76:
Deleted, see next post.
[Google Pixel 7 Pro] Homeboy76:
I thought flashing the init_boot.img to both slots was an easiest: OP (Post 186)

Maybe @badabing2003 or @Lughnasadh has a better solution to fixing Direct installing Magisk failing.
[Google Pixel 7 Pro] innit:
fastboot flash boot --slot all init_boot.img causes boot failure (in bootloader Enter reason: boot failure)

I used these commands:

fastboot flash boot boot.img --slot all

fastboot flash init_boot init_boot.img --slot all

But it just keeps bootlooping.

I can`t contact badabing2003 (user restricts who can view his profile).
[Google Pixel 7 Pro] Homeboy76:
@badabing2003 should see this.
[Google Pixel 7 Pro] badabing2003:
You can't contact me?

I don't have any restrictions, and others do manage to contact me, in any case if there is an issue with the board, use @ to mention me.

None of the commands you used are correct.

The correct way to use the flags (options) is to specify before the command.

usage: fastboot [OPTION...] COMMAND...

Example: fastboot --slot all flash init_boot init_boot.img
[Google Pixel 7 Pro] innit:
I used commands from this thread https://xdaforums.com/t/guide-root-...nlock-bootloader-pass-safetynet-more.4505353/

Will try the one you posted.

No I couldn't. When I clicked your name a warning poped up saying the user restricts who can view his profile or something similar.
[Google Pixel 7 Pro] Homeboy76:
I could be wrong, but I thought the command to flash the init_boot.img is: fastboot flash init_boot --slot all init_boot.img.

The

fastboot command structure

I used came from fastboot • man page

Am I wrong or do both commands achieve the same results?
[Google Pixel 7 Pro] Homeboy76:
Did this command work?

fastboot --slot all flash init_boot init_boot.img
[Google Pixel 7 Pro] Lughnasadh:
Both ways should work.
[Google Pixel 7 Pro] Homeboy76:
I edited my post because according to the fastboot • man page the

partition

is required.

fastboot flash init_boot --slot all init_boot.img.
[Google Pixel 7 Pro] Lughnasadh:
Yeah, I knew what you were getting at (I think, lol) so didn't mention the init_boot missing, but probably should have.

Both of theses should work:

fastboot --slot all flash init_boot init_boot.img

or

fastboot flash --slot all init_boot init_boot.img

I usually do the latter when flashing images/partitions, but it shouldn't matter either way, at least in my experience.
[Google Pixel 7 Pro] Homeboy76:
Got it, I missed the fastboot --slot all flash

init_boot

init_boot.img

:-)
[Google Pixel 7 Pro] Homeboy76:
Yeah you're right, @badabing2003 command was correct. :-)
[Google Pixel 7 Pro] innit:
It successfully flashes boot & init_boot but still bootloops.
[Google Pixel 7 Pro] Homeboy76:
Are you using SDK Platform-Tools: r33.0.3?

If no, there is a link for it in the OP, Prerequisites.
[Google Pixel 7 Pro] innit:
Yes, ver. 33.0.3-8952118
[Google Pixel 7 Pro] Homeboy76:
Nope, you didn't download that version of SDK Platform-tools from the link in the OP.

Are you using a Linux or Mac Computer to flash the img?
[Google Pixel 7 Pro] Lughnasadh:
Did you try this yet? If not, do so (or Android Flash Tool).
[Google Pixel 7 Pro] innit:
Win 10 x64
[Google Pixel 7 Pro] innit:
Just setting up Pixel Flasher now.
[Google Pixel 7 Pro] innit:
Yes I did. I literally went to Part I - 2. Prerequisites - SDK Platform-Tools: r33.0.3 (latest version from August 2022) and downloaded it from there.
[Google Pixel 7 Pro] Homeboy76:
Go to the OP, Prerequisites • A Computer with the latest SDK Platform-Tools: r33.0.3 installed.

Click SDK Platform-Tools: r33.0.3 link and download it.
[Google Pixel 7 Pro] Homeboy76:
AFAIK, none of the SDK Platform-tool downloaded from that link are ver. 33.0.3-

8952118

.
[Google Pixel 7 Pro] innit:
Just downloaded it again and the version is exactly the same. That extra number is only shown in Pixel Flasher.

Finally got it back up and running. Thanks a lot. Appreciate the patience :)
[Google Pixel 7 Pro] Homeboy76:
Ok, I was wondering where the extra number came from. :-)

You're welcome.

Thanks @Lughnasadh for your suggestion to use Pixel Flasher. :-)
[Google Pixel 7 Pro] innit:
Want to flash magisk patched image. Will this command be correct?

fastboot --slot b flash init_boot magisk_patched.img
[Google Pixel 7 Pro] Homeboy76:
You can flash Magisk in Pixel Flasher.

That should work.

Notes:

If you are, manully, flashing it and you are currently on slot b you do not need --slot b

If you are, manully, flashing it and you don't know what slot you're on use --slot all
[Google Pixel 7 Pro] innit:
The slot you want to flash doesn`t have to specified?
[Google Pixel 7 Pro] Homeboy76:
Read my <edited> post #214.
[Google Pixel 7 Pro] Lughnasadh:
You don't need to specify which slot to flash it to as it will flash to your active slot. No need to flash it to your inactive slot.
[Google Pixel 7 Pro] innit:
Thanks again guys and sorry for pestering you @Homeboy76, @Lughnasadh
[Google Pixel 7 Pro] Homeboy76:
@innit, please accept my apology for the noob/noobie comment. I just noticed you have been a XDA member since 2011.

So, you are not a noob/noobie. You, just needed help flashing the Google Pixel 7 Pro: We all need a little help at some point in time.

No apology needed. :)
[Google Pixel 7 Pro] innit:
One more question. I still have November firmware on my phone but want to update it to the newest one from January. Can I flash it to both slots or should I stick to only one?
[Google Pixel 7 Pro] badabing2003:
You can if you want to.

I alternate slots each month, but that's just me.
[Google Pixel 7 Pro] Homeboy76:
@innit, you can but, my recommendation is you

wait for the Feburary Factory image to drop

. It should drop in a few days, if not today. While you are waiting for it to drop.

If you want to flash it manually

Start by getting acquainted with the procedure to flash it to one slot by reading:

~ ~ ~ Part II - INFORMATION, 8, 4, and 5.

Then flash it to one slot.

If you want to flash it using Pixel Flasher

Start by getting acquainted with the procedure to flash it using Pixel Flasher by, throughly, reading: The Pixel Flasher OP.

Notes:

Flashing to the alternate/

other

slot each month and flashing to both slots are both good ideas.

Edit the flash-all.bat file:

Updating or Upgrading To Android 13

* * E D I T - flash-all.bat file * *

Flash to

Other/Inactive

Slot....

Flash to Inactive/Other slot: Run the

edited

flash-all.bat file.

Flash to Active-Inactive/Both slots: Run the

edited

flash-all.bat file

twice

.
[Google Pixel 7 Pro] Lughnasadh:
Just to add to what @badabing2003 and @Homeboy76 said....

If you have never flashed the firmware to your current inactive slot (i.e. you've always manually flashed to the same slot or have never taken an OTA to update), then you should probably flash to both slots or at least the inactive slot. When your phone is shipped the full firmware/OS is only installed on one slot (slot A, lets assume). Thus, if you have never flashed the firmware to slot B it will not be bootable without doing so. It's a good precaution in case slot A becomes unbootable for some reason.

(For the discussion above I'm assuming it is standard for Google to ship with the firmware/active slot only on slot A. None of my Pixels have ever come with the full firmware/OS installed on slot B to start).

The February security update should be released on February 6 (always the 1st Monday of the month unless there is a holiday, then usually the day (sometimes 2) after the holiday).
[Google Pixel 7 Pro] badabing2003:
@Lughnasadh

Although I follow that practice, I know on my newer device I won't be able to boot to the other slot no matter what.

See this, but I still do it out of habit.

If we manage to switch slots and pass AVB, then I can modify PF to flash without system_other or receover the original system after booting successfully.
[Google Pixel 7 Pro] Lughnasadh:
Right. You'd have to flash the firmware to the other slot first before being able to boot that slot, as you mentioned in an earlier, very informative post. But as I understand it, if you got into a bootloop and the device tries to revert to the inactive slot, it would be able to boot into that slot because the firmware had been previously flashed to that slot? Or is this incorrect? Seems I remember (at least I think I do in my old age, lol) some people mentioning that after a bootloop (it has to bootloop 3 times in a row to do this if I remember correctly?) the device reverted to the other slot and was able to boot into that other slot (they noticed they were on an older firmware version afterwards). Maybe when the device does this it does something (AVB related or writes the system_other image?) to make it able to boot to that other slot under these circumstances?
[Google Pixel 7 Pro] badabing2003:
Just to be clear,

Let's say I'm on A and A is bootable

I flash factory to B

B is bootable and now active.

I never tested forcing B to become unbootable and checking if the system switches to A and boots fine.

My guess is that it won't work for sure, because A's system is overwritten by that fact that I flashed to B.

So I did two different tests

1- Restore a backup of system to A, and switch slot to A (making sure that bootctl reported slot usable), A was still not bootable, the system would try 3 times and eventually mark it unbootable and revert to B

2- I deleted system_other from the factory image before flashing B, B was bootable, and I switched to A, this time A's system was untouched, so I expected it to boot, but it still failed because of AVB (on newer devices) but passed on older Pixel XL
[Google Pixel 7 Pro] innit:
@badabing2003 @Homeboy76 @Lughnasadh Thanks again for your help. Flashing to both slots with Pixel Flasher went smoothly. Normally I just do a clean install & set up everything from scratch every month but that always takes a lot of time. Now thanks to PF you only need few minutes 👍😀
[Google Pixel 7 Pro] 15xda:
I'm using the February T-mobile pixel 7 pro image, with magisk 25.2 and universal-safetynet-fix 2.4.0. What I find is that if I just reboot my phone, I pass safetynet. However, after a while I start failing again and have reboot my phone. Has anyone else seen something like this, or does anyone have suggestions? Kind of awkward because payment will suddenly stop working...
[Google Pixel 7 Pro] crypt0kiddie:
I'm having a lot of issues with Tap to Pay.

Sometimes when I open "Wallet" it says, "Device doesn't meet security requirements".

If I close wallet and try again, no message and sometimes Tap to Pay will work after that but other times even though no message, it fails to work when I try to pay.

Yesterday Tap to Pay worked fine, today its not working again.

Sometimes rebooting helps, other times not.

Did this on the December update but its WAY WORSE on February.

Somethings broken.

I need to buy a Play Store credit, cant do that either now.

*Update*

Just ran YASNAC, failed Safetynet for sure. CTS profile mismatch..
[Google Pixel 7 Pro] crypt0kiddie:
I got it working.... The trick was safetynet-fix-v2.4.0-MOD_1.1.zip

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/page-168
[Google Pixel 7 Pro] Pbsipher1:
issuing the command adb shell pm disable-user com.qualcomm.qti.uim has worked on OnePlus phones to ungrey oem toggle and root without unlock .bin or sim unlock(not 100% sure about unlock bin it's been a while since I've had a new 1+ to flash can't remember) for sure that I know of from op6 through op9 and nords could a similar one do the same for this device.
[Google Pixel 7 Pro] supermansaga:
I have a device that has passed the check w/ SEP Mobile, intune company portal, and all that, except as I signed into the Outlook / Edge under company work profile by microsoft, the sign-in process is an endless loop without success. On one screen, there is a red asterisk in front of "Device is healthy." But it won't elaborate. Instead, that screen quickly vanishes. Any clues? Thanks.
[Google Pixel 7 Pro] simplepinoi177:
It is most likely detecting root access. You most likely have to put Outlook, Edge, anything Microsoft, and maybe even some other hidden additional app/setting in the Zygisk DenyList (making sure every sub-entry is ticked in every/all applicable apps/settings) or employ Shamiko. There are other root hiding methods, but they vary with their successes and can particularly work in one way but not others. In the end, there are some apps that just are seemingly impossible to hide root from and they seem to detect even just an unlocked bootloader and will restrict itself. Thems the unfortunate reality and compromise/consequence of having root or custom beyond stock (kernel, ROM, etc.)...
[Google Pixel 7 Pro] supermansaga:
Shamiko has come to the rescue. Many thanks. My final question is now that we have rooted, is there any way to hide apps on P7P? I know the other Android phones have this innate ability, but just not P7P.
[Google Pixel 7 Pro] mcwups1:
I'm sure it's here somewhere, but when I use "search this thread" it's not specific.

I have T-Mobile (Sprint) as a carrier, but I bought the phone from Google unlocked, not T-Mobile. Do I still use the T-Mobile Factory Image, or Global?
[Google Pixel 7 Pro] Homeboy76:
T-Mobile
[Google Pixel 7 Pro] Homeboy76:
SDK Platform-tools r. 33.0.3.

https://xdaforums.com/t/pixelflashe...g-managing-pixel-phones.4415453/post-88141667
[Google Pixel 7 Pro] schmeggy929:
I use the Global version, Carrier firmware is always way behind.