So chainfire released an app that can tell you right away if your Emmc is 0x19 or 0x25
Its a good.
The app is at the bottom of this POST.. look below.
My question is. when people think Samsung will fix this or even bother fixing this. Personally mine is the bad 0x19 and i still run GB. JUST FOR that reason until a custom Rom that i like comes out,or for Samsung to push another update. what do people think. They will do.
Update
14:56 CEST, new response from samsung:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time.
Source: https://plus.google.com/111398485184...ts/21pTYfTsCkB
please remember to thank me.. if you found this post helpful.
They would fix it only after admitting it.
rp4k said:
So chainfire released an app that can tell you right away if your Emmc is 0x19 or 0x25
Its a good. Apk
http://forum.xda-developers.com/attachment.php?attachmentid=1108535&d=1338911969
The app
My question is. when people think Samsung will fix this or even bother fixing this. Personally mine is the bad 0x19 and i still run GB. JUST FOR that reason until a custom Rom that i like comes out,or for Samsung to push another update. what do people think. They will do.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Where can I find this apk? Thanks.
tknguyencsu said:
Where can I find this apk? Thanks.
Click to expand...
Click to collapse
Clicking on the link you have just quoted might prove to be fruitful, perhaps?
chasmodo said:
Clicking on the link you have just quoted might prove to be fruitful, perhaps?
Click to expand...
Click to collapse
looool
So I have 0x19 emmc.
What can be done to change it?
I am currently running ics stunner 4.26.1
randomwalsh said:
So I have 0x19 emmc.
What can be done to change it?
Click to expand...
Click to collapse
Not a thing. 0x19 here as well.
It is sad that sammy wont fix this issue maybe when the next update they will
Sent from my GT-N7000 using XDA
0x19
I has it
Apparently from some light reading, only the Galaxy Nexus and at&t i717 Note are on 0x25 (maybe a few other devices I missed).
Oh well, I like Gingerbread at least. If I was 'stuck' on 2.2 I'd be much more bummed out.
Is Samsung actually still making N7000s with 0x19? I got mine a week ago, but it's possible it was sitting in a warehouse for awhile (though Amazon sells them so fast the vendor changes several times a day).
Mine too have the brick bug
Nice app to increases heart bits
Oh no.... 0x19... sad bug....
Sent from my GT-N7000 using XDA
I don't think uncle sam will ever fix this bug, it's easy to replace some mobo for those ppl that bricked their device than updating the firmware of the eMMC on ~7M notes.
I'm pretty sure that if you update to stock ICS and don't touch any recovery and or wipes its not a problem at all.
My guess is most Note users don't ever install a custom ROM, so for those ppl the "ICS bug" is not really an issue, its the flashaholics that are screwed....if they dont READ.
crap. 0x19 here too!
Only used lq2 so far. I suppose I'm lucky I only got my note a few days ago.
As far as I know, not a single n7000 has 0x25, however the at&t version is patched.
Sent from my GT-N7000 using Tapatalk 2
Zamboney said:
As far as I know, not a single n7000 has 0x25, however the at&t version is patched.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
One guy posted on the "got brickbug" thread under Themes/Apps and said his said he had an unknown firmware that may or may not be dangerous but it wasn't 0x19. So, in very rare cases, there are Notes that don't have 0x19.
Chainfire FTW!!
rp4k said:
So chainfire released an app that can tell you right away if your Emmc is 0x19 or 0x25
Its a good. Apk
http://forum.xda-developers.com/attachment.php?attachmentid=1108535&d=1338911969
The app
My question is. when people think Samsung will fix this or even bother fixing this. Personally mine is the bad 0x19 and i still run GB. JUST FOR that reason until a custom Rom that i like comes out,or for Samsung to push another update. what do people think. They will do.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
OMG Chainfire is like the god of smartphones. This has got to be the most useful and thoughtful apk i have ever seen. If Chainfire was employed by Samsung there would be no Apple lol.
I think to myself the same thing - will Samsung bother to fix this? The answer is no i would bet. Unless we kick up enough of a fuss that it gets regular media attention then they would have to to protect their brand...
Looks like I've got it too... its not even a week old from Vodafone...
Sent from my GT-N7000 using xda premium
SquirtingCherry said:
My guess is most Note users don't ever install a custom ROM, so for those ppl the "ICS bug" is not really an issue, its the flashaholics that are screwed....if they dont READ.
Click to expand...
Click to collapse
it is an issue because it is in the stock rom!
any consumer that upgraded to ics over ota and then did a factory reset could brick their device - nothing to do with us flashaholics!
SquirtingCherry said:
I'm pretty sure that if you update to stock ICS and don't touch any recovery and or wipes its not a problem at all.
Click to expand...
Click to collapse
I use to be one of those "flash-a-day" types, but the older I get, the less time I have in the evening to do anything but RELAX. I flashed mine from stock GB to stock ICS, rooted and that's the last "mod" I did...no issues, and I don't do wipes...
Yeah, if you flash stock, leave it alone, I really doubt you'll have any issues.
I also have 0x19. I have flashed almost 100 times with various GB and ICS roms. I had a few bootloops but not major problems so far. Now when I flash I am more nervous until it starts working.
Related
Hi all. I've had my Nexus for about three weeks now, and while I originally bought it for Froyo, I'm getting impatient and have the urge to root and try ROMs like CM and Modaco.
Should I wait or just root and do it?
-------------------------------------
Sent via the XDA Tapatalk App
i rooted mine yesterday and only had it for 4 days.... havent even gotten the bill yet.... i bought it to hack
Even if you root you can still install Froyo. Its not like you're losing the ability to install Froyo by rooting. Actually, you don't even have to root to install Froyo now irrc..
I say go for it.
Then again, I'm a bad influence, and have a reputation for voiding warranties.
I rooted my phone within the first hour I had it - haven't looked back
Even if you root you can still install Froyo. Its not like you're losing the ability to install Froyo by rooting. Actually, you don't even have to root to install Froyo now irrc..
Click to expand...
Click to collapse
I have an AT&T Nexus One so I can't flash Froyo without root.
-------------------------------------
Sent via the XDA Tapatalk App
I say go for it.
Then again, I'm a bad influence, and have a reputation for voiding warranties.
I rooted my phone within the first hour I had it - haven't looked back
Click to expand...
Click to collapse
My phone looks to be fine. No screen, wifi, or any sort of issues. But I've read that HTC still fixes unlocked phones (at least sometimes). I'm just afraid of paying $530 for this thing and then bricking it. Haha.
-------------------------------------
Sent via the XDA Tapatalk App
tjsimmons said:
My phone looks to be fine. No screen, wifi, or any sort of issues. But I've read that HTC still fixes unlocked phones (at least sometimes). I'm just afraid of paying $530 for this thing and then bricking it. Haha.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
There is no chance of bricking it unless you update the radio. You won't have to update the radio to flash most 2.1 ROMs.... you will have to when you upgrade to Froyo. Might as well go ahead and screw around on 2.1 for now
tjsimmons said:
My phone looks to be fine. No screen, wifi, or any sort of issues. But I've read that HTC still fixes unlocked phones (at least sometimes). I'm just afraid of paying $530 for this thing and then bricking it. Haha.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I recently sent my phone in rooted for repair and htc didn't mind.
got it back a couple days later but it was locked again.
There is no chance of bricking it unless you update the radio. You won't have to update the radio to flash most 2.1 ROMs.... you will have to when you upgrade to Froyo. Might as well go ahead and screw around on 2.1 for now
Click to expand...
Click to collapse
Hmm. I'll have to look at some of the ROMs then and see what I like.
-------------------------------------
Sent via the XDA Tapatalk App
Does anyone else appreciate the irony of someone asking XDA if they should root?
It's like asking a kleptomaniac if you should shoplift.
I didn't root for 3 months until last week when I finally rooted. With froyo so close I thought about waiting. But once I rooted its now obvious that rooting is the way to go. Don't even worry about the official update coming. Just root it and you will have the official update earlier than if you don't root. Plus cyanogen is such a great ROM and totally worth it.
Okay so, I'm going to root and look at flashing some ROMs. Any guides out there? I see the sticky in General for Sense UI, but I'm not terribly sure if that's what I should follow or what.
Thanks!
Edit: started new thread.
just a quick question to you topic creator..im very new to rooting and flashing roms myself may i ask what guide you used to lear to do it?
mykeldrip said:
just a quick question to you topic creator..im very new to rooting and flashing roms myself may i ask what guide you used to lear to do it?
Click to expand...
Click to collapse
In General Paul posted a guide from stock N1 to Sense UI/CM (it's a sticky). I just went down that and it worked great.
codesplice said:
It's like asking a kleptomaniac if you should shoplift.
Click to expand...
Click to collapse
Hey it's not like we do it because we want to, we have to!
Lmao, sooooo true
so i bought my galaxy s last november and was super excited for the super phone it looked like, it is my first android phone and started off amazing. a few weeks after i got it i downloaded 'kies' where i was supposed to be able to update to 2.2, but it completely fried the internal sd card, and bricked me phone :0.
luckily i had a full return warranty for one month with Virgin Mobile Canada (i'm from toronto)
since i got a new I9000 i got the 2.2 firmware to work (with great trouble!) and now have no trust for samsung's Kies program.
i have loved some froyo for the past few months and am a huge android fan,
recently i'm hearing of the gingerbread update coming to the galaxy s in canada very soon, now i'm not sure whether to trust kies with this possible bricking update or not.
so that's why i'm here, to ask for information on the easiest, safest way to root my galaxy s so that i can have the gingerbread update, i am a total beginner with rooting or even the idea of it, and would greatly appreciate any help that is given!
another smaller note is i am getting a message on my galaxy lately that says 'database storage is nearly full' with a popup that looks like a red SD card symbol.
what does this mean none of the internal memory is close to full in any way at all!
so to sum it all up should i trust Kies for Gingerbread?
should i give rooting a try? (and how is the easiest/safest way to do it?!)
and what is with this memory almost full message about?
thanks for any replies everyone!
you dont need to root to update outside of kies, its done with other software on your computer. With that being said, i would think if you are a beginner it would be easier/safer to do it through kies.
can you refer me to a way to update my firmware outside of kies?
Read through this - if after a couple of read throughs you understand what to do, go for it... otherwise yeah you might just be better off sticking to Kies.
http://forum.xda-developers.com/showthread.php?t=723596
http://www.theandroidsoul.com/how-to-install-xxjvo-android-2-3-3-gingerbread-rom-on-your-galaxy-s/
seems like a good guide with video...
Okay thanks everyone!
Sent from my GT-I9000M using XDA App
just flashed 2.3 successfully, awesome thanks again!
hhmm I think since 1st day I got my sgs I have never used kies for update coz I read some forums saying there's chances updating process gets broken then u need to manually flash ur phone.
Sent from my GT-I9000 using XDA Premium App
ndlianke said:
hhmm I think since 1st day I got my sgs I have never used kies for update coz I read some forums saying there's chances updating process gets broken then u need to manually flash ur phone.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
+1 I preordered mine and the first upgrade I did was one of Darkys first roms. just remembered how awesome i felt when I got my hands on the steel edition rom. Oh the memories.
Sent from the best hardware blessed with the best software using the SEXIEST THUMBS IN THE WORLD!
TettZor said:
+1 I preordered mine and the first upgrade I did was one of Darkys first roms. just remembered how awesome i felt when I got my hands on the steel edition rom. Oh the memories.
Sent from the best hardware blessed with the best software using the SEXIEST THUMBS IN THE WORLD!
Click to expand...
Click to collapse
Haha understand how u felt.my 1st custom rom was darky 8.it was marvellous.then tried miui, cm7,juwe,kitchen.still sticking with darky's now
Sent from my GT-I9000 using XDA Premium App
ok, so im not an idiot, needless to say that rude video they showed when you sign up to this glorius forum. My problem is simply this: I have a Galaxy tab us Sprint model, running completly stock( aside from the root) and i have tried instaing spacemooses Honycomb port, my issue is when i flash the kernal that includes cwm 3.0 it starts up and gives me several errors to the likes of E:unable to mount sd card. im pissed! i know how to use heimendall and the flashing software but i keep getting this error, HELP!!!
You need to find your sprint files and flash it back to stock. I installed HC and it just plain ain't ready. Search google for stock sprint kernel and rom. That's what I had to do to get back to working.
Sent from my SCH-I800 using XDA Premium App
well i fixed it by just flashing my stock kernal back, but id already known to do that, my issue is the friggin kernal, i want HC so badd. do you know of anyway to get cwm on it without that no offence, crappy kernal?
jjenkins09 said:
ok, so im not an idiot, needless to say that rude video they showed when you sign up to this glorius forum. My problem is simply this: I have a Galaxy tab us Sprint model, running completly stock( aside from the root) and i have tried instaing spacemooses Honycomb port, my issue is when i flash the kernal that includes cwm 3.0 it starts up and gives me several errors to the likes of E:unable to mount sd card. im pissed! i know how to use heimendall and the flashing software but i keep getting this error, HELP!!!
Click to expand...
Click to collapse
Just so you know no one made you flash the rom. It is an alpha, and things will always go wrong!
If your mad it should be at yourself. The only people who should be flashing this should be people who can get themselves out of it.
And yes, to geet out of this get something flashable with Odin/Hiemdall and go back to stock.
.
jjenkins09 said:
well i fixed it by just flashing my stock kernal back, but id already known to do that, my issue is the friggin kernal, i want HC so badd. do you know of anyway to get cwm on it without that no offence, crappy kernal?
Click to expand...
Click to collapse
No! The kernel is the key to getting it up and running. Yes it is thrown together and somewhat crude bit it works.
Follow up on the progress as things should get fixed rather quickly and try again with a later build.
Sent from my SGH-T959 using XDA Premium App
I never ment to come across as pissed hah, im slightly annoyed and I know I know I made yhe decision to flash blah blah as yo u can see my tab is fine thats not the issue , I was just wondering about the errors I was getting in the cwm kernal...
My apologies if I sent anyones dander up
Sent from my SPH-P100 using XDA Premium App
why dont you wait till the official release?
randy.turker said:
why dont you wait till the official release?
Click to expand...
Click to collapse
+1
LMAO , nice joke !!!
Hah yeah like hell they will ever realse an offical since they said the gt 7inch doeznt have strong enough hardware, besides they have the 8.9inch and the 10.1 inch sporting honycomb so whats it to them?
Sent from my VM670 using XDA App
But does anyone know how to get cwm recovery on a sprint galaxy tab...?
Sent from my SPH-P100 using XDA Premium App
jjenkins09 said:
ok, so im not an idiot, needless to say that rude video they showed when you sign up to this glorius forum.
Click to expand...
Click to collapse
How was the video rude??
It was blunt and to the point. If you felt it was rude then I can only assume that you felt it related to you in some way.
The video is intended to make it extremely clear that 99% of all the questions n00bs/newbies (what ever you want to call them) think of asking have already been asked and answered in abundance. Its also designed to make them think twice about where and when to post aswell as to use the search button.
Now before you think im saying you fall into this category, im not. I'm simply telling you that the video is 100% necessary as staff and the community in general have really had enough of all the crap.
Anyway, back on topic. You should really stay clear of the HC alpha builds and wait for a beta or final. Flash back to stock or custom for now.
I get what he is saying, as I too have encountered the same problem. I've searched and searched, and I've spent most of the week flashing back to stock with heimdall.
I think what he is referring to is the conversion to ext4. It appears CW3 is not successfully converting to the ext4 format. I've even tried the Verizon bootstrap app with the same results, multiple mount errors.
jjenkins09, On a side note,you did come off a little rude, and a little more research before claiming to be pissed may have worked a little better for you (Honey catches bees).
I would love to know if anyone has had success flashing to EXT4 with a Sprint tab, and if so, Could I borrow the zImage and see if the problem is isolated to my tab.
As im glad for any advice , i did actually do a good bit of reasearch, but i feel where your coming from
Sent from my VM670 using XDA App
I have one of the Woot Sprint Tabs. I used the instructions from this thread to get ext4.
but can't find an answer.... is it doable? Also, what other mods can I do to it? I wish XDA had a section for each version of the tab, I have a huge headache from trying to find my answer.... thanks guys
bump..... Please guys, help me out. I tried rooting last night but failed, guess I tried the root from a different tab... so please help me out... I'm getting ready to smash this thing
Really, no one can help me out? ... maybe another forum has more courteous members.
Sent from my MB860 using XDA Premium App
Do you think that bumping your post two hours after posting it is courteous?
I just got a Galaxy Tab WiFi myself, but I did my research *before* I bought it. No Gingerbread is available, that I know of. There are not many alternative ROMs for the WiFi only model.
What did you use in your rooting attempt? The only two ways I know are with a Windows app or with z4root, an Android app. I haven't tried either one, here is a link to z4root on this forum.
http://forum.xda-developers.com/showthread.php?t=833953
I installed GB 2.3.3 using this thread
http://forum.xda-developers.com/showthread.php?t=1083971
hope that helps
SuperOneClick should be able to help you root your Tab.
Here's the Noob Rooting Guide with links and downloads.
Always do your research. The Development forums will be one of your best resources for your Tab.
BUGBEAR_X said:
I installed GB 2.3.3 using this thread
http://forum.xda-developers.com/showthread.php?t=1083971
hope that helps
Click to expand...
Click to collapse
That's for the 1000 not 1010 which is the wifi only model, thank you though.
Sent from my MB860 using XDA Premium App
brucemcl said:
Do you think that bumping your post two hours after posting it is courteous?
I just got a Galaxy Tab WiFi myself, but I did my research *before* I bought it. No Gingerbread is available, that I know of. There are not many alternative ROMs for the WiFi only model.
What did you use in your rooting attempt? The only two ways I know are with a Windows app or with z4root, an Android app. I haven't tried either one, here is a link to z4root on this forum.
http://forum.xda-developers.com/showthread.php?t=833953
Click to expand...
Click to collapse
No offense but if you're going to criticize you might as well not even comment to avoid any frustrations or arguments as a result. Thank you for the link, I was able to find z4 and lag fix yesterday.... applied both but i might roll back on the lag fix since I have no haptic feedback now unless anyone knows of a fix? I wasn't able to find anything on Google... wifi only tab and p1010 aren't too popular searches.
Sent from my MB860 using XDA Premium App
*sigh* waiting for this too..
****ty Samsung , is it so hard to just make an official Gb for this little tab considering the workforce they have at their disposal.
At one point I had heard that the Sprint stock GB (2.3.4) update worked on the Wifi only tabs, but I don't have a wifi only to test with.
I haven't heard of any alternative roms for the wifi only version.
Sent from my SCH-I800 using Tapatalk
Check with Kies, see if you have a firmware update. I only have a P1000, but maybe it's similar.
oh yeah, give time for people to reply your thread. Don't be a spoiled kid.
Sent from my Galaxy Tab P-1000 using Tapatalk
EDIT: from other answers here the Sprint GB 2.3.4 ROM stock or rooted sounds the way to go, so it looks like this should work for you as it did for me on my Verizon CDMA tab.
It's hard to say for sure, experimentation is part of the fun, but killing the tab isn't. I didn't find any definitive answers on flashing a Sprint CDMA ROM on to a Verizon CDMA Galaxy Tab (for example), so I decided to try for myself:
http://forum.xda-developers.com/showthread.php?t=1255339
I suspect doing a FULL ROM flash would be a *very* bad idea (it seems doing that with a GSM ROM on other (non-GSM) tabs KILLS it). However, the technique I used was only to apply the kernel and filesystems, so I would *think* if you had a backup from before (always best to have a backup anyway, right?) you could always revert. You may want to look around and check to see if stock WIFI images are out there (I don't know for sure) but the Voodoo or CwM (ClockworkMod) recovery backups should be fine either way.
Then if you apply the filesystem and kernel files from 2.3.4 and they don't work you should be able to revert (I would assume, I can certainly flash back and forth on mine). I would *think* the kernel supports vanilla hardware + CDMA additionally (i.e. you don't need it, but it doesn't hurt), but may be fine.
But again, unless you're prepared to take the risk, I cannot say for sure, you can wait and see if anyone else chimes in, but that's my take.
pvtjoker42 said:
At one point I had heard that the Sprint stock GB (2.3.4) update worked on the Wifi only tabs, but I don't have a wifi only to test with.
Click to expand...
Click to collapse
I don't feel like bricking mine to find out lol
Sent from my MB860 using XDA Premium App
loserbaby said:
EDIT: from other answers here the Sprint GB 2.3.4 ROM stock or rooted sounds the way to go, so it looks like this should work for you as it did for me on my Verizon CDMA tab.
It's hard to say for sure, experimentation is part of the fun, but killing the tab isn't. I didn't find any definitive answers on flashing a Sprint CDMA ROM on to a Verizon CDMA Galaxy Tab (for example), so I decided to try for myself:
http://forum.xda-developers.com/showthread.php?t=1255339
I suspect doing a FULL ROM flash would be a *very* bad idea (it seems doing that with a GSM ROM on other (non-GSM) tabs KILLS it). However, the technique I used was only to apply the kernel and filesystems, so I would *think* if you had a backup from before (always best to have a backup anyway, right?) you could always revert. You may want to look around and check to see if stock WIFI images are out there (I don't know for sure) but the Voodoo or CwM (ClockworkMod) recovery backups should be fine either way.
Then if you apply the filesystem and kernel files from 2.3.4 and they don't work you should be able to revert (I would assume, I can certainly flash back and forth on mine). I would *think* the kernel supports vanilla hardware + CDMA additionally (i.e. you don't need it, but it doesn't hurt), but may be fine.
But again, unless you're prepared to take the risk, I cannot say for sure, you can wait and see if anyone else chimes in, but that's my take.
Click to expand...
Click to collapse
Lol thanks... I guess if someone has the time and patience to try it and it works then please let the rest of us p1010 owners know
Sent from my MB860 using XDA Premium App
I have the P1010 also and from what I've heard, the two models (P1010 and P1000) have different hardware which makes the latter model possible for the ginger update while ours likely will never get it.
Enjoy it for what it is. That's all I can say.
jstrayy said:
No offense but if you're going to criticize you might as well not even comment to avoid any frustrations or arguments as a result.
Click to expand...
Click to collapse
No offence but you are the one who was rude by bumping your topic after 2 hours and also accusing people who didnt answer as not courteous, so obviously you are going to get criticism.
Your problem is that you cant be bothered to go read or search and expect people to jump on your topic and bring all the info to you. This is XDA-developers, not tech support, try and at least help yourself first before demanding answers.
If anyone tests the spring gingerbread method and it works, please say so. xD Im too much of a coward to risk my tab.
OmniLemur said:
If anyone tests the spring gingerbread method and it works, please say so. xD Im too much of a coward to risk my tab.
Click to expand...
Click to collapse
You can save a flashable ROM in the sdcard. Then if the tab got bricked, you can insert the sdcard in and reflash again. But i don't recommend doing this because me myself never flashed my tab, only my nexus one.
Hello,
I'm wondering if there is a way to discover if I have a bad partition without experiencing a Hard Brick?
I am on the official Taiwanese ICS release (LPF) and I DID to a Factory reset and Cache wipe on the Factory recovery after flashing. I used PC Odin and was coming from stock GB.
As Odin was doing its thing I got an error message about not being able to find a certain file. I wish I had written it down, but I don't have the exact verbiage. Anyway, Odin seemed to finish, the phone booted and it's been fine ever since.
I had been on LPY, but after reading about the emmc bug, I went back to GB.
I have had a few bugs, but the phone seems fine. I guess I'm just paranoid now from all the threads about bricking.
Is there anyway to tell if I have damage if I don't actually have a brick? I tend to copy a lot of pictures from my storage to a NAS, and I'm worried at one point the phone will just blow up if I copy a large number of files one day.
Thanks for the help
Sorry for the bump but I could really use some help.
Maybe I can ask another way. After flashing Official Taiwan ICS and wiping both before and after, am I safe now if I havent bricked yet? Its been over a week.
Thanks
There is currently no way right now that is "public knowledge" at least. Entropy and others are hard at work at fixing the bug, although there already is a workaround like in Franco's kernel and Speedmod kernel. And the CM9 kernel is safe.
I believe you are perfectly safe.I have been switching ROMs ever since ICS was out for note.I've done factory resets on each of them. I didn't face any bricking issues. Incidentally, talking about wiping, I've done factory resets on ZSLPF for about 13 times. It's still perfectly fine. I personally think stock Roms are impeccably SAFE; it's the "rooting" and "cwm" which causes problem in ICS on note. I advise you to be wary of rooting till it's perfectly safe to do so.
abhijit038 said:
I believe you are perfectly safe.I have been switching ROMs ever since ICS was out for note.I've done factory resets on each of them. I didn't face any bricking issues. Incidentally, talking about wiping, I've done factory resets on ZSLPF for about 13 times. It's still perfectly fine. I personally think stock Roms are impeccably SAFE; it's the "rooting" and "cwm" which causes problem in ICS on note. I advise you to be wary of rooting till it's perfectly safe to do so.
Click to expand...
Click to collapse
This makes me angry, i've seen you on other posts stating the same thing, even on the samsung declaration post that the current ics kernels are affected. Please stop directing people into your danger. You dont understand the implications of the bug at all, so dont comment.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
This makes me angry, i've seen you on other posts stating the same thing, even on the samsung declaration post that the current ics kernels are affected. Please stop directing people into your danger. You dont understand the implications of the bug at all, so dont comment.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Could you please post a link to that post where Samsung admitted that their kernels are affected.I wouldn't have ventured out if I had my phone rooted.As I mentioned earlier even Samsung representative told me it's safe to wipe.I wouldn't have said it had they issued the statement to the contrary.
Sent from my GT-N7000 using xda premium
Fair enough, heres link....
http://forum.xda-developers.com/showthread.php?t=1698977
Please stop posting dangerous info, and accept that both google and samsung are looking into this issue as a matter of urgency.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Fair enough, heres link....
http://forum.xda-developers.com/showthread.php?t=1698977
Please stop posting dangerous info, and accept that both google and samsung are looking into this issue as a matter of urgency.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I have already seen that thread.However, I seem to be sceptical about it's verity.
Here is the link where that issue was brought up to Samsung and they have replied to it too.
Please REFER TO IT, IT'S MY EARNEST REQUEST http://innovator.samsungmobile.com/...Id=1&selectedSequence=00dgu030000~&viewMode=2
Sent from my GT-N7000 using xda premium
Fair do's for that post also, but its over a week out of date. Did you check the new thread thoroughly?
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Fair do's for that post also, but its over a week out of date. Did you check the new thread thoroughly?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I have seen that thread too, but it's the only official statement we have till now.
Sent from my GT-N7000 using xda premium
Mate, seriously, you need to keep your oppinionated mouth closed. You hqve the strength of established developers on xda working closely with google and samsung to resolve the issue that is recognised by both. Please stop guiding people to an early death, some of them don't have warranties.
Sent from my GT-N7000 using xda premium
OP,
There is a cumbersome way...but it is a way to test if your data system partition is fried.
Like Sumrall has mentioned in one of the original links, you don't know if it's fried until the phone tries to access that part of the chip. If it is indeed fried, your phone will lock up and reboot.
What I did to test to make sure my NAND was alright was to copy movies into the data folder via Root Explorer. Copy stuff into the data folder until there wasn't any space left (as you approach 10mb and under in the data partition, copy mp3s, and eventually even font files to really hone down on the remaining space). If parts of the NAND were indeed fried, your phone should lock up and reboot when that happens. If nothing happens, your data partition is fine.
You can repeat these steps for the system partition if you so wish, but it is very unlikely, as root explorer indicates, say in my case, that there is only 6mb of space free or so. So if any damage had been done to the system partition, you would have found out a long time ago in my opinion either through a fail flash in odin or something along those lines.
Ignore "abhijit038". He's a troll and is spreading dangerous information.