For all Joying units? Just checking before I install

For all Joying units? Just checking before I install
Does not workIs anyone tried this already? This updated SofiaServer.apk?
As I thought it contains some trojan..So just be aware guys.
Does it work for anyone here?
@IG_Vasilich Yes at some point there was an SD card in the GPS-Card slot. However I removed it after losing the mapdata that was on there through a factory reset. Since then there was no SD Card installed anymore.@SuperSalty
do you have any SD card in any slot? Have you had any somewhen?
Maybe, but I assume that the navi app is still installed and is still looking for its maps on the now missing SD-card.@IG_Vasilich Yes at some point there was an SD card in the GPS-Card slot. However I removed it after losing the mapdata that was on there through a factory reset. Since then there was no SD Card installed anymore.
Thanks for the fast replies from you guys! I really appreciate that!Maybe, but I assume that the navi app is still installed and is still looking for its maps on the now missing SD-card.
Or some persistent property makes the system look for an SD-card, because some program later started (the navi app, maybe no longer installed), might want to access the SD-card. Please try with a cleanly formatted SD-card and see if it runs through the boot process.
I tried it now.I'm afraid you have to flash your unit again, and you have to start with the Joying firmware.
Put the Joying firmware on a fat32 scdard.
Put it in your unit and reset your unit via the pinhole. When the bootlogo appears, reset it immediately. Do this 3 times.
The fourth time it should flash the Joying firmware. When everything is again up and running, you can use the suctom apk to replace the recovery image again and then flash the gtx rom again (if you want to)
If you still have the custom twrp recovery in place, you should try to boot into the twrp recovery. From that point you can reinstall the gtx custom rom (see post #627)Honestly, since I flashed the HU a long time ago, I'm not entirely sure if I replaced the custom recovery with the original one. Since the HU is showing all sorts of unexpected behavior, I'm assuming I did not replace the custom recovery after flashing.
Since you're already mentioning my most likely bad position with the custom recovery still in place:
Do you have any idea about how I could unbrick the HU with the custom recovery still in place?
====Includes====
xposed v87 x86
open gapps x86 Nano Feb 2018
ViPER4ANDROID FX
precompiled dalvik cache (first boot 2 minutes)
enabled eth0 at boot at 192.168.65.100 for debugging
ADB enabled
SeSuperuser built-in
Included [custom] app to manage superdavex's custom recovery for easy installation and maintenance
RightCamera (front cam app) modified APK
AOSP android boot animation
Interactive cpu governor:
go_highspeed_load set at 70% CPU load
titanium backup
nova launcher
GVC CallHandler 4 Joying
Amaze File Manager
Xposed modules:
boot manager
gravitybox
no overlay warning
immsersive mode forcer
app settings
fake wifi
GPSSpeedFix
======Removed======
[I]Debug Services:[/I]
usbactive
sqldebug
pekallfmrserver
watchdog
ap_logfs
apk_logfs
log-watch
crashlogd
adbusbmuxd
adbec
bootwatcher
shcmd
fmd
[I]Removed Apps:
[/I]
BasicDreams
BluetoothMidiService
Exchange2
Galaxy4
HoloSpiralWallpaper
LiveWallpapers
LiveWallpapersPicker
NoiseField
OpenWnn
PhaseBeam
PrintSpooler
GooglePinyinIME
RKUpdateService
CaptivePortalLogin
WAPPushManager
[I]removed from /system-priv-app
[/I]ManagedProvisioning
CallLogBackup
OemTelephonyApp
DeviceTest
StressTest
WallpaperCropper
GoogleFeedback
ProxyHandler
CellBroadcastReceiver
[I]Removed FYT APPS[/I] ( these slow the system down considerably, even when not in use )
SYU-1-C9-Calculator-V1.0
Sofia-1-C9-TV-V1.0
JY-1-C9-Video-V1.0
JY-1-C9-TimeWeather-V1.0
SYU-1-FileManager-V1.0
SYU-1-C9-Update-V1.0
Sofia-1-C9-ExDvr-V1.0
SYU-1-C5009-DVR-V1.0
Sofia-1-C9-Gallery-V1.0
JY-1-C9-MUSIC-V1.0
ZBox
cp -R /system/vendor/oem/LiveWall* /system/app