Database Users

[WIP] Open Bootloader Development for Archos Gen8

Hey geeks,
you might know my hardware hacking thread already:
http://forum.xda-developers.com/showthread.php?t=1199450
Some time ago i started thinking about starting with an open bootloader for Archos Gen8.
So i started from scratch and made use of external boot mode to completely start from external MicroSD and leave the internal memory alone.
Remark: This is a geek project, there's no GUI or something. So don't expect anything useful right now.
At the moment you'll need some hardware hacking, because you'll need a serial console over uart3.
Unfortunately you'll also need a dirty hack to power up the MicroSD permanently.
Don't hesitate to ask for details about it.
So this is for the weird ones out there...
Right now there's work in progress, because stock kernel stucks at some point in the boot process.
Maybe there's some setup missing in the bootcode (it's very basic at the moment) or stock kernel relies heavily on avboot at some point.
I will work on this issue whenever i'll find some time.
Anyway it might be still an interesting project for at least a very few of you, so here's the source code:
- x-loader-archos
- u-boot-2011.09-archos
As pointed out the Archos implementation is very basic at the moment, but the code itself works very well and had been tested on A101IT Gen8.
To further devices, e.g. A70S Gen8, the machine id had to be included in the board file, the rest of the setup in early stage should be very similar.
The code bases:
- x-loader (https://gitorious.org/x-loader/x-loader)
- u-boot (taken from this archive: http://www.technexion.com/images/downloads/ARM_CPU_Modules/TDM-3730/linux-2.6.32-tdm3730.tar.xz)
I'd like to switch to official u-boot release 2011.09 as a base soon.
To start playing with it:
- open your case and start hacking, to get serial console working
- tweak the hardware to power the MicroSD slot permanently
- create a bootable MicroSD for OMAP systems
- place the binaries on your card
- insert the card and use vitalifs kernel module to reboot your device in external bootmode
Please refer to these posts from vitalif (thanks a lot for contributing!!!):
http://forum.xda-developers.com/showpost.php?p=22719203&postcount=105
http://forum.xda-developers.com/showpost.php?p=22765441&postcount=108
You might start digging in the source code and create your own loader:
- use a linux machine with a recent distribution
- setup a cross environment with ARM cross compiler suitable for ARMV7
- extract the sources to directory of your choice
- to compile x-load:
Code:
cd ./x-loader-archos
make archos_config
make
- to compile u-boot-2011.09-archos:
Code:
cd ./u-boot-2011.09-archos
make a101it_config
make
It might be required to tweak the top-level Makefiles to point at your toolchain.
I used my ready to work toolchain (for 32-bit linux only) here:
http://forum.xda-developers.com/showthread.php?t=1328027
Unfortunately i haven't found some time to create a project page at gitorious,
but hopefully i'll manage to do so in the next weeks...
I know this is a very very special project, but anyway if there's some interest, this might lead to something useful in the end.
If the bootcode is working very nice some day, it might also be possible to replace stock loader, but that's fiction yet.
You might ask what for...
I say... it's just for fun!
cheers,
scholbert

Boot console output... so far
Hey,
it had been posted already but her again for completeness...
The console log on UART3 starting custom kernel configured with stock config:
Code:
Texas Instruments X-Loader 1.5.1 (Mar 26 2012 - 20:41:11)
Found 0256 MB
Archos Gen8
Reading boot sector
Loading u-boot.bin from mmc
Done!
U-Boot 2011.09 (Mar 23 2012 - 18:53:39)
OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
Archos 101IT Gen8 + LPDDR/MMC
I2C: ready
DRAM: 256 MiB
MMC: OMAP SD/MMC: 0
Using default environment
In: serial
Out: serial
Err: serial
Die ID #144800029ff800000160a4bb18027009
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
2987000 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-2.6.29-omap1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2986936 Bytes = 2.8 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux.............................................................
................................................................................
..................................................... done, booting the kernel.
<6>Initializing cgroup subsys cpu
<5>Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.1 (GCC) ) #1
PREEMPT Thu Mar 22 23:59:34 CET 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Archos A101IT board
fixup_archos: [console=ttyS2,115200n8 androidboot.console=ttyGS0 init=/linuxrc d
ebug omapdss.debug=0 vram=4915200 omapfb.vram=0:4915200 omapfb.debug=0 mmc_block
.split=0.0001:512M]
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 65536
<7>free_area_init_node: node 0, pgdat c05fd368, node_mem_map c06a5000
<7> Normal zone: 512 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 65024 pages, LIFO batch:15
<4>L2 CACHE is enabled in bootloader
<6>OMAP3630 ES1.2
<6>DIE ID: 144800029FF800000160A4BB18027009
<6>FEATURE_STATUS: 00000c00
<6>SRAM: Mapped pa 0x40200000 to va 0xfc800000 size: 0x100000
<6>Reserving 4915200 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
<5>Kernel command line: console=ttyS2,115200n8 androidboot.console=ttyGS0 init=/
linuxrc debug omapdss.debug=0 vram=4915200 omapfb.vram=0:4915200 omapfb.debug=0
mmc_block.split=0.0001:512M
<3>Unknown boot option `androidboot.console=ttyGS0': ignoring
<3>Unknown boot option `omapdss.debug=0': ignoring
<6>Clocking rate (Crystal/DPLL/ARM core): 26.0/332/600 MHz
BTW, i extracted the function from Archos loader setup up PLL and MPU stuff.
Need some time to extract the stock setup for PLL at early stage.
Maybe this will give some answers.
One of my next plans is, to build some kind of bare bone kernel (console only), which may be used for recovery and debug purpose.
Maybe this gives it a kick and things start up to a login shell
TBC
Have fun!
scholbert

One of my next plans is, to build some kind of bare bone kernel (console only), which may be used for recovery and debug purpose.
Maybe this gives it a kick and things start up to a login shell.
Click to expand...
Click to collapse
Seems like an internal monologue... but i like to point out that i stopped this project for a while.
So don't expect anything like a brick recovery tool or similar.
If others will join in it might be possible that it would led to something,
but as long as no one even starts hacking the hardware this is just for me...
Happy days!
scholbert

scholbert said:
Seems like an internal monologue... but i like to point out that i stopped this project for a while.
So don't expect anything like a brick recovery tool or similar.
If others will join in it might be possible that it would led to something,
but as long as no one even starts hacking the hardware this is just for me...
Happy days!
scholbert
Click to expand...
Click to collapse
Shame you stopped your efforts for now, I always followed your posts with much interest. However I can understand it is frustrating being on your own.
Thanks for what you did this far and for posting your info .
divx118

Sorry to read that, this was a very very interesting reading.
But I don't have the knowledge to make the necessary hardware hack, and above all, my wife would kill me if she saw me opening the tab
Thanks again for all that amazing information scholbert

Hey,
first off all thanks for your interest and your replies
Some words on your comments though...
divx118 said:
Shame you stopped your efforts for now, I always followed your posts with much interest. However I can understand it is frustrating being on your own.
Click to expand...
Click to collapse
I did not want to sound frustrated, because i'm not.
All i do with the device and all that hacking stuff is fun and mostly for educational purpose
Maybe i'll continue working with this stuff, but for now i wanted to point out to not expect too much.
Some guys out there, bricked their devices and were looking for a solution.
That's why i wrote it down.
Basically it should be possible to recover bricks by using external boot procedure, but it's still far from a simple solution.
grim-a101 said:
Sorry to read that, this was a very very interesting reading.
But I don't have the knowledge to make the necessary hardware hack, and above all, my wife would kill me if she saw me opening the tab
Click to expand...
Click to collapse
Yeah that's a good point, the barrier for this kind of hacking is little high.
Unfortunately you'll have to tweak the hardware, to gain access to the serial debugging port and cheat the power management of the MicroSD slot.
Most of you simply want to use the device and do some less harder tweaks at system level.
Anyway, there are some other possibilities as well (e.g. using USB and TI Flash) to access the platform. Maybe i'll do some research here as well.
Thanks again for appreciation!!!
Regards,
scholbert

[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 .?

How to disable cpu cores on Samsung Galaxy A8 (SM-A530F)?

I've been trying for a while to turn off some of the cpu cores on the Samsung A8, but all tries have failed. Can anyone point me in a direction about how to do this? Do I need to configure the kernel or maybe change boot scripts?
What I've tried by now
Writing to /sys/devices/system/cpu/cpuN/online with a rooted device. (echo "0" > ./sys/device/...../online)
Changing the kernel to one of the custom ones here from xda and trying the step above again. (Kernel installed was Quantum Kernel)
Using kernel adiutor to turn off the CPUs on the CPU tab (this turns off the CPU for a while than it turns back on again)
Using su on adb shell to change file permissions on sysfs (chmod 664 /sys/devices/...../online) and then trying to write to it.
All the steps above were tried with both SELinux Enforcing and Permissive state.
I believe the kernel is turning the cores back on again, but I'm not sure. If this is true, is there any way to tell the kernel to manage only some of the cores and leave the others alone?
Device Information
Model: Samsung Galaxy A8 (SM-A530F)
Android Version: Android Pie (9)
Kernel: Quantum Kernel V4
Kernel version: 4.4.111-Quantum_pie.V4.0-A530F
Processor: Samsung Exynos Octa 7885
Magisk version: (used for root) 19.3
Kernel Adiutor: 0.9.11

Expert needed to root Android Headunit with Allwinner A50 SoC

Hi Experts,
In possession of a Pioneer Headnit which consists of a amplifier and seperate tablet SDA-8TAB.
Seems to run on a Allwinner A50 Soc and on Android 9. Would like to get root access but well known Rooting Apps do not work. Somebody can help? I captured some info from the tablet and by looking in the logs which were created when you re-install the tablet:
Manufacturer: worldchip
Model: SDA-8TAB
Brand: Pioneer
Board: exdroid
Device: SDA_8TAB
Hardware: sun8iw15p1
Platform: venus
Product: SDA_8TAB_XEEU5_EEA
Installed RAM: 2 GB
<<< CPU >>>
Core Architecture: 4x ARM Cortex-A7 @ 1800 MHz
Instruction Set: 32-bit ARMv7
CPU Revision: r0p5
CPU Cores: 4
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
<<< Android >>>
Android Version: 9 (Pie)
API Level: 28
Android Security Patch Level: 2019-11-05
Codename: REL
Java Runtime Version: Android Runtime 0.9
Java VM Version: ART 2.1.0
Java VM Heap Size: 256 MB
Kernel Architecture: armv7l
Kernel Version: 4.9.118
Tags: release-keys
Type: user
Google Play Services Version: 20.21.15 (100300-313409149)

hjdevries said:
Would like to get root access but well known Rooting Apps do not work.
Click to expand...
Click to collapse
It would be very helpful if you mentioned wich rooting apps you already tried. How would you otherwise get advice about other apps/options.

surfer63 said:
It would be very helpful if you mentioned wich rooting apps you already tried. How would you otherwise get advice about other apps/options.
Click to expand...
Click to collapse
Sure, thanks for the question, apps I tried:
Kingroot
Kingoroot
dr. Foneroot
RootGenius
P.S I don't want to install custom rom, only would like root access

hjdevries said:
Sure, thanks for the question, apps I tried:
Kingroot
Kingoroot
dr. Foneroot
RootGenius
P.S I don't want to install custom rom, only would like root access
Click to expand...
Click to collapse
Try Magisk. It is the universal rooting method.
You do need to know though how to flash a boot image, or how to dd write a boot image.

surfer63 said:
Try Magisk. It is the universal rooting method.
You do need to know though how to flash a boot image, or how to dd write a boot image.
Click to expand...
Click to collapse
Goedemiddag,
Yes I have read tutorials and I need TWRP with a custom file designed for my device, which I cannot find.
So Magisk is one step too far for the moment.
Any suggestion? Dank, HJ

hjdevries said:
Goedemiddag,
Yes I have read tutorials and I need TWRP with a custom file designed for my device, which I cannot find.
So Magisk is one step too far for the moment.
Any suggestion? Dank, HJ
Click to expand...
Click to collapse
Depending on the head unit you do not need TWRP, but I have no idea how your boot/recovery works.
Other tools are Superuser and SuperSU.

surfer63 said:
Depending on the head unit you do not need TWRP, but I have no idea how your boot/recovery works.
Other tools are Superuser and SuperSU.
Click to expand...
Click to collapse
What I did just now:
1. In developer settings Android allow to boot custom image
2. Downloaded MagiskManagere to tablet and chose the option to install ZIP automatically
3. Booted in Android recovery mode by holding down the power button and volume up button
4. I expected to get booted in a different screen than the stock Android one, see attachment.
Bootloader option just shows the Android puppet....with belly open
Am I doing something wrong?

I also surfed the web and found out that it's helpfull to have the stock factory rom from the device so that later on it can be flashed with root access.
But to get the stock rom you need root, which I am actually after. Or use TWRP but hey, they don't have rom for my device.
So basically stuck. Should I give up or is there a way, or perhaps I am doing something wrong?

hjdevries said:
I also surfed the web and found out that it's helpfull to have the stock factory rom from the device so that later on it can be flashed with root access.
But to get the stock rom you need root, which I am actually after. Or use TWRP but hey, they don't have rom for my device.
So basically stuck. Should I give up or is there a way, or perhaps I am doing something wrong?
Click to expand...
Click to collapse
Most units here are Chinese units. Actually there are only 4~5 Android/MCU manufaturers. All the brands you see are resellers of the hardware of these 4~5 resellers. You have a Pioneer. It might be identical to one of those manufacturers, but maybe also a pure Pioneer in-house development. That makes that it difficult for those Chinese head unut owners to help you.
But did you try this link? : http://howtoandroitroot.com/download/pioneer-sda-8tab
(I didn't follow it through)

surfer63 said:
Most units here are Chinese units. Actually there are only 4~5 Android/MCU manufaturers. All the brands you see are resellers of the hardware of these 4~5 resellers. You have a Pioneer. It might be identical to one of those manufacturers, but maybe also a pure Pioneer in-house development. That makes that it difficult for those Chinese head unut owners to help you.
But did you try this link? : http://howtoandroitroot.com/download/pioneer-sda-8tab
(I didn't follow it through)
Click to expand...
Click to collapse
Note to self for good tutorial, method 2. https://www.the***********.com/install-magisk-root-android-devices/
Need Stock root image.
The website you gave doesn't asllow me anything, however it shows options for all ANdroid which is strange, This tablet just came out.
Do you have somebody in your network who could help find that stock boot image looking at my first post with ingo, or contact me how to get it myself from the device perhaps?
Willing to donate of course.

I think I have almost the same unit as you .. I've been looking everywhere for the info about rooting and any available alternative roms ... Mine is a Xomax XM 2VA 757 ... pure allwinner but now you've answered a lot of my puzzles. Thanks
We have almost identical architectures .... and I have asked my vendor if they can find me an OTA type upgrade ROM for it .. I don't hold out much hope but I am trying.
Manufacturer: Allwinner
Model: QUAD-CORE
Brand: Allwinner
Board: exdroid
Device: venus-a3
Hardware: sun8iw15p1
Platform: venus
Product: venus_a3
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
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
Android Version: 9 (Pie)
API Level: 28
Android Security Patch Level: 2019-01-05
Rooted Device: No
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
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)

And we both live in the Netherlands !! I'm in Den Haag .. where are you ?

I just found anA50 firmware .. don't recognise the device though ...
Here ...

Heya. I have the same device. After a few weeks of research I managed to boot it into a firmware from another device (MultiLaser M7S Lite Oreo) using PhoenixCard. This means that I should be able to use IMGRePacker to extract it, then patch boot.fex with Magisk, flash that back onto the SD Card and from there on out, I should be able to backup the stock img from the internal nand, patch that and then flash it to the nand. I will keep y'all up to date with success/failures.
UPDATE 1: Boot.fex from MultiLaser Stock Firmware is patched and repacked into Firmware IMG. Flashing to SD Card right now.
UPDATE 2: Flashed SD Card with new boot.fex. Wouldn't boot. Will try flashing it with the option "Preserve force encryption" checked.
UPDATE 3: Just found out there are two bootloaders. One on the nand, and one on the SD. Obviously to boot the sd card with a patched img, I will need to unlock the bootloader. Edit: It won't boot to bl with button combo, I am assuming I will need to execute "adb reboot bootloader", so will be trying that.
UPDATE 4: The M7S ROM is booted and rooted baby!

snowlily said:
Heya. I have the same device. After a few weeks of research I managed to boot it into a firmware from another device (MultiLaser M7S Lite Oreo) using PhoenixCard. This means that I should be able to use IMGRePacker to extract it, then patch boot.fex with Magisk, flash that back onto the SD Card and from there on out, I should be able to backup the stock img from the internal nand, patch that and then flash it to the nand. I will keep y'all up to date with success/failures.
UPDATE 1: Boot.fex from MultiLaser Stock Firmware is patched and repacked into Firmware IMG. Flashing to SD Card right now.
UPDATE 2: Flashed SD Card with new boot.fex. Wouldn't boot. Will try flashing it with the option "Preserve force encryption" checked.
UPDATE 3: Just found out there are two bootloaders. One on the nand, and one on the SD. Obviously to boot the sd card with a patched img, I will need to unlock the bootloader. Edit: It won't boot to bl with button combo, I am assuming I will need to execute "adb reboot bootloader", so will be trying that.
UPDATE 4: The M7S ROM is booted and rooted baby!
Click to expand...
Click to collapse
hi,can you send the boot file?i have thepioneer and trying to root it

Lefteris Fragiadakis (Frago) said:
hi,can you send the boot file?i have thepioneer and trying to root it
Click to expand...
Click to collapse
Unfortunately I messed it up and accidentally flashed the internal boot partition with a magisk patched boot from the multilaser and now I have no way to obtain the original boot image. Though you can always check if the multilaser firmware is anywhere near stable on your device using phoenixcard. I'll see if I can find back where I got the flashfile in a bit and post here. Just make sure to use phoenixcard before actually flashing the tablet. This way you can know if it even boots and works in the first place, without risking a brick.

The download quota is exceeded. Imma find a way to download it and reupload it to Mega

i can read system if i take of emmc using ufi box but i dont want to lose guarentee,i also tried to find a boot to patch it with magisk but i didnt,i only want to root this pioneer

snowlily said:
Unfortunately I messed it up and accidentally flashed the internal boot partition with a magisk patched boot from the multilaser and now I have no way to obtain the original boot image. Though you can always check if the multilaser firmware is anywhere near stable on your device using phoenixcard. I'll see if I can find back where I got the flashfile in a bit and post here. Just make sure to use phoenixcard before actually flashing the tablet. This way you can know if it even boots and works in the first place, without risking a brick.
Click to expand...
Click to collapse
also maybe the pathced boot you have i can try to boot it on pioneer to see if this work

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