Database Users

HTC Prophet AND LinWizard Help

Hi all,
View mins ago I setup linux on my HTC.
Well, it does work and i can connect to my device with ssh.
But I have some problems, it cant find the MMC Card (I format it as ext2) on my desktop (debian)
my dmesg
# dmesg
<5>Linux version 2.6.16.27-omap1 ([email protected]) (gcc version 4.1.1) #4 PREEMPT Fri Jan 5 16:56:42 CET 2007
<4>CPU: ARM926EJ-Sid(wb) [41069263] revision 3 (ARMv5TEJ)
<4>Machine: HTC Wizard
<4>Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 24576
<7> DMA zone: 24576 pages, LIFO batch:7
<7> DMA32 zone: 0 pages, LIFO batch:0
<7> Normal zone: 0 pages, LIFO batch:0
<7> HighMem zone: 0 pages, LIFO batch:0
<4>Unknown OMAP cpu type: 0x00
<4>OMAP0000 revision 1 handled as 00xx id: 0000000000000000
<6>SRAM: Mapped pa 0x20000000 to va 0xd0000000 size: 0x32000
<4>htc_wizard_map_io done.
<4>CPU0: D VIVT write-back cache
<4>CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
<4>CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
<4>Built 1 zonelists
<5>Kernel command line: root=/dev/ram0 init=/linuxrc
<4>htc_wizard_init_irq.
<4>Clocks: ARM_SYSST: 0x1040 DPLL_CTL: 0x2793 ARM_CKCTL: 0x6506
<6>Clocking rate (xtal/DPLL1/MPU): 13.0/195.0/195.0 MHz
<4>Total of 96 interrupts in 3 interrupt banks
<6>OMAP730 GPIO hardware
<4>PID hash table entries: 512 (order: 9, 8192 bytes)
<4>Console: colour dummy device 80x30
<4>Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
<4>Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
<6>Memory: 96MB = 96MB total
<5>Memory: 92444KB available (1656K code, 403K data, 96K init)
<7>Calibrating delay loop... 89.70 BogoMIPS (lpj=448512)
<4>Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: ok
<6>checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
<6>Freeing initrd memory: 2604K
<6>NET: Registered protocol family 16
<4>Tornado init.
<4>OMAP730 Watchdog seems to be activated, disabling it for now.
<4>trying to enable USB.
<4>USB_EN to 0 after 0 tries.
<4>MMC host reset done: remaining tries: 100
<6>OMAP DMA hardware version 1
<6>DMA capabilities: 000c0000:00000000:01ff:003f:007f
<4>Initializing OMAP McBSP system
<3>mcbsp: could not acquire dsp_ck handle.
<3>omapdsp: unsupported omap architecture.
<4>USB: hmc 4, usb0 2 wires (dev)
<4>NetWinder Floating Point Emulator V0.97 (double precision)
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<4>HTC Tornado Backlight driver.
<4>VSFB Frame buffer driver for HTC OMAP Based Phones.
<6>vsfb: framebuffer at 0x20001020, mapped to 0xc6800020, size 150k
<4>Console: switching to colour frame buffer device 40x29
<6>TI OMAP Watchdog Timer for OMAP730
<4>RAMDISK driver initialized: 1 RAM disks of 8192K size 1024 blocksize
<6>udc: OMAP UDC driver, version: 4 October 2004 (iso)
<6>udc: OMAP UDC rev 3.6
<6>udc: hmc mode 4, integrated transceiver
<6>udc: fifo mode 3, 648 bytes not used
<6>usb0: Ethernet Gadget, version: May Day 2005
<6>usb0: using omap_udc, OUT ep2out-bulk IN ep1in-bulk STATUS ep3in-int
<6>usb0: MAC 9a:17:46:70:a0:3b
<6>usb0: HOST MAC c2:20:66:22:69:ae
<6>mice: PS/2 mouse device common for all mice
<6>OMAP Keypad Driver
<4>omap_kp_probe.
<6>input: omap-keypad as /class/input/input0
<6>NET: Registered protocol family 2
<3>MMC1: Command timeout, CMD0
<4>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<4>TCP established hash table entries: 4096 (order: 2, 16384 bytes)
<4>TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
<6>TCP: Hash tables configured (established 4096 bind 4096)
<6>udc: USB reset done, gadget ether
<6>TCP reno registered
<6>TCP bic registered
<6>NET: Registered protocol family 1
<6>NET: Registered protocol family 17
<6>NET: Registered protocol family 15
<5>RAMDISK: Compressed image found at block 0
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>usb0: full speed config #1: 100 mA, Ethernet Gadget, using CDC Ethernet
<4>VFS: Mounted root (ext2 filesystem).
<6>Freeing init memory: 96K
<6>vsmmfb: ioctl helper driver for framebuffer 0.1.1, Copyright 2007 Thomas Reith
<6>vsmmfb: loaded, got minor 63
Click to expand...
Click to collapse
# df -h
Filesystem Size Used Available Use% Mounted on
/dev/ram0 5.8M 4.4M 1.4M 75% /
Click to expand...
Click to collapse
# mount
/dev/root on / type ext2 (rw,nogrpid)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw)
sysfs on /sys type sysfs (rw)
Click to expand...
Click to collapse
The problem is , even in /dev
mmcblk0
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
there isnt anything, so if i cant find my mmc, i cant fdisk so i wont have any os.
The next problem is, i dont have gcc?
Because it it not a debian system (i want to) apt wont work, no RPM, just nothing.
How de heck can i compile gcc without gcc? so i can start using my os?
the next thing, but the last one.
When i have my OS ready to play.
It is possible to write it to ram? so it will remove windows and replace it with my linux version?
Any help/tips would be helpfull
thx

MMC and NS.exe on HTC prophet
Hi:
You can activate your sd card using Nico's program sd.exe
Look the web of the linwizard project in sourceforge:
http://sourceforge.net/tracker/index.php?func=detail&aid=1593777&group_id=174107&atid=867988
Luck!!
Sesh maat setep n ra

[Q] Run 6.1.0-RC2-Aria ROM in SDK emulator ?

