Database Info

Chinese Phone

Hello I have bougt a Chinese phone that i am very satisfied with except one thing. I had to do a hard reset, and a´fter that i can't access my storage card. I have got out this data from SKtools. If somebody can help me. Yes, I have tried with 3 other SD-cards without success. Support from China ?.. well does it exist at all? Yeah I know that it is probably cheap thinking too buy a phone like that but now i have done that. It has Builtín GPS,WIFI,3,0 Mpix camera at a price of 180$, and worked flawless until the hard reset. Link to Phone... Sorry for my english, i'm swedish.
HTC G2 Built-in GPS, WIFI 460MHz CPU 3.0MP camera Windows Mobile phone Smart PDA + 2GB TF
[Device]
Marvell PXA312
PocketPC
Total time 20.22 min.
Idle time 15.50 min.
Idle percent 76.7%
Time from last power on 2.97 min.
[Features]
Sound : Available
Pocket Office : Available
Infrared : Not available
Vibration : Available
IMAP4 : Available
Phone : Available
Bluetooth : Available (Microsoft)
MMS : Not available
MUI : Not available
Speech : Not available
Persistent storage : Available
Bluetooth handsfree : Available
[Processor]
Processor info:
Processor core: ARM920T
Core revision: 0
Processor name:
Processor revision: 0
Catalog number :
Vendor: Marvell PXA312
Instruction set: 0
Clock speed: 360
[OS]
OS 5.2.20954.3
Adaptation Kit Update (AKU) version .1.5.0
[Memory]
program: 95568/60748 KB (all/free)
storage: 158928/33252 KB (all/free)
[Power]
LION
On AC Line: No
Main battery: 100%, 4222 mV, 32767 mA, 0 C
Backup battery: 100%
[Screen]
Resolution 240 x 320
DPI 96 x 96
Colors 65536
BackLight AC 5 BATT 0
[Network]
NT901_PPC
Adapter: SDIO86861
SDIO86861
MAC address: 00 22 43 92 58 7b
IP address:
0.0.0.0 0.0.0.0
Gateway:
DHCP server :
---------CMGR--------
CELLULAR_CSD
Status: 32
Secure: 0
CMCC MMS (CSD)
-------
CELLULAR_CSD
Status: 32
Secure: 0
CMCC WAP (CSD)
-------
CELLULAR_GPRS
Status: 32
Secure: 0
CMCC MMS (GPRS)
-------
CELLULAR_GPRS
Status: 32
Secure: 0
CMCC WAP (GPRS)
-------
PROXY_WAP
Status: 32
Secure: 0
CMCC WAP Gateway
-------
PROXY_NULL
Status: 32
Secure: 0
null-corp-{18AD9FBD-F716-ACB6-FD8A-1965DB95B814}
-------
PROXY_NULL
Status: 32
Secure: 0
HTTP-{ADB0B001-10B5-3F39-27C6-9742E785FCD4}
-------
[Hardware buttons]
[Phone]
NXP
NEXPERIA SY.SOL 5209
1.07.9201
366889010003287
240084702067287
VODAFONE SWEDEN
24008
IMSI:240084702067287
CellID:12672
LocationAreaCode:13
[Serial ports list]
COM3:Serial_GPS
COM2:Serial_BT
COM1:Serial_Modem
COM6:Serial_AGPS
[SD information]
Bus driver version 5.2
Slot 0
Host index 0,slot index 0
Inserted card Memory Card
Card type SD Memory
Interface mode 4 bit(s),Clock rate 25000000
[Security Policy]
one/two-tier device : 1
unsigned CABs : 16
unsigned apps : 1
user prompts : 1
4119 : 160
autorun : 0
4120 : 16
unsigned themes : 64
RAPI : 2
DRM : 3072
[Opened TCP/UDP ports]
[UDP]: 0.0.0.0:137
*.*.*.*:*
[UDP]: 0.0.0.0:138
*.*.*.*:*
[UDP]: 0.0.0.0:9204
*.*.*.*:*
[UDP]: 127.0.0.1:1028
*.*.*.*:*

new froyo for i9000 2.2.1

http://forum.xda-developers.com/showthread.php?t=865701
can we use this with the reorented kernel.

sounds good to me....can't wait to hear some reports of how it runs.

Designgears is thinking about trying this one.

About to flash it now. Sounds amazing from the comments over there!

