Database Info

g1 MOBO with EVT1 32B ? Not PVT 32B? (solved see how)

ok some might have seen this strange board in a thread...
I had purchased a broken g1... and i talked about this strange EVT1 in hboot, and it would get stuck on G1 logo
so I waited until i got a usb/serial cable and jtag... I have both and i went on with the whole process
everything worked, up until i tried to get into the recovery, this device will not go into recovery for some reason.
==update==
looking at serial what its displaying... and it does go into recovery when the display turns off, the device is on, i just get error for the display and few others...
I had first the radio that was stated in the jtag process the 3.22.26.17
so hboot stating evt1 32b and were dread1000 or something like that supposed to be... i get drea*****
i researched and ran into other ppl that had a magic/sapphire that was evt 32b
fastboot/hboot is working at that point
here is a pic if you dont believe me
serial display of boot up... txt file is for boot recovery boot up
Code:
OEMSBL VERSION: 3.22.26.17
OEMSBL Build Date: Jan 17 2010 12:08:33
PLATFORM: DREAM
PID: 31
PLATFORM ID: 0
Boot CE manually...
Done.
+16 bit
-msm_nand_probe
[MDDI_HW_ERR] mddi_send_rtd fail!!
[MDDI_EID] mddi_eid_probe enter.
[EID_HW_ERR] mddi_eid_probe: Unknown panel type!!
GetModelName- Default[DREA*****]
Board_PID : 0x1F
Wlan data header ++++++++++++++++++++
Signature : 0xEE1251
UpdateStatus : 0x1
UpdateCount : 0x1
BodyLength : 0x2F0
BodyCRC : 0xC8545E10
aDieId(0) : 0x0
aDieId(1) : 0x0
aDieId(2) : 0x0
aDieId(3) : 0x0
countryID : 0x10
Wlan data header --------------------------
chipset_bootmode reset_reason:0
ARM11 Boot Mode: 0
Platform: HBOOT-7201A
###[ Fastboot Mode ]###

nobody has a clue

did some more forum searching...
in this thread someone states
http://forum.xda-developers.com/showpost.php?p=7582535&postcount=1530
http://forum.xda-developers.com/showpost.php?p=7967905&postcount=1538
that E is for engineering and P is for production?
so it seems that i can get into recovery, BUT there is an error, right when i go into recovery the display is off and below errors and txt file from the serial say the rest of the story...
Code:
boot reason: PM_KPD_PWR_KEY_ON_RT_ST
(PowerOn Status,Boot Reason)=(1,1)
NAND_FLASH_READ_ID : HYNIX_256MB_FLASH_128MB_SDRAM
ARM9_BOOT_MODE0, Boot Android
+16 bit
-msm_nand_probe
[MDDI] Bitmap_Width = 480
[MDDI] Bitmap_Height = 640
[MDDI] RGB_Capability = 0x8888
[MDDI] Mfr_Name = 0xD263
[MDDI] Product_Code = 0x0
GetModelName- Default[DREA*****]
Board_PID : 0x1F
Wlan data header ++++++++++++++++++++
Signature : 0xEE1251
UpdateStatus : 0x1
UpdateCount : 0x1
BodyLength : 0x2F0
BodyCRC : 0xC8545E10
aDieId(0) : 0x0
aDieId(1) : 0x0
aDieId(2) : 0x0
aDieId(3) : 0x0
countryID : 0x10
Wlan data header --------------------------
chipset_bootmode reset_reason:0
ARM11 Boot Mode: 0
Platform: HBOOT-7201A
setup_tag addr=0xA0000100 cmdline add=0x98071C80
TAG:Ramdisk OK
TAG:smi ok, size = 64
TAG:hwid 0x0
TAG:skuid 0xFFFFFFFF
TAG:hero panel = 0x0
TAG:engineerid = 0xFFFFFFFF
Device CID is not super CID
CID is T-MOB010
setting.cid::T-MOB010
serial number: 0123456789*******
commandline from head: no_console_suspend=1 console=null
command line length =331
active commandline: board_trout.disable_uart3=0 board_trout.usb_h2w_sw=0 board_trout.disable_sdcard=0 smisize=64 androidboot.baseband=2.22.23.02 androidboot.cid=T-MOB010 androidboot.carrier=TMUS androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=0123456789*****
androidboot.bootloader=1.33.2005 no_console_suspend=1 console=null
PARTITIOM_NUM_MAX =6 Valid partition num=6
(note put **** in serial number)
im going to attach txt of the recovery boot up
this is from serial cable while home + power (recovery mode)
note this is with the 1.7 dream recovery and the 2.22.23.02 dream radio
also worked fine with the jtag radio and recovery, i believe same error
look at the error, seems with display? as i can pass commands blindly (tried to flash from memory card, but still i believe the device then reboots...)
ignore other errors as only mobo + display and daughter board are connected...
this is one error while going into recov:
hsusb: ONLINE -> OFFLINE
[ 7.667053] ekt8232_probe enter.
[ 7.670471] elan-touch 0-0010: without platform data??!!
[ 7.876098] elan-touch 0-0010: __hello_packet_handler: failed!
[ 7.882019] looks like it's not Elan, so..i'll quit
[ 7.926300] msm_i2c msm_i2c.0: error, status c8
[ 7.931091] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 7.936828] i2c_smbus_write_byte_data failed
[ 7.941375] msm_i2c msm_i2c.0: error, status c8
[ 7.946563] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.056213] msm_i2c msm_i2c.0: error, status 43c8
[ 8.061157] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.183258] msm_i2c msm_i2c.0: error, status c8
[ 8.188140] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.298706] msm_i2c msm_i2c.0: error, status c8
[ 8.303558] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.418060] msm_i2c msm_i2c.0: error, status c8
[ 8.422912] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.538055] msm_i2c msm_i2c.0: error, status c8
[ 8.542907] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.658050] msm_i2c msm_i2c.0: error, status c8
[ 8.662872] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.778167] msm_i2c msm_i2c.0: error, status c8
[ 8.783020] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 8.898071] msm_i2c msm_i2c.0: error, status c8
[ 8.902893] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 9.018066] msm_i2c msm_i2c.0: error, status c8
[ 9.022918] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 9.137939] i2c_smbus_read_byte_data failed
[ 9.142425] synaptics-rmi-ts: probe of 0-0020 failed with error -5
[ 9.150451] GPIO Input Driver: Start gpio inputs for trout-nav in interrupt mode
the error that keeps on repeating is:
msmfb_pan_display timeout waiting for frame start, 1 1
i attached hboot commands?!?

