Develop Bugs

Just got the GS3, first Android phone

I just got the Galaxy S3 I747M on Friday, from Rogers.
I feel like I am seeing colour for the first time, after being shackled to an iPhone 4 and the restraints of the Apple "universe".
I was a heavy jailbreaker/customizer and want to continue on this phone. But I have no idea where to start. So many custom ROMs and what looks like 3-4 things I have to do/install before actually installing a ROM. Is there a comprehensive explanation of what needs to be done and why?
Also, any general tips/must have apps for Android? I find this phone's battery life is not stellar, but have read on here that there is a ROM that seems to help with that.

linuxbman said:
I just got the Galaxy S3 I747M on Friday, from Rogers.
I feel like I am seeing colour for the first time, after being shackled to an iPhone 4 and the restraints of the Apple "universe".
I was a heavy jailbreaker/customizer and want to continue on this phone. But I have no idea where to start. So many custom ROMs and what looks like 3-4 things I have to do/install before actually installing a ROM. Is there a comprehensive explanation of what needs to be done and why?
Also, any general tips/must have apps for Android? I find this phone's battery life is not stellar, but have read on here that there is a ROM that seems to help with that.
Click to expand...
Click to collapse
welcome...
i have only been a heavy Android user since December, but there are some good reference guides in the sticky under this form and under the old North American S3 Forum...(http://forum.xda-developers.com/forumdisplay.php?f=1667)
make sure u follow the rooting process that does not trip the flash counter... if u do, then no worries cause there is an app (Triangle Away) that works to reset the flash counter..
you can always go back to Unrooted stock by downloading the stock ROM's
I am on Rogers as well and i am using the KyanROM 1.2.. and it;s pretty solid.. i get pretty good battery life and using Faux123's Kernel along with it to over clock it makes it even sweeter..
there is a sticky found here (http://forum.xda-developers.com/showthread.php?t=1728824) that gives u a pretty good guide on what to do from start to Rooted happiness...
have fun!

I haven't had any problems with battery life and I just rooted mine 1 hour ago I've had it since Thursday. There is a sticky that gives you detailed step by step root instructions.
Sent from my SAMSUNG-SGH-I747 using xda premium

linuxbman said:
I just got the Galaxy S3 I747M on Friday, from Rogers.
I feel like I am seeing colour for the first time, after being shackled to an iPhone 4 and the restraints of the Apple "universe".
I was a heavy jailbreaker/customizer and want to continue on this phone. But I have no idea where to start. So many custom ROMs and what looks like 3-4 things I have to do/install before actually installing a ROM. Is there a comprehensive explanation of what needs to be done and why?
Also, any general tips/must have apps for Android? I find this phone's battery life is not stellar, but have read on here that there is a ROM that seems to help with that.
Click to expand...
Click to collapse
I was the same as you. I got one x on launch day like 3 months ago and bricked it. It was my fault. Just research !!! Its very hard to brick an iPhone its very easy to brick an android. I'm on the new AOKP with ktoon kernel this phone is just flat out bada$$ just take your time and research
Sent from my SGH-I747 using xda premium

Research research research. Make sure to research how to unbrick the phone especially so you won't be panicked if you manage to softbrick your device.
Sent from my SAMSUNG-SGH-I747 using xda premium

Out with the old and in with the new...
Coming from iOS (after 6+ years) and loving all the homebrew stuff in the Android universe.
Got a Garnet Red GS3 on Friday, rooted and installed CM9 Preview on Saturday

linuxbman said:
I just got the Galaxy S3 I747M on Friday, from Rogers.
I feel like I am seeing colour for the first time, after being shackled to an iPhone 4 and the restraints of the Apple "universe".
I was a heavy jailbreaker/customizer and want to continue on this phone. But I have no idea where to start. So many custom ROMs and what looks like 3-4 things I have to do/install before actually installing a ROM. Is there a comprehensive explanation of what needs to be done and why?
Also, any general tips/must have apps for Android? I find this phone's battery life is not stellar, but have read on here that there is a ROM that seems to help with that.
Click to expand...
Click to collapse
The best thing about Android is that you dont have to root or ROM to do everything that you needed to Jailbreak your iPhone to do. Does that make sense?
I have only rooted my S3 so far to get the ability to apply a few tweaks but I dont plan on ROMing it anytime soon. Runs like a champ.

I am also a new user to the android world, and though my experience I got to say do your research and back up everything.
http://forum.xda-developers.com/showthread.php?t=1739426
Was a great guide for me to flash a rooted stock rom, very simple process just need to be careful, and how to install clockworkmod recovery.
As for apps, i love my titanium backup and is worth every penny especially if you start to try different roms. One thing is if your move across different rom types most of the time you will need to wipe your data, probably the safest thing to do anyways based on my research. I got stuck in the boot screen and only way for me at that time to fix was to wipe my data.

Strange amount of Bricked devices anyone else notice

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

Warning: Non-noobs get it wrong too - bricked SGS3

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

[Q][HELP]S3 Hard Bricked after Flashing Illusions

I FIXED IT
Here's the Link to my Guide.
http://forum.xda-developers.com/showthread.php?t=2369125
Okay, So here's what I did.
I flashed the latest Illusions ROM for my S3 and the Slim AIO 7 for 4.2.2 (since Illusions is based out of SLIM, AOKP, PA, CM, ETC). Then TWRP 2.6.0.0 said that SuperSu wasn't installed (what the heck?!?!?) and it prompted me to install su so I was like "What the heck, why not" so I swiped for yes. Then the screen went black for a good 20 minutes. I got worried, did a battery pull and tried to but straight to recovery... no bueno. Same for booting to dl mode. I plugged my phone in to my computer without the battery and the red LED comes on for 10 seconds and then it dies. It prompted windows to install the QHUSB_DL driver and it failed. WHAT THE HECK JUST HAPPENED?!?
Is there anything I can do to unbrick it?
Do I have to JTAG/JIG or what? If so, can anyone direct me to it? (Last resort)
I'm on the MD4 bootloader and modem.
I really need to get this phone fixed before I go to basic on the 23rd of July.
Other info: Yes, I already went to the local Sprint store (not to get a replacement. That would be irresponsible of me considering my S3 is built by me from the MoBo on up) to get help on flashing it back to stock.

Jtag is the only way and you need to send it to someone who does that.
Sent from the future via Tapatalk 4

deBricker said:
Okay, So here's what I did.
I flashed the latest Illusions ROM for my S3 and the Slim AIO 7 for 4.2.2 (since Illusions is based out of SLIM, AOKP, PA, CM, ETC). Then TWRP 2.6.0.0 said that SuperSu wasn't installed (what the heck?!?!?) and it prompted me to install su so I was like "What the heck, why not" so I swiped for yes. Then the screen went black for a good 20 minutes. I got worried, did a battery pull and tried to but straight to recovery... no bueno. Same for booting to dl mode. I plugged my phone in to my computer without the battery and the red LED comes on for 10 seconds and then it dies. It prompted windows to install the QHUSB_DL driver and it failed. WHAT THE HECK JUST HAPPENED?!?
Is there anything I can do to unbrick it?
Do I have to JTAG/JIG or what? If so, can anyone direct me to it? (Last resort)
I'm on the MD4 bootloader and modem.
I really need to get this phone fixed before I go to basic on the 23rd of July.
Other info: Yes, I already went to the local Sprint store (not to get a replacement. That would be irresponsible of me considering my S3 is built by me from the MoBo on up) to get help on flashing it back to stock.
Click to expand...
Click to collapse
I take it that post I linked to in my thread didnt work then?
And FYI
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/

What was the name of the file for Illusion ROM?
Sent from my SPH-L710 using xda app-developers app

Notorious said:
What was the name of the file for Illusion ROM?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
FML, I made a noob mistake. Flashed a i9300 Illusion Rom. But I got it from the link on the page. It's Illusion i9300 4.2.2 07132013

billard412 said:
I take it that post I linked to in my thread didnt work then?
And FYI
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Click to expand...
Click to collapse
No. Looks like I'm going back to my ogEvo. Won't be able to use that service until after the Navy is done with me. FML. I still can't believe I made a noob mistake. -_____- I have never bricked a phone and this is ironic because i usually de-brick phones... not brick 'em.

Have you looked at this thread
[HOW TO] Unbrick your Sprint phone from flashing an International gsm boot imag

jdelano said:
Have you looked at this thread
[HOW TO] Unbrick your Sprint phone from flashing an International gsm boot imag
Click to expand...
Click to collapse
I JUST FIXED IT! LOL. I'm in the middle of Barnes and noble and I just fixed it. I'll put down directions for a HOW TO for my method, but it involves having Linux.
HARD BRICK FIX W/O THE JTAG!
and I'll have to give credit. I finally figured out how to dd that file that was posted by (I don't have his username atm) but yeah! I got it to work. His method needs a little more instruction.

Just booted to DL mode

Yeah, if I may, please don't make a guide thread for that. It will only encourage people to flash international roms.
Sent from my S3 on Sense 5 (you jelly?)

glad to hear you got it working.

CNexus said:
Yeah, if I may, please don't make a guide thread for that. It will only encourage people to flash international roms.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
Yes, well, some people would like the convenience of not having to send their phone off and spending 60 dollars to get it fixed. And there are many ways to hard brick an S3 and I think that this would be a convenient way of fixing their phone.
Mine was a legit mistake. I'm a veteran flasher of ROMs and everyone does slip up.

deBricker said:
Yes, well, some people would like the convenience of not having to send their phone off and spending 60 dollars to get it fixed. And there are many ways to hard brick an S3 and I think that this would be a convenient way of fixing their phone.
Mine was a legit mistake. I'm a veteran flasher of ROMs and everyone does slip up.
Click to expand...
Click to collapse
Well if you do something like that, you should own up to it and pay the $60 bucks to get it fixed. International roms don't magically wind up on your flashing queue in recovery.
I obviously can't stop you from posting anything, but just keep that in mind.
Good day.

CNexus said:
Well if you do something like that, you should own up to it and pay the $60 bucks to get it fixed. International roms don't magically wind up on your flashing queue in recovery.
I obviously can't stop you from posting anything, but just keep that in mind.
Good day.
Click to expand...
Click to collapse
Yes, well. I can't exactly do that since I'm in the Navy and I'm going to be gone for the next two months. I prefer to find a method BEFORE paying the 60 dollars to unbrick. Dude, this to help everyone. YES I MADE A MISTAKE. We all do. I understand its frustrating. Even I get frustrated. But why should I pay 60 dollars to have someone else fix my phone when I can fix it myself? I'm not a noob at flashing.

deBricker said:
Yes, well. I can't exactly do that since I'm in the Navy and I'm going to be gone for the next two months. I prefer to find a method BEFORE paying the 60 dollars to unbrick. Dude, this to help everyone. YES I MADE A MISTAKE. We all do. I understand its frustrating. Even I get frustrated. But why should I pay 60 dollars to have someone else fix my phone when I can fix it myself? I'm not a noob at flashing.
Click to expand...
Click to collapse
It's a fine line we walk... We here at XDA want to be helpful to "noobs," but we also want to express the importance of reading and critical thinking before acting.
This argument came up a month or two ago. There's an easy way to make the ROMs check the phone model prior to flashing. This would be a great way to prevent hard-bricks, as the installation will abort on the wrong device. The issue that arises is two-fold:
1) There are many Devs and not all will implement this device check.
2) People will start getting lazy with their flashing, as it seems "idiot proof."
We are actually seeing this with the newest CM10.1 releases. Despite it being clearly spelled out in installation threads (if they read the last 3-4 pages of the thread), a lot of people are trying to flash them without updating their bootloader. They then get the infamous system 7 error. I was answering threads one after the next with people asking the exact same question about the system 7 error. A simple 5-minute perusal of the forums (or even just the CM thread) would've yielded the results, but people don't want to put in the "hard work."
In the case of hard-bricks and your guide, I don't fully agree with CNexus (it happens from time-to-time, but he's a quality guy and dev). If it works a good percentage of the time, I think it's a valuable tool that can help a lot of people. That being said, one of the "good" things about a hard-brick is that people generally learn their lesson after one. I've seen people here on XDA that hard-bricked their device (due to carelessness), had to get it JTAG-ed, then came back to become advocates for reading the posts/directions thoroughly. It's amazing how $60 and losing your phone for a week will make people a lot more sober about flashing a Rom.
I don't doubt for a minute that having an "easy" fix for hard-bricks will reduce the impact of this lesson.
That being said, I also believe that having this guide is a good thing. My recommendation would be to rewrite the beginning of the guide to include a strong disclaimer about the dangers of flashing a Rom not meant for your device. I understand that you're trying to take the approach of "hey, we are all noobs at times, it's not that big of a deal," but I think it'll reinforce the lazy mentality of a good number of flashers.
Just my two cents. I'm glad you were able to fix your phone and to find a way to boot into download mode from the SD card so you can rewrite the bootloader partition from Odin.

