*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.
Related
My wife's Tmobile Samsung galaxy s2 got wet and now it's only recognized as "unknown device" by PC via USB connection. The sim card is not detected either but everything else work fine. The battery still charges ok with usb cable and PC can access the phone with kies. Now I’m trying to find out if it’s possible to root this phone without usb connection.
I've searched the forum and seen many people asked the same question before. Pretty much all answers were that it's impossible to root without pc/usb. Sorry I’m asking this again but I see some more recent posts (first 2 links below) in the I9100 Galaxy S2 forum suggesting it's doable by following the guide at the 3rd link below.
http://forum.xda-developers.com/showthread.php?t=1487611
http://forum.xda-developers.com/showthread.php?t=1561027
http://forum.xda-developers.com/showthread.php?t=1501719
so my questions are:
do I understand this correctly and it's indeed possible to root tmobile gaglaxy S2 in a similar way to what described in the I9100 forum? If yes do I have to get the ICS first? I suppose I can get it via PC+Kies since the sim card is not working. the CWM.zip file (cwm stock recovery) used in the guide above seems for AT&T galaxy s2 only. is there a .zip file for tmobile version too? I found a .img file but don't know if it will work and how to put it into the external SD card.
many thanks
ys777 said:
My wife's Tmobile Samsung galaxy s2 got wet and now it's only recognized as "unknown device" by PC via USB connection. The sim card is not detected either but everything else work fine. The battery still charges ok with usb cable and PC can access the phone with kies. Now I’m trying to find out if it’s possible to root this phone without usb connection.
I've searched the forum and seen many people asked the same question before. Pretty much all answers were that it's impossible to root without pc/usb. Sorry I’m asking this again but I see some more recent posts (first 2 links below) in the I9100 Galaxy S2 forum suggesting it's doable by following the guide at the 3rd link below.
http://forum.xda-developers.com/showthread.php?t=1487611
http://forum.xda-developers.com/showthread.php?t=1561027
http://forum.xda-developers.com/showthread.php?t=1501719
so my questions are:
do I understand this correctly and it's indeed possible to root tmobile gaglaxy S2 in a similar way to what described in the I9100 forum? If yes do I have to get the ICS first? I suppose I can get it via PC+Kies since the sim card is not working. the CWM.zip file (cwm stock recovery) used in the guide above seems for AT&T galaxy s2 only. is there a .zip file for tmobile version too? I found a .img file but don't know if it will work and how to put it into the external SD card.
many thanks
Click to expand...
Click to collapse
I dunno about you but if my wifes phone got wet.. I'd be getting it fixed asap before I got my head chewed off instead of worrying about rooting it..
As far as an initial recovery flash with cwm goes, I was under the impression the only way to do it was with ODIN while in download mode and rooting it through the flashable zip from CWM.. Maybe someone can offer some better suggestions though..
So for about a few weeks I have been reading on how to fix a Hardbricked Sprint Galaxy S3. After flashing roms for a year I finally dun goofed and neglected to look closely at the rom details and installed an International rom. So I finally got my 16GB Micro SD Card and followed the simple instructions on Unbricking with said card. The problem is the phone isn't responsive. I did however read up on QPST Unbricking and did some intensive studies on past posts reading page by page and what not. I even went so far as to get QPST to detect my phone allowing me to possible unbrick it. Here is where my question hits. Does anyone have any helpful files for QPST (i.e. xml Phone Images and what not) for this particular phone. Or if you think I did the Micro SD Recovery incorrectly please feel free to throw every trick at me. Im willing to try all suggestions before resorting to QPST.
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.
Hi! I need some serious help. I accidentally bricked my phone while updating the Bootloader.
It's a Samsung Galaxy S3 SGH-T999L (T-Mobile, but it works with my Vodaphone SIM)
Absolutely nothing on the screen, no boot, no recovery mode (just installed CWM), no download mode. Just a red LED when plugged in via USB.
Device Manager shows this: "QHSUSB_DLOAD"
I live in Egypt so there's no such thing as 'insurance' or 'warranty'.
I tried the instructions here: http://forum.xda-developers.com/showthread.php?t=2439367
Didn't work.
Is this the end? Or is there yet hope for it?
Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Need to know the details of what you flashed and what steps you followed.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just installed the CWM custom recovery via Android Toolkit, and was preparing to flash Cyanogen. It said that an S3 needed a Bootloader update to install Cyanogen versions greater than 10.1, So I followed the links and I think I accidentally flashed the Bootloader for SGH-T999 (not the T999L).
CWM said it succeeded, rebooted the phone (did not fix root when it asked), and it just never turned on since (it's been a while)
P.s: Idk if this even matters when its as deep as the Bootloader, but the phone had been rooted for months before.
Oh, and I found this and am downloading the latest T999L in case I need it if ODIN can help: http://forum.xda-developers.com/showthread.php?t=2439367
And from yet more Google I found these drivers, but it won't let me post outside links
But Device Manager says "Driver is not intended for this platform."
That's all I got so far, will keep looking for a good driver and check this thread as often as I can
This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.
Kygies27 said:
This is gonna probably sound stupid, but I tried an emergency recovery with Kies, but it needed me to get it in Recovery Mode.
No change so far. Any help finding the right drivers would be very helpful.
Click to expand...
Click to collapse
YAY! Found working drivers here: http://forum.xda-developers.com/showthread.php?t=1536354&page=4
By: richardlibeau
ATTACHED FILES
File Type: zip QHSUSB_Drivers_(x64).zip - [Click for QR Code] (72.3 KB, 568 views)
File Type: rar qhsusb_dload_Drivers.rar - [Click for QR Code] (56.0 KB, 584 views)
More Google (Where is everybody?)
Found this: http://forum.gsmhosting.com/vbb/f824/karbonn-a9-dead-qualcomm-hs-usb-qdloader-9008-how-fix-1740061/
It seems if I can just find the corresponding hex files, etc, this could work.
Or I could somehow reprogram my CPU and make things even worse...
I'm really stuck now.
P.s: I've ofc by now seen nearly everyone go for a JTAG repair. I will check the shops around here when they open, but I don't know if they can do anything about it.
Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Jtag should be able to repair that kind of brick. Unfortunately, when its due to flashing a different devices firmware, our device methods won't usually work.
You can try the d ebrick method we have posted in development, but just don't expect much. (You never know though, you might get lucky).
I doubt following this instructions will work as they are for a different device. Big risk to try it imo. Might make it non-recoverable by any means. (The process might work, I don't know, but you'd likely need specific files for your device).
Jtag is probably your best option. And in the future, stay away from the toolkit! Its bricked a number of devices and the dev just ignores support requests, even from those who buy it...
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, shops open soon so hopefully I can see what can be done.
I figured not to bother with the qualcomm tools, messing with things I didn't quite understand was how I got in this trouble in the first place.
But just to clarify something, the Android Toolkit wasn't what bricked it, I tried to install the firmware from a .zip on my SDcard viz CWM recovery, but it was the wrong one (I was so damn sure I was T999, not T999L).
Thank you guys for all the help, I'll post if the guy fixes it!
I know, I only mentioned it because you mentioned using it. Just warning you for the future is all.
Good luck!
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.