[Guide]How to revive your bricked Gnote

[asafki]

It seems partition 10 is not so good (4.8% non-contiguous). Still, e2fsck should have helped deal with that and should continue to apply the procedures suggested in the post above. See it it helps at all.

In case that does not work, I would repartition again, leaving the current datafs unused (rm 10 and 11 and create new datafs from 5540 to 7687 and ums from 7687 to 15200). See how it goes.

partition 9 seems to be ok, but 10 not so good. I would:

1. Complete procedures as in post 1349 to see if it helps at all.
if not:
2. Repartition manually: rm 10 and 11 and create a new partition 10 and 11 so that the current partition 10 is left unused. Using the suggestion in the point 7.2 in the guide, but change the start and end number of partitions accordingly.
check again using e2fsck. if you have difficulty doing repartition then should post the partition table so that we can see where (start from what number) to create new partitions.

see how it goes.

First of all, thank you very much!

I did as suggested, still having freezes.
See below the new results of e2fsck, followed by the map from gparted. can you please let me know how to find out the numbers for the repartition? by the way, dd did not hang nor gave any I/O issue. what does it mean?
~ # e2fsck -f -c -y /dev/block/mmcblk0p10
e2fsck -f -c -y /dev/block/mmcblk0p10
e2fsck 1.41.12 (17-May-2010)
/dev/block/mmcblk0p10: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/block/mmcblk0p10: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p10: 4927/131072 files (3.2% non-contiguous), 35885/524288 blocks
~ # e2fsck -f -c -y /dev/block/mmcblk0p9
e2fsck -f -c -y /dev/block/mmcblk0p9
e2fsck 1.41.12 (17-May-2010)
/dev/block/mmcblk0p9: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/block/mmcblk0p9: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p9: 4377/54544 files (0.1% non-contiguous), 49360/218112 blocks
~ # e2fsck -f -c -y /dev/block/mmcblk0p7
e2fsck -f -c -y /dev/block/mmcblk0p7
e2fsck 1.41.12 (17-May-2010)
/dev/block/mmcblk0p7: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/block/mmcblk0p7: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p7: 128/12800 files (7.0% non-contiguous), 18164/51200 blocks
~ #

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 4608MB 5501MB 893MB ext4 FACTORYFS
10 5501MB 7649MB 2147MB ext4 DATAFS
11 7649MB 15.2GB 7551MB fat32 UMS msftres
12 15.2GB 15.8GB 537MB ext4 HIDDEN

 

[Dungeon47]

I was stuck, unable to boot, unable to get into recovery, able to flash kernels in ODIN, unable to flash full ROMs in ODIN.
What worked was flashing stock kernel, not rooted, pure stock. Then I could enter stock recovery. I then flashed HYDRACORE in ODIN and I was able to enter CWM recovery. I then flashed CM10 kernel and restored from nandroid.

PM me with any questions on details. This whole ordeal happened after flashing a purportedly safe kernel while running AOKP JB. I'm still narrowing down the most likely cause for it failing, as I'm very sure I didn't do anything wrong or even remotely dangerous.

The best theory I have is that it was a bad download of a kernel I flashed. I always check MD5 on ROMs, time to check on kernels, too. LFMF.

 

[forest1971]

I was stuck, unable to boot, unable to get into recovery, able to flash kernels in ODIN, unable to flash full ROMs in ODIN.
What worked was flashing stock kernel, not rooted, pure stock. Then I could enter stock recovery. I then flashed HYDRACORE in ODIN and I was able to enter CWM recovery. I then flashed CM10 kernel and restored from nandroid.

PM me with any questions on details. This whole ordeal happened after flashing a purportedly safe kernel while running AOKP JB. I'm still narrowing down the most likely cause for it failing, as I'm very sure I didn't do anything wrong or even remotely dangerous.

The cause for failing maybe not clear but it is clear that you were on safe kernel and "did not do anything that is dangerous". So it is not a case of emmc brick. Good that you find the way to fully revive it. cheers.

---------- Post added at 06:39 PM ---------- Previous post was at 06:23 PM ----------

First of all, thank you very much!



/dev/block/mmcblk0p7: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p7: 128/12800 files (7.0% non-contiguous), 18164/51200 blocks
~ #

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 4608MB 5501MB 893MB ext4 FACTORYFS
10 5501MB 7649MB 2147MB ext4 DATAFS
11 7649MB 15.2GB 7551MB fat32 UMS msftres
12 15.2GB 15.8GB 537MB ext4 HIDDEN

