Database Develop

Life of the BlackStone ROM

How many Flashes till the BlackStone ROM dies out...
I mean, there has to be a limit to the number of
flashes we can perform till the memory dies...

yes there is but...
Believe me, you will trash you device earlier then the amount of re-flashing has attempt...
the amount is really a lot... even if you flash it 10times a day... you will die earlier... so no worries about.... you will never see this!
Good luck with re-flashing your device...
Roman
aaryaputra said:
How many Flashes till the BlackStone ROM dies out...
I mean, there has to be a limit to the number of
flashes we can perform till the memory dies...
Click to expand...
Click to collapse

banzro said:
Believe me, you will trash you device earlier then the amount of re-flashing has attempt...
the amount is really a lot... even if you flash it 10times a day... you will die earlier... so no worries about.... you will never see this!
Good luck with re-flashing your device...
Roman
Click to expand...
Click to collapse
Aha... An [almost] Immortal ROM...
Well, at least my BlackStone will live to see the Touch HD1001

aaryaputra said:
Well, at least my BlackStone will live to see the Touch HD1001
Click to expand...
Click to collapse
only 999 HD versions to go!!

it depends on the chip, but it can resist from 10,000 to 1,000,000 erase cycles.
let's suppose 10,000 times. if you flash it 10 times a day EVERYDAY, which is mostly unlikely, it would take 1,000 days, or approx. 3 years, for you to kill your touch HD.
so from this point of view you can flash it at your own will, you will surely dispose of it before it dies...

Thread served its purpose and is now closed

Why are certain Nexus One phones limited to 2.3 MB for boot image?

I am still trying to find right info about this...
Some posts are mentioning bad flash blocks...?
I am wondering if we could somehow overcome this limitation... I am also wondering what is Google going to do with FroYo builds - Linux kernels are bound to grow more and more... and sooner or later they'll hit the 2.3 MB limit, too...
One of the solutions would be to move more parts to external modules, though.

Ivan Dimkovic said:
I am still trying to find right info about this...
Some posts are mentioning bad flash blocks...?
I am wondering if we could somehow overcome this limitation... I am also wondering what is Google going to do with FroYo builds - Linux kernels are bound to grow more and more... and sooner or later they'll hit the 2.3 MB limit, too...
One of the solutions would be to move more parts to external modules, though.
Click to expand...
Click to collapse
Bad blocks are the conjecture. It really is a frustrating thing when you're trying to balance functionality and size.

My phone is one of the "lucky" ones. Kind of worrying; would be crappy if my phone can't take the Froyo update or something.

Ivan Dimkovic said:
I am still trying to find right info about this...
Some posts are mentioning bad flash blocks...?
I am wondering if we could somehow overcome this limitation... I am also wondering what is Google going to do with FroYo builds - Linux kernels are bound to grow more and more... and sooner or later they'll hit the 2.3 MB limit, too...
One of the solutions would be to move more parts to external modules, though.
Click to expand...
Click to collapse
Yer its the bad blocks in NAND its a harsh fact lol. You can see where tgey are in the recovery logs after applying a new boot.img from zip. If the kernel gets too big (even with modules) Google can remap the mtd partition layout of the device with a nrw SPL. The space is there when needed . Unlike the G1 the N1 has loads of space to play with

grainysand said:
My phone is one of the "lucky" ones. Kind of worrying; would be crappy if my phone can't take the Froyo update or something.
Click to expand...
Click to collapse
How do you check the max image size available?

Flash a new image with a different boot.img i.e Desire port over CM dont reboot use the "copy recovery.log to SD" option reboot and open that file from the SD card in notepad or whatever. see if u find any bad blocks under the writing boot section of the log :-D
if u find one u are limeted to small kernels

I'm pretty sure it's because of bad blocks on the partition. I'm not sure if the N1 NAND flash is more susceptible to bad blocks or what.

Hint:
Code:
$ cat /proc/mtd
Covert the mtd2 : /boot size to decimal ... and you will know what you looking for

