Develop Bugs

Rooting and sprint

After talking with some sprint tech's for a while about issues not only in my area but with the phone in general I found out that they can very very easily find out if you are rooted with a click of a button. I noticed that every single rom that I have ever used always says the name of the rom in the build number area of phone info menu. That is an easy way for sprint to see that you are rooted. Any way to change that or can't rom devs just not edit that part with the name of their rom? I know what rom I'm using, why does it need to be there?

Rom developers do that so they can ID the rom for a reason; and if you're dumb enough to bring it in rooted and the check to see your system, of course they are going to know, a five year old could tell the difference. Either put on a stock rooted rom, change the build prop, or unroot period.

teh roxxorz said:
Rom developers do that so they can ID the rom for a reason; and if you're dumb enough to bring it in rooted and the check to see your system, of course they are going to know, a five year old could tell the difference. Either put on a stock rooted rom, change the build prop, or unroot period.
Click to expand...
Click to collapse
+1... even if that was left totally stock named, and the rom looked like a stock sprint rom, they could still tell you were rooted... all they would have to do is look on your sd card, or look for apps that only work if your rooted such as superuser, rootuninstaller or any file explorer... take the extra minute and unroot to take your phone in.

dbenney said:
+1... even if that was left totally stock named, and the rom looked like a stock sprint rom, they could still tell you were rooted... all they would have to do is look on your sd card, or look for apps that only work if your rooted such as superuser, rootuninstaller or any file explorer... take the extra minute and unroot to take your phone in.
Click to expand...
Click to collapse
It's usually a good idea to
1. S-On the phone
2. Flash an unrooted stock rom
3. switch SD cards
4. Uninstall or do not install any apps requiring root permissions
5. Lock your market (with an app protector)
before taking it into any Sprint Store for service.

teh roxxorz said:
Rom developers do that so they can ID the rom for a reason; and if you're dumb enough to bring it in rooted and the check to see your system, of course they are going to know, a five year old could tell the difference. Either put on a stock rooted rom, change the build prop, or unroot period.
Click to expand...
Click to collapse
I'm not the dumb one here. Assuming always makes an ass out of someone. And it's not me.
The rom dev needs to ID them for what reason? I understand needing to identify the rom from others but I'm not seeing a reason that they need to ID it in this way.
dbenney said:
+1... even if that was left totally stock named, and the rom looked like a stock sprint rom, they could still tell you were rooted... all they would have to do is look on your sd card, or look for apps that only work if your rooted such as superuser, rootuninstaller or any file explorer... take the extra minute and unroot to take your phone in.
Click to expand...
Click to collapse
-1... Again, like the other guy, you are assuming. Take the extra minute and think before you post, ask if I walked into a store first.
shortydoggg said:
It's usually a good idea to
1. S-On the phone
2. Flash an unrooted stock rom
3. switch SD cards
4. Uninstall or do not install any apps requiring root permissions
5. Lock your market (with an app protector)
before taking it into any Sprint Store for service.
Click to expand...
Click to collapse
Must be contagious around here. If I was having problems with the phone in general I would first dump the rom and go back to stock to see if it was a issue with the rom or the phone. Common sense.
It was a phone call to sprint about network issues. About towers that were not working correctly and the tech I talked to at the Kansas center over all network issues could see **ALL** history of the phones ROM. Didn't matter what rom I curently had on the phone. It gets logged into the system. PERIOD. He told me it was rooted and told me the name of the rom installed and what day it was installed. I was kind of blown away.
I didn't walk into a store and say here's my rooted phone, fix it. Never heard of anyone unrooting a phone to call in about network issues. EVER! All I'm asking is is there a simple way to change the info that the Sprint system would see when it gathers the info about the phone to avoid detection of being rooted and a non stock rom installed. That's all. I understand you have life issues and feel angry at the world and need to make an ass out of yourself but if you can not just answer simply then just don't answer.

