yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] Goodm7sn:
I don't understand what's all this fuss about really...

I flashed lpy thru mobile Odin (coming from gingerbread) with root option checked, and all went smooth! No pc was used at all! I was even at University when I did that!

Then 2 days later, I factory reset using stock recovery... And all went fine! I was even in a friend's car!

So what's up with all the bricking all over the forum?!!
[Galaxy Note GT-N7000 General] Ashren81:
It happen randomly due to I/O bug on the kernel. While wiping big chunk of data off the partition, it'll glitch. Maybe after a wipe, 10th wipe, 11th wipe, 50 wipe etc. Maybe ur upcoming wipe will be ur last wipe, u might never know. Wiping thru CWM and stock recovery is known to produce the bricking effect. Only 1 person reported bricking thru the os factory reset.
[Galaxy Note GT-N7000 General] djtiny:
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.

Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
[Galaxy Note GT-N7000 General] Ashren81:
hardware conflict with newly kernel source is possible. different chip revision on different batch of notes produced could also lead to the issue. but if that is to be ruled out not to be the case, then its either samsung released a broken/buggy kernel for public usage or they make changes to the kernel source to react to CWM and the rooting community. just like how apple kept changing their baseband kernel every now and then to block jailbreaking on idevices.

to me its more like a buggy kernel. no wonder they kept pushing and delaying the ics release. ever thought of that?
[Galaxy Note GT-N7000 General] shorty66:
You might just be in the lucky position to have a phone which doesn't have the error.

But somebody also suggested that it makes a difference what you have fleshaed before the LPY rom...

I did not have anything else than stock GB befor the official update, but perhaps there is a way to flash a specific rom before going to LPY to be safe.

Do you still know your flash history?
[Galaxy Note GT-N7000 General] djtiny:
Hi Shorty66,

Sorry to hear about your note. I can remember being on Darky LC1 base rom full root. I downloaded the LPY.tar file flashed this via mobile odin to flash LPY via mobile odin and wiped data/cache from that program. When this was completed I had full root with the premium suit installed. Battery life was naff so I booted into CWM did full wipe along with cache davlik and flashed Stunner 26.1 rom then when this was fully booted I flashed the kernel extracted from. 19 stunner rom via mobile odin. Then when Alba releashed V2 full repack this was flashed via Red Pill 4.2 as I have this on my SD card because of the brick issues. After this was flashed I rebooted into redpill and proceeded with Flashing the Alba V2 full repack zip. This has fully booted with full root and no brick. So I dont quiet understand why my device has never bricked as im a flashaholic I tell you my mrs I always on to me about it. :D
[Galaxy Note GT-N7000 General] djtiny:
Yeah I can understand a buggy kernel but why release it as a proper update. I cannot see them delaying it just to add the premium suit. The note and S2 share the same hardware so the building of the rom should have taken the same amount of development time apart from adding the spen into the framework. The emmc chip if im not mistaken is what the rom and the free memory is on for the internal part of storage feel free to correct me. Im just spit balling ideas here but the way the partition are read on ICS is different as somebody developed a way to bind it like on gingerbread roms. What if the way that ics roms are made screws up and when another rom is flashed when wiping takes place it just erases all the partition info on the chip and this causes the brick. If that makes any sense and when it comes to write the info that seems to start bit sticks and there is no partition information of chip info to write to which is why it just hangs.
[Galaxy Note GT-N7000 General] Ashren81:
Somehow the writing block for this official rom and previously leaked roms suffer some sort of problem. The read/write and i/o for the build surely buggy. or the eMMC driver for this particular kernel base is buggy. it seem to completely screwed up read/writing the blocks when we perform large chunk of data wiping or writing ie flashing. i also realize that the premium app is now listed on the sd card. on gb, correct me if im wrong, no apps were pre installed upon flashing/factory reset that listed under the sd card right?
[Galaxy Note GT-N7000 General] djtiny:
That would be corect no apps are preinstalled. Is the bootloader for the device stored on the eMMC aswell. If so is the ICS kernel or something written in by Samsung or a small change they have implemented or written in the kernel code wiping the whole lot causing the chip to loose everything on it and this is causing the brick as the write part cannot complete due to the missing data partition. And when the battery is removed this is the final nail in the coffin so to speak as this just removes all power to the chip in a write mode causing a none recoverable device. This would explain not being able to boot back into download mode or recovery as its wiped from the device and the phone has power but nothing on the chips at all. I suppose this would not be the case because a jtag would be in theory be able to write back to the chip.
[Galaxy Note GT-N7000 General] Entropy512:
It only affects some users - maybe 5%, maybe only 2%, maybe as high as 10%. Either way, it's FAR higher than the effectively 0% presented by non-bugged kernels. Also, in some cases you may survive a few wipes and then brick later.