I was wondering why I couldnt flash the latest EPF21B boot.img, and I checked the recovery.log to find 6 bad MTD blocks that could not be erased.. How disappointing.

Will HTC warranty/repair for bad blocks?

J.L.C. said:
Will HTC warranty/repair for bad blocks?
Click to expand...
Click to collapse
/facepalm
10char

JHaste said:
/facepalm
10char
Click to expand...
Click to collapse
Why facepalm?
I called them today and they're sending a shipping label for the repair...
*shrug*
________________________
N1 w/ XDA App

Yep, despite an unlocked bootloader, HTC has repaired my N1 TWICE to address the NAND's bad blocks. Turnaround time, if avoiding the weekend or holidays, was about 3 days. The repairs were free, didn't spend a dime. Nothing but good things to say about HTC's customer service!

smb7402 said:
Yep, despite an unlocked bootloader, HTC has repaired my N1 TWICE to address the NAND's bad blocks. Turnaround time, if avoiding the weekend or holidays, was about 3 days. The repairs were free, didn't spend a dime. Nothing but good things to say about HTC's customer service!
Click to expand...
Click to collapse
I'm expecting it to go smoothly since my bootloader is still locked
________________________
N1 w/ XDA App

hi, i am having the issue where i have the bad blocks as well, is there anyway to fix it besides sending it back to HTC? because i bought this phone from USA and now i am in AUS, it's a long time for me to post it back from here to them...

I am on the phone with HTC for resolution on this and they are acting like they have never heard of this problem. Perhaps I don't know the magic phrase to say.

bcjenkins said:
I am on the phone with HTC for resolution on this and they are acting like they have never heard of this problem. Perhaps I don't know the magic phrase to say.
Click to expand...
Click to collapse
They don't really seem to understand what it means....
I just received my phone back, after sending it in to have bad blocks repaired.
It seems as though they replaced the motherboard - I have a new IMEI number.
BUT - after doing a nandroid restore and checking recovery.log - I still have the exact same bad blocks in the exact same partitions, with the exact same addresses....

ROM Flash Limit for Galaxy Note...!!!(Unusual Question, but answer needed)

I have a question for you guys,
Q. Does anyone knows ROM flash limit for Galaxy Note?

bipinbedi said:
I have a question for you guys,
Q. Does anyone knows ROM flash limit for Galaxy Note?
Click to expand...
Click to collapse
Unlimited

bipinbedi said:
I have a question for you guys,
Q. Does anyone knows ROM flash limit for Galaxy Note?
Click to expand...
Click to collapse
I guess there is no limit of flashing roms
Even though there is a limit of flashing,it might be a six digit number

unlimited till u doing it right... limited .. if u having a bad day. LOL

bipinbedi said:
I have a question for you guys,
Q. Does anyone knows ROM flash limit for Galaxy Note?
Click to expand...
Click to collapse
It is just like how many times we can write/delete data from a pendrive or hard disk..i.e., read/write cycles which will be 10000 or more

shyamub4u said:
It is just like how many times we can write/delete data from a pendrive or hard disk..i.e., read/write cycles which will be 10000 or more
Click to expand...
Click to collapse
Don't think they release actual iops cycles data, but I imagine it's towards the 75k mark, never anything we'll achieve. Even if it's 35k iops which is the bottom end of cheap nand storage, we won't reach it.
Sent from my GT-N7000 using xda premium

SpyderTracks said:
Don't think they release actual iops cycles data, but I imagine it's towards the 75k mark, never anything we'll achieve. Even if it's 35k iops which is the bottom end of cheap nand storage, we won't reach it.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sorry..I didnt really mean that What I meant was, we read/write our pendrives many times & its very rare we see it getting spoiled because of too many read/writes..usually we spoil it by dropping it or something similar..sorry for consusing you..

definitely finite if you are using a stock kernel/rom so be wary of that

there are guys who have been flashing rom since gb. probably hundreds of time .. me my self have flashed more than 60 times.
it only limited if u brick ur phone.