so i was playing with a lot of hboot commands that were in that txt file
i ran into writesku/readsku
so what did i do? write some diff words... and result? wow things change...
so how did i fix? simple plugged in a working G1 mobo and copied all the readsku info
now my EVT1 magically turned into PVT, though it now reads DREAM and not DREA**** and not DREAM1000 either... oh well
and i went right into recovery after rebooting
here are the contacts of readsku before and after (is cloned from other mobo)
messed up EVT mobo
Code:
hboot>readsku
skuid item:FunctionSKUField
index:0x0, value:0x0
skuid item:PCBIDField
index:0x1, value:0xFFFF
skuid item:RFSKUIDField_D0
index:0x2, value:0xFFFFFFFF
skuid item:RFSKUIDField_D1
index:0x3, value:0xFFFFFF
skuid item:RFSKUIDField_D2
index:0x4, value:0xFFFFFFFF
skuid item:RFSKUIDField_D3
index:0x5, value:0xFFFFDFFF
skuid item:RFSKUIDField_D4
index:0x6, value:0xFFFFBFFF
skuid item:RFSKUIDField_D5
index:0x7, value:0xEFFFFFFF
skuid item:RFSKUIDField_D6
index:0x8, value:0xFFFFFFFF
skuid item:RFSKUIDField_D7
index:0x9, value:0xFFFFFFFF
skuid item:SKUIDChecksum
index:0xA, value:0xFFFFFF
skuid item:EngineerID
index:0xB, value:0xFFFFFFFF
copy from working mobo
Code:
hboot>readsku
skuid item:FunctionSKUField
index:0x0, value:0x1BE00
skuid item:PCBIDField
index:0x1, value:0x80FFFFFF
skuid item:RFSKUIDField_D0
index:0x2, value:0x12
skuid item:RFSKUIDField_D1
index:0x3, value:0x20000D4
skuid item:RFSKUIDField_D2
index:0x4, value:0xFFFFFFFF
skuid item:RFSKUIDField_D3
index:0x5, value:0xFFFFFFFF
skuid item:RFSKUIDField_D4
index:0x6, value:0xFFFFFFFF
skuid item:RFSKUIDField_D5
index:0x7, value:0xFFFFFFFF
skuid item:RFSKUIDField_D6
index:0x8, value:0xFFFFFFFF
skuid item:RFSKUIDField_D7
index:0x9, value:0xFFFFFFFF
skuid item:SKUIDChecksum
index:0xA, value:0xD8A37369
skuid item:EngineerID
index:0xB, value:0xFFFFFFFF
as you can see the first line is the key and then others too...
this explains all the serial code that i saw, interesting that all the flashing erasing and what not did not touch these values
all those errors were because there was no id to the device and recovery couldnt ID it and couldnt init the display, and not only that funny how the keyboard maping wasnt working either... so its possible to change your device to whatever I guess, its just an ID tag

