ı did same but now still freeze how should i do this can u please step by step guide me
Last edited:
Anyone feels genuine happiness around here or it's just me?
Great work, must read it all.:thumbup:
its become my nightmare waiting when phone will be freezeeeeeeeeeee omgggggg somebody help
thanks for reading ! when you spare time, you can do it. now i using ics 4.0.4. when you made it, i will trying upgrade my phone. hope will success! thank you so much!: Good:: Good:: Good:
hey man, seems I am not talking very clear...
--> the package is already there, it's called i9100_jb4.1 <--
I am only talking about it's name.
Just get this incorrectly named package for now.
May be, I rename it at the weekend.
Did u pay for tb how did u get hyper shell
Sent from my GT-N7000 using xda app-developers app
I have Modem partition brick on my D710 epic 4g touch..
Plz help
My phone is in a condition that is completely described here: http://xdaforums.com/showthread.php?p=38380591#post38380591 DL mode only is availbe and no recovery.
So i think that this guide:http://xdaforums.com/showpost.php?p=26285877&postcount=12 can really help me. But i'm really not sure if it is safe to flash those PITs cause my device is SGSII, not the NOTE.
Can u give me any advice in my situation?
"P6200_tabplus--patched--brick-between-01086-and-03233-MB--DATAFS-moved-by-02048-MiB"
Both have revived my tab, but it last only for one or two days. Then I star having troubles, automatic factory reset and then death again.
You may have got a moving brick or may be it moves for some time until it finally gets stable.
You should scan again to get the new limits of the brick (if it has moved at all). Then use a new pit.
And it keeps failling after two or three days of use.
Maybe I need a more specific pit file.
getting closer to the brick area will not help.
I think I would try a bigger gap, that is increase the second number (end of gap) by some GB.
E.g. you could try an end of around 5000MB, let's see if this behaves different.
SamantaSync said:Can you make me a .pit file for recovering emmc error from 860 MB to 2148 MB. I want to reduce the memory lost as much as possible.. because the pit file I use for recovering make my memory only 7 GB left :/
before: ...-|-FAC?OR??S-|??ATAFS-|-UMS------------------------------------|...
^ ^
| |
BRICK_START BRICK_END
(? = bad blocks)
before: ...-|-FAC?OR??S-|??ATAFS-|-UMS------------------------------------|...
after: ...-| ? ?? ??|-FACTORYFS-|-DATAFS-|-UMS---------------------|...
\ /
------+-----
|
HOLE
(? = bad blocks)
16GB original (Q1_20110914_16GB.pit)
FACTORYFS 548864 ->Fo 1744896 ->Fs
DATAFS 2293760 ->Do 4194304 ->Ds
UMS 6488064 ->Uo 23232512 ->Us
HIDDEN 29720576 ->Ho 1048576 ->Hs
16GB MMC_CAP_ERASE patched
FACTORYFS FoX = Fo+X unchanged
DATAFS DoX = Do+X unchanged
UMS UoX = Uo+X UsX = Us-X
HIDDEN unchanged unchanged
case FACTORYFS-moved-by-...
before: ...-|-FAC?OR??S-|??ATAFS-|-UMS------------------------------------|...
after: ...-| ? ?? ??|-FACTORYFS-|-DATAFS-|-UMS---------------------|...
\ /
------+-----
|
HOLE
case DATAFS-moved-by-...
before: ...-|-FACTORYFS-|D??T?FS-|-UMS------------------------------------|...
after: ...-|-FACTORYFS-| ?? ?|-DATAFS-|-UMS------------------------------|...
\ /
-+-
|
HOLE
(? = bad blocks)
dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard/efs.img
This failed, because to find out which blocks are bad, e2fsck tries to read them and gets stuck by doing so.e2fsck -c /dev/block/mmcblk0p9 (which is the /system partition)
before: - ...-|-FAC?ORYFS-|??ATAFS-|-UMS------------------------------------|...
after: + ...-| ? ?? |-FACTORYFS-|-DATAFS-|-UMS---------------|...
(? = bad blocks, + working, - = not working still bad blocks inside)
I managed to access the device via [I]adb shell[/I]...which is another story for itself...
Then I started [I]parted[/I] with the flash device:
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
As a greeting I got some error messages about the GPT layout, which parted wanted to fix:
[QUOTE]Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 2048 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
this was the partition scheme before implementing the workaround:
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 ext4 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 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1174MB 893MB FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
then I deleted the partitions 9=FACTORYFS=/system, 10=DATAFS=/data and 11=UMS=/sdcard(internal) and recreated them starting at the former start of the internal sdcard partition (11) leaving the former space of the /system and /data partitions unused:
(parted) rm 11
(parted) rm 10
(parted) rm 9
(parted) mkpartfs primary ext2 3500 4400
(parted) mkpartfs primary ext2 4400 7000
(parted) mkpartfs primary fat32 7000 15.2G
(parted) name 9 FACTORYFS
(parted) name 10 DATAFS
(parted) name 11 UMS
now I upgraded both new ext2 partitions to ext4:
~ # tune2fs -j /dev/block/mmcblk0p9
tune2fs -j /dev/block/mmcblk0p9
tune2fs 1.41.11 (14-Mar-2010)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
~ # tune2fs -j /dev/block/mmcblk0p10
tune2fs -j /dev/block/mmcblk0p10
tune2fs 1.41.11 (14-Mar-2010)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
~ # e2fsck -fDp /dev/block/mmcblk0p9
e2fsck -fDp /dev/block/mmcblk0p9
/dev/block/mmcblk0p9: 11/439776 files (0.0% non-contiguous), 71701/878907 blocks
~ # e2fsck -fDp /dev/block/mmcblk0p10
e2fsck -fDp /dev/block/mmcblk0p10
/dev/block/mmcblk0p10: 11/317440 files (9.1% non-contiguous), 26386/634765 blocks
and this is the final partition layout:
~ # parted /dev/block/mmcblk0 print
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 ext4 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 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 3500MB 4400MB 900MB ext3 FACTORYFS
10 4400MB 7000MB 2600MB ext3 DATAFS
11 7000MB 15.2GB 8217MB fat32 UMS msftres
12 15.2GB 15.8GB 537MB ext4 HIDDEN
This configuration works so far (one complete day now).
I can install firmwares and restore backups via recoveries.
Also flashing via Odin should work (not tried yet).
I currently can only imagine one standard procedure which will not work, that is creating a new partition scheme, e.g. via Odin (PIT file) or may be a CWM script.
I think/hope this will not occur too often...
Flashed your pit.
Flashed SGN_XX_OXA_KJ1_FACTORYFS.tar worked no stuck on NAND Write.
Flashed CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5.tar
Installed XXLC1_CheckROM_NoteHD_V6.zip using CWM.
Stucked at Wizard, retried a couple of times and passed wizard.
Now everything Force Closed, after some minutes manages to go to Settings > Privacy > Factory Data Reset
Check Format USB Storage
i only have 8 Gb internal space.
Is there a way i can revert my phone to original state, fix the bad blocks and have 12 gb internal space like before???
don't update youtube from play store, bcoz the update will FC
a lil laggy.