Why did I get another Android phone?

I was so excited to get a different phone. I had been contending with the insufferable Galaxy Note 2 for 9 months. I really believed that getting the LG Optimus G Pro would be great.
Now I come to find out that there is this locked bootloader? yes before you even start typing: I already know about Freegee. I put it on my phone, it did its work. I have CWM on my phone. I cannot install a different rom. It aborts every time.
And nobody here can help. Its not like you don't see my posts. You see them. You just see them and decide to go on to something more interesting figuring that someone else will help the poor guy.
Hey guess what. I took programming in college. Only one course in VB but I did take it. And I've put up several websites back in the day. ("back in the day is a United States colloquialism")
My point is, even though I have a bit of experience with computers (linux distros, html, visual basic) I still can't figure out the quagmire that is Android.
Once the iPhone 6 comes out, I really have no reason to stick with Android anymore. I mean, if rooting and rom-ing the phone is more boringly laborious than jailbreaking, then what is the point of Android?
For example, lets say I do clear the hurdle and then flash a rom so I can get decent sound? THEN my wifi won't work. Or Some other crucial functionality will be fubar-ed. Okay okay... you say you have a fix for that? Well when its all said and done, the time/energy costs just aren't worth it, now is it?

0 #!*! Given ?

That's interesting because I never took any classes and have never had a problem rooting or doing Roms on any android phone. Sorry your experience has been bad but my questions have always been answered by somebody in the related thread. I would try asking again in the ROM's thread to see what is happening.
Sent from my LG-E980 using XDA Premium 4 mobile app

