Related
hi guys, this problem was solved, unexpectedly.
after read guhl99's post in Thread: PSA: Rooting methods and recently discovered dangersthread,
i finally confirm that my htc DS was bricked by an accidentally freeze and the immediately battery pulled-out-&-pushed-in unstably.
the eMMC-chip(marked as SAMSUNG104, KLM4G2DEJE A001, FDAE15PC) was completely dead,
i made a replacement with a new one(made by Sandisk serial:SEM04G), and then everything goes on good.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Thanks to" the design of the battery compartment door, the battery pullout-pushin becomes running-risks.
Make sure there's NOT any tiny battery move when you flipping the compartment door from the side.
Make sure disconnect the battery and DS itself quickly & stably as soon as you could.
Make sure there's at least 10 seconds between battery pullout and pushin.
"How can I be sure if it's a hw problem? I mean, it looks like one, but I would like to be sure..."
please check #27 http://forum.xda-developers.com/showpost.php?p=16135893&postcount=27
A eMMC design flaw, Confirming info from htc-offical (thanks apairofscissors)
http://forum.xda-developers.com/showpost.php?p=20163494&postcount=23
=============Debug Procedure=============
Here are 3 parts in this post.
Actually, it's not that long,
and the most important info is in 8. [ adb shell ]
================Background================
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.00RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2001,14:58:38
ClockworkMod Recovery 3.2.0.0
a busybox within
================what happend================
while installing some apps from the market, DS was stuck at a app called "push ups".
i pulled out battery and reboot, and there came loopboot.
got in Recovery, it promts
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
================things i did================
1. [ wipe data/factory reset]
Code:
Formating /data...
black splash screen, and then
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
[ wipe cache ]
Code:
Formating /cache...
Cache wipe complete.
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
2. [ install zip from sdcard ]
Code:
-Checking Model ID
-success!
-Model ID - HTC sage
Now flashing
E:Error in /sdcard/*******.zip
(Status 1)
Installation aborted.
3. [ backup and restore ]
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoreing system....
Error while formatting /system!
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
4. [ RUU+Goldencard ]
Goldencard is good, in FASTBOOT USB mod,
passed the (version) checking, updating 1.28.401.1 to 1.47.950.3, but stuck at
Code:
rebooting bootloader ......
upgrading ROM image in your Android Phone...
Please do NOT disconnect USB cable nor run any program.
5. [ ROM.zip->PG88IMG.zip ]
ROM.zip was picked-up from RUU, renamed to PG88IMG.zip, copied to sdcard,
reboot to HBOOT, and it unzip the pack normally, then stuck at updating screen, more than 1 hour.
Code:
HBOOT
[INDENT]Parsing...[SD ZIP]
[1] BOOTLOADER -updating
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SLPASH1
[6] USERDATA
[7] TP
[8] DADIO_V2
[9] RADIO_CUST
Do you want to start update?
[/INDENT]
6. [ PG88IMG.zip for Recovery/Radio ]
HBOOT asks do you wanna upgrade, click VOL-up, then stuck at updating screen
Code:
HBOOT
[INDENT]Parsing...[SD ZIP]
[1] RECOVERY -updating
*********
Updating is in progress...
Do not power off the device!
[/INDENT]
7. [ fastboot ]
Code:
SH********8 Connected.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
Radio version: 38.03.02.15_m.
SPL/hboot version: 0.98.0000.
product: saga.
mid: pg88*****.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
[B]fastboot erase cache[/B]
erasing 'cache'...
[COLOR=red]erasing 'cache'... FAILED (command write failed (Unknown error))[/COLOR]
8. [ adb shell ]
DS has 2 storages:
eMMC-chip inside, /system /data /cache are mounted to mmcblk0p25, mmcblk0p26, mmcblk0p27;
SDCard removable /sdcard is mounted to mmcblk1p1.
i connect the my phone(DS-brick) through adb-shell, and compared with my friend's (DS-good), here are the prompts:
DS-good shows
Code:
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,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/[COLOR=blue]mmcblk0p25 on /system type ext3 [/COLOR](rw,relatime,errors=continue,barrier=0,data=writeback)
/dev/block/[COLOR=blue]mmcblk0p26 on /data type ext3[/COLOR] (rw,relatime,errors=continue,barrier=0,
data=writeback)
/dev/block/[COLOR=blue]mmcblk0p27 on /cache type ext3 [/COLOR](rw,nodev,noatime,nodiratime,errors=co
ntinue,barrier=0,data=writeback)
/dev/block/[COLOR=blue]mmcblk1p1 on /sdcard type vfat[/COLOR] (rw,relatime,fmask=0000,dmask=0000,all
ow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-
ro)
DS-brick shows
Code:
/dev/block/[COLOR=blue][COLOR=red][B]mmcblk0p27 on /cache type ext4[/B][/COLOR] [/COLOR](ro,nodev,noatime,nodiratime,barrier=1
,data=ordered)
~ # mount system
mount: mounting /dev/block/mmcblk0p25 on /system [COLOR=red][B]failed: Invalid argument[/B][/COLOR]
~ # mount data
mount: mounting /dev/block/mmcblk0p26 on /data [COLOR=red][B]failed: Invalid argument[/B][/COLOR]
it means the filesystem on eMMC was accidentally broke down. so, im trying to restore the filesystem, and get these:
list the eMMC-chip partition info
Code:
~ # fdisk -l /dev/block/[B]mmcblk0[/B]
fdisk -l /dev/block/mmcblk0
[B][COLOR=red]fdisk: can't open '/dev/block/mmcblk0': I/O error[/COLOR][/B]
format /cache with type ext3
Code:
~ # mke2fs -j /dev/block/[COLOR=blue]mmcblk0p27[/COLOR]
mke2fs 1.40.8 (13-Mar-2008)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
76912 inodes, 307196 blocks
15359 blocks (5.00%) reserved for the super user
[B]First data block=1[/B]
Maximum filesystem blocks=67633152
38 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
[COLOR=blue]Warning: could not read block 0: [/COLOR]
[COLOR=blue]Attempt to read block from filesystem resulted in short read[/COLOR]
[COLOR=blue]Writing inode tables: done[/COLOR]
[COLOR=red][B]ext2fs_mkdir: Attempt to read block from filesystem [/B][/COLOR]
[COLOR=red][B]resulted in short read while creating root dir[/B][/COLOR]
format /system with type ext3
Code:
~ # mke2fs -j /dev/block/[COLOR=blue]mmcblk0p25[/COLOR]
mke2fs -j /dev/block/mmcblk0p25
mke2fs 1.40.8 (13-Mar-2008)
Warning: 256-byte inodes not usable on older systems
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
35760 inodes, 142847 blocks
7142 blocks (5.00%) reserved for the super user
[B]First data block=0[/B]
Maximum filesystem blocks=146800640
5 block groups
32768 blocks per group, 32768 fragments per group
7152 inodes per group
Superblock backups stored on blocks:
32768, 98304
[COLOR=blue]Warning: could not read block 0: [/COLOR]
[COLOR=blue]Attempt to read block from filesystem resulted [/COLOR][COLOR=blue]in short read[/COLOR]
[COLOR=blue]Writing inode tables: done[/COLOR]
[COLOR=blue][B]Creating journal (4096 blocks): done[/B][/COLOR]
[COLOR=blue][B]Writing superblocks and filesystem accounting information: done[/B][/COLOR]
[COLOR=blue][B]This filesystem will be automatically checked every 39 mounts or[/B][/COLOR]
[COLOR=blue][B]180 days, whichever comes first. Use tune2fs -c or -i to override.[/B][/COLOR]
format /data with type ext3
Code:
mke2fs -j /dev/block/mmcblk0p26
mke2fs 1.40.8 (13-Mar-2008)
Warning: 256-byte inodes not usable on older systems
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
75200 inodes, 300799 blocks
15039 blocks (5.00%) reserved for the super user
[B]First data block=0[/B]
Maximum filesystem blocks=310378496
10 block groups
32768 blocks per group, 32768 fragments per group
7520 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
[COLOR=blue]Warning: could not read block 0: [/COLOR]
[COLOR=blue]Attempt to read block from filesystem resulted [/COLOR][COLOR=blue]in short read[/COLOR]
[COLOR=blue]Writing inode tables: done[/COLOR]
[COLOR=blue]Creating journal (8192 blocks): done[/COLOR]
[B][COLOR=blue]Writing superblocks and filesystem accounting information: done[/COLOR][/B]
[COLOR=blue][B]This filesystem will be automatically checked every 22 mounts or[/B][/COLOR]
[COLOR=blue][B]180 days, whichever comes first. Use tune2fs -c or -i to override[/B][/COLOR].
Not identical but market related to this thread http://forum.xda-developers.com/showthread.php?t=1141843
Sent from my HTC Desire S using XDA Premium App
Sorry to hear that mate, Have you tried flashing a custom recovery and format the partitions in ext4 format, cause as far as I know DS default partition format is ext4...
zorbakun said:
Sorry to here that mate, Have you tried flashing a custom recovery and format the partitions in ext4 format, cause as far as I know DS default partition format is ext4...
Click to expand...
Click to collapse
thanx for reply...
but my friend's DS shows:
Code:
/dev/block/mmcblk0p25 on /system type [B]ext3[/B] (rw,relatime,errors=continue,barrier=0,data=writeback)
/dev/block/mmcblk0p26 on /data type[B] ext3 [/B](rw,relatime,errors=continue,barrier=0,
data=writeback)
/dev/block/mmcblk0p27 on /cache type [B]ext3[/B] (rw,nodev,noatime,nodiratime,errors=co
ntinue,barrier=0,data=writeback)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,all
ow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-
ro)
Well, I'm quite sure the DS default partition format is ext4, mine is like wise ext4, you have got nothing to lose there, try to flash that customer recovery and format or convert your phone partitions to ext4, then flash any of the customs roms available around or a RUU if you want.
The easiest way to rectify is to RUU and start over. Unless you enjoy the frustration!
zorbakun said:
Well, I'm quite sure the DS default partition format is ext4, mine is like wise ext4, you have got nothing to lose there, try to flash that customer recovery and format or convert your phone partitions to ext4, then flash any of the customs roms available around or a RUU if you want.
Click to expand...
Click to collapse
thank you guys.
as i wrote above, i did RUU. and stuck at the updating screen.
could zorbakun tell me, how can i format the emmc with ext4(especially to cache)
download this Custom recovery, Flash it and there is an option to format/wipe the partitions in ext4 format or convert current ext3 to ext4, also try to flash one of the custom roms in the development section but first flash the custom recovery.
i ran fastboot oem boot, and got these info:
is there anything wrong about my cid?
Code:
... INFOsetup_tag addr=0xC0000100 cmdline add=0x8D09D070
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x28102
INFOTAG:hero panel = 0x400010
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFOTAG: PS ID = 0x0
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is empty
INFOsetting->[COLOR="Red"][B]cid::11111111[/B][/COLOR]
INFOserial number: SH*********8
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =533
INFOactive commandline: board_saga.disable_uart2=0 board_saga.us
INFOb_h2w_sw=0 board_saga.disable_sdcard=0 diag.enabled=0 board_
INFOsaga.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=
INFOtrue androidboot.pagesize=4096 androidboot.baseband=38.03.0
INFO2.15_M androidboot.[COLOR="Red"][B]cid=11111111[/B][/COLOR] androidboot.batt_poweron=goo
INFOd_battery androidboot.carrier=ALL androidboot.mid=PG88*****
INFOandroidboot.keycaps=qwerty androidboot.mode=normal androidbo
INFOot.serialno=SH*********8 androidboot.bootloader=0.98.0000 zy
INFOgote_oneshot=off msm_watchdog.enable=1 kmemleak=off no_conso
INFOle_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=devlog
INFOaARM_Partion[7].name=pdata
INFOpartition number=8
INFOValid partition num=8
INFOjump_to_kernel: machine_id(3107), tags_addr(0x4400100), kern
INFOel_addr(0x4408000)
INFO-------------------hboot boot time:80883 msec
FAILED (status read failed (Too many links))
Edit: INFOsetting->cid::11111111 means it's super cid, and super cid is good!
It's the very same thing as what happened to me, thought I haven't done deep debugging like you did and my device is S-ON. I did step 5 and my device froze at updating bootloader too. I guess there is something wrong with the phone, I'm worried about this massive market update issue. Maybe you'll be able to provide some more informations.
Also, I'm very sorry to hear this, I hope you'll be able to fix it asap, as this is very strange issue (how can market or battery pulled out brick phone???).
Numline1 said:
(how can market or battery pulled out brick phone???.
Click to expand...
Click to collapse
indeed!!!!
well, i'm kinda glad i'm not the only one with this problem... so far, the phone is still working and only sometimes crashes, so i can live with it...
i guess replacing the chip as mentioned in the first post requires sending the device to htc... would that cost anything with my xtc-clip-s-offed device? if so, how much? an estimate would be nice...
szallah said:
well, i'm kinda glad i'm not the only one with this problem... so far, the phone is still working and only sometimes crashes, so i can live with it...
i guess replacing the chip as mentioned in the first post requires sending the device to htc... would that cost anything with my xtc-clip-s-offed device? if so, how much? an estimate would be nice...
Click to expand...
Click to collapse
if ur DS is S-OFF and can't be succeed in wipe data/cache, can't mount nor open...
i did this replacement in our local-telecomm-market not htc official service.
that cost me US$60.
Same happened to me DAMMIT !!! What can i do? Tell me
All you need do is reflash Recovery and fresh install your rom. DO NOT RUN FLASH THE Nandroid BACK UP. Use PB88 the method.
Replace the chip? lol.
wait wait wait. I had a problem, that my phone wouldn't boot up after a radio flash. In recovery it said
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
I restored a nandroid backup and it booted up, with the new radio (i checked), What should i do now?
There are 2 issues that can cause these errors.
1) Messed up Partition table,
2) Broken eMMC chip (or more specifically, chip controller)
Issue 1 can be fixed by fixing the Partition table, which can be acheived by flashing an RUU.
Issue 2 cannot be fixed. (Unless you're a confident solder-er and know what you're doing, which chip to replace)
It is a hardware issue and your device will have to be returned.
Luckily, We don't know of anyone who has had an issue returning a rooted, s-off device.
There is more information in this thread, as well as how to know definatley whether you have the broken chip or not.
-Nipqer
Nipqer said:
There are 2 issues that can cause these errors.
1) Messed up Partition table,
2) Broken eMMC chip (or more specifically, chip controller)
Issue 1 can be fixed by fixing the Partition table, which can be acheived by flashing an RUU.
Issue 2 cannot be fixed. (Unless you're a confident solder-er and know what you're doing, which chip to replace)
It is a hardware issue and your device will have to be returned.
Luckily, We don't know of anyone who has had an issue returning a rooted, s-off device.
There is more information in this thread, as well as how to know definatley whether you have the broken chip or not.
-Nipqer
Click to expand...
Click to collapse
The partition table is written specifically by Recovery, therefore flashing a new Recovery should write a new partition table. As for a hardware error? I doubt if the phone would boot properly after the third of fourth time if this were the case. A hardware problem causes software errors which spreads quickly like a virus, and because there's an error, the phone gets gunked up and cannot be fixed by a wipe.
What solved the issue? I have the same problem... (
If you have the broken chip, you'll have to return it and get it replaced under warranty.
-Nipqer
Hey all, new to xda. Hope I'm not asking stupid questions.
My friend gave me a Galaxy S to fix. Model: GT-I9003.
It has a boot loop problem, cycling the Samsung introduction animation (and sound first time round). The recovery mode didn't work to start with - also trapped in a boot loop.
I followed the instructions here (using Odin3 v1.85) and flashed XXKPE. It seemed to all work fine, but the boot loop remained. I booted it into recovery mode and the following error messages appear.
E:failed to mount /data (No such file or directory)
Click to expand...
Click to collapse
and under -- Wiping data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p3
Click to expand...
Click to collapse
then
Data wipe failed.
Click to expand...
Click to collapse
From my research I believe it's a corrupted internal SD-Card and is fixed via parted? Could anyone go into more detail on how I would do this?
Many thanks.
I am facing a similar problem on my Galaxy SL... Need a solution too... I would appreciate any help...
Data partition has been corrupted, try flashing userdata.rfs with heimdall. A friend of mine had an stock/untouched phone and this happened to it, even with the corrupted partition i was able to boot cyanogenmod, and tried a lot of things, but nothing worked, it was on warranty, so i flashed back the original firmware and he took it to the service center.
If you want to try do this:
Flash bam kernel PDA_BCK_CF-root_universal_beta14fix.tar (http://forum.xda-developers.com/showthread.php?t=1355675)
Then from CWM flash cyanogenmod (i used cm7, but you can try with cm9)
after that the phone should boot into cyanogemod and give an error on the notification bar
extract the 6 files off the zip i attached and copy them to /xbin
from terminal emulator or adb shell run this for the 6 files:
Code:
chmod 0755 <file>
then run:
Code:
parted /dev/block/mmcblk0 mkfs ext2
When it asks for the partition number, enter 3
finally reboot, and if it worked you can flash a stock rom again, thats it, good luck
My phone boots up, but there are random reboots. Tried a lot of stock and custom ROMs... Nothing works... Warranty expired last week...
Thanks for your time. I appreciate it.
bruisedcrow said:
Thanks for your time. I appreciate it.
Sorry, I'm very new at this - my first hour doing this kind of thing. Could you explain the procedure in more detail - I would like to learn (make the best of a bad situation).
Am I right to say that the Bam Custom Kernel gives super-root level privileges? Allowing the CWM to fiddle with partions?
I've downloaded the normalboot.img for BCK. How do I flash this to my device? Could you link me to a tutorial?
EDIT: Alternatively could you point me to all the prerequisites I need to properly understand the problem and the methods required to fix it?
Click to expand...
Click to collapse
I tried that... My phone was booting up...
I have Android SDK on my PC... It includes some tools like ADB.
If your phone is rooted, you can use ADB to do things, like formatting...
Connected my phone. Booted into recovery. From Command Prompt, I went to ADB folder, then typed "adb shell". Then, typed in the parted command, and followed steps. Successfully done...
But the problem continues...
I have found many other users have faced this problem -- http://forum.xda-developers.com/showthread.php?t=1736118
I am disappointed. My phone is no longer in warranty... I am too late...
it is possible that using cyanogenmod and S2E (simple2ext) will work as a workaround until you send it to service center.
grab a copy of s2e and push it to /system/app/
Repartition your External-SD using the same method used for phones with low storage capacity, warning: it will erase all the data in it, so make backups
Start s2e and mark to move:
App and Private app
Applications data
Dalvik and download cache
This makes another partition, and it does not fix data, but at least you should be able to install apps.
I face this problem too. Please someone give us the solution.
Update: I flashed BAM Custom Kernel and put it in recovery mode. Attached it to the computer, but I'm stuck at this error message.
Thanks again.
More information
EDIT: There doesn't seem to be a /data partition at all! I feel I'm getting closer to fixing this.
There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.
alfrix said:
There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.
Click to expand...
Click to collapse
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?
bruisedcrow said:
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?
Click to expand...
Click to collapse
I think that the problem is when /tmp/updater.sh tries to mount /emmc your internal memory (EDIT: I've just noticed you tried with CM7, so, if I remember correctly, /emmc is the external memory, but I think that the problem is always the impossibility to mount the internal memory.) to backup your /efs directory. Because of the not avaible internal memory (/emmc) it simply exits and aborts the installation.
A simple change in updater.sh will allow you to install CyanogenMod, but wait for a confirmation from alfrix, maybe there's something more.
Anyway here there's a thread of a user with the same problem, he solved this by using the external SD as internal SD, as alfrix suggested.
strange, before touching anything try with the release i used that time (14.12.2011), if it doesn't work, then edit the updater.sh and remove
Code:
if ! /tmp/busybox mount -t ext4 /dev/block/mmcblk0p3 /data ; then
/tmp/busybox umount /data
/tmp/make_ext4fs -b 4096 -g 32768 -i 8192 -I 256 -a /data /dev/block/mmcblk0p3
fi
EDIT: is there any mmcblk on /dev/block?
Code:
ls /dev/block/
Weird the has mmcblk0 reappeared.
Code:
~ # ls /dev/block
ls /dev/block
bml0!c bml6 loop6 ram13 ram9 stl6 tfsr2
bml1 bml7 loop7 ram14 stl1 stl7 tfsr3
bml10 bml8 mmcblk0 ram15 stl10 stl8 tfsr4
bml11 bml9 mmcblk0p1 ram2 stl11 stl9 tfsr5
bml12 loop0 platform ram3 stl12 tfsr0!c tfsr6
bml13 loop1 ram0 ram4 stl13 tfsr1 tfsr7
bml2 loop2 ram1 ram5 stl2 tfsr10 tfsr8
bml3 loop3 ram10 ram6 stl3 tfsr11 tfsr9
bml4 loop4 ram11 ram7 stl4 tfsr12
bml5 loop5 ram12 ram8 stl5 tfsr13
So I tried
Code:
C:\Users\Bruised>adb shell
~ # /sbin/parted /dev/block/mmcblk0 mkfs ext2
/sbin/parted /dev/block/mmcblk0 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
/sbin/parted: invalid token: ext2
Yes/No? y
y
y
Partition number? 3
3
3
Error: Partition doesn't exist.
~ #
That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app
alfrix said:
That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
What should I try next? 14.12.2011 download link is down.
try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip
alfrix said:
try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip
Click to expand...
Click to collapse
It installs it.
Code:
Checking state of RFS/EXT4...
Install from sdcard complete.
After I reboot CM9 boot screen loads then I get "Encryption unsuccessful" as shown here
After rebooting I get
Code:
CWM-based Recovery v5.5.0.4
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p3
Formatting /cache...
Data wipe failed.
Heres the log file from the sdcard:
Code:
+ /tmp/busybox test -e /sdcard/backup/efs/nv_data.bin
+ /tmp/busybox mount -t ext4 /dev/block/stl9 /system
+ /tmp/busybox mount -t ext4 /dev/block/stl10 /dbdata
+ /tmp/busybox mount -t ext4 /dev/block/stl11 /cache
+ /tmp/busybox umount -l /system
+ /tmp/busybox umount -l /cache
+ /tmp/busybox umount -l /data
umount: can't forcibly umount /data: Invalid argument
+ /tmp/busybox umount -l /dbdata
+ /tmp/busybox umount -l /efs
umount: can't forcibly umount /efs: Invalid argument
+ exit 0
Ever wanted to try a new rom without having to waste our time on making backups then trying the rom and then again restoring it, and if another rom pleases you at the moment , you'll have to perform the same drill again and again ... Well Now NO MORE of this frustrating business.
Here i present you my very own method of Dual Booting almost ANY two roms you like on YOUR device.
But make sure to try at your risk.. as per DoomLord many devices can be hardbricked too.
Do Not use this method
on newer (post 2012) qualcomm chipsets the TA and Bootloader, reside on similar partitions... if u screw with these partitions device gets HARD BRICKED!
As the partition maps vary from device to device it may not work for you and you may get your device hard bricked!
Also your device must use older bootloader bypass based kernels i.e boot.img format and has SD-card slots for this method to work !!
Before we begin here's what Dual Booting means :
- Dual booting is the process through which you can switch between any two or more roms without the need of wiping data or making backups before flashing ,all you need to do is switch between the roms ,meanwhile all the apps you've insatlled remain intact in their specific rom.
for ex- If you are using cm10 and you have installed a lot of apps, and you want to test other rom ,but you don't want the fuss of backing up then flashing.. This dual booting method is for you !!
So to begin with make sure you meet the following prerequisites :
Your Device which can run android
an class 6 or above SD-Card
an Os on the PC to make partitions on the SD-card
ubuntu for kernel specific changes
notepad ++
ConCentRation
If you meet all the above requirements you are good to go
Now to Before we get our hand in the filth remember : You need to have and an SD-Card that's class 6 or above because we would be using it extensively , and slow cards may not keep up
SO LET'S ROLL :
In this method [/CENTER]
Primary Rom = The rom which is modded and remains on the Sd-ext partitons
Secondary Rom = any rom you wish (any android version for ex- cm9 , cm10.1 and even stock !) [ make sure that the secondary rom doesn't use sd-ext partitions]
I would be dividing the process in tow steps : 1) Kernel level changes and 2)SD-card and Rom level changes
1- Kernel Level Changes :
Get the source of any kernel for your device (if you don't know what's kernel compilation you can go to xda-university to learn it.)
-Now open the defconfig file (usually present in : "arch/arm/config" -folder)
-Search for LBDAF and then change the line consisting it as follows :
Code:
CONFIG_LBDAF=y
and now compile the kernel
This is done so that our Primary Rom can support multiple SD-ext partitons
-Now grab the boot.img of your Primary Rom , unpack it using any tool of your convenience(Google : chanpionwimmer's kernel tools -- i use it ) now open the ramdisk part , then open init.rc
-Search for the rom's mounting functions it will be like:
Code:
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
it will vary from device to device.. proceed only if you know the correct mount points for your device.. otherwise you WILL hardbrick your device
-Now replace the following lines from the mounting functions to this Make sure you know the correct mount points of your device :
Code:
# Mount SD-SYSTEM
wait /dev/block/mmcblk0p2
wait /dev/block/mmcblk0p2
wait /dev/block/mmcblk0p2
wait /dev/block/mmcblk0p2
mount ext4 /dev/block/mmcblk0p2 /system
mount ext4 /dev/block/mmcblk0p2 /system ro remount
# Mount SD-DATA
wait /dev/block/mmcblk0p3
wait /dev/block/mmcblk0p3
wait /dev/block/mmcblk0p3
wait /dev/block/mmcblk0p3
mount ext4 /dev/block/mmcblk0p3 /data nosuid nodev noatime nodiratime barrier=0 data=ordered commit=15 noauto_da_alloc nouser_xattr errors=continue
# Mount SD-CACHE
wait /dev/block/mmcblk0p4
wait /dev/block/mmcblk0p4
wait /dev/block/mmcblk0p4
wait /dev/block/mmcblk0p4
mount ext4 /dev/block/mmcblk0p4 /cache nosuid nodev noatime nodiratime barrier=0 data=ordered commit=15 noauto_da_alloc nouser_xattr errors=continue
-Now recompile the kernel and you are good to go
more in the 2nd post ..
Here now comes the SD-Card and Rom level changes :
YOU MUST USE ATLEAST CLASS 6 OR ABOVE SDCARD WITH MINIMUM 8GB CAPACITY
First you need 3 EXT4 partitions on SD-card, using minitool partition wizard
1) around 400 MB - SD-SYSTEM (ext4)
2) around 1 GB (or can be less) - SD-DATA(ext4 format),
3)around 75MB (can be less) SD-CACHE(ext4 format) (refer to the screenshot):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rom level changes :
Get the updater-script of your Primary rom and find for these lines (Will differ from device to device - but basically the format is same )
Code:
format("yaffs2", "MTD", "system", "0", "/system");
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system");
Now replace it with :
Code:
run_program("/sbin/busybox", "mount", "-t", "auto", "/dev/block/mmcblk0p2", "/system");
run_program("/sbin/busybox", "rm", "-rf", "/system/*");
package_extract_dir("system", "/system");
-what we are doing here is extracting the sustem files to the sd-ext partition we just created earlier
save it and replace this updater-script in the original Primary rom and also replace the boot.img with the one you made earlier.
That's it.If you have followed the guide correctly you can Dual boot any Rom on your device
Now flash the primary rom first.. and then any rom you choose as the secondary rom (PROVIDED IT DOESN"T USE SD-Ext partitions..) and flash it
REMEMBER DO NOT wipe data before installing the secondary rom
If you want to change your secondary rom DO NOT WIPE DATA instead goto recovery -
if in CWM or philz -go to mounts and storage and format system , data and cache
For Switching roms :
-put the boot.img of primary rom in the root of your sd-card(not in any directory) reanme it primary.img
-put the boot.img of secondary rom in the root of your sd-card(not in any directory) reanme it sec.img
-get terminal emulator app
-type
Code:
su
flash_image boot /sdcard/primary.img (or secondary.img)
But STOP here are some restrictions of this method :
You must make sure your device uses boot.img format and you know your device's correct mount points !! if you do it wrong you WILL hard brick your device !!
1. For The secondary rom you CANNOT use scripts like int2ext, etc.
2. Also you CANNOT use pll2 OC method in Secondary ROM
3. The edited cm10beta 6 (primary rom) is clocked at 600mhz, so NO chances of burnt nand.
4. You can choose ANY rom as secondary ROM provided it does not violate the first 2 clauses, that is, it should not use sd-ext partitions
5. The process is only for people having class 6 or higher sd card.
PS : This has taken a lot of effort and time so please don't go on commenting "This is useless" , "i don't like it" ,etc. If you don't like it, you are free to leave.
<JohnCarter> said:
...
-Now grab the boot.img of your Primary Rom , unpack it using any tool of your convenience(Google : chanpionwimmer's kernel tools -- i use it ) now open the ramdisk part , then open init.rc
-Search for the rom's mounting functions it will be like:
Code:
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
it can vary from device to device..
-Now replace the following lines from the mounting functions to this :
Code:
# Mount SD-SYSTEM
wait /dev/block/mmcblk0p2
wait /dev/block/mmcblk0p2
wait /dev/block/mmcblk0p2
wait /dev/block/mmcblk0p2
mount ext4 /dev/block/mmcblk0p2 /system
mount ext4 /dev/block/mmcblk0p2 /system ro remount
# Mount SD-DATA
wait /dev/block/mmcblk0p3
wait /dev/block/mmcblk0p3
wait /dev/block/mmcblk0p3
wait /dev/block/mmcblk0p3
mount ext4 /dev/block/mmcblk0p3 /data nosuid nodev noatime nodiratime barrier=0 data=ordered commit=15 noauto_da_alloc nouser_xattr errors=continue
# Mount SD-CACHE
wait /dev/block/mmcblk0p4
wait /dev/block/mmcblk0p4
wait /dev/block/mmcblk0p4
wait /dev/block/mmcblk0p4
mount ext4 /dev/block/mmcblk0p4 /cache nosuid nodev noatime nodiratime barrier=0 data=ordered commit=15 noauto_da_alloc nouser_xattr errors=continue
..
Click to expand...
Click to collapse
PLEASE DONT POST INCORRECT INFORMATION!
the partition maps vary from device to device!
on newer (post 2012) qualcomm chipsets the TA and Bootloader, reside on similar partitions... if u screw with these partitions device gets HARD BRICKED!
also not all devices use standard boot.img format...
if u were able to get it to work on a particular device atleast test it out on 8-10 different devices from different vendors and different platforms before posting such threads...
DooMLoRD said:
PLEASE DONT POST INCORRECT INFORMATION!
the partition maps vary from device to device!
on newer (post 2012) qualcomm chipsets the TA and Bootloader, reside on similar partitions... if u screw with these partitions device gets HARD BRICKED!
also not all devices use standard boot.img format...
if u were able to get it to work on a particular device atleast test it out on 8-10 different devices from different vendors and different platforms before posting such threads...
Click to expand...
Click to collapse
I truly second that. The information on this thread is valid only for some devices. You can seriously screw a number of devices.
DooMLoRD said:
PLEASE DONT POST INCORRECT INFORMATION!
the partition maps vary from device to device!
on newer (post 2012) qualcomm chipsets the TA and Bootloader, reside on similar partitions... if u screw with these partitions device gets HARD BRICKED!
also not all devices use standard boot.img format...
if u were able to get it to work on a particular device atleast test it out on 8-10 different devices from different vendors and different platforms before posting such threads...
Click to expand...
Click to collapse
Ok thanks for the info... i'll give a caution for not using this method on newer devices
Device: Teclast P78HD tablet, Allwinner A31 SoC, Android 4.4.2 (rooted) :::: Software: Busybox X (with fdisk, vi, etc.)
The Teclast P78HD tablet has a small 8GB internal eMMC SDcard with an external microSD slot. In order to best make use of the Link2SD utility, I chose to split in half the almost empty 4.7GB (usable) internal SD FAT32 partition and then format the new (primary) second partition to EXT2 EXT3 or EXT4 as used by the Link2SD app.
I used Busybox X to fdisk /dev/block/mmcblk0 ( /mnt/sdcard )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After rebooting, the DiskInfo app showed P1 ( mmcblk0p1 ) partition had shrunk to 2.4GB and, as expected, a new (unmounted) 2.3GB P4 ( mmblk0p4 , type 83, Linux ) was there too.
Connecting to a PC vis USB, I tried to format P4 to ext4 using MiniTool Partitioner (Windows) but it did not see the new partition, I then tried Gparted under Linux but it indicated that neither P1 or P4 existed. Gparted just showed a large 4.7GB "unallocated" block.
[ QUESTIONS ]
1. How do I format the new P4 mmblk0p4 partition to EXT4 using Busybox X on the tablet itself ?
2. Should I use some sort of fsck command to fix any side effects of simply truncating the original P1 mmblk0p1 FAT32 partition ?
3. What entry should I add to the tablet's /fstab.sun6i file shown below to make it automount at boot time ?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/by-name/system /system ext4 ro wait
/dev/block/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1 wait,check
/dev/block/by-name/databk /databk ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1 wait,check
/dev/block/by-name/data /data ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1,noauto_da_alloc wait,check,encryptable=/dev/block/by-name/databk
/devices/virtual/block/nandj /mnt/sdcard vfat rw,relatime,fmask=0000,dmask=0000 wait,check,noemulatedsd,voldmanaged=sdcard:auto
/devices/platform/sunxi-mmc.2/mmc_host /mnt/sdcard vfat rw,relatime,fmask=0000,dmask=0000 wait,check,noemulatedsd,voldmanaged=sdcard:auto
/devices/platform/sunxi-mmc.0/mmc_host /mnt/extsd vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=extsd:auto
/devices/platform/sunxi-mmc.1/mmc_host /mnt/extsd vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=extsd:auto
/devices/platform/sw-ehci.1 /mnt/usbhost1 vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=usbhost1:auto
/devices/platform/sw_hcd_host0 /mnt/usbhost1 vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=usbhost1:auto
/devices/platform/sw-ohci.1 /mnt/usbhost1 vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=usbhost1:auto
BTW, despite the tablet's fstab entries, there is no /devices/platform directory but there is a /sys/devices/platform directory. Also note that sdcard0 and sdcard1 seem to point to the same place with the same files. I assume that my new partition should point to /storage/sdcard2
Did you ever figure it out? Thinking about splitting my internal storage and looking up for all the info I can find....
Hi
I've cm-11-20150607-NIGHTLY-i9100 on my Samsung Galaxy SII i9100
It has gapps-kk-20140105-signed (as far as I remember).
I do have cwm 6.0.5.1
Two days ago, there was some update (haven't seen what exactly).
Now, while booting the phone hangs on the boot screen.
When I lunch into cwm-recovery I do see:
CWM-based Revocery v6.0.5.1
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
The show log says:
mount: mounting /dev/block/mmcblk0p7 on /cache failed: Invalid argument
W: failed to mount /dev/block/mmcblk0p7 (File exist)
E:Can't mount /cache/recovery/log
(and more like this)
...
I do have MTP enabled, and debugging USB disabled- this is a big problem since i can not access adb...
I would like to backup data, but how can I enable adb from cwm?
I did try to wipe dalvik (I think it did work) /format cache - It does not work - it hangs.
I did try to "reboot to receovery (or reboot to bootloader): from the cwm- it hangs
I did try to mount /storage/sdcard0 - it hangs
I did try to create a backup from phone memory to scracd1 - it hangs
I can boot into fastboot.
It looks like some error on partition, or problem with internal phone memory.
Anything that try to access internal sdcard0 hangs
How can I backup the phone (or at lest photo - not all were synced yet).
What would be the next step?
Any idea howto enable USB debugging?
I've seen this tutorial
(can add a link so google "enable usb debbuging through clockworkmod with adb")
but it is for the Nexus, not for the i9100...
I do have Ubuntu, with
adb version 1.0.31
I can switch to Windows if it would help...
Ok,
For the moment, I made the wrong assumption.
I can access adb.
The solution was to install latest android SDK (cm11 is some like Android 4.4.4) to get newest adb
(developer.android com/sdk/installing/index.html?pkg=studio )
To be clear, if you're having this same issue the problem is probably an out-of-date SDK. As of 4.2.2 there is a security feature that requires you to confirm the RSA fingerprint of the connecting device. Open the SDK manager and update the tools! Then reboot. - quote from stackoverflow com/questions/14993855/android-adb-device-offline-cant-issue-command
Click to expand...
Click to collapse
stackoverflow com/questions/14993855/android-adb-device-offline-cant-issue-commands
and
having Enabled ADB Integration via Tools > Android > Enable ADB Integration
stackoverflow com/questions/26079838/android-studio-adb-error-device-unauthorized-please-check-the-confirmat
Now I can access
adb shell (while booting into cwm recovery - Power+volUp+Home)
Code:
# parted /dev/block/mmcblk0 print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 159MB 105MB CACHE
8 159MB 176MB 16.8MB MODEM
9 176MB 713MB 537MB FACTORYFS
10 713MB 2861MB 2147MB DATAFS
11 2861MB 15.2GB 12.4GB UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
~ # cat /etc/fstab
/dev/block/mmcblk0p7 /cache ext4 rw
/dev/block/mmcblk0p10 /data ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
~ # mount -o ro -t ext4 /dev/block/mmcblk0p10 /data
mount: mounting /dev/block/mmcblk0p10 on /data failed: Invalid argument
The problem is - I can not backup the data nor mount the /data partition
Sir,
This forum is for helping new users to help members navigate the site, not for support.
I see you've found your device section and already know how things work on XDA.
So please note the sticky from the top of the Assist section and ask directly in this thread for I9100:
[Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread
Good luck