On a safe kernel, everyone can wipe/flash all they want and never encounter a problem. (Well, you might see eMMC damage if they just flash over and over again without stopping to eat, sleep, or work for a year or two straight.)
[Galaxy Note GT-N7000 General] Entropy512:
That I don't know. I have lost a LOT of faith in Samsung - I've always felt their QA process was pretty dismal in the past (the number of completely idiotic but at least not dangerous bugs present in I9100 update4 was ridiculous), but letting something like this out into the wild is an utter and complete epicfail on their part.

The short of it is - Unlike Sony, Samsung makes a point of not cooperating or communicating with the third-party developer community in any way, shape, or form. As a result, they seem to be partially aware there's a problem (as evidenced by disabling TRIM between SHW-M250S Update4 and Update5), but seem to be unaware of how bad it is and how many devices are affected.

What no one can figure out is how the I9100 escaped unscathed - EVERY other Exynos device that has seen an ICS leak or official release has been affected by this bug.

What we do know is that a kernel developer who rebased from the I9100 update4 sources to the SHW-M250L Update4 sources (which match M250S update5) encountered the exact same problems with NO other changes to his kernel. (The thread on the SiyahKernel 3.1rc6 incident is linked to from my sticky in this forum.) So we know for a fact that this bug made it out "into the wild" 1-2 months ago for the Korean Galaxy S II (SHW-M250S/K/L) variants.
[Galaxy Note GT-N7000 General] MR.change:
WRONG ,doing a wipe from the OS =doing a wipe from stock recovery

the OS would reboot in stock recovery and wipe anyway so it's the same poison really.

besides ,even deleting files could be dangerous on LPY

don't post a tutorial if you're not 100% sure what you're talking about.

people could brick their phones ,and their blood will be on your hands (so to speak)

EDIT: I know that there is no other way to get LPY ICS and the premium apps ,but if you must do a guide then at least make sure to put a big red sign that says (THIS COULD BRICK YOUR NOTE ,DO AT YOUR OWN RISK !!)
[Galaxy Note GT-N7000 General] anshoo:
i hope this helps someone who is looking to move to GB from LPY: http://xdaforums.com/showpost.php?p=26100801&postcount=18
[Galaxy Note GT-N7000 General] oka1:
From the Moderator

TO All ........ A Word of Caution..... Chainfire has clearly stated that the Cf-Root ...and ...LPY is potentially dangerous and he does not recommend going forward using it until he can work out resolving the potential bricking problem. Based on his judgement, (which I highly respect) I would be very wary of flashing anything that is using any part of it... given the word of caution from such a Experienced Developer.

CAVAET EMPTOR....... let the buyer beware......

Remember, you are responsible for trashing/bricking your device and risk do so by not heeding Chainfire's recommendations.

NOW PLAY NICE AND BE RESPECTFUL IN THIS THREAD ...NO FLAMING....... THANKS, Oka1 (Moderator)

__________________
[Galaxy Note GT-N7000 General] l0rd_almighty:
Will factory resetting remove my root and bring me back to GB?
[Galaxy Note GT-N7000 General] PJ147:
In a word - no

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] l0rd_almighty:
Good. Hope that solves my random reboot issue. Getting quite out of hand.
[Galaxy Note GT-N7000 General] dhruvmalik:
So I have been extensively reading the whole LPY / Kernel / CWM issues and my heart goes out to all those who endured the Brick issues; whether hard bricked, super bricked or soft bricked.

I have always used a GB rom and once installed Imilka's AOSP based ICS rom, but then reverted back to GB safely and do not flash often. I was on CheckROM V6 and been using it for a few months. No issues with the ROM but as soon as LPY was released, I took the opportunity to read the guides and did the following.

1) Downloaded LPY from the Samfirmware shared link.

2) Downloaded the LPY Kernel from Chainfire

