A friend of mine brought his i747 to me to see if I can fix his phone because it was tripping out. I decided to root it and installed CM13. That however created even more trouble for the phone. It changed the device model to T999 and also the imei and baseband where unknown. I tried to return it to stock but I couldn't find any site that has the 4.1.1 or 4.1.2 and only found a link to 4.3. I decided to flash that with odin and the phone became unresponsive after that. Is there away in which I can find this or do I need to get a new mother board?
Where did you get the 4.3 file? Do you have the file name?
gaara22 said:
A friend of mine brought his i747 to me to see if I can fix his phone because it was tripping out. I decided to root it and installed CM13. That however created even more trouble for the phone. It changed the device model to T999 and also the imei and baseband where unknown. I tried to return it to stock but I couldn't find any site that has the 4.1.1 or 4.1.2 and only found a link to 4.3. I decided to flash that with odin and the phone became unresponsive after that. Is there away in which I can find this or do I need to get a new mother board?
Click to expand...
Click to collapse
Do you get any vibrations when trying to power it on? Try to take it apart if you are comfortable and look for any physical damage if it doesn't show anything at all. Sometimes the board is damaged pretty bad but still boots, but restoring/flashing bootloader will completely brick it beyond recovery.
If it does give some response then you can look at the other unbrick threads and try em one by one. Wish you luck! BTW if all fails I have a s3 without a screen but good logicboard and stuff I can sell it to you. Or I could also buy the screen off you if you would like. Just PM me if that is the case. Anyways hope you can unbrick it.
Related
I've spend the past day or so just reading these forums. There is tons of great information here. So much so that it can be overwhelming. Since I am new here, I thought I would at least ask to make sure I understand before I brick my phone.
I bought a T-999 from someone. The phone works fine but it does have some issues. Primarily, no imei is showing and the counter has been tripped. Since I don't know what this person did to the phone, I assume the best thing to do it to try to take it back to stock and start over.
I've read the sticky thread by DocHoliday and just wanted to make sure I understand before proceeding. I'm not particularly concerned about rooting the phone at this point, just getting it back to stock to see if I can clear up the imei issue and whatever else may have been done to the phone.
I have odin, the USB drivers, and the November Jelly Bean Firmware all ready to go. So now, I should be able to return the phone to stock following the sticky.
Does anyone know if this will also clear up the no imei issue or will I need to do something else to clear up that issue.
Update: Well, that didn't work. In ODIN mode it shows:
Custom Binary Download: Yes (1 count)
Imei still shows: 0/08
Any ideas?
Look in the dev section for imei injection. Only way you will get it back and get HSDPA+ back. No going back to stock will not get it back.
T-Mobile SGS III
mt3g said:
Look in the dev section for imei injection. Only way you will get it back and get HSDPA+ back. No going back to stock will not get it back.
T-Mobile SGS III
Click to expand...
Click to collapse
no is wont i try i t
Go here please http://forum.xda-developers.com/showthread.php?t=2091069
Hey Guys,
I have read a burch of different threads about my problem and nothing has seemed to help or it was too advanced for me to understand. So here it is:
I tried to root my S3 and at first Oden 307 said the root failed, then i was able to try a different file and it said pass. but now when it boots up it gets stuck on the samsung galaxy s3 screen. I can still get into download mode and recovery mode. I have already tried the factory reset in recovery mode. Please help I have only had this phone a month. At this point I dont even care rooted or not I just want my phone back lol
Thanks for any help
+rep
garrett.burn said:
Hey Guys,
I have read a burch of different threads about my problem and nothing has seemed to help or it was too advanced for me to understand. So here it is:
I tried to root my S3 and at first Oden 307 said the root failed, then i was able to try a different file and it said pass. but now when it boots up it gets stuck on the samsung galaxy s3 screen. I can still get into download mode and recovery mode. I have already tried the factory reset in recovery mode. Please help I have only had this phone a month. At this point I dont even care rooted or not I just want my phone back lol
Thanks for any help
+rep
Click to expand...
Click to collapse
First you need to tell us which build you were on, and then what build did you try flashing...
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
BIGSAMDA1st, can I call you "Sam?" Your post count would indicate you've got more experience than I do so I thought I'd ask: aren't all the Sprint S3s on the MK3 build by default? Or are there inconsistencies within the Sprint-branded line of S3s?
Oh man. At least you've still got access to the download console. Can you also access the recovery console? Also, sounds like you're new to rooting (I could be wrong, just going on your comment about certain techniques being too advanced for you to wrap your head around). If you're new, you really picked both one hell of a time and one hell of a phone to cut your teeth on. Samsung's official 4.3 update (which, for all I know, is shipped standard now) comes with the KNOX bootloader which is, in certain situations, basically a bomb designed to ruin your week... and your phone. In particular, it has a REALLY nasty reaction to attempts at downgrading to the old (and much happier) bootloader. It also seems to really hate the older versions of TriangleAway (might hate the new one too, for all I know. I won't touch it anymore). It has other ways to make you hate life as well, but those are two big ones.
How to tell if you have the KNOX bootloader: Did you install the official OTA update to 4.3? If so, you've got the bomb. Did your phone come with 4.3 right out of the box? If so, you've probably got the bomb. Are you still unsure? Look in your Download console for red text that says something like "Warranty Void Bit" or anything that mentions KNOX. If so, you guessed it, you've got the bomb.
If you have the Warranty Void thing listed, then check to see: is it a 0, or is it a 1? If it's a zero, don't do anything else with trying to flash your ROM or root the device until we try some things in your Recovery Console (assuming it's also accessible). Once that flag is tripped, there's no going back... Not a huge deal if it's just a personal device, assuming you're not still under warranty... If you are, well, don't trip that bugger if you can avoid it.
FallenZen said:
BIGSAMDA1st, can I call you "Sam?" Your post count would indicate you've got more experience than I do so I thought I'd ask: aren't all the Sprint S3s on the MK3 build by default? Or are there inconsistencies within the Sprint-branded line of S3s?
Oh man. At least you've still got access to the download console. Can you also access the recovery console? Also, sounds like you're new to rooting (I could be wrong, just going on your comment about certain techniques being too advanced for you to wrap your head around). If you're new, you really picked both one hell of a time and one hell of a phone to cut your teeth on. Samsung's official 4.3 update (which, for all I know, is shipped standard now) comes with the KNOX bootloader which is, in certain situations, basically a bomb designed to ruin your week... and your phone. In particular, it has a REALLY nasty reaction to attempts at downgrading to the old (and much happier) bootloader. It also seems to really hate the older versions of TriangleAway (might hate the new one too, for all I know. I won't touch it anymore). It has other ways to make you hate life as well, but those are two big ones.
How to tell if you have the KNOX bootloader: Did you install the official OTA update to 4.3? If so, you've got the bomb. Did your phone come with 4.3 right out of the box? If so, you've probably got the bomb. Are you still unsure? Look in your Download console for red text that says something like "Warranty Void Bit" or anything that mentions KNOX. If so, you guessed it, you've got the bomb.
If you have the Warranty Void thing listed, then check to see: is it a 0, or is it a 1? If it's a zero, don't do anything else with trying to flash your ROM or root the device until we try some things in your Recovery Console (assuming it's also accessible). Once that flag is tripped, there's no going back... Not a huge deal if it's just a personal device, assuming you're not still under warranty... If you are, well, don't trip that bugger if you can avoid it.
Click to expand...
Click to collapse
First thing is THANK YOU and as i am a noob, where is the +rep button for you? Second and maybe you could help with this, since I posted this I was able to flash back to the official 4.3 :/ so I got my phone back but made my life harder in the process...I got clockwork recovery working and I was able to flash KNOX app remover .zip and I flashed team epic v5..it said everything was installed I rebooted and Im stll not rooted..Supersu says something about not having binary something another and root checker says I dont have root access. According to the step by step I followed I should be rooted :/ Any advise other than nex time dont upgrade to 4.3? lol
-Thanks Bro
BIGSAMDA1ST said:
First you need to tell us which build you were on, and then what build did you try flashing...
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
Im not quite sure what you are looking for but it says "Build Number JSS15J.L10VPUCMK3" And its a GS3 4.3 Model SPH-L710
Thanks for the reply
Hey mate,
I'm not familiar with the method of rooting 4.3 that you used. I'm glad to hear you got around the soft brick though! As far as running a rooted 4.3, I can tell you that what I wound up using was CNexus's pre-rooted ROM and the various fixes (s)he's compiled here:
http://forum.xda-developers.com/showthread.php?t=2541900
I've also shared my personal installation notes as well as hosted the files that worked for me on my Google Drive. That information is here:
http://forum.xda-developers.com/showthread.php?t=2560478&page=3
You shouldn't need the files I've got hosted on my Drive though... The ones CNexus has assembled in that thread should work just fine (that's where I got most of them, after all).
I cannot speak to whether or not any of the steps in my notes will trip your KNOX Warranty Void bit since I tripped mine (and damn near hard-bricked my phone) before I even knew what the KNOX bootloader was, let alone that Samsung had gone ahead and installed it for me.
I hope that helps.
-Zen
I assume since this is the AT&T Galaxy S 3 section, you already know that I have the SGH-i747 model.
So I've been looking for a while, and I can't find anyone that has caused my same problem the way I did. I'll give the entire story: After having my S3 for a while, I decided to try rooting. I did it successfully, and got CyanogenMod installed. I don't know what, but I wanted to go back to touchwiz. I loaded a backup because it was exactly what I had before CM. fast forward about a month and a half, AT&T keeps bugging me about some update. It's the 4.3 update, I find out, after I installed it. Now, here's the confusing part. The SuperUser app was left over, but I have no CWM and no root privileges. I used this watch?v=yuBuD9aL12o (Paste after yt url) tutorial to root and get SuperSU, and it worked. The phone restarted many times in that entire process, and in the end it worked. One forum told me to install and apk called EZ-Unlock12.apk to unlock my boot loader. (I have included the exact APK if you want to look at it.) It just said successful and I closed out. Now, I wanted to flash CWM again with ODIN. I installed the drivers, and booted up ODIN. This is when it happened. I loaded up the CWM.tar.md5 file into ODIN, (not exact file name but you get what I mean), and it did it's verification and said it was good. I don't remember having my phone plugged in while doing this. I went to shut down my phone and put it in DL/ODIN mode. But now it has happened. I tried to bring my phone back up, but it didn't give ANY feedback. The only possible way to make it do ANYTHING is to plug it in without the battery, and i get the red light. I think it may have been that boot loader unlock program that messed it up, but I can't say for sure.
TL;DR I hardbricked my phone and don't know what went wrong.
Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068
audit13 said:
Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
I meant SGH-i747, sorry for any confusion.
Did you try the unbricking method I linked? I think that may be the only way to unbrick the phone since it appears that your bootloader has been corrupted. If the unbrick method doesn't work, you'll probably have to have it repair via jtag.
Were you able to get it back to normal state? I am in the same situation as you with the same problem and was wondering if i should go do the method someone provided or just go ahead and pay for a jtag service.
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.....)
Here goes...
I got a new phone which is running great and before selling my S3, I wanted to install CM and get rid of the bloatware. Figured it would help the sale. Ha!
The S3 was already rooted and CWM installed but still using the stock OS. Here's where I really ****ed up, I didn't right down the baseband version or android version before trying to get CM installed.
CM10 wouldn't install so after some digging I read that I needed to unlock the bootloader. All the sites say to use EZ-unlock. I do. It unlocks. I restart the device and it's now hard bricked.
Before becoming a brick, I made a backup using CWM but I'm not sure how helpful it is at this point.
I don't know which Android version I'm running but it should be the latest OTA since I always installed the updates.
I tried debrick images for 4.3 and 4.4.2 without any luck.
Essentially, I need a little bit of guidance before I give up for good on this phone. How can I find out which Android version was running in order to use the right debrick img. Does it matter that I was using a custom recovery and that the phone was rooted?
Thanks for the help, guys. I've got too far down the rabbit hole and I'm trying to get out.
i live a little below the bottom of the rabbit hole. my first and only (so far , fingers crossed) brick was by trying to unlock the bootloader of my att i747 s3. guess what :banghead: they arent locked. go figure. and again :banghead: my best guess if you kept updates updated. search for whatever was the latest (which you should be on) use a debrick image for that version. and i guess youve already read the "debrick thread". if one microsd card doesnt work , try another. read too many times where one class/size would work for one user but not another.
i know this isnt much help. i would just say keep trying.
maybe even jtag might ¿ help?
good luck.
maybe try here if havent already.
http://forum.xda-developers.com/showthread.php?t=2549068
"err on the side of kindness"
thats what pretty much happend to me on my s3 i747M. i was downloading a custom rom, phone was rooted had its original os, but i installed a rom, that said it was for i747m, but it was really for the i9300. so after it seemed to install, i click reboot, and instant brick. i also made a WHOLE backup before i did anything, and have flashed a number of different roms in the past.
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
mrrocketdog said:
i live a little below the bottom of the rabbit hole. my first and only (so far , fingers crossed) brick was by trying to unlock the bootloader of my att i747 s3. guess what :banghead: they arent locked. go figure. and again :banghead: my best guess if you kept updates updated. search for whatever was the latest (which you should be on) use a debrick image for that version. and i guess youve already read the "debrick thread". if one microsd card doesnt work , try another. read too many times where one class/size would work for one user but not another.
i know this isnt much help. i would just say keep trying.
maybe even jtag might ¿ help?
good luck.
maybe try here if havent already.
http://forum.xda-developers.com/showthread.php?t=2549068
"err on the side of kindness"
Click to expand...
Click to collapse
this is only if you got bricked while upgrading to 4.4.2 i tried this method already didnt work
MhikeiMPC12 said:
thats what pretty much happend to me on my s3 i747M. i was downloading a custom rom, phone was rooted had its original os, but i installed a rom, that said it was for i747m, but it was really for the i9300. so after it seemed to install, i click reboot, and instant brick. i also made a WHOLE backup before i did anything, and have flashed a number of different roms in the past.
Not quite the same situation. I was following instructions install a new rom and it said to unlock the bootloader when in the end it wasn't necessary. EZ-unlock bricked my phone. I will keep trying with various SD cards.
Does anyone have a link to a KitKat (4.4.2) debrick dump for the I747?
Click to expand...
Click to collapse
Found the right debrick file
Update: I found this debrick file for my S3 on Koodo with 4.4. : http://d-h.st/w7g
Thanks to mitch0422 and this thread: http://forum.xda-developers.com/showthread.php?t=2598240