Related
I have been rooting now for almost 2 months and I have noticed that I am always trying to find and use the latest and greatest ROM. The problem is, I can't figure out the "greatest" part.
I will flash from ROM A and then the next day I will flash to ROM B then another day ROM C, both Sense and AOSP ROM's.
I don't know what it is but I just can't seem to stick with a ROM for more then a few days without feeling the twitch or urge to flash to something else.
So, anyone else ever have this issue? If so, how did you fix it?
I am loving all of these ROM's. It's like an all you can eat buffet with all these ROM's and I can't fill my plate.
Whiteice
I get my fix with cyanogenmod nightlies let me get my fix while still keeping the same rom
elegantai said:
I get my fix with cyanogenmod nightlies let me get my fix while still keeping the same rom
Click to expand...
Click to collapse
Since you mentioned it, I have a question for you.
How exactly do these "nightlies" work? I recently tried the most stable ROM and I am digging it.
Whiteice
Ko!
WhiteiceDMSTech said:
Since you mentioned it, I have a question for you.
How exactly do these "nightlies" work? I recently tried the most stable ROM and I am digging it.
Whiteice
Click to expand...
Click to collapse
Nightlies is produce and includes wtv new code (and sometimes kernel) tweet it(forgot the username)
Back to the topic I agree and that's the reason that I didn't want to root when I got the evo cause I get flashaholic but I like myns a lot and CM7 I don't which one to stay, sometimes I feel that I should unroot my phone and stop wasting my time downloading so many roms. I'm running miui flashed an hour ago lol
Edit : btw downloading another rom lol
Is hard man I tell you
Sent from my PC36100 using Tapatalk
jgalan14 said:
Ko!
Nightlies is produce and includes wtv new code (and sometimes kernel) tweet it(forgot the username)
Back to the topic I agree and that's the reason that I didn't want to root when I got the evo cause I get flashaholic but I like myns a lot and CM7 I don't which one to stay, sometimes I feel that I should unroot my phone and stop wasting my time downloading so many roms. I'm running miui flashed an hour ago lol
Edit : btw downloading another rom lol
Is hard man I tell you
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Yeah it is stressful isn't it lol. I blame it on my ADD.
I used MIUI as my first ROM and loved it. Then started jumping around trying out others as I got more familiar with the rooting stuff.
I tried last weeks MIUI and I kept getting so many force closes (even after full wipes and 2 different fresh installs).
WhiteiceDMSTech said:
Yeah it is stressful isn't it lol. I blame it on my ADD.
I used MIUI as my first ROM and loved it. Then started jumping around trying out others as I got more familiar with the rooting stuff.
I tried last weeks MIUI and I kept getting so many force closes (even after full wipes and 2 different fresh installs).
Click to expand...
Click to collapse
Yeah I didn't root my phone since I got it (June 4) and I didn't root until late August and I was happy with all my apps and stuff but then I root. Try fresh, calk, cm6, virus, and kept bouncing myn came out it with his rom and I was happy for like 2 weeks (thought I found the right one) then they got the HD working and miui and start flashing again like crazy, barnacles, sprints lovers, mik froyo, miui, and any other rom, and I haven't recover since then Mm my last resort would be unroot cause when I get a ron for over a week something brakes (besides myns, calk) and flash another one and some other rom comes out lol, well at least we got a great community I don't know what other phone has the same support ( besides nexus one)
Sent from my PC36100 using Tapatalk
CM for life...i think that a requirement for me when getting a new phone is if teamdouche pours their sauce on it
Swyped from my cyanogenized and gingerbreaded EVO
WhiteiceDMSTech said:
Yeah it is stressful isn't it lol. I blame it on my ADD.
I used MIUI as my first ROM and loved it. Then started jumping around trying out others as I got more familiar with the rooting stuff.
I tried last weeks MIUI and I kept getting so many force closes (even after full wipes and 2 different fresh installs).
Click to expand...
Click to collapse
I kept flashing till i tried miui.
Get a new release every week!
(did you set wifi sleep policy to never?)
aimbdd said:
I kept flashing till i tried miui.
Get a new release every week!
(did you set wifi sleep policy to never?)
Click to expand...
Click to collapse
I thought the wifi sleep policy was only to fix random reboots?
WhiteiceDMSTech said:
I thought the wifi sleep policy was only to fix random reboots?
Click to expand...
Click to collapse
miss read that. yeah it is. Weird, i havnt had a single one all week... xD
I've stuck with the same rom for months now. I actually hate switching.
WhiteiceDMSTech said:
I have been rooting now for almost 2 months and I have noticed that I am always trying to find and use the latest and greatest ROM. The problem is, I can't figure out the "greatest" part.
I will flash from ROM A and then the next day I will flash to ROM B then another day ROM C, both Sense and AOSP ROM's.
I don't know what it is but I just can't seem to stick with a ROM for more then a few days without feeling the twitch or urge to flash to something else.
So, anyone else ever have this issue? If so, how did you fix it?
I am loving all of these ROM's. It's like an all you can eat buffet with all these ROM's and I can't fill my plate.
Whiteice
Click to expand...
Click to collapse
haha! that sounds exactly like me.
i keep my daily mikfroyo v4.5, netarchy 4.3.2-cfs-nosbc-havs-less, DT A2sd and flash 2-3 times a week theres a lot of roms i like cm6/7, fresh, koni, kings. i keep going back to MIK. depends on what u want in a ROM i guess..
Thanks I was loving the cm7 been flashing it every update and so on only problem I had was the camera app not taking 8 mp pics and the voice mail issue with the text thing blacklist option is nice wish u could block unknown number .
Hi everyone,
I made a stupid error last night and I flashed the wrong rom to my phone :S I flashed a AT&T ROM, now my phone won't turn ON at all tried all combination to go into download mode nothing happen. When I plug it to my computer it required a driver that I couldn't find. to make it worse I called T-mobile hoping that they will help me but they couldn't because I don't have a prove of purchase :S since I bought it from someone else.
Any idea what can I do ?
Yep, it's dead for good unless someone has figured out how to make/use a USB jig for the TMO SGS2... that's why we read before flashing roms.... it's never really a good idea to flash a rom from a different device anyway.
What a retarded mistake, seriously?
You go to flash a ROM but fail to even recognize that they are two totally different phones?
If you are that clueless you should not even be flashing ANYTHING
Sent from my SGH-T989 using xda App
Seriously u shouldn't be flashing. Better make use of that paperweight
Sent from my SGH-T989 using XDA App
sometimes I wonder how somebody can want to flash a phone, but not even be able to identify there own phone our even read the instructions
Sent from my SGH-T989 using XDA App
Tunisiano32 said:
Hi everyone,
I made a stupid error last night and I flashed the wrong rom to my phone :S I flashed a AT&T ROM, now my phone won't turn ON at all tried all combination to go into download mode nothing happen. When I plug it to my computer it required a driver that I couldn't find. to make it worse I called T-mobile hoping that they will help me but they couldn't because I don't have a prove of purchase :S since I bought it from someone else.
Any idea what can I do ?
Click to expand...
Click to collapse
I doubt it'll come back to life without a USB jig. You can try calling T-Mobile for a replacement again and just tell them you need a warranty replacement...the person you were speaking to probably doesn't know that proof of purchase is not required. I've never had to show proof of purchase and always gotten my phones from somewhere other than tmobile, but I think that would be considered fraud in your case since its not really a mistake on the manufacturers part....
Does it boot up? if it doesn't boot at all you're golden. Just call in for a warranty replacement.
Sent from my SGH-T989 using xda premium
Yes, even if you do not have a proof of purchase, you can call Samsung directly and get it replaced.
Please remember this guy came here for help not to be criticized. I also know that when something like this happens, it's no fun and he's probably feeling bad enough as it is, so why add salt to injury?
Thank you for all your good replies, say what ever I'm retard or anything you want. I made a mistake ( because I didn't pay attention ). This is not the first time I flash a phone ( I flashed my previous Nexus one and flashed my HD7 ) and I previously flashed my Galaxy S II with BeastMod, I don't know how I missed it this time.
Thank you for the time that you wasted to tell me how retarded I am.
I ordered a USB jig last night and I'm waiting for it if it didn't work I'll send it to Samsung.
While I was searching to try to help Tunisiano, I came across another thread about a "bricked phone"...LOL
Apologies for laughing, but this guy in the other thread said his gf bricked his phone when she flashed the wrong rom from another device. He said he left his phone in the house for a while when he went out and she tried to flash a rom for him cause she does not like the TW launcher...LOL
...Idk if he's telling the truth or not but that was funny and people there bombed him for that...(I'm sure some of you were on that thread). I mean come on, "my gf flashed the wrong rom for me" LOL
Ur right...post edited
OP-sorry if I offended you....hope u get it replaced
Sent from my SGH-T989 using XDA App
solution
solution is www.mobiletechvideos.com i promise u josh can bring it back to life. He is great.... send him an email and he will hit u back right away. It costs like 40 bucks no biggie. Just go to the website. I assure u have nothing to worry about. Don't listen to these guys making fun of u **** happens... its really no big deal u can send ur phone tomorrow have it back working in a week.
safeplayer22 said:
While I was searching to try to help Tunisiano, I came across another thread about a "bricked phone"...LOL
Apologies for laughing, but this guy in the other thread said his gf bricked his phone when she flashed the wrong rom from another device. He said he left his phone in the house for a while when he went out and she tried to flash a rom for him cause she does not like the TW launcher...LOL
...Idk if he's telling the truth or not but that was funny and people there bombed him for that...(I'm sure some of you were on that thread). I mean come on, "my gf flashed the wrong rom for me" LOL
Click to expand...
Click to collapse
LOL yea that's a likely story.
I can sort of understand what the OP did, I mean, it's the "even if I know it's not the right thing it's close enough and if I do it just right maybe it will work or I can make it work" thing. Haven't we all experienced this at one time or another? We learn from this stuff
Good luck OP, at least you didn't get pwned by your girlfriend!
Tunisiano32 said:
Thank you for all your good replies, say what ever I'm retard or anything you want. I made a mistake ( because I didn't pay attention ). This is not the first time I flash a phone ( I flashed my previous Nexus one and flashed my HD7 ) and I previously flashed my Galaxy S II with BeastMod, I don't know how I missed it this time.
Thank you for the time that you wasted to tell me how retarded I am.
Click to expand...
Click to collapse
I don't think you are retarded, just the mistake.
We all make them, this one was just easily avoidable
Hopefully the jig works, I haven't heard about anyone trying it yet
Sent from my SGH-T989 using XDA App
I did it, not ashamed, it happens and I'm by no means new to the root and ROM game. Odin'd recovery and forgot to untick repartition. Same thing you got...Qualcomm high speed USB interface...this phone is way more sensitive in download mode than the vibrants are. So I brought mine back once for that then two more times for the screen.
Sent from my SGH-T989 using xda premium
Radsolutionz said:
solution is www.mobiletechvideos.com i promise u josh can bring it back to life. He is great.... send him an email and he will hit u back right away. It costs like 40 bucks no biggie. Just go to the website. I assure u have nothing to worry about. Don't listen to these guys making fun of u **** happens... its really no big deal u can send ur phone tomorrow have it back working in a week.
Click to expand...
Click to collapse
They can't do it for T-989, only AT&T version of Galaxy S II
My first two word in my post was " Stupid mistake" because I know that it's preventable...
There's no one among us who hasn't made some type of mistake at some point in life so lay off the guy.
Sue you might not make THIS particular mistake but that's aside from the point.
For him to meekly ask people for advice while openly admitting an error that he could've lied about or blamed on a made up entity and receive this brand of childish, elitist, holier than thou, insulting nonsense is an embarrassment to the rest of us.
Sorry about your mistake man. Good luck and I hope that you don't think everyone on xda is a huge infantile douche.
Sent from my SGH-T989 using xda premium
Hopefully you can get it replaced
This exact post happens like 15 times a day if you guys have not noticed....you are not alone
I would just say my phone got really hot and no longer turns on.
Assuming you have warranty
Sent from my SGH-T989 using XDA App
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
ive asked a couple time on here before about this but all i ever get is smart remarks. i have a s3 that i have had rooted and put hell fire rom on it.idk if that has anything to do with the problem. i been running hell rom for about a month with no problems. and one day i wake up and my phone didnt cut on or nothing. i never droped it. so i know its not that. after messing with it for awhile i figured out that the phones led comes on when connected to a power source with out the battery in the phone. it will not do this with the battery in it. i have tryed booting into download mode. it never worked. im curious to think it is a battery issue. but i cant be sure. and before i waste my money on a battery it would be great to get some help on what to do or what the problem is..
Jtag sevice
codey895 said:
ive asked a couple time on here before about this but all i ever get is smart remarks. i have a s3 that i have had rooted and put hell fire rom on it.idk if that has anything to do with the problem. i been running hell rom for about a month with no problems. and one day i wake up and my phone didnt cut on or nothing. i never droped it. so i know its not that. after messing with it for awhile i figured out that the phones led comes on when connected to a power source with out the battery in the phone. it will not do this with the battery in it. i have tryed booting into download mode. it never worked. im curious to think it is a battery issue. but i cant be sure. and before i waste my money on a battery it would be great to get some help on what to do or what the problem is..
Click to expand...
Click to collapse
Did you try connecting it to your PC?
Sent from my SGH-I747 using xda premium
zap12341 said:
Did you try connecting it to your PC?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
yes. it didnt reconize it. but maybe im just missing somthing..
if you connect to your computer does it usb wizard come up saying "QHSUSB_DLOAD"?
my phone is in the same situation as yours right now. completely bricked
How is it even possible to get a complete brick by not flashing anything? Just wake up one morning and your phone doesn't turn on? Doesn't make any sense...
I have and the S1,2 &3 flashed 100's of ROMs and usually the only thing that can hard brick a Samsung is flashing a ROM/Kernel for another phone or a bad flash from ODIN.
Sent from my SAMSUNG-SGH-I747 using xda premium
Jason123420 said:
How is it even possible to get a complete brick by not flashing anything? Just wake up one morning and your phone doesn't turn on? Doesn't make any sense...
I have and the S1,2 &3 flashed 100's of ROMs and usually the only thing that can hard brick a Samsung is flashing a ROM/Kernel for another phone or a bad flash from ODIN.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
im not here lien. honestly thats what happen.
If you think it could be a battery issue, try going to a local place that sells the phone and just ask if you could try a battery in your phone.
jeeper11 said:
If you think it could be a battery issue, try going to a local place that sells the phone and just ask if you could try a battery in your phone.
Click to expand...
Click to collapse
thats my plan. although i did ask walmart and they said no lol.
You did something that youre not telling us because things dont just break randomly, and/or without cause 99% of the time.
I dont help people that try to act like "i dont know what happened, it just magically stopped working maybe a unicorn tampered with the motherboard while i was asleep" kind of nonsense.
The guys on here are trying to help you and youre not giving any information at all. So go and waste your money and buy batteries, service calls from a repair center.
But "i dont know maybe im missing something", and "i dont know what happened" is not an acceptable response from someone seeking help.
So go ahead and pulll out all the four letter words and insults, but until you start to pony up some good information your phone will be dead, and you can begin preparing it for its next stage of "life" which would be a desk decoration or christmas tree ornament
ssCISengineer said:
You did something that youre not telling us because things dont just break randomly, and/or without cause 99% of the time.
I dont help people that try to act like "i dont know what happened, it just magically stopped working maybe a unicorn tampered with the motherboard while i was asleep" kind of nonsense.
The guys on here are trying to help you and youre not giving any information at all. So go and waste your money and buy batteries, service calls from a repair center.
But "i dont know maybe im missing something", and "i dont know what happened" is not an acceptable response from someone seeking help.
So go ahead and pulll out all the four letter words and insults, but until you start to pony up some good information your phone will be dead, and you can begin preparing it for its next stage of "life" which would be a desk decoration or christmas tree ornament
Click to expand...
Click to collapse
stop being so mean bro. if i knew anything else i would tell you. ive had tons of android phones and have fixed all my problems. i understand you need more info. well so do i. everything i told you is the truth. and 100% true of what happen. nothing has ever happen to me like this. if you cant help, thats fine. i understand that. but just say that. dont be rude and disrespect to me just cause "you think" im lieing.
I seen someone mention that
People have been labeling tw roms and aosp roms incorrectly,There have been an unusual amount of brick topics lately, anyone else wondering if we are dealing with standard "flashing" user error, or actual misleading info on certain roms . Many of the most novice to longtime xda members have even been bricking over the stupidist stuff.
This device t999 specifically
bricking this(any) phone by flashing an incorrect rom isnt that easy to be honest... plus the worst that can happen by flashing is usually a softbrick a.k.a bootloop. (unless your an idiot and you flash stuff from a different device)
i mean i may just be way too experienced after 8 years of hacking away at android, but its not simple to brick a phone. its usually caused by lack of attention. for example, most people dont even read the OP of roms threads the whole way. they just download and flash and come back and say "why doesnt this work?"
im also curious how many people actually tried to use ODIN to restore there phone before they proclaimed "hard brick"
ziggy46 said:
i mean i may just be way too experienced after 8 years of hacking away at android, but its not simple to brick a phone.
Click to expand...
Click to collapse
I have literally 4.5 months of experience with Android and I feel the way you do so I think it's largely lack of paying attention or not doing the research and reading first. I've tried multiple ROMs on my phone and I've helped friends learn how to root and understand the process of installing ROMs and no one has had a brick yet.
If you jump out of an airplane without learning how to use your parachute what do you expect ?
The S3 most likely has a high number of bricks because it has a huge user-base - thus even if the proportions are the same as other devices there are more people by number who are trying things without knowing what they're doing and those people are going to end up with bricks.
I've certainly seen times when the ROM was to blame, but it's almost always not a hard brick. That's the chance you take with installing a custom ROM - sometimes there are bugs and stuff happens. If you can't accept that possibility don't flash.
Pennycake said:
I have literally 4.5 months of experience with Android and I feel the way you do so I think it's largely lack of paying attention or not doing the research and reading first. I've tried multiple ROMs on my phone and I've helped friends learn how to root and understand the process of installing ROMs and no one has had a brick yet.
If you jump out of an airplane without learning how to use your parachute what do you expect ?
The S3 most likely has a high number of bricks because it has a huge user-base - thus even if the proportions are the same as other devices there are more people by number who are trying things without knowing what they're doing and those people are going to end up with bricks.
I've certainly seen times when the ROM was to blame, but it's almost always not a hard brick. That's the chance you take with installing a custom ROM - sometimes there are bugs and stuff happens. If you can't accept that possibility don't flash.
Click to expand...
Click to collapse
ahh the userbase! thats a good one thanks for pointing it out. i also believe that users from other variants end up here and flash the incorrect rom by google-ing "roms for s3" and going to the first xda link they see. which may lead to flashing improper roms resulting in the $400 paper weight
999 times out of 1000 it's user error.
DaMn NoObS
Sent from my SGH-T999 using Tapatalk 2
Yes user error is to blame nobody likes to search or even read for that matter
Reading fixes 99.999% of all common newb problems
Sent from my SGH-T999 using Tapatalk 2
If anyone hard bricks this device they deserve it. You literally almost have to intentionally try to brick in order to do so.
On another note... I haven't seen many brick threads with ppl that actually broke their devices
Sent from my SGH-T999 using Tapatalk 2
Most brick threads I've seen lately are either softbricks, boot loops or not bricked at all, just errors from dirty flashing.
Sent from my SGH-T999 using xda premium
ziggy46 said:
ahh the userbase! thats a good one thanks for pointing it out. i also believe that users from other variants end up here and flash the incorrect rom by google-ing "roms for s3" and going to the first xda link they see. which may lead to flashing improper roms resulting in the $400 paper weight
Click to expand...
Click to collapse
+1 i definitely agree with what you said. my friend searched on google "how to root galaxy s3" attempting to root her AT&T GS3, and almost ended up with a brick (she found an international s3 root method) had she not came and asked me first...phew that was close.
It's just called common sense, not many have it.
Most I have seen are soft breaks and user panics before either: clearing cachy and factory reset or Odin. They just jump straight to I have a break.
Sent from my SGH-T999 using xda premium
Name of post should be "Strange amount of idiots bricking their phones"
Sent from Flip's S3
ziggy46 said:
bricking this(any) phone by flashing an incorrect rom isnt that easy to be honest... plus the worst that can happen by flashing is usually a softbrick a.k.a bootloop. (unless your an idiot and you flash stuff from a different device)
i mean i may just be way too experienced after 8 years of hacking away at android, but its not simple to brick a phone. its usually caused by lack of attention. for example, most people dont even read the OP of roms threads the whole way. they just download and flash and come back and say "why doesnt this work?"
im also curious how many people actually tried to use ODIN to restore there phone before they proclaimed "hard brick"
Click to expand...
Click to collapse
Wow bro 8 years of android hacking? Can I borrow your flux capacitor? First android phone released 10/2008
sbell7105 said:
Wow bro 8 years of android hacking? Can I borrow your flux capacitor? First android phone released 10/2008
Click to expand...
Click to collapse
i over-exaggerated a little its actually only about 5 years... im 16 now and i started when i was 10-11ish
ziggy46 said:
i over-exaggerated a little its actually only about 5 years... im 16 now and i started when i was 10-11ish
Click to expand...
Click to collapse
Aww man 16? does that mean I wasted my flux capacitor reference? Just messing around I figured it was a typo or something I just couldn't resist :laugh:
NoOooOoOObs
ziggy46 said:
bricking this(any) phone by flashing an incorrect rom isnt that easy to be honest... plus the worst that can happen by flashing is usually a softbrick a.k.a bootloop. (unless your an idiot and you flash stuff from a different device).........
im also curious how many people actually tried to use ODIN to restore there phone before they proclaimed "hard brick"
Click to expand...
Click to collapse
I'm one. (lol)
Aerowinder said:
999 times out of 1000 it's user error.
Click to expand...
Click to collapse
bfranklin1986 said:
DaMn NoObS
Click to expand...
Click to collapse
Google and XDA Premium have been my friend throughout my past few years with T-Mobile... since the days of my Behold, Memoir, Samsung Galaxy S 4g, and now my SGS3... I've found a great piece of mind in knowing I'm not a complete idiot, nor am I the first to screw something up.
And while I have made a few devices "boot-loop" from time to time, rooting is easy as pie. And if you happen to research before you do any job, you might learn a thing or two. I specifically love the threads (on any forum, not just here) where someone posts "READ CAREFULLY" followed by "DOWNLOAD LINK" and just two or three replies later, there has to be that one r-tard that asks "What do I do? Where's the download link? I'm so confused!". I want to piss in their coffee and break their mug over their face. Literacy is depleting; and there's little we can do about it.
sbell7105 said:
Wow bro 8 years of android hacking? Can I borrow your flux capacitor? First android phone released 10/2008
Click to expand...
Click to collapse
Hilarious!
Things have gotten so much easier. My only brick was a g1 (HTC dream). Things were a lot trickier then. It had an IPL-initial program loader (bootloader) and an SPL-secondary program loader (radio). Some roms required the bootloader from the the HTC magic (mytouch3g). Not all dream radios were compatible with the magic bootloader. So you always flashed a magic compatible radio first then bootloader. One night when it was really late, I was repeating the flash I had already done I my own g1 but on my wife's g1 this time. I accidentally reversed the order and BOOM, hard brick. In that state, the ipl can't hand off to the spl. Only option was hardware jtag that hadn't been discovered yet.
She was pissed.
Sent from my SGH-T999
Remember when I rooted my first (lg optimus v) I thought with a recovery I could flash any Rom...thankfully I have learned otherwise and didn't have to learn by looking like an idiot.I came very close to flashing some random Rom probably from the evo4G
Fortunately laziness actually served me well lol
Sent from my SGH-T999 using xda premium