Database Develop

[Q] Spacemoose-Honycomb issues

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.

just got a wifi only tab and I want to upgrade to gingerbread

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.

URGENT! DO NOT INSTALL KERNEL "ICS Full Root Stock LP1 base kernel I9220"

It causes a total brick the phone. It is literally useless. Under no circumstances install or flash this kernel.
If you have it installed do not wipe.
Flashing by odin another kernel.
Thanks.

Mod please delete this useless double post
Sent from my GT-N7000 using Tapatalk

I don't know about useless... seems like this could be reposted a thousand times and still be relevant to the person who hasn't seen it yet.

Well, the download links are long gone, so for those who haven't been there yet the risk is not only virtually non-existent, isn't it ?

What's alarming is that there are many other links out there on the internet with this kernel. I hope this gets bumped for as long as necessary. Bricking a $700 device sounds like a very expensive pill to swallow.
In this case, a little clutter wouldn't be too bad, if it serves the greater purpose of warning even than one to two people who are unaware of this issue.

maybe people will stop posting stuff from xda all over the net and make users come here to get it instead of stealing someone elses work.

I keep reading posts about warnings against flashing a i9220 kernel. I checked mine and I'm not sure if I should be worried and if so, how do I fix it.
I am on midnote 2.0 with kernel 3.0.15-I9220ZCLP1-CL131270 [email protected] #3
Thanks guys
Sent from my GT-N7000 using XDA

[Q] when will Samsung fix brickbug

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.

Urgent HELP wanted !!!

I just flashed cleanote rom v4 over stock ICS after wiping cache and dalvik. Stuck at boot logo ? how am i supposed to proceed now ? please help !

To be safe, reflash to GB using pc odin.
Sent from my GT-N7000 using xda app-developers app

Now had to flash abyss and clear data and then installed stock ICS. Now running safe.
Sent from my GT-N7000 using XDA Premium HD app

Akilesh said:
I just flashed cleanote rom v4 over stock ICS after wiping cache and dalvik. Stuck at boot logo ? how am i supposed to proceed now ? please help !
Click to expand...
Click to collapse
Do the full wipe every flashing custom rom..
Sent from my GT-N7000 using Tapatalk 2

fahrie12 said:
Do the full wipe every flashing custom rom..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
PEOPLE DON'T EVER FOLLOW THIS ADVICE!!
Your advice will add to the many victims of getting the Super brick bug
Before you advice something (like a full wipe on every flash), PLEASE THINK first before you ever suggesting others to fully wipe their device on every flashing of custom ROMS...

letters_to_cleo said:
PEOPLE DON'T EVER FOLLOW THIS ADVICE!!
Your advice will add to the many victims of getting the Super brick bug
Before you advice something (like a full wipe on every flash), PLEASE THINK first before you ever suggesting others to fully wipe their device on every flashing of custom ROMS...
Click to expand...
Click to collapse
well it's not entirely incorrect.
correct me if im wrong, but the majority of custom roms out there have cap_erase removed which means people can factory reset safely.
the bricks usually occur if people wipe on a stock samsung rom, where cap_erase ISN'T removed.
so if you're on a custom rom, and you flash another custom rom, assuming both roms had cap_erase removed, it shouldn't be a problem right?

little-vince said:
well it's not entirely incorrect.
correct me if im wrong, but the majority of custom roms out there have mmc_cap_erase removed which means people can factory reset safely.
the bricks usually occur if people wipe on a stock samsung rom, where mmc_cap_erase ISN'T removed.
so if you're on a custom rom, and you flash another custom rom, assuming both roms had mmc_cap_erase removed, it shouldn't be a problem right?
Click to expand...
Click to collapse
You haven't done a lot of reading have you? Look for it in the General section, especially topics for eMMC and 'Entrophy'
Wiping be it on custom or stock doesn't guarantee any safeties at all. even using CMW is a no no. If your custom rom has an infected kernel (that comes with it), fully wiping after flashing your phone ensures you a deadweight one after that.
It only takes one single full wipe to brick your phone, and it takes a load of hell to fix it.

