Database Users

[Q] I have a problem with android phone please I want the solution

Hello to all members
I have a problem with android phone please I want the solution
I got phone Recovery error
Does not enter the Recovery but enters as in the pictures
I have worked a backup copy of a soft program( gscript and Install) There is also the root of the phone
My problem I do not know how to refer the backup I experimented more Flash_Tool program of issuing gives me error messages
Please you help me to return Recovery
Or give me Recovery is ready for carry it on the phone and memory card to be rate
Where after the piece that I can ride it from Rohm
This Android phone specifications
CPU: ARM cortex-A9
cores: 1
GPU Renderer: Power VR SGX 531
Model: A330(android_2xgb2))
board: android_2xgb2
Display:ALPS.GB2.MP.V2.4
Hardvare:mt6575
Android vers:4.0.3
Kernel Arch:armv7l
Kernel vers:2.6.35.7 (eng.linux-build1.1358392821)
Screen:320x480 240dpi
Total ram: 234MB
Avail.RAM:35MB
?nternal Strog:0,17MB
Root: yes
MPU3000 gyroscope sensor
AMI304 Orien..Sensör
AMI304-3axis magnetic fiel sensör

Android wear related .?

SM-T533 custom ROM + recovery

Hi,
I am the 'proud' owner of an SM-T533 Value Edition WiFi, specs: http://pdadb.net/index.php?m=specs&id=7941&c=samsung_sm-t533_galaxy_tab4_ve_10.1_lte-a
What I am looking for is a custom recovery for this thing. It has an Snapdragon 410 processor and is an update of the older Tab 4 10.1
Currently the latest official KitKat 4.4.4 is installed, rooted with Kingo Root.
Questions:
- is there a Cyanogen or Blisspop ROM available for this model? (preferably Bliss, because I have this on my Moto G and like it very much)
- if yes, can I flash it with Flashify if there is no TWRP/CWM available?
thanks
Hans

h,
it's a qcom/msm8916 device with a snapdragon 410,
it's likely you can use another sm-t53xx 's [lte] custom recovery without issue, twrp or philz/cwm.
keep hold of your firmware, and since you are rooted, dump a copy of stock recovery from your device to your pc
and package it for odin flashing jic.
your recovery partition would likely be mmcblk0p15, so in terminal run,
dd if=/dev/block/mmcblk0p15 of=/sdcard/stock-recovery.img
then pull it to your pc and package it for flashing through odin, [lookup instuctions].
then get a copy of twrp or philz for sm-t53x lte model and flash it through odin and see if it works out.
if good. then make a full backup of your rom via recovery and then give one of the lte rom releases a try.
m

moonbutt74 said:
h,
it's a qcom/msm8916 device with a snapdragon 410,
it's likely you can use another sm-t53xx 's [lte] custom recovery without issue, twrp or philz/cwm.
keep hold of your firmware, and since you are rooted, dump a copy of stock recovery from your device to your pc
and package it for odin flashing jic.
your recovery partition would likely be mmcblk0p15, so in terminal run,
dd if=/dev/block/mmcblk0p15 of=/sdcard/stock-recovery.img
then pull it to your pc and package it for flashing through odin, [lookup instuctions].
then get a copy of twrp or philz for sm-t53x lte model and flash it through odin and see if it works out.
if good. then make a full backup of your rom via recovery and then give one of the lte rom releases a try.
m
Click to expand...
Click to collapse
M,
You called? I pulled this from the SM-T533 5.1.1 build, XEO Region (Poland). Hope it suits your fancy (the tar is obviously in the zip)
https://www.androidfilehost.com/?fid=24269982086992814
T

moonbutt74 said:
h,
it's a qcom/msm8916 device with a snapdragon 410,
it's likely you can use another sm-t53xx 's [lte] custom recovery without issue, twrp or philz/cwm.
keep hold of your firmware, and since you are rooted, dump a copy of stock recovery from your device to your pc
and package it for odin flashing jic.
your recovery partition would likely be mmcblk0p15, so in terminal run,
dd if=/dev/block/mmcblk0p15 of=/sdcard/stock-recovery.img
then pull it to your pc and package it for flashing through odin, [lookup instuctions].
then get a copy of twrp or philz for sm-t53x lte model and flash it through odin and see if it works out.
if good. then make a full backup of your rom via recovery and then give one of the lte rom releases a try.
m
Click to expand...
Click to collapse
Hi moonbutt74, I downloaded the stock recovery and tomorrow I will try to flash TWRP/Philz
thanks a bunch
Hans

HausiX10 said:
Hi moonbutt74, I downloaded the stock recovery and tomorrow I will try to flash TWRP/Philz
thanks a bunch
Hans
Click to expand...
Click to collapse
- flashed "T533XXU1BOI3_T533OXA1BOI3" to get latest bootloader -> OK
- flashed "TWRP-2.8.7.0-SM-T5XX-150901_matisse_wifi_3g_lte" -> RECOVERY IS NOT SEANDROID ENFORCING
- flashed "cwm-recovery" -> RECOVERY IS NOT SEANDROID ENFORCING
so I'm back to square one (KitKat)
n.B. flashing the provided stock recovery results in a black screen :crying:

HausiX10 said:
- flashed "T533XXU1BOI3_T533OXA1BOI3" to get latest bootloader -> OK
- flashed "TWRP-2.8.7.0-SM-T5XX-150901_matisse_wifi_3g_lte" -> RECOVERY IS NOT SEANDROID ENFORCING
- flashed "cwm-recovery" -> RECOVERY IS NOT SEANDROID ENFORCING
so I'm back to square one (KitKat)
n.B. flashing the provided stock recovery results in a black screen :crying:
Click to expand...
Click to collapse
Sorry to hear about the stock recovery, I did what I always do. You can still fix it by flashing an Odin firmware
N.B. it says "recovery is not seandroid enforcing" even when the custom recovery is working properly, so that doesn't tell us anything. I assume you were trying to say TWRP didn't work

