I have the same issue with my phone and it was definately CWM touch that messed it up . Samsung has a one year warranty on these phones.....and even though mine was bought as soon as they were available which was last june I called samsung and was told my phone is indeed under warranty until december of this year by it`s lot number...so as you can imagine I am sending mine directly to sammy free shipping out and back She expected to have my phone back to me in five to seven days !!! Samsung support number 1-800-726-7864 Hope this helps !!!
In the case of the international Note not everyone has the replacement options that the E4GT has, where most can replace it for $35 and *maybe* $100 if you go through Asurion. People that have made custom .PIT files - like hg42 - have also supported the position that this shouldn't be a permanent fix; just a way to restore the device to functionality until you can replace the device (which should be in a timely fashion.).
This also will not resolve issues where the lockup occurs in the boot process, so not everyone will be able to be saved.
Lastly thanks to the information from Mr. Sumrall and hurculean efforts of those like Entropy512 and Sfhub several developers are working to remove the offending code from their ICS builds to avoid the brick altogether. This will help stem the tide of bricks due to the eMMC lockup.
Until then people are still recommended to wipe from GB kernels and replace if bricked.
Whatever works for you. There are limitations though. It isn't a universal fix and for most people it is simpler to use warranty. If they don't have warranty, then it is a decision point what they want to do.
As to paying Samsung, they are not charging for the warranty repair. You just need to send it in and wait a week. The $35 is for "advanced replacement" through Sprint, where you get a new phone same day or in a few days if they need to order.
Forest, please check your PM. Won't go back and forth on things on threads when it's not necessary.
HI: If your phone is having problem with data partition due to the eMMC bug, then try to format it will not help. So far only re-partition workaround seems to help.
cheers,
I just tried this today, and so far so good. First off, the guide is worth a read to understand the issue, and how they went about solving it ...but we'll save all that reading for afterwards... :silly:
After trying to follow about 3 or 4 different threads on this issue, I finally came across the guide here for the Galaxy Note: ATTENTION! my way out of a MMC_CAP_ERASE brick! Lucky for E4GT owners with the brick issue, it works for us too! (brick issue meaning your phone powers on, and you can get in to recovery, but can't format /data or install a rom)
I just tried this today, and so far so good. First off, the guide is worth a read to understand the issue, and how they went about solving it ...but we'll save all that reading for afterwards... :silly:
Head over to the ATTENTION! my way out of a MMC_CAP_ERASE brick! thread, and scroll down to the section Update: instructions for unexperienced users
Read those instructions carefully, and make sure you are using the 16GB file from pits-patched-standard.zip
Now open up ODIN. Make sure your phone is plugged in and in Download Mode (When phone is off, hold down Power and Vol Down until you see the warning screen). There should also be a yellow box in ODIN meaning your phone is ready.
Choose the 16GB PIT file in the PIT box. Select the EG30 Stock Rom in the PDA box. Cross your fingers, and Start the process.
If the process Passes (Green), then EG30 Stock should start booting up!
If you're cool with that, you're done. Otherwise, use e4gtauto-sfx to root and install CWM, then flash a *good* ICS rom such as Phantom's Blazer Rom. :good:
* one small note though, using the Standard PIT fix, will decrease your internal storage from 16GB, to a total of 8GB. There are other PIT files you could try to get some of that space back, or just write it off as a loss, and get a bigger MicroSD card.
* one small note though, using the Standard PIT fix, will decrease your internal storage from 16GB, to a total of 8GB. There are other PIT files you could try to get some of that space back, or just write it off as a loss, and get a bigger MicroSD card.
After trying to follow about 3 or 4 different threads on this issue, I finally came across the guide here for the Galaxy Note: ATTENTION! my way out of a MMC_CAP_ERASE brick! Lucky for E4GT owners with the brick issue, it works for us too! (brick issue meaning your phone powers on, and you can get in to recovery, but can't format /data or install a rom)
I just tried this today, and so far so good. First off, the guide is worth a read to understand the issue, and how they went about solving it ...but we'll save all that reading for afterwards... :silly:
Head over to the ATTENTION! my way out of a MMC_CAP_ERASE brick! thread, and scroll down to the section Update: instructions for unexperienced users
Read those instructions carefully, and make sure you are using the 16GB file from pits-patched-standard.zip
Now open up ODIN. Make sure your phone is plugged in and in Download Mode (When phone is off, hold down Power and Vol Down until you see the warning screen). There should also be a yellow box in ODIN meaning your phone is ready.
Choose the 16GB PIT file in the PIT box. Select the EG30 Stock Rom in the PDA box. Cross your fingers, and Start the process.
If the process Passes (Green), then EG30 Stock should start booting up!
If you're cool with that, you're done. Otherwise, use e4gtauto-sfx to root and install CWM, then flash a *good* ICS rom such as Phantom's Blazer Rom. :good:
* one small note though, using the Standard PIT fix, will decrease your internal storage from 16GB, to a total of 8GB. There are other PIT files you could try to get some of that space back, or just write it off as a loss, and get a bigger MicroSD card.
So after months of trying...flashing all the one clicks they showed and of odining stocks and ics I just got to flash al el26 modem and the calks format all and cyanogenmod 9?!?! and thats all?! or I have to do the galaxy note page that is shown?! confuseed
FYI, CWM Touch recovery has also caused some problems with BlazerROM. I don't know if this information would help figure out the issue, but i'll bring it up just in case.
A few people were on the 'Hitman' kernel (comes with Touch recovery) and tried to flash BlazerROM v3.8 (latest at the time) and got stuck at boot loops or would just hang at the Samsung logo. People were able to restore back to a nandroid of v3.7 though. Some people used the one-click ODIN'd back to EL29 stock without issue as well. If you look at the BlazerROM thread in the dev section, it starts around page 417. PhantomHacker also suggests not using hitman (read: touch recovery) to flash his ROMs.
So it seems CMW Touch Recovery is the common denominator, but folks in the BlazerROM thread were able to restore successfully, either through nandroid backups or odin. I'm wondering if its the combination of touch recovery and the FBxx leaks that's causing the /data corruptions.