letters_to_cleo said:
PEOPLE DON'T EVER FOLLOW THIS ADVICE!!
Your advice will add to the many victims of getting the Super brick bug
Before you advice something (like a full wipe on every flash), PLEASE THINK first before you ever suggesting others to fully wipe their device on every flashing of custom ROMS...
Click to expand...
Click to collapse
I'm sorry I often do this and there is no problem...
If u do it with stock kernel of course u will get superbrick..
But if u do it with safe kernel then superbrick can be avoided..
N many people had did my advice n nothing get superbrick..
Sent from my GT-N7000 using Tapatalk 2

fahrie12 said:
I'm sorry I often do this and there is no problem...
If u do it with stock kernel of course u will get superbrick..
But if u do it with safe kernel then superbrick can be avoided..
N many people had did my advice n nothing get superbrick..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
how do you generalize your advice to all the people your giving it? do you ask for their kernel first before telling them to fully wipe their NOTE?
Your playing a russian roulette dude. People would misunderstand your advice generally. There a lot of custom ROMS out there. Most often than not, its carrying an infected kernel. People who just scans and see your advice would tantamount to follow it to a tee (w/o telling you the full details of their kernel) and WHAM!! they get their phone brick!
There are already to many people asking help here... PLEASE don't add it more with your senseless advice!

letters_to_cleo said:
how do you generalize your advice to all the people your giving it? do you ask for their kernel first before telling them to fully wipe their NOTE?
Your playing a russian roulette dude. People would misunderstand your advice generally. There a lot of custom ROMS out there. Most often than not, its carrying an infected kernel. People who just scans and see your advice would tantamount to follow it to a tee (w/o telling you the full details of their kernel) and WHAM!! they get their phone brick!
There are already to many people asking help here... PLEASE don't add it more with your senseless advice!
Click to expand...
Click to collapse
did you ever try flashing the custom rom? did you ever see the kernel of what's recommended to do the flashing?
see the link...
n looking for the tutorial his use..
http://forum.xda-developers.com/showthread.php?p=25082204
Sent from my GT-N7000 using Tapatalk 2

fahrie12 said:
did you ever try flashing the custom rom? did you ever see the kernel of what's recommended to do the flashing?
see the link...
n looking for the tutorial his use..
http://forum.xda-developers.com/showthread.php?p=25082204
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
For someone who just registered this month, you surely got a lot of nerve!.
I've flash a lot of custom roms before you ever had gone here in Xda-dev dude. Don't divert me into clicking on that link.. been there done that. get it?
My advice to you is, before you try advising people for their problems. READ FIRST in all the stories and forum threads on our beloved Note. You will gain infos on what's causing it, and how to resolve and prevent it from ever happening it again.
So tip of advice, don't go all around the forum in advicing people to fully wipe their phone after flashing any roms. STOCK or CUSTOM.
Person's like you are the causes on why there are still people getting the bricks on their phone. Crappy advice and stuff!
Geez!!

letters_to_cleo said:
For someone who just registered this month, you surely got a lot of nerve!.
I've flash a lot of custom roms before you ever had gone here in Xda-dev dude. Don't divert me into clicking on that link.. been there done that. get it?
My advice to you is, before you try advising people for their problems. READ FIRST in all the stories and forum threads on our beloved Note. You will gain infos on what's causing it, and how to resolve and prevent it from ever happening it again.
So tip of advice, don't go all around the forum in advicing people to fully wipe their phone after flashing any roms. STOCK or CUSTOM.
Person's like you are the causes on why there are still people getting the bricks on their phone. Crappy advice and stuff!
Geez!!
Click to expand...
Click to collapse
+1 big time, I've seen a few people like yourselves who are newbies and posting despite warnings given by devs and it annoys me massively. Don't lead people down a dangerous path just because of your laziness!
Sent from my GT-N7000 using xda premium