thisisapoorusernamechoice said:
Sorry to hear about the stock recovery, I did what I always do. You can still fix it by flashing an Odin firmware
N.B. it says "recovery is not seandroid enforcing" even when the custom recovery is working properly, so that doesn't tell us anything. I assume you were trying to say TWRP didn't work
Click to expand...
Click to collapse
correct, just the message and no recovery (TWRP|CWM) :crying:

HausiX10 said:
correct, just the message and no recovery (TWRP|CWM) :crying:
Click to expand...
Click to collapse
okay, that's what i wanted to know, display drivers in kernel, quit your whining by the way.
so i'll need to get hold of kernel source, oh joy.
i'll get back to this thread when i have a kernel compiled and tinker with the recovery image.
re-flash your stock recovery.
m

moonbutt74 said:
okay, that's what i wanted to know, display drivers in kernel, quit your whining by the way.
so i'll need to get hold of kernel source, oh joy.
i'll get back to this thread when i have a kernel compiled and tinker with the recovery image.
re-flash your stock recovery.
m
Click to expand...
Click to collapse
great, appreciate your effort

moonbutt74 said:
okay, that's what i wanted to know, display drivers in kernel, quit your whining by the way.
so i'll need to get hold of kernel source, oh joy.
i'll get back to this thread when i have a kernel compiled and tinker with the recovery image.
re-flash your stock recovery.
m
Click to expand...
Click to collapse
M,
Idk if this will help but I'm giving you the stock 5.1.1 boot.img (zipped and attached), I'm still working on getting the /system/lib/modules/ listing. Also, and idk if this is significant, but unlike all other Tab 4 models, the SM-T533 is 64 bit, google it if you don't believe me but I'm 95% confident on the veracity of that statement.

okay guys,
i am NOT finding a source for t533 ,
this model is sm-t533 ?
for now i'll take a spin with sm-t535 LL source release, the 64 bit thing is iffy though.
m

moonbutt74 said:
for now i'll take a spin with sm-t535 LL source release, the 64 bit thing is iffy though.
m
Click to expand...
Click to collapse
I know right? I can't even get the system.img.ext4 to play nicely, otherwise I'd have the /system/lib/modules/ listing for you. But this SM-T533 seems to be a real challenge. But if it's any help, yes, it's definitely 64 bit (DogBlamn, right??!)

thisisapoorusernamechoice said:
I know right? I can't even get the system.img.ext4 to play nicely, otherwise I'd have the /system/lib/modules/ listing for you. But this SM-T533 seems to be a real challenge. But if it's any help, yes, it's definitely 64 bit (DogBlamn, right??!)
Click to expand...
Click to collapse
T,
is anything in the firmware, to identify the display? also H, download and install cpuz from playstore and post all the info it spits out.
m

thisisapoorusernamechoice said:
M,
Idk if this will help but I'm giving you the stock 5.1.1 boot.img (zipped and attached), I'm still working on getting the /system/lib/modules/ listing. Also, and idk if this is significant, but unlike all other Tab 4 models, the SM-T533 is 64 bit, google it if you don't believe me but I'm 95% confident on the veracity of that statement.
Click to expand...
Click to collapse
@this...
it is 100% 64Bit as per the specs I linked in my firts post
keep going guys and thanks
Hans

HausiX10 said:
@this...
it is 100% 64Bit as per the specs I linked in my firts post
keep going guys and thanks
Hans
Click to expand...
Click to collapse
M, here comes CPUZ stuff, if need more or different, just say...