how do i debug (system ui crash, stopped)

hi everyone, i'm trying to mod some apk's (systemui and frameworkres)
i get no errors in apktool but when i flash the apk's in cwm, i get systemui has stopped and i have no ui.
i wipe cache and wipe cache partion with no help.
i'm trying to get a logcat but it's pretty much empty, one message about about heapsize.
so my question is whats the best way to find the cause of the errors?
Thanks
my logcat
Code:
--------- beginning of /dev/log/main
[ 05-12 09:25:40.243 4361: 4361 E/Trace ]
error opening trace file: No such file or directory (2)
[ 05-12 09:25:40.243 4361: 4361 D/ActivityThread ]
setTargetHeapUtilization:0.25
[ 05-12 09:25:40.243 4361: 4361 D/ActivityThread ]
setTargetHeapIdealFree:8388608
[ 05-12 09:25:40.243 4361: 4361 D/ActivityThread ]
setTargetHeapConcurrentStart:2097152

any help would be much appreciated.

[SOLVED][Q] WiFi won't turn on

All of a sudden, on Stock + Root TF700T, WiFi won't turn on. I highly doubt that this is related to my WiFi router ... the WiFi won't even enable on the tablet, and I can't even see a MAC address in About Tablet section.
I also did some digging and have some additional detail, but I cannot find a solution.
logcat:
Code:
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '43 softap fwreload wlan0 STA' failed with '400 43 Softap operation failed (No such file or directory)'
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2767): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2767): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2767): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2767): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 3ms+3ms, total 57ms
D/AsusBrightnessManager( 489): br transform : 35 -> 13
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '46 softap fwreload wlan0 STA' failed with '400 46 Softap operation failed (No such file or directory)'
E/WifiStateMachine( 489): Failed 6 times to start supplicant, unload driver
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '48 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 48 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2792): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2792): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2792): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2792): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 2ms+1ms, total 22ms
W/NvCpuClient( 489): Failed to bind to service
D/AsusBrightnessManager( 489): br transform : 35 -> 13
E/WifiHW ( 489): Supplicant not running, cannot connect
W/NvCpuClient( 489): Failed to bind to service
Also, output from netcfg:
Code:
[email protected]:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
dummy0 DOWN 0.0.0.0/0 0x00000082 76:ad:93:6b:c9:b7
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
And here is output of my wpa_supplicant.conf:
Code:
[email protected]:/ # cat /etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
And I searched the entire filesystem for "nl80211" and found nothing.
Does anyone have suggestions on where to go next? Did my driver somehow get deleted, or am I just not looking for the right thing?
Thanks.

I will use this question in the future as an example of how to ask for support properly. Unfortunately I don't have a solution for you, but you could check the files in your /data/misc/wifi, maybe you can find something unusual. Your MAC address should come from some file on the FAT filesystem on /dev/block/mmcblk0p5 - I'd recommend making an image of it as a backup and then analyze the image.

_that said:
I will use this question in the future as an example of how to ask for support properly.
Click to expand...
Click to collapse
I provide Enterprise-level support to software devs working in the Cloud and particularly on CentOS/RHEL Linux servers. This is why I know how to ask for help properly.
Well, since I can't find much, and there aren't any definitive answers here, my next thoughts are:
1) Something is seriously jacked up on the filesystem, possibly corrupted driver, possibly something worse. Hopefully, this is the case, because a software problem is possible to fix.
2) The WiFi radio is permanently damaged, or "burnt out".
In the hopes that it's something more like software, I'm going to reimage. I just need to decide what ROM to use. Not having network connectivity will make the prep for this a bit more challenging, but I can work through it using a MicroSD card.
If it's #2, well then I suppose I will have wasted my time reimaging and will be on the market for a new tablet ... and I need to get on that right away because I need to travel soon. Any suggestions are welcome ... I'd like a 9" or 10" tablet and it must have an HDMI out (micro preferred) and be able to handle 1080p video.
Thanks.

