Related
Has anyone successfully done this??
Link: http://forum.xda-developers.com/showthread.php?t=1220181
I finally hard-bricked my Vibrant, and I'm wondering if this has been accomplished, instead of sending it to a specialist to JTAG it the traditional way!!
Im trying to see if I can resurrect it myself instead of losing it for a week!
And yes I'm aware of the One guy here in the states that does JTAGing, but Id be seriously outa work for a week as my phone is my work/life line, cuz I'm an Independent contractor, so its not about the money Id spend but the time down without a way to work/communicate, I haven't contacted TMO yet and told them it was hosed using the Kies method to upgrade it to Froyo. Wish I never had done that!! Should've known better, didn't see/read any post about the horrors of using Samsungs KIES program until it was too late!!!
I was trying to purge a SH 5.0 install that went bad, I flashed back to stock Eclair. Then went to Froyo, But thats when I developed a problem with boot looping after doing Froyo, so I tried the KIES program to go to "FROYO" and that's when It bricked!!!
Anyways its bricked hard, and I'm wondering if this has actually been done successfully!
And any tips that I might need to get the Heimdall Program to actually detect it thru the USB method, would be awesome! Even though it wont turn on!!
Link to the thread: http://forum.xda-developers.com/showthread.php?t=1220181
JTAG isn't a method that can be done through usb. If you had googled jtag, you would have found out that it is a physical port built into the motherboard of our phones. In fact most electronics have a jtag port.
*Joint Test Action Group**(*JTAG*) is the common name for what was later standardized as the*IEEE
1149.1**Standard Test Access Port and Boundary-Scan Architecture*. It was initially devised for testing*printed circuit boards*using*boundary scan and is still widely used for this application.
Today JTAG is also widely used for*IC*debug ports. In the embedded processor market, essentially all modern processors support JTAG when they have enough pins.*Embedded systems*development relies on*debuggers*talking to chips with JTAG to perform operations like*single stepping*and*breakpointing. Digital electronics products such as*cell phones
*or awireless access point
*generally have no other debug or test interfaces.
In order to flash your phone, it will have to be dismantled, and hooked up to the jtag box.
Beware of angry gingerbread man
Adamcooks, I read the entire squabble about this between you and RaverXX
I downloaded your one click as well!!
So can you give me some advice on how to get my phone to even simply turn on, WO the soldering involved using traditional method of JTAGing??? Mine wont power up or show any LED activity, nothing when plugged in or do anything using traditional methods known to work with "SOFTBRICKING"
I mean, it seems my Boot loader is corrupted, or the other file you suggested, when Raver and u were arguing!! If I could even get a faint indication of life from the phone, It could be brought back to DL, but a DL Jig, as well as all the other extensive methods to get it even to power on, let alone go into DL mode isnt working at all, after many, many try's!
Can your one-click program, with the proper BL's for my T959 Vibrant be acknowledged by either yours or Heimdall's Program, so as to even be able to flash this WO, Jtaging it, even if it wont even power up in any way to handshake with my lappy???
BTW, I'm not trying to start another **** storm, after what happened with RaverXX, but it seems some of the people who had the same scenario as I do, were successful, so I'm wondering between the 2 of you, how to approach and try this, I respect both ya'll's work and contributions, but for me the bottom line is to get my phone working once again, short of either#1 JTAGing it, or trying to go thru the painful experience of trying to get TMO to replace it with a new same model, because KIES fubar'd it!!
Anyway I wish you 2 guys could lay out the proper set of instructions as you suggested, along with the proper files or links, for us to try either his method or yours. I think its possible to resurrect these phones, this way short of physical damage, and as such!! IDT you 2 fellas would've put so much effort into this theory, if there wasn't some merit to it!
So I'm all ears and eyes to your suggestion of how to get my phone to even breath again, so I can go back to DL mode, and get her working again!!
But when nothing what so ever happens, no power up, no lights, no nothing occurs, it seems to me its bricked, even though you say a truly bricked phone , has physical hardware damage, which tech is prolly correct, however in this case, mine is software bricked very hard!!!! And for purposes of communication and clarity, Ill stick with bricked, If I knew the MB was fried and or damaged, Id simply order another one, and replace it, and power up the phone, and be done with this ordeal, but my corruption occurred during using the Samsung KIES program, regrettably!!
And I'm fairly certain that either the Boot loader file is corrupted or the file you say creates a black screen usually displaying the Pc-phone logo is done for, so again, should I try the command prompt instructions to fix that, or do I use your one-click, or go to ravers method ?? I asking legitimately, because I know your knowledge in these matters has merit!! Thanks for your reply!!
Unless he changed his account, that was a different Adam in that other thread. I still say try it, cant make things any worse.
Sent from my ZenDroid, meditating on the XDA App
I may give a sharp response sometimes, but an internet squabbler I am not. connextion(sp) has a motherboard cradle that contacts the correct pins to jtag flash, without causing any damage to your phone.
Have you tried the resistance jig? I think that skorpn is the one who makes them ( 301k ohm resistor plug into the usb port can force d/l mode if the bootloaders aren't borked)
these are the last two resorts in ng phone resurrection.
Beware of angry gingerbread man
Ya My mistake Sorry
Ya I got you mixed up with another developer who has a very similar handle, so many apologies, however I wasn't flaming you anyway, shape or form, just apologizing for the mistaken ID
BTW Is the skorp resistance Jig a completely different animal from the DL Jig Tech Mobile sells doing the same result, in other words is it able to bring a phone like mine in the condition it is, into DL mode??? I saw the Skorp design, it just seems to me, its the same thing I already have from Tech Mobiles design. Accomplishing the same thing, but for phones that actually power on in some way shape or form, light off etc!!
Anyway thanks for your input, and effort, I'm still sorting all the info on everybody's suggestions and methods, short of JTaging it!!! Gonna make a move on a procedure here soon, this evening!!
Ok I was having trouble getting S-off, it was getting stuck at the first reboot and was saying waiting for device, well i fianall got to where it said to do the wire trick, and well, now the usb port isnt working on the phone! I can't reflash anything, i can get to fastboot, but my computer doesn't detect it! I'm Screwed! Please help!
Db0y505 said:
Ok I was having trouble getting S-off, it was getting stuck at the first reboot and was saying waiting for device, well i fianall got to where it said to do the wire trick, and well, now the usb port isnt working on the phone! I can't reflash anything, i can get to fastboot, but my computer doesn't detect it! I'm Screwed! Please help!
Click to expand...
Click to collapse
Make sure you close all terminal windows and reset the computer. I was having this problem too and simply restarting the computer and phone seemed to solve their inability to talk to each other.
Also, I was having the same problem of it hanging on "waiting for device" before I even got to do the wire trick. Oddly enough, it seemed to be related to the kernel I was using (SebastianFMs OC based off the latest ICS kernel). As soon as I tried using an earlier ICS kernel before I tried again, all the sudden it was detecting my phone correctly and would go on to the wire trick part immediately.
a.mcdear said:
Make sure you close all terminal windows and reset the computer. I was having this problem too and simply restarting the computer and phone seemed to solve their inability to talk to each other.
Also, I was having the same problem of it hanging on "waiting for device" before I even got to do the wire trick. Oddly enough, it seemed to be related to the kernel I was using (SebastianFMs OC based off the latest ICS kernel). As soon as I tried using an earlier ICS kernel before I tried again, all the sudden it was detecting my phone correctly and would go on to the wire trick part immediately.
Click to expand...
Click to collapse
I've tried this already. still nothing:/
It won't even charge. I've tried 3 different computers, usb cords and still nothing, I'm trying to reflash my Boot.img and my recovery.img through the PH98IMG.zip method, but I can't seem to get either of them working. I'm running GB, and all the PH98IMG.zip files i've found are all for ICS.
Db0y505 said:
I've tried this already. still nothing:/
It won't even charge. I've tried 3 different computers, usb cords and still nothing, I'm trying to reflash my Boot.img and my recovery.img through the PH98IMG.zip method, but I can't seem to get either of them working. I'm running GB, and all the PH98IMG.zip files i've found are all for ICS.
Click to expand...
Click to collapse
Real quick, when you say it won't charge. Do you mean if you plug it into a wall it won't charge, even when turned off?
Pull out the battery entirely, connect the phone to the computer, and turn on the phone. You should be able to get to HBOOT via USB power. Does this work?
Think this is the one you want
View attachment PH98IMG.zip
sindroidx said:
Real quick, when you say it won't charge. Do you mean if you plug it into a wall it won't charge, even when turned off?
Click to expand...
Click to collapse
Correct, the LED light won't go on.
a.mcdear said:
Pull out the battery entirely, connect the phone to the computer, and turn on the phone. You should be able to get to HBOOT via USB power. Does this work?
Click to expand...
Click to collapse
Nope, this doesn't work.
Khayos said:
Think this is the one you want
View attachment 1021148
Click to expand...
Click to collapse
I'm going to try this now.
Db0y505 said:
I've tried this already. still nothing:/
It won't even charge. I've tried 3 different computers, usb cords and still nothing, I'm trying to reflash my Boot.img and my recovery.img through the PH98IMG.zip method, but I can't seem to get either of them working. I'm running GB, and all the PH98IMG.zip files i've found are all for ICS.
Click to expand...
Click to collapse
It's going to be ok, just take a deep breath and calm down. If you're stressed out, take a break and put your feet up. Panic and stress are the only thing that will brick a rezound. Anything else can be fixed, besides of course hardware failure, and that's not your issue.
Khayos said:
Think this is the one you want
View attachment 1021148
Click to expand...
Click to collapse
Do i put my boot.img in here, or do i just flash it as is?
CharliesTheMan said:
It's going to be ok, just take a deep breath and calm down. If you're stressed out, take a break and put your feet up. Panic and stress are the only thing that will brick a rezound. Anything else can be fixed, besides of course hardware failure, and that's not your issue.
Click to expand...
Click to collapse
I'm not really stressed out, I mean i switched back my Droid 4 while the Rezound is down so i have a working phone, I just want to get my rezound up an running again...
What do you think could be causing this if it's not hardware failure?
Db0y505 said:
I'm not really stressed out, I mean i switched back my Droid 4 while the Rezound is down so i have a working phone, I just want to get my rezound up an running again...
Well what do you think could be causing this?
Click to expand...
Click to collapse
Honestly I'm concerned that your phone doesn't see power or respond to USB at all anymore. Is it possible that you've broken the little tab inside the port on your phone, or is it possible that some piece of debris is shorting out the contacts in there?
you say its still possible to get to HBOOT, which means if you can remove your SDCARD and put a PH98IMG.zip file on it with the correct boot.img you can get it booting again - but I'm concerned that the USB port is damaged and therefore the phone may be useless once the battery is depleted.
a.mcdear said:
you say its still possible to get to HBOOT, which means if you can remove your SDCARD and put a PH98IMG.zip file on it with the correct boot.img you can get it booting again
Click to expand...
Click to collapse
Technically you can, it's just a huge pain in the ass, I've done it before. You have to pull the battery out at like a 45 degree angle but make sure there's enough pressure on it so it still makes contact, then slide out the sdcard with your fingernail and get the sdcard. Place the battery back in, get a card reader and put it on there, then reverse the process.
a.mcdear said:
Honestly I'm concerned that your phone doesn't see power or respond to USB at all anymore. Is it possible that you've broken the little tab inside the port on your phone, or is it possible that some piece of debris is shorting out the contacts in there?
you say its still possible to get to HBOOT, which means if you can remove your SDCARD and put a PH98IMG.zip file on it with the correct boot.img you can get it booting again - but I'm concerned that the USB port is damaged and therefore the phone may be useless once the battery is depleted.
Click to expand...
Click to collapse
I just looked at usb port, and it's perfect, i blew some compressed air so it's clean.
And yeah i can get into hboot, but im having a problem flashing a PH98IMG.zip, it keeps saying "Parsing" when it finds the file, and it doesn't flash the boot.img
And I'm not worried about the battery depleting, I have a Thunder Bolt to charge the battery. But the fact that my pc won't detect my phone is worrying me.
Db0y505 said:
I just looked at usb port, and it's perfect, i blew some compressed air so it's clean.
And yeah i can get into hboot, but im having a problem flashing a PH98IMG.zip, it keeps saying "Parsing" when it finds the file, and it doesn't flash the boot.img
And I'm not worried about the battery depleting, I have a Thunder Bolt to charge the battery. But the fact that my pc won't detect my phone is worrying me.
Click to expand...
Click to collapse
Yeah it sounds like something is definitely wrong with the phone... has me wondering if the USB issue and the hanging on "parsing" are related by a common malfunction or failure of the device.
Either that, or the PH98IMG.zip file you have on there is bad? I suppose that is entirely possible too... Or if somehow the installed kernel became corrupt, I could see the phone behaving the way it is.
I would try re-downloading another kernel as a PH98IMG.zip file, putting it on the SDCARD and trying all over again with a completely new download. Don't use the one you've been using, just to eliminate a bad PH98IMG.zip as the possible culprit.
a.mcdear said:
Yeah it sounds like something is definitely wrong with the phone... has me wondering if the USB issue and the hanging on "parsing" are related by a common malfunction or failure of the device.
Either that, or the PH98IMG.zip file you have on there is bad? I suppose that is entirely possible too... Or if somehow the installed kernel became corrupt, I could see the phone behaving the way it is.
I would try re-downloading another kernel as a PH98IMG.zip file, putting it on the SDCARD and trying all over again with a completely new download. Don't use the one you've been using, just to eliminate a bad PH98IMG.zip as the possible culprit.
Click to expand...
Click to collapse
Same problem trying to flash the new kernal.
I think something is went wrong the phone's hardware.
DO you think i could make an Asurin claim on it? It already has a broken screen.
Db0y505 said:
Same problem trying to flash the new kernal.
I think something is went wrong the phone's hardware.
DO you think i could make an Asurin claim on it? It already has a broken screen.
Click to expand...
Click to collapse
If it has a broken usb/charging port, hell yes I'd definitely try for an exchange first on the basis that a critical part failed. If they give you grief over the damaged screen then definitely do an insurance claim on it, assuming you got insurance on it..
a.mcdear said:
If it has a broken usb/charging port, hell yes I'd definitely try for an exchange first on the basis that a critical part failed. If they give you grief over the damaged screen then definitely do an insurance claim on it, assuming you got insurance on it..
Click to expand...
Click to collapse
Alright, I'll try for an exchange, But would they get mad because it boots to the green arrow screen?
Db0y505 said:
Alright, I'll try for an exchange, But would they get mad because it boots to the green arrow screen?
Click to expand...
Click to collapse
oh yeah, its stuck on the juopunutbear screen? that could make it a little obvious then huh? I suppose that is a bit of a risk - perhaps just an insurance claim would be best in your case. I exchanged my last unlocked/rooted Rezound, but the screen was broken and wouldn't turn on anymore. no problems for me though...
a.mcdear said:
oh yeah, its stuck on the juopunutbear screen? that could make it a little obvious then huh? I suppose that is a bit of a risk - perhaps just an insurance claim would be best in your case. I exchanged my last unlocked/rooted Rezound, but the screen was broken and wouldn't turn on anymore. no problems for me though...
Click to expand...
Click to collapse
Yeah lol. Well what I suppose i could try it, or just run the battery out so it won't turn on and they can't charge it.
Well thanks for helping out, Ill post back what happens when i get off the phone.
Just throwing it out there. As the title states. I attempted the S-off, failed a couple of times, more than likely due to my timing on the wire trick. Then my computer was unable to find device anymore. Long story short, I got my rom to reboot, however the phone will not connect to computer or charge. Tried Pc, Mac, different usb cords. Wiped, reinstalled rom, pulled battery, etc..
This is a risk that I took, and I take full responsibility for that. But just beware that this could affect your hardware and not just your software too, which makes sense because you are messing with the hardware. I am def in the minority here, but I thought I would share. But something to think about. The phone now still functions but I have to take out the battery to charge, and I can't push any files to the phone.
ive never heard of anyone's usb port getting fried with the s-off method but i guess it's possible since your basically grounding your device out.
I know it won't help you with fastboot, but you can still do ADB over wireless. Look for instructions on how to enable it via terminal, or just go the the store and find a widget or app to enable it. At least with functional ADB, you can still push files to your phone using wifi tether or if they are on the same wireless network.
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
con247 said:
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
Click to expand...
Click to collapse
do you think the wire trick is causing this? if soo that's kinda scary.
fix-this! said:
do you think the wire trick is causing this? if soo that's kinda scary.
Click to expand...
Click to collapse
I had the exact same thing happen to me on my original Rezound, while I was doing all sorts of fastboot stuff to completely wipe it and prepare it to be shipped back to Verizon. In the end, it shipped back to them in a state where it would ONLY boot to hboot, because it had no /boot or /system or /data or /recovery partitions or anything. I don't really know what happened, but before I could run the RUU to complete the job, the USB connection just stopped working and it wouldn't charge. Exactly the same situation, except it was on its way back to Verizon anyway with a dead screen so I didn't bother to investigate any further.
To the people who have had the problem, were you using an uninsulated wire?
tekhna said:
To the people who have had the problem, were you using an uninsulated wire?
Click to expand...
Click to collapse
Or else inadvertantly touched the wrong terminals ? Just trying to figure out how it could happen.
lack of usb function was a product of a corrupted misc image on the HTC Desire. It is possible the same thing happened here so that is being tested. It is worth looking into as a last resort before sending it back.
Yes I was using an insulated wire. I placed the wire exactly where the pictures show. I'm really not sure what happened. But at least I have a backup phone.
Sent from my Galaxy Nexus using XDA
con247 said:
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
Click to expand...
Click to collapse
Thanks con
Sent from my Galaxy Nexus using XDA
Knew I didn't wanna do it.
Sent from my ADR6425LVW using xda premium
http://forum.xda-developers.com/showthread.php?t=1620803
Here's a case of fried USB but no s-off. Currently unlocked. Any ideas?
Snuzzo said:
http://forum.xda-developers.com/showthread.php?t=1620803
Here's a case of fried USB but no s-off. Currently unlocked. Any ideas?
Click to expand...
Click to collapse
Sounds like he is in the exact same boat as me. Will be following that thread as well.. Thanks.
Me three
In same Boat.
Please post a cure if you find one.
Another nice option for transferring files is SSHDroidPro used with something like WinSCP.
I know you tried wiping your rom, but did you try an RUU? On the off chance it is a corrupted partition that might be able to fix it. Worth a try anyway.
Maybe this question belongs in the general android dev section, if so then sorry. What makes a phone "brick". I know what it means, but why can't we in brick them. If everything is wiped, what keeps us from accessing the wiped partition with a pc and doing what we want to with it. We do it with computers all the time. I know its not exactly the same, but its very similar isn't it? Is it like the BIOS going bad on a pc that causes them to brick?
Sent from my ADR6425LVW using xda app-developers app
From what I have heard, at least on the Rezound, bricks are generally caused by bad hboots. People do often compare hboots to BIOSs, but when they do, they always qualify their statements, adding that the two actually have little in common, but it's the best comparison between Android and PC. I'm sure someone else can explain that a lot better than I can. I believe a brick can also, theoretically, be caused by a bad kernel/boot partition, since it is what tells the phone where to get the information needed to boot (or something like that).
People also sometimes call it bricking when they just mess up the hardware in some way, like while replacing the digitizer.
Their are methods to unbrick from an hboot related brick, but they do not always work.
What Max said.
Just wanted to say you did indeed post this in the correct section. Even if it's a development related question, questions belong in the questions section
Sent from my ADR6425LVW using XDA Premium.
I always thought the same thing why can't you just wipe everything and reinstall if the brick is caused by a software issue then what's the stop you from removing that software and putting working stuff on.
The only thing I can think of to answer my own question would be, for example, you know how you can adjust the voltages to the CPU, well lets say you install some bad or damaged software which controls the Hardware say you send too much voltage to a component such as the CPU and you fry the component by sending too much voltage or maybe its even possible by sending not enough voltage.
Just a thought anyways . I could be way off I have no idea really.
Sent from my HTC One S using xda premium
Bad hboot brick is the most common common and it is irreversible because you need a functional hboot to flash anything. So a corrupted hboot leaves you with a catch 22. Your hboot is bad, you want to flash a working hboot but your bad hboot can't flash anything so your stuck.
A kernel or bootlooping brick is a soft brick because you can still boot to hboot or recovery and flash a working kernel
Sent from my ADR6425LVW using xda app-developers app
Can't a bad radio brick it too? I know on a pc you can start with nothing, no boot partition or mbr, and the kernel is flashed with the os (windows, linux), and you boot from a cd or floppy. The only thong you start with is BIOS. Is being incapable of booting from another source like USB or sd card the main reason we can't unbrick most phones? I guess I'm just looking for deeper detailed nerd answers for a better understanding. I'm a nerd as most of you would probably claim to be too lol and I just want to get a better understanding of how it all works.
Sent from my ADR6425LVW using xda app-developers app
There are three main parts to phone firmware. You have the boot loader, which handles very low level stuff and generally doesn't touch partitions, but provides a boot environment for other software such as recovery and system...which is why, in Broad com routers, it is called the CFE or Common Firmware Environment. Think of it as the BIOS of the phone. If the boot loader is corrupt or damaged, chances are there will be no way to recover the phone via normal methods; JTAG must be used to directly interface with the hardware and force reflash of the boot loader.
Recovery is in a way like DOS. It has the ability to create, mount, change, and delete partitions, but can't touch low level stuff like the radio or bootloader. It can modify and remove files on partitions and change specific things such as the kernel. A damaged recovery can usually be fixed without any special tools as the phone will boot but won't go into recovery mode. In the case of the Rezound, a PH98IMG flash would fix it.
The operating system of the phone is as Windows or Linux GUI is to a computer. It provides the user with an easy to use environment as well as tools and software to help the user do what he wants to do. A damaged OS may boot, and problems may be limited to a few specific apps, or the problem may be system wide to the point of unusability...or if there is something wrong with the kernel, the OS will not start at all, and will be stuck in a boot loop. Easily fixable via recovery.
socal87 said:
JTAG must be used to directly interface with the hardware and force reflash of the boot loader.
Click to expand...
Click to collapse
What's JTAG?
feralicious said:
What's JTAG?
Click to expand...
Click to collapse
A lot of devices have JTAG ports that allow us to use another piece of hardware to access the deeper levels of the hardware and software.
This makes it possible to unbrick by fixing those deep files that are required for the device to work.
Also, Wikipedia is your friend.
Here's the nerdiest answer you're going to get. Your phone is ultimately just a large hunk of copper and silicon. It contains all sorts of microchips and connections and are necessary for literally every function of the phone. Literally... From the LEDs to the audio components. Everything. If youve heard of a schematic that's what I, talking about. Each one of these microchips must be programmed form its specific function. Were literally talking hardware level here. No Android OS no hboot etc.
Point of explaining all of that being that there are all sorts of programmable parts of the phone that you will never modify, access, or even think about. If you manage to access and screw up the wrong thing.. You can quickly go from functioning phone to just a hunk of copper and silicon. Hboot is the lowest layer software that devs will modify. If you screw up the hboot.... You are left with a brick. Is it ultimately possible to unbrick in any situation? Yeah of course. How else would HTC have made the phone in the first place. But if you screw up the hboot... You're gonna need an engineering degree to fix that thing. And at the cost/effort that that would take.. You'd be better off buying a new phone. Thus your phone is totaled and its best use just because a paperweight.
Sent from my Nexus 7 using Tapatalk 2
I think it's important to note that most of the phones people post about being "bricked" aren't actually bricked. A lot of times people panic and if they can't fix their phone, they call it a brick. It's kind of a common, often used slang term. Now there's terms like hardware brick, hard brick, software brick, and soft brick and probably some more.
But if it's fixable in my opinion using a computer and commands, or if you can see it's getting power, it's usually not really bricked.
For example, when the s off process came out the forums were over run by people who "bricked" their phones while trying to attain s off. What actually happened in a big number of these cases was that the windows script replaced the boot.img that was on their phone with a custom boot.img for the service mode. When there was a windows error with the software which was newly developed and released, and the windows app hung up or the computer went weird mid process, they had a black screen with a funny image, like a disk and arrow maybe, and when they turned the phone on it only went to that screen. In fact it happened to me which is why I figured out how to fix it and what caused the problem.
Now all they would have had to do is run a fastboot command from their computer, "fastboot flash boot boot.img" to flash the boot.img that matched whatever rom was installed on their phone, and they would be back up and running. But for a large number of users, when they phone was unresponsive and turning it on took them straight to the black screen, they considered it "bricked."
When in fact the phone was doing exactly what it had been commanded to do, and it was the person who was expecting something unreasonable, when you think of it in 1's and 0's, or black and white. Of course this isn't always the case, there are some real bricks, just not as many as one would first believe if they scanned through forum topics for the word bricked in the title.
I dun goofed. I, very ignorantly, flashed the Boeffla kernel intl. version to my poor USA phone, which could not handle that.
Now, my phone won't turn on whatsoever. Holding the power button does nothing. Recovery/Download combinations also do nothing. Battery pull did nothing. Phoan is kill. I understand that there are other ways to fix these phones but there are far too many and far too few reviews of said methods. I believe my phone is hard bricked, so I'm not sure if other types of restoration are possible. I do know of ONE, that being JTAG, but I'm not sure I want to go that far. I wanted to know if there was anything else I could do, so I came to the source of all Android knowledge, XDA-devs. forums.
I've reviewed the "Official Samsung Way" that involved shorting a resistor to force the phone into Download mode after doing some other stuff. I don't think this will work as my phone is hard bricked.
I've looked at USB JIGS. However, they appear to only fix soft bricks.
I've looked into a more unique method, but I don't own a 16 GB SD Card at the moment, only a 32 GB, so I'm not sure if that will work.
(I'm a new guy so I can't post links. Just use tinyurl . com / srslyXDA (remove the spaces and you'll get a whole link!)
I have tried it, sort of, but I'm not sure if it worked AT ALL, or if it was the fact I was using a 32 GB SD card. Either way, I'd rather not buy the SD card until I knew for sure if this would work.
Just so we're clear, I'm using a Virgin Mobile (AKA rebranded Sprint) Samsung Galaxy S3. It originally ran CM11.
Any suggestions? I'm open to JTAG but only if there's a good tutorial for it. I think someone once recommended a RIFF box but those just happen to be a good sum of money.
skarlitz said:
I dun goofed. I, very ignorantly, flashed the Boeffla kernel intl. version to my poor USA phone, which could not handle that.
Now, my phone won't turn on whatsoever. Holding the power button does nothing. Recovery/Download combinations also do nothing. Battery pull did nothing. Phoan is kill. I understand that there are other ways to fix these phones but there are far too many and far too few reviews of said methods. I believe my phone is hard bricked, so I'm not sure if other types of restoration are possible. I do know of ONE, that being JTAG, but I'm not sure I want to go that far. I wanted to know if there was anything else I could do, so I came to the source of all Android knowledge, XDA-devs. forums.
I've reviewed the "Official Samsung Way" that involved shorting a resistor to force the phone into Download mode after doing some other stuff. I don't think this will work as my phone is hard bricked.
I've looked at USB JIGS. However, they appear to only fix soft bricks.
I've looked into a more unique method, but I don't own a 16 GB SD Card at the moment, only a 32 GB, so I'm not sure if that will work.
(I'm a new guy so I can't post links. Just use tinyurl . com / srslyXDA (remove the spaces and you'll get a whole link!)
I have tried it, sort of, but I'm not sure if it worked AT ALL, or if it was the fact I was using a 32 GB SD card. Either way, I'd rather not buy the SD card until I knew for sure if this would work.
Just so we're clear, I'm using a Virgin Mobile (AKA rebranded Sprint) Samsung Galaxy S3. It originally ran CM11.
Any suggestions? I'm open to JTAG but only if there's a good tutorial for it. I think someone once recommended a RIFF box but those just happen to be a good sum of money.
Click to expand...
Click to collapse
I would atleast try the jig. i have woken up a hard bricked s2 with it.
coltlacey1 said:
I would atleast try the jig. i have woken up a hard bricked s2 with it.
Click to expand...
Click to collapse
Well I don't want to go about ordering every little thing and such. It may very well be that I need to get it repaired via JTAG, which could either be me doing it or someone else. Either way, I want to be sure. Do you know of anyone who has successfully revived an S3 with this method?
All u have to do is go to radio shack and get a few resistors, and make sure you have the right cord end. Very easy to make. Just takes a little soldering. I don't know of anyone that has done it yet on an s3 but haven't really asked around. If it doesn't work you're out maybe $5.
coltlacey1 said:
All u have to do is go to radio shack and get a few resistors, and make sure you have the right cord end. Very easy to make. Just takes a little soldering. I don't know of anyone that has done it yet on an s3 but haven't really asked around. If it doesn't work you're out maybe $5.
Click to expand...
Click to collapse
I don't think you read my post correctly. My phone is hard bricked, not soft bricked. It doesn't turn on whatsoever. It doesn't freeze, it doesn't boot loop. It stays off. No LED lights. No vibrations. Hard bricked. It'd be different if it gave signs of life, but since I flashed it with a kernel not made for my device, it is most definitely hard bricked. I'm afraid it'll need to be JTAG'd or booted off of an SD card. I don't have a 16 gb one on me at the moment so if you could let me know of anyone who does cheap JTAG.
looks like youll need to locate an sd card. I dont know of anyone that does cheap jtags but i did see a youtube link somewhere that was addressing jtag inquiries but it was from some time ago.
if you do locate an sd >>http://forum.xda-developers.com/galaxy-s3/general/galaxy-s-iii-gt-i9300-hard-brick-fix-t1916796