Hi all,
I have downloaded the 6.1.0-RC2-Aria ROM a couple of days ago, installed it on my phone and everything is working great - thanks again attn1!
Now I would like to do some testing/dev with it; instead of tampering with my device.
I created a NANdroid back-up and then tried running the ROM on the SDK emulator following threads instructions found over here and other forums, e.g. :
http://forum.xda-developers.com/archive/index.php/t-572497.html
http://forum.xda-developers.com/showthread.php?t=525930&page=2
http://android.modaco.com/content/g...p-and-running-a-full-rom-with-the-market-etc/
The emulator seems to be running OK, but the kernel gets stuck before it even gives me the boot animation. (- c.f. below for the parameters passed and the kernel boot log; adb logcat does not report anything at all -)
Anyone has been able to run this particular ROM on the SDK emulator or may give me pointers as to how to do so successfully?
Thank you.
+++++++++++++++++++++++++++++++++++++++++++++++++++++
C:\android-sdk-windows\tools>emulator -avd testing -show-kernel -sdcard mycard
Uncompressing Linux............................................................................................. done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 2.6.29-00261-g0097074-dirty ([email protected]) (gcc version 4.4.0 (GCC) ) #20 Wed Mar 31 09:54:02 PDT 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00093177
CPU: VIVT data cache, VIVT instruction cache
Machine: Goldfish
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
Kernel command line: qemu=1 console=ttyS0 android.checkjni=1 android.qemud=ttyS1 android.ndns=1
Unknown boot option `android.checkjni=1': ignoring
Unknown boot option `android.qemud=ttyS1': ignoring
Unknown boot option `android.ndns=1': ignoring
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 515840KB available (2616K code, 681K data, 104K init)
Calibrating delay loop... 238.38 BogoMIPS (lpj=1191936)
Mount-cache hash table entries: 512
Initializing cgroup subsys debug
Initializing cgroup subsys cpuacct
Initializing cgroup subsys freezer
CPU: Testing write buffer coherency: ok
net_namespace: 520 bytes
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
NET: Registered protocol family 1
checking if image is initramfs... it is
Freeing initrd memory: 160K
goldfish_new_pdev goldfish_interrupt_controller at ff000000 irq -1
goldfish_new_pdev goldfish_device_bus at ff001000 irq 1
goldfish_new_pdev goldfish_timer at ff003000 irq 3
goldfish_new_pdev goldfish_rtc at ff010000 irq 10
goldfish_new_pdev goldfish_tty at ff002000 irq 4
goldfish_new_pdev goldfish_tty at ff011000 irq 11
goldfish_new_pdev smc91x at ff012000 irq 12
goldfish_new_pdev goldfish_fb at ff013000 irq 13
goldfish_new_pdev goldfish_mmc at ff005000 irq 14
goldfish_new_pdev goldfish_memlog at ff006000 irq -1
goldfish_new_pdev goldfish_events at ff014000 irq 15
goldfish_new_pdev goldfish_nand at ff015000 irq -1
goldfish_new_pdev goldfish-switch at ff016000 irq 16
goldfish_new_pdev goldfish-switch at ff017000 irq 17
goldfish_pdev_worker registered goldfish_interrupt_controller
goldfish_pdev_worker registered goldfish_device_bus
goldfish_pdev_worker registered goldfish_timer
goldfish_pdev_worker registered goldfish_rtc
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered smc91x
goldfish_pdev_worker registered goldfish_fb
goldfish_pdev_worker registered goldfish_mmc
goldfish_pdev_worker registered goldfish_memlog
goldfish_pdev_worker registered goldfish_events
goldfish_pdev_worker registered goldfish_nand
goldfish_pdev_worker registered goldfish-switch
goldfish_pdev_worker registered goldfish-switch
ashmem: initialized
Installing knfsd (copyright (C) 1996 [email protected]).
yaffs Mar 26 2010 13:38:48 Installing.
msgmni has been set to 1008
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
allocating frame buffer 320 * 480, got ffa00000
Console: switching to colour frame buffer device 40x30
console [ttyS0] enabled
brd: module loaded
loop: module loaded
nbd: registered device at major 43
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <[email protected]>
eth0 (smc91x): not using net_device_ops yet
eth0: SMC91C11xFD (rev 1) at e084c000 IRQ 12 [nowait]
eth0: Ethernet addr: 52:54:00:12:34:56
goldfish nand dev0: size 6ea0000, page 2048, extra 64, erase 131072
goldfish nand dev1: size 4000000, page 2048, extra 64, erase 131072
goldfish nand dev2: size 4000000, page 2048, extra 64, erase 131072
mice: PS/2 mouse device common for all mice
*** events probe ***
events_probe() addr=0xe0854000 irq=15
events_probe() keymap=qwerty2
input: qwerty2 as /devices/virtual/input/input0
goldfish_rtc goldfish_rtc: rtc core: registered goldfish_rtc as rtc0
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: [email protected]
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
802.1Q VLAN Support v1.8 Ben Greear <[email protected]>
All bugs added by David S. Miller <[email protected]>
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
goldfish_rtc goldfish_rtc: setting system clock to 2010-12-05 03:32:33 UTC (1291
519953)
Freeing init memory: 104K
mmc0: new SD card at address e118
mmcblk0: mmc0:e118 SU02G 1.00 GiB
mmcblk0:
init: cannot open '/initlogo.rle'
yaffs: dev is 32505856 name is "mtdblock0"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.0, "mtdblock0"
yaffs_read_super: isCheckpointed 0
save exit: isCheckpointed 0
yaffs: dev is 32505857 name is "mtdblock1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.1, "mtdblock1"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
request_suspend_state: wakeup (3->0) at 4206070790 (2010-12-05 03:32:36.48957032
7 UTC)
init: untracked pid 34 exited
init: untracked pid 42 exited
request_suspend_state: wakeup (0->0) at 4256118986 (2010-12-05 03:32:36.53963374
7 UTC)
init: untracked pid 44 exited
init: untracked pid 53 exited
request_suspend_state: wakeup (0->0) at 9387505566 (2010-12-05 03:32:41.67101886
1 UTC)
init: untracked pid 54 exited
init: untracked pid 60 exited
init: untracked pid 68 exited
init: untracked pid 69 exited
request_suspend_state: wakeup (0->0) at 14518491192 (2010-12-05 03:32:46.8020076
30 UTC)
init: untracked pid 74 exited
init: untracked pid 82 exited
init: untracked pid 83 exited
request_suspend_state: wakeup (0->0) at 19655651551 (2010-12-05 03:32:51.9391665
92 UTC)
init: untracked pid 89 exited
request_suspend_state: wakeup (0->0) at 24731037643 (2010-12-05 03:32:57.0145514
97 UTC)
init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting i
nto recovery mode
save exit: isCheckpointed 1
save exit: isCheckpointed 1
Restarting system with command 'recovery'.
Reboot failed -- System halted
+++++++++++++++++++++++++++++++++++++++++++++++++++++

LOL, root the emulated device!

I would if I knew how to do so on the emulator itself
I have rooted my actual device, but I have no idea how to accomplish this on the emulator; could you elaborate or send links on how to do this please?
I have googled and nothing relevant has showed up other than the emulator is supposed to be already root-ed; by issuing adb root I get:
C:\android-sdk\android-sdk-windows\tools>adb root
adbd is already running as root
I also tried running the emulator with the '-shell' parameter, but got the same result and the boot process gets stuck as well...
A little bit of extra guidance would be great.
Thank you.

Telus Desire HD users need your help

Can anyone who has a Telus Model Desire HD post a logcat during boot and a dmesg after boot for me? I am working on a project and need some info.

No telus desire hd users?

The Telus Desire HD is an Inspire 4G but with an HTC logo on the back rather than AT&T. Thats the only difference in the two hardware wise, they're both A9192's. Software wise, its just a different cid (661 builds are for canadian market, thats why the sensation's .661 build is for Bell Mobility, the Evo 3D's build for Rogers is also .661, and why Telus' DHD build also has .661 in its build numbers)(at&t's CID is 502)
You can ask Inspire 4G users for their logcat's too, they'll be the same thing. Both have the same Hboot version in 2.43.661 (telus build) and the 2.47 (cingular build)
... just sayin.

Only reason I ask is because the Telus Desire HD ruu do not have dualmic enabled but the AT&T Inspire 4g does have dualmic enabled. Both the kernel config and dmesg when booting the telus ruu on an inspire show that dualmic is disabled. So if you someone does have one I would like to read the logs from it to see if the telus really doesn't have a dualmic.

jznomoney said:
Only reason I ask is because the Telus Desire HD ruu do not have dualmic enabled but the AT&T Inspire 4g does have dualmic enabled. Both the kernel config and dmesg when booting the telus ruu on an inspire show that dualmic is disabled. So if you someone does have one I would like to read the logs from it to see if the telus really doesn't have a dualmic.
Click to expand...
Click to collapse
It just doesnt have dual mic enabled, because telus doesnt feel that its neccessary (another reason why I dont use the stock rom on my A9192) (the dev's that work for telus arnt the brightest in the bunch either)

do me a favor if you have a telus desire hd, right after a boot do this
adb shell dmesg | grep revision
What revision does it return
<6>[ 0.245697] spade_init: revision = 128 this is the desire hd without a dualmic
if it = 129 than it does have a dualmic.

mine's got 129. (not running stock software, everything's been changed)
what value did your A9192 have

I have an Inspire 4g.

jznomoney said:
I have an Inspire 4g.
Click to expand...
Click to collapse
... again, its the same device hardware wise (down to the smaltest spec), just different logo on the metal backing.

If you have time could you test this rom for me
http://forum.xda-developers.com/showthread.php?p=16354726#post16354726

jznomoney said:
Can anyone who has a Telus Model Desire HD post a logcat during boot and a dmesg after boot for me? I am working on a project and need some info.
Click to expand...
Click to collapse
HTC Desire HD, Telus, updated OTA to Gingerbread
here dmesg (part):
<6>[ 0.000000] spade_map_io
<4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 160782
<5>[ 0.000000] Kernel command line: board_spade.disable_uart2=0 board_spade.usb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 board_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=true androidboot.baseband=26.10.04.03_M androidboot.cid=TELUS001 androidboot.batt_poweron=good_battery androidboot.carrier=TELUS androidboot.mid=PD9814000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=xxxxxxxxxxxxTandroidboot.bootloader=0.85.0024 zygote_oneshot=off kmemleak=off no_console_suspend=1 wire.search_count=5
<6>[ 0.000000] diag_set_enabled: 0
<6>[ 0.000000] smd_try_open(diag_set_enabled): 0
<6>[ 0.000000] board_bootloader_setup: 0.85.0024
<6>[ 0.000000] board_bootloader_setup: default ENG BUILD
<6>[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
<6>[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>[ 0.000000] Memory: 320MB 128MB 185MB = 633MB total
<5>[ 0.000000] Memory: 635784k/635784k available, 12408k reserved, 320512K highmem
<5>[ 0.000000] Virtual kernel memory layout:
<5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
<5>[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
<5>[ 0.000000] DMA : 0xffa00000 - 0xffe00000 ( 4 MB)
<5>[ 0.000000] vmalloc : 0xd4800000 - 0xf8000000 ( 568 MB)
<5>[ 0.000000] lowmem : 0xc0000000 - 0xd4000000 ( 320 MB)
<5>[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
<5>[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
<5>[ 0.000000] .init : 0xc0008000 - 0xc0038000 ( 192 kB)
<5>[ 0.000000] .text : 0xc0038000 - 0xc052b000 (5068 kB)
<5>[ 0.000000] .data : 0xc052c000 - 0xc057e640 ( 330 kB)
<6>[ 0.000000] Hierarchical RCU implementation.
<6>[ 0.000000] RCU-based detection of stalled CPUs is disabled.
<6>[ 0.000000] Verbose stalled-CPUs detection is disabled.
<6>[ 0.000000] NR_IRQS:390
<6>[ 0.000000] Calibrating delay loop... 511.18 BogoMIPS (lpj=2555904)
<6>[ 0.240142] pid_max: default: 32768 minimum: 301
<4>[ 0.240386] Mount-cache hash table entries: 512
<6>[ 0.240753] Initializing cgroup subsys debug
<6>[ 0.240783] Initializing cgroup subsys cpuacct
<6>[ 0.240783] Initializing cgroup subsys freezer
<6>[ 0.240814] CPU: Testing write buffer coherency: ok
<6>[ 0.243713] NET: Registered protocol family 16
<6>[ 0.243835] NPA: Init done.
<6>[ 0.244018] msm_ssbi_init()
<6>[ 0.244964] pm8058_init: PMIC 8058
<6>[ 0.245941] spade_init: revision = 129
<6>[ 0.245941] spade_init: microp version =
<6>[ 0.245941] cur_cpu 0x7, id 0x4a
<6>[ 0.245971] socinfo_init: v4, id=74, ver=2.0, raw_id=1392, raw_ver=1392, hw_plat=0, hw_plat_ver=0

Is my Nexus 7 dead?

Okay, I have fastboot and ADB, the only way to get into recovery is through wugs toolkit. I have pushed a ROM to my phone but is says FAILED when I try to flash.
it says TWRP v 2.4.1.0 errors saying
Error flashing zip
Updating partition details...
E:Unable to mount ' /system'
E:Unable to mount ' /cache'
If I use fastboot to try and install recovery, boot, bootloads, or anything it fails as well.
C:\Program Files (x86)\WugFresh Development\data>fastboot devices
xxxxxxxxxxxxxxxxxxxx fastboot
C:\Program Files (x86)\WugFresh Development\data>fastboot erase boot
erasing 'boot'...
OKAY [ 2.531s]
finished. total time: 2.533s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.033s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase system
erasing 'system'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.021s
C:\Program Files (x86)\WugFresh Development\data>fastboot flash bootloader bootl
oader-grouper-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
C:\Program Files (x86)\WugFresh Development\data>fastboot -w update image-nakasi
-jop40d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: xxxxxxxxxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.585s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 0.760s
C:\Program Files (x86)\WugFresh Development\data>
C:\Program Files (x86)\WugFresh Development\data>
(and I get the same for every file I try.
Any help is much appreciated.
Now this is my 4 year olds tablet and we woke up the other morning and it just wouldnt boot anymore. I did unlock it just for fun when we got it a couple months ago but I dont know why it would just not boot into the OS after two months.

In the situation you are in, you should NEVER use fastboot to attempt overflashing of the bootloader. All else, OK.
Try soft-booting (not flashing) a more recent recovery, e.g. TWRP 2.3.x.x or 2.4.x.x
pull it down to your computer & verify it's MD5 sig, then
fastboot boot recovery-image-name.img
If that works, via "adb shell" (once the recovery starts, ADB should work), see if you can do a
# mount /system
# mount /data
if these succeed, that means that each filesystem is OK. (Already mounted counts as a success) If it doesn't you will have to use the mke*fs tools located in the /system/bin or /sbin folder of the TWRP boot to re-initialize the /system, /data partitions as necessary.
My guess though is that if the device failed before all this happened, things might not be fixable.
If you can't even soft-boot a recovery - let us know what error message occurs.

bftb0 said:
In the situation you are in, you should NEVER use fastboot to attempt overflashing of the bootloader. All else, OK.
Try soft-booting (not flashing) a more recent recovery, e.g. TWRP 2.3.x.x or 2.4.x.x
pull it down to your computer & verify it's MD5 sig, then
fastboot boot recovery-image-name.img
If that works, via "adb shell" (once the recovery starts, ADB should work), see if you can do a
# mount /system
# mount /data
if these succeed, that means that each filesystem is OK. (Already mounted counts as a success) If it doesn't you will have to use the mke*fs tools on the /system/bin or /sbin folder of the TWRP boot to re-initialize those filesystems.
My guess though is that if the device failed before all this happened, things might not be fixable.
If you can't even soft-boot a recovery - let us know what error message occurs.
Click to expand...
Click to collapse
I went into fastboot
opened cmd
fastboot boot recovery.img
Recovery booted up
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # mount /system
mount /system
mount: mounting /dev/block/platform/sdhci-tegra.3/by-name/APP on /system failed:
No such file or directory
~ # mount /data
mount /data
mount: mounting /dev/block/platform/sdhci-tegra.3/by-name/UDA on /data failed: N
o such file or directory
~ # # mount /system
# mount /system
~ # # mount /data
# mount /data
~ #
I tried to mount system and data in recovery and it didnt work...i tried cwm 6.0.2.3 and twrp 2.4.1.0
I see files in /sbin folder in recovery, how do I use those files?

well, if you are using the touch version of TWRP the "format data" command rebuilds the filesystem (after nuking it first) with mke2fs.
The command line for mke*fs can have lots of arguments, and off the top of my head I don't know which device plumbed into the kernel is the correct device.
Gimme a minute, I just did a factory reset on my tablet.
But yeah, if you are doing stuff manually from the command line with adb, you will be using the executables in the recovery's /sbin or /system/bin or /system/sbin (e.g. the mke2fs command).
Hang on, gotta check something.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
with your recovery running, type the command
mke2fs --help
you should see something like this:
Code:
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
I believe the commands you will want to use are something like
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
for /data and /system respectively. Give that a roll, power off the device, reboot into the bootloader, and then soft boot into your recovery again and see if /data and /system can be mounted

bftb0 said:
well, if you are using the touch version of TWRP the "format data" command rebuilds the filesystem (after nuking it first) with mke2fs.
The command line for mke*fs can have lots of arguments, and off the top of my head I don't know which device plumbed into the kernel is the correct device.
Gimme a minute, I just did a factory reset on my tablet.
But yeah, if you are doing stuff manually from the command line with adb, you will be using the executables in the recovery's /sbin or /system/bin or /system/sbin (e.g. the mke2fs command).
Hang on, gotta check something.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
with your recovery running, type the command
mke2fs --help
you should see something like this:
Code:
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
I believe the commands you will want to use are something like
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
for /data and /system respectively. Give that a roll, power off the device, reboot into the bootloader, and then soft boot into your recovery again and see if /data and /system can be mounted
Click to expand...
Click to collapse
I get
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
how so I apply the lines
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
I know that sounds dumb but I havent used adb, getting this far this fast feels pretty good. I appreciate your help!!

Skyler2Dope said:
I get
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
how so I apply the lines
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
I know that sounds dumb but I havent used adb, getting this far this fast feels pretty good. I appreciate your help!!
Click to expand...
Click to collapse
just type them in and hit the return key.
report any errors or successes, pls.

NRT v1.6.2 flash this stock rom instead
https://developers.google.com/android/nexus/images#nakasi
i have gotten errors on the flash that the program downloads for you before..
this saved my n7

bradman117 said:
NRT v1.6.2 flash this stock rom instead
https://developers.google.com/android/nexus/images#nakasi
i have gotten errors on the flash that the program downloads for you before..
this saved my n7
Click to expand...
Click to collapse
My partition is shot, I can't do anything with the toolkit. But I'll give it another go
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2096 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.198s
rebooting into bootloader...
OKAY [ 7.302s]
finished. total time: 7.303s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >

should it look like this
C:\Program Files (x86)\WugFresh Development\data>adb shell /sbin/mke2fs/mke2fs -
T ext4 -m 0 /dev/block/mmcblk0p9
/sbin/sh: /sbin/mke2fs/mke2fs: not found

Skyler2Dope said:
should it look like this
C:\Program Files (x86)\WugFresh Development\data>adb shell /sbin/mke2fs/mke2fs -
T ext4 -m 0 /dev/block/mmcblk0p9
/sbin/sh: /sbin/mke2fs/mke2fs: not found
Click to expand...
Click to collapse
add me on gtalk, [email protected]

did you try re-creating those filesystems?
probably you should add /cache in there for good measure
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p4
It is possible that when you are in fastboot mode (bootloader), the bootloader does not rely on having intact filesystems and performs a wipe and re-creation of each filesystem before it unpacks those (sparse) ext4 image files onto the targets.
But what I am suggesting above will give you more visibility into what is going on than using fastboot.
Given that you don't know where the trouble is, as I said before you should not be doing ANYTHING at this time which overflashes the bootloader - including installing full factory images.
---------- Post added at 06:59 PM ---------- Previous post was at 06:58 PM ----------
Skyler2Dope said:
should it look like this
C:\Program Files (x86)\WugFresh Development\data>adb shell /sbin/mke2fs/mke2fs -
T ext4 -m 0 /dev/block/mmcblk0p9
/sbin/sh: /sbin/mke2fs/mke2fs: not found
Click to expand...
Click to collapse
NO. just type
C:\blahblah> adb shell
you will get a different prompt - which means you are using the command line on the phone at that time
and then the commands as shown previously

bftb0 said:
did you try re-creating those filesystems?
probably you should add /cache in there for good measure
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p4
It is possible that when you are in fastboot mode (bootloader), the bootloader does not rely on having intact filesystems and performs a wipe and re-creation of each filesystem before it unpacks those (sparse) ext4 image files onto the targets.
But what I am suggesting above will give you more visibility into what is going on than using fastboot.
Given that you don't know where the trouble is, as I said before you should not be doing ANYTHING at this time which overflashes the bootloader - including installing full factory images.
---------- Post added at 06:59 PM ---------- Previous post was at 06:58 PM ----------
NO. just type
C:\blahblah> adb shell
you will get a different prompt - which means you are using the command line on the phone at that time
and then the commands as shown previously
Click to expand...
Click to collapse
C:\adt-bundle-windows-x86_64\sdk\platform-tools>adb shell
~ # ←[6nmke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs 1.41.12 (17-May-2010)
Could not stat /dev/block/mmcblk0p9 --- No such file or directory
The device apparently does not exist; did you specify it correctly?
~ # ←[6n
does that look right?

Skyler2Dope said:
C:\adt-bundle-windows-x86_64\sdk\platform-tools>adb shell
~ # ←[6nmke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs 1.41.12 (17-May-2010)
Could not stat /dev/block/mmcblk0p9 --- No such file or directory
The device apparently does not exist; did you specify it correctly?
~ # ←[6n
does that look right?
Click to expand...
Click to collapse
It looks right for the stock kernel, but stuff gets plumbed into the device tree differently depending on kernel.
Which recovery are you using?
you could try the "by name" devices:
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC
(UDA -> /data, APP -> /system, CAC -> /cache)
BTW - if you haven't figured it out by now - you get "out of" the remote shell by typing the command "exit". You'll see the prompt change back to the Windows command prompt "C:\blahblahblah>"
Hmmm - those "by-name" entries are symlinks back to the same device names I gave you originally. Well, on the stock kernel anyway.
what does the command "ls -ld /dev/block/*" get you (on the adb shell) ?
---------- Post added at 08:12 PM ---------- Previous post was at 08:07 PM ----------
Send me a link to the place you downloaded your recovery image from, I can soft boot it and take a look.
either that or do a "cat /proc/partitions" and let me know what the output is.

bftb0 said:
It looks right for the stock kernel, but stuff gets plumbed into the device tree differently depending on kernel.
Which recovery are you using?
you could try the "by name" devices:
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC
(UDA -> /data, APP -> /system, CAC -> /cache)
BTW - if you haven't figured it out by now - you get "out of" the remote shell by typing the command "exit". You'll see the prompt change back to the Windows command prompt "C:\blahblahblah>"
Hmmm - those "by-name" entries are symlinks back to the same device names I gave you originally. Well, on the stock kernel anyway.
what does the command "ls -ld /dev/block/*" get you (on the adb shell) ?
---------- Post added at 08:12 PM ---------- Previous post was at 08:07 PM ----------
Send me a link to the place you downloaded your recovery image from, I can soft boot it and take a look.
either that or do a "cat /proc/partitions" and let me know what the output is.
Click to expand...
Click to collapse
I am using TWRP 2.4.1.0
ls -ld /dev/block/* gets me
C:\Program Files (x86)\WugFresh Development\data>adb shell ls -ld /dev/block/*
brw------- 1 root root 7, 0 Jan 2 05:41 /dev/block/loop0
brw------- 1 root root 7, 1 Jan 2 05:41 /dev/block/loop1
brw------- 1 root root 7, 2 Jan 2 05:41 /dev/block/loop2
brw------- 1 root root 7, 3 Jan 2 05:41 /dev/block/loop3
brw------- 1 root root 7, 4 Jan 2 05:41 /dev/block/loop4
brw------- 1 root root 7, 5 Jan 2 05:41 /dev/block/loop5
brw------- 1 root root 7, 6 Jan 2 05:41 /dev/block/loop6
brw------- 1 root root 7, 7 Jan 2 05:41 /dev/block/loop7
C:\Program Files (x86)\WugFresh Development\data>adb shell cat /proc/partitions
major minor #blocks name

.
.
.
.
.
Skyler - we may well have stumbled onto the problem. I booted a couple of different recoveries, and they mostly plumb devices into the same device nodes in /dev/block.
What that suggests is that your partition table got mangled.
If it turns out that this is the case, your question "Is my Nexus 7 dead"? can probably be answered in the affirmative - until someone clever reverse-engineers the Nexus 7's APX mode.
There is a way that you can check this - with the "dmesg" output from your soft-booted recovery.
From the windows prompt, do this:
- soft boot the recovery (so it has been fairly recently booted), and once the ADB link comes up, do this:
C:\ugh> adb shell dmesg > dmesg_out.txt
this (the file "dmesg_out.txt") will have the kernel boot log in it. In an orderly boot, you would see something like this:
Code:
<6>[ 3.629591] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3b78000 prod_name
MMC32G BOOT_MULTI 0x10
<6>[ 3.631511] mmc0: new high speed DDR MMC card at address 0001
<6>[ 3.631716] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 3.632078] mmcblk0: mmc0:0001 MMC32G 29.7 GiB
<6>[ 3.632304] mmcblk0boot0: mmc0:0001 MMC32G partition 1 2.00 MiB
<6>[ 3.632587] mmcblk0boot1: mmc0:0001 MMC32G partition 2 2.00 MiB
<4>[ 3.634589] Primary GPT is invalid, using alternate GPT.
<6>[ 3.634765] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9
<6>[ 3.636710] mmcblk0boot1: unknown partition table
<6>[ 3.637896] mmcblk0boot0: unknown partition table
<6>[ 3.638149] [mmc]:mmc_rescan_try_freq:1907 mmc0: eMMC completed
note that it detects 9 partitions
and further, the command
C:\ugh> adb shell cat /proc/partitions
should display something like this:
Code:
major minor #blocks name
179 0 31178752 mmcblk0
179 1 12288 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 665600 mmcblk0p3
179 4 453632 mmcblk0p4
179 5 512 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 512 mmcblk0p8
179 9 30014464 mmcblk0p9
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
If you are missing a bunch of partitions, you have a problem with the eMMC Flash memory chip that is not currently correctable with tools in the wild.
Is that what you see - errors in the dmesg log, or a lack of partitions in /proc/partitions?

bftb0 said:
.
.
.
.
.
Skyler - we may well have stumbled onto the problem. I booted a couple of different recoveries, and they mostly plumb devices into the same device nodes in /dev/block.
What that suggests is that your partition table got mangled.
If it turns out that this is the case, your question "Is my Nexus 7 dead"? can probably be answered in the affirmative - until someone clever reverse-engineers the Nexus 7's APX mode.
There is a way that you can check this - with the "dmesg" output from your soft-booted recovery.
From the windows prompt, do this:
- soft boot the recovery (so it has been fairly recently booted), and once the ADB link comes up, do this:
C:\ugh> adb shell dmesg > dmesg_out.txt
this (the file "dmesg_out.txt") will have the kernel boot log in it. In an orderly boot, you would see something like this:
Code:
<6>[ 3.629591] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3b78000 prod_name
MMC32G BOOT_MULTI 0x10
<6>[ 3.631511] mmc0: new high speed DDR MMC card at address 0001
<6>[ 3.631716] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 3.632078] mmcblk0: mmc0:0001 MMC32G 29.7 GiB
<6>[ 3.632304] mmcblk0boot0: mmc0:0001 MMC32G partition 1 2.00 MiB
<6>[ 3.632587] mmcblk0boot1: mmc0:0001 MMC32G partition 2 2.00 MiB
<4>[ 3.634589] Primary GPT is invalid, using alternate GPT.
<6>[ 3.634765] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9
<6>[ 3.636710] mmcblk0boot1: unknown partition table
<6>[ 3.637896] mmcblk0boot0: unknown partition table
<6>[ 3.638149] [mmc]:mmc_rescan_try_freq:1907 mmc0: eMMC completed
note that it detects 9 partitions
and further, the command
C:\ugh> adb shell cat /proc/partitions
should display something like this:
Code:
major minor #blocks name
179 0 31178752 mmcblk0
179 1 12288 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 665600 mmcblk0p3
179 4 453632 mmcblk0p4
179 5 512 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 512 mmcblk0p8
179 9 30014464 mmcblk0p9
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
If you are missing a bunch of partitions, you have a problem with the eMMC Flash memory chip that is not currently correctable with tools in the wild.
Is that what you see - errors in the dmesg log, or a lack of partitions in /proc/partitions?
Click to expand...
Click to collapse
<4>[ 2.271075] GTCO usb driver version: 2.00.0006
<6>[ 2.271234] usbcore: registered new interface driver hanwang
<6>[ 2.271401] usbcore: registered new interface driver kbtab
<6>[ 2.271531] kbtab: v0.0.2:USB KB Gear JamStudio Tablet driver
<6>[ 2.271638] usbcore: registered new interface driver wacom
<6>[ 2.271769] wacom: v1.52:USB Wacom tablet driver
<4>[ 2.271841] [ektf3k]:[elan] elan_ktf3k_ts_init
<4>[ 2.272001] [ektf3k]:[ELAN] Start HW reset!
<4>[ 2.529906] [ektf3k]:The boot code is new!
<4>[ 2.709905] INOK=L
<5>[ 2.710168] smb347_charger: [cable_type_detect] Reg3F : 0x93
<5>[ 2.710486] smb347_charger: [cable_type_detect] Reg3E : 0x09
<4>[ 2.710561] Cable: CDP
<4>[ 2.710632] ========================================================
<4>[ 2.710765] battery_callback usb_cable_state = 3
<4>[ 2.710837] ========================================================
<4>[ 2.710978] inok_isr_work_function -
<6>[ 3.259898] cable_detection_work_handler(): vbus_active = 0 and is_active
= 1
<6>[ 3.260032] The USB cable is connected
<4>[ 3.310055] [ektf3k]:[elan] __hello_packet_handler: hello packet 55:55:55:
55
<4>[ 3.310189] [ektf3k]:[elan] hello packet's rc = 0
<4>[ 3.521744] [ektf3k]:[elan] __fw_packet_handler: firmware version: 0xb018
<4>[ 3.523705] [ektf3k]:[elan] __fw_packet_handler: X resolution: 0x0078
<4>[ 3.525607] [ektf3k]:[elan] __fw_packet_handler: Y resolution: 0x00c6
<4>[ 3.546763] [ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3021
<4>[ 3.546901] [ektf3k]:[Elan] Max X=2111, Max Y=1279
<6>[ 3.547105] input: elan-touchscreen as /devices/virtual/input/input0
<4>[ 3.547345] [ektf3k]:The firmware was version 0xB018 and id:0x3021
<4>[ 3.547444] [ektf3k]: /proc/ektf_dbg created
<4>[ 3.547690] [ektf3k]:[elan] Start touchscreen elan-touchscreen in interrup
t mode
<4>[ 3.547877] [ektf3k]:[ELAN]misc_register finished!!
<6>[ 3.548014] elan-ktf3k 1-0010: Update power source to 1
<6>[ 3.548383] in function ____rmi_bus_init____
<6>[ 3.548495] rmi_bus_init: successfully registered RMI bus.
<6>[ 3.548667] rmi_spi_init: registering synaptics spi driver (ref=124)
<6>[ 3.548742] driver.owner = 0x0
<6>[ 3.548872] driver.name = rmi_spi
<6>[ 3.548944] id_table[0].name = rmi
<6>[ 3.549073] id_table[1].name = rmi_spi
<6>[ 3.549145] probe function ptr = 0xc064f2b8
<6>[ 3.549297] in function ____rmi_register_driver____
<6>[ 3.549389] in function ____rmi_get_function_handler____
<6>[ 3.549523] in function ____rmi_get_function_handler____
<6>[ 3.549596] in function ____rmi_get_function_handler____
<6>[ 3.549727] in function ____rmi_get_function_handler____
<6>[ 3.549798] in function ____rmi_get_function_handler____
<6>[ 3.549947] in function ____rmi_get_function_handler____
<6>[ 3.550242] lid_init+ #####
<5>[ 3.550316] hall_sensor: [lid_init] start LID init.....
<6>[ 3.550672] input: lid_input as /devices/virtual/input/input1
<6>[ 3.550875] Wake28 for irq=374
<6>[ 3.551041] Wake28 for irq=374
<6>[ 3.551114] Enabling wake28
<6>[ 3.581073] using rtc device, max77663-rtc, for alarms
<6>[ 3.581222] max77663-rtc max77663-rtc.0: rtc core: registered max77663-rtc
as rtc0
<6>[ 3.581783] i2c /dev entries driver
<6>[ 3.582240] Linux video capture interface: v2.00
<6>[ 3.582387] usbcore: registered new interface driver uvcvideo
<6>[ 3.582461] USB Video Class driver (1.1.1)
<6>[ 3.582652] trpc_sema_init: registered misc dev 10:45
<6>[ 3.582782] trpc_node_register: Adding 'local' to node list
<6>[ 3.583912] nvavp nvavp: allocated IOVM at ff00000 for AVP os
<6>[ 3.584248] tegra_camera tegra_camera: tegra_camera_probe
<6>[ 3.584603] sensor_init+ #####
<6>[ 3.584706] mi1040 sensor_probe
<6>[ 3.584912] sensor_init- #####
<6>[ 3.585084] al3010_init+ #####
<4>[ 3.585157] light sensor info : al3010 init
<4>[ 3.585991] light sensor info : al3010 probe successed
<6>[ 3.586127] al3010 2-001c: driver version 1.0 enabled
<4>[ 3.586355] i2c-core: driver [al3010] using legacy suspend method
<4>[ 3.586491] i2c-core: driver [al3010] using legacy resume method
<6>[ 3.586572] al3010_init- #####
<6>[ 3.586918] device-mapper: uevent: version 1.0.3
<6>[ 3.587154] device-mapper: ioctl: 4.21.0-ioctl (2011-07-06) initialised: d
[email protected]
<6>[ 3.587314] Bluetooth: HCI UART driver ver 2.2
<6>[ 3.587388] Bluetooth: HCI H4 protocol initialized
<6>[ 3.587461] Bluetooth: HCILL protocol initialized
<6>[ 3.587592] Bluetooth: BlueSleep Mode Driver Ver 1.1
<6>[ 3.587714] Wake7 for irq=390
<6>[ 3.588340] cpuidle: using governor ladder
<6>[ 3.588764] cpuidle: using governor menu
<6>[ 3.588884] sdhci: Secure Digital Host Controller Interface driver
<6>[ 3.589016] sdhci: Copyright(c) Pierre Ossman
<6>[ 3.589088] sdhci-pltfm: SDHCI platform and OF driver helper
<6>[ 3.589220] sdhci_tegra_init+ #####
<6>[ 3.589391] sdhci-tegra sdhci-tegra.3: Error: tegra3 io dpd not supported
for sdhci-tegra.3
<4>[ 3.590545] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.591751] Registered led device: mmc0::
<6>[ 3.595172] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using
ADMA
<6>[ 3.595304] sdhci-tegra sdhci-tegra.2: Error: tegra3 io dpd not supported
for sdhci-tegra.2
<4>[ 3.596453] mmc1: Invalid maximum block size, assuming 512 bytes
<7>[ 3.597656] Registered led device: mmc1::
<6>[ 3.599941] mmc1: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using
ADMA
<6>[ 3.600056] sdhci_tegra_init- #####
<7>[ 3.600422] Registered led device: statled
<6>[ 3.601595] tegra-se tegra-se: tegra_se_probe: complete
<6>[ 3.603034] usbcore: registered new interface driver usbhid
<6>[ 3.603175] usbhid: USB HID core driver
<6>[ 3.603501] logger: created 256K log 'log_main'
<6>[ 3.603696] logger: created 256K log 'log_events'
<6>[ 3.603823] logger: created 256K log 'log_radio'
<6>[ 3.604008] logger: created 256K log 'log_system'
<6>[ 4.150710] inv_mpu_probe: Probe name mpu6050
<6>[ 4.150789] i2c i2c-2: MPU6050 is ready to go!
<4>[ 4.151024] i2c-core: driver [LTR_558ALS] using legacy suspend method
<4>[ 4.151100] i2c-core: driver [LTR_558ALS] using legacy resume method
<6>[ 4.152010] inv_ami306_probe: Probe name ami306
<6>[ 4.649906] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
<4>[ 4.690540] rt5640_modinit
<4>[ 4.690642] rt5640_i2c_probe
<4>[ 4.690753] i2c-core: driver [rt5640] using legacy suspend method
<4>[ 4.690885] i2c-core: driver [rt5640] using legacy resume method
<5>[ 4.710594] bq27541_get_psp status: Full ret= 0x0201
<5>[ 4.711314] bq27541_get_psp voltage_now= 4157000 uV
<5>[ 4.711963] bq27541_get_psp current_now= -172000 uA
<5>[ 4.712664] bq27541_get_capacity = 100% ret= 100
<5>[ 4.713310] bq27541_get_psp temperature= 289 (0.1óXC)
<6>[ 4.921173] DSP version code = 0x501a
<4>[ 4.921407] ************************realtek_ce_init_hwdep*****************
********************
<4>[ 4.921545] do_rt5640_dsp_set_mode mode=0
<6>[ 4.921628] rt5640 4-001c: w->name=SDI1 TX Mux
<6>[ 4.921701] rt5640 4-001c: path->name=IF2 path->connect=0
<6>[ 4.921833] rt5640 4-001c: path->name=IF1 path->connect=1
<6>[ 4.921978] rt5640 4-001c: w->name=Stereo DAC MIXL
<6>[ 4.922113] rt5640 4-001c: path->name=DAC L1 Switch connect=1
<6>[ 4.922241] rt5640 4-001c: w->name=Stereo DAC MIXL
<6>[ 4.922375] rt5640 4-001c: path->name=DAC L2 Switch connect=0
<6>[ 4.922655] rt5640 4-001c: w->name=Stereo DAC MIXR
<6>[ 4.922791] rt5640 4-001c: path->name=DAC R1 Switch connect=1
<6>[ 4.922918] rt5640 4-001c: w->name=Stereo DAC MIXR
<6>[ 4.923054] rt5640 4-001c: path->name=DAC R2 Switch connect=0
<6>[ 4.923333] rt5640 4-001c: w->name=Stereo ADC MIXL
<6>[ 4.923410] rt5640 4-001c: path->name=ADC1 Switch connect=1
<6>[ 4.923538] rt5640 4-001c: w->name=Stereo ADC MIXR
<6>[ 4.923613] rt5640 4-001c: path->name=ADC1 Switch connect=1
<6>[ 4.923797] rt5640 4-001c: w->name=Stereo ADC MIXL
<6>[ 4.923873] rt5640 4-001c: path->name=ADC2 Switch connect=1
<6>[ 4.924055] rt5640 4-001c: w->name=Stereo ADC MIXR
<6>[ 4.924130] rt5640 4-001c: path->name=ADC2 Switch connect=1
<6>[ 4.924311] rt5640 4-001c: w->name=Mono ADC MIXL
<6>[ 4.924386] rt5640 4-001c: path->name=ADC2 Switch connect=0
<6>[ 4.924569] rt5640 4-001c: w->name=Mono ADC MIXR
<6>[ 4.924643] rt5640 4-001c: path->name=ADC2 Switch connect=0
<6>[ 4.931835] asoc: rt5640-aif1 <-> tegra30-i2s.1 mapping ok
<6>[ 4.934256] asoc: dit-hifi <-> tegra30-spdif mapping ok
<6>[ 4.938087] asoc: dit-hifi <-> tegra30-i2s.3 mapping ok
<6>[ 4.938881] headset_init+ #####
<4>[ 4.938954] HEADSET: Headset detection init
<4>[ 4.939240] HEADSET: Headset detection mode
<4>[ 4.939315] HEADSET: Config Headset Button detection gpio
<7>[ 4.939389] gpio_request: gpio-186 (btn_INT) status -16
<4>[ 4.939521] HEADSET: Config uart<->headphone gpio
<4>[ 4.939592] HEADSET: Config Jack-in detection gpio
<4>[ 4.939722] HEADSET: Turn on micbias power
<6>[ 4.939800] Wake12 for irq=402
<6>[ 4.939942] Wake12 for irq=402
<6>[ 4.940073] Enabling wake12
<6>[ 4.940145] gpio bank wake found: wake12 for irq=119
<6>[ 4.940217] Enabling wake12
<4>[ 4.959895] HEADSET: Turn off micbias power
<4>[ 4.959977] HEADSET: Config LineOut detection gpio
<7>[ 4.960051] gpio_request: gpio-179 (lineout_int) status -16
<6>[ 4.960182] headset_init- #####
<6>[ 4.960253] ALSA device list:
<6>[ 4.960324] #0: HDA NVIDIA Tegra at 0x70038000 irq 113
<6>[ 4.960453] #1: tegra-rt5640
<6>[ 4.960734] oprofile: using arm/armv7-ca9
<6>[ 4.960914] GACT probability NOT on
<6>[ 4.961050] Mirror/redirect action on
<6>[ 4.961123] u32 classifier
<6>[ 4.961193] Actions configured
<6>[ 4.961325] Netfilter messages via NETLINK v0.30.
<6>[ 4.961462] nf_conntrack version 0.5.0 (15580 buckets, 62320 max)
<6>[ 4.961848] ctnetlink v0.93: registering with nfnetlink.
<6>[ 4.961958] NF_TPROXY: Transparent proxy support initialized, version 4.1.
0
<6>[ 4.962091] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
<6>[ 4.962439] xt_time: kernel timezone is -0000
<6>[ 4.962722] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 4.962960] arp_tables: (C) 2002 David S. Miller
<6>[ 4.963069] TCP cubic registered
<6>[ 4.963314] NET: Registered protocol family 10
<6>[ 4.964057] Mobile IPv6
<6>[ 4.964153] ip6_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 4.964423] IPv6 over IPv4 tunneling driver
<6>[ 4.965272] NET: Registered protocol family 17
<6>[ 4.965424] NET: Registered protocol family 15
<6>[ 4.965602] Bluetooth: RFCOMM TTY layer initialized
<6>[ 4.965687] Bluetooth: RFCOMM socket layer initialized
<6>[ 4.965818] Bluetooth: RFCOMM ver 1.11
<6>[ 4.965891] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[ 4.966024] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>[ 4.966249] NET: Registered protocol family 37
<6>[ 4.966326] VFP support v0.3: implementor 41 architecture 3 part 30 varian
t 9 rev 4
<5>[ 4.966494] Registering SWP/SWPB emulation handler
<4>[ 4.974201] Do not disable PWM clock when kernel inits
<4>[ 4.974289] Disabling clocks left on by bootloader:
<4>[ 4.974361] fuse_burn
<4>[ 4.974498] cclk_lp
<4>[ 4.974570] pll_x_out0
<4>[ 4.974642] pll_d2_out0
<4>[ 4.974712] pll_d_out0
<4>[ 4.974842] pll_p_out2
<4>[ 4.974918] pll_c_out1
<4>[ 4.974992] pll_m_out1
<6>[ 4.975161] CPU rate: 1000 MHz
<3>[ 4.975332] tegra_fuse_program_init: no vdd_fuse. fuse write disabled
<4>[ 4.975836] tegra3_dvfs: minimum cap.cbus rate 228000000 requires 1000 mV
<6>[ 4.976034] tegra dvfs: tegra sysfs cap interface is initialized
<6>[ 4.976374] tegra_actmon.emc: Completed initialization (0)
<6>[ 4.976649] tegra_actmon.avp: Completed initialization (0)
<4>[ 4.977660] regulator_init_complete: fixed_reg_cdc_en: incomplete constrai
nts, leaving on
<4>[ 4.977806] regulator_init_complete: max77663_ldo8: incomplete constraints
, leaving on
<4>[ 4.977945] regulator_init_complete: max77663_ldo4: incomplete constraints
, leaving on
<4>[ 4.978188] ## wifi_probe
<4>[ 4.978323] wifi_set_power = 1
<3>[ 4.978395] Powering on wifi
<4>[ 5.278776] wifi_set_carddetect = 1
<4>[ 5.278986]
<4>[ 5.278989] Dongle Host Driver, version 5.90.195.75
<4>[ 5.278993] Compiled in drivers/net/wireless/bcmdhd on Oct 14 2012 at 16:3
1:58
<3>[ 5.649903] mmc0: error -110 whilst initialising MMC card
<3>[ 7.709905] mmc0: error -110 whilst initialising MMC card
<3>[ 9.769905] mmc0: error -110 whilst initialising MMC card
<3>[ 11.839906] mmc0: error -110 whilst initialising MMC card
<6>[ 11.894505] mmc1: new high speed SDIO card at address 0001
<4>[ 11.895367] F1 signature read @0x18000000=0x16044330
<4>[ 11.899466] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 11.900153] wl_create_event_handler thr:69 started
<4>[ 11.900863] p2p0: P2P Interface Registered
<4>[ 11.901081] dhd_attach thr:6a started
<4>[ 11.901224] dhd_attach thr:6b started
<4>[ 11.901371] dhd_attach thr:6c started
<4>[ 11.901653] wifi_get_mac_addr
<4>[ 11.902142] Broadcom Dongle Host Driver: register interface [wlan0] MAC: 0
0:90:4c:11:22:33
<4>[ 11.902293] wifi_set_power = 0
<3>[ 11.902366] Powering off wifi
<6>[ 11.909977] [mmc]:mmc_rescan_try_freq:1903 mmc1: sdio completed
<4>[ 12.202737] =========== WLAN placed in RESET ========
<6>[ 12.202902] Wake24 for irq=392
<6>[ 12.203228] input: gpio-keys as /devices/platform/gpio-keys.0/input/input2
<6>[ 12.203445] gpio_keys: Released KEY_POWER
<6>[ 12.203523] gpio_keys: Released KEY_VOLUMEUP
<6>[ 12.203654] gpio_keys: Released KEY_VOLUMEDOWN
<6>[ 12.218332] max77663-rtc max77663-rtc.0: setting system clock to 2000-01-0
2 05:54:49 UTC (946792489)
<4>[ 12.218590] Warning: unable to open an initial console.
<6>[ 12.218875] Freeing init memory: 272K
<5>[ 12.225884] bq27541_get_psp status: Full ret= 0x0201
<5>[ 12.226540] bq27541_get_psp voltage_now= 4168000 uV
<5>[ 12.227244] bq27541_get_psp current_now= -10000 uA
<5>[ 12.227888] bq27541_get_capacity = 100% ret= 100
<5>[ 12.228534] bq27541_get_psp temperature= 289 (0.1óXC)
<3>[ 12.283042] init: Unable to open persistent property directory /data/prope
rty errno: 2
<3>[ 12.284820] android_usb: already disabled
<3>[ 12.285298] android_usb: already disabled
<6>[ 12.287073] adb_open
<6>[ 12.287178] adb_open(adbd)
<6>[ 12.287329] adb_bind_config
<6>[ 12.453844] android_work: did not send uevent (0 0 (null))
<5>[ 12.635110] bq27541_get_capacity = 100% ret= 100
<5>[ 12.635916] bq27541_get_psp status: Full ret= 0x0201
<6>[ 12.692380] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 12.719994] set_config : usb set config wake lock ++
<6>[ 12.720088] android_usb gadget: high speed config #1: android
<6>[ 12.720350] android_work: sent uevent USB_STATE=CONFIGURED
<6>[ 13.279938] cable_detection_work_handler(): vbus_active = 0 and is_active
= 1
<6>[ 13.280080] The USB cable is connected
<6>[ 13.280157] elan-ktf3k 1-0010: Update power source to 1
<4>[ 46.107840] adbd (118): /proc/118/oom_adj is deprecated, please use /proc/
118/oom_score_adj instead.
<5>[ 64.800603] bq27541_get_psp status: Full ret= 0x0200
<5>[ 64.801328] bq27541_get_psp voltage_now= 4173000 uV
<5>[ 64.801977] bq27541_get_psp current_now= 73000 uA
<5>[ 64.802680] bq27541_get_capacity = 100% ret= 100
<5>[ 64.803329] bq27541_get_psp temperature= 288 (0.1óXC)
<5>[ 72.747283] bq27541_get_capacity = 100% ret= 100
<5>[ 72.748015] bq27541_get_psp status: Full ret= 0x0200
C:\Program Files (x86)\WugFresh Development\data>
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
YEAH EMPTY lol

Skyler2Dope said:
<4>[ 2.271075]
<6>[ 3.589220] sdhci_tegra_init+ #####
<6>[ 3.589391] sdhci-tegra sdhci-tegra.3: Error: tegra3 io dpd not supported
for sdhci-tegra.3
<4>[ 3.590545] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.591751] Registered led device: mmc0::
<6>[ 3.595172] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using
ADMA
<6>[ 3.595304] sdhci-tegra sdhci-tegra.2: Error: tegra3 io dpd not supported
for sdhci-tegra.2
<4>[ 3.596453] mmc1: Invalid maximum block size, assuming 512 bytes
<7>[ 3.597656] Registered led device: mmc1::
<6>[ 3.599941] mmc1: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using
ADMA
...
<3>[ 5.649903] mmc0: error -110 whilst initialising MMC card
<3>[ 7.709905] mmc0: error -110 whilst initialising MMC card
<3>[ 9.769905] mmc0: error -110 whilst initialising MMC card
<3>[ 11.839906] mmc0: error -110 whilst initialising MMC card
<6>[ 11.894505] mmc1: new high speed SDIO card at address 0001
<4>[ 11.895367] F1 signature read @0x18000000=0x16044330
Click to expand...
Click to collapse
ouch.
Skyler2Dope said:
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
YEAH EMPTY lol
Click to expand...
Click to collapse
Well, that explains that. Some bootloaders (usually S-OFF engineering bootloaders, not public release bootloaders) allow re-partitioning if the device gets completely stuffed up, but generally the public release bootloaders do not - which explains why flashing the factory roms from fastboot mode was failing - it too needs to read the partition table(s).
The Tegra 3 has this mode called "APX" which is similar to the "download mode" on Samsung phones where the PC application "Kies" can be used for manipulating Samsung phones at a very low level, including things like repartitioning the basic flash filesystems. It's what makes those Galaxy phones nearly impossible to brick, short of hardware failure.
Until we have tools for working in APX mode though, situations like yours are a dead end even for rooters.
RMA time? I don't think it was anything you or the 4-year old did by the way - I would engage with Asus/Google with a completely clear conscience.

bftb0 said:
ouch.
Well, that explains that. Some bootloaders (usually S-OFF engineering bootloaders, not public release bootloaders) allow re-partitioning if the device gets completely stuffed up, but generally the public release bootloaders do not - which explains why flashing the factory roms from fastboot mode was failing - it too needs to read the partition table(s).
The Tegra 3 has this mode called "APX" which is similar to the "download mode" on Samsung phones where the PC application "Kies" can be used for manipulating Samsung phones at a very low level, including things like repartitioning the basic flash filesystems. It's what makes those Galaxy phones nearly impossible to brick, short of hardware failure.
Until we have tools for working in APX mode though, situations like yours are a dead end even for rooters.
RMA time? I don't think it was anything you or the 4-year old did by the way - I would engage with Asus/Google with a completely clear conscience.
Click to expand...
Click to collapse
I called and I am doing an RMA, Ill be shipping it off tomorrow or the next day. I will post back if they actually send me another one. Google was amazing by the way, a real pleasure to deal with. I appreciate all the time you and bradman put in tonight to help me figure this out. I REALLY REALLY REALLY appreciate your time and efforts! This has by far been the best experience I have had on any forum! You guys are awesome!

Well they received my device. Waiting to see if I get charged or get a new one.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

bftb0
You deserve a lot more 'thanks' in your posts for doing so much to help the OP.
Sent from my Nexus 7 using xda premium

AOSP Flame Kernel Compiled Sucessfully, but it "failed to find device default fstab"

I tried looking for a solution a lot, but all I managed to get are threads that do relate to development boards: https://community.nxp.com/t5/i-MX-Processors/Android-9-Filesystem-not-Mounted-on-imx6q/m-p/1034102
Or threads that I don't understand: https://github.com/danielfullmer/robotnix/issues/4 ¯\_(ツ)_/¯
Ok, so I did the following to to build the AOSP Flame kernel:
Bash:
mkdir AOSP
cd AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-10.0.0_r41
repo sync -j`nproc`
source ./build/envsetup.sh
lunch aosp_flame-userdebug
m #### build completed successfully (09:45 (mm:ss)) ####
And... All of that worked like a charm. However, when I type emulator, I get a black screen on the emulator window:
{
"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"
}
So, I tried emulator -show-kernel -wipe-data -no-snapshot, which gave me more info in regards to why this isn't working:
Code:
emulator: WARNING: Couldn't find crash service executable /home/mohamed/Desktop/android/kernel/AOSP/prebuilts/android-emulator/linux-x86_64/emulator64-crash-service
emulator: WARNING: encryption is off
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 3.18.94+ ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Feb 12 19:55:24 UTC 2018
Boot CPU: AArch64 Processor [411fd070]
debug: skip boot console de-registration.
efi: Getting EFI parameters from FDT:
efi: UEFI not found.
PERCPU: Embedded 11 pages/cpu @ffffffc07ffdb000 s14272 r0 d30784 u45056
Detected PIPT I-cache on CPU0
CPU features: enabling workaround for ARM erratum 832075
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 517120
Kernel command line: qemu=1 no_timer_check androidboot.hardware=ranchu androidboot.serialno=EMULATOR29X0X1X0 console=ttyAMA0,38400 keep_bootcon earlyprintk=ttyAMA0 android.qemud=1 android.checkjni=1 qemu.gles=1 qemu.settings.system.screen_off_timeout=2147483647 qemu.opengles.version=131072 [email protected] loop.max_part=7 ramoops.mem_address=0xff018000 ramoops.mem_size=0x10000 memmap=0x10000$0xff018000 qemu.dalvik.vm.heapsize=192m mac80211_hwsim.mac_prefix=5554
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Memory: 2056292K/2097152K available (5451K kernel code, 326K rwdata, 1468K rodata, 236K init, 483K bss, 40860K reserved, 0K cma-reserved)
Virtual kernel memory layout:
vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000 ( 247 GB)
vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000 ( 7 GB maximum)
0xffffffbe00000000 - 0xffffffbe01c00000 ( 28 MB actual)
PCI I/O : 0xffffffbffa000000 - 0xffffffbffb000000 ( 16 MB)
fixed : 0xffffffbffbdfb000 - 0xffffffbffbdff000 ( 16 KB)
modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
memory : 0xffffffc000000000 - 0xffffffc080000000 ( 2048 MB)
.init : 0xffffffc00074a000 - 0xffffffc000785000 ( 236 KB)
.text : 0xffffffc000080000 - 0xffffffc0005d4cb0 ( 5460 KB)
.data : 0xffffffc000796000 - 0xffffffc0007e7a00 ( 327 KB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptible hierarchical RCU implementation.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
NR_IRQS:64 nr_irqs:64 0
GIC CPU mask not found - kernel will fail to boot.
GIC CPU mask not found - kernel will fail to boot.
Architected cp15 timer(s) running at 62.50MHz (phys).
sched_clock: 56 bits at 62MHz, resolution 16ns, wraps every 2199023255552ns
Calibrating delay loop (skipped), value calculated using timer frequency.. 125.00 BogoMIPS (lpj=625000)
pid_max: default: 32768 minimum: 301
Security Framework initialized
SELinux: Initializing.
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
Initializing cgroup subsys freezer
Initializing cgroup subsys debug
sched-energy: CPU device node has no sched-energy-costs
Invalid sched_group_energy for CPU0
CPU0: update cpu_capacity 1024
hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 1 counters available
EFI services will not be available.
ASID allocator initialised with 32768 entries
Brought up 1 CPUs
SMP: Total of 1 processors activated.
alternatives: patching kernel code
Invalid sched_group_energy for Cluster0
DMI not present or invalid.
atomic64_test: passed
NET: Registered protocol family 16
vdso: 2 pages (1 code @ ffffffc0005da000, 1 data @ ffffffc00079c000)
hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
software IO TLB [mem 0xbd000000-0xbd400000] (4MB) mapped at [ffffffc07d000000-ffffffc07d3fffff]
DMA: preallocated 256 KiB pool for atomic allocations
Serial: AMBA PL011 UART driver
9000000.pl011: ttyAMA0 at MMIO 0x9000000 (irq = 33, base_baud = 0) is a PL011 rev1
console [ttyAMA0] enabled
SCSI subsystem initialized
Advanced Linux Sound Architecture Driver Initialized.
cfg80211: Calling CRDA to update world regulatory domain
Switched to clocksource arch_sys_counter
NET: Registered protocol family 2
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP: reno registered
UDP hash table entries: 1024 (order: 3, 32768 bytes)
UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 772K
futex hash table entries: 256 (order: 2, 16384 bytes)
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(0.570:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
fuse init (API version 7.23)
io scheduler noop registered
io scheduler cfq registered (default)
brd: module loaded
loop: module loaded
vda: unknown partition table
vdb: unknown partition table
vdc: unknown partition table
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
mac80211_hwsim: initializing netlink
mousedev: PS/2 mouse device common for all mice
input: qwerty2 as /devices/9040000.goldfish-events/input/input0
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.28.0-ioctl (2014-09-17) initialised: [email protected]
hidraw: raw HID events driver (C) Jiri Kosina
ashmem: initialized
u32 classifier
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
ctnetlink v0.93: registering with nfnetlink.
xt_time: kernel timezone is -0000
ip_tables: (C) 2000-2006 Netfilter Core Team
arp_tables: (C) 2002 David S. Miller
TCP: cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 10
mip6: Mobile IPv6
ip6_tables: (C) 2000-2006 Netfilter Core Team
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Bridge firewalling registered
Registered cp15_barrier emulation handler
Registered setend emulation handler
registered taskstats version 1
/buildbot/src/partner-android/n-dev-android-goldfish-3.18-arm64/goldfish/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
Freeing unused kernel memory: 236K
Freeing alternatives memory: 48K
init: init first stage started!
init: Using Android DT directory /proc/device-tree/firmware/android/
init: [libfs_mgr]ReadDefaultFstab(): failed to find device default fstab
init: bool android::init::FirstStageMount::InitRequiredDevices(): partition(s) not found in /sys, waiting for their uevent(s): system
init: Wait for partitions returned after 10011ms
init: bool android::init::FirstStageMount::InitRequiredDevices(): partition(s) not found after polling timeout: system
init: Failed to mount required partitions early ...
init: #00 pc 00000000000e91e0 /init
init: #01 pc 000000000006c4dc /init
init: #02 pc 000000000006ea50 /init
init: #03 pc 00000000000a35d4 /init
init: #04 pc 0000000000064250 /init
init: #05 pc 0000000000145c7c /init
init: Reboot ending, jumping to kernel
reboot: Restarting system with command 'bootloader'
Reboot failed -- System halted
I have been googling for a while now with no success. Any advice is greatly appreciated.

Same here, I face this problem when I run emulator after successfully build AOSP.