moonbutt74 said:
T,
is anything in the firmware, to identify the display? also H, download and install cpuz from playstore and post all the info it spits out.
m
Click to expand...
Click to collapse
M,
Sorry , I'm always running (at least) one step behind you. I got the listing of the /system/lib/modules folder, also zipped and attached below. I'm going to go through the system folder (and then take a look at the other images in the tar if that doesn't work) to see if I can find anything about the display.
/system/lib/modules/ listing:
A folder named pronto (so /system/lib/pronto/) with a single file, pronto_wlan.ko
ansi_cprng.ko
core_ctl.ko
dma_test.ko
evbug.ko
gator.ko
mmc_block_test.ko
mmc_test.ko
msm-buspm-dev.ko
oprofile.ko
radio-iris-transport.ko
spidev.ko
tcp-htcp.ko
tcp_westwood.ko
test-iosched.ko
UPDATE: I know this isn't what you're asking for but these lines in the build.prop seemed interesting enough to mention:
Code:
ro.product.device=matissevewifi
ro.product.board=MSM8916
ro.chipname=APQ8016
ANOTHER UPDATE @moonbutt74, am I annoying you yet? :silly: I opened a couple files (/system/usr/idc/Synaptics_RMI4_TouchPad_Sensor.idc and /system/usr/idc/Synaptics_RMI4_TouchPad.idc) and they both talk about "Atmel Maxtouch touch screen", is this what you were looking for? I'm going to keep combing the system folder to be thorough. And screw it, I'm going to zip and attach those two files, since why the hell not?

for reference
CPU-Z for Android Report - 1.15
CPUs : 4
SoCs : 1
CPU 0 : ARMv7 Processor rev 0 (v7l)
Name : Qualcomm Snapdragon 400/410
CPUs : 4
Core set 0 : ARM Cortex-A53
Core set 0 Nb Cores : 4
Core set 0 Max Clock : 1190 MHz
Core set 0 Impl.id : 0x41
Core set 0 Arch.id : 0x7
Core set 0 Var.id : 0
Core set 0 Part.id : 0xd03
Core set 0 Rev.id : 0
Core set 0 Revision : r0p0
Arch : 4x ARM Cortex-A53 @1.19 GHz
Codename :
Process : 28 nm
GPU Vendor : Qualcomm
GPU Renderer : Adreno (TM) 306
Model : SM-T533 (matissevewifixx)
Manufacturer : samsung
Board : MSM8916
Hardware : qcom
Android Ver. : 4.4.4
Kernel Arch. : armv7l
Battery capacity : 6800
--- CPUInfos ---
abi : armeabi-v7a
abi2 : armeabi
processor : 0
model name : ARMv7 Processor rev 0 (v7l)
BogoMIPS : 38.40
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 0
processor : 1
model name : ARMv7 Processor rev 0 (v7l)
BogoMIPS : 38.40
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 0
processor : 2
model name : ARMv7 Processor rev 0 (v7l)
BogoMIPS : 38.40
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 0
processor : 3
model name : ARMv7 Processor rev 0 (v7l)
BogoMIPS : 38.40
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 0
Hardware : Qualcomm Technologies, Inc APQ8016
Revision : 0002
Serial : b38cd6490de57cef
Processor : ARMv7 Processor rev 0 (v7l)
--- Debug Infos ---
4=400000000
5= 0 1028763655
8=400000000 310000000 200000000
15=-1
20=tsens_tz_sensor0=39
21=tsens_tz_sensor1=36
22=tsens_tz_sensor2=34
23=tsens_tz_sensor4=36
24=tsens_tz_sensor5=37
25=pm8916_tz=29345
26=pa_therm0=10
27=stc3117-fuelgauge=-4000
28=battery=27400
51=tsens_tz_sensor0=39
52=tsens_tz_sensor1=36
53=tsens_tz_sensor2=34
54=tsens_tz_sensor4=36
55=tsens_tz_sensor5=37
56=pm8916_tz=29345
57=pa_therm0=10
58=stc3117-fuelgauge=-4000
59=battery=27400
clock0=1190400
clock1=-1
clock2=-1
clock3=-1
i am guessing this is the panel -- samsung_panel_init : ss_dsi_panel_TC358764_LTL101A106_WXGA

HausiX10 said:
M, here comes CPUZ stuff, if need more or different, just say...
Click to expand...
Click to collapse
H,
can you run uname -a in terminal or give me a screenshot of the tab in your settings that shows kernel version information?
also can you run the following command,
ls -al /proc/config.gz
if it comes back with an actual listing of that file, i need it, if so then run
cp /proc/config.gz /sdcard/config.gz and attach that to your post.
@sub77 has resources for a twrp build for matissevewifi using prebuilt kernel,
https://github.com/GalaxyTab4/twrp_device_samsung_matisseve/blob/twrp-cm12/BoardConfig.mk
if he has a build of twrp available for your tab then
that would be the way to go.
i did stumble onto this source for a kernel https://github.com/MSM8916-Samsung/android_kernel_samsung_e53g
it has dts's for your device,
Code:
/dts-v1/;
#include "msm8916-sec-matissevewifi-eur-r00.dtsi"
#include "msm8916-memory.dtsi"
so once my internet gets fixed maybe i'll be able to clone that and get something working.

from uname -a:
Linux localhost 3.10.28-4271302 #1 SMP PREEMPT Wed Jul 8 14:21:44 KST 2015 armv7l GNU/Linux
there is no config.gz in the kernel
btw I tried the twrps from sub77, but none would install/display
hans

HausiX10 said:
from uname -a:
Linux localhost 3.10.28-4271302 #1 SMP PREEMPT Wed Jul 8 14:21:44 KST 2015 armv7l GNU/Linux
there is no config.gz in the kernel
btw I tried the twrps from sub77, but none would install/display
hans
Click to expand...
Click to collapse
sub & moon,
copied a few logfiles from cache/recovery, maybe that helps ...
hans

Allwinner R16 (astar_d7) Android 6.0.1 Marshmallow - Partition Dump & Information

Please note that I gave up on this unit (MTCD PX5 units are so much nicer...). I will try to update this post (however infrequently) with information that may appear in this thread or come my way by other means, but I will not seek information actively and updates will no longer be from my own experience or experiments.
At the time of writing this head unit is available here and (probably) here. These are both custom fit for Kia Sorento, but other versions do exist; in particular several EONON units feature the same hardware configuration (model numbers GA2160, GA7153 GA7163, and I am sure others).
Hardware-wise this seems to be the same unit as described in this thread so many tricks therein will work for this unit. In particular the USB debugging password continues to be "[email protected]" (without quotes); the extra settings password is most likely either 123456 or 668811; the factory reset and developer options passwords appear to be both 7890.
In all the unit is an Allwinner quad core R16, with the MCU version 5.3.19-16-10-650101-161115 and System version V7.3.1-2016-11-12.100233_TW2. Here is the Droid Info report:
Code:
DEVICE
Model: QuadCore-R16 (astar_d7)
Manufacturer: Allwinner
Baseband Version: Not Available
RIL Version: sw-dataonly-ril-for-6.0_v1.0
Build Number: astar_d7-eng 6.0.1 MOB30R 20161112 test-keys
Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20161112:eng/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0.1)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 5 (v7l)
Board: exdroid
Chipset: sun8i
Cores: 4
Clock Speed: 480 MHz - 1200 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: Not Available
Kernel Version: 3.4.39
Kernel Architecture: armv7l
GRAPHICS
Renderer: Mali-400 MP
Vendor: ARM
OpenGL Version: OpenGL ES 2.0
RAM
Total: 986 MB
Java Heap: 80 MB
STORAGE
Internal: 12 GB
EXTERNAL: Not Detected
Software-wise the unit comes with a fairly stock version of Marshmallow, though as usual the operating system is a bit locked down (but to my surprise not too locked down) compared to stock.
The purpose of this thread is to gather information about the software and possible customization for these units. I have added the information I gathered from my experience and I will update this post with any new information I manage to obtain.
1. Partition dump
For reference I dumped all the partitions of my device. The dump is available here. The dump was done by name (for those partitions that have a name) and symlinks point to the device name from /dev/block. Feel free to share (credit appreciated but not necessary) and please share any information that you gather from it (which will be included in this section as it becomes available).
2. Flashing firmware
There are multiple ways of flashing new firmware, depending on the actual unit and also its state (working, bootloop, etc.). All methods require that the all the files (three to six) that contain said firmware (see next section) be placed in the root of a SD card formatted FAT32 and inserted in the GPS slot of the unit. Some reports of the firmware being flashed from a USB stick rather than the SD card also exist; they also mention that choosing one USB port over another might make the difference between success and failure.
On a working system inserting the card and/or USB stick and choosing "update system" from preferences will likely do the trick.
On a system that is not working the following methods have been reported:
Hold Home, press Reset, and keep holding Home until the update starts (thanks).
A hardware solution is to short Key 1 (steering wheel controls) to ground, then press and hold Reset for 10 seconds; release Reset and disconnect Key 1 when "update" is displayed (thanks).
Yet another procedure might be needed for some units (thanks): Using a USB stick prepared as above and inserted in the unit, turn ignition to ACC, press Reset, turn ignition off, then after 5 seconds turn it again to ACC. A video is also available.
3. Flashable firmware
All the reports I have seen indicate that all the firmware versions are interchangeable. However, a factory reset will be needed most of the time for full functionality, especially so when installing firmware from a different vendor. It is VERY important however to note that the file bd07a5ee-fbb0-11e4-ae78-000c29ba27c0 contains the MCU firmware and so SHOULD NOT be flashed on incompatible devices as doing so will brick the unit (thanks).
Partition 11 of the above dump in particular stores a flashable image. It contains the following files:
81cb828c-9b57-11e6-ad2a-df6786178d62
827ba428-9b57-11e6-8dfb-37398ea70e52.0
827ba428-9b57-11e6-8dfb-37398ea70e52.1
bd07a5ee-fbb0-11e4-ae78-000c29ba27c0
The files 827ba428-9b57-11e6-8dfb-37398ea70e52.* in particular when cat-ed together form an ext4 file system that appear to be a copy of the system partition. This 4pda forum thread contain more information (thanks @Ahfish22); I do not speak Russian at all but Google Translate does a good job most of the time.
Since I started this thread many people have posted many firmware versions. Here is a hopefully complete list. There might be duplicates and misses and I apologize for both in advance.
The following set of firmware (in particular V7.3.1_20170610.110122_KED1 therein) come recommended by several users (thanks).
EONON firmware:
GA2162_KBT2_20170309 (thanks)
V7.3.1_20170114.111256_KBT2 (thanks)
EONON-R16-20170509 (thanks)
EONON-R16-KLD20170515
V7.3.1_20170427.104257_KBT2 (thanks)
EONON-R16-KLD20170515 (thanks)
KED1 (MEDEKE?) firmware (thanks):
V7.3.1_20170216.180104_KED1
V7.3.1_20170720.152039_KED1
TW2 (TopWinner?) firmware (thanks):
V7.3.1_20170111.114952_TW2-IVT+ROOT+RADIO
V7.3.1_20161229.175327_TW2
V7.3.1_20161201.154419_TW2
TH6 firmware (thanks): V7.3.1_20161129.194710_TH6
JYZC1 (Joying?) firmware (thanks):V7.3.1_20170317.114203_JYZC1
Kaier firmware (thanks)
Rooted KLD (Klyde) firmware (thanks):V7.3.1_20170512.203736_KLD1-0-1-mod
4. Recovery
Mot units do have a working recovery partition, though some are reported not to have such. The command "reboot recovery" at a root prompt (terminal emulator or ADB) will enter recovery (if available).
Alternatively recovery can be reached with an external USB keyboard as follows: While holding Alt and Print Screen keep tapping i; the system will eventually restart in recovery (thanks pir8man) .
It should be noted that despite the on-screen instructions the stock recovery does not react to any buttons on the head unit, but works well with an external USB keyboard.
5. Customization
There are useful tweaks that come with the stock operating system including speed-dependent volume and (apparently, I have not tested exhaustively) the elimination of the full-screen keyboard.
I found this alternative to the stock radio app (context, source code) which is pretty nice except that the app force closes upon attempting to enter settings. If you speak Russian it may be worth discussing this with the developer.
Root: Kingoroot works, though several attempts (reboot and try again) may be needed. Note that a reliable Internet connection is needed during the whole process. I do not like the extra apps and intrusive ads that come with Kingoroot. I therefore recommend once rooted to install Chainfire's SUperSU, let it update the su binary, and then uninstall Kingoroot. Note however that the current Play Store SuperSU (namely, version 2.82) may not be able to overwrite Kingoroot's su (saying instead that "the su binary is occupied"). If this is the case you may want to try version 2.79 (downloadable from here) which is known to work. Once the Kingoroot's su binary is overwritten you can upgrade to the latest (Play Store) SuperSU.
Busybox: Installed without incidents using the usual installer from the Play Store.
Xposed: Installed using the Xposed installer v. 3.1.1 and works well. I tried Gravity Box and Xprivacy.
6. Outstanding issues
It should be possible to redefine the default apps for music, video, and radio but I did not find any way to do it.
Mapping SWC and front button panel events works to some degree (for testing purposes I mapped the "Band" button to the app drawer), but this seems to be exclusively at the mercy of the MCU, which only allows mapping to predefined actions. I could find no way to map these events to custom actions on the OS side. It was reported that button events are communicated to the OS as long as no MCU app is running. However, I was unable to reproduce this; for me no event is ever seen by the OS no matter how many (or how few) apps are running. I stopped all the MCU apps but even so KeyTest does not register any event.
Needless to say, no custom recovery (such as TWRP) exist for these units.