wipe data/factory... later on, the os freezes and require reset

I got a note7000 offer at a bargain price; half the price of the original... the idea is that the guy is selling it as fault emmc bug. He told me that wiping the data - factory reset caused the problem.
The phone works from times to times he said, is still partially functional, thus he still asks for the price of SII for it, which he wants to replace with.
My question is:
Is the emmc bug permanent? I want to buy it cause is such a awesome screen\phone and i cant afford one from retails at full price. My plan is to downgrade from ics to gb with safe kernels and hope it wont brick with odin as unsafe as it is already.

Don't buy it. He is selling a bricked device for half the price (I wouldn't pay that for a used but fully functional right now).
And you will always get problems with it in many different situations.

Its risky for me, but also rewarding. If you'd seen this particular phone, is almost brand new. He told me it wasn't used much and that is visible on the over all aspect. And god, i love amoled screens, even if pentile is infamous.
Could you describe what you mean by being bricked? -> the phone boots and installs stuffs, but from time to times has the flaw of getting stuck -> require reset.
Its on the way
ps. I trust that if i had this stuff happen to me, coming from a samsung product, i would be able to get it fixed somehow.

Congrats: you just bought a bricked device. I guess he used the repartition workaround which reduces available capacity.
He didn't do the only real fix: replace motherboard in Samsung Service Center.
If you read here more before buying you would understand my "do not buy". Now you will learn later.
And he didn't lie to you - he told everything about the condition.
If you want to learn now while waiting for it, start to read about bricked devices here, about hg42's repartition thread etc. You might need it

Well, wish me luck. I'm gonna follow the steps from around the topics here.
I just hope i can watch movies, and pictures, and browse the mail... then he can get stuck but just a little.
I got an ace on my sleeves though. I can test it before i buy it... any advices, maybe doesn't even have the bug, how i notice
that ?

I'm gonna try these steps on the clip from rootgalaxynote:
youtube - hDtTNDVcTF4
If it doesn't work, i'm screwed cause i do not have a replace phone atm.

Following those steps will only mean that you won't brick it again... and anyway that is really outdated... When you've had enough of constant freezes then you will probably want to try a slim rom such as Slim Bean 4.2.2

I just purchased a n7000 from a guy on eBay for $350.00. It has the Ultimate rom installed in the screenshots. This means that it should be fine, right? I should receive it this week sometime. I bricked my i9100 back when the brick bug first appeared so I'm kind of worried about this.
Sent from my Nexus 4 using xda premium

Thanks for replies. I dunno what to expect. It is worrying, but probably i'll return it back cause is not worth the money if you put it this way "unusable".
He said to me to add a new sd card,,, i guess here is where he was just too honest. This confirms that there is actually a permanent damage to the hardware, especially the hefty 16 GB of memory.

My friend has the bug and he did the workaround , The phone freezes when you turn on bluetooth or wifi , And also the internal memory is low , but good luck with your's btw "restarting it from time to time" seems suspicious though
Sent from my GT-N7000 using xda app-developers app

KayKrate said:
My friend has the bug and he did the workaround , The phone freezes when you turn on bluetooth or wifi , And also the internal memory is low , but good luck with your's btw "restarting it from time to time" seems suspicious though
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Apparently that was a slight misleading. On itself doesn't restart. I got the phone right now. Is so huge even an elephant could use it.
Only freezes when i try write something thru usb cable. The ram is smaller, only 5 gb.

neier24 said:
Apparently that was a slight misleading. On itself doesn't restart. I got the phone right now. Is so huge even an elephant could use it.
Only freezes when i try write something thru usb cable. The ram is smaller, only 5 gb.
Click to expand...
Click to collapse
Really? Then it might be double-bricked and double "workarounded". Each time lossing about 3 GB...
When I close my eyes I see the grinning of this a--h-le who sold it for real money.

That sucks...
Now I want to see if is only a memory problem of the storage sd, or is as well as for the last 'bastion' of my phone, 2GB rom... cause then i can install slimbean like i've been adviced here.