The non-contiguous just suggest it is not in optimal condition.
If the procedures in post 1349 does not help then try repartition datafs as below, to leave another chunk of memory unused:
(parted) rm 10
(parted) rm 11
(parted) mkpart primary 7649 9796
(parted) mkpartfs primary fat32 9796 15200
(parted) name 10 DATAFS
(parted) name 11 UMS

Then go to CWM and format data. then you can install rom.
See if it helps at all. This operation is reversible.

Should also check partition 7 as well, since it can also cause freeze.

---------- Post added at 06:45 PM ---------- Previous post was at 06:39 PM ----------

ArdL

Hi,
I've try the second way efs but didn't work.

And about flashing a modem which one should I try if you can give me it link because these links you've give didn't works.
Note: am on cm9 nightly.
Ginger bread also the same can't detect sim.

Find a modem suitable to the rom in the link below.

http://forum.xda-developers.com/showthread.php?t=1645202

see if it helps.

---------- Post added at 06:53 PM ---------- Previous post was at 06:45 PM ----------

Hello to all.
I recently managed to revive a GT-N7000 with forset's help and the schemes he provided for the case in which the UMS partition is damaged. The device worked for a couple of days but it was faulty and my guess is that there are still damaged parts of the memory in use. Until it broke completely once again and I had to repartition it again.
Now my request from forest or anyone who knows the way is to create a tutorial on how to determine the best partition scheme for each device so that we can do it ourselves.
Thanks.

Each brick device could be hit at a different place.

The principal is:
- If you can enter recovery then should using hg42 partition scanner or adb/dd scan as in my guide to identify brick area. Then try to repartition around that area using custom PIT file or manually using parted.
- If there is no recovery, only download mode, adn you are sure it is emmc brick, then just use the custom PITs for common case. If not work then try with other ones.
cheers.

 

[hg42]

/dev/block/mmcblk0p10: 5272/131072 files (5.3% non-contiguous), 148931/524288 blocks

this is in no way alarming.
The value 5.3% stands for file fragmentation.
It's only an informational output, no error.

I am sure most windows file systems are fragmented more.
The very low value for /system tells us, that /system is never written to, so there is no fragmentation.

The ext* file systems have auto-defragmentation, so that's no problem at all, may be much bigger values (greater 50%?) could eventually worry me.

But fragmentation has nothing to do with freezing.

Partitioning exactly like before probably will not stop freezes.

---------- Post added at 05:33 AM ---------- Previous post was at 05:21 AM ----------

I was stuck, unable to boot, unable to get into recovery, able to flash kernels in ODIN, unable to flash full ROMs in ODIN.
What worked was flashing stock kernel, not rooted, pure stock. Then I could enter stock recovery. I then flashed HYDRACORE in ODIN and I was able to enter CWM recovery. I then flashed CM10 kernel and restored from nandroid.

PM me with any questions on details. This whole ordeal happened after flashing a purportedly safe kernel while running AOKP JB. I'm still narrowing down the most likely cause for it failing, as I'm very sure I didn't do anything wrong or even remotely dangerous.

'No boot' and 'stuck' could be because the kernel may have been incompatible to the aokp jb rom.
But I think this wouldn't explain not getting into recovery nor beeing unable to flash roms.
What happened, when flashing rom via odin?

I got the feeling, that stock kernel does some scripting things on reboot, so there may be the difference.

 

[mulla88]

Thanks

 

[ctokay]

It works!

If you can revive your Note please share your success with us so that we can share your good feeling !

when i want to decide update my Note from ICS to JB, i mistakenly pressed the data/factory wipe and then boom! My note was bricked!.

Thanks to your advice, i revived my NOTE!!:laugh::good::laugh: i made my DATAFS partition different like 4500-6647 and then everything works perfectly(wipe,dd)! Thank you so much dude!:laugh: You are life saver:cyclops:

 

[forest1971]

when i want to decide update my Note from ICS to JB, i mistakenly pressed the data/factory wipe and then boom! My note was bricked!.

Thanks to your advice, i revived my NOTE!!:laugh::good::laugh: i made my DATAFS partition different like 4500-6647 and then everything works perfectly(wipe,dd)! Thank you so much dude!:laugh: You are life saver:cyclops:

Nice ! thank you too!

 

[asafki]

Still no luck...
What should I try next?
e2fsck and dd looks clean, running out of ideas... should I just continue with moving the partitions to other location and see if it helps?

In Addition, can I use parted to actually define the data and system on the external sd card? would that work?

Thanks.

 

[No.01]

Flashing a modem didn't solve (no detecting sim card), and tried efs way I found nothing in efs folder.. I lost everything in efs folder now how to restore it?

 

[aletheus]

Still no luck...
What should I try next?
e2fsck and dd looks clean, running out of ideas... should I just continue with moving the partitions to other location and see if it helps?

In Addition, can I use parted to actually define the data and system on the external sd card? would that work?

Thanks.

I'm having trouble with the gTab 7.7. Cant get a stable data partition, and must be doing something wrng...ive gotten cm10 to boot a few times, no gapps. But i cant figure out how to use the emmc2extSD script.... i'm not a developer, but i'm smart enough to follow directions...i think.. hahah!

I'm guessing te problem with using parted to swap is this: the ROM has flash instructions embedded. These are using addresses for the internal memory (mmcblk0). Why you couldnt find and replace mmcblk0 with mmcblk1 everywhere you'd need, i don't know, that part is over my head....

I wish i could adb into my bricked tablet from my new Note 10.1 (believe it or not i have no pc)... but alas, again this is over my head...

---

 

[forest1971]

Flashing a modem didn't solve (no detecting sim card), and tried efs way I found nothing in efs folder.. I lost everything in efs folder now how to restore it?

Flash the EFS image in the file below using odin should help restore the (damaged) efs partition. If it works you will have a generic emei, but will let the phone recognized Simcard. (this is from a GB wipe rom that has efs image).

see how it goes.

http://www.mediafire.com/?uafc086sfh2a3td

---------- Post added at 10:15 AM ---------- Previous post was at 10:05 AM ----------

Still no luck...
What should I try next?
e2fsck and dd looks clean, running out of ideas... should I just continue with moving the partitions to other location and see if it helps?

In Addition, can I use parted to actually define the data and system on the external sd card? would that work?

Thanks.

In some case the reason is still unknown. I would try the things below.

1. Use dd to scan partition again from 1 to 12 to see if there is damage somewhere that can be dealt with.
2. Try to swap internal and external sdcard. There is one case I help through PM where the phone will not freeze anymore when the ums partition is remove (so you have no internal sdcard). So I guess it is worth trying, and it is reversible. There is thread in the general section that give guide on how to swap internal and external sdcard (to make external become internal).
See it it helps at all.

---------- Post added at 10:18 AM ---------- Previous post was at 10:15 AM ----------

I'm having trouble with the gTab 7.7. Cant get a stable data partition, and must be doing something wrng...ive gotten cm10 to boot a few times, no gapps. But i cant figure out how to use the emmc2extSD script.... i'm not a developer, but i'm smart enough to follow directions...i think.. hahah!

I'm guessing te problem with using parted to swap is this: the ROM has flash instructions embedded. These are using addresses for the internal memory (mmcblk0). Why you couldnt find and replace mmcblk0 with mmcblk1 everywhere you'd need, i don't know, that part is over my head....

I wish i could adb into my bricked tablet from my new Note 10.1 (believe it or not i have no pc)... but alas, again this is over my head...

---

I guess if you try adb/parted in a proper way with a PC, you will be able to deal effectively with the damaged partition. As for using another android device I have no idea yet. cheers.

 

[aletheus]

I guess if you try adb/parted in a proper way with a PC, you will be able to deal effectively with the damaged partition. As for using another android device I have no idea yet. cheers.

http://forum.xda-developers.com/showthread.php?t=1454753

Is this the thread you were talking about?

Is there a way to get a rom to flash directly to the sd and just bypass internal storage alltogether?

---

 

[forest1971]

http://forum.xda-developers.com/showthread.php?t=1454753

Is this the thread you were talking about?

Is there a way to get a rom to flash directly to the sd and just bypass internal storage alltogether?

---

Yes, that is the thread about changing internal and external sdcard. It is assumed that for some case the internal sdcard has too much damage, so when app try to access to it it cause freeze. It is just specific cases.
As for flashing: most cwmwould recognize external scared. So should put custom Rom to it. Or can flash using Odin. Still in your case I suspect will need to use adb parted with a pc. Cheers.

