yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] V0latyle:
Make sure you're not confusing image-device-buildnumber.zip with boot.img that's inside it. The "image-device-buildnumber.zip" is the system update; boot.img is the boot image. I hope that helps clarify things.

I don't provide support for any other software, so I can't speak to the proper use of a flasher tool. I prefer to do everything myself, without using any scripts or third party software. In that regard, this is exactly how I performed the December update:

Update Magisk app to 23016; after app is updated, update the boot image patch, then reboot

Download and extract the factory image; extract boot.img from the image-device-buildnumber.zip

Patch the boot image in Magisk; copy magisk_patched-23016_xxxxx.img back to PC

Reboot device to bootloader

Update bootloader + radio; reboot to bootloader

Install the update:

fastboot update --skip-reboot <drag and drop the image-device-buildnumber.zip here>

After update completes, reboot to bootloader

Flash the patched boot image:

fastboot flash boot <drag and drop patched boot image here>

Reboot to rooted system.
[Google Pixel 6] acefan:
Thanks for your reply!

I think I'm effectively now at point 6 in your list (magisk is 23016, bootloader and radio are updated, new image-device-buildnumber.zip is flashed).

Currently the phone is running the december release but without root.

If I now create a new Magisk patched boot image, will this work to gain root again (without data wipe)?
[Google Pixel 6] t-ryder:
Just patch the Dec. '21 boot image with latest Magisk canary and fastboot flash it manually.
[Google Pixel 6] acefan:
Thanks, it worked (without the need to wipe data). :)
[Google Pixel 6] t-ryder:
EDIT: it was my f* USB port.
[Google Pixel 6] bush911:
Thanks very much for your guide. I am currently using Pixel 3 and going to upgrade to Pixel 6.

What I was wondering is

1. whether I can still update factory image by "flash-all" after deleting "-w" to keep data then patch boot.img.

I always did this for nexus 5, pixel 1 & 3, to keep bootloader and radio is most updated, for me updating them one by one feels bad.

2. For me, lsposed and hide root is a must, pass SafeNet is not. But nowadays things are getting more and more complicated. By now, we don't have a stable Magisk build, hide root feature was removed, zygisk was introduced. There are so many terms I can hardly follow. what is the simplest way to keep both Lspose and hide root? Using Riru modue lsposed or waiting for workable zygisk-lsposed?, there is still an unoffical magisk alfa development is on going.

Thank you very much in advance for your comment, really appericated it.
[Google Pixel 6] rbouza1:
Use the Android flash tool and get the build you want.
[Google Pixel 6] V0latyle:
Yes

I have no experience with Lsposed, I can't really answer that question. SafetyNet passes and GPay is working on my Pixel 5 using Magisk 23016 + Universal Safety Net Fix 2.2.0 + MagiskHide Props Config 6.1.2.

Sharing useful information is what makes XDA a great place.
[Google Pixel 6] t-ryder:
Now this is bananas. I forgot that I did some fixes on the wall in my flat and did unplug all cables on my PC for moving it. I plugged the cable in another USB port I guess after the work. When the error occured I tried all remaining ports on the back of the PC. ADB was working, fastboot was working as it should - but not that one specific part of the flashing process. I then used my front USB port and was able to flash with the flash-all.bat from the factory image package. I knew that USB-controllers can be a pain in the a** when flashing images or doing ADB stuff. But this... I mean really all was working, but not flashing that partition.

This hustle gave me a full wipe, but I had a 3 day old backup of all my stuff. Don't forget your backups!

I'm glad I don't have to RMA the device. I first thought storage is damaged or something.
[Google Pixel 6] t-ryder:
Sorry for the trouble. I updated the 0riole-Flasher thanks to this feedback. v3 now checks if all needed files are there. If a file is missing it can be added and the flasher can be started again. For the platform-tools cleanup after the flash I added a choice with confirmation for deletion of the image files.

Newer versions of 0riole-Flasher will be released at my Github page. You can find v3 there.
[Google Pixel 6] acefan:
Sorry to hear that, but at least you had that backup ready.

What kind of backup solution did you use?

I find it kind of cumbersome to create/restore a backup. Although Swift / Titanium Backup can help with all the apps, for me the recreation of the system settings and individual adjustment takes the longest part.

There still isn't a TWRP-like solution available, is there?

