Database Info

The Infuse 4G Development Platform AKA UnBrickable Mod

Introduction
This is the 10th device to receive UnBrickable Mod! Lets go back to where it all started. It was proposed by XDA Member js22 that a device could be recovered without JTAG, using only it's native hardware. After months upon months of research, reading debug logs, reverse engineering of hardware and software, we came up with a solution.. Since I was the first to do it, I called it UnBrickable Mod. XDA Member Rebellos then reverse engineered a portion of the IBL into what is known as the HIBL(Hummingbird Interceptor BootLoader). We decided to call it this because the process goes like this: With UBM applied, the processor requests a code download from USB. We feed it the HIBL which reuses IBL code to authenticate with the Hummingbird's secure booting chain, then the Interceptor bootloader calls back and reuses the same IROM Download code used to download it, but we bypass security checks. This "Interception" of the boot sequence is why UnBrickable Mod works. The HIBL has proven to be so powerful and multipurpose that we've been able to package it into a one-click which works with ALL S5PC110 based devices with USB download capabilities.
I'd like to thank pdx 528e for donating the Infuse4G for this modification. This modification would not have been possible on this particular device without total removal of the processor.
After we verify this modification works This will be a replacement for JTAG. How could it possibly be better then JTAG? Let's count the ways....
1. The only part required is a wire.
2. No shipping time.
3. No cost for a box to interface the computer.
4. Permanent.
5. Can be done as a preventive measure.
6. Gives the ability to test new Bootloaders temporarily.
7. Allows development of the entire system.
8. Removes worry about flashing and acts as a backup.
After performing this mod:
Remove the battery, replace the battery, your phone will connect to the computer via USB and await commands. Otherwise it will pretty much act like an Infuse 4G. See the Special Instructions section.
Modification
You will need:
1. Get someone who knows what they're doing with a soldering iron. If they don't know what flux is, then they don't know what they're doing. You can send me a PM(my username @gmail.com) or Connexion2005(aka MobileTechVideos.com).
2. soldering iron - make sure it's sharp, if it's not sharp, then sharpen it, flux it and retin it.
3. flux
4. solder
5. tweezers
6. A relay (for the wire contained within)
getting started:
You will need a very small peice of wire. Tear apart the relay unravel the coil within and grab about 12cm~ of wire. The fact that it comes from a relay is important because relays generally have very small wire which are individually treated with a non-conductive coating.
Take the 12cm~ wire from the relay and tin the very edge of it. No more then 1/32". If you tin more then 1mm, cut off the excess. It is desirable to have a slight bit of excess solder on the tip of this wire.
performing the modification:
1. tear apart your phone... remove six(6) #1 phillips screws from the back. Then you can separate the back from the front. Make sure to take out your SIM and external SDCard before you do this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Remove the two(2) screws and four(4) electric connections securing the mainboard into the unit and remove the board.
3. remove the EM shield from the processor side.
4. remove xOM5 resistor.
5. Bridge the active side of xOM5 to the active side of xOM3. Most of the resistors in the top row will also work.
6. *OPTIONAL* for Bootloader development you will want UART output. You can use these points to a connection outside the device for UART. These points are exposed when the mainboard is secured to the unit. They are located on the JTAG port.
7. Reassemble the device.
Special Instructions
This replaces the battery charging sequence. The normal battery charging sequence can be activated by holding power for 4 seconds.
To turn on the device, and operate in normal mode, you must hold the power button for 5 seconds.
3 button Download mode works as usual, however you must not have the S5PC110 drivers installed on the computer. You can use your custom rom menu option, adb reboot download, or use a terminal to "reboot download". 301Kohm Factory Mode JIGs work as well, but you must press power to bypass the S5PC110 mode.
Conclusion
Congratulations. You now have a device which works like a KIT-S5PC110 with an OM Value of 29. Now get to developing some serious custom software.
reading material
Creating your own Samsung Bootloaders: http://forum.xda-developers.com/showthread.php?t=1233273
KIT-S5PC110 manual: http://www.mediafire.com/?94krzvvxksvmuxh
how to use DNW: http://tinyurl.com/dnw-how-to
Flash using openOCD and DNW: http://www.arm9board.net/wiki/index.php?title=Flash_using_OpenOCD_and_DNW
another DNW example: http://www.boardset.com/products/mv6410.php
ODroid dev center: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
drivers and utilities
This will be an ever expanding list
Windows Drivers http://forum.xda-developers.com/attachment.php?attachmentid=678937&d=1312590673
Windows Download Tool DNW: http://forum.xda-developers.com/attachment.php?attachmentid=678938&d=1312590673
Windows Command Line tool: http://forum.xda-developers.com/showpost.php?p=17202523&postcount=27
Linux DNW Utility: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
Linux ModeDetect tool: http://code.google.com/p/hummingbird-hibl/downloads/list
Linux Automated UnBricker:http://code.google.com/p/hummingbird-hibl/downloads/list
firmware
Bootloader Hello World by Rebellos http://forum.xda-developers.com/attachment.php?attachmentid=698077&d=1314105521
UnBrick tool http://forum.xda-developers.com/showthread.php?t=1242466

At this time I have not performed this modification. If you are in a pinch, please use this method. I will be performing this mod on my own device shortly.

We confirmed this device has got another iROM build, this means different HW revision of CPU.
HIBL for that will be released soon.

U are a genius Adam
Sent from my SAMSUNG-SGH-I997 using xda premium

JordanElliott said:
U are a genius Adam
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I second that. I'm ready to send my phone in.
I'm not a developer but I try to play one on XDA. Seriously I'm not a developer. DlevROM Yo!

Thanks. But my wife wont let me touch hers...
Edit. Her phone...LOL..
Sent from my SAMSUNG-SGH-I897 using XDA App

To much trouble .....but thanks anyway
Sent from my SAMSUNG-SGH-I997 using xda premium

To bad i'm a perfectionist that doesn't know how to solder; my baby is to new to put her through this lol.
Sent from my SGH-I997 using xda premium

oh man glad to see this here thanks

It would be good to mention a recommendation on soldering iron power. I mean I have 75 watt irons, and 150/400 watt guns, I like to use a bigger than needed iron because it reduces the heat up time and if you get it the first time reduces damage but only if you get it exactly at the right time.
But I wouldn't put any of those big tools near a computer or phone. I'd say 15 Watts is plenty, 25 is manageable if you are good and the to is sharp and clean, these small electronics are soldered with infrared and aren't even designed to have an iron used on them. Keep that in mind if you consider this mod! This can be tricky stuff that can damage your hardware.
Adam, has any progress been made on the galaxy s to boot Meego or Linux? I know you can install Linux to the sd card and run it along side Android using terminal emulator to access it like you posted in the captivate section a while back but I never saw it running with a GUI on the phone, if you Jeanne a way to accesses fluxbox with the phones touch screen, that would be cool even if I can't boot stair into Linux yet.