Sent from my LT18i using Tapatalk 2

 

[aletheus]

I'm sorry for all the questioos, but: does this make it so the device boota from ext sd? Or does it ist move /data to the sd?

---

 

[asafki]

forest1971, thanks a lot!
So, by some kind of mistake, I was installing a patched PIT file. than, by running adb command, I removed the mount points to my internal drive, and mounted my external as both internal and external.
its been 3 days now without a freeze!!
still having issues with running a script after reboot, but no freezes!
would that also work after flashing another rom, or should I be careful with this?

 

[d3mv2]

need help with infinite reboots on my precoius gnote. having cm10-nightly builds working perfect for a few month but then suddenly without any unusual actions (even no new apps) i got infinite reboot problem.

wipe dalvik/cache dont help (after dalviks wipe system can boot till app reorganizing, when it completes -> infinite reboot)
after flashing hydracore kernel (used for instaling cm10, but it seems nightly builds have their own kernel) phone even cant start (charging ??/100 or CWM/DL MODE only)
after flashing rom (latest cm10 nighty) it comebacks to infite reboots again
didnt try to do factory reset yet coz i want to save all my stuff (silly! forget to backup after tons time of customization)

any suggestions about whole problem and saving stuff?

 

[forest1971]

need help with infinite reboots on my precoius gnote. having cm10-nightly builds working perfect for a few month but then suddenly without any unusual actions (even no new apps) i got infinite reboot problem.

wipe dalvik/cache dont help (after dalviks wipe system can boot till app reorganizing, when it completes -> infinite reboot)
after flashing hydracore kernel (used for instaling cm10, but it seems nightly builds have their own kernel) phone even cant start (charging ??/100 or CWM/DL MODE only)
after flashing rom (latest cm10 nighty) it comebacks to infite reboots again
didnt try to do factory reset yet coz i want to save all my stuff (silly! forget to backup after tons time of customization)

any suggestions about whole problem and saving stuff?

If there is enough time between reboot then you can try to back up application using titanimum back up. Then copy the back up folder and other contents in internal sdcard like photos...to PC. Then try to change rom and do other tricks to solve the reboot problem. After that you can restore applications using Titanium backup again to save time.
Just remember to avoid wiping/restore using unsafe ICS stock kernel. The safest way is to go back to a GB rom while try to fix the problem, then change to other rom later.
If reboot is very frequent, then you need to see if the phone is stable in cwm recovery mode, then in the recovery mode you can still back up content of the sdcard, as suggested in the guide, but cannot back up apps.

Sending from my phone

 

[No.01]

I flashed efs with Odin but didn't make anything in gb rom, now I changed to cm9 to try efs way again, but the problem now is when I want to download root explorer app Google play says *server error*.. every time
Now how to fix this error?!
I tried to flash the rom again and wipe data factory and no luck.

 

[forest1971]

I flashed efs with Odin but didn't make anything in gb rom, now I changed to cm9 to try efs way again, but the problem now is when I want to download root explorer app Google play says *server error*.. every time
Now how to fix this error?!
I tried to flash the rom again and wipe data factory and no luck.

Not sure what cause the issue with "server error". I suspect it is the Gapps that has not been properly installed.

I would try to flash the multi-part GB stock rom below that has EFS image with it:

http://forum.xda-developers.com/showthread.php?t=1423514

It is tricky that there are to many parts for putting in Odin tabs. I hope you would be able to figure out how to flash all of them. (Perhaps will need to untick auto-reboot and to select again or to reboot in download mod then flash other files-I have not tried).

 

[No.01]

Not sure what cause the issue with "server error". I suspect it is the Gapps that has not been properly installed.

I would try to flash the multi-part GB stock rom below that has EFS image with it:

http://forum.xda-developers.com/showthread.php?t=1423514

It is tricky that there are to many parts for putting in Odin tabs. I hope you would be able to figure out how to flash all of them. (Perhaps will need to untick auto-reboot and to select again or to reboot in download mod then flash other files-I have not tried).

I did, but still stuck at datafs, when I flash rom from 3 files this happens.
but if there's a wipe rom from one file It will works.
I did untick auto-boot way as you said but stuck at datafs, but maybe I didn't understand it well.
where is the problem when someone calls me it gives busy signal!
my phone detect sim cards and shows the network signal is excellent, but when I try to call the line turns off then it shows "No Service" triangle!