Hi,
I've followed the instructions on how to build froyo on Ubuntu 10.04 32Bit,
I had to disable gdb in /buildroot/local/g8_arm/g8_arm.config
or shot make -i world
make menuconfig breaks everything
....so edit configs by hand.....
then it builds fine.....
thanks to his patch:
www android-hilfe de /android-os-entwicklung-customize/4801-kernel-module-kompilieren-erster-versuch.html
it runs (else unionfs complains about missing symbols..)
Code:
adb push unionfs.ko /data/local/tmp
adb push ntfs.ko /data/local/tmp
I've created a second 2GB ext3 partition on my sdhc class6
Code:
insmod /data/local/tmp/unionfs.ko
mount /dev/block/vold/179:18 /data/newroot
mount -t unionfs -o dirs="/data/newroot/rootfs=rw:/system=ro" unionfs /system
and now i've things like a writeble host file .....
it runs since yesterday here - and is fine.
jens
jensbln said:
Hi,
I've followed the instructions on how to build froyo on Ubuntu 10.04 32Bit,
I had to disable gdb in /buildroot/local/g8_arm/g8_arm.config
or shot make -i world
make menuconfig breaks everything
....so edit configs by hand.....
then it builds fine.....
thanks to his patch:
www android-hilfe de /android-os-entwicklung-customize/4801-kernel-module-kompilieren-erster-versuch.html
it runs (else unionfs complains about missing symbols..)
Code:
adb push unionfs.ko /data/local/tmp
adb push ntfs.ko /data/local/tmp
I've created a second 2GB ext3 partition on my sdhc class6
Code:
insmod /data/local/tmp/unionfs.ko
mount /dev/block/vold/179:18 /data/newroot
mount -t unionfs -o dirs="/data/newroot/rootfs=rw:/system=ro" unionfs /system
and now i've things like a writeble host file .....
it runs since yesterday here - and is fine.
jens
Click to expand...
Click to collapse
For morons like me what does that mean....root access??
Sorry if that is a dumb question
@mothy
so far, temporary root with writable /system directory
So just to be clear. Do you replace the kernel at all?
And do you have to mount the sd partition every time you boot up?
It's for the original Archos Kernel 2.6.29-omap1
Code:
# lsmod
ntfs 213028 0 - Live 0xbf276000
unionfs 74364 1 - Live 0xbf211000
this means you have to
temproot+"re"mount
the writable places, maybe soft-reboot (i use LCDDensity, it's soft-rebooting) and all your're changes are magicly there
instead of using sd, you can just create /data/newroot and let the things go there
Code:
# df -h
/dev/block/mmcblk0p4 299.4M 205.1M 78.9M 72% /data
i don't see any new rom's soon, unless we get a new bootloader, Archos uses mmcblk0 (an SD-Card device) and not mtd, so i think we can forget all that fastboot, flash_unlock mtd stuff.
this is very annoying, maybe i'm wrong,
but it looks like they don't want us to reflash the device :-(
unionfs usually need a own kernel, but the "ugly patches" make it run with the archos gen8 kernel
So i use temproot, gscript, LCDDensity after each reboot - and have all my settings back, apps like adsfree runs...
jens
forgive my lack of knowledge but you keep mentioning ntfs in the code fragments but you havent actually said that this is giving you ntfs support. does your kernal changes allow for reading ntfs volumes?
yes, i hope so, but i havn't tested it until now, minimum is that you can mount ntfs volumes by hand - but maybe it's automounting....
i want test a HD movie from sd, but mine doesnt fit in 4Gig (fat)
jens
i've connected same ntfs disk and:
Code:
usb 2-1:1.0: uevent
usb-storage 2-1:1.0: usb_probe_interface
usb-storage 2-1:1.0: usb_probe_interface - got id
devdb: devpath usb-musb_hdrc-1 not found
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
/mnt/flash/releases/G8A/v2.0.53-r80341/arcbuild/linux/drivers/usb/core/inode.c: creating file '002'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1 enable change, status 00000503
scsi 0:0:0:0: Direct-Access SAMSUNG HM160HI PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 38 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 38 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
usb-storage: device scan complete
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sda1.
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
usb 2-1: USB disconnect, address 2
usb 2-1: unregistering device
usb 2-1: usb_disable_device nuking all URBs
usb 2-1: unregistering interface 2-1:1.0
same things more need to be done, a trick could be having a small fat partition, so the system has it's sda1 as fas as expecting .....
jens
Hi guys, Total Noob here.
I've been reading through the forums over the last week and am still at a total loss. Despite trying numerous things, nothing I've tried has worked.. If anything, I'm afraid I've made things worse.
The back story: The NC we have is a newer one purchased *just* over a year ago, given to my 10yr old daughter as a bday gift. It's never been rooted or modded in anyway whatsoever. Two weeks ago while she was playing a game on it, it locked up, and wouldn't power off. We let it sit for a couple of days for the battery to drain. After that, the battery wouldn't charge, the NC would not boot and the cable indicator stayed orange. So I purchased, and replaced the battery. I let it sit overnight after replacing the battery, and we got a green light. On boot up, it would hang at the 'N Screen', and do nothing more.
I tried running the NC recovery, but that only resulted in an "INSTALL FAILED" error message, and that was the last sign of life to have been seen coming out of the NC.
At this point, it will only boot off the SD card, (currently using an 8gb with CWR 6.0.1.2), I no longer get even the 'N screen' anymore. I've tried leapinlars partitioning and formatting .zips, I've tried every stock image I could find, but the result is always the same. No partitions are mounted, and nothing but errors are generated.
I've tried connecting through ADB, but 'ADB DEVICES" only returns:
Code:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0000000000000000 recovery
...and nothing more.
Since this NC is for my daughters use, I'm really not interested in rooting or opening up android for her, I'd really like it to be nothing more than stock, but at this point I'd be grateful just to see some sign of life come out of this thing. All help would be greatly appreciated.
I hope I've provided enough info, anybody have a clue whats going on here?
Some other screen grabs from adb:
Code:
C:\android-sdk-windows\platform-tools>adb shell
~ # ls -l
ls -l
drwxr-xr-x 2 root root 0 Jan 9 05:40 boot
drwxr-xr-x 2 root root 0 Jan 9 05:40 cache
drwxr-xr-x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 9 05:40 datadata
-rw-r--r-- 1 root root 2553 Jan 1 1970 default.prop
drwxr-xr-x 10 root root 2440 Jan 9 05:40 dev
drwxr-xr-x 2 root root 0 Jan 9 05:40 emmc
drwxr-xr-x 2 root root 0 Jan 9 05:40 etc
-rwxr-x--- 1 root root 98756 Jan 1 1970 init
-rwxr-x--- 1 root root 1415 Jan 1 1970 init.rc
dr-xr-xr-x 64 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 1 1970 res
drwxrwxrwx 2 root root 0 Jan 9 05:40 rom
drwx------ 2 root root 0 Sep 21 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 9 05:40 sd-ext
drwxr-xr-x 2 root root 0 Jan 9 05:40 sdcard
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 9 05:40 tmp
-rw-r--r-- 1 root root 32 Jan 1 1970 ueventd.encore.rc
-rw-r--r-- 1 root root 272 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 3825 Jan 1 1970 ueventd.rc
~ #
and
Code:
fdisk -l
returns nothing except for the command 'fdisk -l' being echoed back to the screen.
Even though I can boot with CWM; when booting CWM, it displays the following error messages
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
When trying to install "NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip", I get:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repartition /boot, /system, /data (1GB), /cache and /media
Repartitioning internal memory - be patient this may take a while
Done. YOU MUST REBOOT TO RELOAD THE PARTITION TABLE
Install from sdcard complete.
Then, rebooting and installing "NookColor-emmc-format-partitions-5-6-7-8.zip" generates the following output instantly, with absolutely no delay when the formatting should be occuring:
Code:
-- Installing: /sdcard/NookColor-emmc-format-partitions-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Reformatting /system, /data, /cache, and /media
Reformatting /system (0p5)
This may take some time, please be patient
Reformatting /data (0p6)
This may take some time, please be patient
Reformatting /cache (0p7)
This may take some time, please be patient
Reformatting /media (0p8)
This may take some time, please be patient
Done.
Install from sdcard complete.
Trying "NookColor-emmc-repair-partition-2.zip", ends with:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partition-2.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repair /rom partition (P2)
Checking for /factory - if not found will return error message and repair will be aborted.
assert failed: mount("ext2", "EMMC", "/dev/block/mmcblk0p3", "/factory") == "/factory"
E:Error in /sdcard/NookColor-emmc-repair-partition-2.zip
(Status 7)
Installation aborted.
and then after not making progress with those; trying "NookColor-emmc-stockrecovery-CWM6012asAlt.zip" returns:
Code:
-- Installing: /sdcard/NookColor-emmc-stockrecovery-CWM6012asAlt.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Installing Stock Recovery to EMMC with CWM 6.0.1.2 as Alternate
-----------------------------------------
Done
Install from sdcard complete.
, ...with still no recovery process being possible.
MaGoober said:
Some other screen grabs from adb:
Code:
C:\android-sdk-windows\platform-tools>adb shell
~ # ls -l
ls -l
drwxr-xr-x 2 root root 0 Jan 9 05:40 boot
drwxr-xr-x 2 root root 0 Jan 9 05:40 cache
drwxr-xr-x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 9 05:40 datadata
-rw-r--r-- 1 root root 2553 Jan 1 1970 default.prop
drwxr-xr-x 10 root root 2440 Jan 9 05:40 dev
drwxr-xr-x 2 root root 0 Jan 9 05:40 emmc
drwxr-xr-x 2 root root 0 Jan 9 05:40 etc
-rwxr-x--- 1 root root 98756 Jan 1 1970 init
-rwxr-x--- 1 root root 1415 Jan 1 1970 init.rc
dr-xr-xr-x 64 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 1 1970 res
drwxrwxrwx 2 root root 0 Jan 9 05:40 rom
drwx------ 2 root root 0 Sep 21 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 9 05:40 sd-ext
drwxr-xr-x 2 root root 0 Jan 9 05:40 sdcard
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 9 05:40 tmp
-rw-r--r-- 1 root root 32 Jan 1 1970 ueventd.encore.rc
-rw-r--r-- 1 root root 272 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 3825 Jan 1 1970 ueventd.rc
~ #
and
Code:
fdisk -l
returns nothing except for the command 'fdisk -l' being echoed back to the screen.
Even though I can boot with CWM; when booting CWM, it displays the following error messages
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
When trying to install "NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip", I get:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repartition /boot, /system, /data (1GB), /cache and /media
Repartitioning internal memory - be patient this may take a while
Done. YOU MUST REBOOT TO RELOAD THE PARTITION TABLE
Install from sdcard complete.
Then, rebooting and installing "NookColor-emmc-format-partitions-5-6-7-8.zip" generates the following output instantly, with absolutely no delay when the formatting should be occuring:
Code:
-- Installing: /sdcard/NookColor-emmc-format-partitions-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Reformatting /system, /data, /cache, and /media
Reformatting /system (0p5)
This may take some time, please be patient
Reformatting /data (0p6)
This may take some time, please be patient
Reformatting /cache (0p7)
This may take some time, please be patient
Reformatting /media (0p8)
This may take some time, please be patient
Done.
Install from sdcard complete.
Trying "NookColor-emmc-repair-partition-2.zip", ends with:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partition-2.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repair /rom partition (P2)
Checking for /factory - if not found will return error message and repair will be aborted.
assert failed: mount("ext2", "EMMC", "/dev/block/mmcblk0p3", "/factory") == "/factory"
E:Error in /sdcard/NookColor-emmc-repair-partition-2.zip
(Status 7)
Installation aborted.
and then after not making progress with those; trying "NookColor-emmc-stockrecovery-CWM6012asAlt.zip" returns:
Code:
-- Installing: /sdcard/NookColor-emmc-stockrecovery-CWM6012asAlt.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Installing Stock Recovery to EMMC with CWM 6.0.1.2 as Alternate
-----------------------------------------
Done
Install from sdcard complete.
, ...with still no recovery process being possible.
Click to expand...
Click to collapse
You need to type
fdisk -l /dev/block/mmcblk0
in ADB. That will show you the partition structure of emmc. I suspect your cylinder/head/sector count is messed up. That is why my zips appear to work, but do not.
Report here the output of the command.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
You need to type
fdisk -l /dev/block/mmcblk0
in ADB. That will show you the partition structure of emmc. I suspect your cylinder/head/sector count is messed up. That is why my zips appear to work, but do not.
Report here the output of the command.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Thanks for the suggestion leapinlar, I assumed fdisk -l would show all disk info by default if a specific disk wasnt specified. For some reason when I plugged the NC into the USB port today, My Win7 box did not recognize it or want to reload the drivers the same way it did last night, and I was unable to connect to the NC through ADB.
I will try to figure out that later on, or try to use ADB through my Fedora box when I get a chance. In the meantime, I once again tried your repair-partions.zip and copied CWM's error log, which is pasted below. Hopefully this gives some insight:
Starting recovery on Sun Jan 9 18:13:58 2000
framebuffer: fd 4 (1024 x 600)
CWM-based Recovery v6.0.1.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot vfat /dev/block/mmcblk0p1 (null) 0
2 /system ext4 /dev/block/mmcblk0p5 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /emmc vfat /dev/block/mmcblk0p8 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /sd-ext ext4 /dev/block/mmcblk1p8 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.larry.20121021.181637
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sun Oct 21 18:17:05 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=larry
ro.build.host=larry-HP-Pavilion-dm4-Ubuntu
ro.build.tags=test-keys
ro.product.model=NookColor
ro.product.brand=bn
ro.product.name=encore
ro.product.device=encore
ro.product.board=encore
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=bn
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
ro.build.product=encore
ro.build.description=encore-user 4.0.4 IMM76D 228551 release-keys
ro.build.fingerprint=bn/bn_encore/encore:4.0.4/IMM76D/228551:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=encore
wifi.interface=tiwlan0
wifi.supplicant_scan_interval=30
ro.additionalmounts=/mnt/emmc;/mnt/usbdisk
ro.vold.switchablepair=/mnt/sdcard,/mnt/emmc
ro.pm.awake_on_usb=1
ro.cwm.forbid_format=/boot
ro.sf.hwrotation=270
ro.emmc=1
com.ti.omap_compat=true
ro.magic.optimization=ZOMG
ro.com.android.dateformat=MM-dd-yyyy
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
alsa.mixer.playback.master=default
alsa.mixer.capture.master=Analog
ro.opengles.version=131072
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=(link removed)
ro.url.legal.android_privacy=(link removed)
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=9-20121022-UNOFFICIAL-encore
ro.modversion=9-20121022-UNOFFICIAL-encore
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=encore
ro.revision=5
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
W:Can't unlink /cache/recovery/command
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
-- Installing: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
I:Update location: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
Opening update package...
Installing update...
Repartition /boot, /system, /data (1GB), /cache and /media
Repartitioning internal memory - be patient this may take a whileabout to run program [/tmp/repartition.sh] with 1 args
Archive: /tmp/boot.zip
inflating: boot.img
144522+0 records in
144522+0 records out
73995264 bytes (70.6MB) copied, 1.259857 seconds, 56.0MB/s
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
The number of cylinders for this disk is set to 236032.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): No partition is defined yet!
Command (m for help): 4: unknown command
Command Action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Partition number (1-4): script result was [Done. You MUST REBOOT TO RELOAD THE PARTITION TABLE]
Done. You MUST REBOOT TO RELOAD THE PARTITION TABLE
Install from sdcard complete.
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
W:Can't unlink /cache/recovery/command
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I:Can't partition unsafe device: /dev/block/mmcblk0p8
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
Click to expand...
Click to collapse
leapinlar said:
You need to type
fdisk -l /dev/block/mmcblk0
....
Click to expand...
Click to collapse
Okay, got adb working again. Here's the result:
Code:
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ #
Well now, isnt that special?
So that got me curious and I took a look/see in the /dev/block folder:
Code:
/dev/block # ls
ls
loop0 loop4 mmcblk0 ram1 ram13 ram3 ram7
loop1 loop5 mmcblk0p1 ram10 ram14 ram4 ram8
loop2 loop6 platform ram11 ram15 ram5 ram9
loop3 loop7 ram0 ram12 ram2 ram6
/dev/block # ls -l
ls -l
brw------- 1 root root 7, 0 Jan 9 18:13 loop0
brw------- 1 root root 7, 1 Jan 9 18:13 loop1
brw------- 1 root root 7, 2 Jan 9 18:13 loop2
brw------- 1 root root 7, 3 Jan 9 18:13 loop3
brw------- 1 root root 7, 4 Jan 9 18:13 loop4
brw------- 1 root root 7, 5 Jan 9 18:13 loop5
brw------- 1 root root 7, 6 Jan 9 18:13 loop6
brw------- 1 root root 7, 7 Jan 9 18:13 loop7
brw------- 1 root root 179, 0 Jan 9 18:13 mmcblk0
-rw-rw-rw- 1 root root 73995264 Jan 9 18:14 mmcblk0p1
drwxr-xr-x 4 root root 80 Jan 9 18:13 platform
brw------- 1 root root 1, 0 Jan 9 18:13 ram0
brw------- 1 root root 1, 1 Jan 9 18:13 ram1
brw------- 1 root root 1, 10 Jan 9 18:13 ram10
brw------- 1 root root 1, 11 Jan 9 18:13 ram11
brw------- 1 root root 1, 12 Jan 9 18:13 ram12
brw------- 1 root root 1, 13 Jan 9 18:13 ram13
brw------- 1 root root 1, 14 Jan 9 18:13 ram14
brw------- 1 root root 1, 15 Jan 9 18:13 ram15
brw------- 1 root root 1, 2 Jan 9 18:13 ram2
brw------- 1 root root 1, 3 Jan 9 18:13 ram3
brw------- 1 root root 1, 4 Jan 9 18:13 ram4
brw------- 1 root root 1, 5 Jan 9 18:13 ram5
brw------- 1 root root 1, 6 Jan 9 18:13 ram6
brw------- 1 root root 1, 7 Jan 9 18:13 ram7
brw------- 1 root root 1, 8 Jan 9 18:13 ram8
brw------- 1 root root 1, 9 Jan 9 18:13 ram9
/dev/block # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
/dev/block # fdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1
Disk /dev/block/mmcblk0p1: 73 MB, 73995264 bytes
255 heads, 63 sectors/track, 8 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block #
Strange, today when I opened adb, it appears that some of the entries in /dev/block have changed. mmcblk0p1 is gone and replaced with mmcblk1p1.
Yesterday I saw this
Code:
/dev/block # ls
ls
loop0 loop4 mmcblk0 ram1 ram13 ram3 ram7
loop1 loop5 mmcblk0p1 ram10 ram14 ram4 ram8
loop2 loop6 platform ram11 ram15 ram5 ram9
loop3 loop7 ram0 ram12 ram2 ram6
This is what I see today:
Code:
/dev/block # ls
ls
loop0 loop4 mmcblk0 ram0 ram12 ram2 ram6
loop1 loop5 mmcblk1 ram1 ram13 ram3 ram7
loop2 loop6 mmcblk1p1 ram10 ram14 ram4 ram8
loop3 loop7 platform ram11 ram15 ram5 ram9
/dev/block #
If my understanding is correct (and it's usually not) the "P1" indicates that this is "partition one" on the "mmcblock one" device. (or 'disk'). I'm further assuming that of the two devices shown (mmcblk0, and mmcblk1) one of them is my 8gb microsd card, and the other is the NC's internal 8gb memory. Which makes me wonder why yesterday's "ls" did not show both devices. Also makes me wonder what the 'p1' partition is, which disk it's really on, and why it appears to have moved.
I took a look at the geometries of the disks and the partition using fdisk again, I dont know what I should be looking for here, and dont know whats relevant and what isn't. I can see I have two disks of slightly different sizes, and a mystery partition of some sort that doesnt seem like it should fit on either of the two disks.
Code:
/dev/block # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
/dev/block # fdisk -l /dev/block/mmcblk1
fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 7948 MB, 7948206080 bytes
255 heads, 63 sectors/track, 966 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 * 1 38 305203+ b Win95 FAT32
/dev/block # fdisk -l /dev/block/mmcblk1p1
fdisk -l /dev/block/mmcblk1p1
Disk /dev/block/mmcblk1p1: 312 MB, 312528384 bytes
4 heads, 16 sectors/track, 9537 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block #
Ok. I feel real stupid, obviously the mmcblk1 device is the sdcard and the p1 partition on it is the fat32 partition on it. Still leaves me wondering what happened to the geometry on the internal memory. CHS looks way off. shouldn't it be more like that of my sdcard?
*** Second Update***
I'm pulling my hair out here. I tried to correct the CHS values...no love there, even after rebooting it remains unchanged.
Code:
~ # fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
Command (m for help): w
w
The partition table has been altered.
Calling ioctl() to re-read partition table
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
After trying to fix the geometry several times, and failing. I said Eff this, and tried living with the incorrect values and creating the partitions anyway. I keep getting fdisk: short write, when creating partition 8.
Anway....from start to finish here - notice the # of cylinders as I progress.
Code:
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ # fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
p
p
Partition number (1-4):
Value is out of range
Partition number (1-4): 1
1
First cylinder (1-940, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-940, default 940): 9
9
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
p
p
Partition number (1-4): 2
2
First cylinder (10-940, default 10):
Using default value 10
Last cylinder or +size or +sizeM or +sizeK (10-940, default 940): 18
18
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
p
p
Partition number (1-4): 3
3
First cylinder (19-940, default 19):
Using default value 19
Last cylinder or +size or +sizeM or +sizeK (19-940, default 940): 56
56
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
e
e
Selected partition 4
First cylinder (57-940, default 57):
Using default value 57
Last cylinder or +size or +sizeM or +sizeK (57-940, default 940):
Using default value 940
Command (m for help): n
n
First cylinder (57-940, default 57):
Using default value 57
Last cylinder or +size or +sizeM or +sizeK (57-940, default 940): 114
114
Command (m for help): n
n
First cylinder (115-940, default 115):
Using default value 115
Last cylinder or +size or +sizeM or +sizeK (115-940, default 940): 236
236
Command (m for help): n
n
First cylinder (237-940, default 237):
Using default value 237
Last cylinder or +size or +sizeM or +sizeK (237-940, default 940): 281
281
Command (m for help):
at this point, I'll stop and review the changes before I commit (w) them to disk...
Code:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
255 heads, 63 sectors/track, 940 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 9 72261 83 Linux
/dev/block/mmcblk0p2 10 18 72292+ 83 Linux
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 940 7100730 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
Okay, Now the number of cylinders originally being reported was 236032, I specified 965 using the -C switch, and somehow ended up with a value of 940 - still leaving the geometry out of whack. Before I go any further I will commit and (w) the pending partition table here ...
Code:
Command (m for help): w
w
The partition table has been altered.
Calling ioctl() to re-read partition table
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
255 heads, 63 sectors/track, 940 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 9 72261 83 Linux
/dev/block/mmcblk0p2 10 18 72292+ 83 Linux
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 940 7100730 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
~ #
So it appears my partition table has been written successfully. I just need to create partition 8. ... before I do that, I will reboot the NC to make sure the partition table is persistent...
Code:
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
...and that's a big fat fail.
At this point, It looks like my only option to ever use this NC again, is to have a stand alone bootable sd card. If anybody has a suggestion, please throw it my way.
Do either of these things indicate anything of importance that could potentially be of help?
1) 'adb devices' lists the Device ID as "RECOVERY"
2) The internal memory seems to be in a 'read only' mode of some sort.
The last time this NC did power up under its own free will, was when the stock recovery was being attempted - and crashed.
MaGoober said:
Do either of these things indicate anything of importance that could potentially be of help?
1) 'adb devices' lists the Device ID as "RECOVERY"
2) The internal memory seems to be in a 'read only' mode of some sort.
The last time this NC did power up under its own free will, was when the stock recovery was being attempted - and crashed.
Click to expand...
Click to collapse
Your CHS (cylinder, head, sector) settings are wrong. It should be 255 heads, 63 sectors/track and 965 cylinders. You need to run fdisk CHS to fix it. You need to type the following command in ADB shell.
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Then do an
fdisk -l /dev/block/mmcblk0
to see what you get.
If the CHS is right you can do my 145678 repair and format. I don't know if the p2 repair will work though. If not, I may be able to help.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Your CHS (cylinder, head, sector) settings are wrong. It should be 255 heads, 63 sectors/track and 965 cylinders. You need to run fdisk CHS to fix it. You need to type the following command in ADB shell.
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Then do an
fdisk -l /dev/block/mmcblk0
to see what you get.
If the CHS is right you can do my 145678 repair and format. I don't know if the p2 repair will work though. If not, I may be able to help.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Here's the result - as before, it just doesn't 'stick'.
Code:
C:\android-sdk-windows\platform-tools>adb shell
~ # fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
Command (m for help): w
w
The partition table has been altered.
Calling ioctl() to re-read partition table
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ #
Thanks for your help, I really do appreciate it.
I may be crazy here, but what are the odds my NC does not have the same emmc chip? This thing sure acts like its fallen victim to the 'brick bug'. I cant seem to write anything at all, Tried creating new partitions with parted, no go. Even tried overwriting the mbr with dd if=/dev/zero of=/dev/block/mmcblk0 bs=512 count=1 and it didnt even touch it.
MaGoober said:
I may be crazy here, but what are the odds my NC does not have the same emmc chip? This thing sure acts like its fallen victim to the 'brick bug'. I cant seem to write anything at all, Tried creating new partitions with parted, no go. Even tried overwriting the mbr with dd if=/dev/zero of=/dev/block/mmcblk0 bs=512 count=1 and it didnt even touch it.
Click to expand...
Click to collapse
I have had SD chips that became ready only by some mysterious means. It is possible that your emmc has done the same. In fact, one other user said that happened to his emmc.
Sent from my Galaxy Tab 2 using XDA Premium
Alrighty then, I confirmed this much at least:
with
Code:
dmesg | grep mmc0
The emmc chip in my NC is the Samsung M8G2FA, which is prone to the "Brick Bug", and from the little I've read on it so far, the bug is brought on merely by wiping the cache partitions clean. I got me some more reading up to do...
Today, I called BN tech support for the second time in a week, after visiting the local store to see if anybody there could offer up assistance. Long story short, because our NC was just out of warranty (by three weeks) they did offer to exchange it with a 'certified pre-owned' . When that comes in, the very first thing I'm going to do is see what memory chip it has in it, Evidently just trying to do a 'hard reset' and run the stock recovery bricks the M8G2FA EMMC. However, I still don't know what caused our NC to lock up in the first place. I guess at this point, that's moot.
leapinlar, I've read through many of your posts, although I couldn't fix my problems, you were instrumental in keeping me sane. ... well, depending on how loosely you define sane,