Hello
I have hard bricked my SGH-T999L 4.3 after installing EZ-Unlocker by mistake, I was trying to downgrade my android version, I know it was a big mistake :silly:
The phone now is dead, I can't see it on Odin, I tryed to debrick it with sd-card method from the KAsp3rd post hier: http://forum.xda-developers.com/showthread.php?t=2439367 but I have no luck, I searched in the past 2 days for another method but I can't find it.
Please can someone help me?
I'm also experiencing the same problem on my Samsung Galaxy S3 T999 variant.
I flashed the FlashingDroid v2.2 for the I9300 (which was pretty st***d on my part) and ended up hard-bricking the phone.
I have tried the SD Card method on 2 different 16gb micro SDs with no luck.
Odin can't detect my phone, but it's listed as QHSUSB_DLOAD on the device manager.
I have no way of getting a jig (and no skills to make one whatsoever)
If no one has any other way to resolve the issue, I might TRY to make a jig.
Related
I have Hard Bricked my SPH-L710 (noob mistake). I upgraded to 4.3 without reading up on features. Everybody now knows about the annoying KNOX security that comes with it but i did something so HORRIFIC lol i tried to downgrade. didnt end so well. little did i know trying to downgrade with KNOX causes a hard brick..:crying: everyones trying to do the SD card trick where you image the debrick image on the sd card. people are mad to find out that if you upgraded 4.3 you cant fix a hard brick that way anymore. UNLESS someone extracts the boot image from their rooted 4.3 SPH-L710 device then there is a chance that this method will work. use Philz recovery to root 4.3. and someone get this image for me!! dont just do it for me get it for other models too. be nice. or if there is, will someone link it to this thread. or any other way to fix this hard brick.
will a jig work ? i know how to fix it if i get to download mode.
BadThoughtss said:
I have Hard Bricked my SPH-L710 (noob mistake). I upgraded to 4.3 without reading up on features. Everybody now knows about the annoying KNOX security that comes with it but i did something so HORRIFIC lol i tried to downgrade. didnt end so well. little did i know trying to downgrade with KNOX causes a hard brick..:crying: everyones trying to do the SD card trick where you image the debrick image on the sd card. people are mad to find out that if you upgraded 4.3 you cant fix a hard brick that way anymore. UNLESS someone extracts the boot image from their rooted 4.3 SPH-L710 device then there is a chance that this method will work. use Philz recovery to root 4.3. and someone get this image for me!! dont just do it for me get it for other models too. be nice. or if there is, will someone link it to this thread. or any other way to fix this hard brick.
will a jig work ? i know how to fix it if i get to download mode.
Click to expand...
Click to collapse
i Bricked mines too, i have been looking for it too hopefully someone share's the file
Same here, bricked Boot Loader *sigh* Mine came from an idiotic move with the EZ-Unlock app tho. Suppose my next step is to invest in a Class 10 SD Card and pray for the best. There is some other threads around here that have various S3 unbrick images tho, just gotta poke around :good:
I'm in the same boat guys
Aggghh.....I pray for this file every night to fix both mine AND my hubby's GS3. Yup.....had so much confidence in myself (Really it was cockiness) that I bricked mine and then his!
me too...bah!
I missread the dev topic on the S3 Factory reset and counter and got burned. I was running a custom 4.3 and thought I was good...oh well.
I have tried the SD card method with several different images, but alas I am still in crapville without a shovel. $50 to send off for repairs or wait for something to come along. Right now I am hurting, hard to believe that phone was so important! Argh! Has anyone had luck?
Sigh...a little searching helps.
http://forum.xda-developers.com/showthread.php?t=2637424
*I bought this off a friend of mine.*
All he told me was that he tried installing a rom and he thinks that he installed a rom for a different model S3.
What Happens/What I Did?
1. I tried to plug it into the computer and the computer doesn't show that anything plugged in, the S3 doesn't turn on. NOTHING.
2. I connected the phone to the PC without the battery inside and the phone responds with one RED light at the top left of the phone. Nothing shows up on my computer still, not even that the phone was connected NOTHING.
3. I bought a JIG device and tried plugging it into my phone and it doesn't work. (I previously tested this JIG on another samsung device and it worked)
4. I tried doing the method to use a 16gb SD card and downloading an i747m debrick IMG and using Win32FlashTool to copy it to my SD Card. I tried with 2 different cards the first one was a 16gb SD card and the other was a 32gb SD card.
5. Through a lot of research I found a leaked way to unbrick the Samsung Galaxy S3 i9300 by shorting out the R313 chip, I'm sure you guys are all aware of this method. I opened my device and couldn't find the R313 chip. After further research I found that a user was able to locate the R313 chip on the i747m and he'd unbricked his phone with that method. If anyone can help me locate the i747m R313 chip it'd be GREATLY appreciated!
If anyone can help me out it would be great! I'm very experienced at soldering so if there's a method that requires me to solder I'm more than confident I can do it.
Thank you!! :good:
Would love to know where you found R313 on the i747m circuit board. Think that's going to be the last choice for me.
Thank you.
Where did you find info confirming someone did that on the I747M? The I9300 is a very different device with very different hardware. Im not saying it wouldn't be possible....but I would be surprised to hear that. Can you link us to where you found that?
DocHoliday77 said:
Where did you find info confirming someone did that on the I747M? The I9300 is a very different device with very different hardware. Im not saying it wouldn't be possible....but I would be surprised to hear that. Can you link us to where you found that?
Click to expand...
Click to collapse
(12-38) GT-I9300 JTAG Guide_rev1.0.pdf
if you find r313 post some pic's
Ok, I just answered similarly in another thread. Thst is for the i9300, which is a very different device from all on the US Qualcomm models. Very good chance ours simply doesn't have the same components being referred to.
Noob here (as you can tell by my problem)
Okay so here's the full story, I rooted my phone. It was on 4.4.2 when I first rooted it. I found the LiquidSmooth ROM online and I wanted to flash it into my phone. After hours of research I finally flashed it successfully. I fell in love with UI and everything. But this is where the real stuff happens. I didn't find it very attractive anymore. So I tried wiping the whole phone hoping it'd revert back to it's original settings, I hoped wrong. It still had the ROM so I went online and I found this damn file that I thought would revert it back to normal. Turns out it not only took back to normal without it being rooted, but it downgraded to 4.0.4 and then my problems began from here. I had no signal so I couldn't update to the latest firmware so I rerooted the device and I tried flashing CM11 so I can get to 4.4.2 again. But the bootloader would not let me do it while in the recovery mode. So I researched how to unlock the bootloader. I found what is called EZUnlock, I downloaded the .apk file and installed it into the device, unlocked the bootloader and then used ROM Manager to boot into Recovery Mode. The screen went black and bam! Did not turn on after 5mins. I started to press the power button but to no avail, it would not turn on. I have searched ways to unbrick my Samsung Galaxy S3 but none of the threads seem to connect to what is going with my phone. So I have decided to make a thread to get specific help on my problem. Please, I beg you, if you are reading this now please help me out! I have no money to go out and buy a new phone. Even this phone wasn't affordable. I beg you to help me out here. I am in desperate need. I NEED my phone.
Not sure why you needed to unlock the bootloader since the s3 bootloader is not locked.
Did you try using the de-brick method using an SD card?
audit13 said:
Not sure why you needed to unlock the bootloader since the s3 bootloader is not locked.
Did you try using the de-brick method using an SD card?
Click to expand...
Click to collapse
Yeah I read about that, but I had not known that until after I tried looking for Unbricking methods. And yes, I tried it with my 8GB SD card...But nothing is happening. I can't afford to buy a JTAG for this phone either. Do I really have to go out and buy myself a 16GB Class 10 SD Card to say for sure if my phone will work again or not?
Greenhope47 said:
Yeah I read about that, but I had not known that until after I tried looking for Unbricking methods. And yes, I tried it with my 8GB SD card...But nothing is happening. I can't afford to buy a JTAG for this phone either. Do I really have to go out and buy myself a 16GB Class 10 SD Card to say for sure if my phone will work again or not?
Click to expand...
Click to collapse
I have never tried the de-brick method but it seems you need to use a very specific brand and size of sd card. Maybe it needs to be 16 GB because that's what the i747 has internally.
Thr sdcard has to be at least 16gb. 32gb sdcards will work too. The higher the cards class rating the better, Class 6 and up seem to have the highest success rates, but I have seen it work on class 2 and 4 cards as well.
Unfortunately, there are bricks thst cannot be recovered using this method, depending on what partitions got screwed up. I'm not sure which got messed up on yours, but there is a chance it messed with something the debrick method cant fix...
In that thread there are debrick.img files posted throughout the last few pages. Try any that are for your device.
Good luck!
DocHoliday77 said:
Thr sdcard has to be at least 16gb. 32gb sdcards will work too. The higher the cards class rating the better, Class 6 and up seem to have the highest success rates, but I have seen it work on class 2 and 4 cards as well.
Unfortunately, there are bricks thst cannot be recovered using this method, depending on what partitions got screwed up. I'm not sure which got messed up on yours, but there is a chance it messed with something the debrick method cant fix...
In that thread there are debrick.img files posted throughout the last few pages. Try any that are for your device.
Good luck!
Click to expand...
Click to collapse
I used my 64gb sdcard(class 10) and it worked too
just make sure if you want to reuse the sdcard like normal sdcard, you need to reformat it with your phone instead of your computer, cuz somehow if you format it with your pc it will only show 64mb instead of 64gb lol...
and to my knowledge, sdcard debricking will work with any hard bricked bootloader problem (been there, done that), so it should work for you too unless you did something wrong such as wrong version of debrick.img
Greenhope47 said:
Yeah I read about that, but I had not known that until after I tried looking for Unbricking methods. And yes, I tried it with my 8GB SD card...But nothing is happening. I can't afford to buy a JTAG for this phone either. Do I really have to go out and buy myself a 16GB Class 10 SD Card to say for sure if my phone will work again or not?
Click to expand...
Click to collapse
That's correct. You need min 16Gb (high quality) SD card. What we are trying to do is simulate the internal SD card of the device itself so your debrick card needs to be, at least, or greater than the internal card. I'm somewhat surprised by the sequence of events especially how you ended up on ICS 4.0.4 - unless that was the last official stock ROM your device had before you went custom. Also, EZ-Unlock wouldn't normally cause a hard brick unless you were on the 4.3 MJB bootloader or higher in which case, the result is usually a guaranteed hard brick - similar to what happened. Probably you ended up with the 4.3 MJB bootloader one way or other.
The debrick method should work for you in this case from what you've described. If you haven't seen it already, the definitive thread on this subject is given below .... All the instructions and files/images you need are available on the first page.
http://forum.xda-developers.com/showthread.php?t=2549068
Please note that once you have been able to get the phone to boot from the SD card, you need to work your way up the food chain to a full firmware restoration. In this case, only a full stock restore to 4.3 would get the phone booting normally and on its own. You can do a full stock restore via custom recovery.
Hey guys. I've been looking for this information online and I just haven't been able to get any help.
I hardbricked my s3(wont power on) while on 4.4.2, while trying to install a bootloader/modem. I cant even remember which one I installed, it was chaos trying to get cm 11 working.
Is there a unbrick img that works for the i747m model on 4.4.2? Is there any way to fix my phone without a jig or jtag or any DIY methods? I've read a unbrick threads and some say they don't have a fix for 4.4.2 yet but im not sure if they are just outdated.
Any help would be greatly appreciated
Pantea01 said:
Hey guys. I've been looking for this information online and I just haven't been able to get any help.
I hardbricked my s3(wont power on) while on 4.4.2, while trying to install a bootloader/modem. I cant even remember which one I installed, it was chaos trying to get cm 11 working.
Is there a unbrick img that works for the i747m model on 4.4.2? Is there any way to fix my phone without a jig or jtag or any DIY methods? I've read a unbrick threads and some say they don't have a fix for 4.4.2 yet but im not sure if they are just outdated.
Any help would be greatly appreciated
Click to expand...
Click to collapse
We need to know which one you flashed so we can suggest a fix. Otherwise, you could end up flashing the wrong bootloaders/baseband and hard-brick your phone (if it's not already).
As for the unbrick, it is for 4.3. I don't think we have one for 4.4.2 yet.
A Jig is only helpful if you didn't mess with the bootloaders.
If you've flashed the 4.4.2 modem on 4.3 firmware, there is no way to fix this type of brick yet. I think one or two other people who hard bricked differently on 4.4.2 have been able to fix theirs. Hard to remember for sure. (Everyone keeps opening new threads for every brick rather than just posting in the existing thread so it makes it a lot harder to keep track of what has worked, and even more difficult to find the relevant posts again.....)
I hard brick a t-mobile note 3 by using the NSPRO to repair the IMEI by using N7105 and afterward it hard brick and only do QHSUSB_DLOAD.
my question is that i completely forgotten what android it was on. I wanted to know if it was on 4.3 or 4.2.2 can i use any Kitkat SD debrick file to fix the issues.
The wrong won't work but it won't hurt either, so pick one, and if it fails pick the other.
Frank