That's awesome news, good to see that my feedback could help. Thanks for providing the adapted version so fast. :)
[Google Pixel 6] t-ryder:
I got a full local storage backup and a full swift backup plus a vcf file for my contacts (not using any sync or cloud service for data or files in any way). Going from full wipe to daily driver again takes me like 2 hours (adding the backup and doing all app and system settings). Even though swift backup does a lot of the work, I always have to wipe data of my banking and credit card apps (and the german covid vaxx certificate app) and set them up again.
[Google Pixel 6] Galaxea:
Am I the only one getting this virus warning when extracting this tool?
[Google Pixel 6] V0latyle:
Might be false; his source code is available, it's always wise to look at the source before using third party software
[Google Pixel 6] Galaxea:
The tool stops here for me: The phone stays in Fastboot Mode

Edit: Trying another PC where I know that ADB works correctly.....
[Google Pixel 6] t-ryder:
If you would have read the included info file, you would know it's a false positive. 22 of the 60 most common antivirus software give a false positive for my flasher, since it's a compiled batch script. The source is available at GitHub.
[Google Pixel 6] t-ryder:
Make sure ADB is enabled, permitted for your PC, drivers are OK, got a proper cable, your USB controller/port does not mess up things etc.
[Google Pixel 6] Galaxea:
All good. USB drivers were not working. Worked like a charm. Thanks for the tool.
[Google Pixel 6] marvi0:
Hi guys have followed the guide for gpay to work on my rooted p6 but it's still failing. Is there anything else I should do to get gpay to run please?
[Google Pixel 6] V0latyle:
Universal Safetynet Fix 2.2.0 + MagiskHide Props Config 6.1.2 works for me...on my P5.

You may have to enable DenyList on Play Store.
[Google Pixel 6] rippedwarrior:
Make sure to clear the GPay app storage/cache after installing the Magisk mods.
[Google Pixel 6] LLStarks:
Are we supposed to use the "Patch vbmeta in boot image" option for Magisk Alpha?

Initial root? Every time? Never?
[Google Pixel 6] Strephon Alkhalikoi:
The OP should feel free to correct me on this if wrong, but my answer is "never". I didn't use that option making my initial boot image (November), and didn't use it just now when I updated to the December image while keeping the November radio in place. Yet the unit works perfectly.
[Google Pixel 6] khatidaal:
Hey, I'm at step 8 on the Initial Root spoiler and I'm getting the following error message in PowerShell:

PS C:\platform-tools> fastboot flash boot C:\platform-tools\magisk_patched-23016_JSvuM.img
target reported max download size of 261095424 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.480s]
writing 'boot'...
FAILED (remote: partition (boot) not found)
finished. total time: 1.496s

I've checked the following:

Platform-tools are updated

Correct build number across device and factory image

Not sure how to proceed from here..
[Google Pixel 6] V0latyle:
I use command line, not PowerShell. I don't know if that would make any difference; seeing that fastboot is responding with status messages, I wouldn't think so.

Make sure that you are indeed using Platform Tools 31.0.3 and you don't have any duplicate folders from older versions. Delete the platform-tools folder, re-download Platform Tools 31.0.3, extract, and use Shift+right click to open command line/PowerShell window in that specific folder.
[Google Pixel 6] khatidaal:
Thank you, I'll try this again and follow up
[Google Pixel 6] khatidaal:
Ok so I redownloaded PT from the link you provided and redid the steps but same error. However, when you mentioned that you use CMD, I tried the same and it worked with Command Prompt running as administrator.

For anyone that has the same issue, here are the steps to get around this error using WIndows 10 (should work for any version though):

Launch Command Prompt as administrator

Change your where your Command Prompt window is working from to your Platform Tools folder:

I saved my PT folder under C:\platform-tools, in that case you would type 'cd C:\platform-tools'

Rename your patched boot.img to 'master_image.img'

Use the same command in step 8, 'fastboot flash boot master_image.img'

That's what worked for me for the FAILED (remote: partition (boot) not found) error message using Windows 10 on Powershell.

Thank you so much for your help @V0latyle
[Google Pixel 6] V0latyle:
There is an easy registry tweak to enable Command Prompt in the context menu with Shift+Right click in any directory.

HKEY_CLASSES_ROOT\DIrectory\Background\Shell\cmd, go into permissions, change owner to yourself, then change "HideBasedOnVelocityID" to "ShowBasedOnVelocityID".

Here is the guide for anyone who is interested.

@khatidaal thanks for discovering this, I will update my notes.
[Google Pixel 6 Pro] Ghisy:
Hi,

Any developers around here working on custom kernels already?

It would be nice if @flar2 and @Freak07 would work on our Pixel 6 Pro!

