Database Info

Software Development Joying Extra Tools apk - an apk to help you install mods, tweak your unit, etc.

Hi,
Below the latest versions of the "Joying Extra Tools" apk.
20 May 2020: V76
22 December 2019: V75
17 October 2019: V74
16 September 2019: V73
10 August 2019: V72
21 July 2019: V71
30 June 2019: V70
30 June 2019: V69
05 June 2019: V68
Website
Changelog: at the bottom of this post (latest release) and completely on the github website.
Credits.
Info on options (can hardly be called a manual).
Source code: Everything is in one big Appinventor/Thunkable .aia source code file.
Root your unit (Read how) with this apk and the "SuperSU Version x.y.z" from the Releases page.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It requires a rooted unit for most of the functionality. Read here.
It is created for Joying Intel Sofia 3GR FYT units, the Joying Rockchip PX5 FYT units and the Joying Intel Airmont sp9853i units . Most functionality will probably run just as well on other brand FYT units but for the time that is only functional for a few number of other FYT based units (The app tests whether it is running on a Joying or one of the other supported FYT based units like Zhan PX5, Sinosmart SC9853i and 2 "unbranded" SC9853i units).
Some functionality is the same for 5.1.1, 6.0.1, 8.0.0 and 8.1.0. The apk will detect wich Android version and on which hardware you are running and will offer the correct relevant options for your android version and unit.
It allows you to:
Enable or disable adb over WiFi
Install the Xposed framework and installer (EXPERIMENTAL on Sofia requiring Superuser rooting specifically ; stable on PX5 but requiring SuperSU "setenforce 0" rooting)
Install some specific Xposed modules not in the global Xposed repository pool.
Update busybox
Install Viper4Android on 5.1.1 ROMs (Joying/FYT blocked this on 6.0.1, 8.0.0 and 8.1.0)
Install several "main server" mods (Sofia-Server on Sofia 3GR; 100000000_com.syu.ms on PX5; 190000000_com.syu.ms on sp9853i)
Install Radio mods (examples)
Install other mods (examples)
Add mod to make it possible to put Bluetooth apk to background during call (PX5; standard on 9853i ROMs as of 12 June 2019 firmware)
(Continuously) measure temperatures of your unit
Alter the DPI of your unit
Expand the hosts file to prevent ads, banners, hijackers, etc. (see http://winhelp2002.mvps.org/hosts.htm)
Some micro apks like BTMusicStarter, WiFiOn, WiFioff to make live easier on the Joyings.
Optimization: Remove/disable non-functional system services and apps, and non-functional Joying apps
Set system wide immersive modes
You can also have a look at a really early version here on youtube.
Changelog latest version:
20 May 2020, V76
9853i: Add main server mods for 07 April 2020: Original, Original with "extended navi_app list, unkill_app.txt, player_app.txt and navi_audio_from_playstatus.txt", Nokill mod with the txt files from "extended".
Previous Changelogs:
See my website.
This apk is open source and will remain open source, but if you want you can donate something.

Been reading all the threads on the Joying as they are the only ones who make a single din with an adjustable screen as nothing else will fit...
This looks like it will help a lot
Will be ordering it over the next few days, just have to decide on which android version. Hopefully once I have one a lot of what you have all been doing will make more sense and I will pick it all up

This is awesome. You've helped alot of people with their units, thanks and keep up the good work!

THANKS!!! I will test it out. Does the enable and disable of adb also restart the server? I have had issues where ABD stops responding for no reasons.

dyabolikarl said:
THANKS!!! I will test it out. Does the enable and disable of adb also restart the server? I have had issues where ABD stops responding for no reasons.
Click to expand...
Click to collapse
Yes,it does.
The enable does
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
The disable does
Code:
setprop service.adb.tcp.port -1
# If it was set persistent, make sure to switch it off
setprop persist.adb.tcp.port -1
stop adbd
start adbd
As you can see I use "service.adb.tcp.port" instead of "persist.adb.tcp.port". The "persist" setting makes the setting "for always", so also through reboots.
The "service" setting is a setting active until the next reboot.
The "service" setting is safer, but maybe a bit too much. I'm doubting whether it should become a multi-select as well "enable permanenly/temporary", "disable permanently/temporary".

this is the coolest app i have ever seen that was made with app inventor! great work! thanks a bunch!

I did a few improvements.
That means: it works flawless for me. I hope it does for others.
See updated first post with Changelog.

Looks great. Thank!

@surfer63 I'm getting era when trying to root my HU JY-UM135N2
I unzip file open cmd as a administrator copy_install to cmd and it says system cannot find path specified. I have adb over WiFi enable and show up address apk. here is. screen shot
Sent from my Pixel XL using Tapatalk

freddienuxx said:
@surfer63 I'm getting era when trying to root my HU JY-UM135N2
I unzip file open cmd as a administrator copy_install to cmd and it says system cannot find path specified. I have adb over WiFi enable and show up address apk. here is. screen shotView attachment 4196251
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
What did you download?
The SuperSU V2.82 SR1 from the Releases page?
The error you get is that the adb.exe can't be found, so I wonder what you downloaded, or how you unzipped it.

Thanks a lot for yor effort! Already istalled and changed the radio app on my 124N2 . Great work.
Two things came across my mind: Please mention somewhere in your description that the user should be logged into a WLAN to allow Joying_extra_tools to download the wanted .apks (didn't found that. Well it's obvious, but sometimes it's bettter to avoid misunderstandings). Second: Can you implement a "reboot button"? This way yo can be sure people reboot and not just switch off/on.
Thanks again from a happy Joing user ?

AP756 said:
Thanks a lot for yor effort! Already istalled and changed the radio app on my 124N2 . Great work.
Two things came across my mind: Please mention somewhere in your description that the user should be logged into a WLAN to allow Joying_extra_tools to download the wanted .apks (didn't found that. Well it's obvious, but sometimes it's bettter to avoid misunderstandings). Second: Can you implement a "reboot button"? This way yo can be sure people reboot and not just switch off/on.
Thanks again from a happy Joing user
Click to expand...
Click to collapse
I will mention the WLAN necessity. To me it was completely obvious, but you are right. It will mention it on the website
I have a WiFi option in the Top-left menu. I will use the functionality on startup like: "Hey user. You don't have an active WiFi connection. blah blah blah"
The reboot button is already integrated in the actions, but I need to change a lot of "feedback" screens like
Code:
"This has been done. The unit needs to be rebooted."
[reboot] [No, I do it later]

surfer63 said:
What did you download?
The SuperSU V2.82 SR1 from the Releases page?
The error you get is that the adb.exe can't be found, so I wonder what you downloaded, or how you unzipped it.
Click to expand...
Click to collapse
I actually downloaded the first root kit root master and the second one as well SuperSU . i downloaded to download folder unzipped it with WinZip and unzipped in same place/downloaded folder copy install.bat to cmd and I get that error. I forgot to mention unzipped it into downloaded wit no folder.
Sent from my Pixel XL using Tapatalk

surfer63 said:
I will mention the WLAN necessity. To me it was completely obvious, but you are right. It will mention it on the website
I have a WiFi option in the Top-left menu. I will use the functionality on startup like: "Hey user. You don't have an active WiFi connection. blah blah blah"
The reboot button is already integrated in the actions, but I need to change a lot of "feedback" screens like
Code:
"This has been done. The unit needs to be rebooted."
[reboot] [No, I do it later]
Click to expand...
Click to collapse
Hey, thanks for the fast feedback. Installed Viper right now and had no issues at all. Regarding the reboot option I think I missed it, because I use a large font. I didn't see that...
Greetings

freddienuxx said:
I forgot to mention unzipped it into downloaded wit no folder.
Click to expand...
Click to collapse
That was wrong. It is based on the folder structure. I hate it when it becomes one big mess, instead of a nicely separated "tools" and "stuff" setup.

AP756 said:
Hey, thanks for the fast feedback. Installed Viper right now and had no issues at all. Regarding the reboot option I think I missed it, because I use a large font. I didn't see that...
Click to expand...
Click to collapse
No, typo in the command parameter for the popup. I will correct it.

Hey Guys.
Yesterday my Radio.apk was gone after a reboot.
I installed the blue-white mod a day before.
Did this ever happens to anyone else?
Now i did reset all and installed again everything and hope that it won`t dissapear again. Maybe i freezed something wrong with Titanium Backup.
Thx

f1nch87 said:
Hey Guys.
Yesterday my Radio.apk was gone after a reboot.
I installed the blue-white mod a day before.
Did this ever happens to anyone else?
Now i did reset all and installed again everything and hope that it won`t dissapear again. Maybe i freezed something wrong with Titanium Backup.
Click to expand...
Click to collapse
When reporting these kind of things, please also mention what you did, how you did it, on which ROM version (5.11/6.0.1, which date) (and if relevant using which version of my apk). Your "report" makes it hard to diagnose as we need to ask all kind of counter questions to get relevant info.
Do you mean you used my app to install the blue-white mod?
Did you reboot immediately after the install, or was the "next day reboot" your first reboot?
Did you use the 1.0 or the 1.01 version of my apk?
What do you mean with "reset all and installed everything again"? I hope you don't mean you flashed the entire ROM, or did a factory reset? There is always the possibility to re-install the original radio apk, also from my apk.

surfer63 said:
When reporting these kind of things, please also mention what you did, how you did it, on which ROM version (5.11/6.0.1, which date) (and if relevant using which version of my apk). Your "report" makes it hard to diagnose as we need to ask all kind of counter questions to get relevant info.
Do you mean you used my app to install the blue-white mod?
Did you reboot immediately after the install, or was the "next day reboot" your first reboot?
Did you use the 1.0 or the 1.01 version of my apk?
What do you mean with "reset all and installed everything again"? I hope you don't mean you flashed the entire ROM, or did a factory reset? There is always the possibility to re-install the original radio apk, also from my apk.
Click to expand...
Click to collapse
Sorry for my inacurate question
So. I am on Android 6.0.1 official Joying, Version of May 25th.
I have it succesfully rooted and installed the Radio.apk (Blue-White) with your Joying Extra Tools 1.01.
I also changed DPI to 200.
The App did not dissapear after a immediately reboot. It happened after the car was turned off one night and then the HU reboots Android and it was gone.
And yes i then did flash the rom again then.

f1nch87 said:
Sorry for my inacurate question
So. I am on Android 6.0.1 official Joying, Version of May 25th.
I have it succesfully rooted and installed the Radio.apk (Blue-White) with your Joying Extra Tools 1.01.
I also changed DPI to 200.
The App did not dissapear after a immediately reboot. It happened after the car was turned off one night and then the HU reboots Android and it was gone.
And yes i then did flash the rom again then.
Click to expand...
Click to collapse
Thanks for the report
Apart from the fact that this should not have happened, the best approach here would have been to install the "Joying Default" from my apk. We have had several issues where my radio mod does work for one person and not at all for another (from my previous scripts). However, a re-install from the original radio apk always fixed the issue.
Anyway, I will continue to try to find the issue why it sometimes fails. I guess it has to do with the underlaying CarRadio app that does the real work, and the Radio app just being the GUI to it.

Paylib Société Générale - Rooted / Unlocked bootloader phone & how to make it work

Paylib Société Générale - Rooted / Unlocked bootloader phone & how to make it work
This is a guide only for French users of the Société Générale Bank, in order to make the Paylib app work with a rooted/unlocked phone.
When launching, the app can display "Cette application est incompatible avec votre téléphone" on the basis it is rooted or unlocked.
I made the app work using Magisk 13.2B on a ZTE Axon 7
- Enable Magisk & Magisk Hide
- Hide the following apps (fewer may be required, it just works as-is for now)
> Android Services Library
> Android SHared Libary
>Gestionnaire de comptes Google (com.google.gsf.login)
>Google Play Store
> mobi.societegenerale.mobile.hce.sghce (com.societegenerale.paylibsanscontact)
> Shell
>Société Générale (if you have the app installed - mobi.societegenerale.mobile.lappli)
There it is, enjoy

I'm trying to do the same with OnePlus 3 with Oreo and for PayLib solution by Banque Populaire (fr.banquepopulaire.ccmp).
Without success...
I've got :
- OP3
- OxygenOS 5.0
- Android 8.0.0
- Magisk 14.5
And I've tried with hiding the following :
- Banque Populaire Cyberplus (fr.banquepopulaire.cyberplus)
- Paiement mobile (fr.banquepopulaire.ccmp)
- and like you,
--- Android Shared Library (com.google.android.ext.shared)
--- Android Services Library (com.google.android.ext.services)
--- Google Play Store (com.android.vending)
--- Shell (com.android.shell)
I don't have the Gestionnaire de compte (com.google.gsf.login)
Is it still working with your phone with Société Générale ?

apollonaute said:
I'm trying to do the same with OnePlus 3 with Oreo and for PayLib solution by Banque Populaire (fr.banquepopulaire.ccmp).
Without success...
I've got :
- OP3
- OxygenOS 5.0
- Android 8.0.0
- Magisk 14.5
And I've tried with hiding the following :
- Banque Populaire Cyberplus (fr.banquepopulaire.cyberplus)
- Paiement mobile (fr.banquepopulaire.ccmp)
- and like you,
--- Android Shared Library (com.google.android.ext.shared)
--- Android Services Library (com.google.android.ext.services)
--- Google Play Store (com.android.vending)
--- Shell (com.android.shell)
I don't have the Gestionnaire de compte (com.google.gsf.login)
Is it still working with your phone with Société Générale ?
Click to expand...
Click to collapse
ouais ouais, same for me...
Banque Pop. Paiement Mobile used to work, until yesterday.
Since the payment app has been updated (to v1.4.0), it detects root and does not start, even after hiding the recommended apps & gapps, disable USB debugging...
Tested with Magisk 14.0.
I will try to hide some other apps, but Paiement Mobile might detect other apps requiring root (such as Titanium Backup or the like)

fred.lyon said:
ouais ouais, same for me...
Banque Pop. Paiement Mobile used to work, until yesterday.
Since the payment app has been updated (to v1.4.0), it detects root and does not start, even after hiding the recommended apps & gapps, disable USB debugging...
Tested with Magisk 14.0.
I will try to hide some other apps, but Paiement Mobile might detect other apps requiring root (such as Titanium Backup or the like)
Click to expand...
Click to collapse
Funny that Pokémon Go and other apps like that didn't do the same trick to detect root, and Banque Populaire app with 10k users (play store said) succeed detecting root.

Finally, I made it. Here are the steps that worked for me:
1. check if RootBeer Sample can detect root --> yes (su & busybox)
2. flash Busybox-cleaner found here
3. install Magisk module "Busybox for Android NDK"
4. check if RootBeer Sample can detect root --> no :victory:
5. deactivate Apps2SD; don't know why, but this app or its scripts allow "Paiement mobile" to detect root
Several other apps using root could help payment apps to detect root.
Great! Now I can use this sh..ty app that works once every 5 trials... :silly:

fred.lyon said:
Finally, I made it. Here are the steps that worked for me:
1. check if RootBeer Sample can detect root --> yes (su & busybox)
2. flash Busybox-cleaner found here
3. install Magisk module "Busybox for Android NDK"
4. check if RootBeer Sample can detect root --> no :victory:
5. deactivate Apps2SD; don't know why, but this app or its scripts allow "Paiement mobile" to detect root
Several other apps using root could help payment apps to detect root.
Great! Now I can use this sh..ty app that works once every 5 trials... :silly:
Click to expand...
Click to collapse
I followed your steps without success. I don't have Apps2SD but Lucky Patcher (more or less the same intrusive ODEX modifier/patcher).
Nevermind, I'm still searching the app/tool which blocks that Paiement Mobile sh**ty app.

apollonaute said:
I followed your steps without success. I don't have Apps2SD but Lucky Patcher (more or less the same intrusive ODEX modifier/patcher).
Nevermind, I'm still searching the app/tool which blocks that Paiement Mobile sh**ty app.
Click to expand...
Click to collapse
I succeeded to identify Apps2SD as troublemaker by symply deactivating it with TitaniumBackup. All the following apps (for rooted devices) are installed on my phone and none of them prevent the Paylib app to start:
- ROM Toolbox
- SD Maid
- Root Explorer
- Apps Ops
- Betterbatterystats
- Aurostarts
- Adaway
Hope it will shorten the list of apps to test.

Here the image of my RootBeer Sample app. What about yours?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://ibb.co/d10xn6

apollonaute said:
Here the image of my RootBeer Sample app. What about yours?
https://ibb.co/d10xn6
Click to expand...
Click to collapse
Mine is now green for all categories.
Yours is looking like mine before making a fresh réinstallation of Magisk, cleaning busybox and reinstalling it as a Magisk module.
Are you sure Magisk Hide is working for you? What's going on when you install Root Checker (by App Hippie), hide it in Magisk and then run the app again?

My mistake. I didn't hide RootBeer. Now I've hide it. And now almost everything is green checked. Except "potentially dangerous app".
So I need to find out which one breaks the root. Or at least makes other apps discover root.
I've tried with Root Check, with Magisk Hide and it works.
Edit : ok, with some app removed, now RootBeer is all green. But root is still detected by Paiement Mobile by Banque Populaire. F***ing app...

Hi I'm also trying to install paylib and have same problem. tried to hide modules with magisk didn't work... any help ? thanks
edit : I'm using ma ctre, app fo crédit agricole with a paylib part in it

Hello,
It works good with my device (Sony Xperia Z, LineageOS 14.1). I disabled "USB debug" in developer options and hide apps mentioned in the first post (MaBanque and MaCarte apps instead of SocieteGenerale ones).

Hello !
It works on my S9 with the Banque Populaire app, but if I activate the xposed framework, the app detects root.
Does someone have an idea ?
Thanks

Mati24 said:
Hello !
It works on my S9 with the Banque Populaire app, but if I activate the xposed framework, the app detects root.
Does someone have an idea ?
Thanks
Click to expand...
Click to collapse
Hello,
The BP app used to work up to its version 1.4.0 ("Paiement mobile" app).
At that time, the trick was to install this specific app version (from TitaniumBackup) without Xposed and XposedInstaller (but with proper config in MagiskHide), then make the registration process in the app (code received via SMS). After such an installation, reinstalling XposedInstaller and enabling Xposed framework in Magisk wasn't preventing from running the app; contactless payments were really working fine!
But this is no more possible with the latest version 1.5.0, which is detecting Xposed as soon as it's starting.
Moreover, since 1 week, the app 1.4.0 is requiring an update to 1.5.0, so previous method is no more working
I'm afraid we'll have to choose between this app and Xposed...
I'll try to find a workaround, but I'm a newbie, just able to follow tutos :silly:
If we're lucky :fingers-crossed:, we'll find a french developer also using one of Paylib applications for banks :laugh:

hi guys, since magisk 18 I can no longer hide from "Android SHared Libary", so application ma carte (crédit agricole) detects the root, has anyone found a solution?

oufouf84 said:
hi guys, since magisk 18 I can no longer hide from "Android SHared Libary", so application ma carte (crédit agricole) detects the root, has anyone found a solution?
Click to expand...
Click to collapse
Hello, I'm on magisk 19.3.. I just tried to install "ma carte" application from C.A. and the appli was refusing due to root ..bla bla bla even if Ma carte and my banque were hide in the magisk. So I've hidden also "Services Google paly" and it works... I just need to try now to pay something to be sure but at tleast no more root detected by the Ma Carte appli. Good luck !!

lorenzo_29 said:
Hello, I'm on magisk 19.3.. I just tried to install "ma carte" application from C.A. and the appli was refusing due to root ..bla bla bla even if Ma carte and my banque were hide in the magisk. So I've hidden also "Services Google paly" and it works... I just need to try now to pay something to be sure but at tleast no more root detected by the Ma Carte appli. Good luck !!
Click to expand...
Click to collapse
hi lorenzo,
Can you give me list of what you put in magisk hide?
thank

oufouf84 said:
hi lorenzo,
Can you give me list of what you put in magisk hide?
thank
Click to expand...
Click to collapse
Yep..Alors, I've got quite a lot of app declared but the one that I've selected under Magisk hide are the one related to google and Paylib:
- Service Google Play (com.google.android.gms) ==> 10 sub folders within this app.
- Ma Banque (fr.creditagricole.androidapp) ==> 2 sub folders within this app
- Ma Carte (fr.creditagricole.macarteca) ==> 2 sub folders within this app
- Google (com.google.android.googlequicksearchbox:search....) ==> 13 sub folders within this app
- Drive (com.google.android.apps.doc) ==> 4 sub folders within this app
I don't think the two latest one on this list are related to paylib root issue but more probably the app Services Google Play.
I've red somewhere that paylib app was looking at the android OS to check if the android smartphone is rooted or not.
Hope it will help you.

lorenzo_29 said:
Yep..Alors, I've got quite a lot of app declared but the one that I've selected under Magisk hide are the one related to google and Paylib:
- Service Google Play (com.google.android.gms) ==> 10 sub folders within this app.
- Ma Banque (fr.creditagricole.androidapp) ==> 2 sub folders within this app
- Ma Carte (fr.creditagricole.macarteca) ==> 2 sub folders within this app
- Google (com.google.android.googlequicksearchbox:search....) ==> 13 sub folders within this app
- Drive (com.google.android.apps.doc) ==> 4 sub folders within this app
I don't think the two latest one on this list are related to paylib root issue but more probably the app Services Google Play.
I've red somewhere that paylib app was looking at the android OS to check if the android smartphone is rooted or not.
Hope it will help you.
Click to expand...
Click to collapse
thank you lorenzo I try, the last two are cloud and search bar so I'm not error

oufouf84 said:
thank you lorenzo I try, the last two are cloud and search bar so I'm not error
Click to expand...
Click to collapse
I've tried the app this afternoon and it doesn't work in fact. The app is blocked due to root.. Sorry about the wrong info.

safetynet

hey i just decrypted my phone and Safetynet isn't passing for me anything I can do to fix this?

AngryUserLG said:
hey i just decrypted my phone and Safetynet isn't passing for me anything I can do to fix this?
Click to expand...
Click to collapse
There were apparently some updates in the past (year or two?) that made it harder overall to pass SafetyNet using rooted phones and/or those using certain ROMs. There's a way around it, though.
Toggling "MagiskHide" in the Magisk settings should take care of passing basicIntegrity, but the real issue is passing ctsProfile. There are two methods:
Download SafetyNet Fix and install the module manually in Magisk, or
Spoof the device fingerprint:
Download and install the "MagiskHide Props Config" and "Busybox for Android NDK" modules in Magisk, then reboot.
Open a terminal emulator (eg. Termux) and:
type su and press [enter]
type props and press [enter]
Select "Edit device fingerprint" (probably option 1)
Select "Pick a certified fingerprint" (probably option "f")
Enter the number "Google" (it was 7 for me)
Enter the number for "Pixel 3" or "Pixel 3 XL" (options 18 and 19, respectively, for me)
Select your Android version (11 was option 3 for me)
You'll see the value for ro.build.fingerprint in pink, enter "y" for yes
Enter "y" for yes when asked to reboot
Both options worked for me (I tested them separately). I don't know if you have to run it again if you update the ROM because an update hasn't come out since I did it.
EDIT: oops, thought I was responding to a Google Pixel 3 XL thread. I'll leave this here in case it helps you, though!

Detecting Universal SafetyNet Fix

How can an Android application detect that it is running on a rooted device that is running the Universal SafetyNet Fix with MagiskHide configured to hide from that application, props configured to a known good fingerprint, and magisk renamed to something else?
I have read that the Universal SafetyNet Fix module works by causing hardware attestation to fall back to basic when key attestation fails with the "not implemented" error. How can an app developer detect when this happens and require that true hardware attestation is used?

It's easy for any app to detect whether Android got tampered or not: No Magisk module can prevent this.
Only as example:
The Universal Safetynet Fix changes in system file named build.prop these properties
Code:
ro.boot.flash.locked
ro.boot.verifiedbootstate
ro.boot.veritymode
ro.boot.vbmeta.device_state
what in turn changes LastModifiedTime property of build.prop.
Hence it should be obvious - to see whether Android OS got tampered or not - the most easy method is comparing this timestamp with timestamp when Android OS was built.
IMO it's a misconception to believe that app developers are dumber than the developer of Magisk.

Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 6a Support Thread.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 6a devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.

chopt51 said:
This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.
Click to expand...
Click to collapse
If you don't choose wipe data, or force in flash options, then you should keep your data.

I have my 6a connected with usb. I chose where my platform tools are in a directory but it doesnt find a device via adb. Yet cmd shows an adb connection.

USB debugging turned on?

tlxxxsracer said:
Yet cmd shows an adb connection.
Click to expand...
Click to collapse
Explain what you mean by that?

badabing2003 said:
Explain what you mean by that?
Click to expand...
Click to collapse
usb debugging was on. when I run an adb/fastboot in cmd within the same directory my device is recognized

tlxxxsracer said:
usb debugging was on. when I run an adb/fastboot in cmd within the same directory my device is recognized
Click to expand...
Click to collapse
Please be clear and explicit, exactly what you ran and what response you got, please also generate support.zip file from the help menu of PixelFlasher and post it here.
There is no reason for it not to be detected if you're command detects it.

New Release:
Aug 24, 2022 v3.6.0 release
When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.
Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.
Improved tooltips.

Hello,
I have a pixel 6a on A12 rooted with Magisk.
I tried to upgrade to A13 with PixelFlasher (v3.6.0) with the option to flash all the slots and now I'm stuck in loop.
I tried to use fastboot command to flash again with A13 with no result. I also tried to change the current slot.
The weird thing is that I still have the message that said the bootloader is unlocked...
Any ideas?

jpdurand31 said:
Hello,
I have a pixel 6a on A12 rooted with Magisk.
I tried to upgrade to A13 with PixelFlasher (v3.6.0) with the option to flash all the slots and now I'm stuck in loop.
I tried to use fastboot command to flash again with A13 with no result. I also tried to change the current slot.
The weird thing is that I still have the message that said the bootloader is unlocked...
Any ideas?
Click to expand...
Click to collapse
If you can post support.zip file from help menu I can take a look.

If you want more info, i'm 100% available!

jpdurand31 said:
If you want more info, i'm 100% available!
Click to expand...
Click to collapse
Hmmm ...
I don't see any flashing logs in PixelFlasher, are you sure you flashed in PixelFlasher?
I see you started with PixelFlasher 3.4.0 and upgraded to 3.6.0; good
I see at first you did not have Android Platform Tools installed, and then had version 28.0.2-debian; bad, this is an old version, you should click on the blue link next to the Android Platform Tools and download the latest (don't install from package manager, those are usually old, just download the latest and unpack wherever you want, and point to it in PixelFlasher)
You started in adb mode (good), processed the firmware in PixelFlasher, but that is where you stopped, you did not attempt flashing in PixelFlasher (not sure what you did, but it would help to know)
On next attempt (one hour later) your device was in bootloader mode.
Then you tried disabling magisk, which didn't work because that feature requires adb mode, and your phone is stuck in fastboot mode.
You cannot create a patch file in fastboot mode, it needs to be in adb mode.
And please please don't dare to lock your bootloader, I see you attempted and then cancelled,
Code:
2022-09-02 18:25:29 Lock Bootloader
WARNING!!! WARNING!!! WARNING!!!
NEVER, EVER LOCK THE BOOTLOADER WITHOUT REVERTING
TO STOCK FIRMWARE OR YOUR PHONE WILL BE BRICKED!!!
Do you want to continue to Lock the device bootloader?
Press OK to continue or CANCEL to abort.
2022-09-02 18:25:42 User Pressed Cancel.
Aborting ...
If you lock your bootloader before fixing your device, you will be locked out forever (bricked)
So at this point what are your choice and how can you fix this?
1- get the latest Android Platform Tools
2- If PixelFlasher detects your device, check if it is in fastboot mode (f.b) or adb mode.
Select the firmware, process it, this will show the boot.img file
Select the boot.img file and choose keep data and hit Flash.
Yes I know, you will lose root because you're not flashing a patched boot.img, but you can always re-root if you recover your device.
Alternately, what happens if you select in PixelFlasher to reboot the device into System.
Does it reboot? and if it does, does it end up in adb mode of fastboot mode?
One other option you have is to flash OTA in sideload mode.
Report back, and make sure you capture all the manual steps you perform outside of PixelFlasher.
PixelFlasher logs would tell me everything you do in PixelFlasher, you can submit a new one after your operations.
Good luck

Thanks for your response and the detailed process.
I was fooled by the version of the package that was in 33...
By upgrading the Android Platform Tools to the latest version, I could update to Android 13.
Thanks a lot for the help and the reactivity!

New Release:
Sep 04, 2022 v3.7.0 release
New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.
New Feature: Install compatible apk file onto the device from PixelFlasher menu.
Check Android Platform Tools version and warn if it is old.
Block flashing when stock flash_all.bat file is tampered with.
Don't bother with flashing if bootloader is locked.
More validations and exceptions handling.
Improved logging.

3.7.0 does not start for me on Windows 10. It never appears in my task list as running. 3.6.0 is working fine.

JudasD said:
3.7.0 does not start for me on Windows 10. It never appears in my task list as running. 3.6.0 is working fine.
Click to expand...
Click to collapse
Thanks for reporting and sorry for your troubles.
Can you please open a command prompt, navigate to PixelFlasher 3.7.0 and run it from command prompt (just type PixelFlasher.exe), see if it displays an error in the console.
Can you also please generate a support.zip file using PixelFlasher 3.6.0 ?
It should capture the error PixelFlasher 3.7.0 encountered.

Thank you for the help. The issue has now been resolved after reboot.
Launching 3.7.0 via cli displayed no error message. I went to create support.zip with 3.6.0 and my computer BSODed. After reboot, 3.7.0 runs just fine. Apologies for the false alarm.

JudasD said:
Thank you for the help. The issue has now been resolved after reboot.
Launching 3.7.0 via cli displayed no error message. I went to create support.zip with 3.6.0 and my computer BSODed. After reboot, 3.7.0 runs just fine. Apologies for the false alarm.
Click to expand...
Click to collapse
No need for apology, happy to hear that the issue now resolved.

Not sure if this should be of concern, but upgrading to today's Android release, I got this (very early on, while selecting the device and firmware):
Code:
2022-09-12 18:44:06 ERROR: Exception during Magisk modules processing
Exception: not enough values to unpack (expected 2, got 1)
Everything seemed to work fine, though.