[Q] custom mtd on chacha (follow up to same thread in Dev section) - HTC ChaCha

Hi,
I'm not allowed to reply on "Development" thread, so I open this new one.
But really this should be a reply on qtotter thread:
http://forum.xda-developers.com/showthread.php?t=1568787
I don't want to make it pm as well because this may be of interest to others like me that try and unfortunately get no result at this...
So here is what I got try at qtotter procedure and advices.
My ChaCha original memory mapping is:
Code:
# df /system
df /system
/system: 266240K total, 266116K used, 124K available (block size 4096)
# df /cache
df /cache
/cache: 35840K total, 2324K used, 33516K available (block size 4096)
# df /data
df /data
/data: 153600K total, 131484K used, 22116K available (block size 4096)
original mapping is:
--> 260 / 35 / 150
My custom recovery is CWM v4.0.1.0 (original PH06img.zip thread)
I take an empty SD Card and partition it (CWM recovery) into: "sd-ext = 512, swap = 0, rest of it is fat32"
I copy on it (fat32 part):
FR-Custom-MTD-v1.5.6-boot.zip
FR-Custom-MTD-v1.5.6-recovery.zip
mtdpartmap.txt
mtdpartmap.txt is (UNIX EOL):
Code:
mtd 265 10
I reboot to recovery.
mounts and storage > format /cache
mounts and storage > format /data
mounts and storage > format /system
install zip from sdcard > FR-Custom-MTD-v1.5.6-recovery.zip
Here is what I get in the '/tmp/recovery.log' file:
Code:
-- Installing: /sdcard/FR-Custom-MTD-v1.5.6-recovery.zip
mtd: successfully wrote block at c3a6c00000000
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/FR-Custom-MTD-v1.5.6-recovery.zip
Opening update package...
Installing update...
CustomMTD Patcher v1.5.6about to run program [/tmp/patchbootimg.sh] with 2 args
Recovery Mode
Extracting Patch Tools...
BOARD_KERNEL_CMDLINE no_console_suspend=1 console=null
BOARD_KERNEL_BASE 12c00000
mtd: erase failure at 0x00000000
mtd: erase failure at 0x00040000
mtd: erase failure at 0x00080000
mtd: erase failure at 0x000c0000
mtd: erase failure at 0x00100000
mtd: erase failure at 0x00140000
mtd: erase failure at 0x00180000
mtd: erase failure at 0x001c0000
mtd: erase failure at 0x00200000
mtd: erase failure at 0x00240000
mtd: erase failure at 0x00280000
mtd: erase failure at 0x002c0000
mtd: erase failure at 0x00300000
mtd: erase failure at 0x00340000
mtd: erase failure at 0x00380000
mtd: erase failure at 0x003c0000
mtd: erase failure at 0x00400000
mtd: erase failure at 0x00440000
mtd: erase failure at 0x00480000
mtd: erase failure at 0x004c0000
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
mtd: erase failure at 0x00040000 (I/O error)
mtd: erase failure at 0x00040000 (I/O error)
mtd: skipping write block at 0x00040000
mtd: erase failure at 0x00080000 (I/O error)
mtd: erase failure at 0x00080000 (I/O error)
mtd: skipping write block at 0x00080000
mtd: erase failure at 0x000c0000 (I/O error)
mtd: erase failure at 0x000c0000 (I/O error)
mtd: skipping write block at 0x000c0000
mtd: erase failure at 0x00100000 (I/O error)
mtd: erase failure at 0x00100000 (I/O error)
mtd: skipping write block at 0x00100000
mtd: erase failure at 0x00140000 (I/O error)
mtd: erase failure at 0x00140000 (I/O error)
mtd: skipping write block at 0x00140000
mtd: erase failure at 0x00180000 (I/O error)
mtd: erase failure at 0x00180000 (I/O error)
mtd: skipping write block at 0x00180000
mtd: erase failure at 0x001c0000 (I/O error)
mtd: erase failure at 0x001c0000 (I/O error)
mtd: skipping write block at 0x001c0000
mtd: erase failure at 0x00200000 (I/O error)
mtd: erase failure at 0x00200000 (I/O error)
mtd: skipping write block at 0x00200000
mtd: erase failure at 0x00240000 (I/O error)
mtd: erase failure at 0x00240000 (I/O error)
mtd: skipping write block at 0x00240000
mtd: erase failure at 0x00280000 (I/O error)
mtd: erase failure at 0x00280000 (I/O error)
mtd: skipping write block at 0x00280000
mtd: erase failure at 0x002c0000 (I/O error)
mtd: erase failure at 0x002c0000 (I/O error)
mtd: skipping write block at 0x002c0000
mtd: erase failure at 0x00300000 (I/O error)
mtd: erase failure at 0x00300000 (I/O error)
mtd: skipping write block at 0x00300000
mtd: erase failure at 0x00340000 (I/O error)
mtd: erase failure at 0x00340000 (I/O error)
mtd: skipping write block at 0x00340000
mtd: erase failure at 0x00380000 (I/O error)
mtd: erase failure at 0x00380000 (I/O error)
mtd: skipping write block at 0x00380000
mtd: erase failure at 0x003c0000 (I/O error)
mtd: erase failure at 0x003c0000 (I/O error)
mtd: skipping write block at 0x003c0000
mtd: erase failure at 0x00400000 (I/O error)
mtd: erase failure at 0x00400000 (I/O error)
mtd: skipping write block at 0x00400000
mtd: erase failure at 0x00440000 (I/O error)
mtd: erase failure at 0x00440000 (I/O error)
mtd: skipping write block at 0x00440000
mtd: erase failure at 0x00480000 (I/O error)
mtd: erase failure at 0x00480000 (I/O error)
mtd: skipping write block at 0x00480000
mtd: erase failure at 0x004c0000 (I/O error)
mtd: erase failure at 0x004c0000 (I/O error)
mtd: skipping write block at 0x004c0000
failed with error: -1
flashing recovery from /tmp/recovery.img
error writing recoveryrun_program: child exited with status 255
script result was [to take effect]
minzip: Extracted file "/tmp/mkbootimg"
minzip: Extracted file "/tmp/patchbootimg.sh"
minzip: Extracted file "/tmp/unpackbootimg"
Custom MTD written
Please wipe system,cache & data
& reboot to recovery for changes
to take effect
Install from sdcard complete.
mtd: successfully wrote block at c3a6c00000000
I:Set boot command ""
mtd: successfully wrote block at c3a6c00000000
I:Set boot command ""
Then I format again /cache /data /system partition
and I reboot again to recovery
and there the 'df' commands give me:
Code:
~ # df /system
df /system
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock3 266240 2820 263420 1% /system
~ # df /cache
df /cache
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock4 35840 2328 33512 6% /cache
~ # df /data
df /data
Filesystem 1K-blocks Used Available Use% Mounted on
df: /data: can't find mount point
so this means that the '/system' and '/cache' partitions have not been resized and I still have the same 260 / 35 / 150 mapping...
I tried as well with a newer version of the CustomMTD tools (AutoPatch-v1.5.9-Beta2-CustomMTD_S.zip).
But this time the patch tool gives a more explicit error:
Code:
-- Installing: /sdcard/AutoPatch-v1.5.9-Beta2-CustomMTD_S.zip
mtd: successfully wrote block at c3a6c00000000
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/AutoPatch-v1.5.9-Beta2-CustomMTD_S.zip
Opening update package...
Installing update...
CustomMTD Patcher v1.5.9-Beta2about to run program [/tmp/patchbootimg.sh] with 2 args
Mode AutoPatch
Extracting Patch Tools...
about to run program [busybox test -f /sdcard/mtdpartmap.txt] with 1 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
script result was []
minzip: Extracted file "/tmp/mkbootimg"
minzip: Extracted file "/tmp/patchbootimg.sh"
minzip: Extracted file "/tmp/unpackbootimg"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
############ ERROR #############
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
none consecutive partitions
detected, can not proceed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Install from sdcard complete.
mtd: successfully wrote block at c3a6c00000000
I:Set boot command ""
I'm therefore a bit lost here.
How did you succeed in resizing?
Could you please detail step by step what you did because I followed quite carefully your instructions and HTC Desire steps, but this doesn't work...
Thanks in advance.
spoutnik

