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)
Related
Hello Everyone,
I have an i-mate Jamin, G3 I believe with no sign of life. The battery is 100% charged, and I cannot enter bootloader mode.
So I'm trying JTAG to write bootloader back to the phone.
My steps
1. I installed GIVEIO driver and started the service in Windows.
2. I made the JTAG pins using the resistance and connected the device.
3. In Jflash_MM I started start.bat and the phone was detected.
But next, I dunno what to do.
Sometimes I get error messages. Once I was even able to program. But I dunno what file to write to the device, and what is the address for this phone.
If anyone has restored the bootloader, please advice. Also is it possible on this phone or not.
Thnx
Output
C:\>start.bat
C:\>jflashmm pxa27x32 ebo_a.nb0 N 0 PAR
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: FFC2
Lower half reads: 0
Failed to read the Flash ID. Retrying 4 more times...
Failed to read the Flash ID. Retrying 3 more times...
Failed to read the Flash ID. Retrying 2 more times...
Failed to read the Flash ID. Retrying 1 more times...
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_ffff_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
C:\>jflashmm pxa27x32 ebo_a.nb0 N 3F40000 PAR
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Failed to read the Flash ID. Retrying 4 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 9800
Lower half reads: 0
Failed to read the Flash ID. Retrying 3 more times...
Failed to read the Flash ID. Retrying 2 more times...
Failed to read the Flash ID. Retrying 1 more times...
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_0_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
What is this Flash_0_2_32.dat all about?
Allright, I got the device flashed too, but still no bootloader....
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Found flash type: 28F256L18B
The last 43 percent of image file is all zeros
Would you like to save time by not programming that area? [y/n]: y
Unlocking block at address 0
Erasing block at address 0
Unlocking block at address 10000
Erasing block at address 10000
Unlocking block at address 20000
Erasing block at address 20000
Unlocking block at address 30000
Erasing block at address 30000
Unlocking block at address 40000
Erasing block at address 40000
Starting programming
Using BUFFER programming mode...
Writing flash at hex address 48cc0, 99.38% done
Programming done
C:\>jflashmm pxa27x32 ebo_a.nb0 N 3F40000 PAR
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Found flash type: 28F256L18B
The last 43 percent of image file is all zeros
Would you like to save time by not programming that area? [y/n]: y
Unlocking block at address 3f40000
Erasing block at address 3f40000
Unlocking block at address 3f80000
Erasing block at address 3f80000
Starting programming
Using BUFFER programming mode...
Writing flash at hex address 3f88c40, 99.34% done
Programming done
Dear All,
I am porting JB for QCom's msm8960 architecture (specifically for APQ8060A boards). I have downloaded several MSM8960
specific Code aurora releases and compiled them for msm8960. I have also downloaded Adreno user space drivers binaries.
After successful compilation when I run the Android image on the board, But a graphics related issue occurs.
'/system/bin/bootanimation' is not able to display anything on the screen and receives error while executing
eglSwapBuffers. Following are the Android 'main' logs for the error.
...
E/libEGL ( 515): eglApi.cpp : [eglSwapBuffers] dp->disp.dpy:1, s->surface:1
W/Adreno200-EGLSUB( 515): <GetBackBuffer:2172>: handle base address is NULL
W/Adreno200-ES20( 515): <gl2_surface_swap:43>: GL_OUT_OF_MEMORY
W/Adreno200-EGL( 515): <qeglDrvAPI_eglSwapBuffers:3477>: EGL_BAD_ALLOC
E/libEGL ( 515): [eglSwapBuffers] result = 0
...
W/Adreno200-EGLSUB( 515): <GetBackBuffer:2172>: handle base address is NULL
W/Adreno200-EGL( 515): <qeglDrvAPI_eglSwapBuffers:3477>: EGL_BAD_ALLOC
E/BootAnimation( 515): [BootAnimation.cpp][android] retval of eglSwapBuffers = 0
W/Adreno200-GSL( 515): <gsl_ldd_control:225>: ioctl code 0x40040921 (IOCTL_KGSL_SHAREDMEM_FREE) failed: errno 22 Invalid argument
...
Please let me know if any one of you has faced such problem.
I was doubting that Adreno user space drivers which I downloaded explicilty from QCom's website are not compatible with
the Android release, Therefore I tried with several Android releases but nothing works and shows the same error always.
Regards,
Nitin
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
Hello i have A8 2018 sm-a530f which has the emmc files corrupted , i need to revive and when i connect to the Easy Jtag Plus i get the error Partition info not found ,guide repair procedures and below is the log data
Setting interface to EasyJtag2/ISP
Setting bus width to 1 Bit
Setting frequence to 36 MHz
CMD Pullup Level: 445 mV
CMD Active Level: 1192 mV
EMMC Device Information :
EMMC CID: 150100424A5444345200523F424BB5A7
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacture : SAMSUNG , EMMC NAME: BJTD4R , HEX: 424A544434xx , S/N: 523F42xx , rev. 0x00
EMMC Manufacture ID: 0x15 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 11/2018
EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 0 , Response: Maybe not clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x48 , Boot from: ROM2 (Boot partition 1)
Boot Bus Config: 0x01 , width 4bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
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
Backup saved: BJTD4R_523F424B_20210404_201644.extcsd
EMMC Init completed.
Scanning soft partitions
Partition table not found
Get firmware version
Firmware info not found
NOTE: I HAVE THE BACK UP FILE BUT I DO NOT KNOW WHICH FILES TO LOAD , MAY SOMEONE CHECK THE ATTACHMENT AND TELL ME WHICH FILES TO LOAD LIKE (Select eMMC Image file *.bin) from THIS BACK UP.MAY SOMEONE TELL ME FROM THE BACK UP WHICH ONE IS ( eMMC ROM1 Image file, eMMC ROM2 Image file, eMMC ROM3 Image file, eMMC GP1 Image file, eMMC ExtCSD file. IN THEIR ORDER.
gruka said:
Hello i have A8 2018 sm-a530f which has the emmc files corrupted , i need to revive and when i connect to the Easy Jtag Plus i get the error Partition info not found ,guide repair procedures and below is the log data
Setting interface to EasyJtag2/ISP
Setting bus width to 1 Bit
Setting frequence to 36 MHz
CMD Pullup Level: 445 mV
CMD Active Level: 1192 mV
EMMC Device Information :
EMMC CID: 150100424A5444345200523F424BB5A7
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacture : SAMSUNG , EMMC NAME: BJTD4R , HEX: 424A544434xx , S/N: 523F42xx , rev. 0x00
EMMC Manufacture ID: 0x15 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 11/2018
EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 0 , Response: Maybe not clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x48 , Boot from: ROM2 (Boot partition 1)
Boot Bus Config: 0x01 , width 4bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
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
Backup saved: BJTD4R_523F424B_20210404_201644.extcsd
EMMC Init completed.
Scanning soft partitions
Partition table not found
Get firmware version
Firmware info not found
NOTE: I HAVE THE BACK UP FILE BUT I DO NOT KNOW WHICH FILES TO LOAD , MAY SOMEONE CHECK THE ATTACHMENT AND TELL ME WHICH FILES TO LOAD LIKE (Select eMMC Image file *.bin) from THIS BACK UP.MAY SOMEONE TELL ME FROM THE BACK UP WHICH ONE IS ( eMMC ROM1 Image file, eMMC ROM2 Image file, eMMC ROM3 Image file, eMMC GP1 Image file, eMMC ExtCSD file. IN THEIR ORDER.
Click to expand...
Click to collapse
I think there are not many users who are able to help in your case.
I only found this thread about emmc repair for your device:
Samsung A520f ,A530f Dead boot repair direct emmc file download
gsm flash,gsm flash file,gsm crack,combine file,easy firmware,frp file,gsm firmware,gsm file,samsung firmware,samsung dump,all android flashing tool,
www.awaismobile.com
Yes i downloaded the file ,how do i know this file is rom 1 ,Rom2,Rom 3, and ex PLEASE I DENTIFY FOR ME
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.