3) Used Mobile Odin Pro and flashed LPY and the Chainfire LPY Rooted kernel during the same flash, not after flashing LPY first and then the Kernel afterwards - I checked Wipe Data and Cache & Wipe Dalvik Cache. I also checked in Enable EverRoot, Inject Super User and Inject Mobile ODIN.

Rom flashed successfully and booted up, I used Titanium Backup and got rid of all the Samsung crap (Hubs, SNS Services, news and weather, LWP's, Widgets) that I usually remove from any Rom.

My experience on LPY has been phenomenal and I am very pleased with it, my battery life is also fantastic.

So after writing all this, my question to you all is that whether one should go back to GB or just stay on LPY until a) a new release of ICS is out OR b) a fix is out somehow.

I would prefer to stay on LPY as it runs great but if revert back to GB is suggested, then please provide your methods.

In no way I am a newbie in this subject matter, but I prefer to learn from the experience and of others.

NOTE: I am not a flash wh*re on the Note as CheckROM performed exceptionally well for me. Those were my SGS II days when I flashed each week (only stock with Chainfire Root)

Your suggestions are greatly appreciated.
[Galaxy Note GT-N7000 General] MR.change:
may I give you an honest suggestion?

if you don't want samsung apps on your note ,then just flash CM9 ,if you were pleased with stock ICS ,then you'll be delighted with this one

just revert back to GB via PC ODIN first ,so as not to brick your phone flashing it from LPY
[Galaxy Note GT-N7000 General] dhruvmalik:
Thank you for your suggestion, but I am very displeased with the stock email client. I am a very heavy exchange account user and the samsung email app works fantastic. I read and view over 200 emails a day with many meetings being scheduled via the group and SPlanner is very nice.

My tasks dont sync well with AOSP / AOKP.
[Galaxy Note GT-N7000 General] Ashren81:
First of all, I did not make this guide to brick any note, and so far it didnt. Never once did i tell members to wipe using cwm or the stock recovery, coz that is the major problem with all ics kernel at the moment.

Not until shorty66 today posted about bricking his device while using the FACTORY FORMAT from within the ics menu itself i then update my post about the possibility bricking our device by using the last method of wiping.

Only shorty66 encounter the issue. As my guide says, do the factory reset from the ics menu ON THE FIRST BOOT after installing the ics rom. Not after using it for a couple of hours and after installing a whole bunch of apps from the market and then decided to wipe. Furthermore he did the upgrade method using kies, not using odin and he did not set the device up as a new device after upgrading.

So far people who did the factory reset upon first boot and get rid of all the cache from the previous rom havent complaint any bricking using the menu factory reset. I even said me myself have use it for 6 to 7 times. Its not about getting premium apps... its about preventing the bricking.

Next time be nice and think twice before flaming.


[Galaxy Note GT-N7000 General] MR.change:
fair enough ,then if you want to be safe just flash GB via PC ODIN ,and you're good to go.

---------- Post added at 11:35 AM ---------- Previous post was at 11:30 AM ----------

see that's where you went wrong ,there is no such thing as being safe by wiping from LPY

and like I said , doing a factory reset from the OS = doing a wipe from the STOCK recovery

so in one way ,you are telling people to wipe from stock recovery

yes you could do it 10 times and not get bricked ,but the risk is there .

by the way I wasn't trying to flame this thread ,and I'm usually a very nice person ,but being a victim of LPY ,I really hate to see another bricked note .

no offend was intended so don't take things personally .
[Galaxy Note GT-N7000 General] Ashren81:
Yes but if u get lags using the rom and experiencing fc's and some apps stop working instead of wiping thru CWM or STOCK RECOVERY and it left ur note bricked upon the first wipe, might as well play safe and do a factory reset. Coz the precentage of people bricking using the method is far less than mention above. Only 1 if u're not aware.

Most people bricked when they do the wipe in CWM and stock recovery upon the first boot when they discover something or some app doesnt work. And they're left with a bricked device. Just dont do that. If u decided to wipe upon first boot, use the factory reset menu. Let the phone reconfigure its ics framework and apps freshly before u decide to tinker with it.
[Galaxy Note GT-N7000 General] musashiro:
check the updated PSA... more users gets bricked day by day
[Galaxy Note GT-N7000 General] k@ke:
I flashed ICS XXLPY with Mobile odin (factory reset + wipes) and after that i flashed CF-Root and wiped cache and dalvik cache from ICS CWMR. I was lucky that nothing bad happened, using CWM recovery.