Hi,
No answer yet on this subject...
So I investigated a bit more and here are the steps and results.
(I can tell you already that I did not succeed yet, but I'm sure I'm not far)
*** Which CustomMTD tools version I used ***
As seen in my previous post, with CustomMTD tools v1.5.9 (AutoPatch-v1.5.9-Beta2-CustomMTD_S.zip), the 'patchbootimg.sh' does some smart checking on system / cache / data being concecutive, which is not the case on ChaCha (I'll explain later).
For this reason, I reverted to CustomMTD tools v1.5.8 (recovery-v1.5.8-Beta-CustomMTD_S.zip).
This version improves the 'patchbootimg.sh' code over the 1.5.6, but remains more easily customizable.
*** Which re-partitionning is easier / better for ChaCha ***
The original partition table on ChaCha (official ChaCha_HTC_Europe_1.54.xxx ROM) is:
Code:
0x000002FC0000-0x0000034C0000 : "recovery" --> size = 0x500000 = 5242880 Bytes = 5120 KB = 5 MB
0x0000034C0000-0x000003800000 : "boot" --> size = 0x340000 = 3407872 Bytes = 3328 KB = 3,25 MB
0x000003800000-0x000013C00000 : "system" --> size = 0x10400000= 272629760 Bytes = 266240 KB = 260 MB
0x000013C00000-0x000015F00000 : "cache" --> size = 0x2300000 = 36700160 Bytes = 35840 KB = 35 MB
0x000015F00000-0x000016900000 : "devlog" --> size = 0xA00000 = 10485760 Bytes = 10240 KB = 10 MB
0x000016900000-0x00001FF00000 : "userdata" --> size = 0x9600000 = 157286400 Bytes = 153600 KB = 150 MB
0x00001FF00000-0x000020000000 : "misc" --> size = 0x100000 = 1048576 Bytes = 1024 KB = 1 MB
As you can see, we have "system" / "cache" / "userdata" = 260 / 35 / 150
But they are not consecutive since the "devlog" partition is inbetween.
This means that it is not possible to repartition in a classic way the "system""cache""userdata" block (... I don't see how the original v1.5.6 and v1.5.8 'patchbootimg.sh' code could work for qtotter in this case ...).
It is as well difficult to switch a partition ("userdata" for instance) to put it "system" instead because 150 MB is too small (the official ROM system takes around 240 MB !!)
After searching, I've seen that firerat has helped on a similar case (LG Optimus S) where the partition table is not consecutive as well. see code modif here: Firerat / CustomMTD / quickly added support for LG Optimus S ( thunderc ) (h_t_t_p_s://github.com/Firerat/CustomMTD/commit/f3ec0fdcd6823e674cd3bc81267db6a482eaa39a)
So my idea about this was to modify the v1.5.8 'patchbootimg.sh' code in a similar way in order to obtain the following partition table:
- keep the "userdata" partition intact
- repartition the "system""cache" block to give more space to the "system" partition
- the 'mtdpartmap.txt' file allowing to specify the "system" partition size
The modified partition table would then be:
Code:
0x000002FC0000-0x0000034C0000 : "recovery" --> size = 0x500000 = 5242880 Bytes = 5120 KB = 5 MB
0x0000034C0000-0x000003800000 : "boot" --> size = 0x340000 = 3407872 Bytes = 3328 KB = 3,25 MB
0x000003800000-0x0000[B]XXX[/B]00000 : "system" --> size = 295 MB - [I]<cache partition size>[/I] MB
0x0000[B]XXX[/B]00000-0x000015F00000 : "cache" --> size = [I]<cache partition size>[/I] MB
0x000015F00000-0x000016900000 : "devlog" --> size = 0xA00000 = 10485760 Bytes = 10240 KB = 10 MB
0x000016900000-0x00001FF00000 : "userdata" --> size = 0x9600000 = 157286400 Bytes = 153600 KB = 150 MB
0x00001FF00000-0x000020000000 : "misc" --> size = 0x100000 = 1048576 Bytes = 1024 KB = 1 MB
*** Modified 'patchbootimg.sh' code and resulting KCMDline ***
I modified then the 'patchbootimg.sh' source code to customize it specifically to the ChaCha and to the modified partition table to get (as explained before).
And I tested this new code on my ChaCha with the 'test-v1.5.8-Beta-CustomMTD_S.chacha.zip' package, built with my modified 'patchbootimg.chacha.sh'.
With 'mtdpartmap.txt' = mtd 290 5
(the 2nd parameter is not used anyway)
I should get:
Code:
[idem] 0x000002FC0000-0x0000034C0000 : "recovery" --> size = 0x500000 = 5242880 Bytes = 5120 KB = 5 MB
[idem] 0x0000034C0000-0x000003800000 : "boot" --> size = 0x340000 = 3407872 Bytes = 3328 KB = 3,25 MB
[changed] 0x000003800000-0x000015A00000 : "system" --> size = 0x12200000= 304087040 Bytes = 296960 KB = 290 MB
[changed] 0x000015A00000-0x000015F00000 : "cache" --> size = 0x500000 = 5242880 Bytes = 5120 KB = 5 MB
[idem] 0x000015F00000-0x000016900000 : "devlog" --> size = 0xA00000 = 10485760 Bytes = 10240 KB = 10 MB
[idem] 0x000016900000-0x00001FF00000 : "userdata" --> size = 0x9600000 = 157286400 Bytes = 153600 KB = 150 MB
[idem] 0x00001FF00000-0x000020000000 : "misc" --> size = 0x100000 = 1048576 Bytes = 1024 KB = 1 MB
The test run returns the following command line:
Code:
+ KCMDline=mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](userdata),[email protected](devlog),[email protected](system),[email protected](cache)
This is GOOD
So now I can test the 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package to see if my partition table gets properly modified.
At this point, I do think that my specific 'recovery-v1.5.8-Beta-CustomMTD_S.chacha' package is good to be run on the ChaCha.
So let's re-try.
*** Impossible to flash the "recovery" partition while in recovery mode?? ***
In my first post, I was getting lots of errors when updating my ChaCha in recovery mode with the "recovery-..." package:
Code:
[...]
mtd: erase failure at 0x004c0000 (I/O error)
mtd: skipping write block at 0x004c0000
failed with error: -1
flashing recovery from /tmp/recovery.img
error writing recovery
In fact I did some tests, and it looks like it is not possible to do such recovery flashing operations while in recovery mode.
These operations must be done in fastboot mode.
So what I'll do is:
- reboot in recovery mode and install the 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package
--> this will fail in the end, but it will extract all the necessary files to do things by hand
- reboot in fastboot mode and do operations by hand
Check the next post for this part.
spoutnik

[Q] custom mtd on chacha [please a dev (firerat) look at this]
Hi,
So I built a ChaCha specific 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package and now I'll run it for real.
As I said, what I'll do is:
- reboot in recovery mode and install the 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package
--> this will fail in the end, but it will extract all the necessary files to do things by hand
- reboot in fastboot mode and do operations by hand
*** [recovery mode] Installing the 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package ***
The recovery I use is CWM v4.0.1.0 (original PH06img.zip thread).
install zip from sdcard > 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip'
I get errors, as expected.
Then I reboot to fastboot mode.
*** [fastboot mode] Manual installation of 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package ***
First, here is the content of the '/tmp/recovery.log' file that shows the expected errors (the same than in my first post):
Code:
~ # cd /tmp
cd /tmp
/tmp # ls
ls
recovery.log
/tmp # cat recovery.log
cat recovery.log
Starting recovery on Tue Jul 3 12:02:44 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 320)
ClockworkMod Recovery v4.0.1.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext ext4 /dev/block/mmcblk0p2 (null)
I:Completed outputting fstab.
I:Processing arguments.
Fixing execute permissions for /cache
mtd: successfully wrote block at c3a6c00000000
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_chacha-eng 2.3.4 GINGERBREAD eng.mike.20110714.204851 test-keys
ro.build.version.incremental=eng.mike.20110714.204851
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Thu Jul 14 20:49:56 CEST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=mike
ro.build.host=AndroidCompiler
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_chacha
ro.product.device=chacha
ro.product.board=chacha
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=chacha
ro.build.description=full_chacha-eng 2.3.4 GINGERBREAD eng.mike.20110714.204851 test-keys
ro.build.fingerprint=Android/full_chacha/chacha:2.3.4/GINGERBREAD/eng.mike.20110714.204851:eng/test-
keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT15XV403307
ro.bootmode=recovery
ro.baseband=7.51.35.19
ro.carrier=HTC-FRA
ro.bootloader=1.10.0000
ro.hardware=chacha
ro.revision=128
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mtd: successfully wrote block at c3a6c00000000
I:Set boot command ""
mtd: successfully wrote block at c3a6c00000000
I:Set boot command ""
-- Installing: /sdcard/recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip
mtd: successfully wrote block at c3a6c00000000
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip
Opening update package...
Installing update...
CustomMTD Patcher v1.5.8-Betaabout to run program [/tmp/patchbootimg.sh] with 2 args
2344
16
Recovery Mode
Extracting Patch Tools...
BOARD_KERNEL_CMDLINE no_console_suspend=1 console=null
BOARD_KERNEL_BASE 12c00000
mtd: erase failure at 0x00000000
mtd: erase failure at 0x00040000
mtd: erase failure at 0x00080000
mtd: erase failure at 0x000c0000
mtd: erase failure at 0x00100000
mtd: erase failure at 0x00140000
mtd: erase failure at 0x00180000
mtd: erase failure at 0x001c0000
mtd: erase failure at 0x00200000
mtd: erase failure at 0x00240000
mtd: erase failure at 0x00280000
mtd: erase failure at 0x002c0000
mtd: erase failure at 0x00300000
mtd: erase failure at 0x00340000
mtd: erase failure at 0x00380000
mtd: erase failure at 0x003c0000
mtd: erase failure at 0x00400000
mtd: erase failure at 0x00440000
mtd: erase failure at 0x00480000
mtd: erase failure at 0x004c0000
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
mtd: erase failure at 0x00040000 (I/O error)
mtd: erase failure at 0x00040000 (I/O error)
mtd: skipping write block at 0x00040000
mtd: erase failure at 0x00080000 (I/O error)
mtd: erase failure at 0x00080000 (I/O error)
mtd: skipping write block at 0x00080000
mtd: erase failure at 0x000c0000 (I/O error)
mtd: erase failure at 0x000c0000 (I/O error)
mtd: skipping write block at 0x000c0000
mtd: erase failure at 0x00100000 (I/O error)
mtd: erase failure at 0x00100000 (I/O error)
mtd: skipping write block at 0x00100000
mtd: erase failure at 0x00140000 (I/O error)
mtd: erase failure at 0x00140000 (I/O error)
mtd: skipping write block at 0x00140000
mtd: erase failure at 0x00180000 (I/O error)
mtd: erase failure at 0x00180000 (I/O error)
mtd: skipping write block at 0x00180000
mtd: erase failure at 0x001c0000 (I/O error)
mtd: erase failure at 0x001c0000 (I/O error)
mtd: skipping write block at 0x001c0000
mtd: erase failure at 0x00200000 (I/O error)
mtd: erase failure at 0x00200000 (I/O error)
mtd: skipping write block at 0x00200000
mtd: erase failure at 0x00240000 (I/O error)
mtd: erase failure at 0x00240000 (I/O error)
mtd: skipping write block at 0x00240000
mtd: erase failure at 0x00280000 (I/O error)
mtd: erase failure at 0x00280000 (I/O error)
mtd: skipping write block at 0x00280000
mtd: erase failure at 0x002c0000 (I/O error)
mtd: erase failure at 0x002c0000 (I/O error)
mtd: skipping write block at 0x002c0000
mtd: erase failure at 0x00300000 (I/O error)
mtd: erase failure at 0x00300000 (I/O error)
mtd: skipping write block at 0x00300000
mtd: erase failure at 0x00340000 (I/O error)
mtd: erase failure at 0x00340000 (I/O error)
mtd: skipping write block at 0x00340000
mtd: erase failure at 0x00380000 (I/O error)
mtd: erase failure at 0x00380000 (I/O error)
mtd: skipping write block at 0x00380000
mtd: erase failure at 0x003c0000 (I/O error)
mtd: erase failure at 0x003c0000 (I/O error)
mtd: skipping write block at 0x003c0000
mtd: erase failure at 0x00400000 (I/O error)
mtd: erase failure at 0x00400000 (I/O error)
mtd: skipping write block at 0x00400000
mtd: erase failure at 0x00440000 (I/O error)
mtd: erase failure at 0x00440000 (I/O error)
mtd: skipping write block at 0x00440000
mtd: erase failure at 0x00480000 (I/O error)
mtd: erase failure at 0x00480000 (I/O error)
mtd: skipping write block at 0x00480000
mtd: erase failure at 0x004c0000 (I/O error)
mtd: erase failure at 0x004c0000 (I/O error)
mtd: skipping write block at 0x004c0000
failed with error: -1
flashing recovery from /tmp/recovery.img
error writing recoveryrun_program: child exited with status 255
script result was [to take effect]
minzip: Extracted file "/tmp/mkbootimg"
minzip: Extracted file "/tmp/patchbootimg.sh"
minzip: Extracted file "/tmp/unpackbootimg"
Custom MTD written
Please wipe system,cache & data
& reboot to recovery for changes
to take effect
Install from sdcard complete.
And now, here are the manual steps to install by hand the 'recovery-v1.5.8-Beta-CustomMTD_S.chacha.zip' package:
Here is the content of the '/tmp' folder:
Code:
/tmp # ls
ls
mkbootimg recovery.img-cmdline unpackbootimg
patchbootimg.sh recovery.img-ramdisk.gz update_binary
recovery.img recovery.img-zImage
recovery.img-base recovery.log
Let's clean-up the formerly generated 'recovery.img' file:
Code:
/tmp # rm recovery.img
rm recovery.img
Now let's dump the recovery again and name it 'recovery_original.img' (and backup it to sdcard):
Code:
/tmp # dump_image recovery /tmp/recovery.img
dump_image recovery /tmp/recovery.img
/tmp # cp recovery.img recovery_original.img
cp recovery.img recovery_original.img
/tmp # cp recovery_original.img /sdcard/recovery_original.img
cp recovery_original.img /sdcard/recovery_original.img
/tmp # rm recovery.img
rm recovery.img
Now let's unpack the 'recovery_original.img' in order to repack it with modified command line afterwards:
Code:
/tmp # /tmp/unpackbootimg /tmp/recovery_original.img /tmp/
/tmp/unpackbootimg /tmp/recovery_original.img /tmp/
BOARD_KERNEL_CMDLINE no_console_suspend=1 console=null
BOARD_KERNEL_BASE 12c00000
Now is the IMPORTANT part, which is repacking with the correct kernel command line.
In our case, the kernel command line we want (as explained in my previous post) is the same as the original one + the new 'mtdparts' addition:
Code:
msm_nand:102
[email protected](misc),[email protected](recovery),[email protected](boot),[email protected]
0000(userdata),[email protected](devlog),[email protected](system),[email protected](c
ache)
Here is the command:
Code:
/tmp # /tmp/mkbootimg --kernel /tmp/recovery_original.img-zImage --ramdisk /tmp/recovery_original.im
g-ramdisk.gz -o /tmp/recovery.img --cmdline "no_console_suspend=1 console=null mtdparts=msm_nand:102
[email protected](misc),[email protected](recovery),[email protected](boot),[email protected]
0000(userdata),[email protected](devlog),[email protected](system),[email protected](c
ache)" --base 12c00000
/tmp/mkbootimg --kernel /tmp/recovery_original.img-zImage --ramdisk /tmp/
recovery_original.img-ramdisk.gz -o /tmp/recovery.img --cmdline "no_console_susp
end=1 console=null mtdparts=msm_nand:[email protected](misc),[email protected]
0000(recovery),[email protected](boot),15[email protected](userdata),10240
[email protected](devlog),[email protected](system),[email protected](c
ache)" --base 12c00000
This has repacked a 'recovery.img' file.
Let's name it 'recovery_modified.img' and copy it as well to sdcard:
Code:
/tmp # cp recovery.img recovery_modified.img
cp recovery.img recovery_modified.img
/tmp # cp recovery_modified.img /sdcard/recovery_modified.img
cp recovery_modified.img /sdcard/recovery_modified.img
Now let's unpack the 'recovery_modified.img' in order to check the BOARD_KERNEL_CMDLINE part:
Code:
/tmp/unpackbootimg /tmp/recovery_modified.img /tmp/
BOARD_KERNEL_CMDLINE no_console_suspend=1 console=null mtdparts=msm_nand:[email protected](misc),
[email protected](recovery),[email protected](boot),[email protected](userdata),[email protected]
000015F00000(devlog),[email protected](system),[email protected](cache)
BOARD_KERNEL_BASE 12c00000
This looks coherent with what I want to do.
Now I mount USB to copy the 'recovery_modified.img' in my android sdk tools folder ('D:\android-sdk-windows\tools\recovery_cMTD.img').
Then I'll flash this modified recovery with a "fastboot flash" command.
Code:
D:\android-sdk-windows\tools>adb reboot bootloader
D:\android-sdk-windows\tools>fastboot flash recovery recovery_cMTD.img
sending 'recovery' (3664 KB)...
OKAY [ 2.797s]
writing 'recovery'...
OKAY [ 3.266s]
finished. total time: 6.063s
The flashing process was a success, which is good.
Then I'll boot to recovery to see if this works.
In bootloader mode, I choose RECOVERY
--> THE RECOVERY DOES NOT BOOT !!!!! (stays frozen on green HTC banner...)
Argh........ the recovery does not boot...
And fortunately, when I reflash the original (CWM) recovery, I can boot to recovery.
So my question now is:
Why does the modified recovery does not boot??????
I compared (hexadecimal compare) the 'recovery_original.img' and the 'recovery_modified.img' files, and really the only difference in it is the command line part.
The file are exactly the same byte size.
And they are identical, except at offset 0x61 where:
the 'recovery_modified.img' file contains the following bytes:
[hexa]
Code:
206D746470617274733D6D736D5F6E616E643A313032344B403078303030303146463030303030286D697363292C353132304B403078303030303032464330303030287265636F76657279292C333332384B40307830303030303334433030303028626F6F74292C31303234304B403078303030303135463030303030286465766C6F67292C3239363936306B4030783030303030333830303030302873797374656D292C353132306B4030783135413030303030286361636865292C3136333834306B403078313546303030303028757365726461746129
[ascii]
Code:
mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](devlog),[email protected](system),[email protected](cache),[email protected](userdata)
whereas the the 'recovery_original.img' file contains 0x00 bytes (same number)...
So my question really is:
Why does the modified recovery does not boot??????
spoutnik

