Develop Bugs

Am I damaging my phone

Hello all,
Firstly thanks to all who create these great roms...
Secondly I have my flashed my phone more times than I can remember
my question is am I doing any damage to the device buy doing this....?

Nelkz said:
Hello all,
Firstly thanks to all who create these great roms...
Secondly I have my flashed my phone more times than I can remember
my question is am I doing any damage to the device buy doing this....?
Click to expand...
Click to collapse
the eprom on the device has a life, like all in the world...
I think it can support around 10.000 flashes, so be happy, don't warry!!

ervius said:
I think it can support around 10.000 flashes, so be happy, don't warry!!
Click to expand...
Click to collapse
Well... that depends. Nelkz said that he has flashed his phone more times than he can remember. Assume he has a photographical memory and he could recall till 10.001 previous flashes, that would mean he would have crossed the 10.000 flashlimit.

the flash storage also have a limited number of writes before it too dies
so passing these phones on to kids and grankids is prob out of the question
and the storage will die long before the flash with the rom in it

Rudegar said:
the flash storage also have a limited number of writes before it too dies
so passing these phones on to kids and grankids is prob out of the question
and the storage will die long before the flash with the rom in it
Click to expand...
Click to collapse
In 16 years my kids will probably laugh their pants of if I wanted to pass this (then prehistorical) device on to them.

Consider this: even under minimal use, like when you save a document and even dial a number, there would be something written to the device's flash rom.
The OS part is usually not being written at all except when you are really flashing it.
I think the OS flash rom can survive longer than the part of rom that make up your program storage, in theory.
Of course, in practice the flashes nowadays have mechanism to mark bad block, and even wear levelling in place.

Boot Time?

one thing i've been curious about and haven't seen a thing on in any of the numerous impression/review articles i've read is a note on the the speed of the handset's boot up time.
i've got a droid now, and i absolutely hate how long it takes to transition from powered-off to operational. i go off and do something else, and it takes long enough where i've forgotten about it by the time it turns fully on.
so how long is the EVO's?

Probably because almost everybody leaves their phone on...and don't care how long it takes really...
1 minute or 5 minutes really don't bother most people including me, so thats why it isn't really said in reviews.

I think I saw somewhere where they said it was kind of long. I assume because of the startup animations. I don't know anything about rooting but from what i've gathered you might be able to disable some of those.

Bowhuntr11 said:
Probably because almost everybody leaves their phone on...and don't care how long it takes really...
1 minute or 5 minutes really don't bother most people including me, so thats why it isn't really said in reviews.
Click to expand...
Click to collapse
ok?
...and your point posting in this thread was? i don't care how many people leave their phone on, or the time frame that a phone needs to turn on in so not to bother people; i was asking how long the EVO takes to boot up. so thanks a lot.

In answer to your question... fast! Most boots seem to take about 20 to 30 seconds for me but one boot did take a minute. Regardless, it's faster than any Sense phone I have ever seen. throw AOSP on here and it should boot even faster.

awesome - appreciate the answer.
and yeah, i could imagine it powering up a bit faster with some tuning from xda.

I seen one IO user say his boot time on the Evo was less than a minute but I assume it also is a bare, non-custom, no extra apps device.

Boot time is definitely less than a minute, I'm using the HelixLauncher2 so everything comes up real fast after boot.
It's night and day compared to my old Hero.

I was just going to ask about this...
From fully OFF to the second I can see my lock screen(note, not fully operational yet, but can see the lockscreen), takes 1 minute and 20 seconds. Thats running Fresh 3.3 with whatever kernel comes with that Rom. A kid I go to school with, he has the same rom and kernel, his boots up to fully operational in about 45 seconds.
Just wondering if I can shorten that somehow.
Also, wondering if music and pictures have anything to do with it? Having to load all of that from the sd card might cause the delay?

Holy thread resurrection, Batman!

chazglenn3 said:
Holy thread resurrection, Batman!
Click to expand...
Click to collapse
Quick, to the archives Robin!!

Alright, I'm sorry lol. But you cant be THAT upset with me, I searched before posting. Just didnt take note of the dates. sorry!