This is really great thx so does it mean the infuse can be like the hd2 run almost all the popular Smartphone operating systems ?

leeroy1034 said:
This is really great thx so does it mean the infuse can be like the hd2 run almost all the popular Smartphone operating systems ?
Click to expand...
Click to collapse
What it means is that if you are a developer that wants to develop a way to do those things you can do it without fear or bricking. I doubt it will lead to the infuse being the next hd2 but its a step in the direction.

I'm just hoping it means more roms to get my flashing addiction fix
Sent from my SAMSUNG-SGH-I997 using XDA App

The_Zodiac said:
I'm just hoping it means more roms to get my flashing addiction fix
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
I hope it leads to Meego for the infuse, I kinda dislike Android, its too slow, too fractured, we shouldn't need all this super fast hardware to get a smooth experience. but I have never used Meego. Even with a lack of a huge app market it has to be better than lame ios or win phone7.

Wow, reading these threads and the custom bootloaders threads makes me realize how much smarter some of you are than me. I can only thank you for your work done and time given to the community. Great work to everyone involved!

AJerman said:
Wow, reading these threads and the custom bootloaders threads makes me realize how much smarter some of you are than me.
Click to expand...
Click to collapse
Personally...
Naah, I've just got loads of time to waste for pretty useless things (mainly, once per few months something useful like HIBL comes out) :d

https://m.google.com/app/plus/mp/217/#~loop:aid=z12pxpqbdlikhv0rj04cd5gbiz3wg5eqqjg&view=activity

