possible emmc brick fix - Odin... - Samsung Epic 4G Touch

I was going through the Stuck at Data.img thread and came across the post below from Jaymoon and just thought others may want to take a look at it. It looks like you can bring your phone back to life.... Hope it helps a few of you
http://forum.xda-developers.com/showpost.php?p=27852689&postcount=435
http://forum.xda-developers.com/showpost.php?p=27888069&postcount=444

What I personally don't want is people going straight to that and then not taking it to Sprint if they can get replaced for free - so they should at least check out their options even after they get it running. But however they get back in the game is what matters in the end... Glad it worked for them.
Question though: If someone gets this running and then claims TEP or warranty repair/replace will it be honored? I'm not sure since I don't have available for me and it would seem that most techs are going to say it's not hardware if they can't see it for themselves. (Versus the bootloop with the unmodified .PIT file.)

garwynn said:
What I personally don't want is people going straight to that and then not taking it to Sprint if they can get replaced for free - so they should at least check out their options even after they get it running. But however they get back in the game is what matters in the end... Glad it worked for them.
Question though: If someone gets this running and then claims TEP or warranty repair/replace will it be honored? I'm not sure since I don't have available for me and it would seem that most techs are going to say it's not hardware if they can't see it for themselves. (Versus the bootloop with the unmodified .PIT file.)
Click to expand...
Click to collapse
Most people will probably be happy it booted up. After possible weeks or days at looking at the blue light or Samsung screen... LOL

playya said:
Most people will probably be happy it booted up. After possible weeks or days at looking at the blue light or Samsung screen... LOL
Click to expand...
Click to collapse
If you can get into recovery or ODIN, your device is not bricked. At least not with this phone. Only true brick for the E4GT is the Blue-Light-Of-Death symptom.

akarol said:
If you can get into recovery or ODIN, your device is not bricked. At least not with this phone. Only true brick for the E4GT is the Blue-Light-Of-Death symptom.
Click to expand...
Click to collapse
I agree with this to the extent of the android definition of the word bricked. But that doesn't mean the phone is usable in its current state. The emmc bug cause a phone to not boot or accept a full Odin flash. So while it may get into recovery or download mode it is still pretty useless until the issue with emmc is resolved.
I also agree that people should explore their options before paying 8GB of internal memory to get their phone back up. If you can get a free replacement then that's how I would go about it.
Sent using an AOKP'd ET4G courtesy of Times_Infinity!

akarol said:
If you can get into recovery or ODIN, your device is not bricked. At least not with this phone. Only true brick for the E4GT is the Blue-Light-Of-Death symptom.
Click to expand...
Click to collapse
you obviously dont know about the emmc bug. unless the partition can be fixed and repaired now (which it may be now)...

scarmon25 said:
I agree with this to the extent of the android definition of the word bricked. But that doesn't mean the phone is usable in its current state. The emmc bug cause a phone to not boot or accept a full Odin flash. So while it may get into recovery or download mode it is still pretty useless until the issue with emmc is resolved.
I also agree that people should explore their options before paying 8GB of internal memory to get their phone back up. If you can get a free replacement then that's how I would go about it.
Sent using an AOKP'd ET4G courtesy of Times_Infinity!
Click to expand...
Click to collapse
One note from Drnull's test that does differ - the locations in memory are different for the GNote and the E4GT. His original tests noted you can bypass just the existing assignment for /data and begin reallocation from where the old one ended - resulting in only losing 2GB instead of 8GB. No one ever made a modified .PIT since most people were able to replace.
Let me see if I can track down the stock one and modify it based on those notes. I know I have it at home, just wondering if I have it here at the office...

Hey if this can help a few its better than having a paperweight sitting in your house. I agree like I said with most that exhaust all other options first. But if you have no other option and you have the same symptons as those listed to be repairable in the thread then I say go for it.

akarol said:
If you can get into recovery or ODIN, your device is not bricked. At least not with this phone. Only true brick for the E4GT is the Blue-Light-Of-Death symptom.
Click to expand...
Click to collapse
Yeah that's the same thing I said in the op of ''Stuck at Data Img'' thread.
Lol..... Kinda wish the thread would go away... brings back bad memories. ;-)
Glad tho it looks as if a resolution may have come.

Got mine working again hope it lasts
Sent from my SPH-D710 using xda premium