I'm wondering what might happen if you use a more up to date CWM.
I did build this copy of CWM 6.0.1.5 a month or two ago. MOST functionality works. It has some issues with backings and restoring. but otherwise I didn't notice anything else.
Perhaps it will be helpful, and might work with the patching?

Hello. I've read this thread, and wondered (sorry if this is a silly idea) if the partition scheme cannot be altered because of the phone being S-ON.
If I've understood the flash memory when you boot your Chacha is some kind of plain: just a large set of bits one after the other.
And someone do the job of organizing those bits in partitions that once that are setup, can be used to load Android.
Is my idea right?
If it is, then that someone could be the bootloader, and there is where the changes/hacks should be made.

I'm on my phone only, using Tapatalk, could you paste here, or link me to the content of the patchbootimg.sh file? I'm curious about what it does.
Sent from my Galaxy Nexus

Spoutnik, regarding your intent, just by reading the cmdline it seems you messed the partition order. Also it seems to me that your devlog and user data partitions would start at the same offset.
I've been working to do it manually and it works. I have a 312MB /system as seen from the recovery at least.
I'm 99% sure that s-on/s-off isn't the issue but your command line is.
Wondering what would be a good partitioning?
I was thinking giving more to system, and not that much to userdata as the latter can be replaced with app2sd...
I can't say much more right now, I'm from my phone, Internet line at home is dead tonight :-\
Sent from my Galaxy Nexus