[SOLVED]
I am having a heckuva time even doing what I described above.
-I had never unlocked the bootloader before, so when I tried the ASUS unlock util v8, it gave error "INSTALL_FAILED_SHARED_USER_INCOMPATIBLE"
-I tried the ASUS unlock tool v7, and was finally able to install it but when I run and select Unlock I get an error that there is no network connection (FFS that's what I'm trying to resolve!)
-I can't get into recovery, I just get the Android guy with "ERROR!" when I enter fastboot and select "RCK".
My only option is to go back to Stock. So, I tried this:
http://forum.xda-developers.com/showthread.php?t=1833212
The steps in that post result in the same Android guy with the "ERROR!" screen ... not a very helpful error msg.
So, I tried this, and used the stock firmware from ASUS. (NOTE: I downloaded "ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)" directly from ASUS after I read their notes on where to check for which one you need ([Settings]-->[About tablet]-->Build number).):
http://www.transformerforums.com/fo...e-firmware-tf700-tf701-tf300-tf101-tf201.html
From that post ^^ I did Method B: Flash from MicroSD. I extracted the .zip I downloaded from ASUS, and renamed the new zip EP201_768_SDUPDATE.zip per the GUIDE linked above.
I put in my MicroSD, went back into fastboot, and selected "RCK". It was at this point that I began typing the above. Total time to get to this point was about 90 minutes!
-----
FINALLY, for the first time, I saw a progress bar under the Android guy, and he had gears turning in his belly.
*INSERT SIGH OF RELIEF HERE*
As I was typing out all the above, progress bars were moving, and a few reboots happened. I expected that I would be fully back on Stock ROM, and that my data would have been wiped. I never ran a data wipe, I just assumed the ASUS installer would do that by default.
Well, it didn't wipe data. But, what it did do: restore all my device drivers!! After about 10 minutes, and 2-3 reboots, Android loaded with my existing desktop and settings, and the WiFi connected right away!!
So, this fixed it. I documented the above so anyone (even me, months from now) having a similar problem might be able to use these steps.
WOO HOO!

lost root
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.

CaptainRewind said:
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.
Click to expand...
Click to collapse
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip

sbdags said:
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Click to expand...
Click to collapse
Yep, I had to do that anyway because I wanted to do a full Titanium Backup first. Still, I'm moving to CM now.

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

[SOLVED] Bootloop/kernel panic in meminfo_proc_show() 3.10.65+ trying to port LOS12.1