playya said:
I was going through the Stuck at Data.img thread and came across the post below from Jaymoon and just thought others may want to take a look at it. It looks like you can bring your phone back to life.... Hope it helps a few of you
http://forum.xda-developers.com/showpost.php?p=27852689&postcount=435
Click to expand...
Click to collapse
Hey maybe you can change the title of this to catch more brickers attention....it seems very useful and a great find. Like "possible emmc brick fix - Odin" or something.
Sent from my SPH-D710 using XDA

ive done 3 phones in a similar fashion.. but all with terminal commands.
where you can find the corrupted amount and skip it. and maybe not lose the whole 8gb. but, you have to realize, it makes things different in the future.
everytime you odin you will have to use a custom pit. you have to careful about a lot of different things going forward. one being that GB kernels will no longer recognize your partitions. (at least on hand created, converted partitions) TEP/Insurance is by far a better way to go..

dante32278 said:
Hey maybe you can change the title of this to catch more brickers attention....it seems very useful and a great find. Like "possible emmc brick fix - Odin" or something.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Thanks for the suggestion. I edited the Stuck at Data Img op.

Thank you . My phone was soft bricked , this help me I lost 8 gb but I am back on .

dante32278 said:
Hey maybe you can change the title of this to catch more brickers attention....it seems very useful and a great find. Like "possible emmc brick fix - Odin" or something.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
your wish is my command... done! Also I know some are saying the option of just using TEP and other means but lets remember some of us on here use different carriers with the ET4G and can't go back to Sprint or use TEP so this may be the only alternative for them...
I just want to bring attention to an alternative... Good Luck guys

bump for some more views

playya said:
bump for some more views
Click to expand...
Click to collapse
mid morning bump

I'm going to contact hg42 on his thread and see if he'd be willing to create a .PIT and find out what he needs to do it - I'm guessing it would be a list of each partition, starting position in memory and size.
In the meantime those of you who can't get it fixed by warranty and are using this solution - keep an eye on the eMMC discussion thread as well for updates on efforts to get a true fix for the problem.

garwynn said:
I'm going to contact hg42 on his thread and see if he'd be willing to create a .PIT and find out what he needs to do it - I'm guessing it would be a list of each partition, starting position in memory and size.
In the meantime those of you who can't get it fixed by warranty and are using this solution - keep an eye on the eMMC discussion thread as well for updates on efforts to get a true fix for the problem.
Click to expand...
Click to collapse
Thats what I am talking bout. I just bump this thread for views since I know some of the people who had issues may not check here everyday. Its getting about 200-300 views a day so at least is bringing awareness to a possible fix for some and a fix for quite a few

creating a pit is not hard i have the c source.. and anyone who has sucessfully repaired theirs can do it with heimdall..

Related

[Q] Touch Keys Don't Work

I've done some searching and I haven't found any problems like mine yet. I ran the SGS unlock tool meant for Vibrant on my SGS2 (i know i know) and it didn't work. Ever since my touch keys don't work. I just reflashed my rom and they still don't work.. help!
PS. I'm odining now. Hopefully that'll fix it.
Crap crap crap crap crap odin didn't fix it.
Tynen said:
I've done some searching and I haven't found any problems like mine yet. I ran the SGS unlock tool meant for Vibrant on my SGS2 (i know i know) and it didn't work. Ever since my touch keys don't work. I just reflashed my rom and they still don't work.. help!
PS. I'm odining now. Hopefully that'll fix it.
Crap crap crap crap crap odin didn't fix it.
Click to expand...
Click to collapse
Unable to offer much insight but seems that if you go back to stock they would certainly assume it's a hardware failure.
Sent from my SGH-T989 using xda premium
avarize said:
Unable to offer much insight but seems that if you go back to stock they would certainly assume it's a hardware failure.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I bought the phone off craigslist though, I don't know if they'll replace it.
Tynen said:
I bought the phone off craigslist though, I don't know if they'll replace it.
Click to expand...
Click to collapse
iv'e gotten most of my phones from craigslist and they still replaced them for me. i just waited like a week to make sure that my imei number showed up in there system so they didnt question me where i got my phone from lol.
Yeah my phone was only working for less then 24 hours, I don't think there's any hope for tmo to replace it. What I don't get this is someone at some point bought it from tmobile, why do they care if it changed hands?
damn that sucks. it wont show up in there system if it was only used for less then 24 hours. sometimes i would just chat with tmobile online and tell them that i want to make sure they have my correct imei number in there system and they ask me what my imei number is then they tell me its not the right one and if they want me to have them update it and i say yes then they tell me it can take up to 48 hours for there system to update it. idk why they care if u didnt get it from them.
i already paid for a jtag service so I'll just go that route, but I'll keep all of this in mind the next time i hard brick a phone... =P
Tynen said:
i already paid for a jtag service so I'll just go that route, but I'll keep all of this in mind the next time i hard brick a phone... =P
Click to expand...
Click to collapse
alright well hopefully u can unbrick the phone.. good luck
Tynen said:
i already paid for a jtag service so I'll just go that route, but I'll keep all of this in mind the next time i hard brick a phone... =P
Click to expand...
Click to collapse
dude, did you unbrick your phone yet ?
I got mine solved by inputting
*#*#86824#*#*
and press update firmware.
credit goes to Memeber - ecips

