Related
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
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
Although I wouldn't term myself a pro at all, I am not a noob when it comes to rooting and installing other ROMs. I have rooted many of my Android phones over the years and have diligently read and re-read posts when it comes to rooting and installing ClockworkMod recovery and other ROMs.
Last week, I made a big boo-boo!
I searched for "Sprint SGS3 alternate ROMs" and found a CNet article (http://reviews.cnet.co.uk/mobile-phones/top-5-samsung-galaxy-s3-custom-roms-50009440/) listing the different ROMs. I downloaded a couple (Hawkish and Energy) and promptly tried to install them. I got some error message in CWM. I then rebooted after cleaning caches, dalvik etc.
My phone wouldn't start at all!!!
I tried all the keypresses to get things working but absolutely nothing. The unit wouldn't turn on even with a separately fully charged battery. I tried to borrow a USB Jig from a user in this post (http://forum.xda-developers.com/showthread.php?t=1869203) but no-one was able to help. As the phone was my only phone (no landline) I was readying myself to pay the $60 that one of the other sites charged to JTag the unit.
Before I did that, I decided to take it in to Sprint, and told the technician I made a mess up. They didn't ask anything about what I did and took it to the back for about half an hour. They weren't able to do anything as the unit didn't switch on, but said that I could get a replacement for $50.
I did that and a few days later they swapped out the non-working unit for a working one. I was expecting to pay a whole lot more.
I learned the lesson the hard way: even if I search for "Sprint" the results aren't necessarily going to be for my unit. I should have read (and re-read!) the posts a whole lot more clearly about the other ROMs - they were not for the Sprint unit.
I hope my hard lesson will help others be a wee bit more cautious - even if you have been customizing a long time!
This is about the 100th post this month of people flashing roms for other carriers on a Sprint S3. A simple search in the Q&A would have probably alerted you to the facts.
Transmitted with a portable device using Xparent Blue Tapatalk 2
I *do* realize that I flashed the wrong ROM. The point of my post was to illuminate that it's not only noobies who get things wrong.
Even though I read what I thought was for Sprint, my presumption got in the way and I didn't realize until it was too late that it was not the ROM in the Sprint section of Http://www.xda-developers.com/ that I thought I was reading about.
I took responsibility for my mistake and paid the money to rectify my error.
I am hoping that my misfortune with be a cautionary tale for others to double (and triple) check.
Just because we've done things successfully many times before doesn't mean we're avert to the same errors as noobies.
IconBoy said:
I *do* realize that I flashed the wrong ROM. The point of my post was to illuminate that it's not only noobies who get things wrong.
Even though I read what I thought was for Sprint, my presumption got in the way and I didn't realize until it was too late that it was not the ROM in the Sprint section of Http://www.xda-developers.com/ that I thought I was reading about.
I took responsibility for my mistake and paid the money to rectify my error.
I am hoping that my misfortune with be a cautionary tale for others to double (and triple) check.
Just because we've done things successfully many times before doesn't mean we're avert to the same errors as noobies.
Click to expand...
Click to collapse
If you would've read more carefully you wouldn't have made that mistake... noob! Jk
SPRINT GS3 FAQ
Feel bad but at the same time I dont. You should know a bit better to be sure that you can use that ROM/kernel/zip etc. If you doubt yourself ask in the thread or forum. We all don't know everything there is to rooting and flashing
http://i1202.photobucket.com/albums/bb374/TexasEpic/ThePeoplesROM-KennyGlass123/daniel4653.png
Odexed Blue by Strong Steve + Ktoonz w/ Team Kernelizers tweaks
In the cnet article it had this in the "getting started section"
Just bear in mind that if your S3 handset is not version number I9300 -- and it almost certainly is if you bought it in the UK -- then bad things can happen. So it's worth quickly checking your phone's settings before proceeding.
Click to expand...
Click to collapse
Discuss...
Sent from my SPH-L710 using xda app-developers app
I have to give you credit Iconboy for taking responsibility and paying for a new phone. Even though you messed up you admitted it. A lot of people that have done the same thing have posted things like "can I throw my phone in a river" or "can I just tell sprint that the OTA broke my phone". Thanks for doing it right.
metalfan78 said:
I have to give you credit Iconboy for taking responsibility and paying for a new phone. Even though you messed up you admitted it. A lot of people that have done the same thing have posted things like "can I throw my phone in a river" or "can I just tell sprint that the OTA broke my phone". Thanks for doing it right.
Click to expand...
Click to collapse
Yeah I agree. I don't know why people are bashing him. He maned up and payed for a replacement phone and now he is just letting other people know what can happen.
Sent from my SPH-L900 using xda premium
I did the same thing with my S3 about a month ago, Was on a flashing frenzy and didn't read enough about the rom i was flashing. After the flash my phone wouldn't do anything at all, just a paperweight. Took it into sprint and paid for a new one. Mistake learned, its part of being human.
musclehead84 said:
Yeah I agree. I don't know why people are bashing him. He maned up and payed for a replacement phone and now he is just letting other people know what can happen.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
No one is bashing him, just having some fun at his expense, but you're right, thanks for doing the right thing op!
SPRINT GS3 FAQ
Like others have said, props for owning your mistake. However, the "noob" label applies to you, whether you think so or not. There were so many signs you were walking down the wrong path (including an explicit warning on the very page) the very first being that you were on a .uk website. I'm not posting this about that though, I just don't seem to understand why so many people feel the need to venture away from xda to acquire ROMs, this site if full of great ROMs made by great devs, not sure what more people need to end up flashing things they find on international news sites. Yes, there are other established sites, but usually they overlap with this site. That is to say, if there's something awesome happening somewhere else, you'll hear about it here (with a few exceptions).
Whether I am classified as a "noob" or not ... I have flashed custom ROMs on four or five different Android phones over the years.
The Motorola Photon was one where I thought I had a paperweight (nope...not an int'l ROM that time - Ha! Ha!) but because of XDA, I was able to get it working again after many errors. Decent little phone that one.
My error, my expense, my fault on the SGS3. Thankfully I have a working unit and can put the old EVO in the drawer as a backup - it is sloooow!
IconBoy said:
Whether I am classified as a "noob" or not ... I have flashed custom ROMs on four or five different Android phones over the years.
The Motorola Photon was one where I thought I had a paperweight (nope...not an int'l ROM that time - Ha! Ha!) but because of XDA, I was able to get it working again after many errors. Decent little phone that one.
My error, my expense, my fault on the SGS3. Thankfully I have a working unit and can put the old EVO in the drawer as a backup - it is sloooow!
Click to expand...
Click to collapse
Glad you got it worked out. Its not easy admitting (and on the internet to say the least) that you had made a mistake even as a seasoned flasher. Its never easy to admit an error, at all
I agree with metalfan above and I applaud you, you made a mistake and you paid for it, lesson learned
Well... Don't re-read is for noobs. Sorry if that hurts you.
Sent from my SPH-L710
IconBoy said:
Whether I am classified as a "noob" or not ... I have flashed custom ROMs on four or five different Android phones over the years.
The Motorola Photon was one where I thought I had a paperweight (nope...not an int'l ROM that time - Ha! Ha!) but because of XDA, I was able to get it working again after many errors. Decent little phone that one.
My error, my expense, my fault on the SGS3. Thankfully I have a working unit and can put the old EVO in the drawer as a backup - it is sloooow!
Click to expand...
Click to collapse
You may not be a "noob" in the technical sense of that term, but as you already know, the mistake you made was an amateurish one. For one, you were on a .uk website, and second, the very article mentions that you have to be mindful of your model number and specifically mentions buying in the UK. There were at least 3 checkpoints in that article that should have prompted further scrutiny on your part. I do commend you for taking responsibility for your actions and for you PSA to be careful about what you flash, and I do understand how you got tripped up. This is probably the first Android phone that was released to multiple carriers worldwide. Also, what I would like to see from devs is a conspicuous message in the OP of their ROM about specifically which carrier/version their ROM is for. Often that is not mentioned.
So let me prose this question to everyone calling him a noob (including our devs) - why don't devs write their install scripts to read the current build.prop to check for the correct model before the wipe & install begins? If this is happening hundreds of times per month, a pretty small amount of scripting could probably stop this from happening 99% of the time.
Sent from my SPH-L710 using xda app-developers app
rocket321 said:
So let me prose this question to everyone calling him a noob (including our devs) - why don't devs write their install scripts to read the current build.prop to check for the correct model before the wipe & install begins? If this is happening hundreds of times per month, a pretty small amount of scripting could probably stop this from happening 99% of the time.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Good point. Bad code leads to bad problems. And its actually a very simple line of code in the updater-script that would abort, but increasingly people are dropping that habit and changing to a no-check install
Code:
assert(getprop("ro.product.device")=="DEVICE_NAME" && getprop("ro.product.board")=="DEVICE_NAME")
IconBoy said:
Although I wouldn't term myself a pro at all, I am not a noob when it comes to rooting and installing other ROMs. I have rooted many of my Android phones over the years and have diligently read and re-read posts when it comes to rooting and installing ClockworkMod recovery and other ROMs.
Last week, I made a big boo-boo!
I searched for "Sprint SGS3 alternate ROMs" and found a CNet article (http://reviews.cnet.co.uk/mobile-phones/top-5-samsung-galaxy-s3-custom-roms-50009440/) listing the different ROMs. I downloaded a couple (Hawkish and Energy) and promptly tried to install them. I got some error message in CWM. I then rebooted after cleaning caches, dalvik etc.
My phone wouldn't start at all!!!
I tried all the keypresses to get things working but absolutely nothing. The unit wouldn't turn on even with a separately fully charged battery. I tried to borrow a USB Jig from a user in this post (http://forum.xda-developers.com/showthread.php?t=1869203) but no-one was able to help. As the phone was my only phone (no landline) I was readying myself to pay the $60 that one of the other sites charged to JTag the unit.
Before I did that, I decided to take it in to Sprint, and told the technician I made a mess up. They didn't ask anything about what I did and took it to the back for about half an hour. They weren't able to do anything as the unit didn't switch on, but said that I could get a replacement for $50.
I did that and a few days later they swapped out the non-working unit for a working one. I was expecting to pay a whole lot more.
I learned the lesson the hard way: even if I search for "Sprint" the results aren't necessarily going to be for my unit. I should have read (and re-read!) the posts a whole lot more clearly about the other ROMs - they were not for the Sprint unit.
I hope my hard lesson will help others be a wee bit more cautious - even if you have been customizing a long time!
Click to expand...
Click to collapse
I'd say your a noob. Title is wrong. Lol.
.co.uk <----- not even us website.
Did you see "sprint" or d2spr any where? No.
Derp.
Sent from my SPH-L710 using xda premium
rocket321 said:
So let me prose this question to everyone calling him a noob (including our devs) - why don't devs write their install scripts to read the current build.prop to check for the correct model before the wipe & install begins? If this is happening hundreds of times per month, a pretty small amount of scripting could probably stop this from happening 99% of the time.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
How about a counter point, if the noobs would read before flashing, it would stop this from happening 100% of the time! If you don't have time to read before trying to mod your device, you shouldn't be doing it in the first place...
Will always wonder why people find the right place just a second after they turn theirs phones into a fully functional brick.
Sent from my SPH-L710
hi everyone! I am seeking your expertise as I came upon this forum trying to help my son fix his phone. He's only 11 years old- but as we call him at home our "tech guy". He got a brand new HTC One M8 (carrier is ATT) yesterday and 3 hours later - the phone was "bricked" as I have been told. Apparently, (these are his words) he "unlocked the bootloader using HTCdev, then flashed twrp, then flashed supersu.zip.
I have no idea what any of that means but apparently he did something wrong because his phone is not working and we don't know how to fix it. If you have any compassion for a frustrated Mom who's trying not to be angry with her son -- I would appreciate any advice you can give on how to fix this.
I have attached a picture of what the phone looks like when we turn it on. I also posted this under the ATT forum too.
Thanks in advance for your help!
You bought your 11 year old son an M8?
Do you adopt?
Bchgirl19 said:
hi everyone! I am seeking your expertise as I came upon this forum trying to help my son fix his phone. He's only 11 years old- but as we call him at home our "tech guy". He got a brand new HTC One M8 (carrier is ATT) yesterday and 3 hours later - the phone was "bricked" as I have been told. Apparently, (these are his words) he "unlocked the bootloader using HTCdev, then flashed twrp, then flashed supersu.zip.
I have no idea what any of that means but apparently he did something wrong because his phone is not working and we don't know how to fix it. If you have any compassion for a frustrated Mom who's trying not to be angry with her son -- I would appreciate any advice you can give on how to fix this.
I have attached a picture of what the phone looks like when we turn it on. I also posted this under the ATT forum too.
Thanks in advance for your help!
Click to expand...
Click to collapse
Going by the pic, the bootloader has been relocked. So that's a problem. The bootloader will need to be unlocked again. I would suggest heading over to Youtube, as I have found video tutorials the most helpful when I was learning this stuff. There are plenty of videos that are even specific to the M8.
Edit: I should also point out that a phone can almost always be saved/restored if it still powers on. So don't panic. It would probably be in your best interest though to find someone experienced to fix it. Trying to explain the process to fix it here is not going to be helpful to someone who doesn't know what they're doing. If you can't find someone experienced, then my best suggestion, as stated above, would be to watch some Youtube tutorials on unlocking/rooting the M8.
Okay. In all seriousness.
When was this screen grab taken? In other words, is this your current position with the phone?
Relocked... etc etc
Are you in the US on AT&T?
Your tech son needs to restore ATT backup.. Hopefully someone in that forum has it
sent from my mobile device
UPDATE on my son
Thank you all so much for your responses! It is much appreciated. Believe it or not - this kid fixed it all by himself. Basically (remember I am not technical) he unlocked the boot loader then flashed a ROM onto an SD card and was able to load. Don't think I worded correctly - but I think you know what I am talking about -- it's fixed and working fine. WHEW!!
I guess he "retraced" the steps he did last night and was able to get it. Actually it's strange the first ROM he put on wasn't allowing him to find or pick up wifi. He found another and got it. This kid is good!
I will certainly keep the info to this forum handy because something tells me that I will be visiting again with this child..................
Have a great evening!!
p.s. I typed the wrong key -- he's 12 not 11 And - sure I'd adopt! But he did save up his own money to get this phone and only wanted it to do these "cool" things as he says to it.....rest of my family - we are simple and use Iphones -- sorry.
All I can say to this is Wow!!
Bchgirl19 said:
Thank you all so much for your responses! It is much appreciated. Believe it or not - this kid fixed it all by himself. Basically (remember I am not technical) he unlocked the boot loader then flashed a ROM onto an SD card and was able to load. Don't think I worded correctly - but I think you know what I am talking about -- it's fixed and working fine. WHEW!!
I guess he "retraced" the steps he did last night and was able to get it. Actually it's strange the first ROM he put on wasn't allowing him to find or pick up wifi. He found another and got it. This kid is good!
I will certainly keep the info to this forum handy because something tells me that I will be visiting again with this child..................
Have a great evening!!
p.s. I typed the wrong key -- he's 12 not 11 And - sure I'd adopt! But he did save up his own money to get this phone and only wanted it to do these "cool" things as he says to it.....rest of my family - we are simple and use Iphones -- sorry.
Click to expand...
Click to collapse
I'm glad to hear everything worked out for you and your son.
It's great to know that you're letting your kid tinker around as he is. I know these are quite expensive devices, but we often do learn from our mistakes, and that is even more true when it comes to technology. I'm sure that I have a bit of a bias being a software developer, but tech is such a huge part of life now, and that is only going to become more so with time. So getting an early start as he is, your son is going to have a leg-up in the world, even if he doesn't choose this type of field as a career path.
MindfulSheep said:
I'm glad to hear everything worked out for you and your son.
It's great to know that you're letting your kid tinker around as he is. I know these are quite expensive devices, but we often do learn from our mistakes, and that is even more true when it comes to technology. I'm sure that I have a bit of a bias being a software developer, but tech is such a huge part of life now, and that is only going to become more so with time. So getting an early start as he is, your son is going to have a leg-up in the world, even if he doesn't choose this type of field as a career path.
Click to expand...
Click to collapse
Agree! But keep an eye on him, so that he sleeps from time to time. And hide your car keys!
Please don't create multiple threads asking the same question.
http://forum.xda-developers.com/showthread.php?t=2750594
MindfulSheep said:
I'm glad to hear everything worked out for you and your son.
It's great to know that you're letting your kid tinker around as he is. I know these are quite expensive devices, but we often do learn from our mistakes, and that is even more true when it comes to technology. I'm sure that I have a bit of a bias being a software developer, but tech is such a huge part of life now, and that is only going to become more so with time. So getting an early start as he is, your son is going to have a leg-up in the world, even if he doesn't choose this type of field as a career path.
Click to expand...
Click to collapse
Thanks!! He's very into all of this stuff and always has been from a very young age -- started with Legos at 2. He doesn't play sports and this is his "thing". He really LOVES all this stuff. He's actually really good and understands most things. As you can see - we certainly have issues now and then but overall we certainly let him "tinker". I really should write stuff down so we can laugh about it in about 10 years. We tried to limit his Internet time a couple of years ago and added a password on his computer that we had to input on his computer to gain access. Little **** put a keystroke logger on the computer to get the password. Then he somehow modified the main password screen to say PENIS when we logged on. The stories go on and on....... We will let him continue his technology building and hopefully he really have a bright future in technology!
Thanks for all of the input and support from this forum!
Bchgirl19 said:
Thanks!! He's very into all of this stuff and always has been from a very young age -- started with Legos at 2. He doesn't play sports and this is his "thing". He really LOVES all this stuff. He's actually really good and understands most things. As you can see - we certainly have issues now and then but overall we certainly let him "tinker". I really should write stuff down so we can laugh about it in about 10 years. We tried to limit his Internet time a couple of years ago and added a password on his computer that we had to input on his computer to gain access. Little **** put a keystroke logger on the computer to get the password. Then he somehow modified the main password screen to say PENIS when we logged on. The stories go on and on....... We will let him continue his technology building and hopefully he really have a bright future in technology!
Thanks for all of the input and support from this forum!
Click to expand...
Click to collapse
I was the same from an early age and always have been. I have taken apart or modified more household items than I can think of. I broke a lot of stuff messing as a kid, but now I have a lot of knowledge and can fix almost any thing properly.
It seems you are not so bad yourself with the technical stuff as most moms wouldn't have a clue or even be able to repeat what you have explained here.
mods please delete
next time, use reddit or twitter to ***** about people doing whatever they want with their stuff.
Levent2101 said:
next time, use reddit or twitter to ***** about people doing whatever they want with their stuff.
Click to expand...
Click to collapse
You need to watch your language. Cursing is against the rules.
And i am allowed to complain if i want too. My givin right. If u dont like my complaints dont post on em.
TheMadScientist420 said:
You need to watch your language. Cursing is against the rules.
And i am allowed to complain if i want too. My givin right. If u dont like my complaints dont post on em.
Click to expand...
Click to collapse
TheMadScientist420 said:
Really???
I mean i understand that this is a kindof temp fix to get data off device
But. Wtf. You guys in reality all your doing is voiding waranty. Absorbimg moisture from the fridge. Setting off the moisture strips.
Like this is the first time ive heard this one and thats got to be the dumbest idea ive ever heard. And from what i read it dont even work half the time or more. Its boots up for 30 40 seconds. Isnt a fix.
Then as the device heats up in the fridge just makes even more condensation.
WOW. Ive heard it all now
Click to expand...
Click to collapse
Err... Do you know what WTF actually means? You need to watch your language also!
Sent from my Nexus 6P using Tapatalk
tharweb said:
Err... Do you know what WTF actually means? You need to watch your language also!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
i didnt come out and say it if thats the case corecting me or not u just said i too so u watch yours too
im just making a point that putting a phone in a fridge is a dumb idea and all its doing is tripping the indicators
and voiding any waranty anyone had of getting their g4 fixxed
come on.
this is stupid to be arguing over wtfs and other words
i hold a completly valid point thats its a stupid idea
just because someone says it works and it may have temp worked lets jump a bridge ive read about people claiming lg says their craps been wet and the same people put their crap in a fridge
both of you ive been in this game a long time 100 post apiece for u guys memebers since 2011
so not much input from either of u ove what like 6 years. at least im trying to help people.
risking my device for testing porposes to help the community. says ure on a nexus on tapatalk. do u even own a g4?
im just trying to keep people from making stupid desicions based off others "findings"
Snooping around my profile now lol. Do i own one? Well i bought two back in November 15, so i own two actually, (one of which died a couple of weeks ago), and think that qualifies me to follow this thread, if that's ok with you?
By the way the "c" word is "cussing" also [emoji14]
Sent from my Nexus 6P using Tapatalk
tharweb said:
Snooping around my profile now lol. Do i own one? Well i bought two back in November 15, so i own two actually, (one of which died a couple of weeks ago), and think that qualifies me to follow this thread, if that's ok with you?
By the way the "c" word is "cussing" also [emoji14]
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yea u kinda got one. Lol. Hate it for you that one of the ure g4s died. Just please dont put it in the fridge before sending it in. Lol.
Well having 2 i guess doe qualify u into the threads.
What's the matter? My G4 suddenly got the bootloop problem, and I had no backup of some data.
I did put it in the freezer and luckily managed to complete a full backup.
It worked and didn't harm my device... send it for repair, got the mobo replaced.
This thread should be deleted, I don't get the point of creating a topic to complain about that, seriously.
bel57 said:
What's the matter? My G4 suddenly got the bootloop problem, and I had no backup of some data.
I did put it in the freezer and luckily managed to complete a full backup.
It worked and didn't harm my device... send it for repair, got the mobo replaced.
This thread should be deleted, I don't get the point of creating a topic to complain about that, seriously.
Click to expand...
Click to collapse
its just a point just cause ures made it ok
we all know that moisture can form as the device heats up in a cool place its common science
aside from if it works or not its dangerous and can lead to tripping the moisture indicators
mods please delete my thread here its just causing issues and arguments.
no one sees my point and i see no need to keep this thread alive either
No comment
I left it 30 minutes max in the freezer. It's no problem.
Putting a device in the fridge is not the same as throwing it in water.
I can't imagine LCI being triggered by fresh air. Smh.