jasongthang said:
Alright, I'm sorry lol. But you cant be THAT upset with me, I searched before posting. Just didnt take note of the dates. sorry!
Click to expand...
Click to collapse
I was just having fun and not neccessarily really teasing. At least you searched and this was the result so nothing too serious really

Same here...I wasn't busting your chops...just thought it was funny that you searched that deep...kudos on the search!

It's all good.

That, my lads, may have been epic.
Sent from my PC36100 using XDA App

Mine takes around....a minute and a half. This is with a 32GB microSD card, Apps2SD (with virtually every app I use, including most of the stock apps installed on my microSD, and dalvik on the cache partition.)

TheMagicalSock said:
That, my lads, may have been epic.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
ok... lad.. lol

freeza said:
Mine takes around....a minute and a half. This is with a 32GB microSD card, Apps2SD (with virtually every app I use, including most of the stock apps installed on my microSD, and dalvik on the cache partition.)
Click to expand...
Click to collapse
Where did yoou get your 32GB card from?

klbjr said:
Where did yoou get your 32GB card from?
Click to expand...
Click to collapse
Verizonwireless.com

[Q] Is over flashing possible?

May seem like an odd question but on my old Kaiser (Windows phone I know) I started to get block errors after flashing Android to NAND repeatedly. The developers and gurus there said it was a known problem and that it would continue to worsen, at which point I stopped
The question is, is it possible to over flash the G2?
I KNOW... different device/hardware/OS and all but I confess to being concerned. Is there any chance that repeated flashing is going to cause long term issues?

Don't think you can but I would like a straight answer from someone who knows what there talking about also
Sent from my HTC Vision using XDA Premium App

No. Things just age with use.
It's like the same question with computers, If i never shut it down will it kill my computer? If i reformat my hard drive too much will it kill it? no. while many factors do need to be take into consideration but not so much with phones, And most electronics do have hours powered on stats and each device does have that. but as far as phones i really couldnt tell you.

flash memory can be rewritten 100,000,000 times..... so the answer is yes... (thats a real fact btw)

master.peterm said:
flash memory can be rewritten 100,000,000 times..... so the answer is yes... (thats a real fact btw)
Click to expand...
Click to collapse
yeah but not typical. i have a better chance in dropping my phone in the toilet then over flashing haha.

master.peterm said:
flash memory can be rewritten 100,000,000 times..... so the answer is yes... (thats a real fact btw)
Click to expand...
Click to collapse
Oh crap! Since I'm a 'flashaoholic' Its getting up there on that many time times! GEEZ!
Sent from my HTC Vision using Tapatalk

Once a week....
Thanks to all for the answers. I guess I've got a long way to go to 1,000,000,000 but if devs keep putting out new and improved ROMs I'll keep flashing them.
Good to know the concensus is that, even at one a week I have a few years worth

NAND is typically good to at least tens or hundreds of thousands of read/writes.
http://en.wikipedia.org/wiki/Flash_memory
So even for flashaholics, the frequency of flashing is really not much of a concern. Sure, there is some tiny possibility that memory can randomly fail at any time. And the more you do it, the higher the chance of that occuring. But its not significant, and I wouldn't worry about it.
Even when talking about flash memory on things like SSD drives, that get re-written much more frequently, I believe the mean failure time is often spoken of as being at least 10 years, and often much longer due to various wear-leveling techniques.

xamadeix said:
No. Things just age with use.
It's like the same question with computers, If i never shut it down will it kill my computer? If i reformat my hard drive too much will it kill it? no. while many factors do need to be take into consideration but not so much with phones, And most electronics do have hours powered on stats and each device does have that. but as far as phones i really couldnt tell you.
Click to expand...
Click to collapse
Eh I disagree. Reformatting too much can be a problem with flash memory. My mother, for example, always used to reformat her camera SD card instead of just erasing all the images normally (I know, facepalm). Over only two or three years, her pictures were unable to be developed because the SD card was corrupt. The gold strips on it looked like they had been beat to hell. It wasn't a cheap brand either, it was a Sandisk.
Although, with phones I don't think it's a problem. Lets face it, most of us won't have the same phone for over two years, many won't even have them past one year. We won't be using our phones long enough to get to that point.