eskomo said:
All I'm asking is is there a simple way to change the info that the Sprint system would see when it gathers the info about the phone to avoid detection of being rooted and a non stock rom installed. That's all.
Click to expand...
Click to collapse
No.

Thats the most insane thing ive ever heard. IM almost 100% sure that sprint can't read your ROM details. In fact in order for them to even trouble shoot over the air,they would need your permission to link to your phone using the main network. So dude im kinda sure that your back pedalling a little here after some responses. For future reference try wording your ?'s so they represent your intentions or future actions. Dont get all boohoo on us when you receive a little criticism. The way you are posting gives the impression that you blindly walked into a sprint store without unrooting. Next time just tell us what needs to be done ask for some help and someone will def hook you up right. :beer:
Sent from my A500 using xda premium

PyreKing said:
Thats the most insane thing ive ever heard. IM almost 100% sure that sprint can't read your ROM details. In fact in order for them to even trouble shoot over the air,they would need your permission to link to your phone using the main network. So dude im kinda sure that your back pedalling a little here after some responses. For future reference try wording your ?'s so they represent your intentions or future actions. Dont get all boohoo on us when you receive a little criticism. The way you are posting gives the impression that you blindly walked into a sprint store without unrooting. Next time just tell us what needs to be done ask for some help and someone will def hook you up right. :beer:
Sent from my A500 using xda premium
Click to expand...
Click to collapse
It may sound insane to you but that doesn't change the fact that its true. I know what the guy said on the phone. He said exactly what rom I had installed. You're kind of sure? So you have no idea what you're talking about you so you assume something? Lol The way that you are posting indicates you just want to start something with someone for no reason. Stop trolling and move on to the next thread.
They don't need any permission to link to your phone. They own the rights to access your phone by way of the contract you have with them. They have every right to check the connection between the towers and the phone. By doing that info gets logged to the system about the device connected.
I talked to tech's in the Kansas center that deals with network issues. These are not standard lvl 1 tech's. This guy called me back days later and dealt with me about the towers in my area that were under performing. I gave him my signal strength at multiple locations and he would (on his end) zoom into on each location and look at what was going on at each tower. Explaining to me that the tower at my work was 1.2 miles away and at that distance I should have full signal and even rolled out a van to not only check the strength in the parking lot of my office but various spots in that towers coverage. Determining that the tower had very low strength and needed to be addressed. Also figuring out that my phone was having signal issues near my home which was in range of 5 towers. I'm not back pedaling at all. I know what I'm talking about and i have no reason to ask a question with false pretense to get an answer that would not be pertaining to my actual issue. But since you like to assume everything just assume I didn't respond to your thread and troll some where else.

Wow trolling huh I simply stated what was present. In no way was I even been harsh. In fact I was referencing the way you worded your post that was causing the reactions you recieved. Like I said you had to have given them permission to link to your phone.....So that being said your gonna have a very hard time on xda when you bash people for heading you in the right direction. Good luck with being like that...
Sent from my A500 using xda premium

I was under the impression that sprint serviced rooted phones, is this incorrect?
Sent from my PC36100 using XDA

Yes, most will. Unless you get some ahole (which has never happened to me). I've had hardware pieces replaced countless times in the last 18mo., and have NEVER unrooted. I do think the key, though is it's always been for hardware issues (primarily screens and cameras).
Hell, last time I took it in, I had ICS on it. Techs thought it was pretty cool.
Sent from my PC36100 using xda premium

