Ok I have a very silly question. Does flashing too much harm the nand ?im flashing a hell lot of roms and kernels. Asking it because to go from sgs rom to nexus s port I have to flash the kernel each time and im playing with it. Also I like trying cm nightly builds. From what I've learned kernels are flashed to same nand and the nand has wear levelling capability.
I an very far from usa and have the vibrant.so don't want to destroy it beyond print or ill have a 500$ brick.
Any enlightment on this would be appreciated. Thanks
Sent from my SGH-T959 using Tapatalk
I think nand chips like most solid state memory support writes several hundred thousand times. So you should be good.
Sent from my SGH-T959 using XDA App
Any writes performed on the device decrease it's lifespan. Whether it's done by flashing, installing apps, loading various media on it, etc. You shouldn't need to worry too much about it. Even a serial flasher's phone will likely brick (for other reasons) before the SD card gives out, I'd think.
Solid state flash indeed has a limited number of write cycles. However, it is unlikely that you'll encounter this within the normal lifetime your phone. Several hundred thousand write cycles should be possible before it expires. SD cards also include circuitry to manage "wear-leveling". This spreads writes over the whole of the storage media to try to avoid writing to various frequently written locations too often which could cause premature failure.
Thanks guys.....ya I was thinking the same but since 2 gb is partitioned for the system ,i started thinking what if I messed that 2gb partition.but I guess wear levelling will use whole nand chip to manage wear.
Sent from my SGH-T959 using Tapatalk
Related
so just read up on swap and had a couple more questions. i understand that it changes the way your phone handles the ram different apps use but still not understanding the specifics. if someone could clear that up it would be wonderful also will this affect battery life at all? and last question will this work on the kernel that comes with das bamf remix 1.6.3? ( i think my phone info says dirty by adrynalyne #1 ) or do i need to use the one suggested in the instructions --> http://forum.xda-developers.com/showthread.php?t=1106420 here?
It turns a set amount of your sd card memory into ram essentially, and the less frequently accessed files are written to the sdcard swap partition instead of the ram, essentially freeing up the ram for the more frequently read and written data. I didnt notice any effect on battery life, and i guess the only way it would...was if it drew more power to write to sd...i believe you need to use a kernel with swap enabled like the one by imoseyon
Thanks a ton! that perfectly answered my question as for the kernel i figured as much. does anyone know if the kernel i mentioned supports swap?
Swap is created on internal space, the emmc not the SD card.
sent from a sweet paper weight.
Pretty sure I read from Adrynalyne that his kernels all had swap enabled even though he doesn't believe it works.
Mike
For windows users, swap is like your page file (just better managed). I see very little ever use swap on android though.
ibsk8 said:
Swap is created on internal space, the emmc not the SD card.
sent from a sweet paper weight.
Click to expand...
Click to collapse
First off love your signature and after reading some more it is definitely on emmc. which is fine cuz the thunderbolt has like what 16gb of it?
dak_181 said:
First off love your signature and after reading some more it is definitely on emmc. which is fine cuz the thunderbolt has like what 16gb of it?
Click to expand...
Click to collapse
There are also whispers going about that doing this "could" stress the emmc too much and cause your phone to an hero itself. The emmc is also possibly the leading culprit in the GB reboot of doom. Too lazy to point to source but seen this about the forums.
Truthfully I don't understand why people are putting their phones through this. EMMC is limited to how many times you can write to it. Just like a SSD drive. The first thing people do with SSD's is to either disable the swap file (page file) or move it to another drive. Putting a swap file on your EMMC is just killing the life of your EMMC even sooner. People say that you'll never kill your EMMC chip within the lifetime of your phone. But the fact is, no one knows how many writes your EMMC chip will take before degradation occurs. It's all up to the user though. Just wish people would do some research and fully understand the technology within their phones.
Carnage9270 said:
Truthfully I don't understand why people are putting their phones through this. EMMC is limited to how many times you can write to it. Just like a SSD drive. The first thing people do with SSD's is to either disable the swap file (page file) or move it to another drive. Putting a swap file on your EMMC is just killing the life of your EMMC even sooner. People say that you'll never kill your EMMC chip within the lifetime of your phone. But the fact is, no one knows how many writes your EMMC chip will take before degradation occurs. It's all up to the user though. Just wish people would do some research and fully understand the technology within their phones.
Click to expand...
Click to collapse
+1....Adreylane himself declared that he would not create swap on the EEMC. If he does not recommend it, I am not doing it.
I would like to, however, figure how people have so much RAM remaining on their phones safely. I only get about 120/600 free 98% of the times without having to constantly close out tasks. People in the dev forum are reporting they have had 300-400 free on Froyo. We all know GB takes more but I am on Froyo still and only have seen my aforementioned numbers.
id heard of some problems on emmc but didnt realize it was such a big deal. thanks for clearing that up before i tried it out. and im having the same issue im only getting between 100-200 free mb of ram without a task killer. is there something were doing wrong?
Lately I've been in the mood to taste test some of the fantastic ROMs made by the community, but I have a concern about flashing too many times.
Can I corrupt the hardware with bad blocks by flashing too much? What is an alternative?
No. Flashing a new rom erases all existing data of a previous rom.
Some devices allow you to boot from SD card.
Yes, too much flashing will destroy the chips, but too much usually means millions of cycles (I don't remember the real number, but it should be easy to find... the important part is that it's a lot)... so you don't have a lot to worry about here.
The bigger risk is that something goes wrong and you manage to wreck the software on those chips beyond repair (to the point where you can't even get into any kind of recovery anymore)... the chance isn't very big, but it rises exponentially each time you flash... the risk for each individual attempt is the same, but the chance that one of your attempt fails rises.
How many times we can flash our phone? like custom roming,rooting,kernel etc
I guess till it dies ..I have tested almost every rom n kernel in xda nd android world.it ,over fifty to hundred probably almost for 2 months now and keep changing no problems till now ..
Sent from my LG-P500 using xda premium
alxbsl96 said:
How many times we can flash our phone? like custom roming,rooting,kernel etc
Click to expand...
Click to collapse
you can flash it as many times as you can before it get bricked(from BRICKED i mean it cannot be reapaired by any way....
As many times as you wish.
^ Not completely true. At some point, the flash ROM will die on you. It's a natural event when it comes to flash memory, although it should take a good number of rewrites for that to happen.
metalboy94 said:
^ Not completely true. At some point, the flash ROM will die on you. It's a natural event when it comes to flash memory, although it should take a good number of rewrites for that to happen.
Click to expand...
Click to collapse
Flash memory gets deleted if u delete everything so theres no worry for that, so its almost,
unlimited flash times, as told until u cant start phone (hard bricked)
not soft bricked, l0l
however hard brick is kinda hard, (at least as we often cant flash other rom's also if we do so it wont boot properly to prevent phone from hard brick, so its kinda a good safety)
I'm not talking about bricking here, rather about the physical resistance of the memory. Why don't you check out the back of the packaging from a USB drive or memory card, you will notice an attribute named "Maximum Number of Cycles".
The Optimus One has EEPROM
http://en.wikipedia.org/wiki/EEPROM
Taken from Wiki:
The manufacturers usually specify the maximum number of rewrites being 10 to the 6th power or more.[2]
During storage, the electrons injected into the floating gate may drift through the insulator, especially at increased temperature, and cause charge loss, reverting the cell into erased state. The manufacturers usually guarantee data retention of 10 years or more.
In other words, don't worry about it
Hi guys!
So my previous S3 had been Bricked and I had no other solution other than to make a replacement after many tries.
Long Story cut short: I have a Pebble Blue 16GB version of the Galaxy SIII GT-i9300 and the Device ID, PDA, Modem etc are attached.
My Question is:
It isn't rooted this time. As my prev device fried after Rooting. What are the things I should do in order to make a backup. Like the PIT file! What information do i need to know so that i can recover it from any future incidents?
thank you!
From what I've heard and read, you can't do any backup or something that would revive it if it ever happens. It's a hardware failure. Best thing maybe to do is don't charge overnight. From what I've read, most of those sudden deaths have at least done overnight charging during the lifespan of their s3.
Rooting has nothing to do with it. Why not enjoy your phone because root or stock you will still be affected.
Sent from my Galaxy Nexus using Tapatalk 2
WasifSal said:
...
My Question is:
It isn't rooted this time. As my prev device fried after Rooting. What are the things I should do in order to make a backup. Like the PIT file! What information do i need to know so that i can recover it from any future incidents?
thank you!
Click to expand...
Click to collapse
Rooting (when done right) should have very little to do with a device getting hard-bricked.
The top-two reasons for a true hard-brick are (major) flash malfunction and (IMHO) recharging problems.
The only way you can (somehow) lower your risks for major flash malfunction is to write as little as possible to the internal flash (and for instance place as much stuff as possible on an external microSD card) - but other than that it is just a matter of pure luck.
The simplest way how you can lower your recharging risks is to always use a known-good USB cable and recharge from a good notebook - it will be twice slower but it should be safer and will certainly limit the 'aging' of your battery.
The main part where your S3 has system-unique stuff is probably in the EFS partition (and possibly in the modem partition if it is not a standard model but instead something specific to some carrier - but that is now very rare). Once you have those saved everything else can in theory be recovered by somebody with a lot of skills (and time) from the net.
And of course any important info that you added inside could be unique
As far as I know these incidents are happening at random. Even stock phones have died so it definetly is not cause of rooting. It maybe cause of overnight charging.
More over I have never charged my phone directly so far. I plug it to my laptop using USB cable. That is a better option I guess. I advice you to do the same , the phone does get charged slowly but its safer I guess since the voltage is low.
Sent from my GT-I9300 using xda premium
The voltage is exactly the same on Ac or Usb, namely 5.0volt
The current (Ampere) however varies significantly between Usb2 (0.5Amp) and Ac (1Amp). Notebooks such as the Acer M5 have an always-powered usb port which is Usb3, and thus 0.9Amp
Sent from my GT-I9300 using xda premium
My hp died while not charging.... It was at 55% when it reboot itself and end up at the samsung logo with endless boot looping.
Going to recovery was impossible, I can only go to download mode.. My hp is rooted and i sent to samsung service centre and discover the motherboard was dead. They replaced it without question asked.
Sent from my GT-I9300 using xda app-developers app
Hey folks. Having a real issue with this. My s3 keeps freezing at random intervals for anywhere up to 25-30 mins. Getting really annoying now and I hope someone can help me stop it from happening. Recently rooted and flashed sentinel rom on but thought was that so flashed official touchwiz back on but still happening!
Thanks
Paul
Go and search in the general forum for the freezing thread. There are a couple of things to try before applying for a warranty repair.
Paul043 said:
Hey folks. Having a real issue with this. My s3 keeps freezing at random intervals for anywhere up to 25-30 mins. Getting really annoying now and I hope someone can help me stop it from happening. Recently rooted and flashed sentinel rom on but thought was that so flashed official touchwiz back on but still happening!
Thanks
Paul
Click to expand...
Click to collapse
This is most likely sectors in eMMC going bad. My advice would be to have at least 4GB free on internal SD at all times. Backup weekly to external SD. Avoid writing to internal SD as much as possible. (also be 100% certain that you have multiple EFS backups). If you are using a dual-boot kernel - try to do most of your extensive work in a ROM that you install as second (and keep 1st as emergency backup).
xclub_101 said:
This is most likely sectors in eMMC going bad. My advice would be to have at least 4GB free on internal SD at all times. Backup weekly to external SD. Avoid writing to internal SD as much as possible. (also be 100% certain that you have multiple EFS backups). If you are using a dual-boot kernel - try to do most of your extensive work in a ROM that you install as second (and keep 1st as emergency backup).
Click to expand...
Click to collapse
Thanks for the advice. Is there a fix for this? My internal storage is already below 4gb and nearly everything writes to the sd card (32gb).
Paul043 said:
Thanks for the advice. Is there a fix for this? My internal storage is already below 4gb and nearly everything writes to the sd card (32gb).
Click to expand...
Click to collapse
I doubt - that aging is "normal" with any flash memory (but much less likely with high-end SLC vs low-cost MLC; I am also EXTREMELY curious if the same problems are seen on the 32GB or 64GB versions of the phone - but that could just apparent be since on those you will always have huge amounts of free flash). It was extra-bad with the buggy SDS firmware in the eMMC, but once you do have enough free space the huge lag when multiple-sector relocation takes place becomes far, far less obvious. There are mentions of some tools to improve things but I doubt that anything can do miracles. If the phone is still under warranty from a serious vendor and it dies you will most likely get a replacement.
xclub_101 said:
I doubt - that aging is "normal" with any flash memory (but much less likely with high-end SLC vs low-cost MLC; I am also EXTREMELY curious if the same problems are seen on the 32GB or 64GB versions of the phone - but that could just apparent be since on those you will always have huge amounts of free flash). It was extra-bad with the buggy SDS firmware in the eMMC, but once you do have enough free space the huge lag when multiple-sector relocation takes place becomes far, far less obvious. There are mentions of some tools to improve things but I doubt that anything can do miracles. If the phone is still under warranty from a serious vendor and it dies you will most likely get a replacement.
Click to expand...
Click to collapse
Its on warrenty until mid sept. I might just clear the binary count and bring it to the o2 store to send off.
Paul043 said:
Its on warrenty until mid sept.
Click to expand...
Click to collapse
Why? Is it a refurb? EU has 2 years warranty, so April-May 2014 should be when the first non-refurb units start losing warranty
rootSU said:
Why? Is it a refurb? EU has 2 years warranty, so April-May 2014 should be when the first non-refurb units start losing warranty
Click to expand...
Click to collapse
Not a refurb. I thought was a one year warranty. Will have to bring it in to them once I reset the binary count
UK SOGA warranty from the vendor usually one year. Samsung offer a 24 month limited warranty on top of that .
jje