Related
Hello Everybody,
(hope this is the good section)
I try to investigate on low cost tablet with AllWinner F20 chip (chip near allwinner A10) for trying to create a rom. This tab work well for the price and
i can put it in bootloader mode, LiveSuit seem to find it. I dump my nanda partition and i need help to understand how does F20 boot ? no boot.afx found, only a strange app_demo.axf...This seem like a A10 relics files...
Do you think app_demo.axf can be the bootloader ?
Code:
# mkdir vnanda
# mount -o loop -t vfat nanda.dump vnanda
# tree vnanda
vnanda
├── boot.ini : Normaly used by boot.afx no ? (see content)
├── magic.bin : Normaly used by boot.afx no ? (see content)
├── app_demo.axf : Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [Build 349])
├── drv_de.drv : Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [Build 349])
├── drv_demo.drv : Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [Build 349])
├── drv_nand.drv : Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [Build 349])
├── drv_sd.drv : Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [Build 349])
├── wpower.drv : Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [Build 349])
└── linux
├── bImage : Linux Kernel (5.9 Mo)
├── linux.ini : Memory mapping ? (see content)
├── params : Kernel cmdline ? (see content)
│
├── android : Splash Polaroid
├── android.bmp : Bmp Polaroid
├── ??
│ ├── android : Splash Android
│ └── android.bmp : Bmp Android
├── ???
│ ├── android : Splash Polaroid
│ └── android.bmp : Bmp Polaroid
├── ???2
│ ├── android : Splash Difrnce
│ ├── android.bmp : Bmp Difrnce
│ └── opening24.bmp : Bmp Difrnce
├── epuda1
│ ├── android : Splash MemUp
│ └── android.bmp : Bmp MemUp
├── epuda2
│ ├── android : Splash ACL
│ ├── android24.bmp : Bmp ACL
│ └── android.bmp : Bmp ACL
└── youduo
├── android : Splash Tele System
└── TELE System 32.bmp : Bmp Tele System
7 directories, 27 files
boot.ini
Code:
[system]
start_os_name = linux
timeout = -1
display_device= 0
[linux]
magic.bin
Code:
a1sp9maKde37ee6c-6dc4-4d74-86f0-db32116efb53e0e40ccf-7a66-406b-88c3-415b4a62a8f7777622ab-6bd0-464f-9da5-4cc203e855ea8ce5671f-e8b5-442e-9300-2ee6836c538aabf5f481-c961-4895-8245-631f74851d0c2bbb4229-55a8-4929-a165-3f406f0ee441ab5d09a9-c4dc-44bb-a175-cfb7c978a062329ea51e-1ddc-44ff-ac09-9ef7b64e0c52a712e47d-13f7-4490-9fea-bdcd587b8a4a5ed4d4e6-0ba3-45c5-a778-3232a42d4d960a9b7466-d7b3-4087-b8ff-c51763b852a50cd78bb6-a6d5-43a8-8661-fb91abd346433e8a86ee-711e-49c1-ad54-b59dd01fe513e22b0d8b-647f-4417-a115-9806c5d64eec
linux.ini
Code:
[segment]
img_name = c:\linux\bImage
img_size = 0x2000000
img_base = 0x80008000
[segment]
img_name = c:\linux\params
img_size = 0x100
img_base = 0x83008000
[segment]
img_name = c:\linux\android
img_size = 0x200000
img_base = 0x88200000
[script_info]
script_base = 0x83000000
script_size = 0x8000
[logo_info]
logo_name = c:\linux\android.bmp
logo_address = 0x88000000
logo_show = 1
params
Code:
console=ttyS0,115200 root=/dev/nandb rw init=/init;
Thanks in advance
Rom1nux
Hello All,
For information i found a serial port exposed on this device, i try to get information but a dont build yet the max232 adapter
http://youtu.be/eabA3v0XoeY
Hope i can can bootloader information adapter will be build...
Full info here : http://forum.frandroid.com/topic/102352-polaroid-43-pc-tablet-midcf43-low-cost
Can someone know when exactly the linux kernel is really loaded ?
it's when Android splash aprear ? or it's loading during the Android splash ?
Thanks in advance for information about this stange boot part...
Rom1nux
Hello,
Yip ha, i got a full bootlog from F20
Setup
Quick 2N2222 adapter, badly build
Video
To check the boot timing
http://youtu.be/jN5YoBgeSzM
Bootlog
Code:
HELLO! BOOT0 is starting!
initializing SDRAM OK.
Succeed in opening nand flash.
Succeed in reading Boot1 file head.
The size of Boot1 is 0x00030000.
The file stored in 0X00000000 of block 2 is perfect.
Check is correct.
Ready to disable icache.
Succeed in loading Boot1.
Jump to Boot1.
begin to init file system
bat vol = 3951
1
mount successfully.
[MSG]: BootMain start
0
The all optional count is 1
only one os to boot
WRN:L412(BootOS\BootOS.c):test for multi os boot with display
WRN:L243(Common\ui\display_interface\display_interface.c):ERR: LCD not open
WRN:L60(..\OSAL_Cache.c):Length is ZERO!
start address = 0x80008000
jump to
[ 0.000000] timer_set_mode: periodic
[ 0.000000] Console: colour dummy device 80x30
[ 0.220000] bio: create slab <bio-0> at 0
[ 0.510000] request fb success!
[ 0.520000] [UART]debug disable!
[ 0.560000] The 0 disk name = BOOTFS, class name = DISK, disk size = 32768
[ 0.570000] The 1 disk name = LROOTFS, class name = DISK, disk size = 32768
[ 0.570000] The 2 disk name = LSYSTEMFS, class name = DISK, disk size = 524288
[ 0.580000] The 3 disk name = LDATAFS, class name = DISK, disk size = 1048576
[ 0.590000] The 4 disk name = UDISK, class name = DISK, disk size = 0
[ 0.600000] The 4 disk size = 2291712
[ 0.600000] part total count = 5
[ 0.690000] ------ pmem ioremap cached -------
[ 0.700000] CONFIG_USB_SW_SUN3I_USB0_OTG
[ 0.700000] [sw_hcd0]: usb host driver initialize........
[ 0.710000] [sw_hcd0]: [usb host]: usb_vbase = 0xf1c13000
[ 0.720000] [sw_hcd0]: [usb host]: sram_vbase = 0xf1c00000
[ 0.720000] [sw_hcd0]: [sw_hcd_host0]: close_usb_clock_ex
[ 0.730000] [sw_hcd0]: [sw_hcd_host0]: open_usb_clock
[ 0.770000] [sw_hcd0]: usbc_init_state = 1
[ 0.770000] [sw_hcd0]: platform is usb host
[ 0.770000] [sw_hcd0]: sw_hcd_host0: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
[ 0.790000] [sw_hcd0]: sw_hcd_host0: hw_ep 0shared, max 64
[ 0.790000] [sw_hcd0]: sw_hcd_host0: hw_ep 1tx, max 512
[ 0.800000] [sw_hcd0]: sw_hcd_host0: hw_ep 1rx, max 512
[ 0.810000] [sw_hcd0]: sw_hcd_host0: hw_ep 2tx, max 512
[ 0.810000] [sw_hcd0]: sw_hcd_host0: hw_ep 2rx, max 512
[ 0.820000] [sw_hcd0]: sw_hcd_host0: hw_ep 3tx, max 512
[ 0.820000] [sw_hcd0]: sw_hcd_host0: hw_ep 3rx, max 512
[ 0.830000] [sw_hcd0]: sw_hcd_host0: hw_ep 4tx, max 512
[ 0.840000] [sw_hcd0]: sw_hcd_host0: hw_ep 4rx, max 512
[ 0.840000] [sw_hcd0]: sw_hcd_host0: hw_ep 5tx, max 512
[ 0.850000] [sw_hcd0]: sw_hcd_host0: hw_ep 5rx, max 512
[ 0.850000] [sw_hcd0]: sw_hcd_init_controller: sw_hcd_host0: USB Host mode controller at f1c13000 using PIO, IRQ 38
[ 0.870000] WRN:L271(drivers/usb/sun3i_usb/hcd/core/sw_hcd_core.c):ERR: hcd is not enable
[ 0.880000] [sw_hcd0]: sw_usb_host0_disable start
[ 0.880000] -------sw_hcd0_soft_disconnect---------
[ 0.880000] [sw_hcd0]: INFO : USB VBus power OFF
[ 0.880000] WRN:L370(drivers/usb/sun3i_usb/hcd/core/sw_hcd_core.c):ERR: hcd is not enable
[ 0.890000] [sw_hcd0]: [sw_hcd_host0]: close_usb_clock
[ 0.900000] [sw_hcd0]: sw_usb_host0_disable end
[ 0.900000] [sw_hcd1]: usb host driver initialize........
[ 0.910000] [sw_hcd1]: [usb host]: usb_vbase = 0xf1c14000
[ 0.920000] [sw_hcd1]: [usb host]: sram_vbase = 0xf1c00000
[ 0.920000] [sw_hcd1]: open_usb_clock
[ 0.970000] [sw_hcd1]: usbc_init_state = 0
[ 0.970000] [sw_hcd1]: platform is usb host
[ 0.970000] [sw_hcd1]: sw_hcd_host1: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
[ 0.990000] [sw_hcd1]: sw_hcd_host1: hw_ep 0shared, max 64
[ 0.990000] [sw_hcd1]: sw_hcd_host1: hw_ep 1tx, max 512
[ 1.000000] [sw_hcd1]: sw_hcd_host1: hw_ep 1rx, max 512
[ 1.010000] [sw_hcd1]: sw_hcd_host1: hw_ep 2tx, max 512
[ 1.010000] [sw_hcd1]: sw_hcd_host1: hw_ep 2rx, max 512
[ 1.020000] [sw_hcd1]: sw_hcd_host1: hw_ep 3tx, max 512
[ 1.020000] [sw_hcd1]: sw_hcd_host1: hw_ep 3rx, max 512
[ 1.030000] [sw_hcd1]: sw_hcd_init_controller: sw_hcd_host1: USB Host mode controller at f1c14000 using PIO, IRQ 39
[ 1.040000] [sw_hcd1]: INFO : USB VBus power ON
[ 1.050000] sw_usb_disable_hcd1 start, clk_is_open = 1
[ 1.060000] sw_hcd_stop: sw_hcd disabled
[ 1.060000] [sw_hcd1]: INFO : USB VBus power OFF
[ 1.060000] [sw_hcd1]: close_usb_clock
[ 1.060000] -------sw_hcd1_soft_disconnect---------
[ 1.070000] sw_usb_disable_hcd1 end
[ 1.070000] [sw_hcd2]: usb host driver initialize........
[ 1.080000] [sw_hcd2]: [usb host]: usb_vbase = 0xf1c1e000
[ 1.080000] [sw_hcd2]: [usb host]: sram_vbase = 0xf1c00000
[ 1.090000] [sw_hcd2]: open_usb_clock
[ 1.130000] [sw_hcd2]: open_usb_clock, clk_is_open = 1
[ 1.130000] [sw_hcd2]: usbc_init_state = 1
[ 1.140000] [sw_hcd2]: platform is usb host
[ 1.140000] [sw_hcd2]: sw_hcd_host2: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
[ 1.150000] [sw_hcd2]: sw_hcd_host2: hw_ep 0shared, max 64
[ 1.160000] [sw_hcd2]: sw_hcd_host2: hw_ep 1tx, max 512
[ 1.170000] [sw_hcd2]: sw_hcd_host2: hw_ep 1rx, max 512
[ 1.170000] [sw_hcd2]: sw_hcd_host2: hw_ep 2tx, max 512
[ 1.180000] [sw_hcd2]: sw_hcd_host2: hw_ep 2rx, max 512
[ 1.180000] [sw_hcd2]: sw_hcd_host2: hw_ep 3tx, max 512
[ 1.190000] [sw_hcd2]: sw_hcd_host2: hw_ep 3rx, max 512
[ 1.200000] [sw_hcd2]: sw_hcd_init_controller: sw_hcd_host2: USB Host mode controller at f1c1e000 using PIO, IRQ 40
[ 1.210000] [sw_hcd2]: INFO : USB VBus power ON
[ 1.210000]
[ 1.210000] ------------IRQ SESSION_REQ-------------
[ 1.210000]
[ 1.210000] [sw_hcd2]: INFO : USB VBus power ON
[ 1.220000] [sw_udc]: udc_init: version 20080411
[ 1.230000] [sw_udc]: [sw_usb_udc]: binding gadget driver 'android_usb'
[ 1.230000] [sw_udc]: alloc request: ep(0xc059db70, ep0, 64), req(0xcf92f120)
[ 1.240000] WRN:L2369(drivers/usb/sun3i_usb/udc/sw_udc.c):ERR: usb device is not active
[ 1.250000] Gadget Android: controller 'sw_usb_udc' not recognized
[ 1.260000] WRN:L2369(drivers/usb/sun3i_usb/udc/sw_udc.c):ERR: usb device is not active
[ 1.270000] [sw_udc]: CONFIG_USB_GADGET_DUALSPEED
[ 1.270000] [sw_udc]: usbd_start_work
[ 1.280000] [sw_udc]: alloc request: ep(0xc059dc70, ep4-bulk, 512), req(0xcf969e60)
[ 1.290000] [sw_udc]: alloc request: ep(0xc059dc30, ep3-bulk, 512), req(0xcf969e20)
[ 1.300000] [sw_udc]: alloc request: ep(0xc059dc30, ep3-bulk, 512), req(0xcf969de0)
[ 1.310000] [sw_udc]: alloc request: ep(0xc059dc30, ep3-bulk, 512), req(0xcf969da0)
[ 1.310000] [sw_udc]: alloc request: ep(0xc059dc30, ep3-bulk, 512), req(0xcf969d60)
[ 1.330000] IR Initial OK
[ 1.330000] [sun3i-ts:inf] sun3its_init is invoked.
[ 1.340000] [sun3i-ts:inf] sun3i tp probe initial
[ 1.340000] [sun3i-ts:inf]
[ 1.350000] [sun3i-ts:inf] sun3i tp inital ok
[ 1.350000] sun3i RTC
[ 1.350000] f20_rtc_probe tmp_data = 16385
[ 1.370000] -----[cedar_dev] set ve clock -> 0x3040c019
[ 1.370000]
[ 1.370000] ------------IRQ CONNECT-------------
[ 1.370000]
[ 1.490000] [mmc]: awsmc controller unsing config sdc0 0, sdc1 0, sdc2 1, sdc3 0
[ 1.500000] [mmc]: awsmc.2: pdev->name: awsmc, pdev->id: 00000002
[ 1.510000] [mmc]: smc 2, source = video_pll0, src_clk = 297000000, mclk 99000000,
[ 1.510000] [mmc]: MMC Driver init host 2
[ 1.520000] [mmc]: awsmc.2: Initialisation Done.
[ 1.620000] m1 Audio successfully loaded..
[ 1.620000] registered taskstats version 1
[ 1.630000] incomplete xfer (32
[ 1.630000] incomplete xfer (32
[ 1.640000] incomplete xfer (32
[ 1.640000] incomplete xfer (32
[ 1.650000] incomplete xfer (32
[ 1.650000] incomplete xfer (32
[ 1.650000] incomplete xfer (32
[ 1.660000] incomplete xfer (32
[ 1.660000] incomplete xfer (32
[ 1.660000] incomplete xfer (32
[ 1.670000] incomplete xfer (32
[ 1.670000] incomplete xfer (32
[ 1.680000] incomplete xfer (32
[ 1.680000] incomplete xfer (32
[ 1.680000] incomplete xfer (32
[ 1.690000] incomplete xfer (32
[ 1.690000] incomplete xfer (32
[ 1.690000] incomplete xfer (32
[ 1.700000] [sw_hcd]: reset port.
[ 1.700000] incomplete xfer (32
[ 1.710000] incomplete xfer (32
[ 1.710000] incomplete xfer (32
[ 1.710000] incomplete xfer (32
[ 1.720000] incomplete xfer (32
[ 1.720000] incomplete xfer (32
[ 1.720000] incomplete xfer (32
[ 1.730000] incomplete xfer (32
[ 1.730000] incomplete xfer (32
[ 1.730000] incomplete xfer (32
[ 1.740000] incomplete xfer (32
[ 1.740000] incomplete xfer (32
[ 1.750000] incomplete xfer (32
[ 1.750000] incomplete xfer (32
[ 1.750000] incomplete xfer (32
[ 1.760000] [sw_hcd]: reset port stopped.
[ 1.760000] csr1: 0x2
[ 1.760000] csr2: 0x0
[ 1.770000] spurious?
[ 1.770000] incomplete xfer (32
[ 1.770000] incomplete xfer (32
[ 1.780000] incomplete xfer (32
[ 1.780000] incomplete xfer (32
[ 1.780000] incomplete xfer (32
[ 1.790000] incomplete xfer (32
[ 1.790000] incomplete xfer (32
[ 1.800000] incomplete xfer (32
[ 1.800000] incomplete xfer (32
[ 1.800000] incomplete xfer (32
[ 1.810000] incomplete xfer (32
[ 1.810000] incomplete xfer (32
[ 1.810000] incomplete xfer (32
[ 1.820000] incomplete xfer (32
[ 1.820000] incomplete xfer (32
[ 1.830000] incomplete xfer (32
[ 1.830000] incomplete xfer (32
[ 1.830000] incomplete xfer (32
[ 1.840000] [sw_hcd]: reset port.
[ 1.840000] incomplete xfer (32
[ 1.840000] incomplete xfer (32
[ 1.850000] f20_rtc_gettime
[ 1.850000] read time 2010-1-1 20:49:25
[ 1.860000] EXT2-fs (nandb): error: couldn't mount because of unsupported optional features (244)
[ 1.900000] [sw_hcd]: reset port stopped.
[ 1.900000] csr1: 0x2
[ 1.900000] csr2: 0x0
[ 1.960000] [sw_hcd]: sw_hcd_h_disable, epnum = 0
[ 1.960000] [sw_hcd]: sw_hcd_h_disable, epnum = 0
[ 1.990000] EXT4-fs (nandb): warning: maximal mount count reached, running e2fsck is recommended
[ 2.010000] VFS: Mounted root (ext3 filesystem) on device 93:8.
[ 2.040000] init: /init.rc: 244: invalid option 'root'
[ 2.040000] init: /init.rc: 244: invalid option 'root'
[ 2.340000] invalid bits_per_pixel :0 in var_to_fb
[ 2.380000] invalid bits_per_pixel :0 in var_to_fb
[ 2.520000] EXT4-fs (nandd): warning: maximal mount count reached, running e2fsck is recommended
[ 2.550000] init: not file /data/wipe_me
[ 2.650000] EXT4-fs (nandc): warning: maximal mount count reached, running e2fsck is recommended
[ 2.940000] EXT4-fs (nandd): warning: maximal mount count reached, running e2fsck is recommended
[ 3.050000] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
[ 3.060000] init: cannot find '/system/bin/memsicd', disabling 'memsicd'
[ 6.060000] [DISP]open
[ 7.760000] JBD2: Disabling barriers on nandb-8, not supported by device
[ 8.070000] JBD2: Disabling barriers on nandd-8, not supported by device
[ 8.070000] JBD2: Disabling barriers on nandc-8, not supported by device
[ 36.310000] [DISP]open
[ 36.450000] [DISP]open
[ 36.870000] [DISP]open
[ 38.150000] [sun3i-ts:dbg] suspend off
[ 38.720000] usb_wifi_host = 2
[ 38.730000] sw_usb_enable_hcd2 start, clk_is_open = 1
[ 38.730000] WRN:L1552(drivers/usb/sun3i_usb/hcd/hcd2/sw_hcd2.c):ERR: sw_usb_enable_hcd2, usb clock is open, can't open again
[ 38.750000]
[ 38.750000] rtw driver version=v3.1.2330.20110808
[ 38.750000] register rtw_netdev_ops to netdev_ops
[ 38.760000] CHIP TYPE: RTL8188C_8192C
[ 38.760000]
[ 38.760000] usb_endpoint_descriptor(0):
[ 38.770000] bLength=7
[ 38.770000] bDescriptorType=5
[ 38.780000] bEndpointAddress=81
[ 38.780000] wMaxPacketSize=200
[ 38.780000] bInterval=0
[ 38.790000] RT_usb_endpoint_is_bulk_in = 1
[ 38.790000]
[ 38.790000] usb_endpoint_descriptor(1):
[ 38.800000] bLength=7
[ 38.800000] bDescriptorType=5
[ 38.800000] bEndpointAddress=2
[ 38.800000] wMaxPacketSize=200
[ 38.810000] bInterval=0
[ 38.810000] RT_usb_endpoint_is_bulk_out = 2
[ 38.820000]
[ 38.820000] usb_endpoint_descriptor(2):
[ 38.820000] bLength=7
[ 38.820000] bDescriptorType=5
[ 38.830000] bEndpointAddress=3
[ 38.830000] wMaxPacketSize=200
[ 38.830000] bInterval=0
[ 38.840000] RT_usb_endpoint_is_bulk_out = 3
[ 38.840000]
[ 38.840000] usb_endpoint_descriptor(3):
[ 38.850000] bLength=7
[ 38.850000] bDescriptorType=5
[ 38.850000] bEndpointAddress=84
[ 38.860000] wMaxPacketSize=40
[ 38.860000] bInterval=1
[ 38.860000] RT_usb_endpoint_is_int_in = 4, Interval = 1
[ 38.870000] nr_endpoint=4, in_num=2, out_num=2
[ 38.870000]
[ 38.880000] USB_SPEED_HIGH
[ 39.000000] Chip Version ID: VERSION_NORMAL_TSMC_CHIP_88C.
[ 39.000000] RF_Type is 3!!
[ 39.020000] EEPROM type is E-FUSE
[ 39.020000] ====> ReadAdapterInfo8192C
[ 39.030000] Boot from EFUSE, Autoload OK !
[ 39.530000] i2c-1, xfer timeout
[ 39.530000] Assertion failed! drivers/hwmon/mxc_mma7660.c,85,mma7660_read_xyz,result>=0
[ 39.720000] EEPROMVID = 0x0bda
[ 39.720000] EEPROMPID = 0x8176
[ 39.730000] EEPROMCustomerID : 0x00
[ 39.730000] EEPROMSubCustomerID: 0x00
[ 39.730000] RT_CustomerID: 0x00
[ 39.740000] _ReadMACAddress MAC Address from EFUSE = 00:13:ef:51:30:7b
[ 39.750000] EEPROMRegulatory = 0x0
[ 39.750000] _ReadBoardType(0)
[ 39.750000] BT Coexistance = disable
[ 39.760000] RT_ChannelPlan: 0x02
[ 39.760000] _ReadPSSetting...bHWPwrPindetect(0)-bHWPowerdown(0) ,bSupportRemoteWakeup(0)
[ 39.770000] ### PS params=> power_mgnt(0),usbss_enable(0) ###
[ 39.780000] ### AntDivCfg(0)
[ 39.780000] readAdapterInfo_8192CU(): REPLACEMENT = 1
[ 39.780000] <==== ReadAdapterInfo8192C in 760 ms
[ 39.840000] rtw_macaddr_cfg MAC Address = 00:13:ef:51:30:7b
[ 39.840000] MAC Address from pnetdev->dev_addr= 00:13:ef:51:30:7b
[ 39.870000] bDriverStopped:1, bSurpriseRemoved:0, bup:0, hw_init_completed:0
[ 39.980000] +871x_drv - drv_open, bup=0
[ 40.410000] ===> FirmwareDownload91C() fw:Rtl819XFwImageArray_TSMC
[ 40.410000] fw_ver=v75, fw_subver=0, sig=0x88c0
[ 40.610000] fw download ok!
[ 40.620000] Set RF Chip ID to RF_6052 and RF type to 1T1R.
[ 41.360000] IQK:Start!!!
[ 41.430000] Path A IQK Success!!
[ 41.440000] Path A IQK Success!!
[ 41.440000] IQK: final_candidate is 0
[ 41.450000] IQK: RegE94=100 RegE9C=e RegEA4=fe RegEAC=2 RegEB4=0 RegEBC=0 RegEC4=0 RegECC=0
[ 41.450000] Path A IQ Calibration Success !
[ 41.680000] pdmpriv->TxPowerTrackControl = 1
[ 41.700000] MAC Address from REG_MACID = 00:13:ef:51:30:7b
[ 41.700000] MAC Address = 00:13:ef:51:30:7b
[ 41.700000] -871x_drv - drv_open, bup=1
[ 42.360000] [rtw_wx_set_pmkid] IW_PMKSA_FLUSH!
[ 42.360000] set_mode = IW_MODE_INFRA
[ 42.380000] [rtw_wx_set_pmkid] IW_PMKSA_FLUSH!
[ 44.060000] survey done event(11)
[ 44.110000] set_mode = IW_MODE_INFRA
[ 44.110000] wpa_set_auth_algs, AUTH_ALG_SHARED_KEY and AUTH_ALG_OPEN_SYSTEM [value:0x3]
[ 44.140000] wpa_set_encryption, crypt.alg = WEP
[ 44.140000] (1)wep_key_idx=0
[ 44.140000] wep, set_tx=1
[ 44.140000] ==> rtw_set_key algorithm(5),keyid(0),key_mask(1)
[ 44.140000] =>rtw_wx_set_essid
[ 44.140000] ssid=subway, len=6
[ 44.140000] new candidate: subway(00:0f:66:90:9b:f1) rssi:-65
[ 44.140000] rtw_select_and_join_from_scanned_queue: candidate: subway(00:0f:66:90:9b:f1)
[ 44.140000] <=rtw_wx_set_essid
[ 44.140000] link to new AP
[ 44.320000] link to Broadcom AP
[ 44.340000] OnAuthClient
[ 44.340000] OnAssocRsp
[ 44.340000] report_join_res(5)
[ 44.350000] HW_VAR_BASIC_RATE: BrateCfg(0x15d)
[ 44.380000] HTOnAssocRsp
[ 44.390000] update raid entry, mask=0x40000fff, arg=0x80
[ 44.470000] rtl8192c_set_FwJoinBssReport_cmd mstatus(1)
[ 44.480000] SetFwRsvdPagePkt
[ 44.480000] Set RSVD page location to Fw.
[ 44.480000] =>mlmeext_joinbss_event_callback
[ 45.700000] rtl8192c_dm_RF_Saving(): RF_Normal
[ 47.750000] rtl8192c_dm_RF_Saving(): RF_Save
[ 51.720000] rtw_set_pid set pid[2]=207
...
[ 95.450000] [sun3i-ts:dbg] [suspend_store]change before TPCTRL =0x200681
[ 95.460000] [sun3i-ts:dbg] [suspend_store]change before TP_INT_CTRL=0xb0000723
[ 95.470000] [sun3i-ts:dbg] suspend on
[ 96.970000] [mmc]: awsmc.2: ShutDown.
[ 97.010000] mmc_remove_host cf975800
[ 97.060000] unregister_pm_notifier
[ 97.060000] mmc_stop_host
[ 97.070000] device_del
[ 97.070000] led_trigger_unregister_simple
[ 97.070000] [sw_hcd2]: close_usb_clock
[ 97.080000] [sw_hcd1]: close_usb_clock
[ 97.080000] WRN:L164(drivers/usb/sun3i_usb/hcd/hcd1/sw_hcd1.c):ERR: clock handle is null, sie_clk(0xc05876bc), phy_clk(0xc0587338), open(0)
[ 97.090000] [sw_hcd0]: [sw_hcd_host0]: close_usb_clock
[ 97.490000] Power down.
Hope after analysis i can find the bootloader (boot1) code now...
cool, i was just looking at this option for my tablet
I have a pmid701c that looks to be very similar to yours. I was just looking at setting up a mmc/SD cable to console in. Have you tried hitting one of the buttons. On mine that is how to get to fel mode for flashing, wondering what happens if there is a console cable hooked up
Lots of people working on the pmid at freaktab.com by the way
Hello,
You can have look here http://www.sysfwlab.com and can you tell me more about :
I was just looking at setting up a mmc/SD cable to console in
Click to expand...
Click to collapse
Do you think about hooking the reader pin to a cable ?
Or did you speak about about bootable mmc/SD ?
I can do a try i you want
Bests regards
i did everything in the s-off guide and i always get stuck and the chmod 744/data/local/tmp/soffbin3 seems to not work. I flashed a sense 4 rom RebelROM and tried to do it again this is the result
C:\Users\N\Desktop\ADB + Fastboot + Drivers>adb devices
List of devices attached
HT253W310216 device
C:\Users\N\Desktop\ADB + Fastboot + Drivers>adb reboot bootloader
C:\Users\N\Desktop\ADB + Fastboot + Drivers>fastboot oem rebootRUU
... INFOStart Verify: 3
OKAY [ 0.084s]
finished. total time: 0.085s
C:\Users\N\Desktop\ADB + Fastboot + Drivers>fastboot flash zip PJ8312000-
p
sending 'zip' (36064 KB)... OKAY [ 3.581s]
writing 'zip'... INFOadopting the signature contained in
mage...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 3.694s
C:\Users\N\Desktop\ADB + Fastboot + Drivers>fastboot oem boot
... INFOBoot/Recovery signature checking...
INFOBoot/Recovery signature checking...
INFOsetup_tag addr=0x80400100 cmdline add=0xC02F50C4
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x2FD08
INFOTAG:hero panel = 0x4940047
INFOTAG:engineerid = 0x1
INFOTAG: PS ID = 0x0
INFOTAG: Gyro ID = 0x1
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is empty
INFOsetting->cid::11111111
INFOserial number: HT253W310216
INFOcommand line length =737
INFOactive commandline: poweron_status=32 reset_status=0 board_e
INFOlite.disable_uart3=0 diag.enabled=0 board_elite.debug_uart=0
INFO userdata_sel=0 androidboot.emmc=true androidboot.pagesize=2
INFO048 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.sf=1 td.td=1 t
INFOd.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=6
INFO94 imc_online_log=0 androidboot.efuse_info=NFSL androidboot
INFO.baseband=0.23a.32.09.29 androidboot.cid=11111111 androidboo
INFOt.devicerev=0 androidboot.batt_poweron=good_battery androidb
INFOoot.carrier=ALL andr
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=local
INFOaARM_Partion[5].name=cache
INFOaARM_Partion[6].name=userdata
INFOaARM_Partion[7].name=devlog
INFOaARM_Partion[8].name=pdata
INFOaARM_Partion[9].name=fat
INFOaARM_Partion[A].name=extra
INFOaARM_Partion.name=reserve
INFOaARM_Partion[C].name=radio
INFOaARM_Partion[D].name=adsp
INFOaARM_Partion[E].name=dsps
INFOaARM_Partion[F].name=wcnss
INFOaARM_Partion[10].name=radio_config
INFOaARM_Partion[11].name=modem_st1
INFOaARM_Partion[12].name=modem_st2
INFOaARM_Partion[13].name=reserve
INFOpartition number=20
INFOValid partition num=20
INFOsetting_get_bootmode() = 9
INFOram size = 0
INFOTZ_HTC_SVC_SET_DDR_MPU ret = 0
INFOsmem 90005000 (phy 90005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
INFOTZ_HTC_SVC_LOG_OPERATOR ret = 0
INFOTZ_HTC_SVC_ENC ret = 0
INFOTZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
INFOStart Verify: 3
INFOjump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
INFOnel_addr(0x80408000)
INFO-------------------hboot boot time:10558 msec
FAILED (status read failed (Too many links))
finished. total time: 6.482s
C:\Users\N\Desktop\ADB + Fastboot + Drivers>adb push soffbin3 /data/local/tmp/
662 KB/s (4751 bytes in 0.007s)
C:\Users\N\Desktop\ADB + Fastboot + Drivers>adb shell
[email protected]:/ # chmod 744 /data/local/tmp/soffbin3
chmod 744 /data/local/tmp/soffbin3
[email protected]:/ #
Try powering the phone all the way down and back up a few times. If that doesn't work, wiping cache and dalvik cache might help. Also fastboot getvar cid is a good command to run to make sure you have super cid.
Also, navigate to the fast boot folder you set up, open it the press shift and right click at the same time. Press the open command window here option and THEN run all of the commands. Make sure you have soft.bin in that folder also and it'll work
Sent from my One X using Tapatalk 4
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
That and put it on your c drives root because it my be to deep in the file system
Sent from my One X using Tapatalk 4
The problem isn't where the folder and files are stored. It's the fact that after pushing the soffbin3, the next line of command prompt seems to have the "adb shell [email protected]:/ #" text before he's able to issue the next command.
Sent from my Evita
Hi everybody, yesterday I install cyanogenmod 11 unofficial in my Huawei p6, I have unlocked the bootloader, all works fine, I used for a long time, after that I started charging from the computetr USB port , I went out for 3 hours, when I back the smartphone was off, I turned on, but the Logo Huawei ascend don't change, , after I go to recovery mode, I had installed TWRP 2.8.1.0, when I try to wipe, a error ocurred, "unable to mount /data" and other folders, after that I try to restored the original recovery, I used Fastboot, but nothing happens, the flash is good, but when I reboot in recovery mode appears TWRP, please help me, this smarphone is new, I bought them one month ago.
I'll be very grateful if someone helps me:crying::crying:
When I flash boot and recovery.
"F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot
erase boot
erasing 'boot'...
OKAY [ 0.002s]
finished. total time: 0.002s
F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot
flash boot boot.img
target reported max download size of 838860800 bytes
sending 'boot' (5658 KB)...
OKAY [ 0.188s]
writing 'boot'...
OKAY [ 0.300s]
finished. total time: 0.489s
F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot
erase recovery
erasing 'recovery'...
OKAY [ 0.005s]
finished. total time: 0.005s
F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot
flash recovery recovery.img
target reported max download size of 838860800 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.529s]
writing 'recovery'...
OKAY [ 0.664s]
finished. total time: 1.195s"
try this
try this forum out and if that is something you have tried pm me and ill help you to fix your problem
http://forum.xda-developers.com/showthread.php?t=2534420
Didn't work
Deltax82 said:
try this forum out and if that is something you have tried pm me and ill help you to fix your problem
http://forum.xda-developers.com/showthread.php?t=2534420
Click to expand...
Click to collapse
I was watching and I can not modify any folder in the root directory, eg put a file in "/ system", I reset the smarphone and the file disappears, I probe this command from the console windows "adb shell dmesg" and showed some errors, I think they are serious
---------------------------------------------------------------------------------------------------------------------------------
<7> [104.0, recovery] [13.020177] EXT4-fs (mmcblk0p19): ext4_orphan_cleanup: deleting unreferenced inode
<2> [104.0, recovery] [14.755787] EXT4-fs error (device mmcblk0p19): ext4_readdir: 214: inode # 113127: blo
ck 460238: comm recovery: path (unknown): bad entry in directory: rec_len is smaller than minimal - offset =
0 (0), inode = 16777216, rec_len = 0, name_len = 0
<3> [104.0, recovery] [14.755814] Aborting journal on device mmcblk0p19-8.
<2> [104.0, recovery] [14.755824] EXT4-fs (mmcblk0p19): Remounting filesystem read-only
<2> [104.0, recovery] [14.823290] EXT4-fs error (device mmcblk0p19): ext4_readdir: 214: inode # 113247: blo
ck 459687: comm recovery: path /data/data/de.robv.android.xposed.installer/app_webview: bad entry in direct
ory: rec_len% 4 = 0 - offset = 0 (0), inode = 1118398749, rec_len = 55815, name_len = 0!
---------------------------------------------------------------------------------------------------------------------------------
is a part, the there are more lines of this.
Format data
Wipe
Type 'Yes'
The phone (XT1031, 16GB, Republic Wireless, 4.4.4) is low use and nothing different was done the day it developed the problem. It worked Monday, on Wednesday it flashed indicator and the screen wouldn't power. It was hard-powered off (held power) and it wouldn't turn on again. The computer does not detect it. I have installed the 64-bit driver for my Windows 7 and am attempting to 'blank-flash' without success. Can anyone assist? Attached is the log. Thanks in advance.
C:\Users\Test\Desktop\blankflash>qboot.exe blank-flash
opening device: \\.\COM3
OKAY [ 0.016s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x3598E90
...chip-id = 0x801 (MSM8626)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.016s]
finding files
...programmer = programmer_8626.mbn
...singleimage = singleimage_8626.bin
OKAY [ 0.031s]
validating files
OKAY [ -0.000s]
switching to download mode
OKAY [ 0.016s]
greeting device for image downloading
OKAY [ 0.016s]
sending programmer
OKAY [ 0.047s]
flashing singleimage
Target LOG: Open multi failed, unknown error
Target ERROR: 7 - Open multi failed, unknown error
FAILED (sdl-transfer-image:send-image:sdl-open-multi:target error)
Anyone? Can anyone supply a copy of the corrupted file? Ideas? Any help would be appreciated.
Have a look here: http://forum.xda-developers.com/moto-g/development/guide-qhsusb-dload-workaround-t3182477
Hello all
Since nobody helped me with my mate 9, which did no sign of life, i started searching...on the mainboard.
I found the tespoint that gave me access to board, loaded fastboot in the ram, and now my MATE 9 shows in the fastboot devices.
This, i think ,is a big step for MATE 9 phones, which we might brick.
OK, so here is what i need. If it work, i promise that in maximum 1 day after testing this, i will post a guide for unbrick.
Code:
C:\Users\MONSTER>fastboot flash boot F:\dload\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (16208 KB)...
OKAY [ 0.549s]
writing 'boot'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 0.680s
This is the error style i got,when flashing boot,recovery,fastboot,and others.
Flashing system,product,vendor,vector, works.
As @Tkkg1994 posted here, https://forum.xda-developers.com/showpost.php?p=70410219&postcount=454
vrl.img really exists (i never heard of,and firstly,i thought that is URL.img ) )and may have something to do with partition table or smth like that.
I would need as many as partitions possible, since i have only those extracted from update.app.
So,please,anyone, if have time,try to help.
PS: @duraaraa - sir, i'm disturbing you again. but again,i think you can help.
What do you need, and how to help you?
Gesendet von meinem MHA-L29 mit Tapatalk
i need those img's
verlist.img
vrl.img
vrl_backup.img
dts.img
dtx.img
version.img
isp_boot.img
patch.img
persist.img
secure_storage.img
splash2.img
But i admit,that i have no idea how to get them from a working phone.Maybe others can help here.
I also have no idea how @Tkkg1994 obtained this partition list.
Hmm, the some are included in update.app , which can be extracted. But this is a basic thing you already know.
Indeed the most are not in updated.app like vrl.img dtx, version, isp, pathch persist etc. Maybe they are temporary build during update process.
well...with those in update.app already tried,they solve nothing,even if flashing is ok.
something is missing...
and btw....who seen before this error?
flash write prim vrl failure
Monster.Kali said:
I would need as many as partitions possible, since i have only those extracted from update.app.
Click to expand...
Click to collapse
You should have a clear understanding what is the purpose of these partitions, and how they are used.
If you are loading code into RAM directly (over debug UART or whatever), then it is possible to load Linux kernel (zImage)
with any custom ramdisk (+busybox). At this point "fastboot" is completely redundant, because flashing can be
done by 'cat foo.img > /dev/sdcNN'.
user4774 said:
You should have a clear understanding what is the purpose of these partitions, and how they are used.
If you are loading code into RAM directly (over debug UART or whatever), then it is possible to load Linux kernel (zImage)
with any custom ramdisk (+busybox). At this point "fastboot" is completely redundant, because flashing can be
done by 'cat foo.img > /dev/sdcNN'.
Click to expand...
Click to collapse
well, i don't have that clear understanding. i'm a noob.
imagine that at work, (gsm repair shop)i'm helped by software and hardware tools.
i never did that before,to load something into ram for x reason.
so right now, i try to learn things, and to bring my phone back to life.
what i tried to do,was like that. if i broke internal partitions,that after restart killed my phone, now i'm trying to get them back,maybe they solve something.
in ram, i loaded fastboot image and xloader.
that gave me access to fastboot.
until some clear instructions, i keep trying.
Monster.Kali said:
now i'm trying to get them back,maybe they solve something.
Click to expand...
Click to collapse
vrl and vrl_backup are first 2 partitions on /dev/sdd (/dev/block/sdd1 and /dev/block/sdd2)
Code:
Number Start (sector) End (sector) Size Name
1 128 255 512K vrl
2 256 383 512K vrl_backup
I have dumped them to the SD card with 'cat /dev/block/sdd1 > /storage/sdcard1/D1' and 'cat /dev/block/sdd2 > /storage/sdcard1/D2'
The contents seems to be identical
Code:
# md5sum /storage/sdcard1/D1
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D1
# md5sum /storage/sdcard1/D2
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D2
fastboot (aka bootloader) is the partition /dev/sdd24
Code:
24 151552 154623 12.0M fastboot_a
and the xloader is on a different 4MB "disk" /dev/sda
Code:
# fdisk -l /dev/block/sda
Note: sector size is 4096 (not 512)
Disk /dev/block/sda: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 1 heads, 8 sectors/track
Units: cylinders of 8 * 4096 = 32768 bytes
Disk /dev/block/sda doesn't contain a valid partition table
user4774 said:
vrl and vrl_backup are first 2 partitions on /dev/sdd (/dev/block/sdd1 and /dev/block/sdd2)
Code:
Number Start (sector) End (sector) Size Name
1 128 255 512K vrl
2 256 383 512K vrl_backup
I have dumped them to the SD card with 'cat /dev/block/sdd1 > /storage/sdcard1/D1' and 'cat /dev/block/sdd2 > /storage/sdcard1/D2'
The contents seems to be identical
Code:
# md5sum /storage/sdcard1/NEW/D1
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D1
# md5sum /storage/sdcard1/NEW/D2
06da2cbdf74659d24430114c104e08b8 /storage/sdcard1/D2
Click to expand...
Click to collapse
that's good.
it would be easier to do what i want, with cat, as you said.
i would follow partitions profile by tkkg1994, and write them to emmc.
but since i have only fastboot.....
Monster.Kali said:
but since i have only fastboot.....
Click to expand...
Click to collapse
Check which partitions you can extract from the full ROM/UPDATE.APP.
For your reference, my MHAL29C432 has 4 "scsi" disks /dev/sda (4MB xloader), /dev/sdb (4MB unused), /dev/sdc (frp stuff)
Code:
# fdisk -l /dev/block/sdc
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdc: 16384 sectors, 64.0M
Logical sector size: 4096
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 2047
Number Start (sector) End (sector) Size Name
1 128 255 512K frp
2 256 767 2048K persist
3 768 2047 5120K reserved1
and /dev/sdd
Code:
# fdisk -l /dev/block/sdd
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdd: 124928000 sectors, 576M
Logical sector size: 4096
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15615999
Number Start (sector) End (sector) Size Name
1 128 255 512K vrl
2 256 383 512K vrl_backup
3 384 2559 8704K modem_secure
4 2560 4095 6144K nvme
5 4096 20479 64.0M oeminfo
6 20480 28671 32.0M secure_storage
7 28672 36863 32.0M modem_om
8 36864 37887 4096K modemnvm_factory
9 37888 38911 4096K modemnvm_backup
10 38912 41983 12.0M modemnvm_img
11 41984 43007 4096K modemnvm_system
12 43008 63487 80.0M splash2
13 63488 129023 256M cache
14 129024 129535 2048K bootfail_info
15 129536 130047 2048K misc
16 130048 138239 32.0M reserved2
17 138240 139263 4096K reserved10
18 139264 141311 8192K hisee_fs
19 141312 145407 16.0M dfx
20 145408 149503 16.0M rrecord
21 149504 149567 256K fw_lpm3_a
22 149568 150527 3840K reserved3_a
23 150528 151551 4096K hisee_img_a
24 151552 154623 12.0M fastboot_a
25 154624 155647 4096K vector_a
26 155648 156159 2048K isp_boot_a
27 156160 159743 14.0M isp_firmware_a
28 159744 162815 12.0M fw_hifi_a
29 162816 164863 8192K teeos_a
30 164864 181247 64.0M recovery2_a
31 181248 185343 16.0M sensorhub_a
32 185344 193535 32.0M boot_a
33 193536 209919 64.0M recovery_a
34 209920 214015 16.0M dts_a
35 214016 214527 2048K trustfirmware_a
36 214528 228863 56.0M modem_fw_a
37 228864 241663 50.0M reserved4_a
38 241664 262143 80.0M modemnvm_update_a
39 262144 270335 32.0M patch_a
40 270336 278527 32.0M version_a
41 278528 479231 784M vendor_a
42 479232 528383 192M product_a
43 528384 577535 192M cust_a
44 577536 1777663 4688M system_a
45 1777664 1810431 128M reserved5
46 1810432 15615999 52.6G userdata
ok
got all missing img files from update.app with 7zip, not with update extractor.
on some of them, i have different sizes
here is the log of fastboot.
many of them flashed ok.
some not.
Code:
C:\Users\MONSTER>fastboot flash hisee_fs F:\dload\UPDATE\hisee_fs.img
target reported max download size of 471859200 bytes
sending 'hisee_fs' (8192 KB)...
OKAY [ 0.288s]
writing 'hisee_fs'...
OKAY [ 0.092s]
finished. total time: 0.386s
C:\Users\MONSTER>fastboot flash dfx F:\dload\UPDATE\dfx.img
target reported max download size of 471859200 bytes
sending 'dfx' (16384 KB)...
OKAY [ 0.561s]
writing 'dfx'...
OKAY [ 0.161s]
finished. total time: 0.728s
C:\Users\MONSTER>fastboot flash rrecord F:\dload\UPDATE\rrecord.img
target reported max download size of 471859200 bytes
sending 'rrecord' (16384 KB)...
OKAY [ 0.562s]
writing 'rrecord'...
OKAY [ 0.157s]
finished. total time: 0.725s
C:\Users\MONSTER>fastboot flash fw_lpm3_a F:\dload\UPDATE\fw_lpm3_a.img
target reported max download size of 471859200 bytes
sending 'fw_lpm3_a' (256 KB)...
OKAY [ 0.017s]
writing 'fw_lpm3_a'...
FAILED (remote: image verification error)
finished. total time: 0.061s
C:\Users\MONSTER>fastboot flash fw_lpm3 F:\dload\UPDATE\fw_lpm3_a.img
target reported max download size of 471859200 bytes
sending 'fw_lpm3' (256 KB)...
OKAY [ 0.015s]
writing 'fw_lpm3'...
FAILED (remote: image verification error)
finished. total time: 0.059s
C:\Users\MONSTER>fastboot flash reserved3_a F:\dload\UPDATE\reserved3_a.img
target reported max download size of 471859200 bytes
sending 'reserved3_a' (3840 KB)...
OKAY [ 0.136s]
writing 'reserved3_a'...
OKAY [ 0.056s]
finished. total time: 0.198s
C:\Users\MONSTER>fastboot flash hisee_img_a F:\dload\UPDATE\hisee_img_a.img
target reported max download size of 471859200 bytes
sending 'hisee_img_a' (4096 KB)...
OKAY [ 0.141s]
writing 'hisee_img_a'...
OKAY [ 0.058s]
finished. total time: 0.205s
C:\Users\MONSTER>fastboot flash fastboot_a F:\dload\UPDATE\fastboot_a.img
target reported max download size of 471859200 bytes
sending 'fastboot_a' (12288 KB)...
OKAY [ 0.423s]
writing 'fastboot_a'...
FAILED (remote: image verification error)
finished. total time: 0.466s
C:\Users\MONSTER>fastboot flash vector_a F:\dload\UPDATE\vector_a.img
target reported max download size of 471859200 bytes
sending 'vector_a' (4096 KB)...
OKAY [ 0.145s]
writing 'vector_a'...
FAILED (remote: image verification error)
finished. total time: 0.189s
C:\Users\MONSTER>fastboot flash vector F:\dload\UPDATE\vector_a.img
target reported max download size of 471859200 bytes
sending 'vector' (4096 KB)...
OKAY [ 0.145s]
writing 'vector'...
FAILED (remote: image verification error)
finished. total time: 0.189s
C:\Users\MONSTER>fastboot flash isp_boot_a F:\dload\UPDATE\isp_boot_a.img
target reported max download size of 471859200 bytes
sending 'isp_boot_a' (2048 KB)...
OKAY [ 0.074s]
writing 'isp_boot_a'...
OKAY [ 0.055s]
finished. total time: 0.135s
C:\Users\MONSTER>fastboot flash isp_firmware_a F:\dload\UPDATE\isp_firmware_a.im
g
target reported max download size of 471859200 bytes
sending 'isp_firmware_a' (14336 KB)...
OKAY [ 0.494s]
writing 'isp_firmware_a'...
FAILED (remote: image verification error)
finished. total time: 0.539s
C:\Users\MONSTER>fastboot flash fw_hifi_a F:\dload\UPDATE\fw_hifi_a.img
target reported max download size of 471859200 bytes
sending 'fw_hifi_a' (12288 KB)...
OKAY [ 0.424s]
writing 'fw_hifi_a'...
FAILED (remote: image verification error)
finished. total time: 0.467s
C:\Users\MONSTER>fastboot flash teeos_a F:\dload\UPDATE\teeos_a.img
target reported max download size of 471859200 bytes
sending 'teeos_a' (8192 KB)...
OKAY [ 0.286s]
writing 'teeos_a'...
FAILED (remote: image verification error)
finished. total time: 0.329s
C:\Users\MONSTER>fastboot flash recovery2_a F:\dload\UPDATE\recovery2_a.img
target reported max download size of 471859200 bytes
sending 'recovery2_a' (65536 KB)...
OKAY [ 2.230s]
writing 'recovery2_a'...
FAILED (remote: image verification error)
finished. total time: 2.273s
C:\Users\MONSTER>fastboot flash dts_a F:\dload\UPDATE\dts_a.img
target reported max download size of 471859200 bytes
sending 'dts_a' (16384 KB)...
OKAY [ 0.562s]
writing 'dts_a'...
FAILED (remote: image verification error)
finished. total time: 0.603s
C:\Users\MONSTER>fastboot flash trustfirmware_a F:\dload\UPDATE\trustfirmware_a.
img
target reported max download size of 471859200 bytes
sending 'trustfirmware_a' (2048 KB)...
OKAY [ 0.077s]
writing 'trustfirmware_a'...
FAILED (remote: image verification error)
finished. total time: 0.123s
C:\Users\MONSTER>fastboot flash modem_fw_a F:\dload\UPDATE\modem_fw_a.img
target reported max download size of 471859200 bytes
sending 'modem_fw_a' (57344 KB)...
OKAY [ 1.943s]
writing 'modem_fw_a'...
FAILED (remote: image verification error)
finished. total time: 1.988s
C:\Users\MONSTER>fastboot flash reserved4_a F:\dload\UPDATE\reserved4_a.img
target reported max download size of 471859200 bytes
sending 'reserved4_a' (51200 KB)...
OKAY [ 1.743s]
writing 'reserved4_a'...
OKAY [ 0.413s]
finished. total time: 2.162s
C:\Users\MONSTER>fastboot flash modemnvm_update_a F:\dload\UPDATE\modemnvm_updat
e_a.img
target reported max download size of 471859200 bytes
sending 'modemnvm_update_a' (81920 KB)...
OKAY [ 2.762s]
writing 'modemnvm_update_a'...
OKAY [ 0.648s]
finished. total time: 3.416s
C:\Users\MONSTER>fastboot flash patch_a F:\dload\UPDATE\patch_a.img
target reported max download size of 471859200 bytes
sending 'patch_a' (32768 KB)...
OKAY [ 1.117s]
writing 'patch_a'...
OKAY [ 0.275s]
finished. total time: 1.398s
C:\Users\MONSTER>fastboot flash version_a F:\dload\UPDATE\version_a.img F:\dload
\UPDATE\version_a.img
target reported max download size of 471859200 bytes
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\MONSTER>fastboot flash vendor_a F:\dload\UPDATE\vendor_a.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' (460726 KB)...
OKAY [ 16.785s]
writing 'vendor_a'...
OKAY [ 4.661s]
sending sparse 'vendor_a' (340470 KB)...
OKAY [ 12.505s]
writing 'vendor_a'...
OKAY [ 3.312s]
finished. total time: 37.272s
C:\Users\MONSTER>fastboot flash product_a F:\dload\UPDATE\product_a.img
target reported max download size of 471859200 bytes
sending 'product_a' (196608 KB)...
OKAY [ 6.675s]
writing 'product_a'...
OKAY [ 1.536s]
finished. total time: 8.218s
C:\Users\MONSTER>fastboot flash cust_a F:\dload\UPDATE\cust_a.img
target reported max download size of 471859200 bytes
sending 'cust_a' (196608 KB)...
OKAY [ 6.705s]
writing 'cust_a'...
OKAY [ 1.507s]
finished. total time: 8.218s
C:\Users\MONSTER>fastboot flash system_a F:\dload\UPDATE\system_a.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 593316360 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 112839176 is not a multiple of t
he block size 4096
sending sparse 'system_a' (457291 KB)...
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
OKAY [ 16.816s]
writing 'system_a'...
FAILED (remote: sparse flash write failure)
finished. total time: 22.552s
C:\Users\MONSTER>fastboot flash frp F:\dload\UPDATE\frp.img
target reported max download size of 471859200 bytes
sending 'frp' (512 KB)...
OKAY [ 0.025s]
writing 'frp'...
OKAY [ 0.022s]
finished. total time: 0.052s
C:\Users\MONSTER>fastboot flash persist F:\dload\UPDATE\persist.img
target reported max download size of 471859200 bytes
sending 'persist' (2048 KB)...
OKAY [ 0.075s]
writing 'persist'...
FAILED (remote: partition length get error)
finished. total time: 0.093s
C:\Users\MONSTER>fastboot flash reserved1 F:\dload\UPDATE\reserved1.img
target reported max download size of 471859200 bytes
sending 'reserved1' (5120 KB)...
OKAY [ 0.182s]
writing 'reserved1'...
FAILED (remote: partition length get error)
finished. total time: 0.204s
C:\Users\MONSTER>fastboot reboot
any idea of some img to load into ram?
or is there a method, that, allows me to flash files on emmc, over serial port?
i mean, serial port allows me to load them into ram.
but i wonder if it's capable to see the emmc.
@user4774 - i noticed that, flashing img's in the order that you gave me, beginning with vrl and vrl_backup, the write prim vrl failed error is gone.
so all of them,in that log,are flashed in order.
@ajsmsg78 - sir, i saw your no force encription boot image, and wanted to ask if you could help me with some file to load into ram, but which is capable to accept some others commands, excluding fastboot