letters_to_cleo said:
For someone who just registered this month, you surely got a lot of nerve!.
I've flash a lot of custom roms before you ever had gone here in Xda-dev dude. Don't divert me into clicking on that link.. been there done that. get it?
My advice to you is, before you try advising people for their problems. READ FIRST in all the stories and forum threads on our beloved Note. You will gain infos on what's causing it, and how to resolve and prevent it from ever happening it again.
So tip of advice, don't go all around the forum in advicing people to fully wipe their phone after flashing any roms. STOCK or CUSTOM.
Person's like you are the causes on why there are still people getting the bricks on their phone. Crappy advice and stuff!
Geez!!
Click to expand...
Click to collapse
Thanks for the advice john. I'm running back on stock. Any idea on how long will cleanote take to boot ?

letters_to_cleo said:
PEOPLE DON'T EVER FOLLOW THIS ADVICE!!
Your advice will add to the many victims of getting the Super brick bug
Before you advice something (like a full wipe on every flash), PLEASE THINK first before you ever suggesting others to fully wipe their device on every flashing of custom ROMS...
Click to expand...
Click to collapse
What's wrong with the advice...? OP just flashed one of the custom ROM, and he should already read the guide including how to root, to use a safe kernel to flash, and wipe procedures...
The only thing he didn't do yet was just wipe data, and this guy here was just trying to help by reminding him, which is not wrong...
I believe you concern about others, but why should you going mad? If his advice was not perfect why don't you give a better advice rather than bragging yourself and insulting other member just because he is 'younger' than you...?
Again, for his case, a full wipe is necessary and:
Akilesh said:
Now had to flash abyss and clear data and then installed stock ICS. Now running safe.
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
He did it anyway...

Akilesh said:
Thanks for the advice john. I'm running back on stock. Any idea on how long will cleanote take to boot ?
Click to expand...
Click to collapse
Hi Akilesh,
Yeah, no problem. Regarding your cleanote rom q, hmm that I'm not sure how long it takes to boot though. You may need to address that question my friend to the appropriate Cleanote note thread. http://forum.xda-developers.com/showthread.php?t=1716088
I've ended my quest in flashing custom roms already... eversince this brick bug came and wreck some lives off some people.
By the way, always make sure whenever you need to wipe things, it is better you have a safe kernel installed beforehand.
Like I've said getting the Super brick bug is just like playing a russian roulette. You'll never know when and how you got the brick, so take necessary precautions on how to prevent it
.
Cheers!
---------- Post added at 03:22 PM ---------- Previous post was at 03:12 PM ----------
TerraBuzz said:
What's wrong with the advice...? OP just flashed one of the custom ROM, and he should already read the guide including how to root, to use a safe kernel to flash, and wipe procedures...
The only thing he didn't do yet was just wipe data, and this guy here was just trying to help by reminding him, which is not wrong...
I believe you concern about others, but why should you going mad? If his advice was not perfect why don't you give a better advice rather than bragging yourself and insulting other member just because he is 'younger' than you...?
Again, for his case, a full wipe is necessary and:
Click to expand...
Click to collapse
I am not belittling the guy, It just irks me that he wants to shove on his irrelevant advices, not knowing fully well the full repercussion on his advice. Again, Entropy and a lot of seasoned experts have already made their stand on it. NEVER WIPE your phone in any flashing you do. Lest you get brick. That guy never even asked more than what he had said... WIPE YOUR PHONE AFTER FLASHING CUSTOM ROM!. Seriously can you believe that??
TerraBuzz said:
He did it anyway...
Click to expand...
Click to collapse
Yeah he did wipe it but he was already using a safe kernel. My point is, don't just blurt out to people to wipe anythng without asking them some additional necessary infos. It is okay to wipe and I'm not against that (if your using a safe kernel already). What I am against is the wrong notion in giving advices to WIPE your phone PERIOD.. Without even clarifying other infos at hand.