eskomo said:
I'm not the dumb one here. Assuming always makes an ass out of someone. And it's not me.
The rom dev needs to ID them for what reason? I understand needing to identify the rom from others but I'm not seeing a reason that they need to ID it in this way.
-1... Again, like the other guy, you are assuming. Take the extra minute and think before you post, ask if I walked into a store first.
Must be contagious around here. If I was having problems with the phone in general I would first dump the rom and go back to stock to see if it was a issue with the rom or the phone. Common sense.
It was a phone call to sprint about network issues. About towers that were not working correctly and the tech I talked to at the Kansas center over all network issues could see **ALL** history of the phones ROM. Didn't matter what rom I curently had on the phone. It gets logged into the system. PERIOD. He told me it was rooted and told me the name of the rom installed and what day it was installed. I was kind of blown away.
I didn't walk into a store and say here's my rooted phone, fix it. Never heard of anyone unrooting a phone to call in about network issues. EVER! All I'm asking is is there a simple way to change the info that the Sprint system would see when it gathers the info about the phone to avoid detection of being rooted and a non stock rom installed. That's all. I understand you have life issues and feel angry at the world and need to make an ass out of yourself but if you can not just answer simply then just don't answer.
Click to expand...
Click to collapse
why dont you quit being an ass and take the advice given to you... and yes you do appear to be the idiot here. everyone is just giving you the reason, if you want the real reason, ask a developer why. If you are that worried about it maybe you shouldnt be rooting. We try to be helpful here and look at what happens. If you dont like it here JUST LEAVE and take your idiotic comments/questions somewhere else. I am sure you will fit in on some of the other forums much better. And I always wondered why people flamed and bashed SHESH! I now know why. You try to help someone out with suggestions and answers and they get an attitude... to all those people i say F**K OFF!

dbenney said:
why dont you quit being an ass and take the advice given to you... and yes you do appear to be the idiot here. everyone is just giving you the reason, if you want the real reason, ask a developer why. And go ahead and take your phone in without removing all traces of an unroot. We try to be helpful here and look at what happens. If you dont like it here JUST LEAVE and take your idiotic comments/questions somewhere else. I am sure you will fit in on some of the other forums much better. And I always wondered why people flamed and bashed SHESH! I now know why. You try to help someone out with suggestions and answers and they get an attitude... to all those people i say F**K OFF!
Click to expand...
Click to collapse
Did you read the thread at all? You're the idiot. Only one person answered the question, Shortydoggg. Everyone else assumed I took it into a store and didn't answer anything. As stated above, you do not need to remove root. Don't be a troll. You need to get out into the real world and leave your moms basement bud.
/ignore

PyreKing said:
Wow trolling huh I simply stated what was present. In no way was I even been harsh. In fact I was referencing the way you worded your post that was causing the reactions you recieved. Like I said you had to have given them permission to link to your phone.....So that being said your gonna have a very hard time on xda when you bash people for heading you in the right direction. Good luck with being like that...
Sent from my A500 using xda premium
Click to expand...
Click to collapse
I'm not sure I gave permission. I was speaking to the guy on the phone and he was looking into different things and asked if i had updated to the most recent OTA update. Then proceeded to tell me it looked like I was rooted and had a modded rom. That was it, he didn't ask permission to access my phone.
You said I was back pedaling and that i was boohooing. Umm ya trolling! Being harsh whatever you want to call it. I didnt come after you, you came after me.

eskomo said:
Did you read the thread at all? You're the idiot. Only one person answered the question, Shortydoggg. Everyone else assumed I took it into a store and didn't answer anything. As stated above, you do not need to remove root. Don't be a troll. You need to get out into the real world and leave your moms basement bud.
/ignore
Click to expand...
Click to collapse
The point i was trying to make is, what does it matter what it says? if you dont like htey way devs make their roms, maybe you should make your own. Gotta love your maturity level here. You will not get the type of assistance you require here with this type of bashing and attitude.

Nope it needs to be unrooted and s off. I kinda agree with the other guy here mate. Your
post does suggest what he says it does. And flaming people for pointing things out like is f'd up. You need to-be able to handle constructive criticism to be on xda. Peeps here have heard it all,and don't take kindly to noobs acting in such a manner trust me on this one. Restrict yourself to just simply stating what and why, and you'll always be right. Cheers mate.
Sent from my PC36100 using xda premium