FYI this is for the I9000 and I dont know if a reorented kernel will work.

Works pretty well using Setiron's 1.4.2 and JK3 modem. Only wifi isn't working for me.
The browser in this is amazing. FINALLY we have a browser that's smoother than our 2.1 browser. Seems like it uses hardware acceleration now.
It also doesn't seem to need a lagfix. I haven't run Quadrant yet, but people are reporting up to 1300 with no lagfix.

gtg465x said:
Works pretty well using Setiron's 1.4.2 and JK3 modem. Only wifi isn't working for me.
The browser in this is amazing. FINALLY we have a browser that's smoother than our 2.1 browser. Seems like it uses hardware acceleration now.
It also doesn't seem to need a lagfix. I haven't run Quadrant yet, but people are reporting up to 1300 with no lagfix.
Click to expand...
Click to collapse
oh mahh gahhhd it's raining cats and dogs in the phone world

Let the customising begin hahahah!
Sent from my SAMSUNG-GT-I9000 using XDA App

Main problem right now is that we don't have the kernel source for JPU and thus we can't get a proper reoriented kernel for this.
I'm running JPU using Setiron's reoriented kernel, which is based off JPM source I believe, but wifi and high quality video recording/playback don't work. The video recording/playback might be fixable if Setiron compiles using the new memory config from JPU (posted it below), but I'm not sure about wifi (which sees networks but can't connect).
Here are the new STOCK memory configurations in JPU. There is 339 MB available to the user, so the bigmem tweaks will no longer be necessary once we start getting kernels built on this new source. As I mentioned earlier, we don't need lag fixes any more either because Samsung seems to have fixed some problems with RFS and it's a lot faster now. So this is great news for us.
Chainfire said:
Code:
<7>[ 0.000000] s5pv210_setup_clocks: registering clocks
<7>[ 0.000000] s5pv210_setup_clocks: clkdiv0 = 14131330, clkdiv1 = 00300400
<7>[ 0.000000] s5pv210_setup_clocks: xtal is 24000000
<6>[ 0.000000] S5PV210: PLL settings, A=800000000, M=667000000, E=96000000
<6>[ 0.000000] s5pv210: 33554432 bytes system memory reserved for mfc at 0x30ec8000
<6>[ 0.000000] s5pv210: 33554432 bytes system memory reserved for mfc at 0x40204000
<6>[ 0.000000] s5pv210: 12582912 bytes system memory reserved for fimc0 at 0x42204000
<6>[ 0.000000] s5pv210: 1048576 bytes system memory reserved for fimc1 at 0x42e04000
<6>[ 0.000000] s5pv210: 12582912 bytes system memory reserved for fimc2 at 0x42f04000
<6>[ 0.000000] s5pv210: 2097152 bytes system memory reserved for pmem at 0x32ec8000
<6>[ 0.000000] s5pv210: 4194304 bytes system memory reserved for pmem_gpu1 at 0x330c8000
<6>[ 0.000000] s5pv210: 1536000 bytes system memory reserved for pmem_adsp at 0x334c8000
<6>[ 0.000000] s5pv210: 10485760 bytes system memory reserved for texstream at 0x3363f000
<6>[ 0.000000] s5pv210: 3145728 bytes system memory reserved for fimd at 0x43b04000
<6>[ 0.000000] s5pv210: 262144 bytes system memory reserved for wifi at 0x3403f000
<4>[ 0.000000] Built 3 zonelists in Zone order, mobility grouping on. Total pages: 117856
<5>[ 0.000000] Kernel command line: console=ttySAC2,115200 loglevel=4
<6>[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
<6>[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>[ 0.000000] Memory: 80MB 256MB 128MB = 464MB total
<5>[ 0.000000] Memory: 343740KB available (9224K code, 1909K data, 2892K init, 0K highmem)
Click to expand...
Click to collapse

Just flashed with xcalibur's kernel and jk3 modem... oh boy. This thing flies. I'VE GOT BLISTERS ON ME CELLPHONE!
Edit: Quick notes/test results
linpack=13.202
Web browsing is buttery smooth, even with a site full of content! Full engadget breezes on through the screen bye-bye website stutters
GPS gets a lock within 4000 meters instantly, took 10 seconds to get around 40 meters, with a pinpoint lock after around 10 more seconds.
Wi-Fi is a no go
High quality video recording is a no go.
Will use this tomorrow (today I guess, lol) and post more resultz.

Needing developers for ZTE V875

Hi
I'm writing this because there is no tool for root and none custom rom available for this device. According to ZTE this phone is sold in China, Portugal and Brazil but there is no development for this phone. Here in Portugal we decided (in a portugues forum) to raise money to buy a new phone and pay shipping but we need developers to develop a tool for root and a custom rom.
Those interested, please send me a private message.
And any suggestion, please feel free to comment.

[deleted by the user]

[Deleted by the user]

Ok, I know I'm crossing the line here, but I believe this can be crucial to the Development of this terminal. This is one of the stock rom's for this phone, and inside it's the default recovery.img. Maybe that will help you to start the development!
Here is the Stock Rom.
Good luck!
Edit:
Also
Code:
dev: size erasesize name
mtd0: 00600000 00020000 "recovery"
mtd1: 00400000 00020000 "boot"
mtd2: 00180000 00020000 "splash"
mtd3: 00080000 00020000 "misc"
mtd4: 03980000 00020000 "cache"
mtd5: 0dc00000 00020000 "system"
mtd6: 0a280000 00020000 "userdata"
mtd7: 00100000 00020000 "oem"
mtd8: 00180000 00020000 "persist"
Code:
OS
Browser UserAgent : Mozilla/5.0 (Linux; U; Android 2.3.5; pt-pt; tmn smart a7 Build/GRJ22) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1
Android ID : 54fa62763779a37e
Uptime : 0 days, 0 hours, 19 minutes, 34 seconds
Uptime (without sleeps) : 0 days, 0 hours, 19 minutes, 34 seconds
BuildInfos
Android version : 2.3.5
Release Codename : REL
API LEVEL : 10
CPU ABI : armeabi
Manufacturer : ZTE
Bootloader : unknown
CPU ABI2 : unknown
Hardware : sailboat
Radio : unknown
Board : sailboat
Brand : ZTE
Device : sailboat
Display : GB_TMN_V875V1.0.0B04
Fingerprint : ZTE/P727P_TMN/sailboat:2.3.5/GRJ22/eng.xuzhenxuan.20111125.111323:user/release-keys
Host : xuzhenxuan-111
ID : GRJ22
Model : tmn smart a7
Product : P727P_TMN
Tags : release-keys
Type : user
User : xuzhenxuan
Battery
Charging in progress...
Level : 73 %
Technology : Li-ion
Temperature : 29.0 °C (84.2°F)
Voltage : 3955 mV
Memory
Download Cache Max: 57,48 MB/ Free: 56,36 MB
data Max: 162 MB/ Free: 34,27 MB
External storage Max: 7,40 GB/ Free: 7,14 GB
Total RAM: 422 MB
Free RAM: 265 MB
Threshold RAM: 24,00 MB
Low Memory Killer Levels
FOREGROUND_APP:__ 8,00 MB
VISIBLE_APP:_________ 12,00 MB
SECONDARY_SERVER: 16,00 MB
HIDDEN_APP:________ 24,00 MB
CONTENT_PROVIDER: 28,00 MB
EMPTY_APP:__________ 32,00 MB
Telephony
Data Activity: DATA_ACTIVITY_NONE
Data State: DATA_DISCONNECTED
IMEI(or MEID): 860790010186042
IMEI/SoftVer: 00
MSISDN: 926855982
Registered MCC: pt
Registered MCC MNC: 26806
Registered Operator Name: P TMN
Network Type: NETWORK_TYPE_UMTS
Phone Type: PHONE_TYPE_GSM
SIM Country Code: pt
SIM MCC MNC: 26806
SIM Operator Name:
SIM Serial Number: 89351060000312816380
SIM State: SIM_STATE_READY
Subscriber ID(IMSI): 268063100633279
VoiceMail number: +351962000000
Roaming: false
CID: 2662768
LAC: 320
No Cell detected
Networks
Background Data Usage: true
type mobile[UMTS]
state DISCONNECTED/DISCONNECTED
reason dataDisabled
extra internet
roaming false
failover false
isAvailable true
type WIFI[]
state CONNECTED/CONNECTED
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
type mobile_mms[UMTS]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
type mobile_supl[UMTS]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
type mobile_dun[UMTS]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
type mobile_hipri[UMTS]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
CPU
Processor ARMv6-compatible processor rev 5 (v6l)
BogoMIPS 532.48
Features swp half thumb fastmult vfp edsp java
CPU implementer 0x41
CPU architecture 6TEJ
CPU variant 0x1
CPU part 0xb36
CPU revision 5
Hardware sailboat
Revision 0000
Serial 0000000000000000
Freqency range: 122.88 -> 800.0MHz
Current Frequency: 800.0MHz
Frequency Stats (time):
- 122.88 MHz 0.0% (0)
- 245.76 MHz 81.36% (95413)
- 320.0 MHz 0.38% (445)
- 480.0 MHz 0.78% (916)
- 800.0 MHz 17.48% (20496)
Camera
As retreiving camera infos can give the impression that it is taking picture on some device, it is not enabled by default. If you wish to, go in settings menu.
Screen
Resolution: 320 x 480
Refresh Rate: 0.77
X factor for DIP: 1.0
Density: 160 dpi
Pixel per inch X: 159.37254 dpi Y: 160.42105 dpi
OpenGL
As retreiving opengl infos can crash some device, it is not enabled by default. If you wish to, go in settings menu.
Sensors
LIS33DE/ADXL346 3-axis Accelerometer: 0.2 mA by ST/ADI
AK8973 3-axis Magnetic field sensor: 6.8 mA by Asahi Kasei
AK8973 Orientation sensor: 7.0 mA by Asahi Kasei
TSL2771 Proximity sensor: 0.5 mA by Taos
TSL2771 Light sensor: 0.5 mA by Taos
Gravity Sensor: 0.2 mA by Google Inc.
Linear Acceleration Sensor: 0.2 mA by Google Inc.
Rotation Vector Sensor: 7.0 mA by Google Inc.
Environment
Root Directory: /system
Data Directory: /data
Download Cache Directory: /cache
External Storage State: mounted
External Storage Directory: /mnt/sdcard
Medias Directories
Alarms: /mnt/sdcard/Alarms
DCIM: /mnt/sdcard/DCIM
Downloads: /mnt/sdcard/Download
Movies: /mnt/sdcard/Movies
Music: /mnt/sdcard/Music
Notifications: /mnt/sdcard/Notifications
Pictures: /mnt/sdcard/Pictures
Podcasts: /mnt/sdcard/Podcasts
Ringtones: /mnt/sdcard/Ringtones
Features
android.hardware.wifi
android.hardware.location.network
android.hardware.telephony
android.hardware.location
android.software.sip
android.hardware.touchscreen.multitouch
android.hardware.sensor.compass
android.hardware.camera
android.hardware.bluetooth
android.hardware.sensor.proximity
android.software.sip.voip
android.hardware.sensor.light
android.hardware.microphone
android.hardware.location.gps
android.hardware.telephony.gsm
android.hardware.camera.autofocus
android.hardware.touchscreen
android.hardware.sensor.accelerometer
android.software.live_wallpaper
glEsVers=2.0
JavaProperties
java.vendor.url: http://www.android.com/
java.class.path: .
java.class.version: 46.0
os.version: 2.6.35.7-perf+
java.vendor: The Android Project
user.dir: /
user.timezone: null
path.separator: :
os.name: Linux
os.arch: armv6l
line.separator:
file.separator: /
user.name:
java.version: 0
java.home: /system

{edited by user}

RomJOB 2
I did a custom rom for this device.
It is 2.3.5, rooted, zipalign, odexed, tweaks build.prop and int.d, battery percentage, bloatware removed and others.
You need to be rooted and have cwm on it.
Do a factory reset in cwm and install the zip.
Download here: https://docs.google.com/file/d/0ByCmvmvJz1jmSHAwckdhUlRiM0U/edit?usp=sharing

job said:
I did a custom rom for this device.
It is 2.3.5, rooted, zipalign, odexed, tweaks build.prop and int.d, battery percentage, bloatware removed and others.
You need to be rooted and have cwm on it.
Do a factory reset in cwm and install the zip.
Click to expand...
Click to collapse
Witch cwm and recovery do you have?????

pass25 said:
Witch cwm and recovery do you have?????
Click to expand...
Click to collapse
1. Push with ADB the attached file tou your device. (if you don't know how to do this, let me know)
2. Then you need to be rooted. (it's another step)
3. Install ROM Manager or Quick Boot from the Playstore
4. Reboot into recovery through one of those apps
And that's it! You'll be booting into CWM 5.0.2.5 (I think it's this version)

job said:
1. Push with ADB the attached file tou your device. (if you don't know how to do this, let me know)
2. Then you need to be rooted. (it's another step)
3. Install ROM Manager or Quick Boot from the Playstore
4. Reboot into recovery through one of those apps
And that's it! You'll be booting into CWM 5.0.2.5 (I think it's this version)
Click to expand...
Click to collapse
the rom its great, but it drains the batery a litle fast!!!
and cyanogen, can you port some for us or not?

I'm planningon porting it, yes. But just next month since i?m moving home right now and it's all in a big mess.

job said:
I'm planningon porting it, yes. But just next month since i?m moving home right now and it's all in a big mess.
Click to expand...
Click to collapse
ok, if you need any help, tell me about it!
here are you from?

pass25 said:
ok, if you need any help, tell me about it!
here are you from?
Click to expand...
Click to collapse
Thank you. For right now, I don't have time at all since I'm moving home. But I will let you know as soon as I have the time, end of March beginnning April. I will PM you

[DEAD] Crius Mea Q7A+ - Qualcomm MSM8625 SoC ARMv7-A arch DEAD

ⴰⵣⵓⵍ,
When i say dead, it's typically dead.
The tablet is a Crius Mea Q7A+, uses the Qualcomm MSM8625 SoC based on the ARMv7-A arch that combines 2 ARM Cortex-A5.
While this tablet was just bricked for a long while, and i couldn't and didn't have time and firmware to reflash it, since it's one of those useless chinese low end tablets.
Having such a desirable SoC for a programmer i thought i can test on it my first steps bootloaders and Embedded OS while developing them for this sole purpose.
ⵣ Space to avoid readers jumping lines ⵣ
The tablet after i flashed it with a lower firmware of an equivalent or almost another SoC, was booting in fastboot mode only thinking that i could get more info's with that about partitions.
I didn't, so what i did was erasing the modem partition, and that left the tablet open as a generic storage drive, i saved almost every information i could have about this SoC, the partition that were available, Qualcomm's boot sequence, UART serial connection of the SoC, and read for week several pages to gather information useful to make a bootloader.
ⵣ Space to avoid readers jumping lines ⵣ
At the end i failed, i thought i could repartition the Flash memory of the SoC to prepare it for future uploading of my bootloader, there was a partition that is miss aligned, which was maybe the 3gb internal storage, so what i did is delete the partition and recreate it erasing the secondary ones, it was working normally as expected.
But then tomorrow i decided to plug the tablet again, but it doesn't get detected, this happened before, i cant really explain how the Primary core is trying to establish connection with the PC, but it's a bad mofo. Still it was detected all the time if i remember well.
But today the tablet was dead, i can even feel the SoC is not responding at all.
Not even detected when plugged to PC.
The battery does charges, cause i tested with a diode since i dont have a multimeter, which burned even with a resistor after the current was too high, but then with a DC brushless motor.
Mainly the charging circuit is separated from other components and connected directly to DC, that's why it's charging.
I opened the tablet, and took off the battery cables thinking i might be able to get the core to QDload mode which pressing some combinations...
And yeah i tried every combination i can think off, i even tried pressing my mouse in the PC and pressing the Vol UP in the tablet... am so funny.
I hope anyone can tell me a way to communicate with the SoC in this state, or any other solution thanks peace.
Finally i forgot the partition i saved as a text before i repartitioned the last ones only :
Code:
Disk /dev/sdd: 3.7 GiB, 3909091328 bytes, 7634944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdd1 * 1 40 40 20K 4d QNX4.x
/dev/sdd2 41 540 500 250K 45 unknown
/dev/sdd3 541 102940 102400 50M c W95 FAT32 (LBA)
/dev/sdd4 102941 7634943 7532003 3.6G 5 Extended
/dev/sdd5 131072 135167 4096 2M 46 unknown
/dev/sdd6 135168 141311 6144 3M 58 unknown
/dev/sdd7 141312 147455 6144 3M 4a unknown
/dev/sdd8 147456 153599 6144 3M 4b unknown
/dev/sdd9 153600 157695 4096 2M 5d unknown
/dev/sdd10 157696 165887 8192 4M 90 unknown
/dev/sdd11 165888 167935 2048 1M 63 GNU HURD or SysV
/dev/sdd12 167936 169471 1536 768K 47 unknown
/dev/sdd13 169472 196623 27152 13.3M 60 unknown
/dev/sdd14 196624 217103 20480 10M 91 unknown
/dev/sdd15 217104 413711 196608 96M 83 Linux
/dev/sdd16 413712 440863 27152 13.3M 48 unknown
/dev/sdd17 440864 1362463 921600 450M 83 Linux
/dev/sdd18 1362464 1567263 204800 100M 83 Linux
/dev/sdd19 1567264 1567303 40 20K 4c unknown
/dev/sdd20 1567304 4536903 2969600 1.4G c W95 FAT32 (LBA)
/dev/sdd21 4536904 7510599 2973696 1.4G 83 Linux
/dev/sdd22 7510600 7634942 124343 60.7M 83 Linux
As you can the sdd4 partition was overlapping other partitions sectors so i had to erase it, the rest got erased in the way, but the main boot and from 1 to 3 are intact.
Something else, the MSM7627a is a close SoC to this one, except for the one i have got 2 Cores instead of one, and supports LPDDR and have a more developed GPU, here's a note i wrote :
Code:
MSM7627 seems close enough to the MSM8625, except that it uses a single core ARMv7-A CORTEX A5.
Which is the primary core that we need to boot up, then add the next core to the equation for the kernel.
Some differences about the MSM7627a and the MSM8625 :
MSM7627a | MSM8625
CPU Clock Speed 1,000MHz 1,200MHz
CPU Cores 1 2
GPU Qualcomm Adreno 200 Qualcomm Adreno 203
RAM Interface LPDDR2 SDRAM LPDDR, LPDDR2 SDRAM
As we can see here, they are almost identical, except for the cores which wont make a wall since we're making a bootloader, the GPU... and the RAM interface
Am on Debian Stretch and i dont have any ways of visualization but i accept any link on any platform. Thanks everyone peace again
I also want to add, that i can feel a bit of heat over the tablet it's certainly not from the battery, i dont really know if its coming from the SoC, but if it is am really glad he's doing some cycles.

And i thought i had a chance in this forum lol. looks like am on ma own.

[KERNEL] mainlining Manta kernel

Hi,
I'm trying to port kernel 5.x to the Manta device (Nexus 10). The architecture is arm and the soc is exynos5250. I have no problem with drivers support because there are few similar devices already supported in mainline.
Therfore I started a write a device tree and tried to boot it. Nothing happened. Screens stays blank and device seems to be dead.
I'm looking for ideas. I tried a lot of things already . It's very strange because I would have expected a kernel panic and a reboot. It does nothing at all.
Of course I don't have a serial link. For now I use a small ramdisk image that just reboot the system after a 20 seconds sleep.
I'm wondering if there not a compatibility problem with the old bootloader. Please note that I append the dtb to the zImage and I activated the DTB-ATAGS compatibility options.
I fixed the decompressed kernel address (zreladdr) because the default calculation couldn't work.
I was thinking that my kernel image was a bit too big : I increased the original kernel size using zeroed padding and this one still works very well with my ramdisk.
So I'm a bit confused and I don't really know what I could check right now.
Here is the repo : https://github.com/jmarcgit/manta-mainline
You can find there the current dts and the config file I'm 'using.
I'm merging the default exynos config file with mine therefore it discards a lot of useless options in order to reduce the kernel size and does very few adaptations.
Thanks a lot for your support

Hi,
Happy to see that I'm not the only one trying to accomplish that!
I am not surprised that your reboot script does not work. On my config, the kernel boots without panic, but any call to a sleep/wait function freezes the system. Hence you may want to try to reboot the system without delay.
I cannot remember any compatibility issue with the bootloader.
Please note that you can get a serial link using the audio jack, see here: https://wiki.postmarketos.org/wiki/Serial_debugging:Cable_schematics#Nexus_debug_cable
Then you will have to enable low-level serial (I don't remember the exact name of the kernel option) on TTYSAC2. This has been immensely helpful on my side. Be careful though, as manta uses 1.8V UART.
I will fork your repo to put my config and dts in there as soon as I get some time, so that we can hopefully share, compare and improve our respective progress.

As a follow-up, I ran your configuration on my Manta (I only made the changes to get the serial console and added a missing fixed-clock node in the DTS that made the kernel panic in an early stage, see my fork here https://github.com/alexmrqt/manta-mainline/tree/8bf3528c1f9d9fb5eeb478901a88c495cacf5247).
With that, the device reboots after some times (but it is due to a kernel issue, as I used another ramdisk that is not supposed to do that).
See the kernel console below.
Code:
Starting kernel at 0x40008000...
AST_POWERON..
DEVICEINFO;R32D2042RBF;MANTAMF01;8;08:D4:2B:1F:C7:06;08:D4:2B:1F:C7:05;INFODONE
DTB:0x4021CC48 (0x0000A06D)
C:0x400080E0-0x40226E00->0x40682800-0x408A1520
DTB:0x40897368 (0x0000A1AB)
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 5.16.0-rc5-next-20211215 ([email protected]) (armv7-alpine-linux-musleabihf-gcc (Alpine 11.2.1_git20220219) 11.2.1 2022022
CPU: ARMv7 Processor [410fc0f4] revision 4 (ARMv7), cr=10c5387d
CPU: div instructions available: patching division code
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
OF: fdt: Machine model: Samsung Nexus 10 (manta)
printk: bootconsole [earlycon0] enabled
Memory policy: Data cache writealloc
Samsung CPU ID: 0x43520210
Zone ranges:
Normal [mem 0x0000000040000000-0x000000004fffffff]
HighMem empty
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x0000000040000000-0x000000004fffffff]
Initmem setup node 0 [mem 0x0000000040000000-0x000000004fffffff]
percpu: Embedded 9 pages/cpu s13136 r0 d23728 u36864
Built 1 zonelists, mobility grouping on. Total pages: 65024
Kernel command line: earlyprintk mem=256M console=ttySAC2,115200n8 PMOS_NO_OUTPUT_REDIRECT s3cfb.bootloaderfb=0x60000000 androidboot5
Unknown kernel command line parameters "PMOS_NO_OUTPUT_REDIRECT", will be passed to user space.
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
mem auto-init: stack:off, heap alloc:off, heap free:off
Memory: 249628K/262144K available (3072K kernel code, 519K rwdata, 896K rodata, 1024K init, 207K bss, 12516K reserved, 0K cma-reserve)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
rcu: Preemptible hierarchical RCU implementation.
rcu: RCU event tracing is enabled.
Trampoline variant of Tasks RCU enabled.
rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
random: get_random_bytes called from start_kernel+0x374/0x5e4 with crng_init=0
Exynos5250: clock setup completed, armclk=1000000000
Switching to timer-based delay loop, resolution 41ns
clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
genirq: irq_chip COMBINER did not update eff. affinity mask of irq 57
arch_timer: cp15 timer(s) running at 24.00MHz (virt).
clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
Ignoring duplicate/late registration of read_current_timer delay
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
CPU: Testing write buffer coherency: ok
CPU0: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
/cpus/[email protected] missing clock-frequency property
/cpus/[email protected] missing clock-frequency property
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
cblist_init_generic: Setting adjustable number of callback queues.
cblist_init_generic: Setting shift to 1 and lim to 1.
Setting up static identity map for 0x40100000 - 0x40100060
rcu: Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
CPU1: failed to boot: -110
smp: Brought up 1 node, 1 CPU
SMP: Total of 1 processors activated (48.00 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911

Hi Alex,
you did a great step forward ! I definately missed the serial cable.
Do you still work on it ? I think we are close to get it stable now.

Hi Marc,
Yes, I still work on it from time to time.
I got some nice progress since my last post:
- All CPUs now boot (a secure-firmware node was missing)
- WiFi now works
- Access to MMC partitions now works
- USB gadget works, but only when booting via fastboot (which suggests that something prevents the kernel to properly initialize the chip).
No luck getting the display to work so far
I just updated my repo with the last DTS and defconfig I use.
FYI, I do my tests with postmarketos (which allows me to test "advanced" features such as WiFi).

Hi Alex,
that's really great progress...
Does the backlight work ?
I don't have much time now.

Hi Marc,
Good news, I got the screen to work (as well as other things: battery, USB, touchscreen).
The bad news is that it requires some patches to the kernel code.
I included the patches (generated against kernel 6.1.4 from kernel.org) in the "patch" folder here - > https://github.com/alexmrqt/manta-mainline/tree/f4c38a7867f4e0e7481b71f96a0d0b4116b41c0f