[ROM] ROOTROM and Themed roms - Sense 2.5 - SMS/MMS - Sashimi Compliant - 05/26/2010

[rootlinux]

It does effect the custom roms if you have random issues.

[iknowsquat]

Originally Posted by drdrewdown

are you doing the flash dance?

stock shipped rom --> custom rom

[faint]

Exsqueeze me? Could you speak into my GOOD ear?
You're not suggesting...that it was...a BAD FLASH?!

[rootlinux]

Originally Posted by winmonewbie

[faint]

exsqueeze me? Could you speak into my good ear?
You're not suggesting...that it was...a bad flash?!

lmao

[drdrewdown]

Originally Posted by winmonewbie

[faint]

Exsqueeze me? Could you speak into my GOOD ear?
You're not suggesting...that it was...a BAD FLASH?!

you didn't see me type "bad flash", as always i suggest the flash dance because a lot of people dont know to do it if they have issues. a "bad flash" would suggest the flash was incomplete or failed at some point thru the process like i tried to explain last time its all irrelevant anyway & primarily just a debate topic we can have fun with. nice try tho, lets play again soon =] hehe

[botnryan]

i always thought the idea of a "bad flash" was odd. from the point of downloading the rom to unzipping it to flashing it to being done flashing it, its basically an all or nothing type of deal it would seem to me.

When downloading it you'll either get all of it or none. if the download doesnt complete successfullly then the .zip/.rar file will be corrupt. When unzipping it will either complete it or corrupt it. When flashing it, it will either do it, or it wont. If the flash completes youre phone will work correctly, unless the rom you had on it before hand had radio data that conflicts with the new rom (which can be fixed by flashing stock) I think that is the most common thing called a "bad flash" and actually has nothing to do with the Custom rom flash the person just did. Also, IMO, most of these "bad flashes" are after people have installed CABS that mess with the rom in a negative way and cause it to not work correctly. When you flash a rom from your computer, to your phone (or SD card to phone), the data is there, on your phone. otherwise the little bar would never reach 100%. you can reflash and reflash and reflash, its just going to put the same data on the phone again. Now if a custom Rom had some weird radio data it flashed to your phone, then you flash straight to another custom rom thats expecting the normal stock radio info, you might have a problem. i really dont agree with the whole "bad flash" thing either drew.

[drdrewdown]

Originally Posted by botnryan

i always thought the idea of a "bad flash" was odd. from the point of downloading the rom to unzipping it to flashing it to being done flashing it, its basically an all or nothing type of deal it would seem to me.

When downloading it you'll either get all of it or none. if the download doesnt complete successfullly then the .zip/.rar file will be corrupt. When unzipping it will either complete it or corrupt it. When flashing it, it will either do it, or it wont. If the flash completes youre phone will work correctly, unless the rom you had on it before hand had radio data that conflicts with the new rom (which can be fixed by flashing stock) I think that is the most common thing called a "bad flash" and actually has nothing to do with the Custom rom flash the person just did. Also, IMO, most of these "bad flashes" are after people have installed CABS that mess with the rom in a negative way and cause it to not work correctly. When you flash a rom from your computer, to your phone (or SD card to phone), the data is there, on your phone. otherwise the little bar would never reach 100%. you can reflash and reflash and reflash, its just going to put the same data on the phone again. Now if a custom Rom had some weird radio data it flashed to your phone, then you flash straight to another custom rom thats expecting the normal stock radio info, you might have a problem. i really dont agree with the whole "bad flash" thing either drew.

wow amen brotha. tried to but couldn't say it as good as you well done

[em1davis]

Originally Posted by botnryan

i always thought the idea of a "bad flash" was odd. from the point of downloading the rom to unzipping it to flashing it to being done flashing it, its basically an all or nothing type of deal it would seem to me.

When downloading it you'll either get all of it or none. if the download doesnt complete successfullly then the .zip/.rar file will be corrupt. When unzipping it will either complete it or corrupt it. When flashing it, it will either do it, or it wont. If the flash completes youre phone will work correctly, unless the rom you had on it before hand had radio data that conflicts with the new rom (which can be fixed by flashing stock) I think that is the most common thing called a "bad flash" and actually has nothing to do with the Custom rom flash the person just did. Also, IMO, most of these "bad flashes" are after people have installed CABS that mess with the rom in a negative way and cause it to not work correctly. When you flash a rom from your computer, to your phone (or SD card to phone), the data is there, on your phone. otherwise the little bar would never reach 100%. you can reflash and reflash and reflash, its just going to put the same data on the phone again. Now if a custom Rom had some weird radio data it flashed to your phone, then you flash straight to another custom rom thats expecting the normal stock radio info, you might have a problem. i really dont agree with the whole "bad flash" thing either drew.

You know I thought the same thing till I had a series of bad flashes. No matter what ROM I installed (over 5 roms kept trying to find the "non-buggy" rom) it would constantly lock up, a soft reset would turn into a hard reset this was all with the Rom no extra CABs. I nearly tossed my TP until I flashed a stock rom and went back to custom roms I haven't had an issue since.

[drdrewdown]

Originally Posted by em1davis

You know I thought the same thing till I had a series of bad flashes. No matter what ROM I installed (over 5 roms kept trying to find the "non-buggy" rom) it would constantly lock up, a soft reset would turn into a hard reset this was all with the Rom no extra CABs. I nearly tossed my TP until I flashed a stock rom and went back to custom roms I haven't had an issue since.

a series of bad flashes lol. then you flashed the stock rom, hrrm.. so wonder why that wasn't a so-called "bad flash" lol. c'mon now. its like most people are saying, the stock rom overwrites something the custom roms are doing. but it has nothing to do with a bad flash. u need the stock rom to do its thing, & then flash the custom rom. why would you think its a series of bad flashes & then it amazingly works fine after a stock flash.

[botnryan]

the flash of the custom rom was not bad. it flashed just fine. the rom you had on it BEFORE you flashed obviously didnt mesh well with something on the new rom and cause malfuntioning of the device. thats why when you flashed to stock and then to the new custom it worked correctly. theres no "bad flash" there at all. Just "bad following-of-directions" Although in some instances i realize it still works to flash from a custom rom directly to another, just in some cases it doesnt work and going to stock, im willing to say, will ALWAYS fix that problem. has nothing to do with the flash you just did, it has to do with the rom on the phone before the flash. THAT is what causes the problems.

[drdrewdown]

Originally Posted by botnryan

the flash of the custom rom was not bad. it flashed just fine. the rom you had on it BEFORE you flashed obviously didnt mesh well with something on the new rom and cause malfuntioning of the device. thats why when you flashed to stock and then to the new custom it worked correctly. theres no "bad flash" there at all. Just "bad following-of-directions" Although in some instances i realize it still works to flash from a custom rom directly to another, just in some cases it doesnt work and going to stock, im willing to say, will ALWAYS fix that problem. has nothing to do with the flash you just did, it has to do with the rom on the phone before the flash. THAT is what causes the problems.

+1million