slapshot30 said:
Eh I disagree. Reformatting too much can be a problem with flash memory. My mother, for example, always used to reformat her camera SD card instead of just erasing all the images normally (I know, facepalm). Over only two or three years, her pictures were unable to be developed because the SD card was corrupt. The gold strips on it looked like they had been beat to hell. It wasn't a cheap brand either, it was a Sandisk.
Although, with phones I don't think it's a problem. Lets face it, most of us won't have the same phone for over two years, many won't even have them past one year. We won't be using our phones long enough to get to that point.
Click to expand...
Click to collapse
I don't know how you thought that reformatting something could physically damage the gold contacts on it. That's probably because she took the card out and put it back in a ton of times.
Sent from my G2 running Cyanogenmod 7.

Omg i was actually thinking of your question.. cause my battery is really hot!! Hopefully its not for that reason.
Sent from my HTC Vision using XDA App

ibemad1 said:
I don't know how you thought that reformatting something could physically damage the gold contacts on it. That's probably because she took the card out and put it back in a ton of times.
Click to expand...
Click to collapse
Yeah, it sounds like some physical abuse, and not just from reformatting it. I've swapped SD and Micro-SD cards in and out of devices and card readers countless times, and never had any damage to the contacts. Mama might be inserted the card incorrectly, or to forcefully.
In any case, that example is just anecdotal. The failure could have been for any random reason. Memory can just stop working one day. Doesn't mean that formatting it was the cause.

Wow....didnt even know that overflashing is possible. ...... . But still on a low number i will get there in less than 10 years (maybe)

got back to stock ROM

I rooted my phone about half a year ago, and now, finally I got back to the stock ROM. You may ask why, so here is why I initially rooted it, and then why I got back to the stock ROM.
My main reason for rooting was the extremly small sized internal storage. Even with the "stock" app2sd it was hell like fast full. Of course customizen played also a role, and I liked the ability to change like everything the way I like, but moving nearly the whole apps was the main reason.
So I finally decided to root my phone. The process was (in opposite of what I thought) really easy, especially with the help of this awesome guide and I chose "MIUI" as the first OS to try out. I really liked it, but I had some occasional crashes which I wasn't able to solve. But that wasn't the reason I got back to the stock ROM. After about 2-3 months with "MIUI" my complete phone got stock in a bootloop. Flashing the zip again wasn't succesfull, so I finally tried an older backup. This worked, but sadly all my SMS data and else got lost.
After some searching I tried out cyanogenMod. I liked it quite well, but I also got the crashes and freezes I got with MIUI, but I was able to live with it. But then, about a week ago, my phone got completly stuck in a bootloop, and instead of throwing it straight ahead into a wall, I flashed back to the stock ROM.
At first I was quite surprised how fluidly it runs, in comparision to cyanogenMod. Then I noticed, that you can't really switch between 3G and 2G data, and was afraid of getting out of energy much sooner. But the opposite happened, the battery lasts much longer than with the other two ROMs, and I hadn't had any crashes or complete freezes till yet. Also, I haven't got the great warning "Battery level 0% or lower (how is this even f*ing possible?), please connect to power source" I got on cyanogenMod, with the addition of my phone shutting down immediately afterwards.
So, long story, short: I really like the ability to root my phone and everything, and I do not regret having done it. It was a great experience, I now I know the "true" capability of android. But after all this trying out, I have to say, that I think I will now stick with the stock ROM, since it's more stable. Probably it was a hardware issue with my device, probably some kind of software bug. Maybe something of both.
just my quick thoughts, and sorry for my bad english, but it's not my native language

To each his own.
I've been using Cyanogenmod more often than any other rom and never experienced bootloops that is caused by the rom itself. It's always something I did with the rom. LOL

Well, that's also a possibility, but since I wasn't able to find the cause of it, I gave up. It was not only the bootloop, but also the quick battery draining and the complete freezes.

I understand where you are coming from... You just want it to work properly.
As for the battery, the default cm7 kernel isn't really that good compared with ManU kernel. That's the first thing I change when I flash.

Now I'm taking my stopwatch to count how long will it take for loons to start Runnymede or ICS recommendations.
Sent from my HTC Desire using Tapatalk