Yeah my girl works for Verizon cs and she said there is no way that she can bring up someone's phone and tell if they are rooted or not.
Sent from my Rezound running stock/leaked ICS.

Wow. I am astonished by the level of ungratefulness going around
thread closed before anyone gets hurt.

New To Android, but bricked my phone?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Hard Brick Sprint GS3

Okay, I have seen many post on hard brick and also seen the many suggestions. Tried all but it seems that I just have to bite the bullet and turn it in to either Sprint or Samsung. I loaded a international rootbox mod and hard bricked my phone. It recognize by my pc by the usb connection and assigning a com port. It dose not load the flash drives though. Odin dose not recognize the usb connection. I tried qubking777 methods(which seem to be used for only soft bricking), tried to put it every mode possible, and even removed the sd/battery then connect to usb. It gets a red led light for about a couple minutes but nothing in trying to flash via Odin. If anyone has anything new that I can try without jig/Jtag would be helpful. I have been claim to be a noobie at this from friend at work and know that the pc world is different from the smartphone world but some of the concepts are the same. That if you think the same way as I do. So please no crazy remarks that is any demeaning ways. I do have some experience with root and mods when I did this HTC EVO original.
Thanks

Its done the only way to fix is JTAG if you don't want to go through Samsung or sprint which would be insurance fraud anyway
Sent from my SPH-L710 using xda app-developers app

evo4gnoob said:
Its done the only way to fix is JTAG if you don't want to go through Samsung or sprint which would be insurance fraud anyway
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
To my knowledge, none of the Jtag methods worked on the G S III [currently].

teh roxxorz said:
To my knowledge, none of the Jtag methods worked on the G S III [currently].
Click to expand...
Click to collapse
I've seen people report that they work. Never tried it myself, but thats just my 2 cents
@OP............have you read the numerous stickies, questions, threads, posts about what to flash and what not to flash? kennyglass123 and numerous others have made sticky threads about how to get started, what to do and not do after you root
Cmon dude, even though they may have the same name doesnt mean that software-wise theyre the same
I have an EVO 4G and an EVO shift 4G, but i dont go flashing roms between the two just because theyre similar
When you're doing this kind of system level, you need to know what you're getting yourself into, in the end you couldve just asked in the thread if it works for the sprint s3 or <insert carrier here> s3, and you wouldve gotten a "no"

CNexus said:
I've seen people report that they work. Never tried it myself, but thats just my 2 cents
@OP............have you read the numerous stickies, questions, threads, posts about what to flash and what not to flash? kennyglass123 and numerous others have made sticky threads about how to get started, what to do and not do after you root
Cmon dude, even though they may have the same name doesnt mean that software-wise theyre the same
I have an EVO 4G and an EVO shift 4G, but i dont go flashing roms between the two just because theyre similar
When you're doing this kind of system level, you need to know what you're getting yourself into, in the end you couldve just asked in the thread if it works for the sprint s3 or <insert carrier here> s3, and you wouldve gotten a "no"
Click to expand...
Click to collapse
The mentioning of me doing things to the EVO and talking about the same thing was saying that I am reading and not jumping into stuff i do not know about when working with the S3. Yes they have different ways of rooting and flashing what not but the technology and concepts are the same. The only thing have jumped into over my head was that I grabbed the international load of rootbox mod because there was no clear indication what mod was what from their website. Once I loaded that and reboot, now I am a bricked. I am just trying to see if there anything that I haven't tried yet. It seems that I have indications that the phone has not gone to far and I can do something. Maybe something that works the with bootloader to get it to a point to clear and flash a restore..

The technology is not the same either
The international version is GSM while the sprint variant is cdma, the international version is quadcore while the sprint one is not
Software wise, the partitions line up, but incorrectly
The boot partition on the sprint variant lines up with the misc partition on the international, and a couple other partitions line up incorrectly as well