Ok. I'm having a problem. We have USB debug mode..
Code:
Bus 001 Device 035: ID 04e8:1234 Samsung Electronics Co., Ltd
It is enumerating properly in Linux.
It is uploading the HIBL properly as well.
Code:
[email protected]:~/Desktop$ sudo smdk-usbdl -a d0020000 -f ./HIBL.bin
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 034
=> loaded 24576 bytes from ./HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum 5d9c
=> usb_bulk_write() returned 24586
[email protected]:~/Desktop$
However, the device does not un-enumerate and re-enumerate as it usually does after receiving and executing the HIBL.
Here is the UART output from uploading HIBL.
Code:
Insert an OTG cable into the connector!
����
Uart negotiation Error
����
Here is a typical boot.
Code:
Uart negotiation Error
Insert an OTG cable into the connector!
Enumeration TimeOut Error
1
-----------------------------------------------------------
Samsung Primitive Bootloader (PBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
-----------------------------------------------------------
+n1stVPN 2688
+nPgsPerBlk 64
PBL found bootable SBL: Partition(3).
MAX8893_REG_ONOFF return val 1
MAX8893_REG_DISCHARGE return val ff
MAX8893_REG_LSTIME return val 8
MAX8893_REG_DVSRAMP return val 9
MAX8893_REG_BUCK return val 2
MAX8893_REG_LDO1 return val 2
MAX8893_REG_LDO1 new val e
MAX8893_REG_LDO2 return val e
MAX8893_REG_LDO2 new val 10
MAX8893_REG_ONOFF return val 1
MAX8893_REG_ONOFF new val 21
MAX8893_REG_ONOFF return val 21
MAX8893_REG_ONOFF new val 31
Set cpu clk. from 400MHz to 800MHz.
OM=0x29, device=OnenandMux(Audi)
IROM e-fused - Non Secure Boot Version.
-----------------------------------------------------------
Samsung Secondary Bootloader (SBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
Board Name: ARIES REV 03
Build On: May 19 2011 22:17:14
-----------------------------------------------------------
Re_partition: magic code(0x80040)
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] OneNAND nMID=0xec : nDID=0x50
[PAM: ] --FSR_PAM_Init
fsr_bml_load_partition: pi->nNumOfPartEntry = 12
partitions loading success
board partition information update.. source: 0x0
Now Read Images - ID : 1
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : IBL+PBL (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : PIT (0x1)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 1
===============================
ID : EFS (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 2
NO_UNITS : 40
===============================
ID : SBL (0x3)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 42
NO_UNITS : 5
===============================
ID : SBL2 (0x4)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 47
NO_UNITS : 5
===============================
ID : PARAM (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 52
NO_UNITS : 20
===============================
ID : KERNEL (0x6)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 72
NO_UNITS : 30
===============================
ID : RECOVERY (0x7)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 102
NO_UNITS : 30
===============================
ID : FACTORYFS (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 132
NO_UNITS : 1146
===============================
ID : DBDATAFS (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1278
NO_UNITS : 536
===============================
ID : CACHE (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : 130
===============================
ID : MODEM (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1944
NO_UNITS : 60
===============================
loke_init: j4fs_open success..
load_lfs_parameters valid magic code and version.
reading nps status file is successfully!.
nps status=0x504d4f43
load_debug_level reading debug level from file successfully(0x574f4c44).
init_fuel_gauge: vcell = 3660mV, soc = 13
check_quick_start_condition- Voltage: 3660.0, Linearized[0/15/30], Capacity: 12
init_fuel_gauge: vcell = 3660mV, soc = 13, rcomp = d01f
reading nps status file is successfully!.
nps status=0x504d4f43
PMIC_IRQ1 = 0xc0
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x1
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0x0
PMIC_STATUS2 = 0x0
get_debug_level current debug level is 0x574f4c44.
aries_process_platform: Debug Level Low
keypad_scan: key value ----------------->= 0x0
CONFIG_ARIES_REV:48 , CONFIG_ARIES_REV03:48
check_download: micorusb_status1 = 0, key_value = 0
aries_process_platform: final s1 booting mode = 0
DISPLAY_PATH_SEL[MDNIE 0x1]is on
MDNIE setting Init start!!
vsync interrupt is off
video interrupt is off
[fb0] turn on
MDNIE setting Init end!!
lcd_power_on_ld9040
s6e63m0_c110_spi_read_byte-------------------------: 86
DA lcd ID1 = 86
s6e63m0_c110_spi_read_byte-------------------------: 48
DB lcd ID2 = 48
s6e63m0_c110_spi_read_byte-------------------------: 44
DC lcd ID3 = 44
LCD_ID == 3
Autoboot (0 seconds) in progress, press any key to stop
get_debug_level current debug level is 0x574f4c44.
get_debug_level current debug level is 0x574f4c44.
boot_kernel: Debug Level Low
FOTA Check Bit
Read BML page=, NumPgs=
FOTA Check Bit (0x871f8801)
Load Partion idx = (6)
..............................done
Kernel read success from kernel partition no.6, idx.6.
setting param.serialnr=0x31352402 0x61dc00ec
setting param.board_rev=0x30
setting param.cmdline=console=ttySAC2,115200 loglevel=4
Starting kernel at 0x32000000...
Uncompressing Linux.............................................................
[ 0.000000] copy: bad source 0
[ 0.000000] mout_audss: bad source 0
[ 0.090119] KERNEL:kernel_sec_get_debug_level_from_boot=0x574f4c44
[ 0.094853] KERNEL:magic_number=0x0 DEBUG LEVEL low!!
[ 0.099864] (kernel_sec_set_upload_cause) : upload_cause set 0
[ 0.804603] irq requested hpd irq
[ 0.850107] --------A1026 i2c driver A1026_probe called
[ 0.853875] --------A1026_probe: device not supported
[ 0.859131] --------A1026_driver_init successful
[ 0.863514] --------A1026_dev_powerup called
[ 3.007976] Failed to request gpio touchkey_init:738
[ 3.011482] Failed to request gpio touchkey_init:740
[ 12.856445] init: [disk_config] initialize_mbr_flash for S1_EUR
[ 12.860891] init: [disk_config] [Disk Size (16005464064), (15630336k), secto]
[ 12.870565] init: [disk_config] calc_pte_of_disk -> start 64 num lba 2732844
[ 12.879153] init: [disk_config] calc_pte_of_disk -> start 27328512 num lba 3
[ 12.888197] init: [disk_config] compare_partition -> num_part 0 , offset (44)
[ 12.896007] init: [disk_config] [ target -> Disk0 : 13992165376 (13664224k) ]
[ 12.905162] init: [disk_config] Match partition table entry ... skip(0)
[ 12.911775] init: [disk_config] compare_partition -> num_part 1 , offset (46)
[ 12.919575] init: [disk_config] [ target -> Disk1 : 2013265920 (1966080k) 00]
[ 12.928584] init: [disk_config] Match partition table entry ... skip(1)
[ 12.935185] init: [disk_config] compare_partition -> num_part 2 , offset (47)
[ 12.942987] init: [disk_config] [ target -> Disk2 : 0 (0k) 00:00:00000000:00]
[ 12.950698] init: [disk_config] Match partition table entry ... skip(2)
[ 12.957303] init: [disk_config] compare_partition -> num_part 3 , offset (49)
[ 12.965104] init: [disk_config] [ target -> Disk3 : 0 (0k) 00:00:00000000:00]
[ 12.972811] init: [disk_config] Match partition table entry ... skip(3)
[ 12.979399] init: [disk_config] bNeedRoot : 0x00
[ 12.990828] init: cannot open '/initlogo.rle'
[ 13.075055] Failed to request FM_RESET!
[ 13.172981] init: [disk_config] :::: /dev/block/mmcblk0p1 :::::
[ 13.180732] init: [disk_config] vfat_identify -> ok
[ 13.184160] init: [disk_config] :::: /dev/block/mmcblk0p2 :::::
[ 13.190129] init: [disk_config] Error ::rfs_identify -> oem_name ()
[ 13.196466] init: [disk_config] rfs_identify -> failed
[ 13.202486] init: [disk_config] Error ::rfs_identify -> oem_name ()
[ 13.207833] init: [disk_config] rfs_identify -> failed
[ 13.213839] init: [disk_config] Error ::rfs_identify -> oem_name ()
[ 13.219189] init: [disk_config] rfs_identify -> failed
[ 13.225210] init: [disk_config] rfs_format -> /system/bin/fat.format -F 32 -
[ 13.252568] init: [disk_config] rfs_format -> ok[BIF: ] FSR VERSION: FSRM
[ 13.552104] init: cannot find '/system/bin/false', disabling 'noplaylogos'
[ 13.586570] init: cannot find '/system/etc/install-recovery.sh', disabling ''
sh: can't access tty; job control turned off
$ [ 19.506760] init: no such service 'bootanim'
[ 43.514858] init: no such service 'bootanim'
[ 61.035132] init: sys_prop: permission denied uid:1000 name:dpm.allowcamera
[ 71.204861] init: untracked pid 3290 exited
����
Uart negotiation Error
Rebellos, any ideas?

Updated 3rd post in this thread. We found out another S5PC110 iROM revision for the first time.

It's working. Excellent work Rebellos!
This log shows HIBL, then SBL going into download mode. Then a heimdall print-pit was excuted and the device rebooted.
Code:
����
Uart negotiation Error
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v1.0
Copyright (C) Rebellos 2011
-------------------------------------------------------------
Calling IBL Stage2 ...OK
Testing DRAM1 ...OK
iRAM reinit ...OK
cleaning OTG context ...OK
Chain of Trust has been successfully compromised.
Begin unsecure download now...
0x00000000BL3 EP: 0x40244000
Download complete, hold download mode key combination.
Starting BL3 in...
Set cpu clk. from 400MHz to 800MHz.
OM=0x29, device=OnenandMux(Audi)
IROM e-fused - Non Secure Boot Version.
-----------------------------------------------------------
Samsung Secondary Bootloader (SBL) v3.0
Copyright (C) Samsung Electronics Co., Modified by Rebell
Build On: Jun 8 2011 21:44:47
-----------------------------------------------------------
Re_partition: magic code(0x0)
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] OneNAND nMID=0xec : nDID=0x50
[PAM: ] --FSR_PAM_Init
fsr_bml_load_partition: pi->nNumOfPartEntry = 12
partitions loading success
board partition information update.. source: 0x0
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : IBL+PBL (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : PIT (0x1)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 1
===============================
ID : EFS (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 2
NO_UNITS : 40
===============================
ID : SBL (0x3)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 42
NO_UNITS : 5
===============================
ID : SBL2 (0x4)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 47
NO_UNITS : 5
===============================
ID : PARAM (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 52
NO_UNITS : 20
===============================
ID : KERNEL (0x6)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 72
NO_UNITS : 30
===============================
ID : RECOVERY (0x7)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 102
NO_UNITS : 30
===============================
ID : FACTORYFS (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 132
NO_UNITS : 1146
===============================
ID : DBDATAFS (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1278
NO_UNITS : 536
===============================
ID : CACHE (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : 130
===============================
ID : MODEM (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1944
NO_UNITS : 60
===============================
loke_init: j4fs_open success..
load_lfs_parameters valid magic code and version.
reading nps status file is successfully!.
nps status=0x504d4f43
load_debug_level reading debug level from file successfully(0x574f4c44).
init_fuel_gauge: vcell = 4102mV, soc = 80
check_quick_start_condition_with_charger- Voltage: 4102.50000, Linearized[64/79/94], Capacity: 83
init_fuel_gauge: vcell = 4102mV, soc = 80, rcomp = d01f
reading nps status file is successfully!.
nps status=0x504d4f43
PMIC_IRQ1 = 0x28
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x0
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0x40
PMIC_STATUS2 = 0x2c
get_debug_level current debug level is 0x574f4c44.
aries_process_platform: Debug Level Low
keypad_scan: key value ----------------->= 0x20
CONFIG_ARIES_REV:48 , CONFIG_ARIES_REV03:48
reading nps status file is successfully!.
nps status=0x504d4f43
==> Welcome to ARIES!
==> Entering usb download mode..
DISPLAY_PATH_SEL[MDNIE 0x1]is on
MDNIE setting Init start!!
vsync interrupt is off
video interrupt is off
[fb0] turn on
MDNIE setting Init end!!
Error : Current Mode is Host
EP2: 0, 2, 0; len=7
EP2: 0, 2, 0; len=7
sug: IN EP asserted
Error:Invalid connection string!
Error:Invalid connection string!
- Odin is connected!
set_nps_update_start: set nps start flag successfully.
process_packet: request id(100), data id(0)
process_rqt_init: platform number(0x0), revision(0x0)
process_packet: request id(100), data id(1)
process_packet: request id(101), data id(1)
.Done.
read 1 units.
check_pit_integrity: valid pit magic code.
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(2)
process_packet: request id(101), data id(3)
process_packet: request id(103), data id(0)
process_rqt_close: xmit completed!
set_nps_update_completed: set nps completed flag successfully.
process_packet: request id(103), data id(1)
process_rqt_close: target reset!
ARIES MAGIC_ADDR=0x0 / INFORM5=0x12345678
1
-----------------------------------------------------------
Samsung Primitive Bootloader (PBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
-----------------------------------------------------------
+n1stVPN 2688
+nPgsPerBlk 64
PBL found bootable SBL: Partition(3).
MAX8893_REG_ONOFF return val 1
MAX8893_REG_DISCHARGE return val ff
MAX8893_REG_LSTIME return val 8
MAX8893_REG_DVSRAMP return val 9
MAX8893_REG_BUCK return val 2
MAX8893_REG_LDO1 return val 2
MAX8893_REG_LDO1 new val e
MAX8893_REG_LDO2 return val e
MAX8893_REG_LDO2 new val 10
MAX8893_REG_ONOFF return val 1
MAX8893_REG_ONOFF new val 21
MAX8893_REG_ONOFF return val 21
MAX8893_REG_ONOFF new val 31
Set cpu clk. from 400MHz to 800MHz.
OM=0x29, device=OnenandMux(Audi)
IROM e-fused - Non Secure Boot Version.
-----------------------------------------------------------
Samsung Secondary Bootloader (SBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
Board Name: ARIES REV 03
Build On: May 19 2011 22:17:14
-----------------------------------------------------------
Re_partition: magic code(0x0)
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] OneNAND nMID=0xec : nDID=0x50
[PAM: ] --FSR_PAM_Init
fsr_bml_load_partition: pi->nNumOfPartEntry = 12
partitions loading success
board partition information update.. source: 0x0
Now Read Images - ID : 1
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : IBL+PBL (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : PIT (0x1)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 1
===============================
ID : EFS (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 2
NO_UNITS : 40
===============================
ID : SBL (0x3)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 42
NO_UNITS : 5
===============================
ID : SBL2 (0x4)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 47
NO_UNITS : 5
===============================
ID : PARAM (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 52
NO_UNITS : 20
===============================
ID : KERNEL (0x6)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 72
NO_UNITS : 30
===============================
ID : RECOVERY (0x7)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 102
NO_UNITS : 30
===============================
ID : FACTORYFS (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 132
NO_UNITS : 1146
===============================
ID : DBDATAFS (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1278
NO_UNITS : 536
===============================
ID : CACHE (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : 130
===============================
ID : MODEM (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1944
NO_UNITS : 60
===============================
loke_init: j4fs_open success..
load_lfs_parameters valid magic code and version.
reading nps status file is successfully!.
nps status=0x504d4f43
load_debug_level reading debug level from file successfully(0x574f4c44).
init_fuel_gauge: vcell = 4101mV, soc = 80
check_quick_start_condition_with_charger- Voltage: 4101.25000, Linearized[67/82/97], Capacity: 83
init_fuel_gauge: vcell = 4101mV, soc = 80, rcomp = d01f
reading nps status file is successfully!.
nps status=0x504d4f43
PMIC_IRQ1 = 0x0
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x0
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0x40
PMIC_STATUS2 = 0x2c
get_debug_level current debug level is 0x574f4c44.
aries_process_platform: Debug Level Low
keypad_scan: key value ----------------->= 0x0
CONFIG_ARIES_REV:48 , CONFIG_ARIES_REV03:48
check_download: micorusb_status1 = 4, key_value = 0
aries_process_platform: final s1 booting mode = 0
DISPLAY_PATH_SEL[MDNIE 0x1]is on
MDNIE setting Init start!!
vsync interrupt is off
video interrupt is off
[fb0] turn on
MDNIE setting Init end!!
lcd_power_on_ld9040
s6e63m0_c110_spi_read_byte-------------------------: 86
DA lcd ID1 = 86
s6e63m0_c110_spi_read_byte-------------------------: 48
DB lcd ID2 = 48
s6e63m0_c110_spi_read_byte-------------------------: 44
DC lcd ID3 = 44
LCD_ID == 3
Autoboot (0 seconds) in progress, press any key to stop
get_debug_level current debug level is 0x574f4c44.
get_debug_level current debug level is 0x574f4c44.
boot_kernel: Debug Level Low
FOTA Check Bit
Read BML page=, NumPgs=
FOTA Check Bit (0x871f8801)
Load Partion idx = (6)
..............................done
Kernel read success from kernel partition no.6, idx.6.
setting param.serialnr=0x31352402 0x61dc00ec
setting param.board_rev=0x30
setting param.cmdline=console=ttySAC2,115200 loglevel=4
Starting kernel at 0x32000000...
Uncompressing Linux..............................................................................................................
[ 0.000000] copy: bad source 0
[ 0.000000] mout_audss: bad source 0
[ 0.090122] KERNEL:kernel_sec_get_debug_level_from_boot=0x574f4c44
[ 0.094863] KERNEL:magic_number=0x0 DEBUG LEVEL low!!
[ 0.099874] (kernel_sec_set_upload_cause) : upload_cause set 0
[ 0.802403] irq requested hpd irq
[ 0.846178] --------A1026 i2c driver A1026_probe called
[ 0.849942] --------A1026_probe: device not supported
[ 0.855208] --------A1026_driver_init successful
[ 0.859587] --------A1026_dev_powerup called
[ 3.004125] Failed to request gpio touchkey_init:738
[ 3.007639] Failed to request gpio touchkey_init:740
[ 12.613596] init: [disk_config] initialize_mbr_flash for S1_EUR
[ 12.617987] init: [disk_config] [Disk Size (16005464064), (15630336k), sector_size 512 :: num_lba 31260672 ]
[ 12.627716] init: [disk_config] calc_pte_of_disk -> start 64 num lba 27328448 next : 27328512
[ 12.636293] init: [disk_config] calc_pte_of_disk -> start 27328512 num lba 3932160 next : 31260672
[ 12.645348] init: [disk_config] compare_partition -> num_part 0 , offset (446)(0x1be)
[ 12.653148] init: [disk_config] [ target -> Disk0 : 13992165376 (13664224k) 00:0c:00000040:01a0ffc0 ]
[ 12.662313] init: [disk_config] Match partition table entry ... skip(0)
[ 12.668924] init: [disk_config] compare_partition -> num_part 1 , offset (462)(0x1ce)
[ 12.676721] init: [disk_config] [ target -> Disk1 : 2013265920 (1966080k) 00:0c:01a10000:003c0000 ]
[ 12.685729] init: [disk_config] Match partition table entry ... skip(1)
[ 12.692391] init: [disk_config] compare_partition -> num_part 2 , offset (478)(0x1de)
[ 12.700135] init: [disk_config] [ target -> Disk2 : 0 (0k) 00:00:00000000:00000000 ]
[ 12.707841] init: [disk_config] Match partition table entry ... skip(2)
[ 12.714454] init: [disk_config] compare_partition -> num_part 3 , offset (494)(0x1ee)
[ 12.722244] init: [disk_config] [ target -> Disk3 : 0 (0k) 00:00:00000000:00000000 ]
[ 12.729962] init: [disk_config] Match partition table entry ... skip(3)
[ 12.736538] init: [disk_config] bNeedRoot : 0x00
[ 12.748654] init: cannot open '/initlogo.rle'
[ 12.832898] Failed to request FM_RESET!
[ 12.931189] init: [disk_config] :::: /dev/block/mmcblk0p1 :::::
[ 12.938955] init: [disk_config] vfat_identify -> ok
[ 12.942398] init: [disk_config] :::: /dev/block/mmcblk0p2 :::::
[ 12.948354] init: [disk_config] Error ::rfs_identify -> oem_name ()
[ 12.954696] init: [disk_config] rfs_identify -> failed
[ 12.960739] init: [disk_config] Error ::rfs_identify -> oem_name ()
[ 12.966056] init: [disk_config] rfs_identify -> failed
[ 12.972089] init: [disk_config] Error ::rfs_identify -> oem_name ()
[ 12.977424] init: [disk_config] rfs_identify -> failed
[ 12.983432] init: [disk_config] rfs_format -> /system/bin/fat.format -F 32 -S 4096 -s 4 /dev/block/mmcblk0p2
[ 13.009915] init: [disk_config] rfs_format -> ok[BIF: ] FSR VERSION: FSR_1.2.1p1_b139_RTM
[ 13.310236] init: cannot find '/system/bin/false', disabling 'noplaylogos'
[ 13.337944] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
sh: can't access tty; job control turned off
$ [ 19.257644] init: no such service 'bootanim'
[ 39.060649] init: sys_prop: permission denied uid:1000 name:wifi.interface
[ 44.151646] init: no such service 'bootanim'
the commands run were:
Code:
sudo smdk-usbdl -a d0020000 -f ./Infuse_HIBL_3.bin
sudo smdk-usbdl -a d40244000 -f ./Sbl.bin
You can get these pre-release binaries here: http://www.mediafire.com/file/yewg81mwdklb357/HIBLandSblBinaries.zip
Everything is working but I have not yet tested flashing. Flashing should go off without a hitch. You will use Odin 1.7 or 1.8.

HTC One XL (evita) keeps dying on me..

I had the problem on stock few month back and thought it was time for me to go custom Rom while wauting for my OnePlus invite. So I installed Cyanogenmod. I did my homework, I think, and got started with CyanogenMod 11 M6. I am:
- Bootloader 2.18.0000 unlocked ( and *** TAMPERED *** ) ? for whatever that means.
- S-ON (so I use `./fastboot flash boot boot.img` everytime)
- non rooted (because some app I need do not like rooted phone), but CWM is quite flexible for that,
I use CWM revovery:recovery-clockwork-touch-6.0.4.8-evita.img
I am relatively novice to all this so you have to be patient as I do not always understand all I am doing. I am using:
gapps-kk-20140105-signed.zip
I installed the following roms:
cm-11-20140504-SNAPSHOT-M6-evita.zip
cm-11-20140608-SNAPSHOT-M7-evita.zip
cm-11-20140708-SNAPSHOT-M8-evita.zip
cm-11-20140804-SNAPSHOT-M9-evita.zip
cm-11-20140829-NIGHTLY-evita.zip
I tend to do the Wipe data and Factory reset on CWM when applying a new ROM.
I still had issues with M6 (automatic switch off). I found that M7 was relatevly stable. With M8 & M9, the device kept turning itself off after a while (anything between 1 min to 2 days). It sometime turn itself off whlibe booting, or even when I am in fastboot.
I managed to get a last_kmsg, and that shows something like this at the end:
Code:
...
[ 64.695956] mipi_dsi_clk_enable: dsi_escWclk - clk_set_rate failed
[ 64.712864] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 64.730016] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 64.755379] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
S 64.775644] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 65.549793] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 65.56¶671] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 65.771188] [BATT] batT_worker: total_time since last batt update = 60030 ms. at 65766048772 (2014-08-30 11:14:23.808850840 UTC)
[ 65.786571] [BATT][BMS] FCC=0784000,UC=0,RC=963360,CC=12727,CC_reset=0,RUC=950633,SOC=54,SOC_R=511300,start_percent=-22,end_percent=-22,OCV=3840441,OCV_raw=3855441,rbatt=128,rbatt_sf=0,batt_temp=327,soc_rbatt=0,last_rbatt=-22,V_unusable_uv=3000000,pc_unusable=0,rc_pc=54,scalefactor=100,no_ocv_update_is=0,consistent=0
[ 65.814283] [BATT][BMS] soc = 54 reporting last_soc = 53
[ 65.818922] [BATT][BMS] pm8921_bms_get_batt_soc: state_of_charge=53, store_soc_ui=-1, last_good_ocv_uv=3840441, raw.cc=2957555, stored_cc_uv:2957555, currtime_ms=647990725
[ 65.834274] [BATT][CHG] usbin_ov_irq_state:1 -> 1 [1,0,1]
[ 65.839615] [BATT] remap: no soc drop and no additional 1%, ui:53%
[ 65.845811] [BATT][BMS] pm8921_bms_get_battery_ui_soc: batt_stored_soc: 0
[ 65.852525] [BATT] htc_batt_get_battery_ui_soc: original soc: 53, changed soc: 53. at 65848758982 (2014-08-30 11:14:23.890177113 UTC)
[ 65.866870] [BATT][BMS] soc = 54 reporting last_soc = 53
[ 65.879719] [BATT][CHG] V=3595 mV, I=873 mA, T=32 C, SoC=53%, FCC=1784000, id=256 mV, H=1, P=1, CHG=1, S=0, FSM=0, AC=0, USB=0, DC=0, WLC=0 iusb_ma=100, usb_target_ma=0, OVP=0, UVP=0, TM=0, eoc_count/by_curr=0/0, vbatdet_low=1, is_ac_ST=0, batfet_dis=0x2, pwrsrc_dis=0x1, is_full=0, temp^fault=0, is_bat_warm/cool=0/0, btm_warm/cool=0/0, ichg=797 uA, vph_pwr=3567699 uV, usbin=7572 uV, dcin=11358 uV, pwrsrc_unDer_rating=0, usbin_critical_low_cnt=0, disable_reverse_boost_check=0, flag=0000, hsml_target_ma=0, vin_iin=4400, pj_exist=0
[ 65.893575] mipi_dsi_clk_enable:`dsi_esc_clk - clk_set_rate failed
[ 65.932946] [BATT][CHG] [irq1] 0110 1010 0000 000 [irq2] 0011 0000 1010 011[ 65.939081] KBATT][CHG] CNTRL=0x85,CNTRL_2=0x72,CNTRL_3=0x88,PBL_ACCESS1=0x4,PBL_ACCESS2=0x2¬SYS_CONFIG_1=0x3,SYS_CONFIG_2=0xd8,IBAT_SAFE=0x10,IBAT_MAX=0x10,VBAT_DET=0x7f,VDD_SAFE=0x30,VDD_MAX=0x30,VIN_MIN=0x6,VTRICKLE=0xfa,ITRICKLE=0x8a,ITERM=0x0,TCHG_MAX=0x7f,TWDOG=0xa0,TEMP_THRESH=0x94,COMP_OVR=0x0,BUCK_CTRL_TEST1=0x1,BUCK_CTRL_TEST2=0x8d,BUCK_CTRL_TEST3=0x91,CHG_TEST=0xd0,USB_OVP_CONTROL=0x42,USB_OVP_TEST=0xa0,DC_OVP_CONTROL=0x4c,DC_OVP_TEST=0xa0,REGULATION_LOOP_CONTROL=0x0
[ 65.982755] [BATT][BMS] CONTROL=0x99,OUTPUT0=0x8c,OUTPUT1=0x06,TOLERANCES=0x2f,BMS_TEST1=0x11,OCV_UPDATE_STORAGE=0xa0,read_cc=0x2968823,last_good_ocv=0x3840441,vbatt_for_rbatt=0x0,vsense_for_rbatt=0x0,ocv_for_rbatt=0x0,vsense_avg=0x9493, [irq]0010000
[ 66.004089] [BATT] ID=2,level=53,level_raw=53,vol=3604,temp=327,current=896700,chg_src=0,chg_en=0,pj_src=0,pj_level=0,full_bat=1800,over_vchg=0,batt_state=1,overload=0,ui_chg_full=0 at 66009082497 (2014-08-30 11:14:24.041771801 UTC)
[ 66.025362] [BATT] power_supply_changed: battery at 66018360690 (2014-08-30 11:14:24.063044501 UTC)
[ 66.033633] [BATT] batt_worker: done
[ 66.333923] [LS][cm3629] lightsensor_ioctl LIGHTSENSOR_IOCTL_ENABLE, value = 0
[ 66.344605] [LS][cm3629] lightsensor_disable
[ 66.353792] [LS][cm3629] lightsensor_release
[ 67.020265] mipi_dsi_clk_enable: dsi_esc_clk - clk_set_rate failed
[ 67.030489] mipi_dsi_panel_power: state : 0
[ 67.030489] mipi_dsi_panel_power: off
[ 67.071204] request_suspend_state: sleep (0->3) at 67060082039 (2014-08-30 11:14:25.108886100 UTC)
Y 67.079169] [LS][cm3629] cm3629_early_suspend
[ 67.084205] [PS][cm3621] capella_pl_sensor_lpm_power: enter lmp,OK
[ 67.089638] [TP] synaptics_ts_suspend: enter
[ 67.096871] [DISP] sii9234_early_suspend(isMHL=0)
[ 67.100564] [DISP] MhlTx: SiiMhlTxInitialize
[ 67.109781] [DISP] Drv: SiiMhlTxChipInitialize: 9244
[ 67.114298] [DISP] SiI 9234
[ 67.116496] [DISP] Drv: WriteInitialRegisterValues
[ 67.145368] [DISP] Drv: MHL 1.0 Compliant Clock
[ 67.181168] [DISP] Drv: InitCBuqRegs
[ 67.187913] [DISP] Drv: Switch To 3: pinAllowD3 = 1
[ 67.281580] [BMA250] GSensor Low Power Mode
[ 67.286983] [GSNR][MPU3050][TIMERIRQ]stop_timerirq: data->period = 66, data->run = 1
[ 67.798351] [VIB_PWM]pm8xxx_vib_enable vibrate period: 0 msec
[ 67.803082] [VIB_PM]pm8xxx_vib_sep_off
[ 68.688020] NOHZ: local_softirq_pending 08
[ 68.751747] NOHZ: local_softirq_pending 08
[ 69.146223] NOHZ: local_softirq_pending 08
[ 69.197192] NOHZ: local_softirq_pending 08
[ 69.583946] NOHZ: local_softirq_pending 08
[ 70.700961] NOHZ: local_softirq_pending 08
[ 71.692629] NOHZ: local_softirq_pending 08
[ 71.788768] NOHZ: local_softirq_pending 08
[ 71.804425] NOHZ: local_softirq_pending 08
[ 71.848527] NOHZ: local_softirq_pending 08
[ 72.792339] resout_irq_handler PMIC Initiated shutdown
[ 72.796459] PMIC Initiated shutdown cpu_power_off cpu=0
[ 72.801648] [K] Powering off the SoC
[ 72.805249] Calling scm to disable arbiter
[ 72.809308] SCM returned even when asked to busy loop rc=-4
[ 72.814832] waiting on pmic to shut msm down
=== EOF ===
I also ran an `./adb bugreport` command but that gave me 7MB of stuff I cannot understand..
Any idea to help resolve that automatic power off would be welcome.
Thanks
JM

If your phone is shutting off or rebooting while in fastboot mode, you're dealing with a hardware fault. It's a fault with the battery or the emmc.
Transmitted via Bacon

timmaaa said:
If your phone is shutting off or rebooting while in fastboot mode, you're dealing with a hardware fault. It's a fault with the battery or the emmc.
Click to expand...
Click to collapse
Oh dear... At least I know that it is not me playing up with flashing that put me into that state. Thanks for taking the time to read my post.
Hopefully it is not as bad as being a faulty emmc. Let's pray it is just the power button playing up and I can fix it myself. Phone is way out of warranty and maybe it is time to consider a nice upgrade.
Thanks
JM

Fixed: HTC One XL (evita) keeps dying on me..
jm_paulin said:
Let's pray it is just the power button playing up and I can fix it myself.
Click to expand...
Click to collapse
Ok, so after the excellent suggestion from @timmaaa it might well be hardware, I decided to open it and figure out what could go wrong. Had nothing to loose anyway. I just followed video PrArAes5liM on YouTube (good evening spam control), but used a credit card as I do not have the guitare thingy...
It is incredible the amount of crap that got into that phone over the last 2 years. So I brushed everything, cleaned the power button, and put it back together. Since then, not a problem... Okay, it is only 28 hours but that is nearly a record.
I also installed an app to switch the screen on using one of the sensor.
JM

HELP!!!!! I NEED TO REINsTALL LINUX ON A TV BOX

Hello all ,
I linked a serial cable to my allwinner a20 based Android Tv box.
It can not pass after the boot logo and next is all what it display in serial console.
Somebody pelase help i need to reisntall linux on it ,if you knwo any u boot keys that i have to press on the uboot serial consoel pelase help.I tryed to press ransom keys but i see nothin.
Here is all i see when it start:
====================================
HELLO! BOOT0 is starting!
boot0 version : 3.0.0
dram size =512
sum=0x9c3bd8cf
src_sum=0x9c3bd8cf
Ready to disable icache.
Jump to secend Boot.
[ 0.133]
U-Boot 2011.09-rc1-dirty (Nov 08 2013 - 11:06:32) Allwinner Technology
[ 0.141]version: 1.1.0
[ 0.144]pmbus: ready
axp read error
probe axp20x failed
axp_probe error
boot_clock = 912
dcdc2_vol = 1400
axp set dcdc2_vol to 1400 failed
dcdc3_vol = 1250
ldo2_vol = 3000
ldo3_vol = 2800
ldo4_vol = 2800
power_start = 0
storage_type = -1
usb_recovery = 0
find power_sply to end
fel key old mode
run key detect
no key found
no key input
dram_para_set start
dram_para_set end
[ 0.293]DRAM: 512 MiB
relocation Offset is: 15b27000
user_gpio config
user_gpio ok
DRV_DISP_Init: opened
[ 0.560]boot_disp.output_type=2
[ 0.563]boot_disp.output_mode=5
[ 0.567]boot_disp.auto_hpd=1
workmode = 0
[ 1.871]NAND: NAND_UbootInit
NB1 : enter NAND_LogicInit
nand : get id_number_ctl from script, 3
not burn nand partition table!
NB1 : nftl num: 3
init nftl: 0
NB1 : NAND_LogicInit ok, result = 0x0
[ 2.381]sunxi flash init ok
In: serial
Out: serial
Err: serial
--------fastboot partitions--------
-total partitions:12-
-name- -start- -size-
bootloader : 1000000 1000000
env : 2000000 1000000
boot : 3000000 1000000
system : 4000000 20000000
recovery : 24000000 2000000
databk : 26000000 2000000
misc : 28000000 1000000
private : 29000000 1000000
sysrecovery : 2a000000 21000000
data : 4b000000 40000000
cache : 8b000000 17000000
UDISK : a2000000 0
-----------------------------------
base bootcmd=run setargs_nand boot_normal
bootcmd set setargs_nand
key 0
recovery key high 6, low 4
cant find fstbt value
Fastboot detected, will boot fastboot
to be run cmd=run setargs_nand boot_fastboot
the user data'magic is bad
WORK_MODE_BOOT
board_status_probe
sunxi_bmp_display
WORK_MODE_BOOT
[ 2.509]Hit any key to stop autoboot: 0
run usb fastboot
sunxi_fastboot_init
recv addr 0x41000000
send addr 0x582580a8
delay time 0
usb init ok
------------------------------------------------------------------
After this nothing .Please help me

After searching all google and reading documantation ,I contacted the box seller and he gied me the files i neeeded.
I used a image file named sun7i_A20v2.0_android_sugar-ref001_2014.09.04_TakenYBSJ.img and a windwos software to flash it via usb named PhoenixPacketV333
To flash teh device you muist hava a serial console to the box (veru easy to do if you have the cable ) ,and keep pushed the key 2
on serial consle (putty) while powering the device ,so it enter in fel mode ( something like recovery mode ,it accept usb connection) .Then oyu need a usb male to male cable to conect the android tv box usb port to the windows usb port ,and start flasing using the PhoenixPacketV333 software.
If somebody needs more help or files just write here I check daily .
have a nice day all!

Allwinner A31 H4 Hummingbird Kit

Hi
Around for months ago I buy from Aliexpress "Merrii H4" board.
Then it was delivered, I try to use it... Connect power cord, connect VGA display, power on.... and see - nothing. For I wiil right at all, I see "wrong resolution" OSD message. I use my PHILIPS 223V display, I try to connect HDMI thru HDMI->DVI converter, see - nothing, and display "freezing" not answer to any button, POWER included.
I connect UART->USB converter and have a look boot LOG, it's right... I can read how system (android 4.4) started, I see info about screen resolution (800x480)
But... I want to do something else. I'm already try to communicate with merrii support... it is terrible... Hi talking with me, like I'm a stupid guy with no any skill and ... it is very very slow... Hi is answer to me two...three times per day, and him answer not helpfull.
NOW I'm already try to use PhoenixSuite 1.0.6, 1.0.8, 1.10 and PhoenixSuitePro 3.3.0, 3.3.4 to replace firmware, I can't do it, programm can't open iimages what I have...
sun6i_android_fiber-3g_v3.3_hummbingbird__TP_WIFI_BT_TV-IN_VGA_USB_OTG_3G_TCARD_RTC_OK_测试.img
sun6i_android_fiber-3g_v3.3_hummbingbird__LCD_TP_WIFI_BT_USB_OTG_CAMERA_3G_GMAC_TFCARD_RTC_ok_出货.img
what I do: run programm, press the UBOOT button and then plug USB cable, nothin is action with PS, and PSPro say "bla bla bla.. don't connect any device before ..."
When I try to open IMG file in PS, programm say "can't open Image"
When I open IMG file in PSPro and press START button after, nothing
Have I any luck to Sombody can help my situation?
I want to use my board with SOMETHING display for the begin.... And after I want to use it with 12.3" screen in my car.

boot LOG
<0>HELLO! BOOT0 is starting!
boot0 version : 3.0.0
reg_addr 0x01f00HELLO! BOOT0 is starting!
boot0 version : 3.0.0
reg_addr 0x01f00100 =0x00000000
reg_addr 0x01f00104 =0x00000000
reg_addr 0x01f00108 =0x00000000
reg_addr 0x01f0010c =0x00000000
reg_addr 0x01f00110 =0x00000000
reg_addr 0x01f00114 =0x00000000
[DRAM]ver 1.03 clk = 240
cpu 3 pmu 0
dram size =1024
sum=0xc0fe9d5b
src_sum=0xc0fe9d5b
Ready to disable icache.
[ 0.216]
0.231]PMU: AXP22x found
[ 0.234]PMU: bat ratio = 100
[ 0.237]PMU: dcdc3 1260
40]PMU: pll1 1008 Mhz
dcdc1_vol = 3000
fel key old mode
ram_para_set end
[ 0.284]DRAM: 1 GiB
relocation Offset is: 15b25000
[ 0.284]DRAM: 1 GiB
relocation Offset is: 15b25000
tart
eyB
:boot_init_gpio)
relocation Offset is: 15b25000
tart
dol = 1200
dcdc5_vol = 1500
aldo1_vol = 3000
aldo2_vol = 1800
deu_mode1 not exist.
exist.
aldo3_vol = 3000
eldo3_vol = 1800
find power_sply to end
200
ist.
lcdgamma4iep for lcd1 not ocation Offset is: 15b25000
tart
DRV_DISP_Init: opened
[ 0.559]fetch script data boot_disp.output_type fail
0.574]lcd0_para.lcd_used=1
[ 0.564]fetch script data boot_disp.output_mode fail
[ 0.569]fetch script data boot_disp.auto_hpd fail
tput_mode fail
[ 0.569]fetch script data boot_disp.auto_hpd fail
workmode = 0
B1 : nftl num: 2
init nftl: 0
: 2
init nftl: 0
ND_UbootInit
NB1 : enter NAND_LogicInit
not burn nand partition table!
[ 3000
NAND_LogicInit
not burNB1 : NAND_LogicInit ok, result = 0x0
[ 1.250]sunxi flash init ok
[mmc]: cmd 8 timeout, err 100
[mmc]: mmc cmd 8 err 0x00000100
: mmc cmd 1 err 0x00000100
mmc send op cond failed
-------fastboot partitions--------
data : 34000000 80000000
2000000
bootcmd set setargs_nand
s_probe
to stop autoboot: 0
read boot or recovery all
=====hanbiao 111===: start=18000, addr=40007800
autoboot: 0
read boot or recovery all
=====hanbiao 111===: start=18000, addr=40007800
WORK_MODE_BOOT
boot or recovery all
=====hanbiao 111===: start=18000, addr=40007800
WORK_MODE_BOOT
ot: 0
read boot or recovery all
=====hanbiao 111===: start=18000, addr=40007800
WORK_MODE_BOOT
[ 1.387]Hit any key oard_statu-------------------------
ll
=====hanbiao 111===: start=18000, addr=40007800
WORK_MODE_BOOT
recovery all
=====hanbiao 111===: start=18000, addr=40007800
WORK_MODE_BOOT
[ 1.387]Hit any key oard_statu-------------------------
base bootcmd=run setargs_nand boot_normal0
===hanbiao 111===: start=18000, addr=40007800
WORK_MODE_BOOT
111===: start=18000, addr=40007800
WORK_MODE_BOOT
[ 1.387]Hit any key oard_statu-------------------------
art=18000, addr=40007800
WORK_MODE_BO=====hanbiao 222===: start=18040, addr=4000f800
[ 1.915]sunxi flash read ffset 3000000, 11201530 bytes OK
dy to boot
NAND_UbootExit
NB1 : NAND_LogicExit
[ 1.926]
Starting kernel ...
signature pass
[ 1.923]rea<6[ 0.915214] aw_pm_init: not support super standby.
[ 0.979688] sun6i_vibrator_fetch_sysconfig_para motor is not used in config
[ 1.604963] otg_wakelock_init: No OTG transceiver found
[ 4.072052] init: /init.sun6i.rc: 45: invalid command 'umount'
[ 4.272611] init: /dev/hw_random not found
[ 6.614276] init: width = 800
[ 6.617579] init: height = 480
[ 6.620973] init: s.st_size = 1536000
[ 6.633434] init: dont need format /dev/block/by-name/UDISK
[ 8.007838] init: /dev/hw_random not found
[ 8.031591] healthd: wakealarm_init: timerfd_create failed
[ 8.043859] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
[ 8.054414] init: cannot find '/system/bin/usb_scan', disabling 'ttyusb-scan'
[ 8.184908] android_usb: already disabled
[email protected]:/ $ [ 10.162964] gslX680 1-0040: read failed
[ 10.367857] init: untracked pid 1764 exited
[ 24.838266] init: sys_prop: permission denied uid:1003 name:service.bootanim.exit
Click to expand...
Click to collapse

Need help, Phone rebooting randomly

I am using Moto G 3(2015)
My phone is rebooting randomly without doing anything. It generally happen 2 - 3 times in a day.
I have taken bug report for last 5 reboot. I found below information in "Last kmsg" from bugreport file :
[ 17.103106,1] msm_cci_release invalid ref count 0 / cci state 1
[ 17.103122,1] msm_sensor_cci_i2c_util line 512 rc = -22
[ 17.103127,1] msm_actuator_close:1439 cci_init failed
[ 17.103423,1] msm_csid_init: CSID_VERSION = 0x30010000
[ 17.103884,1] msm_csid_init: Failed in getting TOP gdscr regulator handle
[ 17.105711,1] msm_csid_init: CSID_VERSION = 0x30010000
[ 17.107891,1] msm_csid_init: Failed in getting TOP gdscr regulator handle
[ 17.112417,0] msm_vfe40_init_qos_parms: NO D/S entries found
[ 17.112433,0] msm_vfe40_init_vbif_parms: NO VBIF entries found
[ 17.129867,0] MSM-CPP cpp_init_hardware:952 CPP HW Version: 0x40000000
[ 17.129883,0] MSM-CPP cpp_init_hardware:973 stream_cnt:0
[ 17.156069,1] MSM-CPP cpp_load_fw:1110 MC Bootloader Version: 0x312e3176
[ 17.161889,1] MSM-CPP cpp_load_fw:1123 CPP FW Version: 0x10040005
[ 17.437125,2] camera_check_event_status : event_data status out of bounds
[ 17.437141,2] camera_check_event_status : Line 71 event_data->status 0X10001
[ 17.437148,2] camera_v4l2_open : checking event status fails Line 592 rc -14
[ 17.438450,3] mdss_fb_release_all: try to close unopened fb 1! from init
[ 17.438474,3] mdss_fb_release_all: try to close unopened fb 0! from init
[ 17.439087,0] Restarting system with command 'post-wdt'.
[ 17.439099,0] Current task:init(1) Parent task:swapper/0(0)
[ 17.439114,0] Going down for restart now
[ 17.440404,0] scm_call failed: func id 0x82000109, arginfo: 0x2, args: 0x1, 0x0, 0x0, 0x0, ret: -2, syscall returns: 0xfffffffc, 0x0, 0x0
[ 17.440417,0] Failed to disable secure wdog debug: -22
Need help to find root cause of issue.
Information of phone:
Build: MPI24.65-25
Build fingerprint: 'motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0/MPI24.65-25/28:user/release-keys'
Bootloader: 0x80CB
Radio: msm
Kernel: Linux version 3.10.49-g88eb8b3 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Tue Dec 8 05:34:29 CST 2015

My moto g is also rebooting randomely :/

mcnico said:
My moto g is also rebooting randomely :/
Click to expand...
Click to collapse
My phone is rebooting in safe mode too, I think it is some hardware bug.
Maybe you can capture bug report for your phone and check if you are getting same error message.

Firstly I am too getting this issue. My phone reboots randomly 2-3 a day. Strangely it reboots even when it is idle for quiet some time.
Secondly did anyone resolve this issue.
Thirdly how do I get the BUG report that you got in the first post?