all other partitions come back different?

does this tell me anything?


steve@lovejoyub:~$ adb shell
~ # mke2fs -T ext4 /dev/block/mmcblk0p12
mke2fs: lseek: Value too large for defined data type
~ #

Originally Posted by lovejoy777

all other partitions come back different?

does this tell me anything?


steve@lovejoyub:~$ adb shell
~ # mke2fs -T ext4 /dev/block/mmcblk0p12
mke2fs: lseek: Value too large for defined data type
~ #

You mean have been able to get parted running now? that is a good sign if yes.

can you post the partition table using (parted) print?

Also, the above code should not be used for partition 12 because it is media partition and format is fat32.

ok just had the hang at waiting for omap44xx devices, this is how i got out of it.

pull battery terminal
perform usb_fix from firekit
when it says waiting for omap44xx device short pin and insert usb cable. if it doesn't work. (it normally starts 2nd stage bla bla bla),
normally ends with waiting for omap again(if no script at all runs try unplugging usb and re-shorting pins then reconnect usb), at this point
plug in battery, this should start the installs etc

Edit: I always keep pin shorted throughout the process.

notes: it is best to always start from scratch after each attempt ie. if its hanging anywhere, unplug kindle and close terminal, reopen terminal and start again.
I hope this helps

---------- Post added at 05:48 PM ---------- Previous post was at 05:45 PM ----------

Originally Posted by forest1971

You mean have been able to get parted running now? that is a good sign if yes.

can you post the partition table using (parted) print?

Also, the above code should not be used for partition 12 because it is media partition and format is fat32.

no parted just hangs on print but i tried the scripts anyway. (i know it wont help just wanted to know why 12 returned different.
now i know:)
Edit: if i run commands in parted (except print) I always get things returning in terminal. does this mean the commands are being performed?

Originally Posted by lovejoy777

ok just had the hang at waiting for omap44xx devices, this is how i got out of it.

pull battery terminal
perform usb_fix from firekit
when it says waiting for omap44xx device short pin and insert usb cable. if it doesn't work. (it normally starts 2nd stage bla bla bla),
normally ends with waiting for omap again(if no script at all runs try unplugging usb and re-shorting pins then reconnect usb), at this point
plug in battery, this should start the installs etc

Edit: I always keep pin shorted throughout the process.

notes: it is best to always start from scratch after each attempt ie. if its hanging anywhere, unplug kindle and close terminal, reopen terminal and start again.
I hope this helps

---------- Post added at 05:48 PM ---------- Previous post was at 05:45 PM ----------



no parted just hangs on print but i tried the scripts anyway. (i know it wont help just wanted to know why 12 returned different.
now i know:)

If you have been able to install bootloader then try to:
fastboot oem format

If works it will restore partition structure and in that case parted should be able to see it.

Originally Posted by forest1971

If you have been able to install bootloader then try to:
fastboot oem format

If works it will restore partition structure and in that case parted should be able to see it.

I wish I was that lucky:)

I've been trying everything for days lol.
whilst i still have bootloader and some sort of adb/fastboot i will keep trying.

if anyone wants to test any bootloaders or anything else a blocked emmc chip can do, let me know.

Originally Posted by Entropy512

Samsung files???? If you mean his recovery - it's hopefully the solution to preventing eMMC damage from happening in the first place to anyone else. Currently, once it has happened, nothing short of replacing the flash chip or the whole motherboard will fix it. While a way DOES exist for resurrecting these chips, it requires "supah-secret-Samsung-info" that we don't have.

(This all assumes that the failure mode here is the same as Samsung Superbrick - is there anyone that had a failure with a flash chip other than M8G2FA?)

As to your first problem - sounds like you still have some bad areas that you haven't partitioned around.

In my case, the resurrection is starting to not look so good. Although initially the re-partioning around the bad blocks was working, it now appears that there is some spillover from the adjacent bad blocks as my KF is beginning to lock up more often and even a system wipe with a fresh install came after great pain and crossed fingers. I think I'm witnessing the slow demise of this KF ... that new Lenovo IdeaTab is starting to look sweeter and sweeter ...

Thanks again to all.

steve@lovejoyub:~$ adb shell
~ # for F in /sys/block/mmcblk0/mmcblk0p*
> do
> echo $F
> cat $F/partition_name $F/start $F/size
> done
/sys/block/mmcblk0/mmcblk0p1
xloader
256
256
/sys/block/mmcblk0/mmcblk0p10
userdata
1657856
2328576
/sys/block/mmcblk0/mmcblk0p11
cache
3986432
524288
/sys/block/mmcblk0/mmcblk0p12
media
4510720
10508288
/sys/block/mmcblk0/mmcblk0p2
bootloader
512
512
/sys/block/mmcblk0/mmcblk0p3
dkernel
1024
20480
/sys/block/mmcblk0/mmcblk0p4
dfs
21504
393216
/sys/block/mmcblk0/mmcblk0p5
recovery
414720
32768
/sys/block/mmcblk0/mmcblk0p6
backup
447488
131072
/sys/block/mmcblk0/mmcblk0p7
boot
578560
20480
/sys/block/mmcblk0/mmcblk0p8
splash
599040
10240
/sys/block/mmcblk0/mmcblk0p9
system
609280
1048576
~ #

Tried everything on this thread i still seem unable to find a solution, bummer. Can i push SU files to adb? Could it be that's the reason i'm unable to work with the partitions? I get the feeling that i'm not rooted and i'm currently locked out and its blocking commands im running via some sort of permission set.

Originally Posted by jsantiago.antonio

Tried everything on this thread i still seem unable to find a solution, bummer. Can i push SU files to adb? Could it be that's the reason i'm unable to work with the partitions? I get the feeling that i'm not rooted and i'm currently locked out and its blocking commands im running via some sort of permission set.

I've had the same thought.

---------- Post added at 11:47 PM ---------- Previous post was at 11:41 PM ----------

for some reason im doubting its the sammy superbrick.

on all there posts about the brick it stats most seem to have a bad return on this command. but we seem ok?

dmesg | grep mmc0

Originally Posted by jsantiago.antonio

Tried everything on this thread i still seem unable to find a solution, bummer. Can i push SU files to adb? Could it be that's the reason i'm unable to work with the partitions? I get the feeling that i'm not rooted and i'm currently locked out and its blocking commands im running via some sort of permission set.

I am not sure about the status of your KF yet.

If it can boot and can get into TWRP then parted should work and it can help deal with faulty partition if there is. (please confirm if it can boot and get into TWRP).

Before bootloader and TWRP work parted is of no use.

cheers