Is there any update of this issue?
I am a fresh hand in this field. I think it is much better to keep /data as large as possible because /system size will not increase after new software installation (if my understanding is correct).
BTW, any books recommended for android?
kronflux said:
I'm wondering what might happen if you use a more up to date CWM.
I did build this copy of CWM 6.0.1.5 a month or two ago. MOST functionality works. It has some issues with backings and restoring. but otherwise I didn't notice anything else.
Perhaps it will be helpful, and might work with the patching?
Click to expand...
Click to collapse

watchthinker said:
Is there any update of this issue?
I am a fresh hand in this field. I think it is much better to keep /data as large as possible because /system size will not increase after new software installation (if my understanding is correct).
BTW, any books recommended for android?
Click to expand...
Click to collapse
I got it working, it's a bit tricky but feasible.
Actually with increasing versions of Android also increases the size of system. While on the other hand, if you use app2sd you don't need that much /data AFAIK.
That's why I would rather increase system over data.
Sent from my Galaxy Nexus, no Internet at home these days.

Yes, but I'd like to keep my /system as small as possible, only to keep the basic system (maybe the kernel?).
Chacha's battery is not durable and I'd like programs run from internal flash so I can save battery a little bit
adlx.xda said:
I got it working, it's a bit tricky but feasible.
Actually with increasing versions of Android also increases the size of system. While on the other hand, if you use app2sd you don't need that much /data AFAIK.
That's why I would rather increase system over data.
Sent from my Galaxy Nexus, no Internet at home these days.
Click to expand...
Click to collapse

watchthinker said:
Yes, but I'd like to keep my /system as small as possible, only to keep the basic system (maybe the kernel?).
Click to expand...
Click to collapse
Sorry, that doesn't make much sense...
Sent from my Galaxy Nexus

It is the pity that Chacha comes with a too small ROM for data.
I don't know why my internal flash size keep going down.
adlx.xda said:
Sorry, that doesn't make much sense...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse

Related

Stuck on HTC black screen.