USB jig question

Maybe a stupid question but I ordered a jig and haven't received it yet but how would I check if it works to leave positive feedback.. I'm stock rooted with Odin no custom recovery.... Would I just turn the phone off take the battery off put it back in and connect the jig? If it goes to download then it works?
Sent from my SPH-D710 using xda premium
Power down the phone, plug in the jig, turn on the phone. It shoudl go into ODIN download mode directly and say something about stats being reset. If it doesn't do the latter, you are probably on a new bootloader and it isn't the fault of the jig.
Turn the phone off, take the battery out for about 15 seconds, put the battery back but leave the phone off. Put in the jig and in a few seconds you should be at the download screen and the download count should say it has been reset.
Sent from my SPH-D710 using XDA
dante32278 said:
Turn the phone off, take the battery out for about 15 seconds, put the battery back but leave the phone off. Put in the jig and in a few seconds you should be at the download screen and the download count should say it has been reset.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
And from there, are you free to just turn the phone back off by taking out battery?
You don't need to take out the battery. Just press and hold the power button until it resets.
Thanks for the quick reply, I bought one in the event I get a brick and need to take it to a store. Oh and it will still work if im on an FC07 leak right? Or will it only work with GB roms, kernels?
It will work with the ICS ROMs as long as you have the original (EG30/31) bootloader. If you flashed the raw leaked tar from Samsung/Sprint, then the reset of flashing data might not work (but it should still put you in ODIN D/L mode). If you flashed one of the ODIN OneClick packages I put together, then all the features will work.
Ok I think Ill be good to go then because Ive always waited til Calk puts up a stock rooted version, not flashing the tars. Anyways while I kind of have you here, I was just wondering if this type of stuff has anything to do with our phones our might show up in the future and which type does our phone use, if any. heres the link http://forum.xda-developers.com/showthread.php?t=1387334 I was rooting my dads Epic 4G so I kept on seeing it in the thread titles. Just curious
rsalinas1 said:
Ok I think Ill be good to go then because Ive always waited til Calk puts up a stock rooted version, not flashing the tars. Anyways while I kind of have you here, I was just wondering if this type of stuff has anything to do with our phones our might show up in the future and which type does our phone use, if any. heres the link http://forum.xda-developers.com/showthread.php?t=1387334 I was rooting my dads Epic 4G so I kept on seeing it in the thread titles. Just curious
Click to expand...
Click to collapse
I didn't read that thread very closely, but MTD is sometimes an overloaded term and could mean different things to different people.
If used to compare flash memory types, we actually have eMMC rather than MTD. eMMC memory are block devices. MTD devices are similar to but not really block devices so they created a new category in the kernel to deal with them.
To get an idea about MTD, read this post:
http://www.linux-mtd.infradead.org/faq/general.html
Not that technical in Linux lol but thanks I will still give it a read. Bottom line of that thread made it just seem like MTD is a huge thing and makes the epic 4g a much better phone versus BML. Oh and it just said that they are types of partition maps, mtd being open and bml being closed source.
Sent from my SPH-D710 using Tapatalk
rsalinas1 said:
Not that technical in Linux lol but thanks I will still give it a read. Bottom line of that thread made it just seem like MTD is a huge thing and makes your phone better versus BML, whatever that is lol.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Ok, I read the thread a little more closely.
It seems the 2 main benefits from switching to the kernel supporting MTD partition format over the stock BML are you can resize the partitions easier and use ext4 (because those new kernels support ext4)
Our kernels already use ext4. w/r/t resizing partitions perhaps some people need more space in /data but most people seem to be ok with it.
It is always nice to have more options, but there is probably less demand for it on this phone than Epic.
I gotcha, maybe we will see it once our devices get older and we need something new lol. So just asking again now that you've read more closely, our phones dont use either of these partition maps correct?
Sent from my SPH-D710 using Tapatalk
I'm actually not sure which partition map we are supporting. I initially read the thread as MTD vs eMMC memory technology, which is different than the purpose of that thread.
I see, maybe you can figure that out for us in your spare time lol (if it really even makes a difference.) The E4GT is a beast of a phone anyways lol.
Sent from my SPH-D710 using Tapatalk
Just an FYI:
I got my jig and put it right in the slot while my phone was still on... it shut down my phone and put it directly into download mode and showed that my counter had been reset.
On a side note, for what ever reason, my GPS started working when I restarted the phone. It hadn't been working for days.
rsalinas1 said:
Thanks for the quick reply, I bought one in the event I get a brick and need to take it to a store. Oh and it will still work if im on an FC07 leak right? Or will it only work with GB roms, kernels?
Click to expand...
Click to collapse
If you "brick" your phone, a JIG is not going to help you.
Drumrocker said:
If you "brick" your phone, a JIG is not going to help you.
Click to expand...
Click to collapse
Depends what kind of brick. The /data nonwritable brick still allows you to write every other partition as well as use the jig to reset the counter