So if the hardware is the same as the other 4.4.2 units then can we update our old units to 6.0?

Can you share me the content of /sbin directory?

sambacha said:
So if the hardware is the same as the other 4.4.2 units then can we update our old units to 6.0?
Click to expand...
Click to collapse
If the hardware matches then I do not see why not. In addition to dd-ing the system and boot partitions of my dump (which you are welcome to try) please see my last edits of the first post for possible flashable firmware being available.
Just make sure that you have a (tested) way to get back if things do not work...

mrtnb said:
Can you share me the content of /sbin directory?
Click to expand...
Click to collapse
See attached.

Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!

Alternative to the stock radio -- help needed
I found this alternative radio app (reference, source code). It works well but I am unable to set preferences as the app force closes on selecting the setting menu item.
I would ask the developer, except that I do not speak Russian. I was wondering if any Russian speaker around here could inquire about the issue. I have also downloaded the sources and I am poking around but I am not holding my breath until I find a solution (I am a coder but not an Android developer). Many thanks in advance!

sambacha said:
Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!
Click to expand...
Click to collapse
Can you share your experience and the russian thread's link?

sambacha said:
Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!
Click to expand...
Click to collapse
Can you give us a link?
---------- Post added at 07:40 AM ---------- Previous post was at 07:21 AM ----------
can I flash this over Android 4.4?
This is my unit:
Android 4.4.2 Operation System
CPU Processor: Allwinner R16 Cortex A9 Quad-core 1.6GHz
RAM Memory: Samsung DDR3 1GB/16GB

