Database Users

[Q] Confused... ICS leaks can brick the Note, will official releases do the same?

I'm sorry. I SWEAR I read tons of threads but things still aren't clear to me.
ICS leaks seem to possibly brick the Note.
But there are several threads with official ICS firmwares for the Note (ex: http://forum.xda-developers.com/showthread.php?t=1646088)
Can I use the official ICS firmware to upgrade my Note? Or should I wait a bit more?
Thanks!

From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel. What are you using now?

leppo said:
From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel. What are you using now?
Click to expand...
Click to collapse
Kernel says 2.6.35.7-N7000UBKK8
I suppose I'll stay on GB. Things look a bit scary even with the stock kernel!

The official can brick the note muaaahuahuahuahuuaaa
Seriously as the previous poster said only if you are into wiping and restoring you MAY be in danger
Sent from my iPad using Tapatalk

fjhuerta said:
I'm sorry. I SWEAR I read tons of threads but things still aren't clear to me.
ICS leaks seem to possibly brick the Note.
But there are several threads with official ICS firmwares for the Note (ex: http://forum.xda-developers.com/showthread.php?t=1646088)
Can I use the official ICS firmware to upgrade my Note? Or should I wait a bit more?
Thanks!
Click to expand...
Click to collapse
Well I upgraded my Note and it is completely fine, my friend with a Note as well hasn't told me about his phone being bricked either. But I'm not sure about all the others though, since mine is the Hong Kong official one, and I never use the leaks so they don't really bother me.
Sent from my Galaxy Note

leppo said:
From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel. What are you using now?
Click to expand...
Click to collapse
When you say factory reset you mean going into settings and then "data factory reset"? I normally do that after a huge update and format my SD card too. So that is a no no on ICS?
Sent from my GT-N7000 using xda premium

Hagow said:
When you say factory reset you mean going into settings and then "data factory reset"? I normally do that after a huge update and format my SD card too. So that is a no no on ICS?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
That is correct.

leppo said:
From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel.
Click to expand...
Click to collapse
Bull****. I have tried to do wipe from CWM and MobileOdin over and over again more than 15 times at ICS leaks and ICS stocks and custom kernels and custom ROMs. Never got any problem.

anonymous572 said:
Bull****. I have tried to do wipe from CWM and MobileOdin over and over again more than 15 times at ICS leaks and ICS stocks and custom kernels and custom ROMs. Never got any problem.
Click to expand...
Click to collapse
You might want to read the stickies in this forum regarding the fact that it's not an issue that effects all users. But it effects some by bricking their phones.
Along with the advice to not tell others that the problem doesn't exist based on your experience.

diji1 said:
You might want to read the stickies in this forum regarding the fact that it's not an issue that effects all users. But it effects some by bricking their phones.
Along with the advice to not tell others that the problem doesn't exist based on your experience.
Click to expand...
Click to collapse
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".

anonymous572 said:
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".
Click to expand...
Click to collapse
How can you say that man,,,thr are so many ppl on Xda here that are reporting to have bricked thr devices......or are you saying that as long as you r not rooted , this bricking thing just wudn't happen?

anonymous572 said:
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".
Click to expand...
Click to collapse
and I never saw anyone without this strange wipe problem, want to know for sure? go install an app by chainfire called got brickbug?
http://forum.xda-developers.com/showthread.php?t=1693704
maybe you are lucky to have an unaffected chip ,but 99.9% of users have a known damaged chip fw.
I suggest you go read the sticky in which it says that some people have wiped 19 times and got a full brick on the 20th attempt ,some even more .
I myself have wiped once safely ,but the second wipe made the emmc go nuts ,luckily however it was not fully dead ,and I restored it ,barely .
besides ,samsung and Google have both confirmed this bug ,so who are you to state otherwise?!!
http://forum.xda-developers.com/showthread.php?p=27137024
so I would like to suggest that you stop spreading dangerous miss information to the noobs or I'll report your post next time.

MR.change said:
besides ,samsung and Google have both confirmed this bug ,so who are you to state otherwise?!!
http://forum.xda-developers.com/showthread.php?p=27137024
so I would like to suggest that you stop spreading dangerous miss information to the noobs or I'll report your post next time.
Click to expand...
Click to collapse
+1
The source of the problem has been found and confirmed...how can people still be ignorant and spread bad advice.
As Mr.change said above, yes there is a problem even with official ICS, you may get lucky but you will run into a problem eventually if you keep wiping data/factory reset with affected ICS kernels...so best not to do so.

What would be the alternative to a factory reset then? I'm waiting to receive a new Note and intend to install stock ICS straight away but I worry that I'll mess up my first ever Android install and have to start again. Could you re.install the update without a wipe?

solarboy said:
What would be the alternative to a factory reset then? I'm waiting to receive a new Note and intend to install stock ICS straight away but I worry that I'll mess up my first ever Android install and have to start again. Could you re.install the update without a wipe?
Click to expand...
Click to collapse
if you are new to this then I would advise that you stay way from it till you learn your way around the basics of flashing using PC ODIN ,mobile ODIN ,and recovery.
then flash stock ICS with a safe custom kernels and you should be safe.
besides ,samsung stock ICS isn't that different from GB ,same look and same performance . you'd want to install CM9 to get a taste of true ICS.
so like I said ,take your time ,bricking your new shinny phone can be devastating .

anonymous572 said:
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".
Click to expand...
Click to collapse
The problem is you don't know if you will hit the problem until you find out the hard way.
Once you've hit the problem there is no recovery.
So stop telling everyone that they are safe because you got lucky.
People who want to run ICS should use a kernel that has a safe configuration (MMC_CAP_ERASE removed from drivers/mmc/host/mshci.c) - This includes, but is not necessarily limited to (check the kernel's info) the CM9 included kernel, Hardcore's Speedmod ICS, and Franco.kernel r3 and above. Be sure to verify that you're running a safe kernel with CPUSpy before dropping into recovery - a few people had Mobile Odin fail to flash a safe kernel when they were on a dangerous one and then bricked because they didn't verify.

شكرا

solarboy said:
شكرا
Click to expand...
Click to collapse
you are most welcome my friend
لا شكر على واجب

nandihno said:
The official can brick the note muaaahuahuahuahuuaaa
Seriously as the previous poster said only if you are into wiping and restoring you MAY be in danger
What do u mean..? doing a factory reset is a common thing.. who on this earth doesn't do a factory data reset at all on their phone.. and if u ask me we must do a factory reset after updating to a new rom.
Pity on samsung.. their official builds destroy the phone. I can't believe.. how they released it without testing.. and why didnt the stop their ****ty ics update from being live till now..
i also have a question .. Has Samsung acknowledged the fact that their stock ics can cause bricking issues?
Click to expand...
Click to collapse

Autobrick Bug and ICS

Does anyone know if Samsung know about the autobrick bug and if the recent ICS update is going to avoid it?
The last thing I want to do is brick my tab.

three people so far have confirmed that it is not an issue. one said they did NOT factory reset afterwards in case it IS an issue.
i am about to flash and will post when finished

Thanks man
It's a shame that Samsung doesn't address this directly and the community has to

I installed the new ICS FW and made a factory reset after having updated.
I dont had a Problem, the device was not brick.
But i dont know if this can be said in General.

Did Chainfire's brick checker come up as positive on your model before flashing?

RXP said:
Did Chainfire's brick checker come up as positive on your model before flashing?
Click to expand...
Click to collapse
Yes it did, and I'm sending this from------>
Sent from my GT-P6800 running 4.04 using XDA Premium HD app

I flashed with mobile odin, over rooted stock.
i didnt factory reset, but i chose wipe cache and wipe data in the mobile odin app(all my apps and settings stayed, md5 failed, but everything flashed despite that).
Everything okay, but could someone confirm this kernel has the bug in the kernel of the official ics?

Mine is positive too ... running ICS as I type this.
Hopefully Samsung are being good boys and sorted things out this time after lots of troubles with the Note (same chipset as 7.7):good:

It was nice to meet you!!

It was nice 8 months experience,just Super bricked my Note while perfotming a wipe with CWM,too bad couldnt claim the warrenty.
Thanks for everyone who helped me during this period,both Developers and Members.
Jack

Sorry for your phone man.
Btw which kernel were you using?

Boy124 said:
Sorry for your phone man.
Btw which kernel were you using?
Click to expand...
Click to collapse
German LRK DBT stock 4.0.4 and it was running fine no problems,just wiped it to test the Paranoid Android JB 4.1.1,which was actually the last thing it did.

I see. But you can't flash roms using stock recovery. Anyways it confirms the bug still exists.

What CWM did you use or did you wipe from stock recovery?
Does it give any sign of life?
If it boots you can use: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
to see if you have emmc damage.

jgaviota said:
What CWM did you use or did you wipe from stock recovery?
Does it give any sign of life?
If it boots you can use: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
to see if you have emmc damage.
Click to expand...
Click to collapse
Unfortunately doesnt boot up,just stuck on the Gt-7000 logo but the download screen works,however when try to flash with PC Odin stops at the factoryfs.img which after research discovered is a Superbrick symptom.

hagba said:
too bad couldnt claim the warrenty.
Click to expand...
Click to collapse
Hello hagba, since you cannot claim warranty have you thought of getting your device repaired via the Samsung service centre in your region?
I would suggest you to enquire about the repair cost and then make a suitable decision.

Have you tried this? it worked for many users.
http://forum.xda-developers.com/showthread.php?p=26285877

YLNdroid said:
Hello hagba, since you cannot claim warranty have you thought of getting your device repaired via the Samsung service centre in your region?
I would suggest you to enquire about the repair cost and then make a suitable decision.
Click to expand...
Click to collapse
First thing on monday,

dr.ketan said:
Have you tried this? it worked for many users.
http://forum.xda-developers.com/showthread.php?p=26285877
Click to expand...
Click to collapse
Dr.Ketan,
I have tried the PIT procedure,but its such a long and tedious process Im not sure will be able to make viable partition for normal usage.
However will see what Samsung does on Monday.

So does this mean that Stock ROMS are still unsafe to wipe rather than how samsung claims that Stock ROM wont brick?
Did you report this to Entropy? Did you wipe after flashing Paranoid ROM successfully or did you wipe on stock. If it was after succesfully flashing the CM10 based JB ROM, it should mean that CM10 doesnt have MMC_CAP_ERASE disabled or maybe no ICS kernel is safe.
Should report to Entropy if you didnt.

He already.wrote 'wipe it to test jb' means wiped on.stock.
Entropy aleeady aware of this (i have already reported 2 case on 4.0.4). And he hav mentioned on his thread, stock ics are known unsafe kernels.
Sent from my GT-N7000 using xda premium

dr.ketan said:
He already.wrote 'wipe it to test jb' means wiped on.stock.
Entropy aleeady aware of this (i have already reported 2 case on 4.0.4). And he hav mentioned on his thread, stock ics are known unsafe kernels.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I made a mistake of wiping twice from Settings under android in Indian Stock DDLP8 stock 4.0.3 but luckily never bricked. But now I take care not to. But do you think I may have caused damage in the first two wipes? I see no issues till now but just asked.

It cause damage once in while, not every wipe/reset result to brick (good if it was like that, sammy must have find solution then)
Still if you have any doubts find 'emmc brick bug' application from market n scan ur device.
Sent from my GT-N7000 using xda premium

dr.ketan said:
It cause damage once in while, not every wipe/reset result to brick (good if it was like that, sammy must have find solution then)
Still if you have any doubts find 'emmc brick bug' application from market n scan ur device.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I have the affected emmc firmware VYLOOM 0x19. Its just that I turned out to be lucky. I dont believe Samsung would fix the Indian firmware (4.0.3) while the bug remains on the latest 4.0.4 ROMS. If there is a fix from Samsung, we Indians are the ones who usually get it last. But strangely, I havent heard of any superbricked Indian Notes in this forum.

satishp said:
So does this mean that Stock ROMS are still unsafe to wipe rather than how samsung claims that Stock ROM wont brick?
Did you report this to Entropy? Did you wipe after flashing Paranoid ROM successfully or did you wipe on stock. If it was after succesfully flashing the CM10 based JB ROM, it should mean that CM10 doesnt have MMC_CAP_ERASE disabled or maybe no ICS kernel is safe.
Should report to Entropy if you didnt.
Click to expand...
Click to collapse
I think Samsung's claim was that you won't get bricked if you stick to stock and don't root. I'm not saying that's true . Even seems unlikely since I think you can factory wipe from the settings without root, IIRC (memory's rusty, haven't been on a stock ROM for ages).
There were some bricks with CM10, but only from people who flashed from stock ICS or stock ICS based ROMs. Flashing from the safe ICS kernels seems to still be safe.
satishp said:
But strangely, I havent heard of any superbricked Indian Notes in this forum.
Click to expand...
Click to collapse
Maybe that's because Indians are careful enough to read the instructions before risking their device? I doubt it's because Indian Notes have had some special pixie dust sprinkled over them while they passed customs.

If you dont mod your device then how many chances are.there to make hard reset device?
I know lot ppl they purchasing and selling.device without single reset.
So rooting opens.100 ways to explore ur device, simultaneously opens 100 ways to put u in situation,u needs reset. That is the only reason rate.of bricking is high with rooted device, but if you read carefully and avoid reset/wiping there is almost zero chances to brick.
And yes if you look, compare to selling of notes in india, u don't see indians are quite less on forum?
Sent from my GT-N7000 using xda premium

dr.ketan said:
If you dont mod your device then how many chances are.there to make hard reset device?
I know lot ppl they purchasing and selling.device without single reset.
So rooting opens.100 ways to explore ur device, simultaneously opens 100 ways to put u in situation,u needs reset. That is the only reason rate.of bricking is high with rooted device, but if you read carefully and avoid reset/wiping there is almost zero chances to brick.
And yes if you look, compare to selling of notes in india, u don't see indians are quite less on forum?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I'm really worried because you said if I avoid wiping I'm almost zero chance of briking.. I got my note clean, I mean I don't dare to put music and movies into it because then I don't dare to delete all those files... Will this brick my phone? I'm stock 4.0.4 rooted
Enviado desde mi GT-N7000 usando Tapatalk 2

Obviously the culprit is wiping with CWM,I have factory Reset million times with no consequences at all,and just once with CWM was enough to Superbrick it,and yes I was on stock ROM.

msedek said:
I'm really worried because you said if I avoid wiping I'm almost zero chance of briking.. I got my note clean, I mean I don't dare to put music and movies into it because then I don't dare to delete all those files... Will this brick my phone? I'm stock 4.0.4 rooted
Enviado desde mi GT-N7000 usando Tapatalk 2
Click to expand...
Click to collapse
It says big files shudn't be deleted. Though frankly speaking i have not seen any case brick by that, though we cant ignore comments from recognised developer.
But wat best idea i found to manage file is
Connect device with PC as mass storage and manage files from PC explorer. I believe that is safe way.
hagba said:
Obviously the culprit is wiping with CWM,I have factory Reset million times with no consequences at all,and just once with CWM was enough to Superbrick it,and yes I was on stock ROM.
Click to expand...
Click to collapse
That was your bad luck this time, otherwise both have same effect.

Updating to 4.3 when on custom ROM

Hello! It is possible to update from 4.2.2 to 4.3 if you are using CM10.1 for example, right? But why do so many people want to update through fastboot when there is a recovery flashable zip?
Sent from my Nexus 4 using xda app-developers app

i didnt go through all the hastle.. i dirty flashed(flashed in recovery without wiping anything) aosp 4.3 over rasbean jelly rom 4.2.2, without a single issue. didnt have to wipe, didnt have to re set everything up. it took just about 3-4 minutes to go from 4.2.2 to 4.3. but, id make a nandroid backup just in case things do go wrong.

simms22 said:
i didnt go through all the hastle.. i dirty flashed(flashed in recovery without wiping anything) aosp 4.3 over rasbean jelly rom 4.2.2, without a single issue. didnt have to wipe, didnt have to re set everything up. it took just about 3-4 minutes to go from 4.2.2 to 4.3. but, id make a nandroid backup just in case things do go wrong.
Click to expand...
Click to collapse
Yeah I indeed thought that was possible, but why do so many people struggle and really want to flash through fastboot?
But I'm glad to know you can just update in recovery, so I will do that with the next update as well.
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
Yeah I indeed thought that was possible, but why do so many people struggle and really want to flash through fastboot?
But I'm glad to know you can just update in recovery, so I will do that with the next update as well.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
too many people just dont know, they do what they are told. anyways, flashing the factory img in fastboot is probably the "cleanest" way to update. but as you can see, all these people that are doing it, and still reporting many issues. im completely issue free here, and havent lost any of my previous data

Samsung keyboard on stock kitkat not working?

If I flash stock kitkat my Samsung keyboard won't work (force closes over and over).. I've no problems with any custom roms, on sweetrom now with no problem.. It's not a massive issue but it's annoying me! Does anyone have any suggestions as to how to fix it?
P. S- installing SwiftKey etc isn't fixing it..
Sent from my SM-N9005 using xda app-developers app

hypnodaz said:
If I flash stock kitkat my Samsung keyboard won't work (force closes over and over).. I've no problems with any custom roms, on sweetrom now with no problem.. It's not a massive issue but it's annoying me! Does anyone have any suggestions as to how to fix it?
P. S- installing SwiftKey etc isn't fixing it..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
You may need to do a full wipe when you flash stock, it's possible something has corrupted somewhere along the line.

Yeah I've tried all the usual tricks, re - downloaded stock from several places with no luck.. It's baffling me..
Sent from my SM-N9005 using xda app-developers app

hypnodaz said:
Yeah I've tried all the usual tricks, re - downloaded stock from several places with no luck.. It's baffling me..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
..
Format all your data in system via CWM - then reinstall your ROM from scratch, it'll fix any coruption issues. ->>> Important >>> Make sure you make/get a PIT file for your device before you change anything in case you need to sort your partitions out for a reflash

I'll give it a try thank_you...

Nope still got the same problem.. Must be some weird conflict with my phone that I can't pin down.. Like I say I'm on a custom rom anyway but it irritates me because I know it's still there...
Sent from my SM-N9005 using xda app-developers app

hypnodaz said:
Nope still got the same problem.. Must be some weird conflict with my phone that I can't pin down.. Like I say I'm on a custom rom anyway but it irritates me because I know it's still there...
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
How bizarre , I'd stick with the custom ROM for now just in case something else gets crazy corrupted - This Kitkat stuff atm is causing havoc all around.

Yeah I think you're right, maybe different batches of phones and buggy kitkat are causing problems for a few of us? It'll all get ironed out in the end hopefully..
Sent from my SM-N9005 using xda app-developers app

I got the same problem. KitKat update failed in the end and had to CF_Root in order to boot up.
Action Memo (with pen) are not working for me as well. It is all linked with Handwiting somehow.
Is your Action Memo broken also ?
The only thing that I didn't do is Wipe Data/Factory Reset in Recovery mode.
Did you try that ?

Colide said:
I got the same problem. KitKat update failed in the end and had to CF_Root in order to boot up.
Action Memo (with pen) are not working for me as well. It is all linked with Handwiting somehow.
Is your Action Memo broken also ?
The only thing that I didn't do is Wipe Data/Factory Reset in Recovery mode.
Did you try that ?
Click to expand...
Click to collapse
got the same problem as yours, no idea why though, after the update samsung keyboard and action memo stopped working.
I think I will wipe it tomorrow but it seems it's not working either

I'm checking around and they say that problem probably lies in the application S Pen Keep, there is no data on this one ... I guess as you said it's linked to the handwriting recognition. tried to do that using Snote transform into text as well and it immediately stopped working as well..

For time being I'm using different keyboard and I like it better than stock one. I really don't want to wipe a phone. Takes so much time to install everything back.
Sent from my SM-N9005 using Tapatalk

Did u guys intentionally or unintentionally uninstalled Samsung apps? From what I've understand, certain Samsung apps needs to be either freeze thru TB or disable it...

Haven't touched it. I've upgraded to KitKat without updating a bootloader and it happened.
Sent from my SM-N9005 using Tapatalk

same here, got the OTA update, after that it simply stopped working.. I don't need the keyboard .. I need the action memo more

Mine still isn't working, I'm on omega rom now so it doesn't affect me, but it still does it if I flash stock... Strange..

try to download another stock rom? maybe that will fix it.. if it did .. let us know... try to download the newest one that came up in Poland..

mine got fixed by formatting and wiping, re-download another stock rom I guess yours has some form of data missing ..
@Colide , just go back to factory settings , will resolve the issue, do it from the recovery of course.

I kinda hate it to wipe data. Lot of apps to reinstall. Thanks for a tip. ?
Sent from my SM-N9005 using Tapatalk