Can't boot into stock ROM after RUU 1.56 and getting the 110 error. I am able to boot if I use fastboot oem boot however. I've been able to get to the Ramon-recovery and I've attempted to flash a new ROM several times. I have downloaded new copies of the RUU and the ROMs and still a no go. After it flashes it starts to reboot but then just shuts off and I have to take the battery out. I've followed the guide to fix the 110 error in thread by dfbonney. Of course I never did a nandroid backup, but when following the guide I can't flash the boot section I get
Code:
#
flash_image boot /sdcard/boot.img
mtd: erase failure at 0x000a0000 (I/O error
mtd: erase failure at 0x000a0000 (I/O error
mtd: skipping write block at 0x000a0000
error writing boot: No space left on device
Help?

Help - Can not unbrick TF101 B70 with Wheelie

Hi, my wife's stock TF101 went into a boot loop last night that I can't get it to break out of after multiple cold boot attempts. I also tried doing a factory reset but that gives me the sad android guy on his back (same thing when I try to boot to recovery).
I've installed tons of custom roms over the years and am generally quite knowledgeable when it comes to android, but I'm stuck on this issue (and I'm starting to wonder if my eMMC is faulty or something).
The good news is that I can get into APX mode and use nvflash
I've downloaded both the .24 and .27 firmware updates from asus and tried to to a reflash using wheelie and I keep getting the same error (I've tried this via windows and linux)
My formats and downloads go through successfully each time but then I get these errors:
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x14000
5) flags: 0
I've been googling them all morning with no luck and any help would be greatly appreciated
Here's the full output from reflash:
C:\Users\panderson\Desktop\wheelie>blobunpack.exe blob
Header size: 60
4 partitions starting at offset 0x3C
Blob version: 65536
Partition 0
Name: EBT
Offset: 124 (0x7C)
Size: 1454712 (0x163278)
Writing file blob.EBT (1454712 bytes)
Partition 1
Name: SOS
Offset: 1454836 (0x1632F4)
Size: 4284416 (0x416000)
Writing file blob.SOS (4284416 bytes)
Partition 2
Name: LNX
Offset: 5739252 (0x5792F4)
Size: 4151296 (0x3F5800)
Writing file blob.LNX (4151296 bytes)
Partition 3
Name: APP
Offset: 9890548 (0x96EAF4)
Size: 536870912 (0x20000000)
Writing file blob.APP (536870912 bytes)
C:\Users\panderson\Desktop\wheelie>reflash_sbkv2.bat
C:\Users\panderson\Desktop\wheelie>cd C:\Users\panderson\Desktop\wheelie\
C:\Users\panderson\Desktop\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl
bootloader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x252308533528241111
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
C:\Users\panderson\Desktop\wheelie>"nvflash.exe" -r --bct transformer.bct --setb
ct --configfile flash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
sending file: blob.LNX
/ 4151296/4151296 bytes sent
blob.LNX sent successfully
sending file: blob.APP
/ 536870912/536870912 bytes sent
blob.APP sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x14000
5) flags: 0
C:\Users\panderson\Desktop\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0

[Q] No MBR found after flashing image files into a board

I have a Samsung development board. After flash ICS images files into internal storage, at first time it can boot to android animation but failed to go to launcher; when i boot it again, it report 'NO MBR is found at SD/MMC', and can not be flashed. I use MMC command to create the partition and flash it, same error occurs. u-boot log is:
reading kernel device 0 Start 6144, Count 10240
mmc read 0 0x40008000 6144 10240
MMC read: dev # 0, block # 6144, count 10240 ... there are pending interrupts 0x00000008
error during transfer: 0x00008024
mmc read failed
-1 blocks read: ERROR
completed
reading ramdisk device 0 Start 16384, Count 10240
mmc read 0 0x41000000 16384 10240
MMC read: dev # 0, block # 16384, count 10240 ... there are pending interrupts 0x00000008
[ERROR] response timeout error : 00002104 cmd 18
mmc read failed
-19 blocks read: ERROR
completed

Encryption Unsucsessful - E:unable to mount /data - nothing works

