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
Related
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
ok i worked on this phone for a few months got fed up and gave up for a few now im back lol.i have a s3 that bricked after a ota update before 4.4 updates to the s3.i have done everything that was on this site.i cant dl anything to it from odin. i have done pit files and all.my question is what file do i put in the bootloader box in odin????? thats about the only thing i have'nt done because i cant seem to find out if its just a boot loader file are a whole kernel.btw the whole issue is when it took the update it lost recovery but it wont let me dl a recovery...any help in making this work would make my hair grow back because im one of those people who wont throw this phone out till i figure it out lol
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.....)
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