letters_to_cleo said:
Hi Akilesh,
Yeah, no problem. Regarding your cleanote rom q, hmm that I'm not sure how long it takes to boot though. You may need to address that question my friend to the appropriate Cleanote note thread. http://forum.xda-developers.com/showthread.php?t=1716088
I've ended my quest in flashing custom roms already... eversince this brick bug came and wreck some lives off some people.
By the way, always make sure whenever you need to wipe things, it is better you have a safe kernel installed beforehand.
Like I've said getting the Super brick bug is just like playing a russian roulette. You'll never know when and how you got the brick, so take necessary precautions on how to prevent it
.
Cheers!
---------- Post added at 03:22 PM ---------- Previous post was at 03:12 PM ----------
I am not belittling the guy, It just irks me that he wants to shove on his irrelevant advices, not knowing fully well the full repercussion on his advice. Again, Entropy and a lot of seasoned experts have already made their stand on it. NEVER WIPE your phone in any flashing you do. Lest you get brick. That guy never even asked more than what he had said... WIPE YOUR PHONE AFTER FLASHING CUSTOM ROM!. Seriously can you believe that??
Yeah he did wipe it but he was already using a safe kernel. My point is, don't just blurt out to people to wipe anythng without asking them some additional necessary infos. It is okay to wipe and I'm not against that (if your using a safe kernel already). What I am against is the wrong notion in giving advices to WIPE your phone PERIOD.. Without even clarifying other infos at hand.
Click to expand...
Click to collapse
And john i second your point in here. His intention is not bad but he just missed a point der. But anyways since all is fine it is good to go. And cleanote 5 is coming up. So hope it reduces the first boot time. I also had a post in the forum but without of a much help.
Sent from my GT-N7000

The point is....u should read the correct step bfore playin with ur phone, right? There is a ton of thread out there explain about what can make ur phone dead, read first carefully and u dont need to be an expert to flash safely in any cust rom or stock. Cheers. -=khai81=-
#nyimaklagi
Sent from my GT-N7000 using xda premium

Akilesh said:
And john i second your point in here. His intention is not bad but he just missed a point der. But anyways since all is fine it is good to go. And cleanote 5 is coming up. So hope it reduces the first boot time. I also had a post in the forum but without of a much help.
Sent from my GT-N7000
Click to expand...
Click to collapse
I'm sorry if I can't answer your cleanote question bud. Like I've said. I stopped changing /flashing custom Roms after the onset of this superbrick bug issue. Im all on stock 4.0.4 firmware now.
Anyway, it's all nice and dandy feeling that everything has been fix already in your end.
Let the good times roll.. :good:
John
Cheers!

I also want to flash cleanote rom and i am currently waiting on an updated version of that rom with the latest notecore kernel. I'm on stock 4.0.4 also and will use the PC Odin method to flash notecore kernel to root and then triangle away for binary reset. Then finally go with mobile Odin/PC Odin to flash the rom. After hours of reading threads, this seems to be a safest way to do it.
Sent from my GT-N7000 using xda premium

letters_to_cleo said:
For someone who just registered this month, you surely got a lot of nerve!.
I've flash a lot of custom roms before you ever had gone here in Xda-dev dude. Don't divert me into clicking on that link.. been there done that. get it?
My advice to you is, before you try advising people for their problems. READ FIRST in all the stories and forum threads on our beloved Note. You will gain infos on what's causing it, and how to resolve and prevent it from ever happening it again.
So tip of advice, don't go all around the forum in advicing people to fully wipe their phone after flashing any roms. STOCK or CUSTOM.
Person's like you are the causes on why there are still people getting the bricks on their phone. Crappy advice and stuff!
Geez!!
Click to expand...
Click to collapse
+1 : Things are different from device to device. once I vaguely advised what I did from my device, one member advised me not to give my own advice deviating from safe and standard procedure. I felt sorry for myself and thanked the member.