Sorry for my bad English
A few weeks ago i installed TWRP 2.2.1.4 and flashed the eos4 JB4,2 rom
I created 3 User on Android and it worked fine with no problems.
After 2 weeks i used the keyboard-Dock and now it boots with
"Encryption Unsucsessful"
I used the wipe Button on recovery boot - no sucsess
Then I went into Recovery Menu and used Factory Reset - no sucsess
I reflashed the eos4 - rom - failure "E:unable to mount /data"
I read in different Forums and used different ways (Easy Flasher,Peri-Tool,Wheelie,NVFlash...)
to unbrick the Transformer but nothing works for me.
(E:unable to mount /data)
I can connected to the TF101(SBK1) under win8 and Ubuntu 12.10 in adb and apx Mode
and can use the sytem and sdcard folder to push or pull files to or from the TF101.
Is there any way to swap the internalSD to externalSD (vold.fstab) and flash a rom that can access it
or knows someone another way to fix my Problem?
What errors did NvFlash return and what files did you use?
Thing O Doom said:
What errors did NvFlash return and what files did you use?
Click to expand...
Click to collapse
Thank you for answer
I used so many different ways on windows and linux, i am not sure which software i used at first,
but i start from scratch.
use Ubuntu 12.10
- udev.rules created for user
Sorry cant post complete Links (min.10 posts)
- download wheelie - androidroot.mobi/download/wheelie.tar.bz2
- download recovery twrp - techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
- download recovery cwm - download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.3-tf101.img
- open terminal:# sudo ./blobunpack recovery-clockwork-6.0.1.3-tf101.img
=
Header size: 60
1 partitions starting at offset 0x3C
Blob version: 65536
Partition 0
Name: SOS
Offset: 76 (0x4C)
Size: 4628480 (0x46A000)
Writing file recovery-clockwork-6.0.1.3-tf101.img.SOS (4628480 bytes)
- same with trwp
- tablet in bootmode (power and vol + for 10sec.)
- terminal:# sudo ./nvflash -r --download 5 recovery-clockwork-6.0.1.3-tf101.img.SOS
=
Nvflash started
[resume mode]
(hang - 60min. - restart)
- tablet in bootmode (power and vol + for 10sec.)
- terminal:# sudo ./nvflash -r --download 5 openrecovery-twrp-2.3.2.3-tf101.blob.SOS
=
Nvflash started
[resume mode]
(hang - 120min. restart)
-download WW_epad-user-9.2.1.27 from asus.de/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
-unzip the file and copy the blob to the wheelie-folder
-use blobunpack and open a terminal
-terminal:# sudo ./reflash_sbkv1.sh
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 1.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x33c208443603097
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
sending file: blob.LNX
/ 4151296/4151296 bytes sent
blob.LNX sent successfully
sending file: blob.APP
/ 536870912/536870912 bytes sent
blob.APP sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x140005) flags: 0
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Use these files: http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.27
Wheelie from androidroot.mobi
Unzip first link, then overwrite with wheelie.zip files. Run reflash_sbkv1.bat
See what that does.
Thing O Doom said:
Use these files: xdafileserver.nl/index.php?dir=Asus%2FAsus+Transformer+%28TF101%29%2FSTOCK+ROMS%2FICS+.27
Wheelie from androidroot.mobi
Unzip first link, then overwrite with wheelie.zip files. Run reflash_sbkv1.bat
See what that does.
Click to expand...
Click to collapse
Ok, i download and unzip the file in a new folder.
Then i copy all files from wheelie to the new folder and run "sudo ./reflash_sbkv1.sh"
Result:Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 1.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x33c208443603097
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
sending file: blob.LNX
/ 4151296/4151296 bytes sent
blob.LNX sent successfully
sending file: blob.APP
/ 536870912/536870912 bytes sent
blob.APP sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x140005) flags: 0
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
That error looks like it's with NvFlash, if possible can you try running the .bat in Widoze?
If not I don't think it's going to take anything you send at it, can you try just writing the Blob.SOS and Blob.EBT partitions, then try booting into the recovery, if that works you can pick up the TWRP or Rouge or whatever recovery blob file and rename to Blob.SOS , giving you back recovery that might work.
This is a very strange issue.
Thing O Doom said:
That error looks like it's with NvFlash, if possible can you try running the .bat in Widoze?
If not I don't think it's going to take anything you send at it, can you try just writing the Blob.SOS and Blob.EBT partitions, then try booting into the recovery, if that works you can pick up the TWRP or Rouge or whatever recovery blob file and rename to Blob.SOS , giving you back recovery that might work.
This is a very strange issue.
Click to expand...
Click to collapse
I reactivated my old PC with Windows XP and install the Software and Driver
Then I start "cmd" with admin rights and execute download.bat
C:\android\NVFLASH_ICS_9.2.1.27_WW_NOROOT\NVFLASH_ICS_9.2.1.27_WW_NOROOT>"nvflas
h.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl blob.
EBT --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c208443603097
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x2 (0x2) flags: 0
second
C:\android\NVFLASH_ICS_9.2.1.27_WW_NOROOT\NVFLASH_ICS_9.2.1.27_WW_NOROOT>nvflash
-r --download 5 openrecovery-twrp-2.3.2.3-tf101.blob.SOS
Nvflash started
[resume mode]
failed executing command 14 NvError 0x120002
command failure: partition download failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
third
C:\android\NVFLASH_ICS_9.2.1.27_WW_NOROOT\NVFLASH_ICS_9.2.1.27_WW_NOROOT>nvflash
-r --getpartitiontable partition_table.txt
Nvflash started
[resume mode]
I dont know what "partition 2 BCT" is ?
Is the Partitionstable completely damaged ?
and if its broken, is there a way to manually create new partitions?
same problem.
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %, but here my device hang ... -> this line not comming -> [!] Done - your device should now be ready for nvflash
what now? try with unix system or a hardfailure emmc problem?
only apx mode running, not adb possible or start recovery ...
I'm starting to think that the eMMC is bad/Faulty chip. Which would mean a hardware problem and almost nothing you can do.. :[:[
Is RMA an option or not at all?
I'm essentially out of Software related ideas tbh, and you've been wonderful about doing things right :/
Anyone else have any ideas?
EDIT: May want to do this just in case --
Lethe6 said:
The usual... uninstall and delete the drivers, reinstall the recommended one (the universal naked drivers), and try again. Do this even if everything appears ok, there still may be corruption of some sort, like chkdsk messing up a driver file or moving it, etc.
Click to expand...
Click to collapse
I had an issue like that but it turned out to be a faulty cord. Not saying that's your issue but it is a possibility.
Sent from my Transformer TF101 using xda premium
Thing O Doom said:
I'm starting to think that the eMMC is bad/Faulty chip. Which would mean a hardware problem and almost nothing you can do.. :[:[
Is RMA an option or not at all?
I'm essentially out of Software related ideas tbh, and you've been wonderful about doing things right :/
Anyone else have any ideas?
EDIT: May want to do this just in case --
Click to expand...
Click to collapse
Thank you for your help :highfive: but RMA is no option for me.
Either I find a way to install a rom and boot from the external SD card or I must take the tablet out of operation, the repertory is too expensive ...
Some time ago I read a post of Prime Transformer where the vold.fstab file was modified, and the system ran on the sd card
but I dont find the Post currently
I will post my next steps further and if you should still have an idea what I could do, I'm grateful for any tip
The thing about that is you would need to modify the bootflags to get it to do boot from the sd card, and I'm not sure you can do that with your tab in it's current state :c
Thing O Doom said:
The thing about that is you would need to modify the bootflags to get it to do boot from the sd card, and I'm not sure you can do that with your tab in it's current state :c
Click to expand...
Click to collapse
Can you specify how can I do that?
Meanwhile I started the Tablet in TWRP Recovery and use adb with folowing commands
C:\android\adb>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30203904 mmcblk0
179 1 524288 mmcblk0p1
179 2 542208 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 542208 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 28563968 mmcblk0p7
259 0 5120 mmcblk0p8
259 1 8192 mmcblk0p9
~ # ←[6nfdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT di
sklabel
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 943872.
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): ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 30.9 GB, 30928797696 bytes
4 heads, 16 sectors/track, 943872 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
~ # ←[6nfdisk -l -u /dev/block/mmcblk0
fdisk -l -u /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 30.9 GB, 30928797696 bytes
4 heads, 16 sectors/track, 943872 cylinders, total 60407808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table ???
C:\android\adb>adb shell
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1,
data=ordered)
/dev/block/mmcblk0p1 on /system type ext4 (rw,relatime,barrier=1,data=ordered)

[Q] EXT4-fs errors - NAND dying?