I just installed an EONON GA2162. Link
Which appears to be a clone of the same..
MCU version: 5.3.19-108-10-943101-170114
System version: V7.3.1_20170114.111256_KBT2
Code:
DEVICE
Model: QuadCore-R16 (astar_d7)
Manufacturer: Allwinner
Baseband Version: Not Available
RIL Version: sw-dataonly-ril-for-6.0_v1.0
Build Number: astar_d7-eng 6.0.1 MOB30R 20170112 test-keys
Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20170112:eng/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0.1)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 5 (v7l)
Board: exdroid
Chipset: sun8i
Cores: 4
Clock Speed: 480 MHz - 1200 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: Not Available
Kernel Version: 3.4.39
Kernel Architecture: armv7l
GRAPHICS
Renderer: Mali-400 MP
Vendor: ARM
OpenGL Version: OpenGL ES 2.0
RAM
Total: 836 MB
Java Heap: 80 MB
STORAGE
Internal: 12 GB
EXTERNAL: Not Detected
I can dump the rom if anyone desires.

sbruda said:
[*]It would be great if long press events (SWC and/or front panel buttons) can be used. Some hints in various threads suggest that this is possible with these units but I found no way to do it. Advice is once more much appreciated.
Click to expand...
Click to collapse
Hi, I recently bought one of these for a Ford Mondeo and I somehow have figured about using keypress events.
The problem doesn't lie in the unit itself, but the damn apps it has.
I have been two entire days staring at Extreme Logcat screen and button event but no go, but, suddently, key event started registering next, prev and play/pause.
GREAT, I thought, and I started configuring Xposed Additions to start some audio visualizers in some buttons but when I started the music app, it stopped registering the events. It closed that app and those events where working again. Tried powerAmp and everything works like a charm. Menu and back keystrokes can also be mapped while the on-screen button still do the default action, so:
- It seems like the built-in apps capture those events and prevent anyone (tasker, Xposed Additions) to use them.
- MP3 and video player can be replaced pretty easyly but radio and specially bluetooth manager (Which has a whooping 12 keys that can be customized (0-9, # and *)) cannot be replaced.
- Decompiling the app, and disabling those captures could be the solution to use all those keystrokes OR finding some way to block those apps from capturing those events.
If I get something new I'll post asap.
Hope this helps.

pir8man said:
I just installed an EONON GA2162. Link
Which appears to be a clone of the same..
MCU version: 5.3.19-108-10-943101-170114
System version: V7.3.1_20170114.111256_KBT2
Code:
DEVICE
Model: QuadCore-R16 (astar_d7)
Manufacturer: Allwinner
Baseband Version: Not Available
RIL Version: sw-dataonly-ril-for-6.0_v1.0
Build Number: astar_d7-eng 6.0.1 MOB30R 20170112 test-keys
Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20170112:eng/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0.1)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 5 (v7l)
Board: exdroid
Chipset: sun8i
Cores: 4
Clock Speed: 480 MHz - 1200 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: Not Available
Kernel Version: 3.4.39
Kernel Architecture: armv7l
GRAPHICS
Renderer: Mali-400 MP
Vendor: ARM
OpenGL Version: OpenGL ES 2.0
RAM
Total: 836 MB
Java Heap: 80 MB
STORAGE
Internal: 12 GB
EXTERNAL: Not Detected
I can dump the rom if anyone desires.
Click to expand...
Click to collapse
could you please upload this rom for us
thanks man

me sumo al pedido
Saludos !
no se si alguien puede pero estaría bueno que puedan subir los packs de actualización. para R16 en la resolucion 1024*600
por ejemplo estos son los Nombres de los archivos que hacen falta...
tambien especificar el android si es 4.4 o 5.1 o 6.0
bd07a5ee-fbb0-11e4-ae78-000c29ba27c0
90436790-1e25-11e5-9b35-000c29ba27c0
91973a18-1e25-11e5-b937-000c29ba27c0
92e82e86-1e25-11e5-bffa-000c29ba27c0

khalwd said:
could you please upload this rom for us
thanks man
Click to expand...
Click to collapse
Hi,
(my first post):laugh:
I would also like to have a copy of this ROM.
I have the same Droid report.
Being someone that cant leave things alone i have somehow corrupted my unit.
I rooted with Kingoroot and all worked well. Uploaded a recovery to the cloud, all good.
Decided to down load back to the unit. Wife moves car and interrupts download.
Now when i boot up all i get is the car logo and the android screen, this is where it stops.
Tried installing various updates, They seem to install. Progress bar for abut 5 min shows update end
then boots to the car logo Android screen and stops.
Cheers

Hi,
pirulazul said:
Hi, I recently bought one of these for a Ford Mondeo and I somehow have figured about using keypress events.
The problem doesn't lie in the unit itself, but the damn apps it has.
I have been two entire days staring at Extreme Logcat screen and button event but no go, but, suddently, key event started registering next, prev and play/pause.
GREAT, I thought, and I started configuring Xposed Additions to start some audio visualizers in some buttons but when I started the music app, it stopped registering the events. It closed that app and those events where working again. Tried powerAmp and everything works like a charm. Menu and back keystrokes can also be mapped while the on-screen button still do the default action, so:
Click to expand...
Click to collapse
Thank you for the report. I tried the same (stop all system apps) but even so KeyTest does not register any event. This was done for the panel buttons since I do not have yet any SWC (the unit is on the bench), which may or may not be the cause of my failure.
pirulazul said:
- It seems like the built-in apps capture those events and prevent anyone (tasker, Xposed Additions) to use them.
- MP3 and video player can be replaced pretty easyly but radio and specially bluetooth manager (Which has a whooping 12 keys that can be customized (0-9, # and *)) cannot be replaced.
Click to expand...
Click to collapse
Have you found any way to replace the default association for these apps? By default the "Mode" action cycles through the default apps, did you find any way to convince this action to cycle through some other (custom) rotation?
pirulazul said:
- Decompiling the app, and disabling those captures could be the solution to use all those keystrokes OR finding some way to block those apps from capturing those events.
Click to expand...
Click to collapse
I'll try to look into this, but at this time I cannot promise any timeline.
Cheers!

would one of my units be similar to yours?
i received a newer firmware from the chinese (build 29.12) as a ZIP which contains the 4 files as above, but i can't update it since i get a signature error (seen below). In the meantime i managed to **** up the screen by accidentally switching to 800x480 and now i can't see anything useful on the display...

zerozoneice said:
would one of my units be similar to yours?
Click to expand...
Click to collapse
Looks pretty much the same as mine (with a slightly newer firmware though).
zerozoneice said:
i received a newer firmware from the chinese (build 29.12) as a ZIP which contains the 4 files as above, but i can't update it since i get a signature error (seen below). In the meantime i managed to **** up the screen by accidentally switching to 800x480 and now i can't see anything useful on the display...
Click to expand...
Click to collapse
Most (all?) Chinese vendors know absolutely nothing about the units they sell so it is quite possible to have the wrong firmware. This, or the file got corrupted during transfer somehow. Have you tried my firmware blob or the others that float around? The probability that it will work look decent and what have you gotta loose?
You can also try to restore the resolution by trial and error (touching the screen where things should be). A couple of success stories have been posted in this thread though the process looks painful...

there are couple of FWs around, i saw them on 4PDA as well. The latest is february, something. The problem is that the ZIP file has the 4 files you listed above, instead of an IMG file. Shouldn't IMG be the default ROM update? I mean even PowerSuit recognizes only IMGs, that is if i manage to connect to the damn box somehow.
I tried TV out, hoping the signal is ****ed only from the mainboard to the screen and it would manage to display it on another external screen, but....there is no TV out. Didn't work with the cables provided.
Trial & error...i would need to see another menu next to me in order to see where the hell i'm pressing on my screen
Resolution change is the first menu, but is hidden in the extra settings, behind a password which i'd also need to enter....blindly.
Did you manage to install any of the 4PDA firmwares properly on yours? Try the December 29th one, this is the one that Infidini sent me....
LE: LOL, i just read the following passage from the thread you posted above:
"What is the Extra Settings password?
Resolved: 123456
Note: Do NOT change the resolution of the head unit. You will destroy your unit. However it is reversible."
Post 807: another quickfinger like me, changed the res. the other way around, from 800 to 1200, but he still sees something....
https://forum.xda-developers.com/showpost.php?p=70762889&postcount=807
Post 747: same problem as me.
https://forum.xda-developers.com/showpost.php?p=70047172&postcount=747
How can i flash this damn unit? How can we connect to it?
@sbruda: i have an idea. Can you please post screenshots of the menu, from the main menu screen all the way to the extra settings, where u enter the password and then the "change resolution" menu option? It can help me to figure my fingers around the screen blindly... THX!
---------- Post added at 04:43 PM ---------- Previous post was at 04:15 PM ----------
HERE is the link to the FW that infidini support provided me.

zerozoneice said:
there are couple of FWs around, i saw them on 4PDA as well. The latest is february, something. The problem is that the ZIP file has the 4 files you listed above, instead of an IMG file. Shouldn't IMG be the default ROM update? I mean even PowerSuit recognizes only IMGs, that is if i manage to connect to the damn box somehow.
Click to expand...
Click to collapse
I believe that the four files can be used directly to upgrade, at least this is what people have reported (I have never tried to upgrade myself). This also makes sense given that a restore to factory from the (Android) menu will presumably use the partition with those files.
zerozoneice said:
I tried TV out, hoping the signal is ****ed only from the mainboard to the screen and it would manage to display it on another external screen, but....there is no TV out. Didn't work with the cables provided.
Click to expand...
Click to collapse
It would appear that TV out only works for the DVD.
zerozoneice said:
Did you manage to install any of the 4PDA firmwares properly on yours? Try the December 29th one, this is the one that Infidini sent me....
Click to expand...
Click to collapse
No, I meant to but I am really pressed for time nowadays so I have no idea when will I get to it.
zerozoneice said:
@sbruda: i have an idea. Can you please post screenshots of the menu, from the main menu screen all the way to the extra settings, where u enter the password and then the "change resolution" menu option? It can help me to figure my fingers around the screen blindly...
Click to expand...
Click to collapse
Here they are. Sorry for the crappy photos but I have no idea how to take screenshots on this unit (please advise):
1-main.jpg - main screen
2-notif.jpg - notifications pulled down (two times)
3-settings-scrolled.jpg - the settings app scrolled all the way down
4-car-settings-scrolled.jpg - the Car settings screen scrolled all the way down
5-settings-pass.jpg - the password entry box and keyboard (I would advise the use of a USB keyboard instead though)
6-extra-settings.jpg - the Extra setting screen
7-resolution.jpg - the resolution dialogue
I hope this helps. If somebody can advise on how to take screenshots I will come back with better quality photos.

sbruda said:
1-main.jpg - main screen
2-notif.jpg - notifications pulled down (two times)
3-settings-scrolled.jpg - the settings app scrolled all the way down
4-car-settings-scrolled.jpg - the Car settings screen scrolled all the way down
5-settings-pass.jpg - the password entry box and keyboard (I would advise the use of a USB keyboard instead though)
6-extra-settings.jpg - the Extra setting screen
7-resolution.jpg - the resolution dialogue
I hope this helps. If somebody can advise on how to take screenshots I will come back with better quality photos.
Click to expand...
Click to collapse
thx, they're good enough. using phone is fine. afaik password for that extras in my case is 123456 and restore to factory settings 7890
i will try tomorrow.
---------- Post added at 07:32 PM ---------- Previous post was at 07:01 PM ----------
How do you power on the thing when not connected in the car???

Eonon GA2175

Hello everyone.
For my first post here I'd like to share and learn more about rooting the EONON GA2175. This Android HU currently operating with Oreo on a RK3326_mid chipset. So after an exhaustive search, there is not much information available in rooting this system. It seems that's this HU seems to be almost completely locked down. For starters, I wasn't able to even access developer mode through the build number as usual. I was finally able to get through by installing a developer access app called "Developer Options Shortcut & Device Info" on the app store.
Using one click apps like Kingo Root, Root Master or Towel Root are completely ineffective. As a matter of fact, Root Master says my "phone is too strong"
I tried connecting the unit to a laptop by using a male to male USB cable. But both my laptop of the HU do not recognize each other. Maybe some drivers may help but none are available.
I've watched you tube videos that demonstrating other people rooting similar units by accessing the safe boot option then loading TWRP on a SD card. I believe this is the only way to root these units. However, for this unit I am unable to access safe mode. I've discovered that holding the "Vol/PWR" knob for approximately 10 sec will cause it to start blinking but combinations with the "RST" button, home or quick pressing the "PWR" doesn't work. That's as far as I got.
I hope this helps anyone with the same unit but any help with my roadblock will be greatly appreciated.
Thanx!

UPDATE
So I finally managed to get to recovery mode on this device.
1. With a tooth pick, quick press the "RST" button.
2. Long press the "PWR/VOL" knob for approximately 10secs until the lights blink.
3. Then immediately quick press the "PWR/VOL"
You may need to do it more than once but it'll work.
Well.... now what TWRP version should I use?
I didn't see my HU listed.
Or should I use a different program?

did you end up getting something to work?
Mark

Not yet.
I did manage to find some unit specifics. I'll post them shortly. Maybe some coder can do something with that info. Where I run into a roadblock is that I cannot find a suitable ROM and MCU.

If this help to figure things out.
BOARD : rk30sdk
SERIAL : 77A6117127A8F7B2
eng.hct.20181229.163118
eng.hct.20181229.163118
DEVICE: rk3326_mid
HOST : r930
MODEL : rk3326_mid
RELEASE : 8.1.0
MANUFACTURER: rockchip
USER : hct
BUILD NUMBER: PX30 8.1.0 OPM8.181105.002 eng.hct.20181229.163118
CPU_ABI: arm64-v8a ; Quad-Core [email protected]
MEMORY: 1960MB
BRAND : rockchip
SDK_INT: 27
DISPLAY : rk3326_mid-userdebug 8.1.0 OPM8.181105.002 eng.hct.20181229.163118 test-keys
FINGERPRINT: rockchip/rk3326_mid/rk3326_mid:8.1.0/OPM8.181105.002/hct12291631:userdebug/test-keys
HARDWARE: rk30board
PRODUCT : rk3326_mid
BOOTLOADER : unknown
REL: REL
ID: OPM8.181105.002
UNKNOWN: unknown
TYPE : userdebug
TAGS : test-keys
MCU VERSION: MTCE_HT_V2.99_1
November 18, 2018 19:03:43

Root Path info
Root Access:
No Access
SU:
su found
UID/GID:
uid=10105(u0_a105) gid=10105(u0_a105) groups=10105(u0_a105),3003(inet),9997(everybody),20105(u0_a105_cache),50105(all_a105) context=u:r:untrusted_app:s0:c512,c768
Utils:
busybox
toybox
toolbox
Path:
/sbin
/system/sbin
/system/bin
/system/xbin
/vendor/bin
/vendor/xbin
Path:
[/system/xbin/su]
Version:
/system/bin/sh: <stdin>[16]: /system/xbin/su: can't execute: Permission denied
Permissions:
rwsr-x---
Owner:
root:shell
SELinux:
Permissive
Path:
[/system/bin/busybox]
Permissions:
rwxr-xr-x
Owner:
root:shell

Get any further with this, wouldn't mind a custom ROM for mine although i'm pretty happy how it works now.

Actually yes!! Type "ADBON" in factory setting password to access developer options. It works. Thanks Ric69!

Blaupunkt Santa Rosa 980 || Android 9 head unit || Custom ROM/Root Access/Custom Recovery || Help needed

Hi,
I am looking for some help in troubleshooting my android car head unit. I’ve been using the Blaupunkt Santa Rosa 980 (9-inch variant) for over a month now. The system on its own is good – fast, responsive. But the manufacturer has limited a lot of settings and features, which makes it difficult to customize and use.
Product Link: https://blaupunkt.com/c_ind/product/santa-rosa-980-9-inch/
My issues with the system:
I use Nova launcher, as I love the interface. But every time the system reboots, the Accessibility settings for it get disabled. I have to enable them each time.
No option to enable Developer settings. Somehow, the Android settings for me like About car/Device, Build number are hidden.
I’ve tried a dozen shortcut apps available on Play Store, none work. They all ask for developer settings to be enabled first. Have also tried via the activity launcher shortcut/widget in Nova, with no luck.
The Status/Notification bar (and the overall UI) is ugly. Default one would have been nice.
While playing videos on installed apps like MX Player or VLC, the respective application simply hangs after few minutes of playback. No media works unless I reboot the system.
What I’m looking for:
A good, stable custom ROM for this system.
Alternatively, I am looking to root the system – in hopes of gaining access to hidden Android settings/developer options.
I’ve tried rooting via KingoRoot, but no luck again. Also, the system does not get detected by my laptop as USB debugging cannot be enabled (without enabling developer options I don’t know to do it).
However, I have been able to get into recovery mode via Terminal Emulator app.
Custom recovery option for this system (TWRP) - as I'm hoping it can help install root access/SU in my case.
Any leads/inputs/suggestions will be really helpful.
System Specifications (CPU-Z):
CPU-Z VALIDATOR
CPU-Z VALIDATOR is the world-recognized standard for system analysis & performance validation
valid.x86.fr
Device:
Manufacturer: Alps
Model ID: ac8257_demo
Android Version: 9
Kernel Version: 4.9.117+
Battery Capacity: 1000 mAh
SoC (Processor):
Architecture: arm64-v8 (aarch64)
SoC Model: ARM Cortex-A53
SoC Family: 4x ARM Cortex-A53 @2.00 GHz
Frequency: 1633 MHz / Min: 850 MHz - Max: 2001 MHz
Main CPU Cores: 4 Cores / 4 Threads
CPUID: 41.0.8.D03.4
Revision: R0P4
Features: FP ASIMD EVTSTRM AES PMULL SHA1 SHA2 CRC32
Bogomips: 26.00 MIPS
Display (GPU / LCD):
SoC Manufacturer: Imagination Technologies
SoC Model: PowerVR Rogue GE8300
OpenGL Ver.: 3.2
LCD Size: 7.4 inches / 18.8 cm
LCD Resolution: 1024 x 600 pixels
LCD Definition: 160 DPI
Memory:
RAM: 3856 MB (4 GB)
Flash: 23484 MB
Though this is branded as Blaupunkt in India, I suspect its just another rebranded Chinese unit. Attaching some screenshots for reference.

Update - managed to get root with Magisk. Had to patch my stock boot.img and flash.

Hello, I have a San Pedro 900 model radio, which was working very well, but over time the applications began to stop working due to the android version and I found an update on the official page, I tried to install everything well and suddenly I returned an error and got black screen.
Do you happen to know how to reinstall the original system?
Product Link: https://blaupunkt.com/c_la/producto/san-pedro-900/

SP Flash Tools + ADB

idkc said:
Hello, I have a San Pedro 900 model radio, which was working very well, but over time the applications began to stop working due to the android version and I found an update on the official page, I tried to install everything well and suddenly I returned an error and got black screen.
Do you happen to know how to reinstall the original system?
Product Link: https://blaupunkt.com/c_la/producto/san-pedro-900/
Click to expand...
Click to collapse
Hi.
You will need the original installation files for your system. Blaupunkt or your service center should be able to provide you with that. I had bricked my system too. Installation is easy if you have the OS/setup files, drivers and a laptop with adb and SP Flash tool.

Hello sir i have
Bluapunk Santa rosa 980 9”
Feature by any change
Android auto carplay possible or not
Wired/wireless

Hello sir i have
Bluapunk Santa rosa 980 9”
Feature by any change
Android auto carplay possible or not
Wired/wireless