Kernel source code is available from Google: https://android.googlesource.com/device/google/raviole-kernel/

Let the games begin! 😁
[Google Pixel 6 Pro] DespairFactor:
I have some stuff started, just wrapping my head around the GKI and modules
[Google Pixel 6 Pro] Ghisy:
@DespairFactor, sweet! I'm mostly interested in using color control with the ElementalX app first.
[Google Pixel 6 Pro] Burt Squirtz:
True words have never been spoken. The hue white point of this device is this weird yellowish tint. KCAL is an absolute must to get the screen to look nice and coolish blue tint like other devices.
[Google Pixel 6 Pro] Ghisy:
Is it? Ugh, I haven't really used the device yet. I like my screens with a coolish blue tint too.
[Google Pixel 6 Pro] Israafil:
Most of the developers probably cant get a pixel 6 currently haha
[Google Pixel 6 Pro] intp.pisces:
I'd lend one mines. 7T is operating perfectly and I can't port my number for another ENTIRE MONTH 🥲
[Google Pixel 6 Pro] darbylonia:
Yes - 100%!!!!!!!!! I have very specific red / green / blue settings that I have to have!!:LOL:
[Google Pixel 6 Pro] Nekromantik:
flar2 has set up a pixel 6 repo so looks like he working on it
[Google Pixel 6 Pro] gokart2:
Same here. Tad bit different. Would like to figure out how to decompile the modules. For curiosity sake... 😂. Been awhile since I compiled anything.
[Google Pixel 6 Pro] DespairFactor:
don't see any reason why you'd do this, the source is readily available
[Google Pixel 6 Pro] ZeNiXxX:
Nice can u show me the repos?
[Google Pixel 6 Pro] Nekromantik:
It's empty.
[Google Pixel 6 Pro] Nekromantik:
Nice.

Not tired you're kernel before. Will give it a go
[Google Pixel 6 Pro] gokart2:
I thought the modules source wasn't available.... Again it's been awhile and it's slightly different than before. Just sync'd the repo at this point, so I haven't really looked hard yet.
[Google Pixel 6 Pro] DespairFactor:
Here you go

kernel/google-modules/ - Git at Google
[Google Pixel 6 Pro] gokart2:
@DespairFactor

I meant these .ko files. Thought these were the vendor specific modules that get loaded separately from the GKI? Honestly I haven't a clue. I at least got it compiling, so its a start. I do this as a challenge/to keep myself busy. Learn as I go.

refs/heads/android12-d1-s5-release - device/google/raviole-kernel - Git at Google
[Google Pixel 6 Pro] DespairFactor:
Some are in the kernel source too
[Google Pixel 6 Pro] gokart2:
@DespairFactor

Have you compiled yet? What's the difference between the vendor_boot.img and the boot.img that gets outputted? The checksums are different, but the filesize is the same? Haven't unpacked them to see if I can tell the difference yet.
[Google Pixel 6 Pro] DespairFactor:
I believe this is the vendor modules. Did you compile manually or using google's script? Feel free to reach out to me directly on telegram. I have a link in my sig that opens a chat with me.
[Google Pixel 6 Pro] gokart2:
Makes sense. Just thought it was really weird both images were the exact same size but different checksum. I used Google's script just to verify I could get it to compile. However I do need to mirror it to the factory image as that is about 13mb bigger. Haven't tried booting it yet, assuming there's an issue with missing that much. Thanks for your time and help. I will likely hit you up on telegram in the future.
[Google Pixel 6 Pro] DespairFactor:
I have a build I made booted on my device right now actually. I am working on getting the mainline branch booting on my device.
[Google Pixel 6 Pro] rav101:
Getting mainline Linux booted would be awesome. Been hoping for that for years and each year it feels like a closer and closer possibility!
[FYT Android Head Units] Icefeldt:
After owning multiple rockchip devices (last a PX5 headunit), I'm now in theprocess of buying a new radio.

Initially I wanted to go for a MTCD radio with a PX6 cpu and 4GB of ram, but now also found the FYT devices with UIS7862, 6GB RAM and 128GB ROM.

(Mekede M600s)

And as "more RAM" is always very helpful with Android devices in the long term, I'm interested.

I saw that the community and ROM developement is not as big as for the MTCD devices, but I do not need to have that, if the devices itself are stable/good.

So I wanted to ask you guys, if you are satisfied with your decision and if you would buy it again?

Anything I need to know, coming from a MTCD device?