Hello Android kernel hackers,
I am trying to port the current ASB-patched LOS12.1 (github "cm12-amami") to a Teclast 98 (M1E9) tablet for which kernel sources are missing. My build completes fine, however, I run into a boot loop due to kernel panic with an (at least for me) totally unhelpful stack trace:
During init.rc processing, the kernel panics on logd startup when logd tries to read from /proc/meminfo with the following stack trace:
Code:
[ 126.200788]00:02:29.656321 openat(AT_FDCWD, "/proc/meminfo", O_RDONLY) = 4
[ 126.200956]00:02:29.656496 fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
[ 126.201077]00:02:29.656614 mprotect(0x7faf52b000, 4096, PROT_READ|PROT_WRITE) = 0
[ 126.201187]00:02:29.656726 mprotect(0x7faf52b000, 4096, PROT_READ) = 0
[ 126.202709]00:02:29.656833 read(4,
* KERNEL PANIC HAPPENS HERE!!! *
Code:
[ 126.202739]<1> (1)[949:logd]<1>start....
[ 126.202805]<1> (1)[949:logd]Unable to handle kernel NULL pointer dereference at virtual address 00000016
[ 126.202817]<1> (1)[949:logd]pgd = ffffffc070dee000
[ 126.202828]<1> (1)[949:logd][00000016] *pgd=0000000000000000 (1)[949:logd]
[ 126.202846]<1> (1)[949:logd][KERN Warning] ERROR/WARN forces debug_lock off!
[ 126.202854]<1> (1)[949:logd][KERN Warning] check backtrace:
[ 126.202868]<1> (1)[949:logd]CPU: 1 PID: 949 Comm: logd Tainted: G W 3.10.65+ #1
[ 126.202878]<1> (1)[949:logd]Call trace:
[ 126.202899]<1> (1)[949:logd][<ffffffc000088f50>] dump_backtrace+0x0/0x16c
[ 126.202913]<1> (1)[949:logd][<ffffffc0000890cc>] show_stack+0x10/0x1c
[ 126.202931]<1> (1)[949:logd][<ffffffc0009a69a0>] dump_stack+0x1c/0x28
[ 126.202947]<1> (1)[949:logd][<ffffffc0002f7210>] debug_locks_off+0x40/0x5c
[ 126.202960]<1> (1)[949:logd][<ffffffc00009a260>] oops_enter+0xc/0x28
[ 126.202974]<1> (1)[949:logd][<ffffffc000089100>] die+0x28/0x1d8
[ 126.202989]<1> (1)[949:logd][<ffffffc0009a49ec>] __do_kernel_fault.part.5+0x70/0x84
[ 126.203003]<1> (1)[949:logd][<ffffffc000094260>] do_page_fault+0x348/0x34c
[ 126.203017]<1> (1)[949:logd][<ffffffc000094350>] do_translation_fault+0x40/0x4c
[ 126.203030]<1> (1)[949:logd][<ffffffc0000813fc>] do_mem_abort+0x38/0x98
which does not seem to uncover the root cause, but rather the root cause stack trace seems to be:
Code:
[ 133.341226]<1>-(1)[949:logd]Call trace:
[ 133.341239]<1>-(1)[949:logd][<ffffffc0001f37d8>] meminfo_proc_show+0x50/0x3c4
[ 133.341255]<1>-(1)[949:logd][<ffffffc0001aefb8>] seq_read+0x1a4/0x40c
[ 133.341271]<1>-(1)[949:logd][<ffffffc0001ebeec>] proc_reg_read+0x4c/0x7c
[ 133.341285]<1>-(1)[949:logd][<ffffffc00018e75c>] vfs_read+0x88/0x170
[ 133.341298]<1>-(1)[949:logd][<ffffffc00018ebf0>] SyS_read+0x40/0x8c
[ 133.341310]<1>-(1)[949:logd]Code: 52800001 91326000 97fe67c1 aa0003f3 (f9400c00)
[ 133.341322]<1>-(1)[949:logd]---[ end trace 1b75b31a2719ed20 ]---
[ 133.341332]<1>-(1)[949:logd]Kernel panic - not syncing: Fatal exception
[ 133.341423]<1>-(1)[949:logd]mrdump: cpu[1] tsk:ffffffc073a3e000 ti:ffffffc070e64000
[ 134.241428]<1>-(1)[949:logd]
Most interestingly, the exact same kernel blob can successfully boot stock Android 5.1 and successfully read from /proc/meminfo when booted from stock boot.img while it crashes with my LOS12.1 build boot.img.
bootimg.cfg (using abootimg) is identical in both cases (except the boot size):
Code:
bootsize = 0x780000
pagesize = 0x800
kerneladdr = 0x40080000
ramdiskaddr = 0x44000000
secondaddr = 0x40f00000
tagsaddr = 0x4e000000
name = 1513588375
cmdline = bootopt=64S3,32N2,64N2 androidboot.selinux=permissive
Thanks a million in advance for any ideas or pointers about what might be going wrong with this stock kernel blob and my LOS12.1 build with regards to meminfo_proc_show()! :highfive:
awl14

Issue resolved!
Finally resolved by making changes (a whole number of, so I haven't tracked it down to one particular change) to my CM12.1 build's system partition, making it resemble the stock image more closely.
I still don't have any clues why the kernel would crash on reading from /proc/meminfo due to "wrong"/buggy contents in the system partition (/system file system), but as the issue is resolved, this can be regarded as a proof that such content in system can indeed matter in a critical way for the behaviour of the kernel...
My custom ROM for Teclast 98 (M1E9) runs fine now, I will publish a download link soon on xda.

Panic caused by kernel reading file /system/bin/cpuinfo
I encountered the same issue and was able to find the root cause. The kernel I'm dealing with has been modified by Chinese crooks who fake the amount of memory in the device by intercepting meminfo_proc_show(). In this routine, they read the file /system/bin/cpuinfo, apparently extracting the value to be shown to the user as the memory size from that file. The code does not even test the return code from the file opening routine, and simply crashes the kernel if the file is not present.