Knowledgement emmc damage tutte le info del caso

[Andromeda1968]

MMC_CAP_ERASE disabilitato ??? forse ci siamo ??? speriamo...primo passo


da Hardcore (Speedmod kernel)


Ho cambiato mshci.c e sdhci.c in questo modo:

drivers/mmc/host/mschi.c:

mmc->ops = &mshci_ops;
mmc->f_min = 400000;
mmc->f_max = host->max_clk;
//SpeedMod: Disable TRIM to fix hard brick bug
mmc->caps |= MMC_CAP_SDIO_IRQ; // | MMC_CAP_ERASE;

drivers/mmc/host/sdhci.c:

if (host->quirks & SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK)
mmc->max_discard_to = (1 << 27) / (mmc->f_max / 1000);
else
mmc->max_discard_to = (1 << 27) / host->timeout_clk;

//SpeedMod: Disable TRIM to fix hard brick bug
mmc->caps |= MMC_CAP_SDIO_IRQ; // | MMC_CAP_ERASE;

[falk88]

MMC_CAP_ERASE disabilitato ??? forse ci siamo ??? speriamo...primo passo


da Hardcore (Speedmod kernel)


Ho cambiato mshci.c e sdhci.c in questo modo:

drivers/mmc/host/mschi.c:

mmc->ops = &mshci_ops;
mmc->f_min = 400000;
mmc->f_max = host->max_clk;
//SpeedMod: Disable TRIM to fix hard brick bug
mmc->caps |= MMC_CAP_SDIO_IRQ; // | MMC_CAP_ERASE;

drivers/mmc/host/sdhci.c:

if (host->quirks & SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK)
mmc->max_discard_to = (1 << 27) / (mmc->f_max / 1000);
else
mmc->max_discard_to = (1 << 27) / host->timeout_clk;

//SpeedMod: Disable TRIM to fix hard brick bug
mmc->caps |= MMC_CAP_SDIO_IRQ; // | MMC_CAP_ERASE;

Quindi il problema e imputabile al fatto che hanno disabilitato il cap erase?


Inviato dal mio LG-P920 usando Androidiani App

[Ducati87]

Non è nulla di certo! L'autore declina ogni responsabilità in caso di eventuale brick.

[Andromeda1968]

post interessante sul kernel speedmod di harcore:



I took a gamble and went for it anyway, with Speedmod K2-2:

1. Factory reset from ROM (triggers stock recovery on this kernel): Works, and phone is OK.

2. CWM backup and advanced restore (data) from CWM (Koush's version 5.8.1.8 used in this kernel): Works, and phone is OK.

Of course, this doesn't guarantee that it won't brick your phone. But it worked for me, at least the one time that I tried it.

Just for reference, my emmc is VYL00M with 0x19 fw rev.

Interestingly, I could see these entries in the recovery logfile at /cache/recovery/last_log:

Code:
Checking MD5 sums...
boot.img: OK
cache.ext4.tar: OK
data.ext4.tar: OK
recovery.img: OK
system.ext4.tar: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2012-05-27.14.54.41//data.ext4.tar
Restoring data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Discard failed

couldn't find default
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.

Restore complete!



The line:
warning: wipe_block_device: Discard failed

Should be indicative that the TRIM function has indeed been disabled in this kernel. And if indeed, the TRIM function was responsible for the hard bricking, then in *theory* this kernel should be safe.

[KamAMaK]

Buone notizie....
Se avessi il cell tedesco in modo da non avere problemi poi di garanzia proverei a fare una decina di wipe per prova

post interessante sul kernel speedmod di harcore:



I took a gamble and went for it anyway, with Speedmod K2-2:

1. Factory reset from ROM (triggers stock recovery on this kernel): Works, and phone is OK.

2. CWM backup and advanced restore (data) from CWM (Koush's version 5.8.1.8 used in this kernel): Works, and phone is OK.

Of course, this doesn't guarantee that it won't brick your phone. But it worked for me, at least the one time that I tried it.

Just for reference, my emmc is VYL00M with 0x19 fw rev.

Interestingly, I could see these entries in the recovery logfile at /cache/recovery/last_log:

Code:
Checking MD5 sums...
boot.img: OK
cache.ext4.tar: OK
data.ext4.tar: OK
recovery.img: OK
system.ext4.tar: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2012-05-27.14.54.41//data.ext4.tar
Restoring data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Discard failed

couldn't find default
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.

Restore complete!



The line:
warning: wipe_block_device: Discard failed

Should be indicative that the TRIM function has indeed been disabled in this kernel. And if indeed, the TRIM function was responsible for the hard bricking, then in *theory* this kernel should be safe.

[Emanuele3000]

Quindi se uno mette ics con questo kernel speedmod non ha problemi? è stato risolto da lui?

[Andromeda1968]

Quindi se uno mette ics con questo kernel speedmod non ha problemi? è stato risolto da lui?

no purtroppo non è certa la situazione...

[Emanuele3000]

Quindi per ora l'unico ics sicuro sarebbe quello cyanogenmod?

[Andromeda1968]

da un utente di XDA



Easily fix bricked Samsung Galaxy Note N7000

As you may know, there are many kernels that can damage your Samsung Galaxy Note’s emmc, so your phone will be hard bricked. Unfortunately there are many bad kernels, including official ones and many have bricked their devices, including me. But I found a fix for this and I also have a list of kernels you should stay away from in order to make sure your device is safe from bricking.

While there isn’t any way of fixing the damaged emmc, you can repartition it and also used the internal SD card to move some system partitions to it in order for the device to work. Doing this is pretty easy, thanks to an XDA Developers user, who created a PIT file that can repartition your device.

First, here is the list of dangerous kernels: XXLPY, XXLPF, UCLD3, SiyahKernel 3.1rc6, all Samsung Epic 4G Touch (SPH-D710) leaks, all Samsung Galaxy Note (GT-N7000) leaks. If you are running on one of these kernels and your device is still working fine, we recommend you to flash another ROM through Odin right away and do not use ClockworkMod Recovery while on this ROM. Flashing or wiping in recovery can permanently damage your Galaxy Note !

We can’t guarantee you that this method will work, but it did work for us. Other users also confirmed that they managed to fix their bricked Galaxy Note with this method. Please note that we are not responsible for any damage this method does to your device. You do this on your own risk. How to unbrick Samsung Galaxy Note N7000 First you will have to download the PIT files for both the 16GB and 32GB versions. And make sure to use the appropriate version because otherwise you might do even more damage to your device.

Then you will need to flash either a stock Gingerbread ROM from sammobile or a rooted KJ1 ROM here. You will also need Odin 1.85, the software used to flash the files on your device. You can download it here.

You might need to unzip the files you download. Odin requires them to be in .pit and .tar file format and it cannot flash .zip files.

Shut down your Galaxy Note and boot in download mode ( press volume down + home button + power button simultaneously ). Then press volume up to actually enter the download mode. While doing this the device has to be disconnected from the computer.

Before you begin flashing the files, make sure that your antivirus and firewall software are open and there isn’t any Kies process open on your computer. You also require the latest Samsung USB drivers, which are included in the latest Kies version, so you should install it if you don’t have it on your computer.

Now launch Odin, click PIT and open either the 16GB or 32GB pit file. Click PDA and open the downloaded ROM. Now you can connect the device to the computer and press start. It might take a few minutes and you should wait even if it appears to get stuck. Sometimes it can take even 20 minutes.
Sent from my GT-N7000 using xda premium

[Andromeda1968]

?????????????