Related
Hi all
I'm trying to test a custom 2.2 ROM.
I followed this link http://www.youtube.com/watch?v=UQ5RyvV_IMc
And I get = the emulator is stuck at "A N D R O I D"
Code:
emulator -show-kernel -avd test
Output =
Code:
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: 24384
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: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 96MB = 96MB total
Memory: 93772KB available (2616K code, 681K data, 104K init)
Calibrating delay loop... 276.88 BogoMIPS (lpj=1384448)
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: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
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_audio at ff004000 irq 14
goldfish_new_pdev goldfish_mmc at ff005000 irq 15
goldfish_new_pdev goldfish_memlog at ff006000 irq -1
goldfish_new_pdev goldfish-battery at ff014000 irq 16
goldfish_new_pdev goldfish_events at ff015000 irq 17
goldfish_new_pdev goldfish_nand at ff016000 irq -1
goldfish_new_pdev goldfish-switch at ff017000 irq 18
goldfish_new_pdev goldfish-switch at ff018000 irq 19
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_audio_probe
goldfish_pdev_worker registered goldfish_audio
goldfish_pdev_worker registered goldfish_mmc
goldfish_pdev_worker registered goldfish_memlog
goldfish_pdev_worker registered goldfish-battery
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 183
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 ffa10000
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 c684c000 IRQ 12 [nowait]
eth0: Ethernet addr: 52:54:00:12:34:56
goldfish nand dev0: size 6400000, 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=0xc6854000 irq=17
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-10-01 19:29:37 UTC (1285
961377)
Freeing init memory: 104K
mmc0: new SD card at address e118
mmcblk0: mmc0:e118 SU02G 500 MiB
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 tragedy: attempting to use non-directory as a directory in scan. Put in lo
st+found.
yaffs: dev is 32505857 name is "mtdblock1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.1, "mtdblock1"
yaffs_read_super: isCheckpointed 0
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs_read_super: isCheckpointed 0
init: cannot find '/system/bin/sh', disabling 'console'
init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
init: cannot find '/system/bin/vold', disabling 'vold'
init: cannot find '/system/bin/netd', disabling 'netd'
init: cannot find '/system/bin/debuggerd', disabling 'debuggerd'
init: cannot find '/system/bin/rild', disabling 'ril-daemon'
init: cannot find '/system/bin/app_process', disabling 'zygote'
init: cannot find '/system/bin/mediaserver', disabling 'media'
init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
init: cannot find '/system/bin/installd', disabling 'installd'
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
init: cannot find '/system/bin/keystore', disabling 'keystore'
init: cannot find '/system/etc/init.goldfish.sh', disabling 'goldfish-setup'
init: cannot find '/system/bin/qemud', disabling 'qemud'
init: cannot find '/system/bin/logcat', disabling 'goldfish-logcat'
What am I doing wrong ?
I too would also like to know. Can any of you wise people out their help us out?
Can anyone help us ?
Are you trying to run Sense in emulator?
Well I'm trying to run a rom of the Evo 4g, so that I can get a hint of what its like before I buy it. So yes.
I'm trying to run a Magic ROM, I need to try a APK before I install it on my phone...
As far as i know the only custom rom you can run in emulator is Cyanogenmod (it's the only one i got working).
So how do the dev's test there programs ?
i flash my phone a 1000 times running logcat to see errors thats my secret lol
apks i push with adb to test before making a rom, if it works i build a rom and flash to test yet again, cause sometimes it acts different if flashed so i test both by pushing then flashing
I had an idea.
Create a AVD, unpack the system.img, replace whatever and repack it.
I managed to unpack, but how do I repack ?
Will it work ?
Anyone ???
threeeye said:
I had an idea.
Create a AVD, unpack the system.img, replace whatever and repack it.
I managed to unpack, but how do I repack ?
Will it work ?
Click to expand...
Click to collapse
As the ROM needs to be signed, I don't think this will work...
To unpack and repack, you will probably need to grab a Kitchen.
Hope this helps
Chief
I can unpack the ROM, and I can pack it to a ZIP and sign, but I can't run that in a emulator.
I want to pack it into a system.img (via YAFFS2) but I can't get that to work...
android avd are just dd images?
just examples:
denvertech.org/node/12
rxwen.wordpress.com/2010/09/29/how-to-build-a-nook-emulator-3/
androidforums.com/behold-2-all-things-root/54424-creating-custom-roms-backups-odin.html
i would like to know how i run the last roms like MIUI on android emulator
Try this - worked for me!
I had the same problem once. and I resolved it as follows:
Open
Code:
C:\Documents and Settings\sys\.android\avd\sample.avd
assuming that your OS lives in C:\ and the name of your virtual device is sample.
Open the config file and check if you have specified the path to the system image correctly. It should look something like
Code:
image.sysdir.1=platforms\Copy of android-10\images\
Restart the emulator and see if this works.
Hope this helped
Press 'Thanks' if I helped. I am badly, badly, oh-so-badly in need of it!
Click to expand...
Click to collapse
It seems there is little information on the internet regarding how to compile the kernel and how to convert to the correct image format so the boot loader will recognise and how to transfer it over to the touchpad. I ended up spent a few hours and finally figured out. I hope this will be useful for someone. I will try to make it concise as this is mainly aimed for developers.
What you will need
A linux development machine with uboot mkimage tool installed.
Sourcery G++ Lite 2010q1-188 for ARM EABI cross compile tool chain
https://sourcery.mentor.com/sgpp/lite/arm/portal/release1294
Touchpad kernel source
https://github.com/CyanogenMod/hp-kernel-tenderloin
CM7 Alpha 3 image (zip file)
http://goo-inside.me/roms/cmtouchpad/alpha3/update-cm-7.1.0-tenderloin-a3-fullofbugs-signed.zip
Prepare
Download CM7 Alpha 3 image and extract the boot.img to a temporary place.
Download Sourcery G++ Lite and install it. Add the G++ Lite tool chain binaray path to the PATH env variable. Get the kernel source from git hub and extract to local disk and change directory to the kernel source.
Compile the kernel
Still in the kernel source directory run
Code:
make ARCH=arm CROSS_COMPILE=arm-none-eabi- tenderloin_android_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-eabi- uImage
Prepare the initramfs U-boot image
Extract the initramfs from the boot.img saved in temporary folder and convert it to uboot-image format
Code:
dd if=boot.img bs=1 skip=3577748 of=img.gz
mkimage -A arm -O linux -T ramdisk -C none -a 0x60000000 -e 0x60000000 -n "Image" -d ./img.gz arch/arm/boot/uRamdisk
(The dd offset for alpha 2.1 image is 3561152)
Combine the kernel and initramfs into a single U-boot image
Create a combined U-boot image (kernel and initramfs)
Code:
mkimage -A arm -O linux -T multi -a 0x40208000 -e 0x40208000 -C none -n "multi image" -d arch/arm/boot/uImage:arch/arm/boot/uRamdisk uImage.CyanogenMod.new
Transfer it to the device
Boot your touchpad into recovery mode and run
Code:
adb shell mount /dev/block/mmcblk0p13 /boot
adb push uImage.CyanogenMod.new /boot/uImage.CyanogenMod.new
adb shell umount /boot
adb shell reboot
After it reboot you should be able to see a new CyanogenMod.new item from the boot menu.
That's it!
Optimisation
For those who wants to experiment with GCC build options you can update the entry "arch-$(CONFIG_CPU_32v7" in file arch/arm/Makefile and I set mine to
Code:
arch-$(CONFIG_CPU_32v7) :=-D__LINUX_ARM_ARCH__=7 -mtune=cortex-a8 -mfpu=neon -ftree-vectorize -mfloat-abi=softfp -O2 $(call cc-option,-march=armv7-a,-march=armv5t -Wa$(comma)-march=armv7-a)
Warning
Please be aware you are working on the bleeding edge kernel for touchpad and there is no guarantee that the latest git version will work for you. Please try an earlier version if that's the case.
As of 2011-11-23 you will need the latest kernel source to build kernel for alpha 3. Please do not mix the kernel with an initramfs from a different version, i.e. don't use initramfs extracted from alpha 2.1 and use it with alpha3.
Thanks for this. Last weekend spent a while trying to figure this out.
Sent from my HP Touchpad using Tapatalk
x2. Huge thanks
Thank you soooooo much for this guide. Quick question if you don't mind though.. I am using an mkimage that goes back to my nook kernel days. Is there anything newer out, or would this still be ok,?
Divine_Madcat said:
Thank you soooooo much for this guide. Quick question if you don't mind though.. I am using an mkimage that goes back to my nook kernel days. Is there anything newer out, or would this still be ok,?
Click to expand...
Click to collapse
As long as the mkimage can generate a standard U-boot image it should be fine.
You can always try it yourself. In worst case you have to hard reboot the touchpad by pressing the power button and home button at the same time for more than 10 minutes. As long as you keep the original image files (UImage.*) untouched I don't think you can brick it even if you want to.
S7
I have been trying to compile the kernel for some time now, and was hopeful reading your guide (and this last post) However, still following the steps to merge the ramdisk, i cannot make a booting kernel. I can get it flashed, as i am using the update.zip method, but moboot always gives me a crc error when booting it.
Though, before i totally go nuts, i think i need to try the source forgery toolchain, as i am using the Android ndk r6b...
Divine_Madcat said:
S7
I have been trying to compile the kernel for some time now, and was hopeful reading your guide (and this last post) However, still following the steps to merge the ramdisk, i cannot make a booting kernel. I can get it flashed, as i am using the update.zip method, but moboot always gives me a crc error when booting it.
Though, before i totally go nuts, i think i need to try the source forgery toolchain, as i am using the Android ndk r6b...
Click to expand...
Click to collapse
Could you check the md5sum of the u-boot image crated on disk and the one installed by update.zip file? Do they match? If they do then you probably will need to upgrade your mkimage tool.
s7mx1 said:
Could you check the md5sum of the u-boot image crated on disk and the one installed by update.zip file? Do they match? If they do then you probably will need to upgrade your mkimage tool.
Click to expand...
Click to collapse
I will give it a check; just in case, know where to get a newer mkimage?
Thanks so much for this guide
s7mx1 said:
You can always try it yourself. In worst case you have to hard reboot the touchpad by pressing the power button and home button at the same time for more than 10 minutes.
Click to expand...
Click to collapse
It feels like 10 mins.. doesn't it
WEll, i checked the MD5 sums, and it looks good. So, i guess it is time to try again with the toolchain listed here, and perhaps a new mkimage (if there is a "modern" one i should using, please point me to it...)
edit: Never mind.. in all my looking, i never saw that ubuntu had a nice one waiting for me.... doh
edit2: Woo! After getting the probably correct mkimage, and the CS toolchain, looks like i finally got it to pass the crc check. Now, lets see if it finishes booting. Thanks again for the guide!
Nope.. no boot. I get a dmesg with this:
<3>[ 69.978716] init: untracked pid 224 exited
<6>[ 70.086076] android_usb gadget: high speed config #1: android
<6>[ 70.086209] gadget_event: schedule host_connected
<6>[ 70.096953] max8903b_current_setup: CURRENT_500MA
<6>[ 70.097040] gadget_event: source=bus mA=500 (no change)
<4>[ 70.910953] UDC-CHG (2-2-2): usb_multi_chg_detect (591) : USB host Adaptor
(500mA)!
<6>[ 70.912805] gadget_event: schedule host_disconnected
<6>[ 70.925482] max8903b_current_setup: CURRENT_ZERO
<6>[ 71.164066] android_usb gadget: high speed config #1: android
<6>[ 71.164220] gadget_event: schedule host_connected
<6>[ 71.173640] max8903b_current_setup: CURRENT_500MA
<6>[ 71.178212] gadget_event: source=bus mA=500 (no change)
<6>[ 72.160955] gadget_event: host_connected=1 (no change)
<6>[ 74.142224] request_suspend_state: wakeup (0->0) at 74121495501 (2011-11-1
1 22:49:33.378031648 UTC)
<3>[ 74.143675] init: untracked pid 266 exited
<3>[ 74.155217] init: untracked pid 273 exited
<6>[ 79.285016] request_suspend_state: wakeup (0->0) at 79264287462 (2011-11-1
1 22:49:38.520824942 UTC)
The last three lines repeat alot, with different pid's .
Alrighty.. figured this one out - You cannot use the latest repository commits with the 2.1 alpha build. However, i was able to build commit fd70bb7aae, and it builds and actually boots. Now, i can actually play around and tweak it. Thank you again for the guide, and sorry for the edit spamming.. heh.
myn said:
x2. Huge thanks
Click to expand...
Click to collapse
Myn, do you have a touchpad???!!!? God I hope so!
vinscuzzy said:
Myn, do you have a touchpad???!!!? God I hope so!
Click to expand...
Click to collapse
He does
Sent from my PG86100 using Tapatalk
Divine_Madcat said:
WEll, i checked the MD5 sums, and it looks good. So, i guess it is time to try again with the toolchain listed here, and perhaps a new mkimage (if there is a "modern" one i should using, please point me to it...)
edit: Never mind.. in all my looking, i never saw that ubuntu had a nice one waiting for me.... doh
edit2: Woo! After getting the probably correct mkimage, and the CS toolchain, looks like i finally got it to pass the crc check. Now, lets see if it finishes booting. Thanks again for the guide!
Nope.. no boot. I get a dmesg with this:
<3>[ 69.978716] init: untracked pid 224 exited
<6>[ 70.086076] android_usb gadget: high speed config #1: android
<6>[ 70.086209] gadget_event: schedule host_connected
<6>[ 70.096953] max8903b_current_setup: CURRENT_500MA
<6>[ 70.097040] gadget_event: source=bus mA=500 (no change)
<4>[ 70.910953] UDC-CHG (2-2-2): usb_multi_chg_detect (591) : USB host Adaptor
(500mA)!
<6>[ 70.912805] gadget_event: schedule host_disconnected
<6>[ 70.925482] max8903b_current_setup: CURRENT_ZERO
<6>[ 71.164066] android_usb gadget: high speed config #1: android
<6>[ 71.164220] gadget_event: schedule host_connected
<6>[ 71.173640] max8903b_current_setup: CURRENT_500MA
<6>[ 71.178212] gadget_event: source=bus mA=500 (no change)
<6>[ 72.160955] gadget_event: host_connected=1 (no change)
<6>[ 74.142224] request_suspend_state: wakeup (0->0) at 74121495501 (2011-11-1
1 22:49:33.378031648 UTC)
<3>[ 74.143675] init: untracked pid 266 exited
<3>[ 74.155217] init: untracked pid 273 exited
<6>[ 79.285016] request_suspend_state: wakeup (0->0) at 79264287462 (2011-11-1
1 22:49:38.520824942 UTC)
The last three lines repeat alot, with different pid's .
Alrighty.. figured this one out - You cannot use the latest repository commits with the 2.1 alpha build. However, i was able to build commit fd70bb7aae, and it builds and actually boots. Now, i can actually play around and tweak it. Thank you again for the guide, and sorry for the edit spamming.. heh.
Click to expand...
Click to collapse
That's because dalingrin has updated the default configuration to use the HIGHMEM which seems to kill all the apps. The latest git actually works if you disable all the HIGHMEM related stuff.
decalex said:
Thanks so much for this guide
It feels like 10 mins.. doesn't it
Click to expand...
Click to collapse
Absolutely
I just hope there is a rest button as the touchscreen occasionally will not respond at all after wake up and I have to reboot to webos and then reboot back to get the touchscreen back.
Great guide and I got the kernel all built, but how do you change the kernel arguments for booting? e.g. where does moboot get its whole root=/dev/ram0 ro fb...stuff, and how does the CyanogenMod kernel know where to look for the rootfs partition?
crimsonredmk said:
Great guide and I got the kernel all built, but how do you change the kernel arguments for booting? e.g. where does moboot get its whole root=/dev/ram0 ro fb...stuff, and how does the CyanogenMod kernel know where to look for the rootfs partition?
Click to expand...
Click to collapse
The root parameter (root=/dev/ram0) that passed to kernel is not useful to you. The root / is mere extracted initramfs in memory. I assume you are looking for system, data partitions etc. With TP we have LVM partitions which you can do really fancy stuff with. The actual mount device and mount point is defined (hard coded) in file init.tenderloin.rc which you can find in the initramfs (i.e. the img.gz which is a gzipped cpio file). You can extract all the contents out from img.gz and modify init.tenderloin.rc to suit your need and then create an updated initramfs file to go with the kernel.
Since Android (at least CM7 on TP) does not use pivot_root any changes made to the initramfs will appear automatically when you boot up the device.
You can google if you are not sure how to work with initramfs file.
This is my first thread/post in the forum, so I am not quite sure if this is the right place for this question. I recently happened to see a schematic diagram of the GT-S5360. I noticed that the main chipset includes support for USBOTG HS(480 Mbps).
http://forum.xda-developers.com/showthread.php?t=1489767
If this is indeed true, is there any way we can enable this feature in the GT-S5360? I mean, is there a custom ROM/Kernel which enables this feature?
Apologies if I have posted this in the wrong section.
If you have usb otg cable then try kuro and merruk kernel....
And search before posting
Sent from my GT-S5360 using xda premium
Hi, please look in the dev section. We already have 2-3 kernels which enable us to use this feature, if i'm not wrong.
Sent from my GT-S5360 using xda premium
that is a block diagram not schematic
alkesh95 said:
If you have usb otg cable then try kuro and merruk kernel....
And search before posting
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
Thanks for the response Alkesh, I will try those. I had infact searched for something similar in the forum but could not come up with any names - maybe I did something wrong. I found this though: http://forum.xda-developers.com/showthread.php?t=1493325
my kernel didn't support it
my kernel is based on samsung's sourcode. on other hand, our "beloved" samsung have messed up the source code. thus, make the OTG stuff on the kernel didn't work.
kurotsugi said:
my kernel didn't support it
my kernel is based on samsung's sourcode. on other hand, our "beloved" samsung have messed up the source code. thus, make the OTG stuff on the kernel didn't work.
Click to expand...
Click to collapse
Thanks for clarifying Kurotsugi. So is there any kernel which supports this feature currently? I searched the development forums - seems Merruk also doesnt support this feature currently, Maroc-OS is working on it as I understand from http://forum.xda-developers.com/showthread.php?t=1550065
xdroid_noob said:
Thanks for clarifying Kurotsugi. So is there any kernel which supports this feature currently? I searched the development forums - seems Merruk also doesnt support this feature currently, Maroc-OS is working on it as I understand from http://forum.xda-developers.com/showthread.php?t=1550065
Click to expand...
Click to collapse
if you have the cable you can try that.
ask samsung
works now
Hi guys.
Sorry for necroposting.
Also this post should probably go to development section, but I don't have access to post there (yet?).
First of all, BCM21553 seems to lack ID pin. ID pin from USB connector goes straight to PMU chip instead.
It is used to detect the type of the charger as far as I can tell.
It's not a big deal to extend PMU isr's to support OTG cable as a different type of charger (yes, external +5v source is required).
The real trick (for me) was to find a way to force DWC core into Host mode. Looks like Synopsis is no longer sharing datasheets with public.
Luckily Broadcom is not the only company which uses the same USB IP.
It looks like DWC driver was designed for an older kernel version.
It was partly ported by Samsung, but only as much as required to support the device mode.
It's still very flaky and fragile. For instance, it you try to cat /sys/devices/lm-2/mode, it will panic the stock kernel.
All HC code is non-functional and does not even build out of the box.
It took me almost a week to fix all the bugs and to be able to build standalone dwc_otg.ko with working HC code.
At the moment I managed to successfully mount a memory stick on my phone. Device mode is not there yet, but I don't really need it:
I'm building a telemetry project and I need the cheapest solution.
If anypony is still interested in HC on SGY, please reply and I will follow up with more details.
thats pretty awesome news.....this should be moved to development section......
Sent from my Typewriter
A bit of logs to support my statement
Code:
<6>[ 1185.825469] dwc_otg: version 2.60a 22-NOV-2006
<6>[ 1185.825531] lm_driver_register()
<6>[ 1185.825592] lm_match()
<6>[ 1185.825622] lm_bus_probe()
<3>[ 1185.825653] Debug level= 17
<3>[ 1185.825683] dwc_otg lm-2: dwc_otg_driver_probe, version 020-10-01-09
<6>[ 1185.826019] It is Ok to create charging current work queue...
<4>[ 1185.826080] >> create: c483f5e0
<6>[ 1185.826324] start_usb_clk_phy
<4>[ 1185.826354] DWC_otg: 1
<4>[ 1185.826385] DWC_otg: 2
<4>[ 1185.826416] DWC_otg: dwc_otg_core_reset() GRSTCTL=80000000
<4>[ 1185.826446] DWC_otg: dwc_otg_core_reset() value to set=80000001
<4>[ 1185.826477] DWC_otg: 3
<4>[ 1185.931610] DWC_otg: 1
<4>[ 1185.931640] DWC_otg: 2
<4>[ 1185.931671] DWC_otg: dwc_otg_core_reset() GRSTCTL=80000000
<4>[ 1185.931701] DWC_otg: dwc_otg_core_reset() value to set=80000001
<4>[ 1185.931701] DWC_otg: 3
<4>[ 1186.853454] >>>> unicorn 1
<4>[ 1186.853485] dwc_otg_pcd_init(c483f5e0)
<4>[ 1186.853485] Dedicated Tx FIFOs mode
<4>[ 1186.853607] registering handler for irq21
<6>[ 1186.853698] DWC_otg: pcd->setup_pkt=0xff6b3000, pcd->setup_pkt_dma_handle=0x82982000
<6>[ 1186.853729] DWC_otg: pcd->status_buf=0xff6b4000, pcd->status_buf_dma_handle=0x85d33000
<4>[ 1186.853729] pcd->setup_pkt=0xff6b3000, pcd->setup_pkt_dma_handle=0x82982000
<4>[ 1186.853759] pcd->status_buf=0xff6b4000, pcd->status_buf_dma_handle=0x85d33000
<6>[ 1186.853790] DWC_otg: Using DMA mode
<6>[ 1186.853820] dwc_otg lm-2: DWC OTG Controller
<6>[ 1186.853851] dwc_otg lm-2: new USB bus registered, assigned bus number 1
<6>[ 1186.853912] dwc_otg lm-2: irq 21, io mem 0x00000000
<6>[ 1186.853973] DWC_otg: Init: Port Power? op_state=1
<6>[ 1186.853973] DWC_otg: Init: Power Port (0)
<7>[ 1186.854064] usb usb1: default language 0x0409
<7>[ 1186.854125] usb usb1: udev 1, busnum 1, minor = 0
<6>[ 1186.854156] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 1186.854156] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 1186.854187] usb usb1: Product: DWC OTG Controller
<6>[ 1186.854217] usb usb1: Manufacturer: Linux 2.6.35.7 dwc_otg_hcd
<6>[ 1186.854217] usb usb1: SerialNumber: lm-2
<7>[ 1186.856048] usb usb1: usb_probe_device
<7>[ 1186.856109] usb usb1: configuration #1 chosen from 1 choice
<7>[ 1186.856170] usb usb1: adding 1-0:1.0 (config #1, interface 0)
<7>[ 1186.857482] hub 1-0:1.0: usb_probe_interface
<7>[ 1186.857513] hub 1-0:1.0: usb_probe_interface - got id
<6>[ 1186.857543] hub 1-0:1.0: USB hub found
<6>[ 1186.857604] hub 1-0:1.0: 1 port detected
<7>[ 1186.857604] hub 1-0:1.0: standalone hub
<7>[ 1186.857635] hub 1-0:1.0: ganged power switching
<7>[ 1186.857666] hub 1-0:1.0: individual port over-current protection
<7>[ 1186.857666] hub 1-0:1.0: Single TT
<7>[ 1186.857696] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
<7>[ 1186.857696] hub 1-0:1.0: power on to power good time: 2ms
<7>[ 1186.857757] hub 1-0:1.0: local power source is good
<7>[ 1186.857757] hub 1-0:1.0: enabling power on all ports
<7>[ 1186.955078] hub 1-0:1.0: port 1: status 0101 change 0001
<7>[ 1187.056640] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
<7>[ 1187.056701] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
<6>[ 1187.251861] usb 1-1: new high speed USB device using dwc_otg and address 2
<7>[ 1187.472076] usb 1-1: default language 0x0409
<7>[ 1187.473388] usb 1-1: udev 2, busnum 1, minor = 1
<6>[ 1187.473419] usb 1-1: New USB device found, idVendor=8564, idProduct=1000
<6>[ 1187.473449] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1187.473480] usb 1-1: Product: Mass Storage Device
<6>[ 1187.473510] usb 1-1: Manufacturer: JetFlash
<6>[ 1187.473541] usb 1-1: SerialNumber: 5550N3UJAP62NU0R
<7>[ 1187.475555] usb 1-1: usb_probe_device
<7>[ 1187.475616] usb 1-1: configuration #1 chosen from 1 choice
<7>[ 1187.475830] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
<7>[ 1187.477294] libusual 1-1:1.0: usb_probe_interface
<7>[ 1187.477355] libusual 1-1:1.0: usb_probe_interface - got id
<7>[ 1187.477447] usb-storage 1-1:1.0: usb_probe_interface
<7>[ 1187.477478] usb-storage 1-1:1.0: usb_probe_interface - got id
<6>[ 1187.477874] scsi3 : usb-storage 1-1:1.0
<7>[ 1187.482482] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
<7>[ 1187.482543] hub 1-0:1.0: port 1 enable change, status 00000503
<5>[ 1188.822296] scsi 3:0:0:0: Direct-Access JetFlash Transcend 8GB 1100 PQ: 0 ANSI: 0 CCS
<5>[ 1188.829681] sd 3:0:0:0: [sda] 15826944 512-byte logical blocks: (8.10 GB/7.54 GiB)
<5>[ 1188.830444] sd 3:0:0:0: [sda] Write Protect is off
<7>[ 1188.830505] sd 3:0:0:0: [sda] Mode Sense: 43 00 00 00
<3>[ 1188.830535] sd 3:0:0:0: [sda] Assuming drive cache: write through
<3>[ 1188.834808] sd 3:0:0:0: [sda] Assuming drive cache: write through
<6>[ 1188.834930] sda:
<3>[ 1188.841308] sd 3:0:0:0: [sda] Assuming drive cache: write through
<5>[ 1188.841339] sd 3:0:0:0: [sda] Attached SCSI removable disk
<4>[ 1192.035308] wl_iw_event: dev=eth0 event=20
/mnt/sdcard/mod # mount -r -t vfat /dev/block/sda /sdcard/media
/mnt/sdcard/mod # busybox df /sdcard/media
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/sda 7898024 3906992 3991032 49% /mnt/sdcard/media
/mnt/sdcard/mod # ls /sdcard/media
ubninit
EFI
ubnkern
boot
casper
dists
install
isolinux
pics
pool
preseed
ubnpathl.txt
README.diskdefines
autorun.inf
md5sum.txt
wubi.exe
ubnfilel.txt
ldlinux.sys
syslinux.cfg
menu.c32
HBCD
/mnt/sdcard/mod #
/mnt/sdcard/media # lsmod
dwc_otg 125404 0 - Live 0xbf262000
sd_mod 26464 1 - Live 0xbf136000
usb_storage 34867 1 - Live 0xbf257000
usb_libusual 9839 1 usb_storage, Live 0xbf09c000
scsi_mod 124018 2 sd_mod,usb_storage, Live 0xbf228000
lm 2661 1 dwc_otg, Live 0xbf055000
usbcore 146797 3 dwc_otg,usb_storage,usb_libusual, Live 0xbf18d000
bcm4330 275939 0 - Live 0xbf147000
brcm_headsetsw 7603 0 - Live 0xbf13f000
gememalloc 661 0 - Live 0xbf133000 (P)
h6270enc 3469 0 - Live 0xbf12d000
hx170dec 5362 0 - Live 0xbf125000
sec_param 8980 0 - Live 0xbf11d000
j4fs 70799 1 - Live 0xbf105000 (P)
rfs_fat 247794 3 - Live 0xbf0bd000 (P)
rfs_glue 79181 1 rfs_fat, Live 0xbf0a1000 (P)
fsr_stl 255325 5 j4fs, Live 0xbf05b000 (P)
fsr 338224 2 sec_param,fsr_stl, Live 0xbf000000 (P)
/mnt/sdcard/media #
Currently I'm working on PMU driver to allow the phone to charge while connected via Y-cable.
Once ready I'll post some binaries and patches against stock kernel sources so you will be able to try it out, or take over if you would like to.
After that I could probably try to restore gadget functionality as loadable module and probably add something to switch device/host mode automatically based on cable type.
But personally I don't need gadget functionality at all, so I'm not sure when I will be able to find enough spare time to do this.
PS.
Please don't move it to development section just yet - I won't be able to post there (need 10 posts or something like that).
Here we go, as promised.
I've decided to test whether SGY is powerful enough to play movies from external USB HDD drive with truecrypted ext4 fs.
It turns out to be good enough.
Code:
/mnt/sdcard/mod # busybox cp ../dmsetup /dev
/mnt/sdcard/mod # busybox chmod +x /dev/dmsetup
/mnt/sdcard/mod # insmod usbcore.ko
/mnt/sdcard/mod # insmod lm.ko
/mnt/sdcard/mod # insmod dwc_otg.ko
/mnt/sdcard/mod # insmod scsi_mod.ko
/mnt/sdcard/mod # insmod sd_mod.ko
/mnt/sdcard/mod # insmod usb-libusual.ko
/mnt/sdcard/mod # insmod usb-storage.ko
/mnt/sdcard/mod # busybox ls -l /dev/block/sda
brw------- 1 0 0 8, 0 Jul 20 04:18 /dev/block/sda
/mnt/sdcard/mod # insmod gf128mul.ko
/mnt/sdcard/mod # insmod xts.ko
/mnt/sdcard/mod # /dev/dmsetup create tc0 --table "0 976772656 crypt aes-xts-pla
in64 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 256 8:0 256"
/mnt/sdcard/mod # insmod jbd2.ko
/mnt/sdcard/mod # insmod ext4.ko
/mnt/sdcard/mod # mount -t ext4 -r /dev/mapper/tc0 /sdcard/media
/mnt/sdcard/mod # am start -n com.mxtech.videoplayer.ad/.ActivityScreen -d /mnt/sdcard/media/Videos/cartoon/mlp/My.Little.Pony.Friendship.Is.Magic.S01E26.The.Best.Night.Ever.480p.WEB-DL.DD5.1.h.264-ETP.mkv
Attachment contains kernel update which you can flash using recovery mode.
Basically, it is an ordinary Samsung kernel without any USB code and with some minor hw-related tweaks.
modules.tar.bz2 contains all modules from snippet above plus HID and FTDI support.
It's huge because of ext4.ko. You probably won't need it.
dwc_otg.ko is USB driver itself. At the moment it has host-only functionality.
It means - it is a very bad idea to connect your phone to PC with this module loaded. Be warned.
Also, I'm using Y-cabe with 30k resistor between D+ and D-. This way MUIC thinks that phone is plugged into 1A charger.
At the same time, D+/D- is routed USB PHY. This hack is statically linked into the kernel.
So - don't try to charge your phone with this kernel with chargers with D+/D- shortened.
Oh, yeah. ID pin connection is irrelevant at the moment, so you can hack any micro-usb cable in the middle - no complex soldering required.
Disclaimer: You may brick your phone. Do it on your own risk. This post is developer-oriented.
If you do not fully understand what's written above - better don't do it at all.
uunicorn said:
Here we go, as promised.
I've decided to test whether SGY is powerful enough to play movies from external USB HDD drive with truecrypted ext4 fs.
It turns out to be good enough.
Code:
/mnt/sdcard/mod # busybox cp ../dmsetup /dev
/mnt/sdcard/mod # busybox chmod +x /dev/dmsetup
/mnt/sdcard/mod # insmod usbcore.ko
/mnt/sdcard/mod # insmod lm.ko
/mnt/sdcard/mod # insmod dwc_otg.ko
/mnt/sdcard/mod # insmod scsi_mod.ko
/mnt/sdcard/mod # insmod sd_mod.ko
/mnt/sdcard/mod # insmod usb-libusual.ko
/mnt/sdcard/mod # insmod usb-storage.ko
/mnt/sdcard/mod # busybox ls -l /dev/block/sda
brw------- 1 0 0 8, 0 Jul 20 04:18 /dev/block/sda
/mnt/sdcard/mod # insmod gf128mul.ko
/mnt/sdcard/mod # insmod xts.ko
/mnt/sdcard/mod # /dev/dmsetup create tc0 --table "0 976772656 crypt aes-xts-pla
in64 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 256 8:0 256"
/mnt/sdcard/mod # insmod jbd2.ko
/mnt/sdcard/mod # insmod ext4.ko
/mnt/sdcard/mod # mount -t ext4 -r /dev/mapper/tc0 /sdcard/media
/mnt/sdcard/mod # am start -n com.mxtech.videoplayer.ad/.ActivityScreen -d /mnt/sdcard/media/Videos/cartoon/mlp/My.Little.Pony.Friendship.Is.Magic.S01E26.The.Best.Night.Ever.480p.WEB-DL.DD5.1.h.264-ETP.mkv
Attachment contains kernel update which you can flash using recovery mode.
Basically, it is an ordinary Samsung kernel without any USB code and with some minor hw-related tweaks.
modules.tar.bz2 contains all modules from snippet above plus HID and FTDI support.
It's huge because of ext4.ko. You probably won't need it.
dwc_otg.ko is USB driver itself. At the moment it has host-only functionality.
It means - it is a very bad idea to connect your phone to PC with this module loaded. Be warned.
Also, I'm using Y-cabe with 30k resistor between D+ and D-. This way MUIC thinks that phone is plugged into 1A charger.
At the same time, D+/D- is routed USB PHY. This hack is statically linked into the kernel.
So - don't try to charge your phone with this kernel with chargers with D+/D- shortened.
Oh, yeah. ID pin connection is irrelevant at the moment, so you can hack any micro-usb cable in the middle - no complex soldering required.
Disclaimer: You may brick your phone. Do it on your own risk. This post is developer-oriented.
If you do not fully understand what's written above - better don't do it at all.
Click to expand...
Click to collapse
Dude what you are doing is great but the problem is its too much difficult for average member to understand what all this means....you should give a better discription about what you have done with the kernel and what is the advantage of that and how it will work.....uploading kernels like this could lead to someone bricking their phone....
According to me you should team up with someone and make a thread in dev section.....
Sent from my Dishwasher
-HellRaiser- said:
you should give a better discription about what you have done with the kernel and what is the advantage of that and how it will work.....
Click to expand...
Click to collapse
Yes, I know, but there is nothing user-friendly to show yet.
There is not much profit for an avg phone user until automatic switching between host and device mode is added.
After this feature is implemented in usb driver, it could be incorporated into someones custom kernel distribution and OTG will just work out of the box.
At the moment it is just an ongoing development, which I would like to share with other developers, because I do not think I have enough motivation to finish everything by myself.
-HellRaiser- said:
uploading kernels like this could lead to someone bricking their phone....
Click to expand...
Click to collapse
Hence all the warnings.
-HellRaiser- said:
According to me you should team up with someone and make a thread in dev section.....
Click to expand...
Click to collapse
There is a thread about OTG on SGY already in development section, but I can't even bump it - no rights to post there.
Someone could probably post a link to this thread there, I suppose.
uunicorn said:
There is a thread about OTG on SGY already in development section, but I can't even bump it - no rights to post there.
Someone could probably post a link to this thread there, I suppose.
Click to expand...
Click to collapse
I bumped it for you :good:
btw, I think you need 10 posts in order to start a thread or post on development section.
anyways, keep up the good work!!!
uunicorn said:
Yes, I know, but there is nothing user-friendly to show yet.
There is not much profit for an avg phone user until automatic switching between host and device mode is added.
After this feature is implemented in usb driver, it could be incorporated into someones custom kernel distribution and OTG will just work out of the box.
At the moment it is just an ongoing development, which I would like to share with other developers, because I do not think I have enough motivation to finish everything by myself.
Hence all the warnings.
There is a thread about OTG on SGY already in development section, but I can't even bump it - no rights to post there.
Someone could probably post a link to this thread there, I suppose.
Click to expand...
Click to collapse
uunicorn said:
Yes, I know, but there is nothing user-friendly to show yet.
There is not much profit for an avg phone user until automatic switching between host and device mode is added.
After this feature is implemented in usb driver, it could be incorporated into someones custom kernel distribution and OTG will just work out of the box.
At the moment it is just an ongoing development, which I would like to share with other developers, because I do not think I have enough motivation to finish everything by myself.
Hence all the warnings.
There is a thread about OTG on SGY already in development section, but I can't even bump it - no rights to post there.
Someone could probably post a link to this thread there, I suppose.
Click to expand...
Click to collapse
what need to doing ?
flash your kernel
for what is modules and dmsetup ?
I can't understand ?
uunicorn said:
Here we go, as promised.
I've decided to test whether SGY is powerful enough to play movies from external USB HDD drive with truecrypted ext4 fs.
It turns out to be good enough.
Code:
/mnt/sdcard/mod # busybox cp ../dmsetup /dev
/mnt/sdcard/mod # busybox chmod +x /dev/dmsetup
/mnt/sdcard/mod # insmod usbcore.ko
/mnt/sdcard/mod # insmod lm.ko
/mnt/sdcard/mod # insmod dwc_otg.ko
/mnt/sdcard/mod # insmod scsi_mod.ko
/mnt/sdcard/mod # insmod sd_mod.ko
/mnt/sdcard/mod # insmod usb-libusual.ko
/mnt/sdcard/mod # insmod usb-storage.ko
/mnt/sdcard/mod # busybox ls -l /dev/block/sda
brw------- 1 0 0 8, 0 Jul 20 04:18 /dev/block/sda
/mnt/sdcard/mod # insmod gf128mul.ko
/mnt/sdcard/mod # insmod xts.ko
/mnt/sdcard/mod # /dev/dmsetup create tc0 --table "0 976772656 crypt aes-xts-pla
in64 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 256 8:0 256"
/mnt/sdcard/mod # insmod jbd2.ko
/mnt/sdcard/mod # insmod ext4.ko
/mnt/sdcard/mod # mount -t ext4 -r /dev/mapper/tc0 /sdcard/media
/mnt/sdcard/mod # am start -n com.mxtech.videoplayer.ad/.ActivityScreen -d /mnt/sdcard/media/Videos/cartoon/mlp/My.Little.Pony.Friendship.Is.Magic.S01E26.The.Best.Night.Ever.480p.WEB-DL.DD5.1.h.264-ETP.mkv
Attachment contains kernel update which you can flash using recovery mode.
Basically, it is an ordinary Samsung kernel without any USB code and with some minor hw-related tweaks.
modules.tar.bz2 contains all modules from snippet above plus HID and FTDI support.
It's huge because of ext4.ko. You probably won't need it.
dwc_otg.ko is USB driver itself. At the moment it has host-only functionality.
It means - it is a very bad idea to connect your phone to PC with this module loaded. Be warned.
Also, I'm using Y-cabe with 30k resistor between D+ and D-. This way MUIC thinks that phone is plugged into 1A charger.
At the same time, D+/D- is routed USB PHY. This hack is statically linked into the kernel.
So - don't try to charge your phone with this kernel with chargers with D+/D- shortened.
Oh, yeah. ID pin connection is irrelevant at the moment, so you can hack any micro-usb cable in the middle - no complex soldering required.
Disclaimer: You may brick your phone. Do it on your own risk. This post is developer-oriented.
If you do not fully understand what's written above - better don't do it at all.
Click to expand...
Click to collapse
A Biggg Thanks to you Master....
I am the one who tried for the same target before... But not yet successed..
I am very much curious to see the source or the patch for this.
I hope you will move your code to github or somethig...
Again .. You have Done a Great Job..
Sorry for reviving old post first of all guys, I'm a Galaxy Ace-I user (cooperve, not cooper) and I've found out that our phone in particular, just like the SGY has a BCM21552 (physically that's what the chip reads not 21553 lol), which also supports OTG as I've stated in this thread, I really think it'd be interesting if S5830i and SGY developers could join forces to make this go through
Whats the status of last development of OTG support?
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
So my tablet has been out of commission for a few months.. The battery drained fully one day and after charging it back up, it wouldn't boot (stuck on cyanogen boot screen) or go into recovery so I tried to re-flash the rom and then it got stuck in APX... so long story short, and a lot of experimentation later, I was able to reflash a working recovery and upgrade to the v8 bootloader, but I think my emmc is shot. --> When I try to flash a rom now it tells me that it can't mount certain partitions and what not, so! since some partitions apparently work, is it possible to flash a custom kernel or boot or something that looks at the sd card for the actual rom?
Read through another thread earlier today about figuring out if your emmc is hosed and ran dmesg | grep mmc in fastboot >>
Code:
<5>[ 0.000000] Kernel command line: tegraid=20.1.4.0.0 [email protected] androidbo
ot.serialno=[omitted] video=tegrafb console=none debug_uartport=hsport us
bcore.old_scheme_first=1 [email protected] [email protected]
brand=acer target_product=a500_ww_gen1 tegraboot=sdmmc gpt gpt_sector=15628287 a
ndroidboot.carrier=wifi-only bootloader_ver=0.03.14-MUL
<4>[ 3.323447] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.323892] Registered led device: mmc0::
<6>[ 3.324098] mmc0: SDHCI controller on tegra [sdhci-tegra.3] using ADMA
<4>[ 3.324377] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[ 3.324540] mmc1: no vmmc regulator found
<7>[ 3.324684] Registered led device: mmc1::
<6>[ 3.324846] mmc1: SDHCI controller on tegra [sdhci-tegra.2] using ADMA
<4>[ 3.325308] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[ 3.325401] mmc2: no vmmc regulator found
<7>[ 3.325613] Registered led device: mmc2::
<6>[ 3.325772] mmc2: SDHCI controller on tegra [sdhci-tegra.0] using ADMA
<6>[ 3.417646] mmc0: new high speed MMC card at address 0001
<6>[ 3.418071] mmcblk0: mmc0:0001 M8G2FA 7.45 GiB
<6>[ 3.420953] mmcblk0: p1 p2 p3 p4 p5 p6 p7
<6>[ 3.654402] mmc1: new high speed SDHC card at address aaaa
<6>[ 3.654751] mmcblk1: mmc1:aaaa SU32G 29.7 GiB
<6>[ 3.657460] mmcblk1: p1
<3>[ 4.159931] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 5.586322] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 5.963153] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 6.356707] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 145.099265] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 145.541972] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 145.968406] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem