So you came from ICS StuNNeR - 1.4.26.1 after that the rest Official Ics with wiping and reseting.*
the other guys i read in xda there were incidents that nag wipe ug reset sila wala manpud naonsa. Bec the thing is during sa time ics custom rom sila ni balik sila sa stock GB and erasing to default then install a new fresh official ICS from then on...lipat lipat pud sila with wiping or hard reseting in which nothing has happened..I`m not sure sammy put the ICS kernel that affects the /data partition in the eMMC chip eventually destroys their own product for this. its maybe a new set of configuration that enables the conflicts between custom roms and the official?...sa ako lang ne 2cents IMHO hehe!![]()
yeah. I think google code ang problema. gikan man nila ang code gibasihan sa kernel. typo daw instead of HEX 0x19 decimal ang gigamit. Don't know the details naa to sa gi post sa XDA news. Nag test nasab sila daw og fix nga mo unlock sa chip kai matud nila na lock ra daw ang eMMc.
According to the famous Google expert 'Ken Sumrall' - in his own interpretation, the eMMC chip holds the binaries where it contains the bootloaders and stuffs to make the phone bootup... there is a way to unlock the chip but it needs a very low hardware and software programming (series of assembly codes and registers) to alter the register blocks on the chip. For every ExyNos running smartphone that Samsung markets today... don't get me wrong, there is 1 or more eMMC chip on that motherboard.
Going back, a Superbrick is by definition when your phone is completely dead.. NO BOOT, NO POWER just completely dead.
If you can still bootup in download Mode then by definition, you are not affected with the Superbrick bug at all. It is just a soft brick where you can painstakingly revive by altering the factory.ifs and re-partitioning your phone and skipping some of the bad blocks that it had incurred when you wiped it before.
Great explanation J.Abz. Usually lang before sa GB, even if di nimo ma boot into android (but boot into download mode) imong phone you can just flash the firmware again using Odin or Kies, but in ICS even if you can boot into download mode, mo ungot siya sa formating /data...
Last edited by comicGeek; 05-30-2012 at 03:59 PM.
^^ that is because ICS has a different file system than that of stock GB.
Kudos to Samsung for fixing my phone - motherboard change.
On the bricking issue here is Chainfire's report:PLEASE READ THIS ENTIRE POST BEFORE FLASHING, IT IS IMPORTANT
By now you have undoubtedly heard about bricking issues on the Galaxy Note, and various other devices. There is a bug in the Samsung stock ICS kernels that can trigger flash corruption and hardbrick your device.
There is a kernel source patch that works around the problem. It doesn't fix it, it just makes sure the problem isn't triggered. As you may or may not know, CF-Root's are not built from source, they are binary modifications to Samsung stock kernels.
As such, it is impossible for me to apply that patch to the source. I have received quite a bit of criticism from people who think they know what they are talking about for not implementing this patch - but as you may understand from the above, there's nothing I can do about it for CF-Root. The bug will disappear from CF-Root kernels as soon as Samsung fixes the issue in their builds, and not earlier.
However, I have patched the CWM included in the v5.6 CF-Root kernels, so CWM will no longer trigger the bug. But, I cannot be 100% certain that patch works. I have done about 50 restores and wipes today (both can trigger the bricking bug) and my device is still fine. But, I may have gotten lucky, or my device may not be affected at all.
In the same way, we will not know which stock Samsung kernels do or do not have the bug. Until they update their source and we see the problem is fixed (or Samsung outright tells us), any Samsung firmware release is suspect - and we won't know if the bug is present until somebody hardbricks on that kernel
Thus keep in mind, while I think CWM recovery will no longer trigger the problem (but I cannot guarantee it), the problem *is* actually still present in the kernel itself. As far as we (and the Android developer who released a lot of information about this) know, nothing else triggers the code that triggers the bug, but to be safe, I wouldn't be using the factory reset function in Android itself, or anything like that.
Beware: update.zip's can trigger the bug if they use "format" commands!
There is and cannot be any guarantee for CF-Root. You use it at your own risk. If you wan't to be safer, use a custom-built kernel of which the developer claims the problem is patched.
Planning to get the Galaxy Note within this week (either sa DB Gadgets or Kimstore).
Ask lang ko:
- how do you determine kung asa na region ang phone gikan (intend to upgrade to ICS later).
- unsay safest way to upgrade to ICS, murag kuyawan man ta basa aning brick Notes after upgrade?
- coming from Gingerbread okay lang ba upgrade to any official release ICS without danger of
bricking the Note?
- I understand naa chance ma brick ang Note if mo-wipe from recovery. Applicable ni cya sa GB or sa ICS lang?
Sorry mga bro, newbie gyud ko aning Android.
TIA.
why online? when you can get it here and maka pili paka barato naman guro ni 27-28t nlng ug installmnt pa with recibo namagamit nimo sa local samsung service center when you want to upgrade to ics. you dny have to DIY (do it yourself)kay
under warrnty and free man mag upgrade sa Samsung center bisan balik balik kapa if your not satisfied.
FYI:
May 2012 ICS
firmware update release from KiesCountry/Carrier
P-Code Android Version PDA CSC Phone Stock ROM
Austria ATO ICS 4.0.3 N7000XXLPY N7000ATOLP2 N7000XXLPT
Bangladesh TML ICS 4.0.3 N7000DDLP8 N7000ODDLP5 N7000DDLP4
Hong Kong TGY ICS 4.0.3 N7000ZSLPF N7000OZSLPF N7000XXLR1
India INU ICS 4.0.3 N7000DDLP8 N7000ODDLP5 N7000DDLP4
Indonesia XSE ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Germany DBT ICS 4.0.3 N7000XXLPY N7000OXALPY N7000XXLPT
Malaysia XME ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Netherlands XEN ICS 4.0.3 N7000XXLPY N7000XENLP1 N7000XXLPT
Nepal NPL ICS 4.0.3 N7000DDLP8 N7000ODDLP5 N7000DDLP4
Philippines XTC ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Philippines SUN XTE ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Philippines Smart SMA ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Philippines Globe GLB ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Poland XEO ICS 4.0.3 N7000XXLPY N7000OXXLP5 N7000XXLPT
Singapore XSP ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Singapore SingTel SIN ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Singapore Starhub STH ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Singapore M1 MM1 ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Sri Lanka SLK ICS 4.0.3 N7000DDLP8 N7000ODDLP5 N7000DDLP4
Turkey TUR ICS 4.0.3 N7000XXLPY N7000OJVLP6 N7000XXLPT
Taiwan BRI ICS 4.0.3 N7000ZSLPF N7000OZSLPF N7000XXLR1
Thailand THL ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Vietnam XEV ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
Vietnam XXV ICS 4.0.3 N7000DXLP9 N7000OLBLP6 N7000DXLP5
june released
europe/UK XEU/CPW ICS 4.0.3 N7000XXLQ2 june released...![]()
Similar Threads |
|