teh roxxorz said:
To my knowledge, none of the Jtag methods worked on the G S III [currently].
Click to expand...
Click to collapse
Mobiletechvideos.com are recommended by a lot of people
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
johnboy228 said:
The mentioning of me doing things to the EVO and talking about the same thing was saying that I am reading and not jumping into stuff i do not know about when working with the S3. Yes they have different ways of rooting and flashing what not but the technology and concepts are the same. The only thing have jumped into over my head was that I grabbed the international load of rootbox mod because there was no clear indication what mod was what from their website. Once I loaded that and reboot, now I am a bricked. I am just trying to see if there anything that I haven't tried yet. It seems that I have indications that the phone has not gone to far and I can do something. Maybe something that works the with bootloader to get it to a point to clear and flash a restore..
Click to expand...
Click to collapse
Phones completely done dude. You can't do anything to recover it without getting it jtagged. You have no boot loader the partition for the kernel on the international S3 is the partition where our boot loader is stored so when you flashed that international rom it wiped your boot loader and wiped other important partitions
Sent from my SPH-L710 using xda app-developers app

Lol. Another one which found the correct model after hard brick his phone.
Sorry but JTAG is your only option.
Sent from my SPH-L710

csmasn said:
Lol. Another one which found the correct model after hard brick his phone.
Sorry but JTAG is your only option.
Sent from my SPH-L710
Click to expand...
Click to collapse
Thank you for pointing this out. The OP also gets defensive when it's pointed out. He uses all the wrong stuff but when he breaks it he finds the right section to seek help. :banghead::banghead::banghead::banghead::banghead:
he claims he is reading and not jumping into things, I guess he skipped over the word INTERNATIONAL as opposed to the one on this section SPRINT.
OP and as you wrote "please no crazy remarks" this and the others are not crazy it's just amazing how you did not find the right section to begin with but had no problem finding it now that you messed it up?
Transmitted with a portable device using Xparent Blue Tapatalk 2

So you guys want defensively. You getting it. Believe it or not, technology is blending together. I have background in IT field to see the history of it all for almost the last 20 yrs. Yes different manfactor and carriers define these phones but that is the only thing that seperate these from computer is the phone portion. Yes I have been following this fourm for a while which lead me to the rootbox mod page in the first place and known where to paste certain threads. I don't even know why I thought there was some very intelligent people on here that are nothing but very disrespecting when someone is looking for just the slightest information. If any one wants a extra check by there chuck wagon meter, please point me in the right direction. Can't believe that I posted any thing here after seeing this stuff in other post. THANKS EVERYONE!

Johnboy you have to understand we get three or four of these every week from people who do not read and just flash away. They find a rom on the international thread and flash it. Voilà 600 dollar paperweight. Then they do fraud and claim hey don't know why their device doesn't work. Who pays all of us with the continued rise in cost on our device.
It's funny though how every single one of them find their way to the right place and forum when they mess-up their phone. Amazingly!
This is the best place and forum to find the right information about your device. Swallow up a little pride own up to that you made a bone head move, and move on and stick around. You will find lots of support.
If not 'goodnight Johnboy'
Transmitted with a portable device using Xparent Blue Tapatalk 2

edfunkycold said:
Johnboy you have to understand we get three or four of these every week from people who do not read and just flash away. They find a rom on the international thread and flash it. Voilà 600 dollar paperweight. Then they do fraud and claim hey don't know why their device doesn't work. Who pays all of us with the continued rise in cost on our device.
It's funny though how every single one of them find their way to the right place and forum when they mess-up their phone. Amazingly!
This is the best place and forum to find the right information about your device. Swallow up a little pride own up to that you made a bone head move, and move on and stick around. You will find lots of support.
If not 'goodnight Johnboy'
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
This most be copy & pasted in every "flashed wrong/hard brick"
Sent from my SPH-L710

Like my mamma always said. If you don't have anything nice to say, don't say nothin! For some reason, i hear it in a southern accent. Even though I'm from upstate NY. These posts will never end. And insurance fraud claims will never end. Either way, the cost of our phones will rise.