Long story short??
Maybe you should publish the unedited version...could be a few volumes in that.
Also, will never go back to stock. I unrooted last year, so I could set up for S-Off, and couldn't wait to get back to a custom ROM. Slow, boring, low storage and boring.
You should use Runnymede, it's the best ROM ever!

Annddd there you have it Erklat.

haha. Funny. And necessarily runnymede

You have luck with the Battery, my phone say 15% or Lower and shutdown, if yours work down to 0%

stankyou said:
Annddd there you have it Erklat.
Click to expand...
Click to collapse
I was being facetious

MetinKale38 said:
You have luck with the Battery, my phone say 15% or Lower and shutdown, if yours work down to 0%
Click to expand...
Click to collapse
Well, that was the problem with it...the battery showed 20 percent when it happened...
btw, the stock rom didn't solve that problem either, but at least the crashes are gone...it's still pretty weird, the battery level showed like 20% or more when it suddenly shut down...

Battery life has always been dreadful on the Desire no matter what ROM you use.
Now on the bootloop, Sandvold ICS Beta 0.4.4 ROM seems to be getting on well.
No bootloops whatsoever!
(Some lags and bugs may occure, but nothing you can't handle with a little bit of patience! )

What was I saying -.-'
Sent from my HTC Desire using Tapatalk

erklat said:
What was I saying -.-'
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Page 2... not a bad prediction man. LOL

erklat said:
What was I saying -.-'
Sent from my HTC Desire using Tapatalk
stankyou said:
Page 2... not a bad prediction man. LOL
Click to expand...
Click to collapse
Click to expand...
Click to collapse
erklat, what will be the numbers in tomorrow nights Lottery draw??
O, I'm in Australia, btw.
kthxbai

777ace said:
erklat, what will be the numbers in tomorrow nights Lottery draw??
O, I'm in Australia, btw.
kthxbai
Click to expand...
Click to collapse
16 24 27 30 36 44
supps 5 13
You are welcome!!

I am so gonna try those!!

Nascor said:
My main reason for rooting was the extremly small sized internal storage. Even with the "stock" app2sd it was hell like fast full.
Click to expand...
Click to collapse
So, how did you resolve the issue with the storage now?
I'm using MIUI too and it runs rock solid for me since months. Next time I will switch, I will switch to a new phone...

hudl said:
So, how did you resolve the issue with the storage now?
I'm using MIUI too and it runs rock solid for me since months. Next time I will switch, I will switch to a new phone...
Click to expand...
Click to collapse
well, since my new Transformer Prime is now my primary mobile gaming device, I just put the most necessary apps on my phone (like facebook, twitter, maps and stuff like that)

Thanks Nascor, Its very important the information.

New To Android, but bricked my phone?

Well i think it is. I rooted my phone last night and installed the beats drivers from the Play Store. Shortly, it froze and went straight to the Samsung logo. I can still go into both recovery and download mode, but what do I do after that? I've heard about Odin....but how do i exactly put the custom roms into my phone, and which ones? And if any one can point me to a guide or tutorial, ill be extremely relieved. I'm new to the website as well as android, so if anyone could please help me out, thanks

When you rooted did you NANDROID backup ? If not go into recovery and clear cache and then go into advanced and wipe delvik cache. reboot
If that fails go back into recovery and do a factory reset and you should be ok.

touchdownadrian said:
Well i think it is. I rooted my phone last night and installed the beats drivers from the Play Store. Shortly, it froze and went straight to the Samsung logo. I can still go into both recovery and download mode, but what do I do after that? I've heard about Odin....but how do i exactly put the custom roms into my phone, and which ones? And if any one can point me to a guide or tutorial, ill be extremely relieved. I'm new to the website as well as android, so if anyone could please help me out, thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1727401

This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone

z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
I disagree as long as you are willing to learn from the mistake all is good. I had a Samsung Exhibit II and deleted touch wiz launched (I was using go launcher) later I would do a factory reset and well... learned that system files do not get restored when you do a factory reset...oops
Sent from my SGH-T999 using xda premium

I agree, we all were NOOBS at some point. That's the one thing I love about XDA is that with patience and the help of the users any noob can learn how to mod their devices. One piece of advice that I can offer is before you do any type of modding is READ and keep on READING. I have bricked the first device I ever rooted because I did not READ the forums as they are meant to be read.

z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
Yea, not cool dude..remember that WE were all NOOBS at some point in time, therefore we should support and help one another. As for what to do next, follow "Saldebot's" instructions and you should be fine. Sounds like it's only a soft brick. Just keep reading and learning as much as you can bud.
Sent from my SGH-T999 using xda premium

Thanks guys, it worked. And my bad for not reading alot, im kinda new to this lol
Sent from my SGH-T999 using xda premium

not fair
z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:

touchdownadrian said:
Thanks guys, it worked. And my bad for not reading alot, im kinda new to this lol
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It's not the noobs who shouldn't be rooting... It's the lazy and careless who should stick to stock. If you are careful and diligent, rooting and all the good stuff that comes with it is easy and rewarding.

TheSeanTeam said:
It's not the noobs who shouldn't be rooting... It's the lazy and careless who should stick to stock. If you are careful and diligent, rooting and all the good stuff that comes with it is easy and rewarding.
Click to expand...
Click to collapse
I whole-heartily agree, I was a freshman noob August 1st this year, by August 4th I was flashing like a pro. Left and right, ROMs, Kernels, Modifying system files, you name it. I wanted to streamline my phone and future proof it somewhat by overclocking. I spent 3 days researching and educating myself, finding the best ROMs, weighing pros and cons, and when it came time to flash, I was on my PC all day making sure whatever I did wouldn't brick me. I carefully analyzed and learned about virtually all methods of flashing by watching tons of videos and reading a bunch of tutorials by several sources. I MD5 checksum'd every zip to be flashed on my phone using an app (to ensure download and transfer was successful). I must have verified that the files I was preparing to flash were indeed for my device make and model about a dozen times before ever touching a button. When I went to flash over my first custom Kernel (even though I had already flashed 2 custom ROMs shortly before that), on that last button my hands were literally shaking, I could not afford a second Galaxy S III. Everything went beautifully, all of my careful planning and hours of invested research payed off. I had done everything right and was rewarded with better battery life (about +50% on heavy load and +500% on idle) and performance (+25%).
My girlfriend also has a Galaxy s3 and she wanted the same performance I was getting. I flashed the exact same software to her device I had to mine, no changes.
Total time invested in flash on my device: 36 hours, at least
Total time invested in flash on her device: 1 hour... if that
The bottom line is yes, if you're not willing to put forth the effort and educate yourself first, you probably shouldn't be doing this. There are guides and tutorials out there for noobs and I would recommend you go there first until you know your way around your device. That way at least you have a little experience on your belt before you start doing anything too advanced (I did this when I was rooting my device for the first time).
As a side note, I know there are a lot of people out there worried about doing anything that could potentially brick their device. That is always a real possibility, I'm not going to lie to you, it happens more often than you think. However in just about every case of bricking you'll ever hear about, it's usually someone flashing something they're not suppose to, like a ROM designed for a different make and model of device, or something experimental that wasn't ready yet. Do all your homework (from multiple corroborating sources) before you undergo a flash and as long as you do everything "by the book" (so to speak) and don't rush through things by being lazy, you should be fine. Some even flash nightlies (yeah they're called that for a reason, updated versions of the ROM they currently have) EVERY NIGHT!!! In the end when you have an android device, you have an open source platform at your fingertips and you should take advantage of that, it would be a waste not to. If not, your next device might as well be an iPhone. They're great for noobs and as long as you're ok drinking whatever punch Apple gives you, they're pretty much impossible to brick since you can't do a whole lot with them. Apple will be happy to take your money and stiff you with closed source for it.

lordazoroth said:
I whole-heartily agree, I was a freshman noob August 1st this year, by August 4th I was flashing like a pro. Left and right, ROMs, Kernels, Modifying system files, you name it. I wanted to streamline my phone and future proof it somewhat by overclocking. I spent 3 days researching and educating myself, finding the best ROMs, weighing pros and cons, and when it came time to flash, I was on my PC all day making sure whatever I did wouldn't brick me. I carefully analyzed and learned about virtually all methods of flashing by watching tons of videos and reading a bunch of tutorials by several sources. I MD5 checksum'd every zip to be flashed on my phone using an app (to ensure download and transfer was successful). I must have verified that the files I was preparing to flash were indeed for my device make and model about a dozen times before ever touching a button. When I went to flash over my first custom Kernel (even though I had already flashed 2 custom ROMs shortly before that), on that last button my hands were literally shaking, I could not afford a second Galaxy S III. Everything went beautifully, all of my careful planning and hours of invested research payed off. I had done everything right and was rewarded with better battery life (about +50% on heavy load and +500% on idle) and performance (+25%).
My girlfriend also has a Galaxy s3 and she wanted the same performance I was getting. I flashed the exact same software to her device I had to mine, no changes.
Total time invested in flash on my device: 36 hours, at least
Total time invested in flash on her device: 1 hour... if that
The bottom line is yes, if you're not willing to put forth the effort and educate yourself first, you probably shouldn't be doing this. There are guides and tutorials out there for noobs and I would recommend you go there first until you know your way around your device. That way at least you have a little experience on your belt before you start doing anything too advanced (I did this when I was rooting my device for the first time).
As a side note, I know there are a lot of people out there worried about doing anything that could potentially brick their device. That is always a real possibility, I'm not going to lie to you, it happens more often than you think. However in just about every case of bricking you'll ever hear about, it's usually someone flashing something they're not suppose to, like a ROM designed for a different make and model of device, or something experimental that wasn't ready yet. Do all your homework (from multiple corroborating sources) before you undergo a flash and as long as you do everything "by the book" (so to speak) and don't rush through things by being lazy, you should be fine. Some even flash nightlies (yeah they're called that for a reason, updated versions of the ROM they currently have) EVERY NIGHT!!! In the end when you have an android device, you have an open source platform at your fingertips and you should take advantage of that, it would be a waste not to. If not, your next device might as well be an iPhone. They're great for noobs and as long as you're ok drinking whatever punch Apple gives you, they're pretty much impossible to brick since you can't do a whole lot with them. Apple will be happy to take your money and stiff you with closed source for it.
Click to expand...
Click to collapse
Same here. It took me months of researching on my vibrant before flashing my first rom (bionix 1.6 by teamwhiskey). As I progressed, I did brick left and right but I always managed to bring it back to life with my prior knowledge. Now I'm eagerly waiting for my computer to be done downloading the root files and get started.
Sent from my SGH-T999 using xda app-developers app

Cr vibe said:
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:
Click to expand...
Click to collapse
Omg I LOVED THE VIBRANT! Restoring it from a brick was a piece of cake
Sent from my SGH-T999

Cr vibe said:
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:
Click to expand...
Click to collapse
+++++++1 on that.... DAMN talk about headaches....

dmarco said:
Yea, not cool dude..remember that WE were all NOOBS at some point in time, therefore we should support and help one another. As for what to do next, follow "Saldebot's" instructions and you should be fine. Sounds like it's only a soft brick. Just keep reading and learning as much as you can bud.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
:good::good:

Yeah one of the only other IMPORTANT thinks i could add would be always do a factory reset before flashing roms.. some people like to flash "dirty" i wouldnt recommend it cause you will ALWAYS have issues maybe not in a hour but guaranteed you will... but knowledge is power dude.. i two read for about 36 hours before rooting my phone.. i rooted my wifes phone days after a rooted mine back in the day it only took like 15 mins.. another thing let phone sit 10 mins before ya play with it... gotta let the cache settle... the ten min wait is well worth it.. ive been doing it that way since the vibrant bro.. happy flashing and welcome..

I read constantly things change hourly like when that new leaked kernels came out for sgs2 and the emmc was trashed never to come back from a brick again. To anyone that cares if you love your phone read more than just the root and flash stuff learn what makes your phone tick from the factory hardware software and added crap from your carrier it all play's a part in the end result. Its as easy as you make it.
Sent from my SGH-T999 using Tapatalk 2

Nabeel10 said:
Omg I LOVED THE VIBRANT! Restoring it from a brick was a piece of cake
Sent from my SGH-T999
Click to expand...
Click to collapse
Ive passed down two vibrants (both rooted) to my sons so they can learn to flash roms and everything else that comes from the joys of root.
Sent from my SGH-T999 using xda app-developers app