G pro is the note 2 killer...... Just follow instructions of any op to the T and you should be fine.... It's simple lol
2SHAYNEZ

I agree. I don't post often but I really do hate Apple. Android kicks Apple's you know what many times over. Talk about being locked down.... If I've ever had a problem with a Rom someone has always helped me figure it out. Sorry about your problems though.
sent from my lgog pro. I just had to go bigger.

@Perry2547,
If CWM doesn't work then try TWRP, even i had problems with CWM.either install it from freegee or install this
copy this to sd card and then flash it in CWM and reboot.

I believe the OP just wanted to start a thread...
So you all may ignore him

Thanks @sukesh.
I tried the twrp you linked to and now my phone will let me flash.
Unfortunately, Camera has stopped.

Close thread please.
2SHAYNEZ

I don't even remember how I rooted this phone... I know I found a thread that had comprehensive instructions, links, etc and believe it was as simple as downloading/extracting an executable file on my PC and plugging the phone into USB at the right moment. I've flashed CM, stock 4.4, Slim and always find my way back to stock 4.1.2, modded to my liking. If you can't flash something in a custom recovery, it's likely your phone is protecting you from failure to completely read/follow a prior mod or a prerequisite to the ROM/Mod you wish to flash.
Sent from my LG E980 via Tapatalk Pro (and stupid-fast LTE)