ooonimrodooo said:
Like my mamma always said. If you don't have anything nice to say, don't say nothin! For some reason, i hear it in a southern accent. Even though I'm from upstate NY. These posts will never end. And insurance fraud claims will never end. Either way, the cost of our phones will rise.
Click to expand...
Click to collapse
Ya! Sounds like a $600 with a 5 years contract.
Sent from my SPH-L710

edfunkycold said:
Johnboy you have to understand we get three or four of these every week from people who do not read and just flash away. They find a rom on the international thread and flash it. Voilà 600 dollar paperweight. Then they do fraud and claim hey don't know why their device doesn't work. Who pays all of us with the continued rise in cost on our device.
It's funny though how every single one of them find their way to the right place and forum when they mess-up their phone. Amazingly!
This is the best place and forum to find the right information about your device. Swallow up a little pride own up to that you made a bone head move, and move on and stick around. You will find lots of support.
If not 'goodnight Johnboy'
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks edfunkycold, I do understand that this get a little redundant. This is not going to get me to swallow on a bone head move. It is determination to find a solution and help find a end this repeated cycle for everyone. Seeing other threads the phone dose respond to get a port assignment and is requesting for a driver install. So that is some of good sign. Everyone keep your eyes and ears open and I will be back with something. lol

Kudos to you Johnboy for powering on to find a solution. Good luck to you.
Friendly Neighborhood Moderator

johnboy228 said:
Thanks edfunkycold, I do understand that this get a little redundant. This is not going to get me to swallow on a bone head move. It is determination to find a solution and help find a end this repeated cycle for everyone. Seeing other threads the phone dose respond to get a port assignment and is requesting for a driver install. So that is some of good sign. Everyone keep your eyes and ears open and I will be back with something. lol
Click to expand...
Click to collapse
I'm going to save some time and update your status for you. As you'd see this imformation if you searched...
The drivers its requesting is the "QHSUSB_DLOAD" driver. Its basically a piece of hardware waiting for firmware to be loaded at a factory level. You will not talk to it with any software you currently own, hence the jtag requirement. Spent months hoping to do the same. You won't I promise. If I'm not mistaken even Samsung doesn't fix it in the state its in. I believe they send it to qualcomm, could be mistaken there tho so don't quote me on that. And props to edfunkycold for telling it like it is. Needs to be said and youll probably recieve an infraction now for not holding his hand and telling him it will be okay. Telling people the truth tends to get you in trouble on here.

I know that I am going to get plenty of flack for this but after a week in working this issue. I had given up and turn it in for new. Even after building a jig that did not do anything at all. I know the jig works because it sent the new phone into download mode immediately but it did not reset the flash counter. Sorry for not finding a fix or even had to turn my phone in. In my field it takes breaking something to make sure you never do it again. So now I know not do flash anything for the GS3 I9300 for the the Sprint model.

johnboy228 said:
Thanks edfunkycold, I do understand that this get a little redundant. This is not going to get me to swallow on a bone head move. It is determination to find a solution and help find a end this repeated cycle for everyone. Seeing other threads the phone dose respond to get a port assignment and is requesting for a driver install. So that is some of good sign. Everyone keep your eyes and ears open and I will be back with something. lol
Click to expand...
Click to collapse
Man, you are wasting your time, get the damn thing JTAG, period. If you are looking for a free fix, it AIN'T happening....the international rom hard bricked...period.
BTW, being an IT guy, you should have known to read before applying....you are more knowledgeable than some of the noobs. And by your negative responses, it is for sure a tech reply!
---------- Post added at 10:31 AM ---------- Previous post was at 10:26 AM ----------
IF ANYONE EVER GETS THIS IN DEVICE MANAGER......"QHSUSB_DLOAD"...it is hosed. Pay the 60.00 and get it over with.
And NO a jiig will NOT work!
now hit the THANKS button...heheh

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

[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.