My main usage would be: Google Maps, Spotify, Bluetooth Connection to my phone for calls, Youtube, so nothing to fancy.
[FYT Android Head Units] marchnz:
Yes. I've written about this a bunch. Look for my posts

You really don't need a modified "hal/mal" ROM with FYT.

Buggy MTCD is dead, long live MTCD :)
[FYT Android Head Units] ludditefornow:
Very happy with my Navifly 7862 4gb. GPS is terrific and can't recall an unexpected reboot. Radio app is a bit naff but bang for buck, I would do it again in a heartbeat.

Bluetooth to phone is seamless and hotspot from phone via macro works like a charm.

If you are the sort of person who looks to find fault, you probably won't be happy. If you just want a system that works for the most part and you know the interface limitations, you will be fine.
[FYT Android Head Units] Bob_Sanders:
I've been kind of keeping my eye on this too, but so far (to me anyway) it looks like

"same sh*t, different pile".

Meanwhile I was pleasantly surprised in my shift from px5 to px6. Px6 seems to be a fairly large upgrade as compared to px5.... runs smoother with a lot fewer bugs. Bluetooth is still a problem when trying to connect devices other than phone though

For me, I have a lot of gadgets connected to my system (tv, front cam, rear cam, dash cam, siriusXM tuner, OBD bluetooth adapter, OBD USB adapter...etc), and I find FYT is more restrictive and locked up when it comes to connecting all these peripherals. That was the make/break for me and is what made me decide to stick with mtcd
[FYT Android Head Units] marchnz:
I respectfully disagree. Ex. MTCD hardware developer here.

Context is everything.

What FYT processor/MCU did you compare.

I have the opposite experience and find my 7862UIS/MCU 53 = YIN far superior and without any of the issues you mention.

On my FYT platform, it is FAR less restrictive. The bonus is the processor is superior and has 4g built in!

Then there is the audio quality, my FYT is simply amazing.

Back to MTCx, isn't it the reason so many mods / modded ROMs exist - again with their horrible problems and daily reports of issues - for the MTCx platform, to fix bugs and get around restrictions. But don't take my work for it, read the MTCD forums and compare.
[FYT Android Head Units] Bob_Sanders:
Yeah, Thanks.

I read your other thread on your switch-over from mtcd with great interest. The problem I'm having is that you jumped ship at the PX5 level. I on the other hand went on to px6 from the px5, and there is no comparison between the two (both were Dasaita). The px6 is light-years ahead of the px5 both in terms of speed and stability. I used to have to do full reboots on the PX5 pretty much weekly to clear up the bugs. With the PX6 I have had to reboot maybe twice in the last 6 months.

I think to sum it up best, comparing the px5 to the px6 is about the same as comparing a 1960's black and white tv to a 60 inch lcd tv of today.

And with Dasaita in particular, the choice of input/output ability simply can not be beat. I have not seen another head unit which supplies the number of input/output jacks and plugs that Dasiata does.

Dedicated inputs for tpms, dash cam, front cam, and TV so I don't have to use up my USB slots. It also has dual subwoofer outputs so I don't have to weaken the signal with a Y splitter for my dual amps.

Now that being said, the new FYT machines do seem to have a slightly brighter screen which is always welcomed, and some also have digital audio outputs but that's not really something I would ever use.
[FYT Android Head Units] marchnz:
Youll find exactly the same input wise and more on the FYT platform.
[FYT Android Head Units] Bob_Sanders:
Not on Joying or navifly. I looked. Maybe I'm missing these inputs?

Here's Dasaita..... a second DEDICATED plug set for

DVR (C)

TV (E)

TPMS (H)

Dual sub outputs (A)

View attachment 5452281
[FYT Android Head Units] marchnz:
Look a little more on the latest FYT platform models.

All of these inputs are present or catered for with USB or AUX inputs, TPMS is USB for instance.

Also, FYT feature an optical out, which MTCx does not have.

You still haven't said what FYT you owned, context/specifics is really important.

The point is, the newer FYT units blow the MTCx units away in nearly every aspect, especially sound, while providing for the same features and more than the MTCx platform.
[FYT Android Head Units] Bob_Sanders:
Well... that's exactly what I am saying. Because of the dedicated inputs I don't have to use up my USB inputs, or my AUX inputs. I can use those for other things (which I do). Also, the supplied software is completely built around those inputs. The software knows exactly where to go. The TV module for example is automatically turned on/off, and tuned up when I bring up the TV app. It all operates in one smooth motion. The FYT units are just plain lacking in this respect.