GSIII will not turn on

I just rooted and installed the JellyBomb rom for the GS3 for a friend. They didn't like the rom, so I remembered that there was a GS3 version of Android Revolution HD. I flashed the phone and hit reboot in TWRP and now nothing. I realized just now that the roms are different for the carriers but I possibly installed a rom for a different carrier. Nonetheless, the phone still isn't doing anything. It won't power on. I get no screen. Nothing. Is it completely bricked? How can I at least get back to Download mode for Odin?
MrAutomatic said:
I just rooted and installed the JellyBomb rom for the GS3 for a friend. They didn't like the rom, so I remembered that there was a GS3 version of Android Revolution HD. I flashed the phone and hit reboot in TWRP and now nothing. I realized just now that the roms are different for the carriers but I possibly installed a rom for a different carrier. Nonetheless, the phone still isn't doing anything. It won't power on. I get no screen. Nothing. Is it completely bricked? How can I at least get back to Download mode for Odin?
Click to expand...
Click to collapse
Good friend. You bricked his phone. Way to not read.
The Root said:
Good friend. You bricked his phone. Way to not read.
Click to expand...
Click to collapse
That's all you have to say? Can I unbrick the phone?
MrAutomatic said:
That's all you have to say? Can I unbrick the phone?
Click to expand...
Click to collapse
Nope, probably should have done some more research before breaking someone else's phone for them. Hope you got a good job cuz I'd make you buy a brand new one
I like to break stuff!
-EViL-KoNCEPTz- said:
Nope, probably should have done some more research before breaking someone else's phone for them. Hope you got a good job cuz I'd make you buy a brand new one
I like to break stuff!
Click to expand...
Click to collapse
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.
It's bricked if it was an international version Rom. There's usually nothing you can do. Hopefully your friend can take it back to store say it was doing update and it never came back on. I hope he's a good friend. You can't get back into download mode at all because the partitions are different and your download and recovery are no longer in existence.
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
It's bricked if it was an international version Rom. There's usually nothing you can do. Hopefully your friend can take it back to store say it was doing update and it never came back on. I hope he's a good friend. You can't get back into download mode at all because the partitions are different and your download and recovery are no longer in existence.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thank you for giving me a real explanation and not just running your mouth. She works for the carrier so she won't have an issue getting the phone replaced. I just hate inconveniencing them. It's just ridiculous that everything went smooth up until that point. What I don't understand is why the phone won't even power back on, at all, but oh well. She says they can have another to her within a day.
MrAutomatic said:
Thank you for giving me a real explanation and not just running your mouth. She works for the carrier so she won't have an issue getting the phone replaced. I just hate inconveniencing them. It's just ridiculous that everything went smooth up until that point. What I don't understand is why the phone won't even power back on, at all, but oh well. She says they can have another to her within a day.
Click to expand...
Click to collapse
here ill explain on the International S3 their Kernel partition is stored where on the US variant our bootloader is stored. So when you flash a international rom it wipes your bootloader because thats where the kernel goes on the international
This same thread will come up in about five hours. I will insult that person too. Learn what you're doing. I'm tired of these threads and they won't ban people who do this. I don't think you should be doing custom stuff to phones if you know this little. Is that more clear?
evo4gnoob said:
here ill explain on the International S3 their Kernel partition is stored where on the US variant our bootloader is stored. So when you flash a international rom it wipes your bootloader because thats where the kernel goes on the international
Click to expand...
Click to collapse
This will prevent it from even powering on or getting into Download mode? Sheesh.
MrAutomatic said:
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.
Click to expand...
Click to collapse
I get that those replies probably werent the most soothing, but all of this could have been avoided and replying like that does not help you resolve you problem.
Now I dont know who you are or how much you looked into it, but next time make sure you stick to the development sections of the phone you're trying to flash
Sent from my PG06100
MrAutomatic said:
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.
Click to expand...
Click to collapse
No problemo! Happy to help
I like to break stuff!
MrAutomatic said:
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.
Click to expand...
Click to collapse
Hey, I'm not trying to be a jackass. Maybe I am, but you have to imagine the frustration of people like myself who read for months before even trying to root a phone. You have to understand what you're doing with your device and especially a friend's. Every phone that goes back and was exchanged because a of a "bad OTA" helped create the excuse for an off-contract $500 Samsung Epic to become a $600-$700 Samasung Galaxy S3. I have never bricked a device. I tested Triangle Away for the first time on this phone for Chainfire and tested countless leaked kernels for Agat on the Epic Touch. My devices are fine because i knew what I was doing. This is why you should read.
MrAutomatic said:
This will prevent it from even powering on or getting into Download mode? Sheesh.
Click to expand...
Click to collapse
Yes since the partitions are different so let's say its supposed to format cache then on the US variant it will format something else. So the System doesn't get installed and the wrong things get formatted. You'd think you could just go back to boot loader but its wiped since the partition was different
Sent from my SPH-L710 using xda app-developers app
evo4gnoob said:
Yes since the partitions are different so let's say its supposed to format cache then on the US variant it will format something else. So the System doesn't get installed and the wrong things get formatted. You'd think you could just go back to boot loader but its wiped since the partition was different
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
For a little comparison, go install linux beside windoze on a separate partition using wubi, then delete the linux install and see if your computer will boot up. Oh no it won't boot because windows can no longer find the MBR (Master Boot Record, which is a PC bootloader) Just like borking the bootloader on a mobile device means that the device no more worky.
I like to break stuff!
-EViL-KoNCEPTz- said:
For a little comparison, go install linux beside windoze on a separate partition using wubi, then delete the linux install and see if your computer will boot up. Oh no it won't boot because windows can no longer find the MBR (Master Boot Record, which is a PC bootloader) Just like borking the bootloader on a mobile device means that the device no more worky.
I like to break stuff!
Click to expand...
Click to collapse
Ah. Hahaha. Good memories
I did this exact thing on my first linux install. Yay for recovery disks lol
Second time around I made sure I chainloaded into windows first and wrote the vista MBR. :good:
Sent from my PG06100
CNexus said:
Ah. Hahaha. Good memories
I did this exact thing on my first linux install. Yay for recovery disks lol
Second time around I made sure I chainloaded into windows first and wrote the vista MBR. :good:
Sent from my PG06100
Click to expand...
Click to collapse
I keep a rescatux disk taped to the bottom of my laptops for just such emergencies. I can't tell you how many times I've decided to upgrade or change my linux distro and hosed the MBR. Even done it a few times when the install was "successful" and linux would boot fine but windoze was MIA :banghead: only problem with a mobile device is once the bootloaders blown there's no rescue disk equivalent for the home user. Sometimes jtag can fix it but not if it doesnt come on at all
I like to break stuff!
Lol..... You did almost the same mistake I managed to do (Was my first time EVER rooting and flashing a rom). Just call sprint an play dumb. You might have to pay a fee but that's all you can really do at this point. After that mistake, I always stay in the Sprint GS3 forum along with researching all my roms, add ons, along with themes that I flash beforehand and reading the reviews on them.
Not to defend anyone but everyone was a newbie at one point but I do agree with if your not sure ask questions and read before flashing
Sent from my SPH-L710 using xda app-developers app
The root is blunt but speaks the truth. If you read. You would have seen that there are threads of people who have bricked their phone. So if you would have searched you would have seen what to do. Sheesh there's even a sticky to remind you not to flash international ROMs on the US variants.
http://forum.xda-developers.com/showthread.php?t=2156714
http://i1202.photobucket.com/albums/bb374/TexasEpic/ThePeoplesROM-KennyGlass123/daniel4653.png

[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

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

Categories

Resources