Now i reverted back to GB, because i'm terrified not knowing what's causing these bricks and nobody knows if this XXLPY would do other harms as well.

So here is how I reverted back to GB:

1. I booted to ICS CF-root CWM recovery

2. I flashed AbyssNote 4.2 Redpill kernel

3. I rebooted to AbyssNote recovery

4. Did factory reset + wipes from AbyssNote recovery

5. Flashed Cassie's XtraliteRom (this is a wipe ROM)

6. Rebooted system (and did the tricks that Cassie's rom needs after flash)

Everything seems to be okay. I'm going to stick on GB now and won't flash to ICS until it's 110% safe.

This is a good reminder of the dangers we take when flashing.
[Galaxy Note GT-N7000 General] Alexanderbooth:
So is there not a common thing people are doing to get this brick problem? how many people have actually bricked there phone? I'll bet this has only happened to people that flash there phones a lot, am I right? Maybe its all the flashing thats the issue? You surely can't just keep writing and writing over the storage forever?
[Galaxy Note GT-N7000 General] dhruvmalik:
SO is flashing via PC Odin better or using the above mentioned method? I have read both work but also read that PC Odin does cause flash failures.

I will go back to CheckROM v6 if anything.
[Galaxy Note GT-N7000 General] k@ke:
I can't give you 100% perfect answer, but in my point of view i choose to use CWM -> AbyssNoteRecovery -> Factory reset + Wipes -> Flash GB from AbyssNoteRecovery.

This could be the safest way, because you are doing all the wipes and resets in GB kernel. Just make sure, that you have all the zip files you need in your SD-Card before you start. (AbyssNote4.2.zip and GB-ROM.zip)

I don't know how PC-Odin works, but i've read that ppl have had problems trying to revert back to GB from ICS using this method.
[Galaxy Note GT-N7000 General] dhruvmalik:
Same here, but then some people insist on PC Odin.

I have always used PC Odin and have never encountered any issues, but dont want this time to be the first.

Maybe sticking with LPY may be the best thing as people trying to revert back also have issues.

It aint broke right now, so maybe wont try to fix it. _ Or maybe thats a lie I tell myself to not go back to GB (Liking ICS and dont want to go through setting up all the apps again.)

Come on guys, what are ya doing, sticking with LPY or have reverted back?
[Galaxy Note GT-N7000 General] Ashren81:
stick with it. using pc odin to get back to GB from LPY is safe provided u wipe before flashing the gb rom. i've tested this on 2 notes and it survived. believe it or not, 1 note encounter problem. stuck in factoryfs. we got it working back by flashing the pit file (just the pit file) and rebooted the phone, get into recovery, wipe, and flashing the gb back onto the phone works. no factoryfs stucking again.

as to when i say wipe ur LPY before going back to GB using pc odin, i mean FACTORY RESET. here we always use that method and not by booting into the recovery mode. when the device booted, skip the setup new device wizard and power off the note. turn it back on, enter download mode, and start flashing gb using pc odin as u would normally do.

2 of the note that went smoothly (factory reset from within menu), 1 that got stuck on factoryfs (did not). so i guess we should really clear the cache and all before wiping off the whole rom with a new one. most people use mobile odin and get the wipe action together with the flash which is why most of them did not face any problem.

JUST DONT WIPE USING CWM & STOCK RECOVERY WITHOUT BOOTING INTO OS.
[Galaxy Note GT-N7000 General] MR.change:
Yes I'm afraid that for now ,there is no such thing as safe ICS ,people will have to choose between ICS or safety

Cm9 has a safe kernel but some features are not fully working yet ,so it's not for everyone

Yes there is ,they all wiped or flashed while on LPY kernel .

as our friend suggested, stick with PC Odin, it is the only safe method for flashing from LPY .

However ,I strongly disagree with doing any kind of wipe/factory reset while using LPY

Instead just do the following:

1. If you're running LPY right now then just turn off your phone immediately

2.put it in download mode

3.flash a GB ROM using PC Odin like you've always done before.

4.when the phone restarts it'll probably enter a boot loop ,so just enter recovery (GB Recovery) and perform a full wipe.

5.welcome back to safety .

Do not ,I repeat do not perform any kind of wipe or factory reset while still on LPY

Any kind of wipe ,be it from recovery or from within the OS itself has the potential of burning the emmc .

Note: if anyone wants to correct me ,then please do ,but I truly believe that this is the only 100% safe method.

Edit: if for some reason you can't or don't want to use PC Odin ,then use mobile Odin to flash ,as mobile Odin will flash it's own temporary flashing kernel and then boot from it to perform the actual flashing .

Two things to note however:

1. When you tick factory reset on mobile Odin ,it will first flash the ROM then perform a wipe from recovery on first boot ,which is safe and goes in line with my request that none of you should wipe on LPY .

2.the down side is that mobile Odin will flash a temporary flashing kernel while on LPY ,it's

very small in size ,and the chances of something going wrong are small ,but still you should know that it's not as safe as PC Odin .

Having said that ,I'll tell you that I actually used mobile Odin instead of PC Odin cause I thought it was safe enough .
[General Questions and Answers] kkheart:
Hiiiii,

I have samsung galaxy ACE GT S5830, i face a peoblem that it bcome very slow, even lock screen take 10 second to appear. I think its bcoz of i cant move app. From phone mememory to SD card. App like, Gmail, facebook, watsup etc.

What i should do for make my instrument faster?????
[General Questions and Answers] Sot0:
You could uninstall some apps or wipe your phone ;)
[General Questions and Answers] nathan-96:
You can