As for the digital outputs... if you are going to go digital you need high quality dacs... and I wouldn't exactly call the electronics inside these machines... "high quality"

I haven't owned one.... but that's my point with your argument... you haven't owned a PX6. You are comparing PX5 technology to the FYT. A cardboard box probably has higher quality and better sound than the PX5.

I have looked at FYT and the lack of input/output ability is the dealbreaker for me. To me these things aren't just Head units. They are central control centers... or at least that's what I bank on them for. If I was looking for a typical head unit I would go with Pioneer or Kenwood.
[FYT Android Head Units] marchnz:
I think I was highly skeptical like you initially, the chinese origin headunits appear to be largely copies and reuse, with little improvements between generations. I was surprised at just how good, at least my unit is.

Disappointing you couldn't find an FYT unit that meets your needs, they really are great.

At least the FYT unit I have, which is an YIN 53 / Mekede has inputs you mention. It's also listed on the schematic diagram obtained from 4pda.

Regarding the optical output, consider optical provides a multichannel noise immune method to connect a power amp via a single "cable."

Don't forget the MCUs on the MTCx platform are the same between processors, also bugs are widely reported in the MTCD forums, including PX6.

Maybe we agree to disagree.
[FYT Android Head Units] Bob_Sanders:
Disappointing to this point anyway.... they'll probably come around though in time.
[FYT Android Head Units] dbmgreen:
I have owned several Joying units over the last 5 years or so, with generally good experiences. Last July/Aug I installed an SC 9853i in my Kluger/Highlander.

Recently a couple of things have gone pear shaped.

1) The google play store needs "uninstall updates" to function (had this with the older devices as well)

2) Waze and google maps are "freezing" sometimes very quickly sometimes after an hour.

3) The built in 4G has disappeared and I now only get 3G/H+ (this is subsequent a firmware update, which installed older modem firmware)

I have been unable to resolve these issues with Joying unfortunately.

They (Joying) were very good in the past sending me a new unit when the screen got a white ring around it, but really have had no luck with them resolving these issues.

I would probably buy a new device off them, but not the same device, the only problem is their website doesn't really have detailed enough information to make an assessment/comparison of the underlying hardware in each of their different models.
[FYT Android Head Units] marchnz:
Found yet another reason to buy an FYT 7862UIS unit - Bluetooth Low Energy support.

My unit seamlessly connects to my Valentine One gen 2 radar locator. Every time. No hiccups, or pairing required.
[FYT Android Head Units] forgivegod:
Sorry for going slightly off thread topic...

Did you try a reset? and then a firmware reload/update?

I had your first problem until I wiped the system and flashed the latest firmware (which was the same)

The apps freezing might indicate a temperature issue. See if it runs warm/hot?

I never used the 3g 4g module since I hotspot.
[FYT Android Head Units] forgivegod:
Yea. I'm on my 2nd joying for my 2010 Rav4. I highly recommend getting one with buttons/knobs. Its very annoying to change volume by screen touching (even if you have steering controls). It seems the devices go thru these rounds of improvement that go like

Version 1 : great new screen, no buttons, no knobs

Version 2 : same new screen, touch buttons

Version 3 : same new screen, knobs and actual buttons

My only gripe is lack of customization of radio app, and the icons on the launcher have stupid large borders (wish the app icon was simply displayed)

I think they are coming out with a whole new ui
[FYT Android Head Units] dbmgreen:
Nah all good, have reset a number of times, and reloaded every version of firmware available to me. I only got the device in 2020 AUG, I feel like it may have had slightly different firmware on it (to what is available for download) based on the screenshots I sent to Joying when I was initially trying to troubleshoot. Yes even wiped completely twip_all.

I think its is running hot 70-90 degrees but this is a recent problem, it ran fine for 12 months.

We use (did use) 4G module for a hotspot in the car for all the passengers, it had worked seamlessly up until joying sent me their firmware :(

I wish I could identify what model they are selling for the 2018 Highlander, I would just buy a new one. I do like their product, and I'm currently 1 of three dodgy products with no resolution :) --- Chinese vendors
[FYT Android Head Units] dbmgreen:
What "brand" are you looking at :)
[FYT Android Head Units] marchnz:
ro.build.fytmanufacturer=116

MCU = NOR

Seller was Mekede. There is no "brand" on Android head units, only factory. You would be taking a gamble buying from any seller without asking for screenshots of the system info, they might ship a unit from any number of factories and therefore variants.