I bought this phone from China. It came with chinese rom 4.4.4 without google services and root.
At the moment I've tried to root it with no luck (all known ways don't work). The bootloader is locked and, therefore no custom roms can be flashed.
There is no "OEM unlocking" menu in debug mode and it doesn't appear after software update request and changing time to +7 days.
I've digged out some information, and the phone turned out to be a clone of G360F (at least I see no difference):
Device Model: SM-G3608
Bootloader: G3608ZMU1AQA2
RAM: 768 MB
Board: MSM8916
Toolchain: GCC 4.7
Runtime Dalivk: 1.6.0
Chipset: QUALCOMM TECHNOLOGIES, INC MSM 8916
SDK Version: 19
Kernel: Linux 3.10.28
CPU Chipset: Qualcomm Snapdragon 410, 28nm LP
Processor Rev: 0 (v71)
Processor Design: Cortex A53
Processor Architecture: ARMV7L
CPU Cores: 4x1190MHz
CPU ABI: ARMEABI-V7A
CPU ABI2: ARMEABI
CPU Revicion: r0p0
CPU implementation: 0x41
Display Resolution: 480x800 TFT
Pixel Density: 210X/210Y ppi
Aspect Ratio: 1.675:1
Refresh Rate: 60 Hz
Orientation: Portrait
Graphics: Qualcomm Adreno (TM) 306
Grpahics API: OpenGL ES 3.0 [email protected] [email protected] ([email protected])
Texture Units: 16
Usable RAM: 630 MB
SD Card 0: 2.28 GB
So I tried to flash the TWRP:
twrp-2.8.7.1-coreprimelte.img.tar and twrp-3.2.2-0-coreprimelte.img.tar
dl.twrp.me/coreprimelte/
github.com/TeamWin/android_device_samsung_coreprimelte
But the phone refuses to run in recovery. It seems that some offsets are different.
I need your help to rebuild twrp-coreprimelte with new parameters or help me to make a correct build config.
All the data for the phone:
Code:
settings.cfg: yadi.sk/d/NV7UF8wK3Zy6Ka
boot_ramdisk.zip: yadi.sk/d/c5xwH9jE3Zy5qo
recovery_ramdisk.zip: yadi.sk/d/SkQPPU653Zy5tV
recovery.img.7z: yadi.sk/d/5AOXxtbV3Zy5zC
build.prop: yadi.sk/d/1QU6Uvf_3Zy6Du
PIT_Analysis_001.txt: yadi.sk/i/2z77_B7a3Zy6FV
ROSSALTE_CHN_CMCC.pit: yadi.sk/d/rBF0t8dm3Zy6Ja
dt.img: yadi.sk/d/mweD5DWT3ZyHNi
recovery.img-zImage: yadi.sk/d/oPkaNM3a3ZyJJY
Here is what (in my opinion) should be changed:
1) BoardConfig.mk
user_debug=23 -> user_debug=31 ?
2) dt.img
replace dt.img
3) kernel
replace kernel -> recovery.img-zImage ?
4) recovery.fstab
recovery_ramdisc\ramdisc\etc\recovery.fstab
no system_image
no data
no misc
efs (efs1) -> ext4 ?
no efs2
external_sd (mmcblk1p1)
other partitions form fstab.qcom ?
Is it correct?, and I'm still confused ,recovery.fstab it's completely different from original recovery.fstab and fstab.qcom
Related
I bought a Literati for only $65 shipped and was thinking maybe android could be ported to this device.
CPU:S3C6410 [email protected]
Audio: None
Camera: None
Touch screen: None
Screen: Color 7" unknown X Unknown
Memory
SD: up to 16gig
User: 256mb(black) expandable to 1gb once telnet is enabled.
System: 64mb(i think)
USB
Mini USB: Mode=device
internal USB: Mode=Host(currently connected to a wireless dongle)
Network
Wifi: rt2860sta
3G: None
Ethernet: None
NAND 512MiB 3,3V 8-bit
0x00000000-0x00040000 : "Bootloader"
0x00040000-0x00340000 : "Kernel"
0x00340000-0x00d40000 : "resource"
0x00d40000-0x11140000 : "File System 1"
0x11140000-0x20000000 : "User space"
The Bootloader is:
U-Boot 1.1.6-g794ab523-dirty (Aug 23 2010 - 00:52:53) for SMDK6410
The Environment has:
bootargs=console=ttySAC0,115200 loglevel=0 ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs
bootcmd=nand read c0008000 40000 300000;bootm c0008000
bootdelay=0
baudrate=115200
ethaddr=[MAC of Literati]
ipaddr=192.168.1.28
serverip=192.168.1.27
gatewayip=192.168.1.2
netmask=255.255.255.0
The Kernel is:
Linux (none) 2.6.24.2 #180 Mon Aug 23 00:49:07 CST 2010 armv6l GNU/Linux
The resource:
It begins with FILE_SECTION04 and then a file directory which shows logo.bin, update.bin, and zImage_rfs.
Here is the development website with more information http://literatidevs.com
Just got one of these today, actually. I looked up and down that board, but didn't find any info on enabling telnet. You have a link handy?
Pulled system logs (new random crashes) and noticed the following in last_kmsg. On CM11 m12, 4.17.605.5 firmware, and just got replacement M8 hardware.
1) Any concern regarding the "Board pid, pcbid, soc version doesn't match device tree!" message?
2) Whats chipset_bootmode(): reset_reason=0x77665501 mean?
Code:
[2487418] chipset_bootmode(): reset_reason=0x77665501
[2489587] DEBUG_DISABLE_WDT: 0x90!
[2490803] Boot Mode: 1
[2492799] Platform: hTCBmsm8974
[2495055] User Trial Debug Flag: 0
[3330697] [INFO] dts table: version = 1
[3333824] [INFO] dts table: num_entries = 46
[3338771] [DEBUG] Board pid:266, pcbid:0x80, soc version:0x10001
[3722365] [WARN] Board pid, pcbid, soc version doesn't match device tree!
[3727225] [WARN] Board pid:266, pcbid:0x80, soc version:0x10001
[3732000] [WARN] DTB pid:266, pcbid:0x4, soc version:0x10000
[3741028] [INFO] Loading matched device tree into memory... (addr:0x1e00000, dt_offset=0xFC800, dt_size=0x40800)
Platform: LG Qualcomm
Selected port: COM18
Selected model: D820
Reading info...
Initializing ADB...OK
Waiting for phone...OK
Model ID: Nexus 5
Firmware version:
Kernel version: 3.4.0-g9eb14ba ([email protected]) (gcc version 4.7 (GCC) ) #3
SMP PREEMPT Tue Nov 26 12:04:50 CST 201
Android version: 4.4.4
Hardware: Qualcomm MSM 8974 HAMMERHEAD (Flattened Device Tree)
ARMv7 Processor rev 0 (v7l)
Performed by 2.4.6 Software version.
--------------------------------------------------------------------------------
Checking data...OK
Platform: LG Qualcomm
Selected port: COM18
Selected model: D820
Reading info...
Initializing ADB...OK
Waiting for phone...OK
Model ID: Nexus 5
Firmware version:
Kernel version: 3.4.0-g9eb14ba ([email protected]) (gcc version 4.7 (GCC) ) #3
SMP PREEMPT Tue Nov 26 12:04:50 CST 201
Android version: 4.4.4
Hardware: Qualcomm MSM 8974 HAMMERHEAD (Flattened Device Tree)
ARMv7 Processor rev 0 (v7l)
Switching to Fastboot mode...OK
Unlocking Bootloader...
Bootloader is unlocked.
Writing Bootloader...OK
Please, wait while the phone will turn on and press "Ok" button.
Trying to enable Diagnostics ports...
Initializing ADB...OK
Waiting for phone...OK
Checking root access...
Phone is already rooted.
Diagnostics ports are enbled!
Switching to Serial Port...
Failed!
Performed by 2.4.6 Software version.
Any Solution ?
I'm not sure what the problem would be since the software and box should force flash the phone, assuming the phone is not physically damaged.
I have been repaired, But what is the Solution Of " Mobile network Not Available ' And ' No Signal " ?
Was the phone dropped? Possible loose internal connection? Phone is showing the correct imei?
Yes It's Have A Correct Imei , I'm not dropped the phone ...
is The problem Of Hardware ?
I want to root my tablet, but ı couldn't.
android version:4.2.2
CPU ABI : x86
CPU ABI2 : armeabi-v7a
hey guys..
i have a module which called bus multimedia.. i need root or read full backup of this device.. but there is no usb socket only exist RX TX pinout and i cannot connect it to pc over putty.. is anyone help me to read backup.?
t-mobile_mda said:
hey guys..
i have a module which called bus multimedia.. i need root or read full backup of this device.. but there is no usb socket only exist RX TX pinout and i cannot connect it to pc over putty.. is anyone help me to read backup.?
Click to expand...
Click to collapse
hey.. i removed the emmc and info..do u think that this device is android based..?
HiPower mode is On
Setting Interface to EasyJtag1/ISP_HiPower
Setting IO Levels to 3.3V
Setting Frequence to 21 Mhz
Setting BusWidth to 1 Bit
CMD Pullup Level: 2134 mV
CMD Active Level: 2609 mV
Setting HS Timing to Enabled
EMMC Device Information :
EMMC CID: 7001004D3732383038801500009374CA
EMMC CSD: D04F01320F5903FFFFFFFFEF8A400060
Manufacturer: KINGSTONE , NAME: M72808 , HEX: 4D3732383038 , S/N: 15000093 , Rev: 80
Manufacturer ID: 70 , OEM ID: 00 , Device Type: BGA (Discrete embedded) , Date: 7/2017
EMMC ROM 1 (Main User Data) Capacity: 7296 MB (0x0001C8000000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (0x000000400000)
EMMC RPMB Capacity: 4096 KB (0x000000400000) , Counter: 0 , Response: Clean
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x00 , Device not boot enabled
Boot Bus Config: 0x00 , x1 (sdr) or x4 (ddr) bus width in boot operation mode
H/W Reset Function [RST_N_FUNCTION]: 0x00 , RST_n signal is temporarily disabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition settings [PARTITION_SETTING_COMPLETED]: 0x00
EMMC Init completed
Backup saved: M72808_15000093_20220611_141710.extcsd (new backup)
Connected successfully
Operation: Scan PartitionTable from Source (Vendor: Binary Read/Write)
Scanning soft partitions from ROM2
GPT header is not found
Scanning soft partitions from ROM3
GPT header is not found
Scanning soft partitions from ROM1
GPT header is not found
MBR header is not found
You need a usb to uart device to get started on that board. You can find one online for about 3 dollars.