Database Users

[Q] Unable to update to stock android 4.2.2 using multirom

I am using multirom v8, with TWRP v2.4.1.0 on a Nexus 7 Wi-fi version. I have stock Android 4.2.1 (but with Tasssadar's kexec-hardboot kernel) as internal and Ubuntu 13.04.
I received the notification that the 4.2.2 update was available. So, I started to install it but it was unsuccessful. I do not remember but I think it said that update had failed and it rebooted.
So, I manually downloaded the update ( to update build JOP40D to JDQ39) and tried to install it using the modified recovery. Got the following error message (relevant parts):
I:Attempt to load settings from settings file...
I:Version number saved to '/cache/recovery/.version'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying current system...
contents of partition "/dev/block/platform/sdhci-tegra.3/by-name/LNX" didn't match EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd
file "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
E:Error in /sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
(Status 7)
Error flashing zip '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'
Updating partition details...
Any suggestions to fix this issue?
PS: I would have posted this here: http://forum.xda-developers.com/showpost.php?p=38043472&postcount=1157 but I do not have sufficient priviledges...

rigved said:
I am using multirom v8, with TWRP v2.4.1.0 on a Nexus 7 Wi-fi version. I have stock Android 4.2.1 (but with Tasssadar's kexec-hardboot kernel) as internal and Ubuntu 13.04.
I received the notification that the 4.2.2 update was available. So, I started to install it but it was unsuccessful. I do not remember but I think it said that update had failed and it rebooted.
So, I manually downloaded the update ( to update build JOP40D to JDQ39) and tried to install it using the modified recovery. Got the following error message (relevant parts):
I:Attempt to load settings from settings file...
I:Version number saved to '/cache/recovery/.version'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying current system...
contents of partition "/dev/block/platform/sdhci-tegra.3/by-name/LNX" didn't match EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd
file "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
E:Error in /sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
(Status 7)
Error flashing zip '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'
Updating partition details...
Any suggestions to fix this issue?
PS: I would have posted this here: http://forum.xda-developers.com/showpost.php?p=38043472&postcount=1157 but I do not have sufficient priviledges...
Click to expand...
Click to collapse
I think the problem is with bootloader (not sure) ...i had same multirom (cyanogenmod +Ubuntu ) ..i deleted ubuntu then flashed Stock 4.2.1 with wugstool then updated to 4.2.2 ... try updating bootloader

rigved said:
I am using multirom v8, with TWRP v2.4.1.0 on a Nexus 7 Wi-fi version. I have stock Android 4.2.1 (but with Tasssadar's kexec-hardboot kernel) as internal and Ubuntu 13.04.
I received the notification that the 4.2.2 update was available. So, I started to install it but it was unsuccessful. I do not remember but I think it said that update had failed and it rebooted.
So, I manually downloaded the update ( to update build JOP40D to JDQ39) and tried to install it using the modified recovery. Got the following error message (relevant parts):
I:Attempt to load settings from settings file...
I:Version number saved to '/cache/recovery/.version'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying current system...
contents of partition "/dev/block/platform/sdhci-tegra.3/by-name/LNX" didn't match EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd
file "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5060608:319331fae14fec8a88063751475fce26bae328e0:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
E:Error in /sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
(Status 7)
Error flashing zip '/sdcard/Download/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip'
Updating partition details...
Any suggestions to fix this issue?
PS: I would have posted this here: http://forum.xda-developers.com/showpost.php?p=38043472&postcount=1157 but I do not have sufficient priviledges...
Click to expand...
Click to collapse
I *just* fixed this problem. Mine was failing on the same line. The trick is to modify the updater-script. I modified it to stop the check, and it flashed without a problem on my tablet. I also removed the sections where it replaced the recovery.
I'm hesitant to post mine because I was NOT running multiboot, so when it patched the bootloader regardless of the checksum, I was fine (Or lucky). I don't know what will happen if you use the one I modified, or if 4.2.1 CAN be updated safely without touching the bootloader.
So here: This script is very untested, and modified by someone who doesn't fully understand what he did. Use this at your own risk, and realize I hold no responsibility if you brick your N7..
That said, if you replace the 'updater-script' in the update zip (located in META-ING/com/google/android) with this one, it will patch.

The LNX partition is the boot partition.
That check is failing because when the script looks at the existing LNX partition (boot), it does not find what it expects to find.
The OTA patches existing files, it doesn't replace them with a full replacement copy. So the starting condition of each file to be patched must be exact.
I believe that the check of the LNX partition is the very last checksum verified, so that is good news - it means nothing else checked in /system is mismatched.
You can either hack the installer script as above (and thus need to use a custom recovery to install it because this will break the signing of the factory package), or you can use a completely safe route:
- make full Nandroid backup (including recovery if possible)
- flash the stock 4.2.1 boot image ( not bootloader! ) to the boot partition
- copy the factory ota .zip file to /cache/update.zip
- create a file named "command" with a single line in it:
--update_package=/cache/update.zip
and copy it to /cache/recovery/command
- flash the stock 4.2.1 recovery to the recovery partition
- reboot to recovery
This runs the pure stock OTA install which does all the patching plus installs a new 4.18 bootloader, 4.2.2 boot partition, and 4.2.2 stock recovery.
Before you get too antsy bear in mind that this whole situation is likely to happen again with the next OTA - meaning, it would be a great time to get a backup of pure stock 4.2.2 (including stock recovery and stock boot partition).
So, now:
- perform a soft boot of a custom recovery (don't flash it in place just yet!)
- overflash a SuperSU/Superuser root kit
- make a Nandroid Backup of this entire "lightly rooted pure stock 4.2.2 ROM" - including the recovery partition!
- hard-flash your custom recovery
- restore only the boot partition from the first Nandroid backup described in these instructions.
cheers

Unable to mount storage when I try to install official MIUI ROMs

Code:
unmount of /firmware failed; no such volume
mount: failed to mount /dev/block/bootdevice/by-name/splash at /firmware: Invalid argument
unmount of /firmware failed; no such volume
My TWRP 3.0.2-0 always show this error when I try to install any official MIUI ROMs. I only can install custom ROMs through TWRP.

(Help) Plasma Mobile porting

I am currently trying to port Plasma Mobile to the 6P. I have gotten through all of the configuration, minus setting the LD_LIBRARY_PATH (causes bootloop, manually export before running lxc-start) and the screen brightness control (Nexus 5/X are LCD). I am currently stuck trying to get lxc to launch the system. It throws the following error:
Code:
1|angler:/ # lxc-start -n system -F
The configuration file contains legacy configuration keys.
Please update your configuration file!
lxc-start: system: namespace.c: lxc_clone: 67 Failed to clone (0x2c020000): Invalid argument.
lxc-start: system: start.c: lxc_spawn: 1253 Invalid argument - Failed to clone a new set of namespaces.
lxc-start: system: start.c: __lxc_start: 1459 Failed to spawn container "system".
lxc-start: system: tools/lxc_start.c: main: 371 The container failed to start.
lxc-start: system: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.
I'm not too sure as to what is going on with the error, as I have never used lxc before.
Attempting to set the logfile throws the following, even after remounting to rw:
Code:
angler:/ # lxc-start -n system -F -o log
lxc-start: system: log.c: log_open: 383 failed to open log file "log" : Read-only file system
Extra info:
LineageOS 14.1 latest nightly
pm-rootfs-20170210-152001 for the rootfs
Latest lxc-android
Any help is appreciated, as I am kinda stuck right now.

Dualboot patcher For A7/A5

Please release official Dualboot patcher for A7/A5.
:laugh::laugh::laugh:

Already done.
I'v tried it.
I install second ROM on sd card, but it cycle rebooting. Helps only restore from TWRP recovery.
DualBootUtilities..zip have an ERROR 1 in TWRP.
https://dbp.noobdev.io/supported_devices.html
Samsung Galaxy A5 (2017)
General information:
Device ID: a5y17lte
Codenames: a5y17lte, a5y17ltexx, SM-A520F
Architecture: armeabi-v7a
Block device paths
Base directories:
/dev/block/platform/13540000.dwmmc0/by-name
/dev/block/bootdevice/by-name
/system block devices:
/dev/block/platform/13540000.dwmmc0/by-name/system
/dev/block/bootdevice/by-name/system
/dev/block/mmcblk0p19
/cache block devices:
/dev/block/platform/13540000.dwmmc0/by-name/cache
/dev/block/bootdevice/by-name/cache
/dev/block/mmcblk0p20
/data block devices:
/dev/block/platform/13540000.dwmmc0/by-name/data
/dev/block/bootdevice/by-name/data
/dev/block/mmcblk0p25
Boot partition block devices:
/dev/block/platform/13540000.dwmmc0/by-name/boot
/dev/block/bootdevice/by-name/boot
/dev/block/mmcblk0p10
Recovery partition block devices:
/dev/block/platform/13540000.dwmmc0/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/mmcblk0p11
Boot UI
Supported: yes
Flags:
TW_HAS_DOWNLOAD_MODE
Maximum brightness: 255
Graphics backends: fbdev
Theme: portrait_hdpi
Click to expand...
Click to collapse

One more theme about Dual Boot

Root/Rom for Allwinner QUAD-CORE 1.5 Ghz exdroid venus-a3 sun8iw15p1 2GB/32GB (Xomax XM2VA757)

Hi all ... I fee like a noob again. Just got me a head unit for my 2003 Volvo V70 and I cannot find any info anywhere on the device .. I's a new (2 week old) unit purchaced though Amazon.nl but the basic device is as listed below (AIDA64 Report).
It claims to be an A23 system running Android 10, but from the 4 cores, Linux Kernel version and API level, it looks more to me like a pin-compatible A33 (possibly sitting on an A 23 board) and running Android 9 ... AIDA confirmed this.
My problems are that it is stuffed with non-disableable loader and vendor-installed sotftware which are all rubbish, various options (specifically things like Notification Access) are disabled, and the inbuilt loader and software seems to be getting in the way of my being able to run a good launcher and/or choose the right applications to launch. This may also be a hybrid based on a tablet .. I'm not sure ...
Looking for advice/help on how to root this particualt device so that I can at least disable the bloatware, and if possible a nice clean stripped down rom for such a device.
With guideance, I can prtovide any data and/or software from the device. I am current;y requesting an installable ROM from the vendor but I don't think it will happen ... keeping my fingers crossed.
AIDA 64 report in the following post

MCU : SA92G1.201024.V1.1-MCX
DVD : SA91G1.201024.V1.2-MCX-TTL-DL860
BUILD No: MCX.U16.3.USER.BUILD.20201117-095320
<<< System >>>
Manufacturer: Allwinner
Model: QUAD-CORE
Brand: Allwinner
Board: exdroid
Device: venus-a3
Hardware: sun8iw15p1
Platform: venus
Product: venus_a3
Installed RAM: 2 GB
Total Memory: 1997 MB
Available Memory: 786 MB
Internal Storage Total Space: 25.67 GB
Internal Storage Free Space: 23.46 GB
External Storage #1 Total Space: 31.24 GB
External Storage #1 Free Space: 30.68 GB
External Storage #2 Total Space: 116.46 GB
External Storage #2 Free Space: 116.01 GB
Bluetooth Version: 4+
Device Features: android.hardware.audio.output
android.hardware.bluetooth
android.hardware.bluetooth_le
android.hardware.camera
android.hardware.camera.any
android.hardware.camera.front
android.hardware.ethernet
android.hardware.faketouch
android.hardware.location
android.hardware.location.gps
android.hardware.location.network
android.hardware.microphone
android.hardware.ram.low
android.hardware.screen.landscape
android.hardware.screen.portrait
android.hardware.sensor.accelerometer
android.hardware.touchscreen
android.hardware.touchscreen.multitouch
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.usb.accessory
android.hardware.usb.host
android.hardware.wifi
android.hardware.wifi.direct
android.software.app_widgets
android.software.autofill
android.software.backup
android.software.cant_save_state
android.software.companion_device_setup
android.software.connectionservice
android.software.cts
android.software.device_admin
android.software.home_screen
android.software.input_methods
android.software.live_wallpaper
android.software.verified_boot
android.software.webview
<<< CPU >>>
Core Architecture: 4x ARM Cortex-A7 @ 1512 MHz
Instruction Set: 32-bit ARMv7
CPU Revision: r0p5
CPU Cores: 4 Cores
CPU Clock Range: 480 - 1512 MHz
Core 1 Clock: 1512 MHz
Core 2 Clock: 1512 MHz
Core 3 Clock: 1512 MHz
Core 4 Clock: 1512 MHz
Supported ABIs: armeabi-v7a, armeabi
Supported 32-bit ABIs: armeabi-v7a, armeabi
AES: Not Supported
NEON: Supported
PMULL: Not Supported
SHA1: Not Supported
SHA2: Not Supported
<<< Display >>>
Screen Resolution: 1024 * 600
Screen Size: 155 mm × 86 mm
Screen Diagonal: 6.98 inches
Pixel Density: 170 dpi (mdpi)
xdpi / ydpi: 168 / 177 dpi
GPU Vendor: ARM
GPU Renderer: Mali-400 MP
Refresh Rate: 59 Hz
Default Orientation: Landscape
OpenGL ES Version: 2.0
GPU Version: OpenGL ES 2.0 8c81e1f
OpenGL ES Extensions: GL_EXT_debug_marker
GL_OES_texture_npot
GL_OES_vertex_array_object
GL_OES_compressed_ETC1_RGB8_texture
GL_EXT_compressed_ETC1_RGB8_sub_texture
GL_OES_standard_derivatives
GL_OES_EGL_image
GL_OES_depth24
GL_ARM_rgba8
GL_ARM_mali_shader_binary
GL_OES_depth_texture
GL_OES_packed_depth_stencil
GL_EXT_texture_format_BGRA8888
GL_OES_vertex_half_float
GL_EXT_blend_minmax
GL_OES_EGL_image_external
GL_OES_EGL_sync
GL_OES_rgb8_rgba8
GL_EXT_multisampled_render_to_texture
GL_EXT_discard_framebuffer
GL_OES_get_program_binary
GL_ARM_mali_program_binary
GL_EXT_shader_texture_lod
GL_EXT_robustness
GL_OES_depth_texture_cube_map
GL_KHR_debug
GL_ARM_shader_framebuffer_fetch
GL_ARM_shader_framebuffer_fetch_depth_stencil
GL_OES_mapbuffer
<< Wi-Fi >>
5 GHz Band: Not Supported
Wi-Fi Aware: Not Supported
Wi-Fi Direct: Supported
<<< Battery >>>
Power Source: A/C Charger
Level: 0 %
Status: Charging
Health: Good
Technology: LiFe
Temperature: 30.0°C
Voltage: 0.001 V
Capacity (Reported by Android): 2850 mAh
<<< Android >>>
Android Version: 9 (Pie)
API Level: 28
Android Security Patch Level: 2019-01-05
Rooted Device: No
Android ID: 68c8e810c1581721
Build ID: MCX.UI6_3.USER.BUILD.20201117-095320
Codename: REL
Fingerprint: Allwinner/venus_a3/venus-a3:9/PPR1.181005.003/20201117-095320:user/test-keys
ID: PPR1.181005.003
Incremental: 20201117-095320
Java Runtime Version: Android Runtime 0.9
Java VM Version: ART 2.1.0
Java VM Heap Size: 192 MB
Kernel Architecture: armv7l
Kernel Version: 4.9.118
Tags: test-keys
Type: user
Google Play Services Version: 21.09.15 (110302-361652764)
Huawei Mobile Services Version: < Not Present >
OpenSSL Version: OpenSSL 1.1.0 (compatible; BoringSSL)
ZLib Version: 1.2.11
ICU CLDR Version: 32.0.1
ICU Library Version: 60.2
ICU Unicode Version: 10.0
Android Language: English (United States)
Configured Time Zone: Central European Summer Time (UTC+02:00)
UpTime: 00:23:15
<<< Devices >>>
No cameras found. Camera permission needs to be granted.
No USB devices found.
No OpenCL devices found.
No CUDA devices found.
No Vulkan devices found.
No PCI devices found.
<<< Directories >>>
Data: /data
Root: /system
Java Home: /system
Download/Cache Content: /data/cache
<< External Storage >>
Primary External Storage: /storage/emulated/0
External Files #1: /storage/emulated/0/Android/data/com.finalwire.aida64/files
External Files #2: /storage/sdcard/Android/data/com.finalwire.aida64/files
External Files #3: /storage/usb1/Android/data/com.finalwire.aida64/files
Alarms: /storage/emulated/0/Alarms
DCIM: /storage/emulated/0/DCIM
Downloads: /storage/emulated/0/Download
Movies: /storage/emulated/0/Movies
Music: /storage/emulated/0/Music
Notifications: /storage/emulated/0/Notifications
Pictures: /storage/emulated/0/Pictures
Podcasts: /storage/emulated/0/Podcasts
Ringtones: /storage/emulated/0/Ringtones
<< Mount Points >>
/: Device: /dev/root
File System: squashfs
Read-Only
/dev: Device: tmpfs
File System: tmpfs
Read-Write
/dev/pts: Device: devpts
File System: devpts
Read-Write
/dev/memcg: Device: none
File System: cgroup
Read-Write
/dev/cpuctl: Device: none
File System: cgroup
Read-Write
/dev/cg2_bpf: Device: cg2_bpf
File System: cgroup2
Read-Write
/dev/usb-ffs/adb: Device: adb
File System: functionfs
Read-Write
/proc: Device: proc
File System: proc
Read-Write
/sys: Device: sysfs
File System: sysfs
Read-Write
/sys/fs/selinux: Device: selinuxfs
File System: selinuxfs
Read-Write
/sys/kernel/debug: Device: debugfs
File System: debugfs
Read-Write
/sys/kernel/debug/tracing: Device: tracefs
File System: tracefs
Read-Write
/sys/fs/bpf: Device: bpf
File System: bpf
Read-Write
/sys/fs/pstore: Device: pstore
File System: pstore
Read-Write
/mnt: Device: tmpfs
File System: tmpfs
Read-Write
/mnt/runtime/default/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/mnt/runtime/read/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/mnt/runtime/write/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/mnt/media_rw/usb1: Device: /dev/block/vold/public:8,1
File System: fuseblk
Read-Write
/mnt/runtime/default/usb1: Device: /mnt/media_rw/usb1
File System: sdcardfs
Read-Write
/mnt/runtime/read/usb1: Device: /mnt/media_rw/usb1
File System: sdcardfs
Read-Write
/mnt/runtime/write/usb1: Device: /mnt/media_rw/usb1
File System: sdcardfs
Read-Write
/mnt/media_rw/sdcard: Device: /dev/block/vold/public:179,65
File System: vfat
Read-Write
/mnt/runtime/default/sdcard: Device: /mnt/media_rw/sdcard
File System: sdcardfs
Read-Write
/mnt/runtime/read/sdcard: Device: /mnt/media_rw/sdcard
File System: sdcardfs
Read-Write
/mnt/runtime/write/sdcard: Device: /mnt/media_rw/sdcard
File System: sdcardfs
Read-Write
/vendor: Device: /dev/block/by-name/vendor
File System: squashfs
Read-Only
/acct: Device: none
File System: cgroup
Read-Write
/config: Device: none
File System: configfs
Read-Write
/bootloader: Device: /dev/block/by-name/bootloader
File System: vfat
Read-Write
/data: Device: /dev/block/by-name/UDISK
File System: f2fs
Read-Write
/cache: Device: /dev/block/by-name/cache
File System: ext4
Read-Write
/storage: Device: tmpfs
File System: tmpfs
Read-Write
/storage/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/storage/usb1: Device: /mnt/media_rw/usb1
File System: sdcardfs
Read-Write
/storage/sdcard: Device: /mnt/media_rw/sdcard
File System: sdcardfs
Read-Write
/storage/self: Device: tmpfs
File System: tmpfs
Read-Write
<<< System Files >>>
Buddy Info: /proc/buddyinfo
Build Properties: /system/build.prop
Character & Block Devices: /proc/devices
Command Line: /proc/cmdline
CPU Information: /proc/cpuinfo
Default Properties: /default.prop
Execution Domains: /proc/execdomains
File Systems: /proc/filesystems
Frame Buffer Devices: /proc/fb
Hosts: /system/etc/hosts
Interrupts: /proc/interrupts
Input Devices: /proc/bus/input/devices
I/O Ports: /proc/ioports
Kernel Version: /proc/version
Load Average: /proc/loadavg
Locked Files: /proc/locks
Memory Information: /proc/meminfo
Memory Map: /proc/iomem
Misc Drivers: /proc/misc
Partitions: /proc/partitions
Statistics: /proc/stat
Swap Spaces: /proc/swaps

After doing loads of research I'm even more confused ...
CPU-Z reports the system as an Allwinner A23 ... And then tells me it's a 4 core processor .. the A23 is a 2 core .. but the A33 is pin compatible with the A23 and is a 4 core so is it an A33 masquerading as an A23 .. but there is also another question mark n in the mix ...
Anyone got any advice on how to proceed with this strange crossbreed of a device ?
Will I brick it if I try to root it as the wrong Allwinner device ?

Are you made root ?

Hi. I have also the Xomax XM-2VA757. And a root would be nice. Or better a clean Android included root.
Because i have many problems. i have no GPS in Apps, but GPS is working, as i used GPS-test app.
And for all Apps location is allowed. Also no rights, to get Android system notifications to be allowed for Apps.
The build in Musicplayer is very, ...trash. And many more. my old 4.2.2 Android works much better as my new. and costs only 1/3 of the new Device.
So, if anyone has an Idea how to get all this work or how to root this Device..?!?
thx.
My Radio: look here

S*** no radio unit, no support, no answer. I am trying enter to recovery mode