1. factory reset in cmw

2. Install a custom rom
[General Questions and Answers] yozgatdeluxee:
A neu customrom

custom rom or a factory reset is good
[HTC Wildfire S] Royal King:
I got a 16GB class, 10 memory card. I made a partition if 1gb and 0mb swap. Is that correct? What does the swap really help with?

I tried Google but couldn't really understand it properly. Someone can explain it to me in layman's terms? ^_^
[HTC Wildfire S] SanderTheNinja:
That's a good size. Now install data2sd by jikanturu and you have more internal memory.

good enough?
[HTC Wildfire S] Royal King:
I tried link2sd. It says no space left on the phone. :S
[HTC Wildfire S] SanderTheNinja:
then reinstall it or try data2sd.
[HTC Wildfire S] w3r3w0lv33:
Link?

Can you provide the link to Data2SD? All the ones I found were deleted off of mediafire D:
[HTC Wildfire S] nikhilkaushik:
Search Data2SDInstallerNXE2.zip and you'd get your desired thing on androidforums.com

Else pm me your email and I'd send you the zips....
[HTC Wildfire S] Liudvis987:
Swap is fake ram. With class 10 SD card you had to use at least 128mb-256mb because wfs have only 512mb ram
[HTC Wildfire S] dudeman1996:
Don't bother with swap, you don't need it. Swap is just using disk space as RAM. But since the SD card is significantly slower than RAM (even if it is a class 10), you won't be having a good time. I've got like 120 apps installed on my phone and I still have 100+MB of RAM available. You don't need swap. As for sd-ext, don't bother with all the many different scripts, the easiest way is just to download S2E from the Play Store, it does it all for you :)
[HTC Wildfire S] asdot:
do we need swap? http://wiki.cyanogenmod.com/wiki/Swap_and_Compcache

It's up to your choice.

my sdcard has 128mb swap.

Sent from MARVEL
[HTC Wildfire S] Senthamil:
Hi, I have a 4GB (Class 10) memory card. (872 MB -Ext4 Partition, 700 MB -Linux Swap and 2300 MB on Standard Partition) and using Link2SD. I have installed 30 apps and got only 45MB internal memory left.

But I see you got more internal memory.

1. How is this possible?

2. Can I now move on to S2E? If yes then how?

Thanks.
[HTC Wildfire S] dudeman1996:
The best way to do it would be to backup all your apps and data with titanium backup, then reinstall your rom from scratch. Make your sd-ext partition bigger if you wish, then install S2E, let it mount your sd-ext and then restore everything with titanium backup.
[HTC Wildfire S] aleflocco:
Hi,

I flashed modpunk's CM9 rom, and tested Reloaded ICS on it.

http://xdaforums.com/showthread.php?t=1531222

When I reboot the phone, it starts to FC all apps.

Did somebody test the couple, and got same issue?

Thanks

Ale
[HTC Wildfire S] SanderTheNinja:
I did the same, without problems. Maybe you can reinstall it?