2012-09-11: update. So far 12 xda users reported a bricked gt8.9. Don't join them...
2012-09-08: update. I will be out of town this weekend. I will keep the top post summarized once per day (if there is news)
Current knowledge is: (note: knowledge on this issue is still evolving and may become more accurate in future)
there is a serious bug in a hardware EMMC chip (or its driver) used in many Samsung devices
in GingerBread / HC this bug was not triggered
in its ICS kernels Samsung has used a feature to wipe EMMC in a way that triggers the bug in the chip
when xda developers used Samsung ICS kernel sources to continue work with (e.g. as kernel for the recovery - which has separate kernel from the ROM itself), they pulled the issue into their work
this has caused many bricks on many many different Samsung devices.
gt8.9 tab's CWM 6.0.1.2 includes this ICS kernel, and is dangerous if used to wipe /system or any other wipe (theoretically, that includes nandroid restore)
gt8.9 earlier CWM are believed to be safe (5.1.2.6, 5.5.0.4, 6.0.0.8, 6.0.0.8_alternate)
potentially, even update-binary inside a flashable .zip can be dangerous: IF it includes a specific (ext4) module from faulty ICS kernel, and IF the updater-script does a format(). So far there are no reports of such so far on the gt8.9
potentially, the same issue can be triggered from the kernel in the ICS ROM (although less risky, as that kernel is normally never used to wipe the boot or system partition). Nobody has reported issues after doing a "factory reset" from within Samsung p7310 stock ICS (USA region). We don't know if the ICS kernel inside that ROM is dangerous. Still, you are (till further notice) adviced not to use that feature inside any ICS rom. If you do, report here!
2012-09-07: v1 (modified)
Still more people are reporting bricking their device, after using CWM 6.0.1.2, even though it's already known 24-48 hours that this recovery can lead to this error.
I will link some threads in a follow up where the issue is discussed. Still, I recommend to try focus the discussion to just 1 thread... It will be easier on us all.
Proposal
- I propose to bump this thread hourly or so, for a few days at least, so that everybody has a chance to see it.
- There are many threads that discuss this issue. Try to keep the discussion a little focussed, don't continue posting in 6-7 different threads. Use this one
- If you see this disappearing from page 1 in General Forum, just reply with either:
* good idea, keep bumping
* stupid, stop it already
- If you heard of this issue here first, hit thanks
Thanks
Links
CWM 6.0.1.2 was made available in the CM9 thread (dev forum) around Sep 4.
By Sep 5 the first reports of bricked devices were coming in. The CM9 thread, starting from post 1066 (link, quote below) has been all about that for several pages. If you have found something really useful, reply on that dev thread. Do not spam it though.
kallt_kaffe said:
FYI, I might have bricked my P7310 so development is paused for now. Was flashing a CM10 build yesterday that I was experimenting with when it got stuck at "Formatting /cache" and after a while I did a long press on power thinking it would recover from it.
However I'm now stuck with black screen and it identifies itself as APX in Device Manager.
(...)
Click to expand...
Click to collapse
If you want to discuss in general, mention you have the same issue, ask for updates, etc, just reply here
other threads started for same issue. just for reference...
http://forum.xda-developers.com/showthread.php?p=31177035
http://forum.xda-developers.com/showthread.php?p=31158609
http://forum.xda-developers.com/showthread.php?p=31238668
http://forum.xda-developers.com/showthread.php?p=31172928
http://forum.xda-developers.com/showthread.php?t=1875756
Reserved
Sent from my HTC Desire using xda app-developers app
I hope those with the problem get a fix soon, i wouldnt be able to sleep if that happended to me
Sorry and up for this thread to warn others
Sent from my GT-P7300 using xda app-developers app
Im not really sure what makes this bugs happen..
But this issues is not new for me in galaxyNOTE gt n7000 and Sgs2 I9100 we call this as EMMC superbrick..
It happen in ICS kernel stock if you operates some EMMC_CAP_ERASE in kernel such as wiping your data or system.. Format.. Or deleting large file in recovery operation or factory reset in EMMC with firmware revision 0x19(firmware of this chip)..
It cannot recover with regular utility like JTAG coz This superbrick makes EMMC faulty in /data partition or /system partition blocks..
If you go to Samsung Service Centre.. Your device should be on mainboard replacement..
Sorry for my english.. You could use this app for testing your emmc has a bug or not..
If you had the emmc bug.. Dont use any recovery from ICS sources until someone with expert knowledge confirm that everything is fine..
Please read this thread for complete issues and discuss..from recognized developer entropy512
http://forum.xda-developers.com/showthread.php?t=1633938
I think it not about cwm version but the kernel is..
THANKS for makes this
Ups seems the i got the bug :-/
Sent from my GT-P7300 using xda app-developers app
I too got the bug and CWM 6.0.0.8 but my tablet will stay with AOKP for the time being until the dust settles.
Could somebody tell me what is the latest safest CWM to use for flashing KK's CM10 preview ROM.
Bump.
Cwm 5.1.2.6, 5.5.0.4 and 6.0.0.8 have all been around long enough to conclude that they are safe (in terms of this emmc bug)
You guys have a twrp?
Sent from my SGH-I727 using xda premium
Well, crap on a cracker...
Okay, so after reading the dumbed down facts about the issue at hand, it would seem that the latest CWM is not completely at fault for bricking devices. This most likely happened to users who were already on ICS and who already had a kernel that will allow the EMMC_CAP_ERASE to execute over a chip incapable of handling it.
The reports of using the latest CWM and successfully updating to ICS experimental builds without bricking most likely came from people going from stock Honeycomb to ICS?
Any of this true?
de3pkeeper said:
Well, crap on a cracker...
Okay, so after reading the dumbed down facts about the issue at hand, it would seem that the latest CWM is not completely at fault for bricking devices. This most likely happened to users who were already on ICS and who already had a kernel that will allow the EMMC_CAP_ERASE to execute over a chip incapable of handling it.
The reports of using the latest CWM and successfully updating to ICS experimental builds without bricking most likely came from people going from stock Honeycomb to ICS?
Any of this true?
Click to expand...
Click to collapse
Yes... You got the point..
strange.
What I understood (not necessarily correct) - simplified and without pointing fingers
the fault is likely in the kernel that is in that recovery 6.0.1.2.
there is another kernel, for the "Android OS", and it could hypothetically contain the same bug, but noone has found any ROM kernel to have the bug.
some developer tried to integrate a (Samsung?) ICS kernel (as released in the opensource for the ROM) in the CWM kernel -
some other developer copied that first developer's work and compiled it for the 8.9 tab
lots of bricked tabs.
So that's not correct? I've been reading about this all day, but I could have missed something in the last few hours.
de3pkeeper said:
The reports of using the latest CWM and successfully updating to ICS experimental builds without bricking most likely came from people going from stock Honeycomb to ICS?
Click to expand...
Click to collapse
I think kallt_kaffe said he flashed at least 10 ROMs using 6.0.1.2 before it failed on him...
Let me look if I can find that back.
orlandoxpolice said:
You guys have a twrp?
Click to expand...
Click to collapse
I've read about that recovery on the 10.1 forums, and on the sub-forum for Galaxy Tab 8.9 SGH-i957 (LTE, 4g version).
But never seen it for the P7300 and P7310.
fred_be9300 said:
I think kallt_kaffe said he flashed at least 10 ROMs using 6.0.1.2 before it failed on him...
Let me look if I can find that back.
Click to expand...
Click to collapse
First.. This bug it doesnt depends how many times you use.. Its random.. Maybe just once or twice or ten times when you wipe..
Second..hardbrick and superbrick is different..superbrick cannot recover with jtag because The chip is broken..
I hope this issue not happen to our tab..we need some testing and investigation..but who can do that?
I guess all samsung device with that kind of type EMMC chipsg is risky when in ICS..
this bug existed for the skyrocket as well as soon as ICS was released, it never existed with gingerbread. seemed completely random as well.
One dumb question: how about if you have already installed ICS kernel. By using CWM 6.0.0.8 or version below and do restore, wipe, etc, will it also brick the tab? Could someone confirm this if it is safe? Or has experience with lower CWM and survive the brick bug? Thanks
nexus_g said:
One dumb question: how about if you have already installed ICS kernel. By using CWM 6.0.0.8 or version below and do restore, wipe, etc, will it also brick the tab? Could someone confirm this if it is safe? Or has experience with lower CWM and survive the brick bug? Thanks
Click to expand...
Click to collapse
All indications are that CWM 6.0.0.8 is 'safe'. The problems appeared to start with 6.0.1.2.
Bump... Just hoping no others get brick from known issue
Related
Please help me !
i am new user for android and i want using a latest version
on my galaxy Note GTN7000
please if you want show me where is the best version of the latest android system and workin without bugs !
hoc1972 said:
Please help me !
i am new user for android and i want using a latest version
on my galaxy Note GTN7000
please if you want show me where is the best version of the latest android system and workin without bugs !
Click to expand...
Click to collapse
I would advice you to wait for official release mate
Right now there are couple of very good ICS ROMs but there is also a risk of bricking your note because ICS leaks kernel are somewhat faulty
Better safe than sorry
matius44 said:
I would advice you to wait for official release mate
Right now there are couple of very good ICS ROMs but there is also a risk of bricking your note because ICS leaks kernel are somewhat faulty
Better safe than sorry
Click to expand...
Click to collapse
I agree. Hearing all the issues, not even about bricking frightens me. Although for those who have successfully installed ICS on the Note, I do envy you because stock android looks amazing! However, once official ICS is released by Samsung devs would prefect stock ICS I bet. =P
I have just come back to stock after using ICS ROMS.
I encountered a lot of problems such as:
not being able to transfer files from pc to note.(i had to take out SD card and use an adapter).
Phones rebooting randomly alot.
When trying to flash in recovery, the flashing procedure kept on freezing.
I think it is safe to stay on stock, where you will be problem free until official ICS release.
BlitzyMannna said:
I have just come back to stock after using ICS ROMS.
I encountered a lot of problems such as:
not being able to transfer files from pc to note.(i had to take out SD card and use an adapter).
Phones rebooting randomly alot.
When trying to flash in recovery, the flashing procedure kept on freezing.
I think it is safe to stay on stock, where you will be problem free until official ICS release.
Click to expand...
Click to collapse
I've never had any of these problems that you mention. I don't think most users have either.
Can't transfer files? USB storage is now native to most ICS ROMS.
Random rebooting? Sounds like a personal problem to me.
Flashing in recovery and freezing? Okay, yeah that's a common problem...but it's an easily fixed problem, and it mainly comes about because you don't have proper root to begin with.
There's also some evidence recently that a few ICS kernels can cause permanent emmc (internal storage) failure that can not be revived. So yes, you probably shouldn't be flashing ROMS to begin with, as it sounds like you don't have much experience. This would put you in over your head for sure. It's best to wait until you've lurked around the boards for a bit and to wait for a stable and official ICS base to come out. Best of luck!
matius44 said:
I would advice you to wait for official release mate
Right now there are couple of very good ICS ROMs but there is also a risk of bricking your note because ICS leaks kernel are somewhat faulty
Better safe than sorry
Click to expand...
Click to collapse
So matius, are you saying that we should not use ics custom roms ?
Abagnale said:
So matius, are you saying that we should not use ics custom roms ?
Click to expand...
Click to collapse
Lol
Personally am sticking to my current setup (ICS Stunner 1.4.19 + LP6) mainly because I have absolutely zero issues so far with great battery life, why fix something not broken? but also because of the recent news of the faulty kernels
matius44 said:
Lol
Personally am sticking to my current setup (ICS Stunner 1.4.19 +- LP6) mainly because I have absolutely zero issues so far with great battery life, why fix something not broken? but also because of the recent news of the faulty kernels
Click to expand...
Click to collapse
I am tired of the rumors about ics customs plz check your PM
man when i read that i was like dam that is not a joke, and bing bang boom back to GB darky 3.4.1 rom is the greatest, as sorry ICS leaks does not worth it with all its problems it already has and now this scary threat of bricking my device due to kernels in those leaks, no way i am on GB again until an ics official release
how many of you did the same , and which rom did u go back to and why
thanks god i did not brick my device, and never ever will i jump into any leaked roms that are not first officially released
I went back to Stock + rooted (PC Odin flash) from ICS stunner (which is a great ROM btw) after reading about the risks of the leaked repack kernels from Entropy512, not to mention the various horror stories by those less fortunate than myself.
There but for the grace of God go I...
I'm going to go for the CM9 version once its a bit more mature (looks really good already on build #3), or wait until a safe kernel is brought into ICS Stunner.
The official ICS might even come out soon...not holding my breath though
Sent from my GT-N7000 using xda premium
I've flashed many ICS ROMs, but I was lucky as I stick to Redpill Recovery procedure of going back to GB and never tried anything with ICS kernels (well almost as I used their CWM Recovery to flash Abyss Kernel 4.2 with Redpill). I'm daily using CheckROM with jKay MOD + DarkyOTA (for easier modifications) and for now I'm happy with it. I've checked what ICS has to offer and now I'm waiting for official version.
There is no need to stick with GB ,I just upgraded from GB to cm9 for the first time
Cm9 contains a safe kernel so you don't need to worry about flashing it .
Been on ICS for a week now
First on AOSP ICS 4.0.4 for awesome UI, next Criskelo ROM 4.0.3 for better speed.
So far so good!
Still doesn't die on me!!
Go ahead and flash it baby!
Dun be a wuzz!
Any recommendations for other ICS variants?
I am still on ICS Stunner and will stay on it. I dont see a reason for changing a stable system with awesome battery life and such great daily performance use.
Loved Stunner's roms but reverted back to GB because of the hard bricks.
Now running CheckRom V6 with AbyssNote 4.2 and Nemus Launcher. Very stable rom, fast and good battery life.
As soon as CM9 matures a bit or Stunner implements the open source kernel I'll probably flash back to ICS. Who knows, maybe Samsung will release ICS in a few weeks.
Sorry but I made a Poll here in Q&A in which I ask who hardbricked the Note with one of those kernels. Where are those bricked devices?
So far no user reported this in this boards section. At least I havent seen anyone.
FiremakerP said:
Sorry but I made a Poll here in Q&A in which I ask who hardbricked the Note with one of those kernels. Where are those bricked devices?
So far no user reported this in this boards section. At least I havent seen anyone.
Click to expand...
Click to collapse
People with a dead phone might just be upset instead of filling out random polls
Here are a few unlucky people:
http://forum.xda-developers.com/showthread.php?t=1629338
http://forum.xda-developers.com/showthread.php?t=1627443
http://forum.xda-developers.com/showthread.php?t=1619630
While his advice is to the leak in general, I think it is VERY clear the problem (SO FAR) has ONLY been caused by the botched Kernel by Angelom and the 1 bad version of Stunner (before fixed).
No one (reported) has EVER been bricked by any other leak/ICS Build on the Note.
There is always a risk, it could happen again with another modified ICS Kernel Build, but it is my opinion based on plain common sense and the facts that no one is going to be bricked using the ICS Leaks currently being used by MANY and having never had a problem.
crawlgsx said:
While his advice is to the leak in general, I think it is VERY clear the problem (SO FAR) has ONLY been caused by the botched Kernel by Angelom and the 1 bad version of Stunner (before fixed).
No one (reported) has EVER been bricked by any other leak/ICS Build on the Note.
There is always a risk, it could happen again with another modified ICS Kernel Build, but it is my opinion based on plain common sense and the facts that no one is going to be bricked using the ICS Leaks currently being used by MANY and having never had a problem.
Click to expand...
Click to collapse
The problem resides in the leaked Samsung kernels that's the base of any and every custom ICS rom currently released in the dev section except for the CWM9 roms.
I've flashed a crapload of ICS roms in the past two weeks, I think I've been alternating between roms at least 15 times and wiped even more but that's absolutely no garantee that my luck won't run out at some point. The moment I've read the posts from people that absolutely know what they're talking about I reverted back to a GB rom. Waiting a couple of weeks for an official update beats not being able to use my Note.
Soft bricking, losing all your data, instability, battery drain, those are the 'normal' risks you should be prepared for when flashing any rom but hard bricking your device beyond JTAG repair is a major thing. It's a garanteed motherboard replacement and Samsung will not give you warranty.
crawlgsx said:
While his advice is to the leak in general, I think it is VERY clear the problem (SO FAR) has ONLY been caused by the botched Kernel by Angelom and the 1 bad version of Stunner (before fixed).
No one (reported) has EVER been bricked by any other leak/ICS Build on the Note.
Click to expand...
Click to collapse
You are wrong, there have been plenty.
I'm currently using Stunner with the DAFUQ kernel. Its kinda buggy but it still beats Gingerbread. Not gonna give up my precious tablet UI!
i am one of those suckers that got bricked by this issue. it is a risk when flashing experimental leaks. it sucks the big one but i knew this was a possibilty when i started flashing. it happened after i had flashed dozens of times with different roms and mods. you just have to suck it up and realize this is always a risk no matter what you are flashing or whether you have done this before or not. luckily i had everything backed up so i have not lost much except my note for a few weeks and maybe a couple of hundred dollars. i am still waiting for mine to be repaired.
bioweb said:
The problem resides in the leaked Samsung kernels that's the base of any and every custom ICS rom currently released in the dev section except for the CWM9 roms.
I've flashed a crapload of ICS roms in the past two weeks, I think I've been alternating between roms at least 15 times and wiped even more but that's absolutely no garantee that my luck won't run out at some point. The moment I've read the posts from people that absolutely know what they're talking about I reverted back to a GB rom. Waiting a couple of weeks for an official update beats not being able to use my Note.
Soft bricking, losing all your data, instability, battery drain, those are the 'normal' risks you should be prepared for when flashing any rom but hard bricking your device beyond JTAG repair is a major thing. It's a garanteed motherboard replacement and Samsung will not give you warranty.
Click to expand...
Click to collapse
very true man and same here.
was a very happy and heavy flashoholic in ICS untill the warning. Have been lucky sometimes by just switching to stock from ICS by Abyss kernel only not red pill even shutting down system instead of rebooting to Red pill. Lol but even after all this damm-i-may-be-hard-tym-screwed i was quite a lucky fella. Even ignored the kernel Warning by Entropy too, but lol man, a comment by a user in stunner that even copying a file more then 200mb to the Note can also fry your system, dammm i was like stoned. Even didnt tried it out against my such a good luck and bamm yesterday i was back to GB.
Even right now i am a happy flasholoic in GB by trying every version here and switching between them with a ratio of 2roms/day.
went back to RocketRom V23 myself today... will wait it out with CM9 mature versions.
I'm going to stick with ICS Stunner for the moment. I always flash Abyss and use RedPill for all 'Recovery' related things anyway.
I'm sure that soon all ROMs will be rebuilt without the leaked kernels and have all the features we currently have but, until that time, I'll keep using the leak based ROMs.
It would bother me, taking a 'step back' to protect myself against something that 'might' happen.
This is all personal preference though, I certainly do not advocate or recommend that anyone do the same as me.
Hey, guys,
I'm talking about this thread http://forum.xda-developers.com/showthread.php?t=1633943
Are these issues resolved somehow? I'm sitting on ICS Stunner ROM and I'm afraid to do anything serious with my phone.
Shouldn't there be fixes when Samsung released official AOSP source of Notes' ICS?
Or am I missing something? I really want to do a completely clean install of some ROM, because my current ROM (the newest version of Stunner) works terribly, forcecloses, slugish, freezing all the time.
Can the behavior of my phone have something to do with the problem discussed in the thread I linked? (I don't understand anything in that thread )
Hi
The issues regarding superbrick arent completely resolved. But there are Kernels for ICS wich contain a workaround. And so far noone has reported bricking with them.
It seems like the official kernel source from sammy still contained that bug. But now it has been bypassed. Still noone is completely sure yet that they are 100% safewhen it comes to wiping etc.
There is also a workaround to repartition the data section effectively bypassing any damaged areas for anyone that has a brick and no warranty.
This of course reduces the data partitions size, and it's still pot luck as to how much damage would occur.
It's also a pretty tricky operation.
Sent from my GT-N7000 using xda premium
So if I want to install a stock ICS rom (the newly released one, not the old leak), I should dooo, what? Which is the safe kernel (the one with a workaround)?..
Sorry for stupid questions..
Probably worth flashing stock ics ROM, with a custom kernel that's safe. Probably best to do it in mobile Odin. Make sure you extract the firmware file and only select ROM partition, then separately point to kernel.
Sent from my GT-N7000 using xda premium
I think its better to be in Stock rom what we got and never do any experiment, instead of wasting time on it to get very little stuff with high risk.
even if some work around solution is there, its very hard to understand and not all will be doing that.
I totally agree. Wait for safe ics kernels or use modified Cm9's for now.
Sent from my GT-N7000 using xda premium
So just to be sure:
I use this ROM http://forum.xda-developers.com/showthread.php?t=1646088
And a kernel? You mentioned CM9 kernel. How do I get it? Can I find it in here http://get.cm/?device=n7000 (I mean is it somehwere in the .zip?)
Or are all those franco/abbyss kernels also considered relatively safe?
Thanks for your patience
No you cant use Cm9 kernels with stock rom. If you flash a stock rom you get a stock kernel included
What if I flash chainfires kernel first and the flash stock rom?
Cyrusas said:
What if I flash chainfires kernel first and the flash stock rom?
Click to expand...
Click to collapse
No, either use a GB kernel or use Franco's #3+, or SpeedMod K3-3, CF's ICS kernels are NOT safe.
Or any other JB by Samsung?
Is it?
From the Moderator
Already posted....... THREAD CLOSED
There are a million threads for this. Why can't you search first? Reported.
Sent from my GT-N7000000000 using Tapastalker 2
Haven't heard of any rom from Spamsung for n7000 yet
There may be a bunch of threads but i am searching for hours not finding anything definitive.
@nokiamodeln91
I use the word rom in traditional sense. So yes, the /system partition is intended not to be modified in daily use. I would consider that a rom, if made by the device manufacturer or someone else.
Always when I ask something on XDA where the answer is buried in spam or not present I get flamed or ignored?
And people seriously waste precious battery power for this?
Whats up with the Note forum?
Back in Desire Z forums people were much nicer.
There is nothing wrong in having a little fun... Take it in a positive way. Don't be defensive. Forums are icer to read when you get to laugh sometimes.
And for your question.? What do you mean by safe? Related to kernel and BrickBug.?
There have been comments that samsung has patched something in the new 3.0.31 kernel JB suppressing the bug. Not sure.. But there is philz kernel which is definitely safe
As per rom perspective : its a very nice rom specially the eybee s
What's up is this is answered in pretty much every LSA thread and there is no need for you to make a thread for such. Instead of your long response you could've easily searched and found your answer.
Since you can't search here is the answer-
1. there have been SOME reports that LSA may cause data corruption after a while requiring a clean install.
2. The stock kernel MAY be safe from emmc secure erase brick bug - this hasn't been confirmed.
3. Philz kernel nonetheless suppresses secure erase making it safe even if Samsung hasn't fixed the issue
4. Note- LSA is not most current leak
Sent from my GT-N7000000000 using Tapastalker 2
@nokiamodeln91
I guess I have gotten too serious in the last few months.
@asf58967
Thanks for the info, thats what I needed, a confirmation of something, even a confirmation that its unknown if stock is safe.
I actually wanted to specifically stock wipe, as Philz Kernel rocks but maybe still doesnt wipe away whatever it is, that tells the system to expect an encrypted partition when there is none.
Hi Everyone
After waiting for a year now and it seems that Samsung didn't released any newer updates for my Note GT-N7000 at my country. I was hoping for them to release an update to prevent that "MMC_CAP_ERASE bug? that causes hardbrick" that i have been hearing around here..
But now i got tired of waiting and Now I want to try to root/flash to a safe custom rom, Since i am currently having some problems with my Note now. It's acting a little weird like apps not functioning properly and deleting a small MB file on Internal Memory it takes very long to get it deleted Annoying artifacts appearing during at Dark or Black scenes while watching a video. Using Earphones while watching a video the audio sometimes got muted itself then for a few seconds it resumes back with audio back on repeatedly.
I have only experience on rooting and flashing my Galaxy Tab GT-P1000 but i had a soft brick thanks to the person who posted misleading instructions that causes this to happen. But eventually i managed to recovered from the soft brick and successfully flashing to a JB custom rom
Yeah before you asked me "have you read this Important thread ? http://forum.xda-developers.com/showthread.php?t=1329360 " Yes I have already read everything on the first post by dr ketan at this thread http://forum.xda-developers.com/showthread.php?t=1329360
Anyway, Here is my Information i found on my Note.
Model Number is GT-N7000.
Android Version 4.0.4 Stock ICS.
Baseband version N7000DXLR1.
Kernel Version 3.0.1.5-N7000DXLR5-CL968032
Build Number IMM76D.DXLR5
Here are my questions,
[Q Number 1]
I have already read everything on the first post by dr ketan. I notice there's so many of methods to root the Note. But I'm not sure which one is the safest and easiest method to Root and Flash Hopefully someone here is kind to guide me through the process since this is my first time rooting and flashing on a Note GT-N7000 running on Android 4.0.4 Stock ICS.
[Q Number 2]
There's tons of JB custom roms everywhere! I'm not sure which one is the best and popular one. I'm looking for a fast and stable Jellybean custom rom that are currently available for my Note GT-N7000.
I will be waiting and checking this thread regularly
dc2mx said:
Hi Everyone
After waiting for a year now and it seems that Samsung didn't released any newer updates for my Note GT-N7000 at my country. I was hoping for them to release an update to prevent that "MMC_CAP_ERASE bug? that causes hardbrick" that i have been hearing around here..
But now i got tired of waiting and Now I want to try to root/flash to a safe custom rom, Since i am currently having some problems with my Note now. It's acting a little weird like apps not functioning properly and deleting a small MB file on Internal Memory it takes very long to get it deleted And annoying artifacts appearing during at Dark or Black scenes while watching a video.
I have only experience on rooting and flashing my Galaxy Tab GT-P1000 but i had a soft brick thanks to the person who posted misleading instructions that causes this to happen. But eventually i managed to recovered from the soft brick and successfully flashing to a JB custom rom
Yeah before you asked me "have you read this Important thread ? http://forum.xda-developers.com/showthread.php?t=1329360 " Yes I have already read everything on the first post by dr ketan at this thread http://forum.xda-developers.com/showthread.php?t=1329360
Anyway, Here is my Information i found on my Note.
Model Number is GT-N7000.
Android Version 4.0.4 Stock ICS.
Baseband version N7000DXLR1.
Kernel Version 3.0.1.5-N7000DXLR5-CL968032
Here are my questions,
[Q Number 1]
I have already read everything on the first post by dr ketan. I notice there's so many of methods to root the Note. But I'm not sure which one is the safest and easiest method to Root and Flash Hopefully someone here is kind to guide me through the process since this is my first time rooting and flashing on a Note GT-N7000 running on Android 4.0.4 Stock ICS.
[Q Number 2]
There's tons of JB custom roms everywhere! I'm not sure which one is the best and popular one. I'm looking for a fast and stable Jellybean custom rom that are currently available for my Note GT-N7000.
I will be waiting and checking this thread regularly
Click to expand...
Click to collapse
The safest and easiest way to flash ROM and get ROOT at the same time is using Odin Mobile, which offers option for getting ROOT.
You can use Stock ROM LT4.
For most popular custom ROMs : Eybee1970, Team Union, Alliance, Sweet,
ThaiDai ROM for slim and mutillanguage, Glory ROM also for multilanguage with mods.
There are a lot of other good ROMs here, you have to read more to find out what suits better to your taste.
dc2mx said:
Hi Everyone
After waiting for a year now and it seems that Samsung didn't released any newer updates for my Note GT-N7000 at my country. I was hoping for them to release an update to prevent that "MMC_CAP_ERASE bug? that causes hardbrick" that i have been hearing around here..
But now i got tired of waiting and Now I want to try to root/flash to a safe custom rom, Since i am currently having some problems with my Note now. It's acting a little weird like apps not functioning properly and deleting a small MB file on Internal Memory it takes very long to get it deleted And annoying artifacts appearing during at Dark or Black scenes while watching a video.
I have only experience on rooting and flashing my Galaxy Tab GT-P1000 but i had a soft brick thanks to the person who posted misleading instructions that causes this to happen. But eventually i managed to recovered from the soft brick and successfully flashing to a JB custom rom
Yeah before you asked me "have you read this Important thread ? http://forum.xda-developers.com/showthread.php?t=1329360 " Yes I have already read everything on the first post by dr ketan at this thread http://forum.xda-developers.com/showthread.php?t=1329360
Anyway, Here is my Information i found on my Note.
Model Number is GT-N7000.
Android Version 4.0.4 Stock ICS.
Baseband version N7000DXLR1.
Kernel Version 3.0.1.5-N7000DXLR5-CL968032
Here are my questions,
[Q Number 1]
I have already read everything on the first post by dr ketan. I notice there's so many of methods to root the Note. But I'm not sure which one is the safest and easiest method to Root and Flash Hopefully someone here is kind to guide me through the process since this is my first time rooting and flashing on a Note GT-N7000 running on Android 4.0.4 Stock ICS.
[Q Number 2]
There's tons of JB custom roms everywhere! I'm not sure which one is the best and popular one. I'm looking for a fast and stable Jellybean custom rom that are currently available for my Note GT-N7000.
I will be waiting and checking this thread regularly
Click to expand...
Click to collapse
to be cancelled
Bump for more replies
The safest and easiest way doesn't exist. It's up to you.
And best Rom threads and questions are simply against XDA policy, read the rules and you'll see.
Sent from my GT-N7000 using xda premium
ThaiDai said:
The safest and easiest way doesn't exist. It's up to you.
And best Rom threads and questions are simply against XDA policy, read the rules and you'll see.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks ThaiDai for XDA policy recall, hope you be back to Aachen. :good:
ThaiDai said:
The safest and easiest way doesn't exist. It's up to you.
And best Rom threads and questions are simply against XDA policy, read the rules and you'll see.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Hello there
I'm really sorry if i just break some of the rules here. I wonder if it's okay for me to just follow the recommended method 1A by dr ketan ? Now i am in PhilZ thread i suppose i have to find my own Galaxy Note Kernel Version first right ? which is DXLR5 so i guess i have to download this kernel here http://www.mediafire.com/?c2jmfqnwajw8ei1 .PhilZ-cwm6-DXLR5-OLB-v3.99 Then flash it in the menu called Stock Recovery (VolumeUP+HOME+POWER button)
I found out that my Baseband version has a DXLR1 in there. Should i be worry on this ?
The PhilZ kernel file listed v3.99 there. my Kernel Version is 3.0.1.5-N7000DXLR5-CL968032, Example when i managed to flash that kernel. I guess that my Kernel Version will changed to like 3.9.9.9 am i right ? or it is not okay to just flash to latest updated kernel like v3.99 ?
I hope it's okay to just answer my newbie questions here. I need someone to help me and tell me whether if i did it right or wrong.
Thank you very much
dc2mx said:
Hello there
I'm really sorry if i just break some of the rules here. I wonder if it's okay for me to just follow the recommended method 1A by dr ketan ? Now i am in PhilZ thread i suppose i have to find my own Galaxy Note Kernel Version first right ? which is DXLR5 so i guess i have to download this kernel here http://www.mediafire.com/?c2jmfqnwajw8ei1 .PhilZ-cwm6-DXLR5-OLB-v3.99 Then flash it in the menu called Stock Recovery (VolumeUP+HOME+POWER button)
I found out that my Baseband version has a DXLR1 in there. Should i be worry on this ?
The PhilZ kernel file listed v3.99 there. my Kernel Version is 3.0.1.5-N7000DXLR5-CL968032, Example when i managed to flash that kernel. I guess that my Kernel Version will changed to like 3.9.9.9 am i right ? or it is not okay to just flash to latest updated kernel like v3.99 ?
I hope it's okay to just answer my newbie questions here. I need someone to help me and tell me whether if i did it right or wrong.
Thank you very much
Click to expand...
Click to collapse
No problem when you see :
- Baseband DXLR1
- Difference between 3.99 and 3.0.1.5-N7000DXLR5-CL968032.The first is the Philz own version, the second is the Samsung one.
It's normal.
dc2mx said:
[Q Number 1]
I have already read everything on the first post by dr ketan. I notice there's so many of methods to root the Note. But I'm not sure which one is the safest and easiest method to Root and Flash Hopefully someone here is kind to guide me through the process since this is my first time rooting and flashing on a Note GT-N7000 running on Android 4.0.4 Stock ICS.
[Q Number 2]
There's tons of JB custom roms everywhere! I'm not sure which one is the best and popular one. I'm looking for a fast and stable Jellybean custom rom that are currently available for my Note GT-N7000.
I will be waiting and checking this thread regularly
Click to expand...
Click to collapse
1.As far as rooting method is concerned on said thread, all the methods are safe. there are pros and cons of different method and already mentioned on thread.
I do recommend 1A, as it will root device as well gives you protection from brick bug and without raising flash counter too. So in case you want to go that way, download LR5 philx kernel in zip version and flash from stock recovery.
2.See ROM selection is totally depends on own taste, you can never rely on others answer, but best way go through OP of custom ROM thread, read features mentioned, read some reviews/bugs and try it yourself. that's the only and best way.
dr.ketan said:
1.As far as rooting method is concerned on said thread, all the methods are safe. there are pros and cons of different method and already mentioned on thread.
I do recommend 1A, as it will root device as well gives you protection from brick bug and without raising flash counter too. So in case you want to go that way, download LR5 philx kernel in zip version and flash from stock recovery.
2.See ROM selection is totally depends on own taste, you can never rely on others answer, but best way go through OP of custom ROM thread, read features mentioned, read some reviews/bugs and try it yourself. that's the only and best way.
Click to expand...
Click to collapse
First of all, Dr Ketan Thank you very much for helping me with this. I really appreciate your help Yeah i understand what you're trying to mean about that custom ROMs I will take a look at all of them later.
But now I want to see if i got it right again. I will flash it after you give me the final confirmation i need :victory:
1. Find my own stock Kernel build code DXLR5 then go to PhilZ thread and find PhilZ Kernel that listed my Kernel code which is PhilZ-cwm6-DXLR5-OLB-v3.99 then download it After that Connect a USB cable to the computer + Note then copy the PhilZ kernel and place at Root dir of External microSD card then turn off Galaxy Note, then hold VOLUME UP + HOME + POWER button for a few seconds to boot in Stock Recovery Menu then flash it at there. am i right ?
Last question here, Finding a Custom Rom that suit my needs might take awhile since i haven't read all of them yet. But i wonder if it's okay to stay in Stock ICS Android 4.0.4 + PhilZ Kernel ?
dc2mx said:
1. Find my own stock Kernel build code DXLR5 then go to PhilZ thread and find PhilZ Kernel that listed my Kernel code which is PhilZ-cwm6-DXLR5-OLB-v3.99 then download it After that Connect a USB cable to the computer + Note then copy the PhilZ kernel and place at Root dir of External microSD card then turn off Galaxy Note, then hold VOLUME UP + HOME + POWER button for a few seconds to boot in Stock Recovery Menu then flash it at there. am i right ?
Last question here, Finding a Custom Rom that suit my needs might take awhile since i haven't read all of them yet. But i wonder if it's okay to stay in Stock ICS Android 4.0.4 + PhilZ Kernel ?
Click to expand...
Click to collapse
1.Yes, but remember you have to select zip version of kernel not tar
obviously there is nothing wrong to stay on stock with safe kernel till you couldn't find out best custom ROM for you.
dr.ketan said:
1.Yes, but remember you have to select zip version of kernel not tar
obviously there is nothing wrong to stay on stock with safe kernel till you couldn't find out best custom ROM for you.
Click to expand...
Click to collapse
Okay Yeah i got the signed version instead of that .tar version which is for ODIN.
Good News! i just flashed it and it works! I have SuperSU application installed. I really appreciate all your help that you have done dr ketan thank you very much. Now i have PhilZ CWM kernel. does it uses the same buttons to activate it like the stock recovery ? VOLUMEUP+HOME+POWER BUTTON,