neier24 said:
That sucks...
Click to expand...
Click to collapse
Why? You knew from the first day about the condition and bought it nevertheless.

ThaiDai said:
Why? You knew from the first day about the condition and bought it nevertheless.
Click to expand...
Click to collapse
First off, i'm in a bit of trouble right now. As you can guess, i can do something about it, cause beyond this is the morality of getting into a mess on someone's fault. Now that has to be decided, as long as is not mine.
This guy told me it is partially usable, add a card, try fix it yourself. At 190$ i expect to be better then a S1 or nexus s which might easly outmatch this phone. If is a matter of pride. Just keep it to yourself.
Either i give this guy a bad review as is a site as amazon, where user feedback is noted, or i return it back myself. Is not the holly grail, is just a phone.
He told me is not permanent damage.
LE: I got some good news and bad new:
I cannot add videos, it simply doesn't write. It doesn't freeze my phone anymore, this time i'm using samsung kies. Good news, i can write photos and songs.
I'm half way there in trusting this guy that with a sd card, the phone will work just okay in installing stuff.
On the other hand, i dunno if the internal storage is damaged; can i install jelly bean? or change the culprit kernel? or should i live with it as it is.

the seller has a no return policy. so ur actually screwed. you think the seller is a noob and that he didnt know about the fix. sometimes being too wise makes u feel and idiot in the end.
Sent from my GT-N7000 using xda app-developers app

Do you guys want to help, or keep ranting?
qazibasit learn some english.
How i change camera setting to save all its files on external microsd card?

neier24 said:
Do you guys want to help, or keep ranting?
qazibasit learn some english.
How i change camera setting to save all its files on external microsd card?
Click to expand...
Click to collapse
And now you are starting to get arrogant?
Even if I do not always follow qazis messages I do understand him very well - because Oxford english isn't a prerequisite here.
Members here can't help you: Why? Because you bought a brick device even when warned about it.

ThaiDai said:
And now you are starting to get arrogant?
Even if I do not always follow qazis messages I do understand him very well - because Oxford english isn't a prerequisite here.
Members here can't help you: Why? Because you bought a brick device even when warned about it.
Click to expand...
Click to collapse
How was his random ranting relevant to this topic?
So what do you think... flashing a new kernel and formating the sdcard do any good?
I may have a different term for bricking: When used in reference to consumer electronics, a "brick" describes an electronic device such as a smart phone, game console, router, or tablet computer that owing to a serious misconfiguration, corrupted firmware or a hardware problem, can no longer function. The term derives from the vaguely cuboid shape of many electronic devices (and their detachable power supplies) and the suggestion that the device can only function as a large, heavy object.
As far as i see, this device has stuff installed on it, and i can't figure how he did it.
recommend me a memory error checking app if u know, please!

Flash a safe kernel and flash a new ROM.. Try that and if all works good we´ll continue..

How bad it is to flash phone very often?

for example today I flashed(with full wipe every time) about 7-8 times....for finding a way to fix gps-network drop fix
normally... I flash about 5-6 times a week... :/
so this came to my mind.... how bad it is to flash too much??

@sandeep.sethi bro....what about you? developers+beta testers are crack flasher....by what extent??

Cpt.mactavish said:
@sandeep.sethi bro....what about you? developers+beta testers are crack flasher....by what extent??
Click to expand...
Click to collapse
i dont use my phone much
i flash rom maybe once in 3-5 days

Cpt.mactavish said:
for example today I flashed(with full wipe every time) about 7-8 times....for finding a way to fix gps-network drop fix
normally... I flash about 5-6 times a week... :/
so this came to my mind.... how bad it is to flash too much??
Click to expand...
Click to collapse
I don't find any harm in that, during my peak time with my phone, I flashed like 8-10 ROMs in a day. My phone is still working fine, but I recommend you to limit your time checking out ROMs, you might end up risking your internal storage.

there is an article on wikipedia I believe that says how many times a nand or nor memory can be written safe