Anyone know how to resolve this issue whereby I'm unable to do anything with the internal storage? As best I can tell, I just can't write to it anymore (some kind of corruption). Every time I turn the device on, it reverts back to the state it was in a few days ago when this started. Everything starts to FC because it can't write to the internal storage. I tried Odin to stock, it completes to success (green and everything), but when it restarts it's as if nothing happened. Same story with a CWM flash. Wipe/Factory Reset says success, but it's clear it isn't doing anything as it flies through it too quickly. Nandroid restore no good. Odin one-click no good. Format of system data or cache completes, but again clearly not doing anything as it happens too fast. ADB Shell coupled with e2fsck gives me an error about the superblock, and checking the CWM recovery log, I see something about wipe_block_device: Discard failed.
Any suggestions on what else I could try?
That sounds worse than a brick
jeff210 said:
That sounds worse than a brick
Click to expand...
Click to collapse
Indeed, the damned device is mocking me. "Haha! I'm ALIVE, but I'm USELESS!"
Just a stupid question but did you happen to install any antivirus/firewall program on your phone?
Also are there any device administrator on your phone other than your own? ie. Device admin from exchange server etc. Sometime those can lock-down your phone preventing any kind of data wipe.
icce007 said:
Just a stupid question but did you happen to install any antivirus/firewall program on your phone?
Also are there any device administrator on your phone other than your own? ie. Device admin from exchange server etc. Sometime those can lock-down your phone preventing any kind of data wipe.
Click to expand...
Click to collapse
Thanks for the suggestion, but no - no firewall/antivirus, and no device administrators that are active. Good question, though. Besides, I don't think any of those would be able to prevent an Odin, would they?
Well, I tried everything and it just won't take. Looks like it's back to the Nexus for me I'll keep it around in case an eventual fix is identified.
EDIT: This output doesn't look right. Any thoughts on how I can clear this table up?
Code:
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15756951552 bytes
1 heads, 16 sectors/track, 1923456 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 92 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 1923584 15284271+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 13313 13375 500 47 Unknown
/dev/block/mmcblk0p6 13825 14080 2048 45 Unknown
/dev/block/mmcblk0p7 14337 14649 2500 4c Unknown
/dev/block/mmcblk0p8 14849 16128 10240 48 Unknown
/dev/block/mmcblk0p9 16385 16447 500 46 Unknown
/dev/block/mmcblk0p10 16897 16959 500 5d Unknown
/dev/block/mmcblk0p11 17409 17471 500 91 Unknown
/dev/block/mmcblk0p12 17921 19200 10240 93 Unknown
/dev/block/mmcblk0p13 19457 32000 100352 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p14 32257 32640 3072 4a Unknown
/dev/block/mmcblk0p15 32769 33152 3072 4b Unknown
/dev/block/mmcblk0p16 33281 33664 3072 58 Unknown
/dev/block/mmcblk0p17 33793 46336 100352 8f Unknown
/dev/block/mmcblk0p18 46593 46976 3072 59 Unknown
/dev/block/mmcblk0p19 47105 47488 3072 5a Unknown
/dev/block/mmcblk0p20 47617 48000 3072 5b Unknown
/dev/block/mmcblk0p21 48129 49408 10240 ab Darwin boot
/dev/block/mmcblk0p22 49665 50944 10240 60 Unknown
/dev/block/mmcblk0p23 51201 52480 10240 94 Unknown
/dev/block/mmcblk0p24 52737 183808 1048576 a5 FreeBSD
/dev/block/mmcblk0p25 183809 446208 2099200 a6 OpenBSD
/dev/block/mmcblk0p26 446465 485120 309248 a8 Darwin UFS
/dev/block/mmcblk0p27 485377 501888 132096 a9 NetBSD
/dev/block/mmcblk0p28 502273 1923584 11370496 90 Unknown
Also, I tried playing around with parted to see if I can repartition the device, but it keeps complaining about "Can't have a partition outside the disk!"
I saw someone else have a similar problem with a different Samsung phone and they were able to get things working again by using Odin and the repartition option with a PIT file. I tried searching for the PIT file that goes with the i717 and I'm not getting any useful hits. Anyone know if such a beast exists?
As I posted previously about flashing issues and errors which came up with my device I've learned that my partitions were corrupted and nearly all were erased. With some help from developer Mev and other members I was able to get my device working with ADB shell yet the commands seemed to be far out of my lead.
I have an YP-G70 USA (8 Gigs) device.
From what I learned this is the partition to the device, yet the start/ending blocks aren't listed. Would that be a problem?
Code:
Device Size (KiB) Mount Name Notes
/dev/block/mmcblk0 7757824 Internal eMMC disk device
/dev/block/mmcblk0p1 1 Extended partition containing everything else
/dev/block/mmcblk0p5 256 boot.bin Initial+Primary Bootloaders
/dev/block/mmcblk0p6 256 YPG70_8G-0304.pit Partition Information Table
/dev/block/mmcblk0p7 1280 Sbl.bin Secondary Bootloader
/dev/block/mmcblk0p8 1280 Sbl.bin SBL backup
/dev/block/mmcblk0p9 5120 /mnt/.lfs param.lfs param.blk and boot logos - source of recovery loops
/dev/block/mmcblk0p10 10240 /efs efs.rfs WiFi and BT MAC addresses - causes missing lockscreen
/dev/block/mmcblk0p11 7680 zImage Kernel
/dev/block/mmcblk0p12 7680 zImage "Recovery" kernel that is never used
/dev/block/mmcblk0p13 296960 /system factoryfs.rfs System partition
/dev/block/mmcblk0p14 137216 /dbdata dbdata.rfs Various Android/app databases
/dev/block/mmcblk0p15 65536 /cache cache.rfs Cache partition
/dev/block/mmcblk0p16 1970176 /data datafs.rfs Data partition (apps and their data)
/dev/block/mmcblk0p17 5252096 /sdcard userfs_8G.rfs "Emmc" "Usb Storage" - where your media goes
/dev/block/mmcblk1 <varies> External SD Card disk device
/dev/block/mmcblk1p1 <varies> /sdcard/external_sd External SD Card partition
Next thing is, whenever I tried using
Code:
fdisk /dev/block/mmcblk0
and later on creating a prime partition within the settings that I try to use the "e" to extend (says nothing about "l" for logical) which I run out of sectors to create them with. And sadly the only ones that ever come up is mmcblk0p4 or mmcblk0p3.
Just looking for help to get my player back up and running .. it's all I have and use at work since I don't have a phone and really have been trying to get this to work but its difficult so im sorry for bothering..
I don't know what to do after this:
Jistropy said:
As I posted previously about flashing issues and errors which came up with my device I've learned that my partitions were corrupted and nearly all were erased. With some help from developer Mev and other members I was able to get my device working with ADB shell yet the commands seemed to be far out of my lead.
I have an YP-G70 USA (8 Gigs) device.
From what I learned this is the partition to the device, yet the start/ending blocks aren't listed. Would that be a problem?
Code:
Device Size (KiB) Mount Name Notes
/dev/block/mmcblk0 7757824 Internal eMMC disk device
/dev/block/mmcblk0p1 1 Extended partition containing everything else
/dev/block/mmcblk0p5 256 boot.bin Initial+Primary Bootloaders
/dev/block/mmcblk0p6 256 YPG70_8G-0304.pit Partition Information Table
/dev/block/mmcblk0p7 1280 Sbl.bin Secondary Bootloader
/dev/block/mmcblk0p8 1280 Sbl.bin SBL backup
/dev/block/mmcblk0p9 5120 /mnt/.lfs param.lfs param.blk and boot logos - source of recovery loops
/dev/block/mmcblk0p10 10240 /efs efs.rfs WiFi and BT MAC addresses - causes missing lockscreen
/dev/block/mmcblk0p11 7680 zImage Kernel
/dev/block/mmcblk0p12 7680 zImage "Recovery" kernel that is never used
/dev/block/mmcblk0p13 296960 /system factoryfs.rfs System partition
/dev/block/mmcblk0p14 137216 /dbdata dbdata.rfs Various Android/app databases
/dev/block/mmcblk0p15 65536 /cache cache.rfs Cache partition
/dev/block/mmcblk0p16 1970176 /data datafs.rfs Data partition (apps and their data)
/dev/block/mmcblk0p17 5252096 /sdcard userfs_8G.rfs "Emmc" "Usb Storage" - where your media goes
/dev/block/mmcblk1 <varies> External SD Card disk device
/dev/block/mmcblk1p1 <varies> /sdcard/external_sd External SD Card partition
Next thing is, whenever I tried using
Code:
fdisk /dev/block/mmcblk0
and later on creating a prime partition within the settings that I try to use the "e" to extend (says nothing about "l" for logical) which I run out of sectors to create them with. And sadly the only ones that ever come up is mmcblk0p4 or mmcblk0p3.
Just looking for help to get my player back up and running .. it's all I have and use at work since I don't have a phone and really have been trying to get this to work but its difficult so im sorry for bothering..
I don't know what to do after this:
Click to expand...
Click to collapse
You should have created that as an extended partition, not primary. Then go through and create new partitions "n"
I apologize for not giving you quite the right information. I know there's a table here with starting and ending blocks.
For illustration, here's an example of what to enter at the prompts. IGNORE THE BLOCK NUMBERS - it's just an illustration; just notice the extended/logical and the partition numbers.
Code:
[[email protected] ~]$ fdisk mmcblk0
Welcome to fdisk (util-linux 2.22.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Device does not contain a recognized partition table
Building a new DOS disklabel with disk identifier 0xab3ebd8d.
Command (m for help): n
Partition type:
p primary (0 primary, 0 extended, 4 free)
e extended
Select (default p): e
Partition number (1-4, default 1):
Using default value 1
First sector (2048-102399, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-102399, default 102399):
Using default value 102399
Partition 1 of type Extended and of size 49 MiB is set
Command (m for help): p
Disk mmcblk0: 52 MB, 52428800 bytes, 102400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xab3ebd8d
Device Boot Start End Blocks Id System
mmcblk0p1 2048 102399 50176 5 Extended
Command (m for help): n
Partition type:
p primary (0 primary, 1 extended, 3 free)
l logical (numbered from 5)
Select (default p): l
Adding logical partition 5
First sector (4096-102399, default 4096):
Using default value 4096
Last sector, +sectors or +size{K,M,G} (4096-102399, default 102399): 16383
Partition 5 of type Linux and of size 6 MiB is set
Command (m for help): p
Disk mmcblk0: 52 MB, 52428800 bytes, 102400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xab3ebd8d
Device Boot Start End Blocks Id System
mmcblk0p1 2048 102399 50176 5 Extended
mmcblk0p5 4096 16383 6144 83 Linux
Command (m for help): n
Partition type:
p primary (0 primary, 1 extended, 3 free)
l logical (numbered from 5)
Select (default p): l
Adding logical partition 6
First sector (18432-102399, default 18432):
Using default value 18432
Last sector, +sectors or +size{K,M,G} (18432-102399, default 102399):
Using default value 102399
Partition 6 of type Linux and of size 41 MiB is set
Command (m for help): p
Disk mmcblk0: 52 MB, 52428800 bytes, 102400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xab3ebd8d
Device Boot Start End Blocks Id System
mmcblk0p1 2048 102399 50176 5 Extended
mmcblk0p5 4096 16383 6144 83 Linux
mmcblk0p6 18432 102399 41984 83 Linux
Command (m for help): w
The partition table has been altered!
Syncing disks.
[[email protected] ~]$
Awe man thank you!! Going to try this out right now I felt bad for messaging you.
Give me like 15 minutes.
Those cover three of the partitions, how do I go about making the rest?
Jistropy said:
Awe man thank you!! Going to try this out right now I felt bad for messaging you.
Give me like 15 minutes.
Those cover three of the partitions, how do I go about making the rest?
Click to expand...
Click to collapse
Just keep going:
Code:
n (new)
l (logical)
<enter> (beginning)
+blocks (size)
and then
Code:
p (print)
to check your work, and
Code:
w (write)
to save changes and exit.
The Block sizes don't matter right?
Jistropy said:
The Block sizes don't matter right?
Click to expand...
Click to collapse
They matter very much. Use the ones from the device. The above was to illustrate the process. It has entirely wrong numbers.
I will have to repeat this process after doing the extended partition:
Code:
Command (m for help): n
Partition type:
p primary (0 primary, 1 extended, 3 free)
l logical (numbered from 5)
Select (default p): l
So what do I do with these?
Code:
First sector (18432-102399, default 18432):
Using default value 18432 (DONT FILL ?)
Last sector, +sectors or +size{K,M,G} (18432-102399, default 102399):
Using default value 102399 (DONT FILL ?)
Should I fill in those with this?
Code:
Device Size (KiB) Mount
/dev/block/mmcblk0 7757824
/dev/block/mmcblk0p1 1
/dev/block/mmcblk0p5 256
/dev/block/mmcblk0p6 256
/dev/block/mmcblk0p7 1280
/dev/block/mmcblk0p8 1280
/dev/block/mmcblk0p9 5120
/dev/block/mmcblk0p10 10240
/dev/block/mmcblk0p11 7680
/dev/block/mmcblk0p12 7680
/dev/block/mmcblk0p13 296960
/dev/block/mmcblk0p14 137216
/dev/block/mmcblk0p15 65536
/dev/block/mmcblk0p16 1970176
/dev/block/mmcblk0p17 5252096
/dev/block/mmcblk1 <varies>
/dev/block/mmcblk1p1 <varies>
Also, how do I do the last two? Just testing things I don't have the numbers so im randomly copying and pasting the number sets.
Jistropy said:
I will have to repeat this process after doing the extended partition:
Code:
Command (m for help): n
Partition type:
p primary (0 primary, 1 extended, 3 free)
l logical (numbered from 5)
Select (default p): l
So what do I do with these?
Code:
First sector (18432-102399, default 18432):
Using default value 18432 (DONT FILL ?)
Last sector, +sectors or +size{K,M,G} (18432-102399, default 102399):
Using default value 102399 (DONT FILL ?)
Should I fill in those with this?
Code:
Device Size (KiB) Mount
/dev/block/mmcblk0 7757824
/dev/block/mmcblk0p1 1
/dev/block/mmcblk0p5 256
/dev/block/mmcblk0p6 256
/dev/block/mmcblk0p7 1280
/dev/block/mmcblk0p8 1280
/dev/block/mmcblk0p9 5120
/dev/block/mmcblk0p10 10240
/dev/block/mmcblk0p11 7680
/dev/block/mmcblk0p12 7680
/dev/block/mmcblk0p13 296960
/dev/block/mmcblk0p14 137216
/dev/block/mmcblk0p15 65536
/dev/block/mmcblk0p16 1970176
/dev/block/mmcblk0p17 5252096
/dev/block/mmcblk1 <varies>
/dev/block/mmcblk1p1 <varies>
Also, how do I do the last two? Just testing things I don't have the numbers so im randomly copying and pasting the number sets.
Click to expand...
Click to collapse
PLEASE have a look around....
http://forum.xda-developers.com/showthread.php?t=1523682
the numbers you want are here within ^post n°8. (value is Kb) and in many other posts!
The last partition n°17, should and must have only some 5gb because your device is 8 gb. Take care to set fdisk with the proper set up between blocks and Bytes and in case of error don't panic, just trail again .
Good luck
sorry lolo9393
Jistropy said:
Okay, rude much?
Your no help, that's for: "CORRECT partition sizes (for 16GB model!):"
As I said above, I have a 8 GIG USA YP-G70.
If your gonna post, maybe you should read more clearly.
Click to expand...
Click to collapse
You follow the table until partition 17 that will show only some "5252096" kb remaining if entered numbers are correct, because you have a 8 Gb device.
I tried to help you with what I know, sorry for my bad english..
Jistropy said:
Okay, rude much?
Your no help, that's for: "CORRECT partition sizes (for 16GB model!):"
As I said above, I have a 8 GIG USA YP-G70.
If your gonna post, maybe you should read more clearly.
Click to expand...
Click to collapse
Please listen th his help. He knows more about it than I do.
i apologize but no matter how i insert those numbers they never come out close
I got up to block 16 but it says i over pass the cylendars
Code:
/dev/block/mmcblk0p16 64181 313396 1993728 83 Linux
/dev/block/mmcblk0p17 313401 1937720 12994560 83 Linux
What do I set for 17 as well?
I can't get the tables to add up to what u got so i copied the start and ending for each.
Stuck on 16/17 need some help.
Edit --
I was able to flash stock! But i get a bunch of errors about opening cache and mounting.
rfs format failed on /dev/block/mmcblk0p15
Jistropy said:
I got up to block 16 but it says i over pass the cylendars
Code:
/dev/block/mmcblk0p16 64181 313396 1993728 83 Linux
/dev/block/mmcblk0p17 313401 1937720 12994560 83 Linux
What do I set for 17 as well?
I can't get the tables to add up to what u got so i copied the start and ending for each.
Stuck on 16/17 need some help.
Edit --
I was able to flash stock! But i get a bunch of errors about opening cache and mounting.
rfs format failed on /dev/block/mmcblk0p15
Click to expand...
Click to collapse
Yes, you were able to flash but your device is still useless because partition 16 and 17 are wrongly built.
may be you entered the right numbers but resulting in wrong recording , check your print (p) attached.
It is perfect until partition 16 beginning..
.Now just delete and rewrite 16 and 17th. (end n°17 by +k instruction will fill the gap and give you the right number or enter 242432 blocks as follow .
Vdev/block/mmcblk0p17 313401 242432 ........... result dotted should give some 5252096 kb.
Then write and print again in order to check your good work and at this point your next flashing will be good! (may be a wipe cache to be sure and avoid bootloop)
other suggestion is you come to my home tomorrow morning in order I arrange that for you!!!!
Cheers
It is perfect until partition 16 beginning..
.Now just delete and rewrite 16 and 17th. (end n°17 by +k instruction will fill the gap and give you the right number or enter 242432 blocks as follow .
Vdev/block/mmcblk0p17 313401 242432 ........... result dotted should give some 5252096 kb.
Then write and print again in order to check your good work and at this point your next flashing will be good! (may be a wipe cache to be sure and avoid bootloop)
Click to expand...
Click to collapse
What do I put for 0p16 then? Sorry I'm making sure i dont mess up
Tried following the same 16 and it went through however for block 17 the number value is too high
Jistropy said:
What do I put for 0p16 then? Sorry I'm making sure i dont mess up
Tried following the same 16 and it went through however for block 17 the number value is too high
Click to expand...
Click to collapse
Quick because it is lunch time here...
P16 is the same as in the 16gb table.
/dev/block/mmcblk0p16 64181 313396 1993728 83 Linux
ok ,got it?
No risk you mess the device, only take care to verify what is done by (p) print instruction and check the written table.
it doesnt allow me to set that value.. im sorry
Jistropy said:
it doesnt allow me to set that value.. im sorry
Click to expand...
Click to collapse
Did you delete the partition before rewriting it?
Should work because you have enough numbers of blocks to fill as said.
If no success do as follow:
delete p16 and 17, then do a write and post the result you get.
here: (I dont have enough space for every 16, or 17)
but im glad you've gotten me this far.
Jistropy said:
here: (I dont have enough space for every 16, or 17)
but im glad you've gotten me this far.
Click to expand...
Click to collapse
Sorry i didn't check it first but you are 4 heads mode (read line 2 of your print) that explain wy your lack of blocks.
You shoud reset fdisk in secondary menu to 1 head like following example
1 heads, 16 sectors/track,
Units = cylinders of 16 * 512 = 8192 bytes
I have no means to open fdisk from here to guide you, but it is easy to find once understood.
I come back in 3 hours time and if you still have pb I'll check for more guidance.
OK?
ADD;
How to change heads number?
select (h) to change number of heads in expert menu (m)
(now you are the "expert") you should get some 970 000 cylinders to split.
For more details:
http://linux.omnipotent.net/article.php?article_id=6979
doing this will allow you to successfully complete your memory table. great!
Hi,
- I can't boot into odin-mode (vol- + home + pwr): some korean text on the display. in the bottom a "!" in a yellow triangle. doesn't switch to the second logo.
- the device doesn't boot normally. Samsung logo and a blue line goes from left to right the the device stops (lsusb: idVendor=04e8, idProduct=6860 recognized)
- I can boot into recovery: cwm-based touch recovery v5.5.0.4. I can't flash any rom. Upgrade process stopped before the end. I can't do wipe data:
formatting /data: E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
same as /cache
what should I do? How can I install a newer recovery with current cwm? Can I unbrick over USB?
regards, Gabor
Now I can do an adb shell while I'm in cwm recovery.
is this partition table normal?
Code:
/proc # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 3816960.
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): p
Disk /dev/block/mmcblk0: 31.2 GB, 31268536320 bytes
1 heads, 16 sectors/track, 3816960 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 92 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 3816960 30431279+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 13313 13375 500 47 Unknown
/dev/block/mmcblk0p6 13825 14080 2048 45 Unknown
/dev/block/mmcblk0p7 14337 14649 2500 4c Unknown
/dev/block/mmcblk0p8 14849 16128 10240 48 Unknown
/dev/block/mmcblk0p9 16385 16447 500 46 Unknown
/dev/block/mmcblk0p10 16897 16959 500 5d Unknown
/dev/block/mmcblk0p11 17409 17471 500 91 Unknown
/dev/block/mmcblk0p12 17921 19200 10240 93 Unknown
/dev/block/mmcblk0p13 19457 32000 100352 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p14 32257 32640 3072 4a Unknown
/dev/block/mmcblk0p15 32769 33152 3072 4b Unknown
/dev/block/mmcblk0p16 33281 33664 3072 58 Unknown
/dev/block/mmcblk0p17 33793 46336 100352 8f Unknown
/dev/block/mmcblk0p18 46593 46976 3072 59 Unknown
/dev/block/mmcblk0p19 47105 47488 3072 5a Unknown
/dev/block/mmcblk0p20 47617 48000 3072 5b Unknown
/dev/block/mmcblk0p21 48129 49408 10240 ab Darwin boot
/dev/block/mmcblk0p22 49665 50944 10240 60 Unknown
/dev/block/mmcblk0p23 51201 52480 10240 94 Unknown
/dev/block/mmcblk0p24 52737 244480 1533952 a5 FreeBSD
/dev/block/mmcblk0p25 244737 507136 2099200 a6 OpenBSD
/dev/block/mmcblk0p26 507393 546048 309248 a8 Darwin UFS
/dev/block/mmcblk0p27 546305 562816 132096 a9 NetBSD
/dev/block/mmcblk0p28 563201 627200 512000 95 Unknown
/dev/block/mmcblk0p29 627201 3816960 25518080 90 Unknown
You might try a usb jig to get into download mode.
I bought one on eBay a while back just in case. But haven't needed it yet.
Google up usb jig i717 or jtag galaxy note, and you will find out how to buy one, or make one if you have soldering skills. And use one.
Here is a link to one on eBay. I'm sure there are many places to get one.
http://www.ebay.com/itm/Samsung-Galaxy-Note-I717-Download-ODIN-Mode-USB-Fix-Jig-/150994349563
There are videos on YouTube that explain how to do it as well.
HTH
Hi,
internal SD-card damaged. Only some partition was readable. I could go to recovery, I could modify the boot.img and map everything to the external SD.
G.
i717 said:
You might try a usb jig to get into download mode.
I bought one on eBay a while back just in case. But haven't needed it yet.
Google up usb jig i717 or jtag galaxy note, and you will find out how to buy one, or make one if you have soldering skills. And use one.
Here is a link to one on eBay. I'm sure there are many places to get one.
http://www.ebay.com/itm/Samsung-Galaxy-Note-I717-Download-ODIN-Mode-USB-Fix-Jig-/150994349563
There are videos on YouTube that explain how to do it as well.
HTH
Click to expand...
Click to collapse
my phone also bricked -SHV-e160k
While updating firmware via ODIN , because of USB connectivity failure it is failed.
Now exclamation mark coming in the ODIN mode. (not able to flash any firmware via ODIN tool)..
I am suspecting '.PIT' table might be corrupted in my phone (SHV-e160K).
Please tell me where I can download .pit file SHV-E160K...??
Please help me to resolve the issue..??
Regards,
Bhanu
Hi everybody..
I need help with my tablet partitions. I want to resize correctly /data and /emmc (internal sdcard).
I tried so much things and I read a lot of pages, but did'nt have what I want.
I have a Novo 10 captain + TWRPv2.6.3 + Backups.
Here are all information do you need.
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
93 0 49152 acta
93 8 49152 actb
93 16 524288 actc
93 24 1048576 actd
93 32 65536 acte
93 40 131072 actf
93 56 58368 acth
93 72 13720275 actj
93 80 262144 actk
179 0 15558144 mmcblk0
179 1 15550888 mmcblk0p1
~ # ←[6n
~ # ←[6ntail ./etc/recovery.fstab
tail ./etc/recovery.fstab
/recovery vfat /dev/block/acta
/boot vfat /dev/block/actb
#/misc vfat /dev/block/actb
/system ext4 /dev/block/actc
/data ext4 /dev/block/actd
/cache ext4 /dev/block/acte
#/data_bak vfat /dev/block/actf
/emmc vfat /dev/block/actj
/sdcard auto /dev/block/mmcblk0p1
/sd-ext auto /dev/block/mmcblk0p2
~ # ←[6n
So, I have just 1G for /data and 13G for /emmc.
It is not useful, so I want to have about 2.5G or more for /data and 10G for /emmc.
I tried so much things with these command: parted, fdisk, e2fsck, resize2fs, etc.
I also read things like MBR/EBR1/EBR2 but it is not very clear for me.
Ok guys, help.. for 1 million dollard
by the way, I'm not very good in english, so be cool :good:..
Ok great !
I finally got the best way to do that. It's very simple and so clear.
I just want say a big "Alleluijah" for that . I searched about 2 weeks for to have more space.
Ok everybody, just read these links and be happy
http://forum.xda-developers.com/showthread.php?t=1716124
http://forum.xda-developers.com/showthread.php?t=1933849
Don't forget to Enable Init.d
So, trying to install LineageOS on a stock Sony Xperia T, I got to trying to unify the userdata and now I have a 2GB "Internal Storage" (on /sdcard) partition and no "Legacy SDCard" partition. So clearly I messed up. I looked at the source code of the unify_userdata-20170128.zip file and it looks like all it does is delete the old UserData and SDCard partitions and then creates a new partition using all the sectors that were previously divided between these two partitions.
My question is this: is this correct? Why did android have two partitions of ~2Gb for Internal Storage and ~10Gb for the Legacy SD Card? Does the unify_userdata script really just delete these two and make one partition from the freed space?
And also, how can I fix my phone? In adb shell, df reports that the userdata partition (number 14) is mounted at /sdcard and is 2GB, but fdisk says that partition 14 has the label Userdata and is 13Gb. So how can it be mounted and only show a size of 2Gb?
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 423.7M 16.0K 423.7M 0% /dev
tmpfs 423.7M 24.0K 423.7M 0% /tmp
/dev/block/mmcblk0p13 246.1M 4.2M 241.8M 2% /cache
/dev/block/mmcblk0p14 2.0G 35.0M 1.9G 2% /data
/dev/block/mmcblk0p14 2.0G 35.0M 1.9G 2% /sdcard
Code:
# fdisk -l /dev/block/mmcblk0
Number Start (sector) End (sector) Size Code Name
1 256 4351 2048K 0700 TA
2 4352 7423 1536K 0700 Boot
3 7424 10495 1536K 0700 Boot2
4 12288 53247 20.0M 0700 Kernel
5 53248 55295 1024K 0700 TZ
6 57344 63487 3072K 0700 modemst1
7 65536 71679 3072K 0700 modemst2
8 73728 79871 3072K 0700 fsg
9 79872 90111 5120K 0700 ramdump
10 90112 106495 8192K 0700 apps_log
11 106496 139263 16.0M 0700 FOTAKernel
12 139264 2654207 1228M 0700 System
13 2654208 3166207 250M 0700 Cache
14 3166208 30535646 13.0G 0700 Userdata