Phone: Galaxy S3 VZW 32GB
Recovery: TWRP 2.7.1.0
Mod: CM11 m8
Kernel, governer, etc all CM11 stock.
Problem:
Twice today the phone rebooted itself while performing large file copy operations. last_kmsg from both reboots basically look the same:
Code:
[40996.107363] Buffer I/O error on device mmcblk0p15, logical block 6751031
[40996.114291] Buffer I/O error on device mmcblk0p15, logical block 6751032
[40996.120761] Buffer I/O error on device mmcblk0p15, logical block 6751033
[40996.127476] Buffer I/O error on device mmcblk0p15, logical block 6751034
[40996.134160] Buffer I/O error on device mmcblk0p15, logical block 6751035
[40996.140813] Buffer I/O error on device mmcblk0p15, logical block 6751036
[40996.147528] Buffer I/O error on device mmcblk0p15, logical block 6751037
[40996.154181] Buffer I/O error on device mmcblk0p15, logical block 6751038
[40996.160926] Buffer I/O error on device mmcblk0p15, logical block 6751039
[41056.701656] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
[41056.708065] afe_callback: cmd = 0x100dc returned error = 0x3
[41056.713681] afe_send_hw_delay: config cmd failed
[41065.991721] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[41066.310781] cypress_touchkey 16-0020: not real interrupt (1).
[41117.725034] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 113, 644 clusters in bitmap, 530 in gd
[41117.744476] Aborting journal on device mmcblk0p15-8.
[41117.764161] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[41117.764161]
[41117.773257] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0778f40>] (panic+0x88/0x1f8)
[41117.781344] [<c0778f40>] (panic+0x88/0x1f8) from [<c01a7134>] (ext4_handle_error+0x8c/0x98)
[41117.789738] [<c01a7134>] (ext4_handle_error+0x8c/0x98) from [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4)
[41117.799626] [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[41117.810125] [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0)
[41117.820288] [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4)
[41117.830085] [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c)
[41117.840005] [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c) from [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388)
[41117.850351] [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388) from [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0)
[41117.860728] [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0) from [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac)
[41117.870739] [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac) from [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4)
[41117.880353] [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4) from [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c)
[41117.890241] [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c) from [<c0191908>] (ext4_da_writepages+0x340/0x5b8)
[41117.900496] [<c0191908>] (ext4_da_writepages+0x340/0x5b8) from [<c00ff3e0>] (do_writepages+0x24/0x38)
[41117.909713] [<c00ff3e0>] (do_writepages+0x24/0x38) from [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c)
[41117.919419] [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c) from [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68)
[41117.930436] [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68) from [<c0188ab0>] (ext4_sync_file+0xb4/0x414)
[41117.940447] [<c0188ab0>] (ext4_sync_file+0xb4/0x414) from [<c0158338>] (vfs_fsync_range+0x34/0x44)
[41117.949451] [<c0158338>] (vfs_fsync_range+0x34/0x44) from [<c0158368>] (vfs_fsync+0x20/0x28)
[41117.957874] [<c0158368>] (vfs_fsync+0x20/0x28) from [<c01586a0>] (sys_fdatasync+0x18/0x34)
[41117.966115] [<c01586a0>] (sys_fdatasync+0x18/0x34) from [<c000e000>] (ret_fast_syscall+0x0/0x30)
[41117.974874] CPU1: stopping
[41117.977529] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0012f6c>] (handle_IPI+0x100/0x1cc)
[41117.986258] [<c0012f6c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[41117.994804] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000ddbc>] (__irq_usr+0x3c/0x60)
[41118.003166] Exception stack(0xcb443fb0 to 0xcb443ff8)
[41118.008141] 3fa0: 75254dc0 752a4547 000001a4 00000564
[41118.016321] 3fc0: 00002000 00000010 00000612 75252000 bea932dc 75254f00 bea932ed 7522b6e8
[41118.024531] 3fe0: 40224e24 bea93268 40211be7 4021ab9c 80010030 ffffffff
[41118.131322] Rebooting in 5 seconds..
[41123.135045] Going down for restart now
[41123.138005] msm_restart : clear reset flag
Connected via ADB and ran e2fsck, but all appears ok.
Code:
e2fsck -pcfv /dev/block/mmcblk0p15
sh: badblocks: not found
/dev/block/mmcblk0p15: Updating bad block inode.
19845 inodes used (1.13%)
1139 non-contiguous files (5.7%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 19521/116/1
6040224 blocks used (86.35%)
0 bad blocks
1 large file
17771 regular files
1861 directories
0 character device files
0 block device files
5 fifos
0 links
191 symbolic links (185 fast symbolic links)
8 sockets
--------
19836 files
~ # ?[6ne2fsck -pcfv /dev/block/mmcblk0p17
e2fsck -pcfv /dev/block/mmcblk0p17
sh: badblocks: not found
/dev/block/mmcblk0p17: Updating bad block inode.
161 inodes used (0.30%)
19 non-contiguous files (11.8%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 153
34685 blocks used (16.13%)
0 bad blocks
0 large files
147 regular files
5 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
152 files
1) Did the file system already correct the previous errors, which is why none are detected now?
2) Any other commands/tests that can be run to determine really what is/was wrong?
any other thoughts on why this issue would occur?
Got another crash last night, again copying a lot of new music onto the phone from computer. Crash call stack is different this time though.
Code:
[ 7523.190689] Buffer I/O error on device mmcblk0p15, logical block 6850041
[ 7523.197373] Buffer I/O error on device mmcblk0p15, logical block 6850042
[ 7523.204241] Buffer I/O error on device mmcblk0p15, logical block 6850043
[ 7523.210711] Buffer I/O error on device mmcblk0p15, logical block 6850044
[ 7523.217395] Buffer I/O error on device mmcblk0p15, logical block 6850045
[ 7523.224140] Buffer I/O error on device mmcblk0p15, logical block 6850046
[ 7523.230732] Buffer I/O error on device mmcblk0p15, logical block 6850047
[ 7523.237721] Aborting journal on device mmcblk0p15-8.
[ 7523.288385] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[ 7523.633754] cypress_touchkey 16-0020: not real interrupt (1).
[ 7524.010986] EXT4-fs error (device mmcblk0p15): ext4_journal_start_sb:328: Detected aborted journal
[ 7524.018982] EXT4-fs (mmcblk0p15): Remounting filesystem read-only
[ 7524.061985] Kernel panic - not syncing: EXT4-fs panic from previous error
[ 7524.062016]
[ 7524.069340] [<c00138c8>] (unwind_backtrace+0x0/0xe0) from [<c07b5180>] (panic+0x88/0x1f8)
[ 7524.077459] [<c07b5180>] (panic+0x88/0x1f8) from [<c01a0714>] (__ext4_abort+0xc0/0xe0)
[ 7524.085394] [<c01a0714>] (__ext4_abort+0xc0/0xe0) from [<c01a0b34>] (ext4_journal_start_sb+0x154/0x1b8)
[ 7524.094794] [<c01a0b34>] (ext4_journal_start_sb+0x154/0x1b8) from [<c018b140>] (ext4_dirty_inode+0x14/0x40)
[ 7524.104530] [<c018b140>] (ext4_dirty_inode+0x14/0x40) from [<c014e37c>] (__mark_inode_dirty+0x2c/0x1c4)
[ 7524.113839] [<c014e37c>] (__mark_inode_dirty+0x2c/0x1c4) from [<c0141c9c>] (file_update_time+0x100/0x120)
[ 7524.123392] [<c0141c9c>] (file_update_time+0x100/0x120) from [<c00f15a4>] (__generic_file_aio_write+0x2cc/0x428)
[ 7524.133586] [<c00f15a4>] (__generic_file_aio_write+0x2cc/0x428) from [<c00f1760>] (generic_file_aio_write+0x60/0xc8)
[ 7524.144085] [<c00f1760>] (generic_file_aio_write+0x60/0xc8) from [<c01819e4>] (ext4_file_write+0x258/0x2bc)
[ 7524.153821] [<c01819e4>] (ext4_file_write+0x258/0x2bc) from [<c012b108>] (do_sync_write+0x9c/0xd8)
[ 7524.162763] [<c012b108>] (do_sync_write+0x9c/0xd8) from [<c012b1ec>] (vfs_write+0xa8/0x130)
[ 7524.171095] [<c012b1ec>] (vfs_write+0xa8/0x130) from [<c012b414>] (sys_pwrite64+0x50/0x80)
[ 7524.179275] [<c012b414>] (sys_pwrite64+0x50/0x80) from [<c000de80>] (ret_fast_syscall+0x0/0x30)
[ 7524.188004] CPU1: stopping
[ 7524.190659] [<c00138c8>] (unwind_backtrace+0x0/0xe0) from [<c001294c>] (handle_IPI+0x100/0x1cc)
[ 7524.199357] [<c001294c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[ 7524.207964] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000dc3c>] (__irq_usr+0x3c/0x60)
[ 7524.216296] Exception stack(0xc6637fb0 to 0xc6637ff8)
[ 7524.221271] 7fa0: b65f8b76 b6ed66d7 b65f8b77 00000037
[ 7524.229481] 7fc0: 00000000 b6ed66da b65faba4 b65f8b54 b65f8b74 b796f610 b6ed5398 00000000
[ 7524.237630] 7fe0: 50704001 b65f8b3c b6ecb283 b6ebf55c 60030030 ffffffff
[ 7524.344360] Rebooting in 5 seconds..
[ 7529.347686] Going down for restart now
[ 7529.350708] msm_restart : clear reset flag
Wrong forum or the content too technical for people?
BSOD2600 said:
Phone: Galaxy S3 VZW 32GB
Recovery: TWRP 2.7.1.0
Mod: CM11 m8
Kernel, governer, etc all CM11 stock.
Problem:
Twice today the phone rebooted itself while performing large file copy operations. last_kmsg from both reboots basically look the same:
Code:
[40996.107363] Buffer I/O error on device mmcblk0p15, logical block 6751031
[40996.114291] Buffer I/O error on device mmcblk0p15, logical block 6751032
[40996.120761] Buffer I/O error on device mmcblk0p15, logical block 6751033
[40996.127476] Buffer I/O error on device mmcblk0p15, logical block 6751034
[40996.134160] Buffer I/O error on device mmcblk0p15, logical block 6751035
[40996.140813] Buffer I/O error on device mmcblk0p15, logical block 6751036
[40996.147528] Buffer I/O error on device mmcblk0p15, logical block 6751037
[40996.154181] Buffer I/O error on device mmcblk0p15, logical block 6751038
[40996.160926] Buffer I/O error on device mmcblk0p15, logical block 6751039
[41056.701656] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
[41056.708065] afe_callback: cmd = 0x100dc returned error = 0x3
[41056.713681] afe_send_hw_delay: config cmd failed
[41065.991721] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[41066.310781] cypress_touchkey 16-0020: not real interrupt (1).
[41117.725034] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 113, 644 clusters in bitmap, 530 in gd
[41117.744476] Aborting journal on device mmcblk0p15-8.
[41117.764161] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[41117.764161]
[41117.773257] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0778f40>] (panic+0x88/0x1f8)
[41117.781344] [<c0778f40>] (panic+0x88/0x1f8) from [<c01a7134>] (ext4_handle_error+0x8c/0x98)
[41117.789738] [<c01a7134>] (ext4_handle_error+0x8c/0x98) from [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4)
[41117.799626] [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[41117.810125] [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0)
[41117.820288] [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4)
[41117.830085] [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c)
[41117.840005] [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c) from [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388)
[41117.850351] [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388) from [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0)
[41117.860728] [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0) from [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac)
[41117.870739] [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac) from [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4)
[41117.880353] [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4) from [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c)
[41117.890241] [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c) from [<c0191908>] (ext4_da_writepages+0x340/0x5b8)
[41117.900496] [<c0191908>] (ext4_da_writepages+0x340/0x5b8) from [<c00ff3e0>] (do_writepages+0x24/0x38)
[41117.909713] [<c00ff3e0>] (do_writepages+0x24/0x38) from [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c)
[41117.919419] [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c) from [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68)
[41117.930436] [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68) from [<c0188ab0>] (ext4_sync_file+0xb4/0x414)
[41117.940447] [<c0188ab0>] (ext4_sync_file+0xb4/0x414) from [<c0158338>] (vfs_fsync_range+0x34/0x44)
[41117.949451] [<c0158338>] (vfs_fsync_range+0x34/0x44) from [<c0158368>] (vfs_fsync+0x20/0x28)
[41117.957874] [<c0158368>] (vfs_fsync+0x20/0x28) from [<c01586a0>] (sys_fdatasync+0x18/0x34)
[41117.966115] [<c01586a0>] (sys_fdatasync+0x18/0x34) from [<c000e000>] (ret_fast_syscall+0x0/0x30)
[41117.974874] CPU1: stopping
[41117.977529] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0012f6c>] (handle_IPI+0x100/0x1cc)
[41117.986258] [<c0012f6c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[41117.994804] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000ddbc>] (__irq_usr+0x3c/0x60)
[41118.003166] Exception stack(0xcb443fb0 to 0xcb443ff8)
[41118.008141] 3fa0: 75254dc0 752a4547 000001a4 00000564
[41118.016321] 3fc0: 00002000 00000010 00000612 75252000 bea932dc 75254f00 bea932ed 7522b6e8
[41118.024531] 3fe0: 40224e24 bea93268 40211be7 4021ab9c 80010030 ffffffff
[41118.131322] Rebooting in 5 seconds..
[41123.135045] Going down for restart now
[41123.138005] msm_restart : clear reset flag
Connected via ADB and ran e2fsck, but all appears ok.
Code:
e2fsck -pcfv /dev/block/mmcblk0p15
sh: badblocks: not found
/dev/block/mmcblk0p15: Updating bad block inode.
19845 inodes used (1.13%)
1139 non-contiguous files (5.7%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 19521/116/1
6040224 blocks used (86.35%)
0 bad blocks
1 large file
17771 regular files
1861 directories
0 character device files
0 block device files
5 fifos
0 links
191 symbolic links (185 fast symbolic links)
8 sockets
--------
19836 files
~ # ?[6ne2fsck -pcfv /dev/block/mmcblk0p17
e2fsck -pcfv /dev/block/mmcblk0p17
sh: badblocks: not found
/dev/block/mmcblk0p17: Updating bad block inode.
161 inodes used (0.30%)
19 non-contiguous files (11.8%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 153
34685 blocks used (16.13%)
0 bad blocks
0 large files
147 regular files
5 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
152 files
1) Did the file system already correct the previous errors, which is why none are detected now?
2) Any other commands/tests that can be run to determine really what is/was wrong?
Click to expand...
Click to collapse
Did you ever figure this out?
Was it transferring from SD to External SD? Or just to Internal?
Sent from my SCH-I535 using XDA Free mobile app
Nope, never figured this out and yes it's occurred more than once.
Seem to recall was transferring large file content from PC to Internal. Don't think it's happened with CM11m10 -- yet... but on the other hand I dont do large file transfers daily.
Still an issue with CM11m11 (or more likely the hardware). system reboot when deleting a ~300 MB file from within MX Player.
Code:
[52140.774902] Buffer I/O error on device mmcblk0p15, logical block 4134812
[52140.781556] end_request: I/O error, dev mmcblk0, sector 43663360
[52140.787874] Buffer I/O error on device mmcblk0p15, logical block 5046272
[52140.794405] end_request: I/O error, dev mmcblk0, sector 44711936
[52140.800387] Buffer I/O error on device mmcblk0p15, logical block 5177344
[52140.807254] Buffer I/O error on device mmcblk0p15, logical block 5242880
[52140.813846] Buffer I/O error on device mmcblk0p15, logical block 5275648
[57664.812106] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 158, 2379 clusters in bitmap, 1936 in gd
[57664.822300] Aborting journal on device mmcblk0p15-8.
[57664.833928] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[57664.833928]
[57664.842962] [<c0013928>] (unwind_backtrace+0x0/0xe0) from [<c07abc78>] (panic+0x88/0x1f8)
[57664.851172] [<c07abc78>] (panic+0x88/0x1f8) from [<c01a257c>] (ext4_handle_error+0x8c/0x98)
[57664.859504] [<c01a257c>] (ext4_handle_error+0x8c/0x98) from [<c01a30e8>] (__ext4_grp_locked_error+0xe8/0x1c4)
[57664.869393] [<c01a30e8>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b1a60>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[57664.879892] [<c01b1a60>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b3a68>] (ext4_mb_init_cache+0x358/0x5f0)
[57664.890055] [<c01b3a68>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b4200>] (ext4_mb_load_buddy+0x278/0x2b4)
[57664.899852] [<c01b4200>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01b7ea4>] (ext4_free_blocks+0x578/0x9f0)
[57664.909436] [<c01b7ea4>] (ext4_free_blocks+0x578/0x9f0) from [<c01ac74c>] (ext4_ext_remove_space+0x6ec/0xe94)
[57664.919385] [<c01ac74c>] (ext4_ext_remove_space+0x6ec/0xe94) from [<c01aed00>] (ext4_ext_truncate+0x100/0x1d0)
[57664.929365] [<c01aed00>] (ext4_ext_truncate+0x100/0x1d0) from [<c0188a24>] (ext4_truncate+0xb4/0x174)
[57664.938582] [<c0188a24>] (ext4_truncate+0xb4/0x174) from [<c018d2c0>] (ext4_evict_inode+0x328/0x490)
[57664.947678] [<c018d2c0>] (ext4_evict_inode+0x328/0x490) from [<c0142c84>] (evict+0x94/0x158)
[57664.956101] [<c0142c84>] (evict+0x94/0x158) from [<c0139f50>] (do_unlinkat+0xe8/0x130)
[57664.963975] [<c0139f50>] (do_unlinkat+0xe8/0x130) from [<c000dec0>] (ret_fast_syscall+0x0/0x30)
[57665.072964] Rebooting in 5 seconds..
[57670.076779] Going down for restart now
[57670.079800] msm_restart : clear reset flag

Categories

Resources