But seriously y'all, I'm just glad I have another two hours if battery life left. That means I will vhave to recharge this phone only 3 more times today.
Unfortunately, Camera has stopped.

I too just got new lg ogp phone. Been trying to customize it to my liking for the past 3 days and night. All I can say about android is it is not for everybody. Sure, you can use it as it is when you first get it as a stock device, and it will work as advertise. But there is a reason that you try modifing it regardless of breaking the manufacturer's warranty (yes, once you start rooting it, you violate the agreement.) You have personality of the kind that thinks you can fix anything by yourself. Nothing wrong with that, I'm in same personality group too, many Android owners are. After all, what is the point if you can't modify the phone to your liking? Might as well get an Iphone right? Sadly though, it seems the new android trend is just heading the way of iphone, where users have to be protected from harming themselves. I noticed all the difficulties when I tried to root this LG phone, as compared to the phone I had two years ago. But android users are a persistent lot, more securities mean inventing more ways to break them. If you have problem installing ROM, try cm11 nightly build, it works for me. Post the specific problems and situations. We should be able to help each other. After all, android owners are together in a special community where we can relate to each other because of ideas we have for our phones. My advice to you is make sure you have the newest recovery and you are properly rooted. I can't use the script method where you run a msdos batch file. Since atnt suppose locked the boot.img file or something. Had to use a program called root master.
Sent from my LG-E980 using XDA Premium 4 mobile app

Nobody gives a damn, get life!

Antigen said:
Nobody gives a damn, get life!
Click to expand...
Click to collapse
Haha
2SHAYNEZ

hawkwind212 said:
I too just got new lg ogp phone. Been trying to customize it to my liking for the past 3 days and night. All I can say about android is it is not for everybody. Sure, you can use it as it is when you first get it as a stock device, and it will work as advertise. But there is a reason that you try modifing it regardless of breaking the manufacturer's warranty (yes, once you start rooting it, you violate the agreement.) You have personality of the kind that thinks you can fix anything by yourself. Nothing wrong with that, I'm in same personality group too, many Android owners are. After all, what is the point if you can't modify the phone to your liking? Might as well get an Iphone right? Sadly though, it seems the new android trend is just heading the way of iphone, where users have to be protected from harming themselves. I noticed all the difficulties when I tried to root this LG phone, as compared to the phone I had two years ago. But android users are a persistent lot, more securities mean inventing more ways to break them. If you have problem installing ROM, try cm11 nightly build, it works for me. Post the specific problems and situations. We should be able to help each other. After all, android owners are together in a special community where we can relate to each other because of ideas we have for our phones. My advice to you is make sure you have the newest recovery and you are properly rooted. I can't use the script method where you run a msdos batch file. Since atnt suppose locked the boot.img file or something. Had to use a program called root master.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly.
If android is going to be locked down, what is the point? With iPhone bringing in 3rd party keyboards and phablet size phones, might as well go with them instead of utilitarian design devices made by dictator led countries where creativity is frowned upon.
Unfortunately, Camera has stopped.

Perry2547 said:
Exactly.
If android is going to be locked down, what is the point? With iPhone bringing in 3rd party keyboards and phablet size phones, might as well go with them instead of utilitarian design devices made by dictator led countries where creativity is frowned upon.
Unfortunately, Camera has stopped.
Click to expand...
Click to collapse
Oh lawdy... Then go to iPhone buddy .. Lol see ya
2SHAYNEZ

But Apple has been implicated in planned obsolescence as well.
Does that matter to you?
To me, it makes me a bit upset that I could work on my vehicle twenty years ago, but now it's not possible. Planned obsolescence.
Make everything sweepstakes m disposable. Lock it down too. Keep every one buying the upgrades.
Unfortunately, Camera has stopped.

Are you still having problem installing the ROM? You have never tell us what kind of problems you ran into specifically. You just ventted your frustration here, nobody wants to hear that. If you want people to help, describe the issue. Go to this site and download the program vroot.
http://www.mobilepoint.us/2013/10/android-root-master-one-click-vroot.html#.U9XRXYfwJGo
The program is in Chinese, so you may want to watch youtube videos on the master root program first. Do a factory reset, clean wipe, run master root program, and hopefully you should be able to install the recovery. Once the recovery is properly installed, you can install the custom rom. Since there aren't many, I suggest you try cyanogenmod.
Sent from my LG-E980 using XDA Premium 4 mobile app

hawkwind212 said:
Are you still having problem installing the ROM? You have never tell us what kind of problems you ran into specifically. You just ventted your frustration here, nobody wants to hear that. If you want people to help, describe the issue. Go to this site and download the program vroot.
http://www.mobilepoint.us/2013/10/android-root-master-one-click-vroot.html#.U9XRXYfwJGo
The program is in Chinese, so you may want to watch youtube videos on the master root program first. Do a factory reset, clean wipe, run master root program, and hopefully you should be able to install the recovery. Once the recovery is properly installed, you can install the custom rom. Since there aren't many, I suggest you try cyanogenmod.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got a ROM to install. I indicated so in the thread. It was the E988 rom on the E980 thread.
I do a lot of whining and complaining but its for the best.
I hope that the complaining I did about Samsung's crappy products has saved a few people from buying...that is the only way that company will learn their lesson. Why pay $800 for a device only to get screen burn in.
But I never ever never ever BRICKED my Note 2.
I've bricked this OGP more times than I can count.
We should have the options to remove the locked boot loader. I would gladly sign an agreement acknowledging the risks.
We're going backwards. We're not making progress.
Same things is happening in desktop/laptop computers. I had to do something unusual to remove the UEFI on a Windows machine I bought last year just to install Lubuntu.
Speaking of Lubuntu, I had an ASUS Netbook with Windows 7 and an Atom processor. Needless to say, it ran slow. So I installed Lubuntu. Then , wow, the device ran so fast and smooth, and the already good battery life got three times better.
Why can't we have an option like that for our smartphones? I want to run the equivalent of Lubuntu on my OGP.
And another thing: Why are some custom roms dimming the display? Is it to make it appear as if the rom is giving better battery life?
Peace out bro.. but yeah, I'm not stopping my rants. If you don't like what I've got to say, simply don't read it.

This phone is not much more difficult to root than any Samsung phone I used. Also why didn't you do research before buying the phone? It was stated clearly that the boot loader was locked. However since day one of purchase I was able to follow a thread and have my phone rooted in ten minutes. It is really not that hard. Now there are a bunch of one click roots. This phone installs custom Roms every time with ease for me. I am no expert but I can read instructions. If you follow them, 99% of the time things will work. I love android for the fact that I have options. I am running a rooted stock ROM now but I love knowing that in ten minutes time I can have a new ROM flashed. This community has been so helpful and responsive.
Sent from my LG-E980 using XDA Premium 4 mobile app